Quote from: MnngSprvsr on August 09, 2021, 10:05:13 AM

i figured out that it is the controller board. I just do not know how to fix it

How did you figure out it was a control board issue? did you try a different control board? if you actually did, and it worked, it could be a different firmware, flash the same firmware on the "bad" control board and it should fix it.

Quote

The miner has mixed hashboard from diffrent batches,
Is there any other solution then the Antminer hash board code editor from ZeusBTC to synchronize the hash boards?

Mixed hash boards can still work if they have the same product id/pcb, look for something like this in the kernel log

Code:

2021-08-09 12:41:02 driver-btm-api.c:589:get_product_id: product_id[0] = 0
2021-08-09 12:41:02 driver-btm-api.c:589:get_product_id: product_id[1] = 0
2021-08-09 12:41:02 driver-btm-api.c:589:get_product_id: product_id[2] = 0
2021-08-09 12:41:02 driver-btm-api.c:533:_set_project_type: project:0
2021-08-09 12:41:02 driver-btm-api.c:558:_set_project_type: Project type: Antminer S17 Pro
2021-08-09 12:41:02 driver-btm-api.c:569:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2021-08-09 12:41:02 driver-btm-api.c:570:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2021-08-09 12:41:02 driver-btm-api.c:569:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2021-08-09 12:41:02 driver-btm-api.c:570:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2021-08-09 12:41:02 driver-btm-api.c:569:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2021-08-09 12:41:02 driver-btm-api.c:570:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103

Another way to confirm if this is actually caused by mixing hash boards, run them 1 by 1, if they all work individually but not when mixed then you make sense, if they don't, then you have bigger problems to worry about.