...after I put small heatsinks on the DCDCs (I had them lying around) and some overclocking, obviously.
Can you post a pic of your heatsink mod?
Topic: ANTMINER S3+ Discussion and Support Thread - page 404. (Read 710164 times)
...after I put small heatsinks on the DCDCs (I had them lying around) and some overclocking, obviously.
Can you post a pic of your heatsink mod?
Well, the only thing broken is that the webinterface isn´t available anymore.
It runs at around 505GH average after I put small heatsinks on the DCDCs (I had them lying around) and some overclocking, obviously.
Erm how do I reflash the firmware from SSH....
It runs at around 505GH average after I put small heatsinks on the DCDCs (I had them lying around) and some overclocking, obviously.
Erm how do I reflash the firmware from SSH....
Has anyone got the download address and instructions for a firmware reflash?
Mine shows this error when I want to access the webinterface:
/usr/lib/lua/luci/dispatcher.lua:582: bad argument #1 to ´pairs´ (table expected, got nil)
[C]: in function ´pairs´
/usr/lib/lua/luci/dispatcher.lua:5882: in function `createtree`
It runs stable over 500GH, but I would like to access the webinterface again
Mine shows this error when I want to access the webinterface:
/usr/lib/lua/luci/dispatcher.lua:582: bad argument #1 to ´pairs´ (table expected, got nil)
[C]: in function ´pairs´
/usr/lib/lua/luci/dispatcher.lua:5882: in function `createtree`
It runs stable over 500GH, but I would like to access the webinterface again
I don't know... If it runs stable at over 500GH, I would leave it alone.
However, if you insist:
https://bitmaintech.com/files/download/antMiner_S320140711.bin
Knock yourself out. If something goes wrong, you have been warned!
Has anyone got the download address and instructions for a firmware reflash?
Mine shows this error when I want to access the webinterface:
It runs stable over 500GH, but I would like to access the webinterface again
Mine shows this error when I want to access the webinterface:
Code:
/usr/lib/lua/luci/dispatcher.lua:582: bad argument #1 to ´pairs´ (table expected, got nil)
[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
[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
It runs stable over 500GH, but I would like to access the webinterface again
Bitmain starting to refund the btc for the hash rate difference 
btw, is there any of you received the coupons???
btw, is there any of you received the coupons???
Quick Question.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Bitmain will tell you to open up the case and reseat the plugs from control board to hashing board. 99% of the time that will fix your problem.
Opened the case up and reseated all connectors. No visible damage. One side is still cold to the touch.
You could swap the ports on the control unit to determine if it is the controller or the blade.
along the same lines if you have 2 s-3's and one works fine you can pull the good controller and swap it with the 'bad' controller
Quick Question.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Bitmain will tell you to open up the case and reseat the plugs from control board to hashing board. 99% of the time that will fix your problem.
Opened the case up and reseated all connectors. No visible damage. One side is still cold to the touch.
You could swap the ports on the control unit to determine if it is the controller or the blade.
Quick Question.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
http://i819.photobucket.com/albums/zz114/oneilljf/s3_bad_blade_zps6ef30a19.jpg
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
http://i819.photobucket.com/albums/zz114/oneilljf/s3_bad_blade_zps6ef30a19.jpg
Bitmain will tell you to open up the case and reseat the plugs from control board to hashing board. 99% of the time that will fix your problem.
Opened the case up and reseated all connectors. No visible damage. One side is still cold to the touch.
Re firmware flashing: it gives the checksum before flashing, but what I supposed to compare it to?
also, "image size 7.5mb (8.1 mb available)"-what is this supposed to mean?
The firmware hash should have a corresponding hash on their site. The two should match ensuring integrity. The 8.1mb available is the space available on the system disk. I ran a 'df -h' on the files system and this is what it showed 29M available in /tmp. also, "image size 7.5mb (8.1 mb available)"-what is this supposed to mean?
I've also been trying to track down how to turn off the system bell (beep) and haven't found anything. It's loud and annoying. I'll let you know when I find out how to disable it completely through software.
thanks, but why size discrepancy-when I download, it shows as a 8.1 mb file, but once I upload to s3 , then it says that it is 7.5mb.
besides, i don't see the checksum posted anywhere on their site.
Re firmware flashing: it gives the checksum before flashing, but what I supposed to compare it to?
also, "image size 7.5mb (8.1 mb available)"-what is this supposed to mean?
The firmware hash should have a corresponding hash on their site. The two should match ensuring integrity. The 8.1mb available is the space available on the system disk. I ran a 'df -h' on the files system and this is what it showed 29M available in /tmp. also, "image size 7.5mb (8.1 mb available)"-what is this supposed to mean?
I've also been trying to track down how to turn off the system bell (beep) and haven't found anything. It's loud and annoying. I'll let you know when I find out how to disable it completely through software.
Re firmware flashing: it gives the checksum before flashing, but what I supposed to compare it to?
also, "image size 7.5mb (8.1 mb available)"-what is this supposed to mean?
also, "image size 7.5mb (8.1 mb available)"-what is this supposed to mean?
Quick Question.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Bitmain will tell you to open up the case and reseat the plugs from control board to hashing board. 99% of the time that will fix your problem.
Quick Question.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
http://i819.photobucket.com/albums/zz114/oneilljf/s3_bad_blade_zps6ef30a19.jpg
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
http://i819.photobucket.com/albums/zz114/oneilljf/s3_bad_blade_zps6ef30a19.jpg
Got my late batch 2 miners today, All seems well except these "discarded".
On the S1 I have after 24 hours, 23000 accepted and 6000 discarded.
On the S3 I have after 6 hours, 6000 accepted and 75000 discarded.
Software is 3.10.12 on both, Why like this?
On the S1 I have after 24 hours, 23000 accepted and 6000 discarded.
On the S3 I have after 6 hours, 6000 accepted and 75000 discarded.
Software is 3.10.12 on both, Why like this?
I am seeing the same thing. I wonder if they just have the two values reversed? According to the pool I am getting share credit at the expected rate.... so I'm not sure what the high discard means if it's real?
Yea pool side were all good, I think the numbers are transposed or some goofy thing like that.
Hi All,
Bought 2 S3. Arrived today.
1. First one, turns on, immediately non-stop ringing. Never turns off.
2. Second one, turns on, no ringing, but the temperature of the first blade says 2C while the second is 44c.
They are both being tested with the SAME Corsair 1000W PSU. The ringing is the worst part, but the temperature thing also concerns me.
Anyone know about this? I am not talking about the intermittent beep that happens, it happens on the second unit, but the first unit is constant ringing, non-stop.
Thoughts?
real1st
Got my late batch 2 miners today, All seems well except these "discarded".
On the S1 I have after 24 hours, 23000 accepted and 6000 discarded.
On the S3 I have after 6 hours, 6000 accepted and 75000 discarded.
Software is 3.10.12 on both, Why like this?
On the S1 I have after 24 hours, 23000 accepted and 6000 discarded.
On the S3 I have after 6 hours, 6000 accepted and 75000 discarded.
Software is 3.10.12 on both, Why like this?
I am seeing the same thing. I wonder if they just have the two values reversed? According to the pool I am getting share credit at the expected rate.... so I'm not sure what the high discard means if it's real?
Here is a my take on the DC-DC regulator issue:
This part can cool off in 3 ways: conduction, convection and radiation. A back-of-the-envelope calculation shows that you can drop radiative cooling.
I think the new S3 design has a (slight?) flaw in the cooling of the DC-DC regulator part. With the cover on, the cooling of this part depends on airflow.
The problem is that the closer to the exhaust, the warmer the air is flowing over the regulator. So from back to front the regulator chips are running hotter. You could could use heat sinks to try to bandaid the problem but you probably could only place them on the last few chips because you don't want to block the air flow. So the issue is are the back chips running too hot?
I think the ultimate solution is removing the top cover, but what does that do to everything else and the warranty?
This part can cool off in 3 ways: conduction, convection and radiation. A back-of-the-envelope calculation shows that you can drop radiative cooling.
I think the new S3 design has a (slight?) flaw in the cooling of the DC-DC regulator part. With the cover on, the cooling of this part depends on airflow.
The problem is that the closer to the exhaust, the warmer the air is flowing over the regulator. So from back to front the regulator chips are running hotter. You could could use heat sinks to try to bandaid the problem but you probably could only place them on the last few chips because you don't want to block the air flow. So the issue is are the back chips running too hot?
I think the ultimate solution is removing the top cover, but what does that do to everything else and the warranty?
Can you post a photo of the chips in question. Removing the case would not be a good idea unless you had airflow directly hitting the chips. The tunnel helps move the heat across the chips.
Got my late batch 2 miners today, All seems well except these "discarded".
On the S1 I have after 24 hours, 23000 accepted and 6000 discarded.
On the S3 I have after 6 hours, 6000 accepted and 75000 discarded.
Software is 3.10.12 on both, Why like this?
On the S1 I have after 24 hours, 23000 accepted and 6000 discarded.
On the S3 I have after 6 hours, 6000 accepted and 75000 discarded.
Software is 3.10.12 on both, Why like this?
Here is a my take on the DC-DC regulator issue:
This part can cool off in 3 ways: conduction, convection and radiation. A back-of-the-envelope calculation shows that you can drop radiative cooling.
I think the new S3 design has a (slight?) flaw in the cooling of the DC-DC regulator part. With the cover on, the cooling of this part depends on airflow.
The problem is that the closer to the exhaust, the warmer the air is flowing over the regulator. So from back to front the regulator chips are running hotter. You could could use heat sinks to try to bandaid the problem but you probably could only place them on the last few chips because you don't want to block the air flow. So the issue is are the back chips running too hot?
I think the ultimate solution is removing the top cover, but what does that do to everything else and the warranty?
This part can cool off in 3 ways: conduction, convection and radiation. A back-of-the-envelope calculation shows that you can drop radiative cooling.
I think the new S3 design has a (slight?) flaw in the cooling of the DC-DC regulator part. With the cover on, the cooling of this part depends on airflow.
The problem is that the closer to the exhaust, the warmer the air is flowing over the regulator. So from back to front the regulator chips are running hotter. You could could use heat sinks to try to bandaid the problem but you probably could only place them on the last few chips because you don't want to block the air flow. So the issue is are the back chips running too hot?
I think the ultimate solution is removing the top cover, but what does that do to everything else and the warranty?
wow, interesting, this is exactly what I hit in 100d on S1 (on average). they must have some formula to predict this.
14% in 100 days is 60% a year. Don't tell me you hit this on the stock market on anything else.
I would say BitMain is well aware of our margins, I am tracking everything in a spreadsheet (IRS) for S1, S2, S3.. they all seem to be on that mark, S1's early appearance really gave it the edge. My first S1 I paid 1.9BTC ($1554.96) ran it for 180 days and then sold it on ebay, net was $634.61 / $1554.96 = 41% Net profit. My first S2 is @ day 129 and is currently $1012.95 in the black, other 2- S2's are 64 days in and @ 49% ROI. SP10's are 63 days in and @ 37% ROI ;(
Just like the market you have to hedge your bets, keep your eye on the future offerings, and get IT while you can! Basically I have watched this grow from a $1500 hobby into a 30K small business. Bitmain is helping me keep that going by NOT raping every nickel of value out of their offerings.
THIS
Jump to: