Antminer D3 Blissz firmware (10/12 v1.12 update) - page 64.

Sidifotoskwa

newbie

Activity: 27

Merit: 0

Quote from: Gritch on November 30, 2017, 02:18:49 PM

got a D3 from bitmain and CHain #3 isn't showing. Should I wait for warranty reply from bitmain before flashing with Blissz firmware?

I had the same problem, you have to reboot

Rebooted and restored but same issue. I should try blissz firmware and see it shows up...

ruptan

sr. member

Activity: 491

Merit: 250

Quote from: blissz on November 30, 2017, 10:51:58 AM

v1.02 :: 30/11 :: recommended update

Download:
*removed link due to temperature reading problems with chain 0*

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down

know issues:
- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!

Thanks mate. I am still using your 11/21 and it is rocking for me. I have no intention to change it for now unless you change the algorithm. Great job by the way. You rock!

Gritch

newbie

Activity: 9

Merit: 0

Quote from: ?? on ??

got a D3 from bitmain and CHain #3 isn't showing. Should I wait for warranty reply from bitmain before flashing with Blissz firmware?

I had the same problem, you have to reboot

Sidifotoskwa

newbie

Activity: 27

Merit: 0

I set ASIC Voltage to 1 instead of lowest on CHain #2 and HW's are at 0 now.

piliff

newbie

Activity: 7

Merit: 0

Quote from: Mattithyahu on November 30, 2017, 01:37:49 PM

Can anyone answer these two questions?

How does the HW errors impact mining speed/hashrate etc?

How does the HW errors impact the lifespan of the hashboard/chain?

+1

In my opinion (and with some experience) HW errors do not affect the process. One of hashing boards in my D3 showed more than 300,000 errors per hour, but the hashrate was exactly the same as on other devices.

But I don't know about device lifetime. Maybe if it has so much errors, chain board will die soon. Maybe not. Huh

Mattithyahu

copper member

Activity: 10

Merit: 0

Too small image, tiny resolution, mate....

Can anyone answer these two questions?

How does the HW errors impact mining speed/hashrate etc?

How does the HW errors impact the lifespan of the hashboard/chain?

SteganoS888

newbie

Activity: 3

Merit: 0

http://i.da.am/6938.jpg http://i.da.am/6940.jpg

funminer

full member

Activity: 218

Merit: 100

Quote from: piliff on November 30, 2017, 01:13:42 PM

Quote from: ?? on ??

HW: 31 on CHain#2
Please, how to reduce HW's?
Thank you

What for? Is your hashrate ok? If that, what problem with HW?

31 HW-Error´s is not much depend the time you have the miner runing.

most hw error´s come from not enough power, you have 2 Options
Lower frequency or higher Voltage on this chain.

piliff

newbie

Activity: 7

Merit: 0

Quote from: ?? on ??

HW: 31 on CHain#2
Please, how to reduce HW's?
Thank you

What for? Is your hashrate ok? If that, what problem with HW?

SteganoS888

newbie

Activity: 3

Merit: 0

