FutureBit Apollo III - Next Gen Home Mining

[heslo]

I've found the same loop on the full Apollo version when I received it. Since I was waiting for my new Nvme drive, I set the miner to an external pool and stopped the node but on the logs I could see all the retries to start the node which I've found weird and unecessary since no Nvme drive on the unit and Node was stopped.

For sure this is way less an issue on the full version since it is supposed to have the node turned ON but yeah a fix would be nice to don't see all thoses retries while the node is stopped.

This is because majority of units have shipped with the full node controller, next update will disable this if no nvme drive is installed. Either way it's just a log artifact.

We should have 2.1.4 out next week with unified Solo Node and Apollo III kernels/image, which lays the groundwork for our major 2.2 update. Lots of cool things in here including dual NVMe support, scheduled miner settings, support for Apollo III devices to mine to multiple pools at once and finally a fool proof and working upgrade system that wont break.

Scheduled mining is EXACTLY what I'm waiting for! If you need testers, reach out

[crypto_curious]

I've extracted mining files and wrote service of my own, similarly what I did with Apollo II two years ago (I've even shared my project files on gitlab).
Now my apollo 3 is fully temperature controlled. Sitting in external enclosure outdoors, it's heating home storage battery when heat is needed (usually at night), or working normally during the day. A lot of fun coding it!

[heslo]

I've extracted mining files and wrote service of my own, similarly what I did with Apollo II two years ago (I've even shared my project files on gitlab).
Now my apollo 3 is fully temperature controlled. Sitting in external enclosure outdoors, it's heating home storage battery when heat is needed (usually at night), or working normally during the day. A lot of fun coding it!

That's really cool man, well done!

[Black_Onyx]

A block was found with a FutureBit Apollo Solo mining...

https://i.postimg.cc/7YBc6XJ4/Screenshot-20261027-220227-Chrome.jpg

https://mempool.space/block/00000000000000000001e7da28fd249de38ba0a36f326ac447d933eef9ea630c?goal=0_8330f4b43c-ce82c8e1e9-297527630&mc_cid=ce82c8e1e9&mc_eid=f8d72942b4

[Black_Onyx]

I've found the same loop on the full Apollo version when I received it. Since I was waiting for my new Nvme drive, I set the miner to an external pool and stopped the node but on the logs I could see all the retries to start the node which I've found weird and unecessary since no Nvme drive on the unit and Node was stopped.

For sure this is way less an issue on the full version since it is supposed to have the node turned ON but yeah a fix would be nice to don't see all thoses retries while the node is stopped.

This is because majority of units have shipped with the full node controller, next update will disable this if no nvme drive is installed. Either way it's just a log artifact.

We should have 2.1.4 out next week with unified Solo Node and Apollo III kernels/image, which lays the groundwork for our major 2.2 update. Lots of cool things in here including dual NVMe support, scheduled miner settings, support for Apollo III devices to mine to multiple pools at once and finally a fool proof and working upgrade system that wont break.

Any news on firmware update?

Just like on the Miner tab—where restarting the miner resets the counters to zero—would it be possible to have the counters on the Solo Pool tab reset to zero when the pool is restarted?

I also noticed that the Solo Pool icon on the top right in the overview tab and the 'Active' status under "Solo Mining Users" on solo pool tab stop updating when I navigate away from the main GUI page and return later. Refreshing the page resolves the issue, and it seems to happen only with the Solo Pool.