Re: Official FutureBit Apollo BTC Software/Image and Support thread

Quote from: jstefanop on Today at 06:33:49 AM

Fan curves work through USB as well. Its the same parameters we use for the full node miner as well just didn't document them in git.

For a full list just type ./apollo-miner -h

FYI we are working on completely revamped support/guides/faq section on our site. These threads are obviously getting out of control, and do apologize for all the digging new users have to go through!

Thanks for that! Much appreciated!

I tried this code (no miner running at the time, in case that matters) with the included result:

Code:

./apollo-miner -h
apollo-miner 09bb0bf 2021-11-22, msp ver 0xd166
Use "--help" switch to print command line options.

ERROR: Invalid command line:
Unknown command line option: -h

but using the --help command results in a lot of interesting output:

Code:

Apollo-Standard_software/linux-x86_64$ ./apollo-miner --help
apollo-miner 09bb0bf 2021-11-22, msp ver 0xd166
Use "--help" switch to print command line options.

Usage (expected arguments):
usage:
-help Display this screen (command line usage)
pool:
-host <hostname> Set pool hostname (default: [stratum.slushpool.com])
-port <port> Set pool port (default: [3333])
-user <username> Set pool username (default: [jstefanop.apollodefault])
-pswd <password> Set pool password (default: [1])
-exit_on_errors Exit if pool rejects our shares
-connect_attempts <n> Exit if cannot connect after <n> attempts (default: 1000000)
-auth_t <n> Authorization timeout in seconds (default: 45)
-subscribe_t <n> Subscription timeout in seconds (default: 45)
-pool_no_data_t <n> No new data from pool timeout in seconds (default: 300)
-start_diff <n> Initial pool difficulty (default: 1024)
-roll_version Perform version rolling
-v_rolling_mask <n> Version rolling mask (default: 0xffffffff)
-v_rolling_min_bits <n> Version rolling min bits count (default: 0)
-sd_no_dma <0|1> Slave debug in dma(0)/sync(1) mode (default: 0)
-fan_temp_low <x> Set board temp at which fan speed should be the lowest (default: 50)
-fan_temp_hi <x> Set board temp at which fan speed should be the highest (default: 80)
-fan_pwm_low <x> Fan PWM if temperature <= fan_temp_low (default: 1)
-fan_pwm_hi <x> Fan PWM if temperature => fan_temp_hi (default: 100)
-comport <port> Name of port where board is connecting (default: COM1)stats export/events:
-alive_event_dt <n> Report miner-alive event each <n> seconds (default: 3600)
chip:
-osc <n> OSC: static oscillator register (default: 0)
-jt <n> OSC: base job time in ms (default: 100)
-ao_mode <n> Auto OSC: mode: 0 - static, 1 - auto (default: 0)
-ao_range_s <n> Auto OSC: adjust range: current osc +/- <n> (default: 2)
-ao_range_b <n> Auto OSC: limit range: current osc +/- <n> (default: 6)
-ao_delay_t <n> Auto OSC: delay time in sec (default: 100)
-ao_sol_d <n> Auto OSC: allowed solution delta for best osc (default: 1)
-ao_tps <n> Auto OSC: tasks per step (default: 32)
-ao_ml <n> Auto OSC: nonce mask len (default: 9)
-osc_step <n> OSC: osc setting step, 0 to disable set osc in one step (default: 1)
board:
-brd_ocp <n> Over Current Protection: max current per power line (default: 0x20)
-log_delay <sec> Logging delay in seconds (default: 10)
-log_chip_stat Log chip statistics

Board revisions table:
Rev ADC Rev SPI (mask) PWR BTC (mask) Volt Flags adcKu adcKi Human Name
3980 - 4030 20 1 x 4 (0x1) 2 x 2 11 (0x7ff) 12 0x31 5.55 10.00 Apollo-BTC

Most of it I don't understand, for some I may have a rudimentary understanding.

So I wonder if I interpret these following lines correctly:

Code:

-fan_pwm_low <x> Fan PWM if temperature <= fan_temp_low (default: 1)
-fan_pwm_hi <x> Fan PWM if temperature => fan_temp_hi (default: 100)

when I make the assumption that (default: 1) means that the stock ASIC fan lowest speed is already turned down to the minimum speed that PWM will allow?
In other words, the stock miner fan will run at 1800rpm no matter how much additional cooling I apply and no matter what software setting changes are made?