Official FutureBit Apollo II/BTC Software/Image and Support thread

[devincrypt]

couple issues for me. First was the package had a packing slip that showed what I paid for it. Might not want to have that sitting on porch for too long.

Totally agree. Wife and I went for a bike ride and upon return found my delivery in the front middle of our porch with the pricing and contents right on top. Never had any company in my life do that! Fortunately I grabbed it first. Strongly consider making only the address visible FutureBit!

Didn't help that the lazy FedEx driver didn't step two paces toward the door to place it behind a column.

From another recent customer:

Hi, I received the Apollo today and the build quality is amazing.  The FedEx guy advised me to tell you to NEVER put the contents and value on the label on the outside like that.  He said it was the talk of the local office with everyone commenting on how bad of an idea it was.  Please, don't do that - I mean it would just take folding the paper one more time to hide it.


Get the message???

[crypto_curious]

Hi, I received the Apollo today and the build quality is amazing.  The FedEx guy advised me to tell you to NEVER put the contents and value on the label on the outside like that.  He said it was the talk of the local office with everyone commenting on how bad of an idea it was.  Please, don't do that - I mean it would just take folding the paper one more time to hide it.

This problem doesn't exist outside of US, people here in Europe don't steal like that and couriers don't leave valuable parcels on the porch without getting signature of recipient first. Here, if FedEx courier is unable to get signature of the receipient, he leaves it in designated safe place, if there isn't one, he tries to leave parcel with the neighbour, and if that fails, he takes it back with him leaving missed delivery note.

[heslo]

How's the first update looking guys? Able to give us an ETA?

[cryptobradley]

Newbie questions...

I have 3 Apollo BTC miners up and running with no issues. Full node downloaded in 1.5 days. :-)

I have a controller and 2 standard units. I am running in turbo mode. Hash rate is ~3.1  I see all 3 in the dashboard.
Is there any way to increase the power on one of the standard units that is running with a 500W power supply? The other 2 are running the 200W PS. If they all need to be managed by the same rules, I will buy 2 more 500W power supplies if that allows me to increase the hash rate . If I do that, how do push all three to the 3.8TH/s limit? Do I need to adjust the power in "Custom Miner Mode"? If so, how high should I go?


Thank you in advance for your help/advice.

"*Our FutureBit 200W power supply is limited to ~ 3 TH/s, 3.8 TH/s is only achievable with an external > 300 watt power supply"

[FreezerB]

Speaking of questions...

Can one power supply power multiple miners? ie. one 500W ATX power supply connected to two miners.

[heslo]

Cant see why not, provided you've got enough PCI-E plugs on the PSU it should be absolutely fine at 500w to power two units

[dwood443]

Posted this in announcement thread by mistake, deleted that post. sorry

Got my full package miner today and the whole thing looks awesome. From the packaging to the power supply and especially the miner itself. Plugged it in and connected to the IP address with no problems. The dashboards look great.

couple issues for me. First was the package had a packing slip that showed what I paid for it. Might not want to have that sitting on porch for too long.

Second, can a wireless usb dongle keyboard be plugged into device?

UPDATE, Miner ran fine for 30 minutes with all default settings and then stopped. choosing miner restart does nothing. So trying to stop node and its appears to try to stop for a minute, but then back to the dashboard. I know I should not just power off right?

After 50 minutes of uptime the fan is starting to howl. I'll check the screws first.

Taking a step back. I've powered off and disabled the miner while the node syncs. once the sync is complete I will try mining again

UPDATE - never touched the fan. The whine seemed to go away on its own. Once the node finished syncing I turned on the miner again and mining now for 8 hours with no issues.

I also looked on ebay and it these things are getting big bucks. One appeared to have sold for $3000 

[crypto_curious]

Newbie questions...

I have 3 Apollo BTC miners up and running with no issues. Full node downloaded in 1.5 days. :-)

I have a controller and 2 standard units. I am running in turbo mode. Hash rate is ~3.1  I see all 3 in the dashboard.
Is there any way to increase the power on one of the standard units that is running with a 500W power supply? The other 2 are running the 200W PS. If they all need to be managed by the same rules, I will buy 2 more 500W power supplies if that allows me to increase the hash rate . If I do that, how do push all three to the 3.8TH/s limit? Do I need to adjust the power in "Custom Miner Mode"? If so, how high should I go?


Thank you in advance for your help/advice.

"*Our FutureBit 200W power supply is limited to ~ 3 TH/s, 3.8 TH/s is only achievable with an external > 300 watt power supply"

+1 for this question. What are recommended settings for 3.8 TH/s?

[100knot2dae]

For those of you with just standalone unit(s):

I have built a small wrapper for the standalone unit's apollo-miner and pushed the source to Github: https://github.com/golden-guy/apollo-launcher/blob/master/apollo-launcher

You can use it to create and launch miner configs as needed, e.g. this might be handy if you have multiple hash boards or just want to test/use different setups on a single hashboard. At least I wanted a more convenient way to switch between (test) setups. 

Only Linux is supported and tested, but the code (bash script) may be ported to macOS.

Feel free to use it when it adds value to your setup.

While this script can (and should) be executed as regular user, apollo-miner won't work out-of-the-box for non-root users. But this can easily be fixed by adding the user to the dialout group. I also added an issue for this here: https://github.com/jstefanop/Apollo-Miner-Binaries/issues/4

