Search content
Sort by
Showing 20 of 2,210 results by jstefanop
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
When will we be able to run knots on the Apollo !! full node?
I am sure FutureBit Team understands that this matter becomes very important day by day.It is crucial to be able to run Bitcoin Knots on Apollo, since it is starting to be obvious that Bitcoin Node gets increasingly corrupted.
Bitcoin will be the ultimate reference to value everything on Earth and beyond. So, there is no place for spam in immutable Bitcoin blockchain.
This youtube video https://www.youtube.com/watch?v=yTUreNqp7i0 explaines it much better.
We have publicly stated we are supporting mutiple core node client versions as well as knots and targeting a fall release for it (will be as easy as a drop down menue for which node client you want to run).
Obviously the whole mission of futurebit is to empower everyone with choice on the bitcoin network, and that choice will come down from the individual user and not us.
Reason its taking so long is because knots does not have extensive testing like core does, and since our Apollo system is a critical block creation tool the last thing we want is to ship something that prevents a solo block fine because of a stupid bug.
When it's ready we will release.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
@jstefanop, since the open source Bitaxe Gamma device is already using the Bitmain BM1370 (S21 Pro chip), are there any plans for Futurebit to release an Apollo model based on that ASIC? Would be great to see that efficiency in your standalone, quiet form factor. I loved both previous designs, Apollo and Apollo II, still using Apollo II to this day.
Any roadmap or technical hurdles you can share?
Any roadmap or technical hurdles you can share?
We have started to tease the Apollo III and since the Apollo II is completely sold out we will have more info soon.
I wont touch Bitmain chips for the same reasons I started futurebit, I dont want to support them even if its just second hand chips (and I wouldn't put second hand chips in any of our products regardless...reflowing an ASIC 3 times drastically reduces its life/failure rate and is the reason we can offer a one year warranty when most bitaxe companies cant.
Either way we have solve the major ASIC supply issue with our last ASIC partnership that essentially hamstrung scaling the Apollo II.
The Apollo III will be a game changer in both specs (will be most things on the market) as well as even more important scaling this to levels we will be able to make a difference in the space.
Exciting stuff coming!
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
@jstefanop Is futurebit working on any Lightning Node etures for the Apollo Nodes?
Focused on building the Solo Node/ Solo Pool features right now.
We have a lot of cool stuff we are working on in that department (friends and family pools, gamifying/paying out best shares etc)
While we could easily add lightning there are other node providers that have built out all of this way better than we could, and since we are focused on Solo mining I dont want to get into the multi app/services/bloatware since that could negatively impact chances of successfully mining a solo block.
Will probably remain laser focused on building the best home solo miner for the next few years, and once compute overhead/SBCs get even cheaper will re-evaluate if we want to add more apps.
(FYI nothing is stopping you form installing a lightning node on the current Apollo system)
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
I want to upgrade the original 500gb ssd m.2 from my BTC apollo MC1 version, what SSD drives will work for this. I hear not all work.
Any suggestions are appreciated
Thanks All
Any suggestions are appreciated
Thanks All
All crucial P2/P3/P3+ drives and Kingston NV2 drives will work...Kingston NV3 drives there is a variant that does not work due to some weird controller they use.
Those are the drives we have tested internally.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
When will we be able to run knots on the Apollo !! full node?
+1 for this question. Apollo 2 software update with this capability soon?
2.1 will be out shortly, we are working on user selectable node clients for 2.2 in a few months.
Needs lots of testing...our nodes being used as solo mining nodes carries more weight, last thing we want is to rush an update and then have someone fail to submit a valid block because of a badly tested node client.
FYI current client is 25.1 and 2.1 client will be 28.1. The controversial update is for 30 so there is not much functional differences between the clients we use as default and knots.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
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.
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.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Another Feb 14th purchaser with the same issues I can see cited here by many in the thread.
The node simply will not connect and on the occasions when it did it never got past block 225K before restarting from scratch again.
Reformatted the SSD 4 times now, the same thing happens or I get Connection Refused error or There was an error getting stats for Node: ETIMEDOUT.
Miner is not running.
Port 8333 is open and reachable.
500mb/s up & down direct to premises fiber.
Tried both static and DHCP LAN addresses. Same issues.
I have reindexed. Same issues.
Unit now intermittently clicks when on and nothing is running (no miner, no node)
I'm an EU user so am starting to think the RMA process will be a painful and expensive experience for me along with the import taxes/duties due on this unit still to pay (i knew what i was getting into in respect to that of course).
I have logged a support request via the online form and email so I guess now I wait for a reply as the 14 day cut off to log an RMA is on Wednesday/Thursday since the unit was finally delivered to me out here, I take my support email as notice to FB in respect to logging a potential RMA.
So far it's been an extremely disappointing experience with my Apollo II. I run a few Bitaxes and was a Butterfly Labs OG back in the day so this isn't my first rodeo with mining hardware but my unit seems seriously buggy/flawed in how it's trying to operate. Starting to think I should've gone with Umbrel or Start9 in running my own node and simply got more Nerd/Bitaxes for hashing but like many here I wanted to support FB and have an all in one unit capable of hashing and running a node from one box. It's a great looking unit the Apollo II but if it cannot do the 1 main thing it was designed to do it's completely useless.
This was supposed to be a plug & play node/miner and so far after the 2 days I have had trying to get it to work correctly it has been far from it in that regard.
The node simply will not connect and on the occasions when it did it never got past block 225K before restarting from scratch again.
Reformatted the SSD 4 times now, the same thing happens or I get Connection Refused error or There was an error getting stats for Node: ETIMEDOUT.
Miner is not running.
Port 8333 is open and reachable.
500mb/s up & down direct to premises fiber.
Tried both static and DHCP LAN addresses. Same issues.
I have reindexed. Same issues.
Unit now intermittently clicks when on and nothing is running (no miner, no node)
I'm an EU user so am starting to think the RMA process will be a painful and expensive experience for me along with the import taxes/duties due on this unit still to pay (i knew what i was getting into in respect to that of course).
I have logged a support request via the online form and email so I guess now I wait for a reply as the 14 day cut off to log an RMA is on Wednesday/Thursday since the unit was finally delivered to me out here, I take my support email as notice to FB in respect to logging a potential RMA.
So far it's been an extremely disappointing experience with my Apollo II. I run a few Bitaxes and was a Butterfly Labs OG back in the day so this isn't my first rodeo with mining hardware but my unit seems seriously buggy/flawed in how it's trying to operate. Starting to think I should've gone with Umbrel or Start9 in running my own node and simply got more Nerd/Bitaxes for hashing but like many here I wanted to support FB and have an all in one unit capable of hashing and running a node from one box. It's a great looking unit the Apollo II but if it cannot do the 1 main thing it was designed to do it's completely useless.
This was supposed to be a plug & play node/miner and so far after the 2 days I have had trying to get it to work correctly it has been far from it in that regard.
Just reply to your order email and will take care of it. As mentioned before in the current batch of controllers we are seeing a few % of them with bad memory chips (either production issue or actual bad chips), which is causing the node to fail to sync.
If you have gone through the normal troubleshooting (reflash your SD card, and reformat your node SSD drive by going to the settings and then extras menu) and it still fails to sync most likely thats whats going on.
If your in EU we can just send you the controller itself to swap out, its relatively straightforward to do.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Hi, I just received my Apollo 2 last week and have been trying to do IBD, but continually hitting the following error. Tried reformatting the ssd (tried a different SSD as well), flashed v2.0.6 (using a different SD card) and tried reindexing but nothing has worked -
2025-04-21T00:58:55Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 6fb015b067fe6a09ce5b3c08309c6192385688b00e75eb9febb97c83fb2f9f7e, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea height=341480 log2_work=82.138294 date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound: current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772 height=341479 log2_work=82.138246 date=2015-02-01T12:14:37Z
2025-04-21T00:58:55Z ERROR: ConnectTip: ConnectBlock 0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea height=341480 log2_work=82.138294 date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound: current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772 height=341479 log2_work=82.138246 date=2015-02-01T12:14:37Z
I'm wondering if this is a hardware issue or if there's anything else to try here.
Thanks!
2025-04-21T00:58:55Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 6fb015b067fe6a09ce5b3c08309c6192385688b00e75eb9febb97c83fb2f9f7e, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea height=341480 log2_work=82.138294 date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound: current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772 height=341479 log2_work=82.138246 date=2015-02-01T12:14:37Z
2025-04-21T00:58:55Z ERROR: ConnectTip: ConnectBlock 0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea height=341480 log2_work=82.138294 date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound: current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772 height=341479 log2_work=82.138246 date=2015-02-01T12:14:37Z
I'm wondering if this is a hardware issue or if there's anything else to try here.
Thanks!
If you keep getting these corruption errors after whipping the drive at least 2 times reach out to support, small number of recent batch of controllers had issues with bad memory chips.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.
I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.
It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised. I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc. I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."
I've scoured most of the 140+ pages in this forum. Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.
All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this. I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.
I've read that their return/exchange policy states only 14 days. So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.
Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II. (Obviously)
The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?
Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.
Just know I had good intentions when I parted with my $1k for the last 2 months...
Do they not test this shit prior to sending it out? They had 2 months!
I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.
It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised. I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc. I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."
I've scoured most of the 140+ pages in this forum. Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.
All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this. I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.
I've read that their return/exchange policy states only 14 days. So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.
Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II. (Obviously)
The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?
Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.
Just know I had good intentions when I parted with my $1k for the last 2 months...
Do they not test this shit prior to sending it out? They had 2 months!
Just reply to your order email for support. Not sure where you get the impression we dont take care of our customers. We are shipping out a high number of units currently so we might not catch 1/100 faulty units out the door.
I dont see any backlog in our support tickets beyond a few hours today.
Anything that does not work within a year is fixed or swapped out, and happy to refund if the issue was within the 14 days of you getting it.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
are there any release notes as to what has been updated? 2.06 is stable for me I dont want to jump up just yet if the updates arent critical.
thanks
thanks
It's a support update for the new hashboards shipping now. Will have the images posted on GitHub later.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Hello everyone.
Is there any way to stop Apollo II from running the fan ultra loud when the miner starts/stops? I have been taking it with me to meetups to show people how mining works, but every time I turn it on it just get lot of unwanted attention. Would be great if it could just start silently. Is it possible?
Thanks!
Is there any way to stop Apollo II from running the fan ultra loud when the miner starts/stops? I have been taking it with me to meetups to show people how mining works, but every time I turn it on it just get lot of unwanted attention. Would be great if it could just start silently. Is it possible?
Thanks!
Unfortunately not with the current controller, its actually a safety feature in case the controller dies...fan speed will go high to prevent board overheat
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Apollo Miner Binary Release v2.0.3 is out!
This release has support for the new variant hashboards which have started shipping out this week. These are the standalone binaries for USB standard units being run on Windows/Linux without an Apollo Full Node
https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/v2.0.3
New 2.0.7 image release for full node units with new board support incoming next week.
While these releases have a few minor bug fixes they are not required if you did not buy the recent lower performance Apollo II hashboards
This release has support for the new variant hashboards which have started shipping out this week. These are the standalone binaries for USB standard units being run on Windows/Linux without an Apollo Full Node
https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/v2.0.3
New 2.0.7 image release for full node units with new board support incoming next week.
While these releases have a few minor bug fixes they are not required if you did not buy the recent lower performance Apollo II hashboards
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
The miner that solved the block was an SK19Pro running Brains OS underclocked to 2250 watts, 100TH. I run it at 1250 watts during the day at 1250 watts / 60TH to keep the noise down. If the complete log is helpful, just let me know.
Yeah, that's what I was thinking. Unfortunately, we don't have any clear indication that an Apollo II has hit a block (on it's own) as yet. Congrats on the block!!
Oh, and be careful, the Karen's in this forum may report you to the mods for reporting that a device other than a FutureBit device hit a block. Ask me how I know, LOL!!
What device found the share is of no consequence to the bitcoin network, what matters 100x more is what and in what manner the block was constructed and submitted to the bitcoin network.
The Apollo is the device that submitted that block, and our work is what made it possible. The end goal has always been more nodes and decentralized block creation.
FYI our devices have been hashing on the bitcoin network for over 5 years now, and have found probably dozens of blocks in that timeframe (confirmed publicly via solo pools like ckpool etc and privately via the major pools that all monitor this internally).
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Won one for the plebs today using an Apollo BTC Full node, Apollo BTC standard, Apollo II standard and one Bitmain S19kpro.
Code:
[2025-03-21 04:31:00.699] Possible block solve diff 393692033929762.687500 !
[2025-03-21 04:31:01.278] BLOCK ACCEPTED!
[2025-03-21 04:31:01.308] Solved and confirmed block 888737 by bc1qa6y279yprwtuthnw0xqu6rzhrf8d6uujcdh9xd.S19k
[2025-03-21 04:31:01.308] User bc1qa6y279yprwtuthnw0xqu6rzhrf8d6uujcdh9xd:{"hashrate1m": "82.6T", "hashrate5m": "93.8T", "hashrate1hr": "102T", "hashrate1d": "57.4T", "hashrate7d": "57.9T", "shares": 76761530792, "authorised": 1735251121}
[2025-03-21 04:31:01.308] Worker bc1qa6y279yprwtuthnw0xqu6rzhrf8d6uujcdh9xd.S19k:{"hashrate1m": "80.8T", "hashrate5m": "86.3T", "hashrate1hr": "92.1T", "hashrate1d": "49T", "hashrate7d": "49.4T"}
[2025-03-21 04:31:01.308] Block solved after 104363805084 shares at 0.1% diff
[2025-03-21 04:31:01.278] BLOCK ACCEPTED!
[2025-03-21 04:31:01.308] Solved and confirmed block 888737 by bc1qa6y279yprwtuthnw0xqu6rzhrf8d6uujcdh9xd.S19k
[2025-03-21 04:31:01.308] User bc1qa6y279yprwtuthnw0xqu6rzhrf8d6uujcdh9xd:{"hashrate1m": "82.6T", "hashrate5m": "93.8T", "hashrate1hr": "102T", "hashrate1d": "57.4T", "hashrate7d": "57.9T", "shares": 76761530792, "authorised": 1735251121}
[2025-03-21 04:31:01.308] Worker bc1qa6y279yprwtuthnw0xqu6rzhrf8d6uujcdh9xd.S19k:{"hashrate1m": "80.8T", "hashrate5m": "86.3T", "hashrate1hr": "92.1T", "hashrate1d": "49T", "hashrate7d": "49.4T"}
[2025-03-21 04:31:01.308] Block solved after 104363805084 shares at 0.1% diff
Congrats just found out on X that you posted here!
If you can share your bitcoind debug.log would be super helpful for us, and any other info like network setup (wifi/ethernet broadband speed general geo area)
I salute you, now make sure you secure that stack 🫡
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Quote
Forum etiquette and posting in the appropriate threads should be followed to help keep things on topic for those of us that want to read things on specific pieces of hardware.
Agreed. Also it is rather bad form to be posting about a competitors gear here. Reported BubbaJoe's post to mods so they will hopefully move it to the BitAxe thread where it belongs.There are no competitors here, just a bunch of plebs reclaiming hashrate from centralized cartels. When Apollos and Bitaxes represent >50% of the hashrate we can talk about competition
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
HI,
I know this has been answered but i was unable to find any info.
https://github.com/jstefanop/Apollo-Miner-Binaries
can i use apollo 2 miner binaries OS image file on raspberry pi 5 and link my own miners ie nano 3?
I know this has been answered but i was unable to find any info.
https://github.com/jstefanop/Apollo-Miner-Binaries
can i use apollo 2 miner binaries OS image file on raspberry pi 5 and link my own miners ie nano 3?
You cant use the images on the Raspberry Pi as it's designed for our custom ARM controllers. The OS itself can be installed on any linux system, but requires some modifications on the system.
it expects an nvme drive at /dev/nvme0n1p1, and the Bitcoin database folder at /media/nvme/Bitcoin
You could probably symlink both of these to wherever they exist on your system and it would probably work on any ARM system
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
The core cpu is a raspberry pi
Nope! It isn't a RaspberryPi!
It is listed as "6 ARM Core CPU @ 2GHZ and 4GB of RAM" which I believe is actually an OrangePi 4!
I have a non-working USB port in my batch 1 node. Does this mean I can replace the pi in the node with a new board (OrangePi 4) - reflash and it will be fixed?
thanks.
Technically yes, the boards are interchangeable between Node/USB variants and both boards have all required ports for either use case.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Cleaning dust off the APOLLO II.
It's been 3 months since I received my Apollo II. I have mine turned sideways for better airflow through the bottom, which it does. The top vents are clogged from dust accumulation. I suspect that would get worse faster if I had the top vents pointed up.
Shut down my node, got the Air compressor blower and blew the dust back out. Lots of fine dust was blown out the top and bottom. No noticeable cooling difference. I thought there might be but the unit seems to be cooling well even with a small coating of dust. Now good for another 3 months.
running a fresh flash of v2.0.6 does seem more stable than v2.0.6 as long as I don't load up a bunch of other stuff In the browser. And don't try to restore saved settings as this wipes the settings installed in v.2.0.6. When I did this my node became less stable with the settings I saved from v.2.0.5 includes reverting back to 32 node connections. On v2.0.5 when I upped the nodes to 64 the system would crash. Not under v2.0.6.
It's been 3 months since I received my Apollo II. I have mine turned sideways for better airflow through the bottom, which it does. The top vents are clogged from dust accumulation. I suspect that would get worse faster if I had the top vents pointed up.
Shut down my node, got the Air compressor blower and blew the dust back out. Lots of fine dust was blown out the top and bottom. No noticeable cooling difference. I thought there might be but the unit seems to be cooling well even with a small coating of dust. Now good for another 3 months.
running a fresh flash of v2.0.6 does seem more stable than v2.0.6 as long as I don't load up a bunch of other stuff In the browser. And don't try to restore saved settings as this wipes the settings installed in v.2.0.6. When I did this my node became less stable with the settings I saved from v.2.0.5 includes reverting back to 32 node connections. On v2.0.5 when I upped the nodes to 64 the system would crash. Not under v2.0.6.
I also have mine on its side with the large vent and switch pointed up, also sitting on top of a laptop cooler. I notice a few days ago the dust on the top vents and used my vacuum to suck it away. I am still using v.2.0.5 and I have set mine to 64 node connection without a problem. It will bounce between 63-64. (Just checked and it's connected to 3 other Apollo nodes right now)
DO NOT DO THIS.
Figured this is also a contributing factor to failed power switches as well.
The unit is carefully designed to have balanced airflow coming from top and bottom of device (even the height of the rubber pads was painstakingly chosen for optimal flow). This is because the PSU is passively cooled via the main heatsink fan, if you put it on the side almost all the airflow goes through the bottom (with yes slightly reduced fan speeds which is why people are probably doing it), but means the PSU gets NO airflow and overheats.
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
The newest Etcher version works fine for flashing the new MCU2 v2.0.6. Old Etcher (v1.18.11) fails to load on my Mac now, advises to immediately dismount or will cause damage.
I was trying to update one of my batch 1 apollo and now that the new version of etcher failed to flash the compressed img and my mac won't load etcher v1.18.11 I have a paperweight with no os how did you get around this?
I figured out that using archive utility to unzip first then flashing with the latest etcher worked
Yes etcher is a mess right now very annoying...use latest version and decompress the image first
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
Software Bug Found: Changing system time zone will cause miner data to reset to 0 while miner and node programs are running. Stopping and restarting the miner did not fix the problem.
v2.0.6 apollo II
I changed the time zone on the Apollo II. This caused all miner data to reset to 0 and not report any data. I waited an hour and no update. It did not affect node data and solo mining data. Miner operated as normal and fan speed is working. But you can't see temp data for the miner nor fan speed.
A reboot after setting the time zone did fix the problem.
v2.0.6 apollo II
I changed the time zone on the Apollo II. This caused all miner data to reset to 0 and not report any data. I waited an hour and no update. It did not affect node data and solo mining data. Miner operated as normal and fan speed is working. But you can't see temp data for the miner nor fan speed.
A reboot after setting the time zone did fix the problem.
Thanks will look into fixing this for UX. Prob a local time bug instead of using UTC.