Official FutureBit Apollo BTC Software/Image and Support thread

[jstefanop]

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.

ECO: This is the most efficient, quiet, and low power mode. Your Apollo will mine at about 2TH/s in this mode and consume about 120 Watts. The fan should be barely audible in this mode.

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

board power - this controls power/voltage for the board in %. It ranges from 30-95
board frequency - this controls the hashboard's frequency. It ranges from 30-60

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.

Yes brd_ocp parameter is essentially power draw of the board in %. The board regulates via current instead of voltage (these chips are prone to runaway current if voltage/heat is too high), so this precisely controls how much heat is given off. The downside is that hashrate can vary based on this setting even between units in same environment, and hotter environments will reduce hashrate even if the setting is the same etc.

The UI is limited to 30% to be dumb proof but you could go lower but you'll quickly get into stability issues as voltages below 30% are below what the chips can usually handle. You can't "hurt" the chips with really low power/voltage so you can experiment if you want to find a really low power draw...you can probably achieve ~ 60 watts @1.5 TH.

[n0nce]

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.

I'll address noise in my upcoming review, but I managed to get it very quiet while running on full speed and 200W, by giving it 4 little feet and two PC fans above and below the device. They are pretty quiet and add more airflow, so the internal fan auto-lowers itself. By additionally placing the unit in a strategical way, it's inaudible from my workspace.

I know that this setting (3TH) is not the most efficient one, but I aim for the highest hashrate and still don't want to hear the fan all day.
Also tried stashing it into a drawer, which was a horrible idea. This thing needs all the airflow it can get!

No issues with PSU noise since I run a 450W Seasonic PSU and its fan barely turns at 200W of load.

[baker240]

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.

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.

Thanks for the prompt reply. What email should I send this too?

[baker240]

So I was able to get it working by flashing the SD hehe. Guess I should have tried that first. Sorry to waste your time.

[CochnocherCrypto]

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.

[Muppet007]

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.

You are thinking correctly.

Each of the 3 non-controlled 'hash boards' would need its own SBC like a Raspberry PI as a controller then connected to the pool as another worker.

Would be cheaper to find a way to access the Apollo BTC UI remotely on your phone.

 

[nullama]

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.

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:

./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...

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.

[devincrypt]

Purring away month after month in balanced mode, about every 3 months I gently shut them down to blow the dust out of the miners and PSUs. Since I popped out the SDD from the start, I do wish I'd get some feedback on safely installing CPUMINER since the cpu is getting bored...

Thanks FutureBit for stability!

[Muppet007]

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.

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:

./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...

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.

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.

[luckyroll4]

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.

[jstefanop]

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.

Yes sounds like there is something wrong with your SSD and its trying to download the blockchain to your sd card. Shoot us an email and well see what's wrong.

[CochnocherCrypto]

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.

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:

./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...

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.

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.

That makes sense! I will see about doing that. For whatever reason, it seems like the Apollo I have with the integrated OrangePi always has a higher HW Error % than the other 3 (nothing major - my 3 standard units generally report an HW error rate of 0.4-0.7% while the unit with the SBC is closer to 3.5-4%) - Wondering if it is because, looking at the way the unit was designed, the OrangePi looks to be drawing it's power from the hashboard, slightly lowering the power the board has at it's disposal. The same unit also runs just a tiny bit hotter with the fan spinning just a tiny bit faster (I guess this is to be expected with the controller attached...). All the same - having them set up in a way that they can be individually tweaked would be great. I will see about launching multiple instances of the Apollo-Miner and will report back!

I appreciate everyone who chimed in and offered their thoughts!!!!

[CochnocherCrypto]

Aside from my one snag you all are helping me to resolve - I have to say compared to the hardware I used to have set up at my place... these are just plain awesome. Lower electricity bill, full node running without having to set up another RaspberryPi, and they look fantastic!

[jedilostone]

Hello, i recently received a Futurebit Apollo in the mail, but i believe it may have been mishandled by the delivery folks

I heard something moving around inside box but didn't pay no mind at first

Later on as i went to plug in the USB cable, i realized it wasn't there...the piece that sits on board to connect usb cable to had fallen off  

I'm not exactly sure how it happened but i have had mail mishandled in the past unfortunately

Can anyone assist me with what i can do to get fixed? Can it be shipped back to Futurebit offices for repair?

Please Advise, Thank you

[baker240]

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.

[nullama]

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.

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.

[baker240]

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.

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.

Thank you nullama

[expatbaku]

Hello everybody,

I have now two full nodes Futurebit Apollo BTC running each with a standard unit (4 boards total), 14 Futurebit Moonlander 2 and 2 full node Futurebit Apollo LTC.

These are absolutely great and help support

Is there a way to get all of them on one single dashboard either through minera on one of the Apollo or running grafana on a raspberry pi to avoid getting back and forth to each invidual IP?


Thanks and regards,

[notabeliever]

I trying to find out why my Apollo stops hashing after several days. When looking at the miner it has all lights blinking and looks to me thats it trying to has.

Log file anywhere stored ?
The fix is to unplug all cables to it and replug them including  ethernet cable. Just turning power off and on doesn't work.

-Front Blinking Red
-Back 1 solid Green 1 Blinking Green
-Back Ethernet blinking yellow

I tend to think its internet related , if only it made a little noise to see if its hashing

My setup is 1500w power supply running at 110V running 2 apollos (standard and Main)

[heslo]

I trying to find out why my Apollo stops hashing after several days. When looking at the miner it has all lights blinking and looks to me thats it trying to has.

Log file anywhere stored ?
The fix is to unplug all cables to it and replug them including  ethernet cable. Just turning power off and on doesn't work.

I tend to think its internet related , if only it made a little noise to see if its hashing

My setup is 1500w power supply running at 110V running 2 apollos (standard and Main)

What version of the software are you using? 0.3.2?