Topic: Antminer D3 reports trouble reading PIC temperature's - page 4. (Read 10326 times)

I have the same thing after rebooting it takes about a day - but I found another unusal thing

Since tonight one of my antminers D3 has a lot of traffic (normal are under  200K now it is over 10M). You see it only if you have a look on the traffic monitor. All the rest was fine with mining so it is not easy to see this. I put now the new firmeware in.
Lets see what happend.

After three hours of monitoring everything looks good again with the new Firmeware. The traffic is again under 200 K.

Hi Guys,

Just a quick followup, I've had a chance to so some more testing with 5 D3's and did the following:
1) Tested with a single APW3++ PSU on a 230V mains source
2) Tested with a 3600 Watts single rail PSU (Lab testbench PSU, so not a converted server PSU or PC PSU)
3) Tested with a power conditioner (used in high end audio setups)
4) Flashed the latest available firmware from: https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201709131713-0M.tar.gz
5) Hard wire connection to a Cisco 24Port managed switch (tested on different ports with different cables)
6) Set the mining pool to Antpool
7) Inspected the hashbords of a single D3 for damaged solder points powerlanes etc, loose/missing heatsinks -> All looked fine.

Results:
- All of the D3's had the random error mode red led warning flash
- All of the D3's had the random (The red led is in sync with this message) "read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!" message in the kernel log's.
- All of the D3's had the occasional "all x'es" on 1 or 2 hashbords, and returning to normal after a "reboot"

This seems to be what most of the contributors to this thread experienced as well.
- So it seems that it's not related to the stability of the used power supply.
- Chances that each D3 (at least in the case of the posters in this thread, that have several D3's that exhibit the exact same behavior) has 1 or 2 malfunctioning hashbords seems unlikely,
and I assume that Bitmain would notice this with their Quality Assurance tests.

That kind of leaves me with:
- Software bugs
- Controller (board) bugs

What I still want to test:
- Is the behavior the same when disconnecting 1 or 2 hashboards.

I'm hoping that Bitmain is able to sort this out with a firmware update (if it's indeed a software problem), however... They might not be inclined to do so since the rapid increase in Dash difficulty might make this
an uninteresting investment.

try this troubleshooting tips what another forum member received from Bitmain support :

All of you who have problem with your D3 ...

What voltage you power supply connected ? 110/120V .. 220V .. 245V ?

Also what PSU's are you using . Bitmain ? Server psu w break out borad ? PC psu ?

Are You using power line Ethernet adapter to connect your miner to a network ?
A lot of the time, the electrical wiring in the house just isn’t ideal for powerline ethernet.

Are You using any kind of Surge protector with your power line adapters ?
Surge protectors can protect your computer, but they also scramble powerline ethernet signals. Plugging a powerline ethernet device into a power bar with surge protection will severely limit your potential speed, if not stop the device from working altogether.

I have 2 Antimner D3 at this moment ,so far no problem with them , mining only dash , not using prohashing, nicehash pool or something similar to mining different coins .

The D3 description on bitmain site says : "Power consumption: 1200W (at the wall, with Bitmain’s APW3 PSU, 93% efficiency, 25°C ambient temp)." In my experience my D3's pulling a little bit more power at the wall than 1200 watts from 245Volt with bitmain PSU

If you running your miners from 110/120 volt with Bitmain APW3++ , you might get in trouble as those psu's are rated 1200 watts if connected to a 110/125 volt outlet  , 1600 watts if connected to 220V

I have Antminer D3 12 machine same error "read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!" All

Im even mining on antpool

I'm having exactly the same issue, but mine causes  mostly HW errors, will try to leave it on just DASH instead of zpool which is constantly jumping in/out of different coins, as such, difficulty changes and causes this

EDIT: Even with Dash only it happens, but less because it's only 1 coin, this will probably be fixed in a firmware update , HOPEFULLY

An interesting one as well, do any of you guys have a blade constantly running hotter than the others, like 8degress?