@jstefanop: I hope you don't mind me posting this here, but I didn't want to create a seperate thread for that. And it's both s/w and support related after all. 

[100knot2dae]

Newbie questions...

I have 3 Apollo BTC miners up and running with no issues. Full node downloaded in 1.5 days. :-)

I have a controller and 2 standard units. I am running in turbo mode. Hash rate is ~3.1  I see all 3 in the dashboard.
Is there any way to increase the power on one of the standard units that is running with a 500W power supply? The other 2 are running the 200W PS. If they all need to be managed by the same rules, I will buy 2 more 500W power supplies if that allows me to increase the hash rate . If I do that, how do push all three to the 3.8TH/s limit? Do I need to adjust the power in "Custom Miner Mode"? If so, how high should I go?


Thank you in advance for your help/advice.

"*Our FutureBit 200W power supply is limited to ~ 3 TH/s, 3.8 TH/s is only achievable with an external > 300 watt power supply"

+1 for this question. What are recommended settings for 3.8 TH/s?

For now, I have been going as far as 85/55, resulting in approx. 3,4TH/s@0,07W/GHs (with a 0,9% error rate). Guess you have to push the freq up to 60 to get the full 3,8TH/s (provided you have a capable PSU ofc!) Each hardware has its own sweet spot, so you have to try out what works best for you.

[dwood443]

Since my node shows as using 400.01 GB and growing I plan on updating the drive soon. How would you think it be completed? My thought was to use a device like https://www.amazon.com/gp/product/B07VVNGYFV/ref=ox_sc_saved_title_6?smid=A1NP2IZEAZE37Z&psc=1 and use the Crucial cloning software that comes with the drives I bought. But I wondered if I should clone with the full node? Or wait until my second miner in batch two is delivered and clone before the node syncs?

[gt_addict]

Since my node shows as using 400.01 GB and growing I plan on updating the drive soon. How would you think it be completed? My thought was to use a device like https://www.amazon.com/gp/product/B07VVNGYFV/ref=ox_sc_saved_title_6?smid=A1NP2IZEAZE37Z&psc=1 and use the Crucial cloning software that comes with the drives I bought. But I wondered if I should clone with the full node? Or wait until my second miner in batch two is delivered and clone before the node syncs?

I had to wait for my 1TB drive to arrive, but when it did I tried the exact same device (used for cloning an M.2 for my PC), But windows doesn't recognise the drive, well at least not for me. Linux would probably clone it just fine.

[jeyzeus]

So my unit arrived the other day and looks great and seems to be running well. The full node has fully synced up and i don't think i ran into any issues while i was mining on Eco.

The only issue i have is on the miner dashboard. For some reason I am getting a very high error rate - it's currently reporting 70%-80%+ hardware errors but i did not get many "rejections".

I thought running the node was taxing the CPU too much so i waited until that synced to reboot the unit and see if it would reset the errors but no luck on that.

It's odd - the unit seems to be running fine, any idea why it's reporting such high levels of hardware errors?

[jstefanop]

So my unit arrived the other day and looks great and seems to be running well. The full node has fully synced up and i don't think i ran into any issues while i was mining on Eco.

The only issue i have is on the miner dashboard. For some reason I am getting a very high error rate - it's currently reporting 70%-80%+ hardware errors but i did not get many "rejections".

I thought running the node was taxing the CPU too much so i waited until that synced to reboot the unit and see if it would reset the errors but no luck on that.

It's odd - the unit seems to be running fine, any idea why it's reporting such high levels of hardware errors?

A very small number of units will have this issue. Probably means you have a bad ASIC with a few bad cores that produce a really high number of errors. As long as your hashrate matches what it should then your unit is fine. Were trying to see if we can disable these cores in software for a future update.

[wavelengthsf]

Still getting the apollo miner crashing at least once daily. Any updates on increased ability to debug where the segmentation fault is coming from?

[jstefanop]

Since my node shows as using 400.01 GB and growing I plan on updating the drive soon. How would you think it be completed? My thought was to use a device like https://www.amazon.com/gp/product/B07VVNGYFV/ref=ox_sc_saved_title_6?smid=A1NP2IZEAZE37Z&psc=1 and use the Crucial cloning software that comes with the drives I bought. But I wondered if I should clone with the full node? Or wait until my second miner in batch two is delivered and clone before the node syncs?

Since these already sync so fast I wouldn't waste money on that. Just pop in the new drive and reflash your SD card and it will automatically set it up and start syncing.

[jstefanop]

Still getting the apollo miner crashing at least once daily. Any updates on increased ability to debug where the segmentation fault is coming from?

Is this on the standalone software or on your full unit?

[wavelengthsf]

Still getting the apollo miner crashing at least once daily. Any updates on increased ability to debug where the segmentation fault is coming from?

Is this on the standalone software or on your full unit?

Standalone unit running on Ubuntu.

[crypto_curious]

Still getting the apollo miner crashing at least once daily. Any updates on increased ability to debug where the segmentation fault is coming from?

I recommend something like this:

Code:

#!/bin/bash

miner_run() {

your mining command

}

# Main loop
while true; do
    miner_run
    sleep 10
done

exit 0

That way you never stop mining even after software miner crash, it just restarts automatically.

[wavelengthsf]

I recommend something like this:
...
That way you never stop mining even after software miner crash, it just restarts automatically.

Thanks, wrapped the start shell script in that.