Pages:
Author

Topic: Braiins OS & Braiins OS+ custom ASIC firmware: optimize performance & efficiency - page 9. (Read 45390 times)

legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Well so far i have only seen that the UI lets you set min powerlimit to 1480W, default is 2100 and max 5000 (don't use that).
In the text file you can even try some values the UI won't let... Not sure of the usefulness of that, you'll have to stop/start bosminer and never go to Miner > Configuration again or the ui will nag you to death about an invalid value.

In manual mode (or non plus), the configuration settings let you type 50 mhz frequency (default 500, max 700) and 14.31843v as the lowest (default 19.6, max 21.36). I doubt the boards would even respond if you forcibly use that, but at what point would they "wake up"?

Someone with an S17 willing to do some science?

S17 winter space heater coming soon. Cheesy
newbie
Activity: 86
Merit: 0
I have yet to try an S17, in the S9 you can set it to 100. Realistically, it will give about 100w to each card, so while you can type 100 (or 200), its more like 300w is the actual minimal for the S9.

I'm surprised that the S17 has such high minimal, i will ask and report.

Heard anything yet?
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Why can´t we go below 1480 watt on the autotune setting? Is there a reason for that?

I have yet to try an S17, in the S9 you can set it to 100. Realistically, it will give about 100w to each card, so while you can type 100 (or 200), its more like 300w is the actual minimal for the S9.

I'm surprised that the S17 has such high minimal, i will ask and report.
hero member
Activity: 2534
Merit: 623
Ahh i was referring to the S9. Not sure on the S17.
newbie
Activity: 86
Merit: 0
We are talking about S17 Pro right? Forgot to mention it.
hero member
Activity: 2534
Merit: 623
Why can´t we go below 1480 watt on the autotune setting? Is there a reason for that?

You can. Currently got mine set to 475w
newbie
Activity: 86
Merit: 0
Why can´t we go below 1480 watt on the autotune setting? Is there a reason for that?
hero member
Activity: 2534
Merit: 623
Yes it will sense the change. If you don't want to install it to the miner's NAND, you would need individual microSD cards for each.

Thanks Artemis. I'll get another SD card.
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Yes it will sense the change. If you don't want to install it to the miner's NAND, you would need individual microSD cards for each.
hero member
Activity: 2534
Merit: 623
Is it possible to switch the SD card from an existing S9 to a new S9 and have it work? Would it run with a current working autotune profile or would it sense the change of miner and redo the autotune?

Or would it be best to just get another SD card and do a new image?
newbie
Activity: 86
Merit: 0
There are no jumpers in the S17. It boots from it if you insert an sd card.

Ok, thanks. Haven't open it to see if i find any jumpers. Now i know  Grin This looks smooth, gonna try tomorrow.
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
There are no jumpers in the S17. It boots from it if you insert an sd card.
newbie
Activity: 86
Merit: 0
Does this apply S17 Pro:

Quote
Install Braiins OS+ using SD card

        Download the SD card image from our website.

        Flash the downloaded image on an SD card (e.g. using Etcher). Note: Simple copy to SD card will not work. The SD card has to be flashed!

        Adjust the jumpers to boot from SD card (instead of NAND memory), as shown below.
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
The 20.09 release is live now. It adds support for the S17 and S17pro; There are also some minor bugfixes for the S9 family (supported models are still the S9, S9j and S9i only). In addition, those mining in Slushpool with Braiins OS+ will not pay any pool fees this month. That's right, its 0. The dev fee remains at 2%.



Here is a little something for those of you who wanted to make monitoring tools for bosminer:

Code:
############
BOSminer API
############


*****
Usage
*****

Basic subset of the upstream cgminer API as well as several
new commands are implemented.

To test API, you can use `nc` in the following way *(replace the *IP_ADDRESS* placeholder with your miner's IP address)*:
**Single command**


  echo '{"command":"pools"}' | nc IP_ADDRESS 4028

In case you want to format JSON string, you can use `jq`:


  echo '{"command":"pools"}' | nc IP_ADDRESS 4028 | jq .

**Multiple commands**


  echo '{"command":"version+config"}' | nc IP_ADDRESS 4028 | jq .


**Command with parameter**


  echo '{"command":"asc","parameter":0}' | nc IP_ADDRESS 4028 | jq .

******************************
List of all supported commands
******************************

=============================
Commands from the CGminer API
=============================

We provide only brief description of the commands below. If interested in additional
details, please read the official documentation. https://github.com/ckolivas/cgminer/blob/master/API-README

 * **asccount** - The details of a single ASC number N in the same format and details as for DEVS
 * **asc** *|N* - The number of ASCs
 * **config** - Some miner configuration information
 * **devdetails** - Report per chain configuration
 * **devs** - Each available ASC with their details
 * **edevs** *[|old]* - The same as devs, except it ignores blacklisted devices and zombie devices (unless the "old" parameter is used)
 * **pools** - Report pool configuration and statistics
 * **summary** - The status summary of the miner
 * **stats** - Each device or pool that has 1 or more getworks with a list of stats regarding getwork times
 * **version** - Print API and BOSminer version
 * **estats** - the same as stats, except it ignores blacklisted devices and zombie devices
 * **check** - checks, whether the API command exists and is accessible
 * **coin** - coin mining information
 * **lcd** - short status summary of the miner
 * **switchpool** *|N* - switches the selected pool to the highest priority
 * **enablepool** *|N* - enables the selected pool
 * **disablepool** *|N* - disables the selected pool
 * **addpool** *|URL,USR,PASS* - adds pool
 * **removepool** *|N* - removes pool

**Note**: the commands *switchpool*, *enablepool*, *disablepool*, *addpool* and *removepool* are not fully implemented in Braiins OS. The outcome of these commands is reset after restart and they do not activate the pools. This is a known issue and is being fixed.

============
New commands
============

 * **fans** - Report fans statistics
 * **tempctrl** - Report temperature control configuration
 * **temps** - Report temperature data
 * **tunerstatus** - Report tuning statistics

********
Examples
********

**fans**
Report fans statistics



   {
     "STATUS": [
       {
         "STATUS": "S",
         "When": 1595938455,
         "Code": 202,
         "Msg": "4 Fan(s)",
         "Description": "BOSminer+ 0.2.0-ea64aec8e"
       }
     ],
   "FANS": [
       {
         "FAN": 0,
         "ID": 0,
         "RPM": 5340,
         "Speed": 100
       },
       {
         "FAN": 1,
         "ID": 1,
         "RPM": 4620,
         "Speed": 100
       },
       {
         "FAN": 2,
         "ID": 2,
         "RPM": 0,
         "Speed": 100
       },
       {
         "FAN": 3,
         "ID": 3,
         "RPM": 0,
         "Speed": 100
       }
     ],
     "id": 1
   }



**tempctrl**
Report temperature control configuration



    {
 "STATUS": [
   {
     "STATUS": "S",
     "When": 1595938464,
     "Code": 200,
     "Msg": "Temperature control",
     "Description": "BOSminer+ 0.2.0-ea64aec8e"
   }
 ],
 "TEMPCTRL": [
   {
     "Dangerous": 110,
     "Hot": 100,
     "Mode": "Automatic",
     "Target": 89
   }
 ],
 "id": 1
}



**temps**
Report temperature data



{
 "STATUS": [
   {
     "STATUS": "S",
     "When": 1595938484,
     "Code": 201,
     "Msg": "3 Temp(s)",
     "Description": "BOSminer+ 0.2.0-ea64aec8e"
   }
 ],
 "TEMPS": [
   {
     "Board": 81.875,
     "Chip": 104.625,
     "ID": 6,
     "TEMP": 0
   },
   {
     "Board": 85.875,
     "Chip": 108.9375,
     "ID": 7,
     "TEMP": 1
   },
   {
     "Board": 84.4375,
     "Chip": 105.4375,
     "ID": 8,
     "TEMP": 2
   }
 ],
 "id": 1
}



**tunerstatus**
Report tuning statistics



{
 "STATUS": [
   {
     "STATUS": "S",
     "When": 1595938492,
     "Code": 203,
     "Msg": "Tuner Status",
     "Description": "BOSminer+ 0.2.0-ea64aec8e"
   }
 ],
 "TUNERSTATUS": [
   {
     "ApproximateChainPowerConsumption": 1344,
     "ApproximateMinerPowerConsumption": 1419,
     "DynamicPowerScaling": "Disabled",
     "PowerLimit": 1420,
     "TunerChainStatus": [
       {
         "ApproximatePowerConsumptionWatt": 448,
         "HashchainIndex": 6,
         "Iteration": 0,
         "LoadedProfileCreatedOn": 1595938289,
         "PowerLimitWatt": 448,
         "StageElapsed": 78,
         "Status": "Tuning individual chips",
         "TunerRunning": true,
         "TuningElapsed": 98
       },
       {
         "ApproximatePowerConsumptionWatt": 448,
         "HashchainIndex": 7,
         "Iteration": 0,
         "LoadedProfileCreatedOn": 1595938289,
         "PowerLimitWatt": 448,
         "StageElapsed": 78,
         "Status": "Tuning individual chips",
         "TunerRunning": true,
         "TuningElapsed": 98
       },
       {
         "ApproximatePowerConsumptionWatt": 448,
         "HashchainIndex": 8,
         "Iteration": 0,
         "LoadedProfileCreatedOn": 1595938289,
         "PowerLimitWatt": 448,
         "StageElapsed": 78,
         "Status": "Tuning individual chips",
         "TunerRunning": true,
         "TuningElapsed": 98
       }
     ]
   }
 ],
 "id": 1
}



**devdetails**
Report device details



{
 "STATUS": [
   {
     "STATUS": "S",
     "When": 1595938989,
     "Code": 69,
     "Msg": "Device Details",
     "Description": "BOSminer+ 0.2.0-ea64aec8e"
   }
 ],
 "DEVDETAILS": [
   {
     "Chips": 63,
     "Cores": 7182,
     "DEVDETAILS": 0,
     "Device Path": "",
     "Driver": "",
     "Frequency": 799682118,
     "ID": 6,
     "Kernel": "",
     "Model": "Bitmain Antminer S9",
     "Name": "Hash Chain 6",
     "Voltage": 8.416799545288086
   },
   {
     "Chips": 63,
     "Cores": 7182,
     "DEVDETAILS": 1,
     "Device Path": "",
     "Driver": "",
     "Frequency": 809812285,
     "ID": 7,
     "Kernel": "",
     "Model": "Bitmain Antminer S9",
     "Name": "Hash Chain 7",
     "Voltage": 8.36398983001709
   },
   {
     "Chips": 63,
     "Cores": 7182,
     "DEVDETAILS": 2,
     "Device Path": "",
     "Driver": "",
     "Frequency": 770406487,
     "ID": 8,
     "Kernel": "",
     "Model": "Bitmain Antminer S9",
     "Name": "Hash Chain 8",
     "Voltage": 8.575228691101074
   }
 ],
 "id": 1
}
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
[...]

I went to website and do not see a link for s17 or s17 pro.

We have a lot of them (17 of them) and would love to see what you have.
hero member
Activity: 2534
Merit: 623
Thanks for the info Artemis. I realised it saves the profile today (after numerous restarts for a supposed "dead" pool which wasn't).

Wish I could afford an S17 lol
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
The profiles are saved (even during the process) to /etc/bosminer-autotune.json. If the process is interrupted, it does resume from where you left. If it finishes (shows Stable), it will do a quick checkup and use it if you reboot or power cycle. Should take about 2 mins and tells you that it loaded the profile saved at date x. Miner > Overview, Tuner Status, Status.

You can also connect to your miner using sftp (ie. filezilla) and copy this file, inspect it, etc. It saves hashboards ids, and you want that because no two boards are identical, chip yield and state of chips varies from each of them. It is the job of the autotuning algorithm to find out the best efficiency for each of the 63 chips on the 3 boards, which is why it takes so long finding the best values within the powerlimit you set, and keeps supervising in case conditions change later.

S17 and S17pro owners that have been waiting for Braiins OS+, get ready for tomorrow... T17, S17+ and S17+ to follow at a later date.
hero member
Activity: 2534
Merit: 623
Is there any setting which allows the miner to be identified as a given name say "S9 Heater" within the braiins OS when running an IP network scan?
EDIT: Found it in the "Network Interfaces" menu. Just edited the Lan settings on the green highlighted one and changed the "Hostname when requesting DHCP"

Also is there anyway to save a Power Tuned Profile somewhere so you can load is instantly rather than it go through the whole testing phase?
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
There is people running a single fan with powerlimit 900w who claim its very silent. There is even one person using 1100w with a single 6k.

So the same rule applies: If in doubt, reduce powerlimit. I think a couple of 3k rpm fans could work, but consider going single (push) as well.

Also leave the Target Temp at default 89°. This is the equivalent of 75° from when cgminer was used, they use the raw data rather than the "curated" (surface temp?) data; so don't think 89° is "too much". The S9 chips are rated fo up to 135° according to Bitmain's documentation. If you enable Dynamic Power Limit, when it reaches 100° (Hot temp) it reduces powerlimit the step you define, as many times as needed to keep the temperature under 100°. This matters when one of your fan fails. Otherwise it simply stops mining if it ever reaches 110° (Dangerous Temp).

It doesn't help if you lower it to 80°. To restore the default, simply delete whatever value you have in the field.
sr. member
Activity: 361
Merit: 267
Used the autotuning and specified 500w. It says its drawing 491w on all three boards  (527w at the wall).

Thanks for the direction/advice.

I set up one of my S9's with the same autotune parameters. It's been running for 11 hours stable @ 498 at the software level and 531 @ the wall. Hashing at 6.086Th/s.

Stock fans haven't gone above 4% and I have the unit in my non climate controlled New York summer garage.

I liked the 120x120x25mm delta fans.

Thanks for the reply. Are you running the 4000 RPM fans?
Pages:
Jump to: