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

If everything is connected correctly, you have a proper power supply, and there's a fan running, it should be fine running at turbo 24/7. It was designed for those settings.

Is there a recommended threshold for temp? Mine runs low to mid 60s on turbo. Wondering if I should drop it down to balanced or eco.

Try not to over-fit a solution to a problem that for the most part does not exist given the maturity of the OS and software..
If you really want these worker alerts via your pool then test if you can run multiple instances of Apollo-Miner v1.1 on the controller unit.
One may have to use a terminal only barebones OS to do this. Would suggest a separate 'TEST' SD card if going this path.

Hi, I received and got my FutureBit Apollo up and running about a month ago. It' been working great except I am only able to mine in ECO mode. Anytime I try to make a change it is reverted back to ECO mode. I've tried rebooting the unit with no luck.  I noticed that the DISK/USAGE is at 14.02 GB / 14.21GB and am wondering if this may be the issue? Any ideas or things I can try? I have a usb keyboard on the way so I can login direct to the unit as my wireless mouse didn't work.

Not sure if it's supported in the web UI, but you can name each worker using the pool username field.

Usually pools allow you to give names to each worker by appending a dot(.) and then the worker name to the username of the pool. Something like this:


You would only need one computer to name those 4 workers. Each one would just be another call of the apollo-miner binary with its name and specific parameters.

So I've had my Apollo's for a little while now and like most people here, I am thrilled to have them in my apartment! Currently running 4 of them - 1 with a controller, 3 without. My question it this - I have them connected to a pool but using the controller's UI via FireFox - I am only able to have these connect to a pool as 1 worker. All of the other miners I use have individual assignable worker names - so should there be an issue, its easy to identify which miner is problematic without actually being at home and staring at the screen. Is there a way to have each apollo connect to the pool as it's own miner while running them all connected to the unit with a controller? Or would I have to use external controllers for each standard unit to achieve this.

./apollo-miner -host POOL_URL -port POOL_PORT -user POOL_USERNAME.WORKER1_NAME -pswd x -comport /dev/ttyACM0 etc...

./apollo-miner -host POOL_URL -port POOL_PORT -user POOL_USERNAME.WORKER2_NAME -pswd x -comport /dev/ttyACM1 etc...

./apollo-miner -host POOL_URL -port POOL_PORT -user POOL_USERNAME.WORKER3_NAME -pswd x -comport /dev/ttyACM2 etc...

etc...

So I've had my Apollo's for a little while now and like most people here, I am thrilled to have them in my apartment! Currently running 4 of them - 1 with a controller, 3 without. My question it this - I have them connected to a pool but using the controller's UI via FireFox - I am only able to have these connect to a pool as 1 worker. All of the other miners I use have individual assignable worker names - so should there be an issue, its easy to identify which miner is problematic without actually being at home and staring at the screen. Is there a way to have each apollo connect to the pool as it's own miner while running them all connected to the unit with a controller? Or would I have to use external controllers for each standard unit to achieve this.

Shoot us an email with this error, its very rare and it seems to be caused by a specific pool/configuration and trying to narrow it down.

I'm trying to make the Apollo run at it's absolutely quietest setting, even below ECO. It would be awesome if you could answer a few questions I have about it.

Thanks @jstefanop for making this nice device. It works and looks great.

I'm trying to make the Apollo run at it's absolutely quietest setting, even below ECO. It would be awesome if you could answer a few questions I have about it.


Based on the documentation, ECO is set to: -brd_ocp 48  -osc 30.


Since I would like to run it even lower, I set brd_ocp to 30 and kept osc at 30(both minimums based on the documentation), this nicely decreases the fan speed (and sound) as expected.

My understanding is that the -osc parameter shouldn't affect the fan speed, and only brd_ocp would affect it. Is that correct?

One thing that I don't understand is why the minimum brd_ocp is 30?, would it be safe to run it at even lower numbers?, I'm aware that the hashrate will be reduced of course, but I'm mainly concerned about the hardware functioning properly at it's absolutely lowest value (for example, would it be possible to run it so low that the fans are not needed?).

Also, I noticed there's another fan in the "official" power supply. Since I'm planning to run it with very low power, I wonder if that fan is even needed as that's now the main contributor of noise. I guess I could buy another PSU without a fan for this "silent miner" project. Any suggestions for one? So far I've found this one, which should run without starting the fan until 220W so it should be absolutely noiseless.

Anyone else have the issue with this error at start?

It seems there is a problem to communicate with the miner, check error message.

SyntaxError: Unexpected end of JSON input

Wait at least 1 minute, if problem persists, try to restart the miner, check the settings or try to reboot the system.

I am running the full node by itself connected via cable.