Chain#   ASIC#   Frequency   MH/S(RT)   HW   Temp(PCB)   Temp(Chip)   ASIC status
1 60 487 5646.18 0 53 65 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2 60 487 5637.95 0 51 65 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
3 60 487 5718.85 0 58 73 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo

EDIT: And I only get HW Errors on the same blade , switched PSU, same...
Until my proper PSU arrives, i'm running a 3 PSU setup, one per blade, the PSU's were fine, as they were running on GPU rigs..., this is getting me frustrated.

Hi guys!

Thanks for all the replys really helpful!
Seems that my D3 has the exact same behavior.

Just for fun I tested the D3 with a lab grade PSU (extremely stable single rail ripple free source) and the
Behaviour was the same.
Also installed the latest firmware, made no difference.

Most important thing is that the D3 does work, can imagine that the overall performance could be better if the D3 was a bit more stable.
Bitmain might just have a golden firmware version that they use in their farms

I concur with @unknownbtc - my D3s are showing a lot of fluctuations in difficulty with one hash board going xxxxxxxxxxxxxx then returning to oooooooooooooooooo.   

Same is happening to me read my post
https://bitcointalksearch.org/topic/m.22053491

I have 14 machines they all do it i guess all D3 miners do this this is the only thing that would explain the changes on the mining difficulty if you watch it goes up and down all day long i guess because the miners are having this behavior

have you try to check the pool you are mining for? configuration because mine at first do the same and was that the pool info was bad and other solution i sell my power to nicehash but maybe check that and if you cant i can help you to try to config and see if you can start mining and i underclok mine to realative fix send a message maybe i can help you

Do you get the same cgminer error Message?

If the entire bord registers as defect, it almost looks like there is a defect in the on hash bord power supply? All power cables are inserted properly and the control cables have no damage?
If there is one defect chip the bord should continue to function.

Might be best if you contact Bitmain to ask if you can remove the defect hash bord and send it back for repair.

Have the feeling that quality control was not that great

Mine just loops and doesn't hash, doesnt show any defect chips or bords.
Still don't know what it could be in my case.

i have the same problem but for me after one or tw hours the d3 show xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx on the asics chips in one hashing board but withe the reebot starts works perfectly  agin for an onther peridod of time and my temp are 68-72 more less any help?

it will be right to contact to Bitmain Support. maybe they can help you.

The part that has me worried a bit is that the red error led flashes (once) then the kernel log shows that message and the fan goes up and then It does the same after a minute or so.

Don't know if it's software or hardware related

to be honest, i don't know real reason for that problem, if i can call that problem. but HW does not increase and it is good. i think it is not real problem for worry.

Hi alexiamni,

It still reads 0 for all three hash boards, think this is because cgminer has not started with actual mining?

what about the number of HW errors. is it increased?

Hi Mining experts,

Well after a while trading and playing a bit with some bots I thought it would be nice to have a Bitmain Antminer D3.
So I Ordered one (quite some time ago) and it arrived today.

First thing I did was to make sure the D3 actually worked so I:
1) Connected all power cables from the APW3++ to the D3 (hash boards and the controller board) its a very stable 230Volts 50Hz here
2) Connected the UTP cable to the network switch
3) Connected the power to the mains
4) Left ALL settings on default to see if the D3 actually worked

Logged in on the Web interface and the Miner status reported all was well:
All chains were there (1 2 3), ASIC# reported as 60 per chain, Frequency 487, MH/S all in the 5700.00 range, HW 0, Temp PCB in the 50 range, Temp Chip in the 60+ range, ASIC status all o (So i assume no reported defects here)

The User was stil Antminer_1 (didn't change it, wanted to see if the D3 works to begin with)

So this looked ok, then after a short while the D3's red light blinked once and the fan's speed increased after a short while to go down again.
When I checked the kernel log there was a line that was added @the same time the red light blinked:
local0.err cgminer[374]: read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!


I've no idea what this means, other than when the cgminer software is running it cant for some reason get all of the chips temps?
however the status window does report temps per hash board?

I'm not sure if its a config/controller/controller cable/hash board/Software(firmware)/other problem

Any insights would be greatly appreciated!
Thanks!
David