notbatman and opentoe thanks for the tip. by having a look at that I noticed i was getting a load of invalid voltage errors.  on investigating it seems if you alter the frequency the voltage for the chips gets wiped from the user config even though there isn't an option to do anything with the voltage.

no reason to reboot except of course when I tried using the cgminer stop/start or restart commands they failed to work and generated an error so the only option was to reboot. which funnily enough worked.  and I understand why

of course actually what I should have done was
1 cd /etc/init.d
2 cgminer stop
3 cd /usr/bin
4 mv cgminer cgminer.bak
5 wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
6 chmod +x cgminer
7 cd /etc/init.d
8 cgminer start

or do it in 5 steps

 1. cd /usr/bin
 2. mv cgminer cgminer.bak
 3. wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
 4. chmod +x cgminer
 5. Reboot

2 wires in the UART  - specifically 3 & 5 (4 is an earth/ground)

I'm pretty sure though by at the cable to the blades it's serial comms

http://ww1.microchip.com/downloads/en/DeviceDoc/61107G.pdf

it seems to go moving away from the blade

UART - MCU - USB hub

the s3+ firmware + the 4.6 cg miner has pretty much got rid of the hardware errors I was getting on one of my S3s.  ok it was only 1.5% (according to Mantmonitor) now it's 0.0018%.

you can check the version via the api


I have noticed bursts of hash rate significantly over 500 even though my frequencies shouldn't get the rate that high as I'd get an X in the row of os when using the higher frequencies  one is on 237.5 and the other 231.25. just spotted one claiming 657.

in response to count fracular I gave it a go but it didn't work as it was compiled for a S1 so the driver is slightly different (I think)  anywayyou can now get an up to date version of cgminer

https://bitcointalk.org/index.php?topic=671189.msg8722578#msg8722578

to get it to work (a potted rehash of what's in the other thread)

ssh into your Antminer

cd /etc/init.d/cgminer stop
cd /usr/bin
mkdir oldcgminer (to keep a copy of the old one)
mv cgminer oldcgminer/cgminer
wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
chmod 755 cgminer
reboot

to alter via the advanced settings

find you way to (I used WINSCP to find it)

/usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

that has the frequencies that are available via the user interface


conf:tab("advanced", translate("Advanced Settings"))
pb = conf:taboption("advanced", ListValue, "freq", translate("Frequency"))
pb.default = "18:218.75:1106"
pb:value("16:250:0982", translate("250M"))
pb:value("17:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M (S3+ default)"))
pb:value("18:218.75:1106", translate("218.75M (S3 default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))


are the ones available by default on the latest and greatest firmware

Mantmonitor worked for me, are you using API access or web?   Web didn't seem overly happy when I tried it

you're in luck cgminer 4.6.0 built for ANTMINERS

https://bitcointalk.org/index.php?topic=671189.msg8722578#msg8722578

 I did see a post be someone using different ports while on the same IP address but that was more in passing than as an instruction on how to do it. what you actually do is connect 1 at a time log into the web interface and change the IP manually.  some suggest using DHCP but the IP address is random so it makes accessing the web interface a bit hard if you don't know for sure what the IP address is

anyway the guide you are after is

https://bitcointalk.org/index.php?topic=702653

No new version of cgminer as far as I can tell.

More frequency options in the advanced setting tab

Best share & Getworks now have numbers in them

they've also fixed the OPKG packages link

S3  - would the login page that initially comes up in place of the status page cause the error?

When using the non-api method to get the info I get in the log - and nothing in the ants tab

"04/09/2014 10:49:09: S3:1.102:80 responded with status page
04/09/2014 10:49:09: An error occurred when parsing the web output for http://192.168.1.102/cgi-bin/luci/;stok=/admin/status/minerstatus/: Object reference not set to an instance of an object."

It appears using that link even if you are logged in to your Ant it wants you to log in again

I know it's easy enough to swap to API, but if you swap from API to web then api (and then in this case back to web) the Ant section gets filled with error details rather than overwriting the bad one

http://oi61.tinypic.com/2wnsoc8.jpg

the info on your ants is stored in the registry I had so many that it refused to work so I had to track down where the data was kept

if you turn off the API option itll help to get some stuff though to the monitor

nope same program you just say your S3 is a S1.  as it says they are almost the same (or at least were until this latest S3 firmware)

M

I've managed to get a new S3 firmware version antminer to talk to your program by unchecking the USE API box.

in my log  when starting up

"6/08/2014 20:24:24: M's Ant Monitor v2.6a starting
16/08/2014 20:25:27: Initiated refresh
16/08/2014 20:25:27: ERROR when querying S1:101 (step 1): After parsing a value an unexpected character was encountered: {. Path 'STATS[0]', line 1, position 212."

got the same when I tried rechecking the USE api box.

managed to reboot the S3 even thought it's not using the API

hope this helps

in mm when requesting version type

"Request":"version","Response":"STATUS=S,When=1408218399,Code=22,Msg=CGMiner versions,Description=cgminer 3.12.0|VERSION,CGMiner=3.12.0,API=3.1,Miner=7.0.0.3,CompileTime=Thu Aug  7 10:56:26 CST 2014,Type=S3|\u0000","CoinName":"","Machine":"192.168.1.101:4028"}

in comparison to an unupdated one
"Request":"version","Response":"STATUS=S,When=1408218579,Code=22,Msg=CGMiner versions,Description=cgminer 3.12.0|VERSION,CGMiner=3.12.0_7.0.0.3,API=3.1|\u0000","CoinName":"","Machine":"192.168.1.102:4028"}

if my count is right it's something in the bold above I'd expect "S3" is the issue

best place to start I guess would be their api part.  http://www.mobileminerapp.com/#api

I've got it combined with mutilminer and it seems that all I can do is detect the antminers on the network but can't do much more than the basic hash rate, pool, whether active or not and a temperature as multiminer is accesing them through the "standard" no changes allowed cgminer API

ah no to get remoting you have to turn on perks and give the writer of mutiminer 1% of your hashrate (in multiminer anyway)

My S3s have a bestshare option in the web interface which on the both of mine say 0, which is what is reported on M's Ant Monitor and Multiminer. it appears the S3s version of CGminer is slightly different to S1's so maybe it's not calculated any more, according to multiminer api lookup S1's version is 3.12.0 and S3's is 3.12.0_7.0.0.3, while the ants web interface software sectiom gives them both the same version 3.12.0-1