ANTMINER S3+ Discussion and Support Thread

[Tripjammer]

Have bought from Bitmain before and never seen a UPS message like this.
Am in the US, BTW.
The packages have left Anchorage probably headed for Louisville.

"07/25/2014   9:16 P.M.   A valid tax ID or deferment number is missing and is required for clearance. We are working to obtain this information. / The package is at the clearing agency awaiting final release."

WTF Over?

Anybody got a clue whose tax ID they want.
And what the heck is a "deferment number"?

Thanks in advance,

When ordering stuff from China, always try to use DHL if possible. DHL seems to always get their stuff through customs with no issues...unlike UPS..

[faetos]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

Thanks for this post ! Going to try this on one of my units and see how it works out.

This was default on the new firmware:

PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"

I tried it on one by adding the --scan-time 1 --expiry 1 flags, but didn't see any difference in discards or load. Maybe some of you will have better luck.

Did you change the Queue to 0?

that I did not do - misread what you wrote. YES!! Just changed it and am seeing really good numbers. Discards are negligible now - 20 accepts and 3 discards. Load dropped from high 2s to under 2. AWESOME!!!!! You rock!

[dlm1130]

**********************

[ZiG]

**********************

...

[iglasses]

**********************

?...

Sometimes we humans drink alcohol.
 

[ZiG]

**********************

?...

Sometimes we humans drink alcohol.
 

...and fall asleep on a keyboard...

Cheers...beer here...

ZiG

[Pjones]

When ordering stuff from China, always try to use DHL is possible. DHL seems to always get their stuff through customs with no issues...unlike UPS..

This may be true for where your shipment enters the US.  While I haven't had any major issues with DHL recently, I've had a few shipments held up due to minor paperwork issues.  FedEX, on the other hand, is almost always a problem.  I get the package, but it comes with a extra invoice for handling customs inspections, which doesn't happen with UPS or DHL.

Anyway, it all depends.

[Billbags]

Hey Duce, could we get an update on your firmware adjustments?

[Lowell904]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

Thanks for this post ! Going to try this on one of my units and see how it works out.

This was default on the new firmware:

PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"

I tried it on one by adding the --scan-time 1 --expiry 1 flags, but didn't see any difference in discards or load. Maybe some of you will have better luck.

Did you change the Queue to 0?

that I did not do - misread what you wrote. YES!! Just changed it and am seeing really good numbers. Discards are negligible now - 20 accepts and 3 discards. Load dropped from high 2s to under 2. AWESOME!!!!! You rock!

Since I've never SSH one of these, I don't want to risk bricking it.

If this fix turns out to be solid though, I hope Bitmain will include it in the next firmware release.

Or maybe I'll learn to SSH. On a side note. Does anyone know if you can get a better GHS/watt ratio by under-clocking the S1?

[faetos]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

Thanks for this post ! Going to try this on one of my units and see how it works out.

This was default on the new firmware:

PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"

I tried it on one by adding the --scan-time 1 --expiry 1 flags, but didn't see any difference in discards or load. Maybe some of you will have better luck.

Did you change the Queue to 0?

that I did not do - misread what you wrote. YES!! Just changed it and am seeing really good numbers. Discards are negligible now - 20 accepts and 3 discards. Load dropped from high 2s to under 2. AWESOME!!!!! You rock!

Since I've never SSH one of these, I don't want to risk bricking it.

If this fix turns out to be solid though, I hope Bitmain will include it in the next firmware release.

Or maybe I'll learn to SSH. On a side note. Does anyone know if you can get a better GHS/watt ratio by under-clocking the S1?

I'll tell you how to do it, but not going to go into every detail (how to SSH, sed, etc). Not responsible for you f'ing your stuff up.

1. SSH into the miner
2. cd /etc/init.d
3. cp cgminer cgminer.bak (in case you really muck it up, cgminer.bak will be your backup)
4. Enter this in the terminal:  sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' cgminer
5. press enter
6. go to the web interface of the miner - Status > Miner Configuration > Save & Apply  - this will restart cgminer with the new settings
7. go tip Duce for figuring this out for us

Duce, where's your tip jar? I owe you.

This is what you're changing:

Original --> PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"
   
New & Improved --> PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 0 --scan-time 1 --expiry 1"

//S1 undervolt guide - https://bitcointalk.org/index.php?topic=526060.msg5838713#msg5838713

[Duce]

Hey Duce, could we get an update on your firmware adjustments?

Setting the Queue to anything but 0 increases both the Load and Discarded values. After another run with the Queue back to 0, accepted values are about the same as stock. My other unit is performing just like this except it likes a lower clock, such as 212.5 as others have identified. Again if you are on P2P then this should be good for you but the Queue value may interact different with your pool. The unit here is connected to a regular pool. Here is the same unit as before with the last run I started.

[Duce]

I am happy to contribute.

I wonder if kano is going take a look at the code and see what he could do as he for the S1 units.

[9600]

Spoke with some engineers at a large pool and they suggested --expiry 15 --scan-time 1 --queue 1. I am going to try that now.

Both of my Ants are all over the place. Just took a nap and woke up to both of them sub 400 at stock speeds.

[kkurtmann]

I am happy with my S3's. As an owner of bfl little singe(now not profitable), cointerra, and spondoolies s10(both perform great but are super noisy), I must say that Bitmain S3 is by far The Best Power Efficiency of the lot. Also the quietest (5 S3's same loudness as my pc).

I get sustained 444Gh/s at pool averaged per machine stock settings.

[Omarko]

can someone share what is a single S3 on a decent PSU pulling from the wall in terms of power ?

cheers

[Duce]

can someone share what is a single S3 on a decent PSU pulling from the wall in terms of power ?

cheers

Corsair RM750, 354-377 depending on clock speeds is what I am getting @110VAC

[9600]

Spoke with some engineers at a large pool and they suggested --expiry 15 --scan-time 1 --queue 1. I am going to try that now.

Both of my Ants are all over the place. Just took a nap and woke up to both of them sub 400 at stock speeds.

I'm not so sure anymore. Faster S3 is starting to slow and the "slower" unit is catching up in accepted shares. Also worth noting is that the S3s never receieved ANY rejected shares when running stock options. I have no idea what to do. I can't get either unit to stabilize over 430 for more than two hours.



As you can see, temps are certainly not the issue.



Ant1 is running at 218, Ant2 at 250. (Ant2 runs at 470-490 for about 30-45 minutes)

It's looking like the extra invalids picked up by the scan, expiry and queue settings make any changes not worth it.

Also curious to know whether or not you guys are running 2x or 4x PCIe connections? I'm concerned that all of those DC/DC modules get warmer using the extra lines?
S1 DC/DC chips used to see small benefits (1GH+) from using heat-sinks...

[Xian01]

I'm not so sure anymore. Faster S3 is starting to slow and the "slower" unit is catching up in accepted shares. Also worth noting is that the S3s never receieved ANY rejected shares when running stock options. I have no idea what to do. I can't get either unit to stabilize over 430 for more than two hours.

 I'm going back to stock options. The tweaks were, seemingly, not making any significant difference after two hours of observation.

[Johnsinkler82]

Hey,

have anyone a coupon for me. That's would great.
Please send me a PM.   

ID Kidprodigy

[Omarko]

can someone share what is a single S3 on a decent PSU pulling from the wall in terms of power ?

cheers

Corsair RM750, 354-377 depending on clock speeds is what I am getting @110VAC

thank you.