Antminer D3 reports trouble reading PIC temperature's

[EpicMining26]

Has the recent update for the D3 solved the " trouble reading PIC temperature's" error when the pool dies or it loses connection?

[1714863373]

1714863373

[1714863373]

1714863373

[1714863373]

1714863373

[1714863373]

1714863373

[Maicol792]

Hi Guys,

There seems to be a new firmware for the D3
With the description:
1. fix the issue: some miner's chip status is 'x' after running for several hours or days.

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201711022227-0M.tar.gz

I'll Test it when I can.

we can confirm that this is now running well so far.

Do try it out.

i have tested new firmare but i have some hw error on my september bach ...

Code:

Nov 10 18:40:18 (none) local0.warn cgminer[4929]: Pool 0 communication resumed, submitting work
Nov 10 18:40:18 (none) local0.err cgminer[4929]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!
Nov 10 18:40:40 (none) local0.warn cgminer[4929]: Lost 2 shares due to no stratum share response from pool 0

[Bibi187]

Hi Guys,

There seems to be a new firmware for the D3
With the description:
1. fix the issue: some miner's chip status is 'x' after running for several hours or days.

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201711022227-0M.tar.gz

I'll Test it when I can.

we can confirm that this is now running well so far.

Do try it out.

i have tested new firmare but i have some hw error on my september bach ...

Code:

Nov 10 18:40:18 (none) local0.warn cgminer[4929]: Pool 0 communication resumed, submitting work
Nov 10 18:40:18 (none) local0.err cgminer[4929]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!
Nov 10 18:40:40 (none) local0.warn cgminer[4929]: Lost 2 shares due to no stratum share response from pool 0

This error come from your pool, when D3 cant reach pool and get work.

Cgminer seems to have trouble to check temp, since i mining on mining dutch pool no more error at all.

[DCShmooC1]

 Same problem, same issue. The last time, All ASICS went out. Same responses from Bitmain. Flashed the firmware twice. Worked for about 3 days fine. Still thinking, probably right, a bug or controller board. Maybe the firmware update didn't fix all. Maybe I do have a bad Hash or controller board. It's weird. Interested in hearing from others who've flashed the firmware but still experience.

[CodeSingularity]

Hi Guys,

For me same thing...

However there seems to be a new firmware?
https://s3.cn-north-1.amazonaws.com.cn/shop-file-server/firmwares/Antminer%20D3/Firmware/00720170915192904493x4FcBXYX06A9/Antminer-D3-201711201715-0M.tar.gz

New: Antminer-D3-201711201715-0M.tar.gz vs Old: Antminer-D3-201711022227-0M.tar.gz

Have not tried it yet.

[Lumining]

Hi Guys,

There seems to be a new firmware for the D3
With the description:
1. fix the issue: some miner's chip status is 'x' after running for several hours or days.

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201711022227-0M.tar.gz

I'll Test it when I can.

we can confirm that this is now running well so far.

Do try it out.

i have tested new firmare but i have some hw error on my september bach ...

Code:

Nov 10 18:40:18 (none) local0.warn cgminer[4929]: Pool 0 communication resumed, submitting work
Nov 10 18:40:18 (none) local0.err cgminer[4929]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!
Nov 10 18:40:40 (none) local0.warn cgminer[4929]: Lost 2 shares due to no stratum share response from pool 0

This error come from your pool, when D3 cant reach pool and get work.

Cgminer seems to have trouble to check temp, since i mining on mining dutch pool no more error at all.

Are you also receiving less hardware errors when mining on dutchpool?
Do you have a normal duct tube connected from outside to the miner or do you have an external ventilator to assist the airflow?

[DCShmooC1]

New Firmware released Nov 20. Specifically to fix this issue. I'll flash and test over the holidays & report whether any success.

[Lumining]

New Firmware released Nov 20. Specifically to fix this issue. I'll flash and test over the holidays & report whether any success.

