D I N G - D I N G - D I N G - D I N G
500 pages of posts for the venerable old S3 (aka The Tank). While not a record, I thought it warranted a mention. Never owned one, but I almost wish I had.
Topic: ANTMINER S3+ Discussion and Support Thread - page 22. (Read 710164 times)
I get that lua error when i mess up with cgminer launch config parameters. To fix it i had no choice but to revert to default. But then i solved the inherent problem by changing firmware. 
i just upgraded firmware to latest one, it had some custom, i don't remeber now wich one.
I get that lua error when i mess up with cgminer launch config parameters. To fix it i had no choice but to revert to default. But then i solved the inherent problem by changing firmware.
I just upgraded y firmware.
it had some custom.
i configured it and rested to connect second board now i cant get into the GUI.
i get this
the miner is hashing i can se it on the pool stats running .
it had some custom.
i configured it and rested to connect second board now i cant get into the GUI.
i get this
Quote
/usr/lib/lua/luci/dispatcher.lua:582: bad argument #1 to 'pairs' (table expected, got nil)
stack traceback:
[C]: in function 'pairs'
/usr/lib/lua/luci/dispatcher.lua:582: in function 'createtree'
/usr/lib/lua/luci/dispatcher.lua:230: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:195: in function
stack traceback:
[C]: in function 'pairs'
/usr/lib/lua/luci/dispatcher.lua:582: in function 'createtree'
/usr/lib/lua/luci/dispatcher.lua:230: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:195: in function
the miner is hashing i can se it on the pool stats running .
Kano,
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Both.Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Thanks for the response. Do you have some sort of reference sheet with frequencies and voltages?
there was one posted on this thread
https://bitcointalksearch.org/topic/bitmain-antminer-s3-support-and-overclocking-thread-699064
but i cant tell you how accurate it is since most s3s cant change voltage and those that have gotten it to work did it by soldering resisters on the dc-dc converters.
anyway its a good thread to read..
Kano,
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Both.Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Thanks for the response. Do you have some sort of reference sheet with frequencies and voltages?
No, I have none.
Kano,
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Both.Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Thanks for the response. Do you have some sort of reference sheet with frequencies and voltages?
Thanks to input from Rich, I may have a board with a multi-phase buck converter and would like to experiment some more. See https://bitcointalksearch.org/topic/m.12222540 for details.
Kano, or anyone else, do you know the correct format to input for voltage? Does the 0x0650 listing indicate 0.065 or 0.65 V, or some incremental offset from the default?
Good news that you have one of the S3 that accepts voltage input from cgminer. I understand the format for voltage input is 0650 for 0.65 volts.
Rich
I updated to Kano's latest and tried setting to 0625. In miner status it shows 0x0650 under voltage, so I assume it took. But it didn't change anything with respect to efficiency. See link below for details.
https://bitcointalksearch.org/topic/m.12211638
Yeah I'm guessing that some or all of the S3 don't actually support voltage change.https://bitcointalksearch.org/topic/m.12211638
(see discussion above/on the previous page)
It wont cause any problems, but it simply uses the driver interface to change the voltage as per "specifications"
If it's possible, it will work, if it's not possible it wont change anything.
I tried 0625 assuming this would lower the voltage to 0.65 V and got the 0x0650 listed in the voltage value after restarting. When I tried imputing 625 I thought I might get 0x650, but the voltage value did not change.
Thanks to input from Rich, I may have a board with a multi-phase buck converter and would like to experiment some more. See https://bitcointalksearch.org/topic/m.12222540 for details.
Kano, or anyone else, do you know the correct format to input for voltage? Does the 0x0650 listing indicate 0.065 or 0.65 V, or some incremental offset from the default?
Kano,
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Both. Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Kano,
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
It works on my S3+.
I did the update, and although I do like the additional info in the Miner Status screen, I'm not sure that I am getting an improvement.
At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
I'm the only one who shows 'Paid' anywhere in bitcoin as far as I know At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
It's something I made up/added to miner.php a while back and then I've added to various ants.
It's the "Accepted" hash rate - thus why I call it "Paid"
It excludes "Rejected" and "Stale" hash rate so it will be lower than the avg hash rate.
Since pools only pay you based on your accepted shares, that's the number that is most useful to work out how your miner is performing.
To calculate it it's: "Difficulty Accepted" * (2^32) / "Elapsed"
On 1 Day 22 Hours running 225 at 0720 Voltage (Although not sure even though it says it is running at 0720 on the Status GUI that it accepted the change hardware side).
Im getting 450 gh Paid on the dot. HW errors at 0.24%
Temps are 43 and 44. Room is not ideal temp however, around 76F
Kano, is the best way to find out if the voltage was accepted is to use a Kill-A-Watt meter and compare to another unit. Is tuning to 0720 more effecient than Bitmain default?
I tuned it to 262.50 at 0720. Got Xs so went back.
Thanks!
Strato
Try bumping the voltage to 0725 with the 225 frequency.
With a S3+ I'm on 4 days 20 hrs with 454 gh/avg with .0003% HW errors at 225 freq and 0725 volt, but also staying between 37-39C with a 40C thrown in every now and then.
If you set 262.5, you should have started at 0750 voltage with all 4 power cables plugged in and then played with lowering/raising volts.
Kano,
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
Does this firmware work well with both the S3 and S3+? or does it work well with just one over the other?
Thanks..
I updated to Kano's latest and tried setting to 0625. In miner status it shows 0x0650 under voltage, so I assume it took. But it didn't change anything with respect to efficiency. See link below for details.
https://bitcointalksearch.org/topic/m.12211638
Yeah I'm guessing that some or all of the S3 don't actually support voltage change.https://bitcointalksearch.org/topic/m.12211638
(see discussion above/on the previous page)
It wont cause any problems, but it simply uses the driver interface to change the voltage as per "specifications"
If it's possible, it will work, if it's not possible it wont change anything.
I updated to Kano's latest and tried setting to 0625. In miner status it shows 0x0650 under voltage, so I assume it took. But it didn't change anything with respect to efficiency. See link below for details.
https://bitcointalksearch.org/topic/m.12211638
https://bitcointalksearch.org/topic/m.12211638
I did the update, and although I do like the additional info in the Miner Status screen, I'm not sure that I am getting an improvement.
At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
I'm the only one who shows 'Paid' anywhere in bitcoin as far as I know At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
It's something I made up/added to miner.php a while back and then I've added to various ants.
It's the "Accepted" hash rate - thus why I call it "Paid"
It excludes "Rejected" and "Stale" hash rate so it will be lower than the avg hash rate.
Since pools only pay you based on your accepted shares, that's the number that is most useful to work out how your miner is performing.
To calculate it it's: "Difficulty Accepted" * (2^32) / "Elapsed"
Thank you for the reply. yes i see now that the average hash rate is indeed between 500 and 550+. I would call this upgrade a must for every s3 owner.
If the voltage setting is having an effect, then as you turn the voltage down, leaving the Frequency unchanged, you will see a lower reading on the Kill-A-Watt meter. If you turn it down too far you will see an increase in hardware errors. If you go much too low you will see a lot of hardware errors or the unit will not hash at all.
If the voltage setting is working then for any frequency there is an optimum voltage setting, that point being where you just get a few HW errors, say .005% or less. The lower you set the frequency the lower you can set the voltage before the HW errors become unacceptable.
There are a lot of IF's in there because I have yet to see an S3 that lets you adjust the voltage from cgminer.
Rich
If the voltage setting is working then for any frequency there is an optimum voltage setting, that point being where you just get a few HW errors, say .005% or less. The lower you set the frequency the lower you can set the voltage before the HW errors become unacceptable.
There are a lot of IF's in there because I have yet to see an S3 that lets you adjust the voltage from cgminer.
Rich
I did the update, and although I do like the additional info in the Miner Status screen, I'm not sure that I am getting an improvement.
At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
I'm the only one who shows 'Paid' anywhere in bitcoin as far as I know At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
It's something I made up/added to miner.php a while back and then I've added to various ants.
It's the "Accepted" hash rate - thus why I call it "Paid"
It excludes "Rejected" and "Stale" hash rate so it will be lower than the avg hash rate.
Since pools only pay you based on your accepted shares, that's the number that is most useful to work out how your miner is performing.
To calculate it it's: "Difficulty Accepted" * (2^32) / "Elapsed"
On 1 Day 22 Hours running 225 at 0720 Voltage (Although not sure even though it says it is running at 0720 on the Status GUI that it accepted the change hardware side).
Im getting 450 gh Paid on the dot. HW errors at 0.24%
Temps are 43 and 44. Room is not ideal temp however, around 76F
Kano, is the best way to find out if the voltage was accepted is to use a Kill-A-Watt meter and compare to another unit. Is tuning to 0720 more effecient than Bitmain default?
I tuned it to 262.50 at 0720. Got Xs so went back.
Thanks!
Strato
I did the update, and although I do like the additional info in the Miner Status screen, I'm not sure that I am getting an improvement.
At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
I'm the only one who shows 'Paid' anywhere in bitcoin as far as I know At stock frequency (225 on the s3+) I still get standard 440 ish hash rate. At 250, I get 480 - 490. I am on F2Pool, and these numbers are from the GH/s paid column of stats.
Running at 250, I get a temp of 40 (max). Perhaps I should go for a higher frequency and take it up to about 50 degrees. Thoughts?
It's something I made up/added to miner.php a while back and then I've added to various ants.
It's the "Accepted" hash rate - thus why I call it "Paid"
It excludes "Rejected" and "Stale" hash rate so it will be lower than the avg hash rate.
Since pools only pay you based on your accepted shares, that's the number that is most useful to work out how your miner is performing.
To calculate it it's: "Difficulty Accepted" * (2^32) / "Elapsed"
That's subjective depending on environment. It wouldn't do you any good. You'll need to perform tests in your mining setup to see just how far you can go. Just give it a bump and see what you see. I wouldn't go over 250 though, unless you don't mind possibly damaging your miner and the replacement cost. For some it's worth the risk. For me it isn't
Jump to: