Braiins OS & Braiins OS+ custom ASIC firmware: optimize performance & efficiency

[Artemis3]

Hi, i think i solved the problem.
i must be put the "Use custom DNS servers"
now working......

but IPv4 broadcast must be fill or not? i'm not fill..... i don't know what write.....

Leave it alone if its working. broadcast address can be deduced automatically most of the time (its the top ip within a segment).

Try using multiple pools in case one fails. Most pools have multiple url addresses for different locations.

[ne4d]

How can i configure fee, using braiins firmware?

[BitMaxz]

No, you can't configure the dev fee and I think they don't have a dev fee unless if you have programming skill to modify the firmware.

If you are planning to modify it check this open-source from here https://github.com/braiins/braiins-os

[balla69]

someone suggest good pool for braiins? ( but i see all working well )

1-slushpool.com
2-depool.ckpool
3-zpool.ca
4-multipool.us

Thanks Artemis3 

[Lunga Chung]

And what do you mean by that? Web version can be installed easily using the web ui update firmware button. This only works with factory firmware from 2018 or earlier, because manufacturer decided to lock the miners in 2019, and requires one of the different methods for unlocking first.

Mass deployment can be done by using a python script. For automated post configuration (stage3) you need to use the earlier version from may because of bug.

Well you said it your self, not really user friendly. Also bear in mind if you wish to revert back to original firmware (without backup from SD card) and only have windows its not a very intuitive task.

[Artemis3]

someone suggest good pool for braiins? ( but i see all working well )

1-slushpool.com
2-depool.ckpool
3-zpool.ca
4-multipool.us

Thanks Artemis3 

zpool.ca is like nicehash, it needs the #xnsub parameter for decent bitrate...

You would use it like this:

stratum+tcp://sha256.mine.zpool.ca:3333#xnsub
stratum+tcp://sha256.na.mine.zpool.ca:3333#xnsub
stratum+tcp://sha256.eu.mine.zpool.ca:3333#xnsub

User is your bitcoin address, password is: c=BTC

Don't use this option with normal pools, its only useful for coin changing pools.

[balla69]

what limit references should be used for overclock downvolt?
i don't understand why in my test braiins result worse than bitmain......

i've tested an s9i 13,5 on bitmain selected default hashrate with low voltage and result Gh/s 13560  W 1153 without error stable.

but with braiins Gh/s 13470 W 1170 with 1 error .... with 625 mhz and undervolt to 8.75.

[Artemis3]

what limit references should be used for overclock downvolt?
i don't understand why in my test braiins result worse than bitmain......

i've tested an s9i 13,5 on bitmain selected default hashrate with low voltage and result Gh/s 13560  W 1153 without error stable.

but with braiins Gh/s 13470 W 1170 with 1 error .... with 625 mhz and undervolt to 8.75.

You can take a look at the logs from bitmain's if you are curious, as it sometimes shows the voltage and speed and try to match. But don't be too reliant on it, discover your best settings by yourself.

Do not pay much attention to errors (unless there are way too many, but wait like an hour first), just at the actual and ideal hashrates, they should match as close as possible. I never used the second decimal, just things like 8.7, 8.6, 8.5... And speeds like 650, 625, 600, etc.

So you are going to do this on each hashboard. Pick a desired speed and start lowering the voltage, until you see the aforementioned values differ too much, then go back a notch in that voltage (OR) lower the speed and start again. Various people here managed to do about 80w per TH, things like 8v 500mhz or so so about 10 TH @ 810W.

Every single hashboard behaves different, you can find the absolute best your hashboard can do with bOS.

It might be useful to do tests against reliable pools such as ckpool which shows your miner stats without registering. The best efficiency is not necessarily close to "stock" speeds (and usually aren't).

[balla69]

yes, I think I have waited too little after each reboot ...... and given too much importance to errors.
I was wondering why with the default values, instead of about 625-6 Mhz on all 3 with bitmain, it starts with values like 631-658-675, I thought that maybe the firmware increases the frequencies of the best cards .... but it is strange ..... because the order is always similar (the first the worst and the last the best, strange not?).
ckpool results should coincide with the actual hashrate no? maybe after 1 hour of mining ...

Questions:
the default configuration of braiins set the frequency different for every card, Is this difference good to maintain to optimize mining?

[percy_tc]

With Braiins OS, is there 100% fan speed upon start?

Is itpossible to downCLOCK miner, to be able to use it in home envirmonet (noise issues)?

Thanks

[Artemis3]

With Braiins OS, is there 100% fan speed upon start?

Is itpossible to downCLOCK miner, to be able to use it in home envirmonet (noise issues)?

Thanks

Yes, when you turn it on because the firmware isn't controlling anything yet. After it boots it can slow down the speeds. If you downclock the hashboards it will naturally slowdown the fans. You can also force it but you have to be very careful to not overheat the unit.

Another trick is reduce the number of hashboards, 2 or 1 need less air than 3.

[Shad0wSmurf]

With Braiins OS, is there 100% fan speed upon start?

Is itpossible to downCLOCK miner, to be able to use it in home envirmonet (noise issues)?

Thanks

8.3volts, 450 mhz, auto fan. start up is abi***, but it levels out

[Artemis3]

Well Philipma here did 7.8volts at 475 mhz, so i think you should be able to do better, either increase speed while keeping that voltage, or lower that voltage by keeping that speed until the hashrate values (ideal / actual) differ too much.

[Behnam fahimi]

i added ((  "bitmain-no-sensor-scan" : true , )) to  cgminer.conf  but temp sensor still has error .
i want the system to ignore temperature error of specific Chain .
please help

this is error log :
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 driver-btm-api.c:189:set_miner_status: ERROR_TEMP_LOST_1ST
2019-08-28 09:03:44 driver-btm-api.c:143:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!

[papampi]

i added ((  "bitmain-no-sensor-scan" : true , )) to  cgminer.conf  but temp sensor still has error .
i want the system to ignore temperature error of specific Chain .
please help

this is error log :
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 driver-btm-api.c:189:set_miner_status: ERROR_TEMP_LOST_1ST
2019-08-28 09:03:44 driver-btm-api.c:143:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!

if it's the last config no "," after it
And it should be --no-sensor-scan not what you used as below

Code:

"--no-sensor-scan":true

[BitMaxz]

Replace it with this code below:

Code:

"no-sensor-scan" : true

Just remove the Bitmain from your code under cgminer.conf

Another sample below add this.

Code:

"no-sensor-scan" : true
"fan-mode" : "speed"
"fan-speed" : "95"

Let me know if it works or not.

[minefarmbuy]

What are some high efficiency settings for the s9 people are using? Hearing of 10th about 600W is possible.

[Behnam fahimi]

hello all dears,
I did every thing you said but did not work !!

here is the code i used :

Code:

cgminer.conf
***************************
"api-listen" : true,
"api-network" : true,
"api-groups" : "A:stats:pools:devs:summary:version",
"api-allow" : "A:0/0,W:*",
"--no-sensor-scan": true,
"bitmain-use-vil" : true,
"bitmain-work-mode" : "0",
"bitmain-freq" : "O",
"bitmain-voltage" : "1900"
*************************************

2019-08-31 06:41:17 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.167373
2019-08-31 06:41:18 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.136758
2019-08-31 06:41:20 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.228603
2019-08-31 06:41:20 power_api.c:50:_get_avg_voltage: average_voltage = 21.177578
2019-08-31 06:41:20 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.18, check voltage passed.
2019-08-31 06:41:20 uart.c:71:set_baud: set fpga_baud to 115200
2019-08-31 06:41:20 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2019-08-31 06:41:20 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2019-08-31 06:41:20 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2019-08-31 06:41:33 driver-btm-api.c:1111:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2019-08-31 06:41:45 driver-btm-api.c:1111:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2019-08-31 06:41:56 driver-btm-api.c:1111:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2019-08-31 06:42:01 driver-btm-api.c:333:set_order_clock: chain[0]: set order clock, stragegy 3
2019-08-31 06:42:02 driver-btm-api.c:333:set_order_clock: chain[1]: set order clock, stragegy 3
2019-08-31 06:42:02 driver-btm-api.c:333:set_order_clock: chain[2]: set order clock, stragegy 3
2019-08-31 06:42:02 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0x34
2019-08-31 06:42:02 voltage[0] = 1700
2019-08-31 06:42:02 voltage[1] = 1700
2019-08-31 06:42:02 voltage[2] = 1700
2019-08-31 06:42:02 power_api.c:214:set_working_voltage_raw: working_voltage_raw = 1700
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 driver-btm-api.c:191:set_miner_status: ERROR_TEMP_LOST_1ST
2019-08-31 06:42:03 driver-btm-api.c:145:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!
2019-08-31 06:42:03 thread.c:698:cancel_read_nonce_reg_thread: cancel thread
2019-08-31 06:42:03 driver-btm-api.c:118:killall_hashboard: ****power off hashboard****
2019-08-31 06:42:08

 Assert fail!! driver-btm-api.c:150: reboot

[philipma1957]

What are some high efficiency settings for the s9 people are using? Hearing of 10th about 600W is possible.

I did 10025gh and 815 - 825 watts

Not sure anyone can do 600 watts.

[BitMaxz]

Code:

"--no-sensor-scan": true,

As I said above this code will not work you need to replace it with this below

Code:

"no-sensor-scan" : true

This is already been discussed here check this post: https://bitcointalk.org/index.php?topic=5036844.380