But what is the <rest of parameters> ? Or do I just enter the above line?
I already said on the last page that the parameters are explained in
start_apollo.sh.
Cheers, the penny finally dropped! I'll explain in case other beginners benefit from a 'For Dummies' explanation:
I falsely assumed that I could change the operating parameters while the Apollo (Full Node or Standard) is already running, like when changing the setting in the GUI of the Full Node Apollo.
But now it dawned on me that the full node Apollo does not respond to GUI settings changes while it is running either. The ASICs needs to be stopped and restarted before a change to the settings will occur.
For the change between ECO, Balanced and Turbo mode this fact is reflected in the "Save and Restart" button that needs to be clicked in the GUI, no option to misunderstand and not actually change the settings.
But for a change to the Fan temp settings, the Save button does not automatically do a restart. Next to the Save button is an explanation:
"You need to save your settings to apply changes (miner won't be restarted)."I think this could be worded better, what it means is
"You need to save your setting to apply changes but you also need to restart the miner before the changes will take effect. The miner will not automatically restart."Or, make it a 'Save and restart' button like for the Miner mode settings.
What the GUI in the Full Node Apollo does when settings changes are applied is this:
It writes a new line of parameters in the start_apollo.sh file. Everything the miner needs to know about how to operate needs to be in that one line of code (or it uses the default settings in the apollo-miner file).
./apollo-miner -host us-east.stratum.slushpool.com -port 3333 -user jstefanop.x -pswd x -comport /dev/ttyACM0 -brd_ocp 48 -osc 30 -ao_mode 1
When the 'Save and restart' button for the Miner mode (Eco, Standard, Turbo) is clicked, then the GUI will also stop the miner (I don't know how yet) and then it 'types'
which starts the miner again, with the parameters specified in that one line of code (and all the defaults in the apollo-miner file).
Thereafter, the miner will stubbornly continue to run with these parameters. No changes are possible unless it is stopped and restarted with a new line of code saved in the ./start_miner.sh file.
So, if you want to change what a Standard Apollo does, you have to edit the line in the ./miner_start file and then start the miner by typing sudo ./start_miner.sh in a terminal (after changing directory to wherever that file is on your computer by using the cd command in that terminal).
You specify your mining pool and user name and password in that line so that it no longer points at jstefanop's pool, but at yours.
Then, if you want to change from Eco to Turbo mode, you change
to
And if you want to test the minimum speed of your miner fan (and risk frying it if you forget to turn it off again!), you add:
and restart it with that added part in that one line of code.
Here is the practical upshot for anyone who has continue to read all this: You don't have to edit that one line in the .sh file every time!
You can save the start_apollo.sh file (including any edits you have made) with a descriptive file name and then use
sudo ./start_DESCRIPTIVE-FILENAME.sh
to start your Standard Apollo with that set of parameters.
For example:
start_Apollo_Turbo_Auto-Fan_Slushpool_20221125.sh
or
start_Apollo_Turbo_NOFAN-DONOTUSE_20221125.sh
for the above example without fan , which would fry your miner if you let it run for too long!
So once you have figured out how to edit the .sh file, and you have tested the proper functioning of the Apollo when it runs with that file, you can save different versions and use them quickly without risking that you make a mistake in the gobbledigook code part. You could have different start_Apollo.sh files for Winter/Summer operation, or loud/quiet, or to quickly change mining pools.