I ask you to help with the solution of the problem:
http://i.da.am/6938.jpg
http://i.da.am/6940.jpg
[SPOILER][ 4054.090223] omap_i2c 4819c000.i2c: controller timed out
.................................
[ 5268.813681] omap_i2c 4819c000.i2c: controller timed out
[ 5269.821536] omap_i2c 4819c000.i2c: controller timed out
[ 5272.067710] omap_i2c 4819c000.i2c: controller timed out
[ 5273.073586] omap_i2c 4819c000.i2c: controller timed out
[ 5274.079488] omap_i2c 4819c000.i2c: controller timed out
[ 5275.087332] omap_i2c 4819c000.i2c: controller timed out
[ 5276.093248] omap_i2c 4819c000.i2c: controller timed out
[ 5277.099118] omap_i2c 4819c000.i2c: controller timed out
[ 5278.204859] omap_i2c 4819c000.i2c: controller timed out
Nov 30 17:39:13 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init chainid = 0
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create rx read thread for /dev/ttyO1 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: Start A New Asic Response.Chain Id:[0]
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create tx read thread for /dev/ttyO1 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init chainid = 1
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create rx read thread for /dev/ttyO2 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: Start A New Asic Response.Chain Id:[1]
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create tx read thread for /dev/ttyO2 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init chainid = 2
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create rx read thread for /dev/ttyO4 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: Start A New Asic Response.Chain Id:[2]
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create tx read thread for /dev/ttyO4 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: open device over
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:39:15 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:39:15 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:39:15 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:39:15 (none) local0.notice cgminer[2489]: every_chain_disable_PIC16F1704_dc_dc_new
Nov 30 17:39:26 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:39:26 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:39:35 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:39:44 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:39:56 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:39:56 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:40:05 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:06 (none) local0.notice cgminer[2489]: every_chain_enable_PIC16F1704_dc_dc_new
Nov 30 17:40:17 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:40:17 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:40:26 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:39 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:40:39 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:40:48 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:57 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:57 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:40:58 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:40:58 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:40:58 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:40:58 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:40:58 (none) local0.notice cgminer[2489]: recheck_asic_num DONE!
Nov 30 17:40:58 (none) local0.notice cgminer[2489]: every_chain_disable_PIC16F1704_dc_dc_new
Nov 30 17:41:09 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:41:09 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:41:18 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:41:31 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:41:31 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:41:40 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:41:52 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:41:52 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:42:01 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:42:02 (none) local0.notice cgminer[2489]: every_chain_enable_PIC16F1704_dc_dc_new
Nov 30 17:42:14 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:42:14 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:42:23 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:42:35 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:42:35 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:42:44 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:42:57 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:42:57 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:43:06 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:43:06 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:43:06 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:43:07 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:43:07 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:43:07 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:43:07 (none) local0.notice cgminer[2489]: recheck_asic_num DONE!
Nov 30 17:43:07 (none) local0.notice cgminer[2489]: every_chain_disable_PIC16F1704_dc_dc_new
Nov 30 17:43:19 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:43:19 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:43:28 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:43:40 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:43:40 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:43:49 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:44:01 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:44:01 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:44:11 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:44:12 (none) local0.notice cgminer[2489]: every_chain_enable_PIC16F1704_dc_dc_new
Nov 30 17:44:24 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:44:24 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:44:33 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:44:45 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:44:45 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:44:54 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:45:06 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:45:06 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:45:15 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:45:16 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:45:16 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:45:16 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:45:16 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:45:17 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:45:17 (none) local0.notice cgminer[2489]: recheck_asic_num DONE!
Nov 30 17:45:17 (none) local0.err cgminer[2489]: calculate_address_interval: temp_asic_number = -1, set addrInterval = '7'
Nov 30 17:45:17 (none) local0.notice cgminer[2489]: set_ticket_mask ticket_mask = 0x0000001d
Nov 30 17:45:17 (none) local0.notice cgminer[2489]: every_chain_get_PIC16F1704_freq_new
Nov 30 17:45:29 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:45:29 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:45:41 (none) local0.err cgminer[2489]: --- get_PIC16F1704_freq_new failed!
Nov 30 17:45:53 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:45:53 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:46:06 (none) local0.err cgminer[2489]: --- get_PIC16F1704_freq_new failed!
Nov 30 17:46:18 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:46:18 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:46:31 (none) local0.err cgminer[2489]: --- get_PIC16F1704_freq_new failed!
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: software_set_address: chain 0 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: Now Set

Chain Address

Nov 30 17:46:32 (none) local0.notice cgminer[2489]: software_set_address: chain 1 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: Now Set [1] Chain Address
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: software_set_address: chain 2 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: Now Set [2] Chain Address
Nov 30 17:46:33 (none) local0.notice cgminer[2489]: software_set_address: chain 3 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:33 (none) local0.notice cgminer[2489]: enable_read_temperature_from_asic: reg_value = 0x07007a61
Nov 30 17:46:33 (none) local0.notice cgminer[2489]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Nov 30 17:46:35 (none) local0.warn cgminer[2489]: set_temperature_offset_value
Nov 30 17:46:36 (none) local0.notice cgminer[2489]: set_temperature_offset_value: Chain0 Sensor0 temp offset : 00,
Nov 30 17:46:37 (none) local0.notice cgminer[2489]: set_temperature_offset_value: Chain1 Sensor0 temp offset : 00,
Nov 30 17:46:38 (none) local0.notice cgminer[2489]: set_temperature_offset_value: Chain2 Sensor0 temp offset : 00,
Nov 30 17:46:38 (none) local0.notice cgminer[2489]: frequency = '0'
Nov 30 17:46:43 (none) local0.err cgminer: Miner compile time: Tue Nov 29 12:03:56 CST 2017 type: Antminer D3 Blissz v1.01
Nov 30 17:46:43 (none) local0.warn cgminer: Started cgminer 4.10.0
Nov 30 17:46:43 (none) local0.warn cgminer[2712]: bitmain_DASH_init
Nov 30 17:46:43 (none) local0.warn cgminer[2712]: check_fan_speed OK
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detected at /sys/class/gpio/gpio51/value chain 0
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detected at /sys/class/gpio/gpio48/value chain 1
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detected at /sys/class/gpio/gpio47/value chain 2
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detect total chain num 3
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: i2c init ok
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: check_whether_need_update_pic_program
Nov 30 17:46:52 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:00 (none) local0.err cgminer[2712]: jump_from_loader_to_app_PIC16F1704_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:12 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new failed!
Nov 30 17:47:12 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0
Nov 30 17:47:21 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:30 (none) local0.err cgminer[2712]: jump_from_loader_to_app_PIC16F1704_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:41 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new failed!
Nov 30 17:47:41 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0
Nov 30 17:47:50 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:59 (none) local0.err cgminer[2712]: jump_from_loader_to_app_PIC16F1704_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:10 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new failed!
Nov 30 17:48:10 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0
Nov 30 17:48:10 (none) local0.notice cgminer[2712]: every_chain_reset_PIC16F1704_pic_new
Nov 30 17:48:19 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:29 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:38 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:38 (none) local0.notice cgminer[2712]: every_chain_jump_from_loader_to_app_PIC16F1704_new
Nov 30 17:48:43 (none) local0.warn cgminer[2712]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995[/SPOILER]

Renanxx1

newbie

Activity: 38

Merit: 0

What about new algo?

Mattithyahu

copper member

Activity: 10

Merit: 0

Quote from: blastar on November 30, 2017, 04:22:01 AM

Quote from: Mattithyahu on November 30, 2017, 02:53:42 AM

Quote from: dlezama on November 30, 2017, 02:40:07 AM

Tuning each card I discovered that changing the voltage on one of them also affects the number of HW errors I get on the other ones. I don't know if frequency has the same effect. This made it quite tricky to get the three cards tuned independently. Have others observed this? What would this happen?

Exactly what happends with me. Please guys, if you get good results, please share the settings you are running, and what batch of Antminer D3 you got. I will share mine as soon as I get decent results!

Any opinion on how much HW errors is acceptable? Does HW error affect mining performance? I dont see any speed changes with a lot of HW errors. Can you just ignore it if temp and everything is allright?

Every D3 is different, so there are no general settings that fit everybody. Even in a single D3, the boards can be very different, and this is the reason Blissz added the individual board tuning feature.

You should just follow these instructions (courtesy of Blissz):
Start with frequency of 400 and a "Low" voltage setting.
Then increase the frequency until you start seeing HW errors.
Now either reduce the frequency if you want to keep the lowest power consumption, or increase the voltage incrementally until the HW errors disappear altogether, or are not more than 12 per hour.
You should also keep an eye on chip temperatures of each board (or chain), and try to keep them under 80 deg. C. using the fan automatic profiles or fixing the fan speed at a certain percentage. I prefer personally to keep it on automatic.

As a rule of thumb (at least in my 19 GHs D3 batch from mid October), the highest frequency I can use without HW errors on "Low" voltage is 438, some boards cannot tolerate higher frequencies, and they start producing too many errors already at a frequency of 425 or even 419!

Thank you for useful information mate. I will try to tweak it as good as I can. How does the HW errors impact the mining?Do you or anyone here really know? Does it only affect the lifespan of the chain/board and not the performance? Maybe Blissz can answear, I never really had any HW errors before on my miners before I got the D3.

COINKING84

full member

Activity: 264

Merit: 100

Quote from: blissz on November 30, 2017, 11:56:43 AM

Quote from: caliel on November 30, 2017, 11:27:34 AM

Quote from: blissz on November 30, 2017, 10:51:58 AM

v1.02 :: 30/11 :: recommended update

Download:
https://mega.nz/#!zl4CBQDQ!fMrZZc9wA76vEXpA4XhelVDGDgidOEvk4pSQ45Wg_xs

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down

know issues:
- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!

FYI, multiple miners are showing a HUGE difference between temps of board 1 versus boards 2 and 3.. like 40 degrees difference. Looks like the logic you applied has put the number out of whack in the opposite direction..

You were ok on the previous firmware? I will pull back this update till I found out what's wrong.

bliss how do i get this? i want to put this on d3

ducdev

newbie

Activity: 41

Merit: 0

Any solution for overheatting D3 ? I tried many ways but no hope.

blissz

sr. member

Activity: 336

Merit: 258

Quote from: caliel on November 30, 2017, 11:27:34 AM

Quote from: blissz on November 30, 2017, 10:51:58 AM

v1.02 :: 30/11 :: recommended update

Download:
https://mega.nz/#!zl4CBQDQ!fMrZZc9wA76vEXpA4XhelVDGDgidOEvk4pSQ45Wg_xs

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down

know issues:
- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!

FYI, multiple miners are showing a HUGE difference between temps of board 1 versus boards 2 and 3.. like 40 degrees difference. Looks like the logic you applied has put the number out of whack in the opposite direction..

You were ok on the previous firmware? I will pull back this update till I found out what's wrong.

caliel

newbie

Activity: 13

Merit: 0

Quote from: blissz on November 30, 2017, 10:51:58 AM

v1.02 :: 30/11 :: recommended update

Download:
https://mega.nz/#!zl4CBQDQ!fMrZZc9wA76vEXpA4XhelVDGDgidOEvk4pSQ45Wg_xs

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down

know issues:
- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!

FYI, multiple miners are showing a HUGE difference between temps of board 1 versus boards 2 and 3.. like 40 degrees difference. Looks like the logic you applied has put the number out of whack in the opposite direction..

streetcredit

newbie

Activity: 1

Merit: 0

yea same the temp on chain 1 is 24 with voltage set to lowest and frequency 400

silvioraof

newbie

Activity: 16

Merit: 0

Hi good guys,
We are in the same boat..so let´s share our know... thanks for helping us Blissz
So, what pool do you use?
Does anyone tried to mine another coins in X11 algo?

blissz

sr. member

Activity: 336

Merit: 258

*removed version due to stability problems*

Monberg75

copper member

Activity: 109

Merit: 0

Why?

I don't have any problems, and are hashing 13-14GH at 650W, so I'm quite happy.

Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 64. (Read 125911 times)