Where do you download the newest software for the D3?
Do you need to download it and insert it in "Flash new firmware image" or is there a command where the D3 downloads and installs the software by itself?

[CodeSingularity]

Hi,

Just use the web interface (system -> upgrade; bottom section select the tar.gz and upload the downloaded file the antminer flashes the firmware and reboots).

You can get it from here:
https://shop.bitmain.com/support.htm

(Menu On The left) Antminer D3 -> Firmware

Or direct link:
https://s3.cn-north-1.amazonaws.com.cn/shop-file-server/firmwares/Antminer%20D3/Firmware/00720170915192904493x4FcBXYX06A9/Antminer-D3-201711201715-0M.tar.gz

[bittawm]

Just thought id share my experience with 50 of these toasters.

a bunch of them had red flashing lights and do not hash (7 of the 50)

it doesnt matter how much you restart the miner on the GUI, it does not matter if you upgrade firmware, the "socket refused" error is still present.

how to fix:

turn off miner at the wall, unplug the controller board 6pin, replug in controller board

turn on and problem is fixed

[chase.pxelplus]

After upgrading to the latest firmware which is https://s3.cn-north-1.amazonaws.com.cn/shop-file-server/firmwares/Antminer%20D3/Firmware/00720170915192904493x4FcBXYX06A9/Antminer-D3-201711201715-0M.tar.gz I still get read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!

Anything I can do to fix this?

[Bibi187]

Hi Guys,

There seems to be a new firmware for the D3
With the description:
1. fix the issue: some miner's chip status is 'x' after running for several hours or days.

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201711022227-0M.tar.gz

I'll Test it when I can.

we can confirm that this is now running well so far.

Do try it out.

i have tested new firmare but i have some hw error on my september bach ...

Code:

Nov 10 18:40:18 (none) local0.warn cgminer[4929]: Pool 0 communication resumed, submitting work
Nov 10 18:40:18 (none) local0.err cgminer[4929]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!
Nov 10 18:40:40 (none) local0.warn cgminer[4929]: Lost 2 shares due to no stratum share response from pool 0

This error come from your pool, when D3 cant reach pool and get work.

Cgminer seems to have trouble to check temp, since i mining on mining dutch pool no more error at all.

Are you also receiving less hardware errors when mining on dutchpool?
Do you have a normal duct tube connected from outside to the miner or do you have an external ventilator to assist the airflow?

I have cool fan on D3, with soft tube on back to extract hot air outside.

Since i do firmware update i have less hw error (Not 20 nov. version for moment)

I dont know if is linked to dutch mining.

[Lumining]

Hi Guys,

There seems to be a new firmware for the D3
With the description:
1. fix the issue: some miner's chip status is 'x' after running for several hours or days.

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201711022227-0M.tar.gz

I'll Test it when I can.

we can confirm that this is now running well so far.

Do try it out.

i have tested new firmare but i have some hw error on my september bach ...

Code:

Nov 10 18:40:18 (none) local0.warn cgminer[4929]: Pool 0 communication resumed, submitting work
Nov 10 18:40:18 (none) local0.err cgminer[4929]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!
Nov 10 18:40:40 (none) local0.warn cgminer[4929]: Lost 2 shares due to no stratum share response from pool 0

This error come from your pool, when D3 cant reach pool and get work.

Cgminer seems to have trouble to check temp, since i mining on mining dutch pool no more error at all.

Are you also receiving less hardware errors when mining on dutchpool?
Do you have a normal duct tube connected from outside to the miner or do you have an external ventilator to assist the airflow?

I have cool fan on D3, with soft tube on back to extract hot air outside.

Since i do firmware update i have less hw error (Not 20 nov. version for moment)

I dont know if is linked to dutch mining.

I wrote an mail to the Bitmain service.
The problem is the default frequency of the Antminer D3 with 19,3 Gh/s is already overclocked.
You need to change the frequency of your miner to 487 and then it will mine with 17 Gh/s but with 0 HW errors.

