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

[JSCSJSCS]

My node is fully verified and now I am trying to connect sparrow wallet to use my Futurebit node. Research shows how to edit the bitcoin.conf file for rcpbind and rcpallowip entries. I used putty to "sudo nano bitcoin.conf in the associated file directory and saved the changes. I even logged into the Apollo ii and used the file manager to see that the changes were confirmed as completed. After a reboot however, the file is reverted back to the default version and of course the sparrow "test connection" fails with "connection refused." I cannot figure it out. I'm going in circles. I don't know how this is even possible.

Futurebit Apollo II Full Node running v2.0.7

[sopsy8t]

After going back and forth with support, it seems my hashboard firmware has been corrupted. They said I would need to reflash it and had instructions. But alas, they are not following up (too common), so am wondering if anyone here has the instructions, and file to do this. It's not the Pi refresh (node) - it's the hashboard (standard).  Anyone?

[MakerAZ]

...and yes knots support too for anyone thats crazy enough to solo mine with that

Will it be possible to use DATUM?

[Lhick]

I read somewhere that if it gets above 76  it may shut down or enter a protection mode and ramp up the fans to full speed.
My operation eco mode is below 70.  normal is 70-72.  fast is 72 to 74 with much higher fan speed.  room temp is around 78 Fahrenheit .
I cant run turbo with room temp above 72F. 

if you have high temp issues, Have you shut down and cleaned the fan and box recently?   I get the air compressor out and blow air back through the apollo to blow all the fine dust out of it outside. lots of dust comes out, then my temp drops when I restart.  In eco mode I am not collecting as much dust with quiet slow fan speeds. 

No problems. I run both on Turbo full time and on a warmer days I'll see 80c with no degradation in performance.  I couldn't find any info on the Futurebit site, so I was just wondering.

80c is the max, thermal shutdown is a few degrees above that

FYI if you are running in turbo with those temps make sure you check your power cord and see if it's getting hot. We are issuing a recall for all remaining early units (ordered Nov-Dec 23) to replace faulty power switches, which can cause this issue in turbo mode.

I replaced the power connectors on my full node (batch 4)and two standard units (batch 4) after they melted. They were running on Turbo for ages and I hadn't checked in for sometime when I found them all with connector issues. I couldn't repair them myself so I got an electrical engineer mate to do the works.

[jstefanop]

I read somewhere that if it gets above 76  it may shut down or enter a protection mode and ramp up the fans to full speed.
My operation eco mode is below 70.  normal is 70-72.  fast is 72 to 74 with much higher fan speed.  room temp is around 78 Fahrenheit .
I cant run turbo with room temp above 72F. 

if you have high temp issues, Have you shut down and cleaned the fan and box recently?   I get the air compressor out and blow air back through the apollo to blow all the fine dust out of it outside. lots of dust comes out, then my temp drops when I restart.  In eco mode I am not collecting as much dust with quiet slow fan speeds. 

No problems. I run both on Turbo full time and on a warmer days I'll see 80c with no degradation in performance.  I couldn't find any info on the Futurebit site, so I was just wondering.

80c is the max, thermal shutdown is a few degrees above that

FYI if you are running in turbo with those temps make sure you check your power cord and see if it's getting hot. We are issuing a recall for all remaining early units (ordered Nov-Dec 23) to replace faulty power switches, which can cause this issue in turbo mode.

I replaced the power connectors on my full node (batch 4)and two standard units (batch 4) after they melted. They were running on Turbo for ages and I hadn't checked in for sometime when I found them all with connector issues. I couldn't repair them myself so I got an electrical engineer mate to do the works.

Yea the specific issue I pointed out is on the Apollo II AC switch.

As for the Apollo BTC with the 6 pin connectors, yea thats always been the issue with those connectors, they dont hold up even to rated specs over a long period of time so if you dont check them and "refresh" the connection (plug and unplug a few times) they eventually start to burn out. Thats why we stopped using them and in general went with an internal PSU design.

[jstefanop]

After going back and forth with support, it seems my hashboard firmware has been corrupted. They said I would need to reflash it and had instructions. But alas, they are not following up (too common), so am wondering if anyone here has the instructions, and file to do this. It's not the Pi refresh (node) - it's the hashboard (standard).  Anyone?

shoot me a DM support does not have access to that firmware, weird that the hashboard firmware would corrupt though have not seen that at all

[TheAnimist]

Hey All,

I'm hoping someone can help me out, I have an Apollo BTC full (plus 2 extra nodes), I'm trying to update the firmware, I've identified the board as the MCU2 (short connector) and flashed the card following the steps in the guide/readme.

When I power up the main unit, nothing happens... the fans spin, the USB mouse doesn't light up and I see nothing on the HDMI output.

This was working perfectly, so I'm not sure what to do? Is there a way to do a full hardware reset? Everything is connected as it was when it was running prior.

Any help/guidance greatly appreciated

Thanks

[MakerAZ]

I want to set up my FutureBit Apollo II Full Node in a way to block any inbound and outbound connections to Core 30.
How can this be achieved? Please help.

[Spezi007]

Hello everyone,

I hope someone can help me. I have an Apollo BTC full. I am trying to update the firmware. I identified the board as MCU1 and flashed the card according to the instructions in the manual/readme file. The flash process was successful. I also tried a second SD card.

When I turn on the main device, nothing happens... The fans are spinning, the USB mouse is not lit, and I don't see anything on the HDMI output.

I previously had the problem that I could no longer access webOS. At first, I thought the monitor was defective, but I had the same problem with a second one. Is there a way to perform a complete hardware reset?

I am very grateful for any help/instructions.

Thank you very much.

[super0]

Hello everyone,

I hope someone can help me. I have an Apollo BTC full. I am trying to update the firmware. I identified the board as MCU1 and flashed the card according to the instructions in the manual/readme file. The flash process was successful. I also tried a second SD card.

When I turn on the main device, nothing happens... The fans are spinning, the USB mouse is not lit, and I don't see anything on the HDMI output.

I previously had the problem that I could no longer access webOS. At first, I thought the monitor was defective, but I had the same problem with a second one. Is there a way to perform a complete hardware reset?

I am very grateful for any help/instructions.

Thank you very much.

Try moving the microSD, sometimes is not well positioned. Or maybe the HHD got moved, try to reconnect that too. Also give it time to start and settle, I remember when I did it I waited 10-20 min, restarted few times and then everything went smooth.

Something I noticed is that the Apollo BTC (at least mine) struggle to run on Turbo mode with the new OS, so I have to keep it running in Balanced mode.

[jstefanop]

I want to set up my FutureBit Apollo II Full Node in a way to block any inbound and outbound connections to Core 30.
How can this be achieved? Please help.

Stuff like this is not helpful regardless of what side you are on in this debate, and where it relates for futurebit mining nodes specifically this is going to cause you to get an orphaned block.

bitcoins ability to connect to all freely available nodes that are protocol compatible is paramount. Get used to many more clients you dont agree with in the future.

All futurebit nodes run 25.1 currently, and will upgrade to 28.1 in the upcoming OS 2.1 update. We are several years away from even considering 30 as the default, and by then hopefully this will all be sorted out (whether it's a hard/soft fork or not), and you'll be able to choose which client you want regardless in 2.2.

In the meantime you have to remember we are in a unique situation where most futurebit nodes are mining nodes, so if you are solo mining dont shoot yourself in the foot. If you block yourself from other nodes, what most likely will happen is these nodes are being run by the major pools, so therefore you will not receive the latest block, and if you do it will be super late and most likely result in an orphaned block.