Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 45. (Read 48695 times)

I started a new thread without direct mentioning of the Apollo hardware.

So if anyone is interested, follow me here: Worst case ASIC heat scenario

https://bitcointalk.org/index.php?topic=5424883.new#new

i will, thanks

Some of them do, and all of mine do.

jstefanop mentioned that Futurebit had supply problems during Covid and had to source a number of different fans, so different Apollo's might have a different fan.

It is not necessary to use the Standard Apollo and command line interface in a terminal with to verify which type of fan is in a specific Apollo. But it is very educational and I'm glad I started to stumnble down that path.

To easily test the capabilities if the miner fan in a Full Package Apollo the owner can simply set the Miner fan speed in the GUI of the Full  Package Apollo to something like 60c/65c and then restart the miner. The fan should then run at it's lowest possible speed, that could be 0 rpm or higher, until the miner temp reaches 60c.

That's correct!

That's all correct, too, thanks for writing such a detailed guide / explanation. Will bookmark it for future reference.

I'm not an expert on fans, but I'd go Noctua (Industrial) or Delta (though those aren't known for being quiet, but certainly high-performance.. so may perform well at low-RPM, too).

Does the stock fan continue running at 1800RPM even when it's set to 1% for any temperature (-fan_pwm_low 1 -fan_pwm_hi 1)?

Maybe try custom install... :/ This should be a software bug.
If you have a spare microSD, give my guide a try.

i am still having the problem, the pool switch at least once a day, so i update manually the pool (remove and add the same url). we can't update the apollo to fix this problem for the moment!!

Still no fix for this?
Really annoying to pay that much to hash for Futurebit !!!
My pool never dropped using the standard unit in Linux terminal.
Only switch pool with the full node unit LAN or WAN no difference.
Please update with a Pool lock command or something FutureBit.
Thanks

Tested it, thanks!

The fan is the type that will not run slower than about 1800rpm. I have double-tested this by connecting a different fan. An 80mm Noctua PWM fan will run intermittently, while the stock fan never goes below 1800rpm.

Could you please let me know which fan would be ideal for the Apollo ASICs ? I'm happy to buy some and replace them if they are now available.

I would like a high quality fan that can reach high speed and air flow when required, but turns off completely (or at least so slow that it is very silent) when the miner temperature is below the -fan_temp_low setting.

How should I turn off a Standard Apollo?

My assumption was to but that does not actually turn it off,

although it seems to claim it has stopped:
What is going wrong here?

Assuming the lines referenced in the above output are these:
 

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).
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 to start your Standard Apollo with that set of parameters.

For example: or 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.

Cheers!
That means that the stock antenna in the FP Apollo is located in the worst possible orientation and inside a Faraday cage. No wonder it did not work well before I put it outside of the housing!

It 'should' be (famous last words?  ) easy enough to make a part to hold it vertical just outside of the housing, and protect against yanking and chafing at the same time.

Optimal would be to route the antenna connector to the outside - maybe to a more sturdy SMB connector, so that even better WiFi antennas such as used on routers and PCs could be screwed on.



Vertical should be much better. The RF waves are like a donut. The center line is your antenna.



If the antenna was horizontal, the strongest reception would be above and below the antenna and not sideways - the direction in which they best propagate across a room / flat towards the access point.

The hole in the housing with 5V DC Out written below it works well for that purpose. I use a rubber cable gland to reduce risk of chafing the cable on the edges. I might design a 3D printable adapter for it if I get bored.

Would this antenna work better in a horizontal or a vertical position, or does it not matter?

No, you could use the Ethernet connection and a different device on the network to set up WiFi, then disconnect the Ethernet cable and it should switch over to WiFi.
However, I don't think WiFi is generally very good on the Apollo. There have been reports of people having issues with it. One idea I had was to 'route' the Orange Pi 4's antenna outside of the metal casing, which may act like an RF shield and weaken reception.

If you have a standard unit and the host (PC) goes to sleep / lock, it will definitely stop the miner. No way around that; that's where SBCs or full unit come in handy. They keep the hashboard busy at minimal overhead in electricity / power draw.

I already said on the last page that the parameters are explained in start_apollo.sh.


You should also be able to execute ./apollo-miner --help for explanation of all parameters.
I think it's trivial to understand that the binary needs to know basic stuff like pool config and device port on the computer. Everything else should be optional. Though it's possible that you have to also set power params (-brd_ocp 60  -osc 40).

Looks like you are not the only one:

https://bitcointalksearch.org/topic/m.61325163

Hi guys,
my Apollo runs on Antpool for a while then randomly switch to this Futurebit pool.

URL: btc.viabtc.com:3333    Username:  portforwarded.futurebit

Once a day or 2 this will happen.
Anyone else experienced this?
Thanks

How do I do this test? With the Standard or the Full Package?

I assume I will have to open a terminal while the Full Package Apollo is connected via HDMI to a monitor.

Then type
But what is the ? Or do I just enter the above line?

And what do I type in afterwards to get rid of 'Oh, the spirits I called...' ?
To set the same parameters as the Auto Fan Settings 'ON', do I have to type the following?

Code:

./apollo-miner -fan_pwm_low 40 -fan_pwm_hi 60

Anyone run into issues where the unit goes to sleep if you 'lock' the computer? If I leave it unlocked and just turn my monitor off, I don't run into connectivity issues.  But, after a few hours if I 'lock' the computer, unit loses connection to the internet in some capacity and the result is that my miner stops delivering hash to slushpool.  Anyone else run into this issue?  I don't see anything in the settings that would change this result when 'locking' the computer.

My WiFi PW is complex but no spaces

My wifi has a complex password with spaces and special characters and it wouldn't connect for me either. I ended up changing to a password with no spaces or special characters and it worked. You could try that if it applies to your situation.

Caps lock or something like it?