[kw1k]

Hi Guys,

There seems to be a new firmware for the D3
With the description:
1. fix the issue: some miner's chip status is 'x' after running for several hours or days.

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201711022227-0M.tar.gz

I'll Test it when I can.

we can confirm that this is now running well so far.

Do try it out.

i have tested new firmare but i have some hw error on my september bach ...

Code:

Nov 10 18:40:18 (none) local0.warn cgminer[4929]: Pool 0 communication resumed, submitting work
Nov 10 18:40:18 (none) local0.err cgminer[4929]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!
Nov 10 18:40:40 (none) local0.warn cgminer[4929]: Lost 2 shares due to no stratum share response from pool 0

This error come from your pool, when D3 cant reach pool and get work.

Cgminer seems to have trouble to check temp, since i mining on mining dutch pool no more error at all.

Are you also receiving less hardware errors when mining on dutchpool?
Do you have a normal duct tube connected from outside to the miner or do you have an external ventilator to assist the airflow?

I have cool fan on D3, with soft tube on back to extract hot air outside.

Since i do firmware update i have less hw error (Not 20 nov. version for moment)

I dont know if is linked to dutch mining.

I wrote an mail to the Bitmain service.
The problem is the default frequency of the Antminer D3 with 19,3 Gh/s is already overclocked.
You need to change the frequency of your miner to 487 and then it will mine with 17 Gh/s but with 0 HW errors.

I underclocked my D3 to 487, this did not fix the issue. However what I did do was reflash the newest firmware a second time onto my D3, I have had zero issues and no furthers errors since.



EDIT: After 12 hours of mining the read temp function has occurred once, but it is far less then before.



BTC 1MaidYHDxpCwNWLaPrEeWtVxXtWFndhdUS
LTC LdeYLW7HYDjwFLKXzwvT8zGR1DeWcqVsnf

[Lumining]

Did someone try out the different frequencies already and can report the different hashrates for each frequency? Mining with 0 hardware errors is good but the sacrifice of 2 GH/s is a lot, did someone find the perfect frequency alraedy?

[DCShmooC1]

New Firmware released Nov 20. Specifically to fix this issue. I'll flash and test over the holidays & report whether any success.

And...No. It lasted 4 1/2 days before it X'd out again. 5 a.m. woke to fan speed at max, all basics out. I keep updating the firmware and running the dials on each chain, just results in chains 1 & 2 with oddly no HW errors, (and fan at 6k), chain 3 runs very hot with a lot of errors. I would think chain 3, or controller board. Bitmain just says unless the ASIC's X out, can't send create a warranty claim, nor will they take the entire miner back for warranty diags. So I'll try the cable unplug/reset next. And maybe I'll ramp up the frequency and diagnose the boards for much longer than the requested "20 Minutes".

[Pumperdumper]

Hey guys,


Extremely useful thread - so just wanted to say a big thank you.


Just got out D3 last week - they shipped the machine first and then the PSU -_-


Hooked it up today in our server room, plenty of ventilation and cool (sub 75 in there)

Once we had the D3 going, very first thing I noticed was a 19mh rate, then after we switched out the pool settings to miningpoolhub / zpool / poolmining.org (someone mentioned pools might be an issue?) it was up and running until I noticed one of the ASIC's went all Vin Diesel Triple X on us.

After that - I attempted a reboot + manual reboot and then updated the firmware with a few reboots in between. Prior to getting to the reboot - the ASIC (second one) went from XXX to not even showing up or registering which makes me think it's basically kaput.

Also noticed that the frequency settings came set as "Default" and I read in another thread that they should come with a specific number and if you change that number that it will void the warranty.

Any suggestions on what to do next?

[DCShmooC1]

I Changed mine to 437 then 444m. Hasn't voided warranty in dealing with them. I had to. It was completely unusable at the "default frequency". They are not great on backing their product warranty, because on diagnosing, two boards had HW errors but oddly when all 3 run there are absolutely 0 HW errors, but it still goes all X in 3 - 4 days, and I have to reboot. I feel like they are dragging the warranty period out, by persistently telling me, "Unless the boards run seperately and X out, I can only return, and I can only return 1 hash board". Makes no sense, not a warranty.

My rant. But I think as long as the frequency is lowered, not raised, then it should not void any warranty. They made them completely inoperable at their default frequency.  I would open a repair ticket with them first though. Typical Bitmain.

[Pumperdumper]

I Changed mine to 437 then 444m. Hasn't voided warranty in dealing with them. I had to. It was completely unusable at the "default frequency". They are not great on backing their product warranty, because on diagnosing, two boards had HW errors but oddly when all 3 run there are absolutely 0 HW errors, but it still goes all X in 3 - 4 days, and I have to reboot. I feel like they are dragging the warranty period out, by persistently telling me, "Unless the boards run seperately and X out, I can only return, and I can only return 1 hash board". Makes no sense, not a warranty.

My rant. But I think as long as the frequency is lowered, not raised, then it should not void any warranty. They made them completely inoperable at their default frequency.  I would open a repair ticket with them first though. Typical Bitmain.

I have 4 tickets open and they haven't responded to a single one.

Lol

So should I assume that chain #2 is done for since it doesn't even show the X's and O's?

I've also noticed that the third pool doesn't register any pool? I've tried mining pool hub and nice hash and both come up as dead?

[DCShmooC1]

I Changed mine to 437 then 444m. Hasn't voided warranty in dealing with them. I had to. It was completely unusable at the "default frequency". They are not great on backing their product warranty, because on diagnosing, two boards had HW errors but oddly when all 3 run there are absolutely 0 HW errors, but it still goes all X in 3 - 4 days, and I have to reboot. I feel like they are dragging the warranty period out, by persistently telling me, "Unless the boards run seperately and X out, I can only return, and I can only return 1 hash board". Makes no sense, not a warranty.

My rant. But I think as long as the frequency is lowered, not raised, then it should not void any warranty. They made them completely inoperable at their default frequency.  I would open a repair ticket with them first though. Typical Bitmain.

I have 4 tickets open and they haven't responded to a single one.

Lol

So should I assume that chain #2 is done for since it doesn't even show the X's and O's?

I've also noticed that the third pool doesn't register any pool? I've tried mining pool hub and nice hash and both come up as dead?

4 Tickets and no response? Yikes. On mine they take 24-48 hours. I'm not in anyway remotely an authority or experienced enough on these diagnostics, but if chain 2 is not showing X or O, I would "guess" controller board?


So many issues with the D3's and I feel (have a hunch maybe?) that there are big-time firmware issues globally.

I'm curious to hear if others are experiencing, would love hear the issues and what they've done in diagnosing and troubleshooting this.

After 2 days running on a D3 with issues, Chain 1 just went entirely X'd. Before 4 days all chains X'd. And prior to that Chain 2 showed 3 ASICs X'd. This is puzzling and driving me bonkers. I feel like I need to diagnose each board for 2-4 days now each to see. Is that practical? What is strange to me are the temps and the fan (Chain 1 and 2 running solo/individually, the fan goes to 6k, 3 only at 4k).  Temp on chain 3 solo gets gets to 77c (Scary) and yet when all run at once the fan is at 4k (Temps run: C1: 69c, C2: 63c, and C3: 70-71c). Chain 3 solo show HW errors but all three running show absolutely 0 HW errors. It's very odd.

I'm lost. I'm thinking firmware? And maybe Bitmain is swamped with these issues. We, or at least the large majority of the mining community, have financed them to a monopoly and likely funded their new Sophon AI brand.   I think we all just need to persist on reporting these issues, and keep opening tickets. They need to back their products.