Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 13. (Read 50722 times)

yes

did that already. I'm wondering if there's something I need to dump in the drive, for it to rebuild and connect. just churning, and I hate to have to start from scratch.

Possible power switch issue?
So I've been pretty happy with my Apollo II, running it in solo mode and even pointing two Avalon Nano 3's to it right now.
Besides the SQL bug for the GUI, it's been great.  Occasionally, I may need to reboot it as I haven't been sure how to work around the SQL bug and monitor the unit remotely.

Recently, when I reset my remote PDU switch to the outlet, the unit won't come back on. When I reset the power switch on the back of the unit, it would start to work just fine.
This happened a few times but now, when it reboots and starts to begin hashing, the unit turns completely off! It seemed the switch was acting as a safety, as if I barely touched it, it would "reset" and start to give it power again.

I decided to open the unit to see if I can see anything but everything looked great inside.  For me, I decided to bypass the wiring inside to skip the switch and have the power supply go straight to the outlet plug.
After verifying where the wires should go, I disconnected the wires from the PSU to the switch and plugged it into the wall plug to bypass the switch.  I powered it up now everything is working again and it has started hashing!

Not sure the quality of the power switch in the back of the Apollo II unit, but if needed, you can bypass it and it seems to work great now.

If you have random shut downs and resetting the power doesn't fit it, that little switch could be the issue.

If your unit us Apollo BTC try to flash it back to MCU2 since according to futurebit support you can download either MCU1 or MCU2 so it means the MCU2 is supported on Apollo BTC and Apollo II is not compatible with MCU1.  Try to reflash it again and test it with MCU2 image.

Have your read message #4 FAQ on this forum?

Apollo BTC. I had the wrong MCU version flashed. So I reflashed it, and let the node catch up to the current block and hit start miner. Its been churning for 3 days with the message - 'waiting for the current miner status to match the desired one (online)'
This doesn't seem to be working itself out.
Do I need to reformat the SSD and start from scratch? Or should I be able to re-flash the correct MCU image and get this working again.

Thanks!

I have an Apollo 2 standard version linked to my MCU2 Apollo full node. Full node trucks away at around 3TH and has alway worked fine. I am not getting a single hash out of the Apollo 2 even though software is updated and I have flashed the Apollo 1 card numerous times now. Oddly the Apollo 1 seems to be recognizing the 2 and certain stats like temp, etc. No hashes on the UI or at the pool end either.  

I have tried everything, BTC Merch and FutureBit support, no luck. I even tried returning it and they want me to have a conference call with the CEO of BTC Merch to do so, I mean come on.

Anyone have a similar issue?


Hashboard #0 - Apollo II
0 TH/s
173 WAtts
66 C
20.9 A
2245 rpm
0%

Hashboard #1 - Apollo BTC
3.03 TH/s
196 WAtts
62 C
24.3 A
3148 rpm
4.8%

Thanks for the help, I did try the GUI option but unfortunately I’m not able to mine with my s19 to my own node when I stop the Apollo from mining.  Guess I’ll just let her mine away and consume unnecessary power.   

I should add, I get the solo-to-your-own node idea using modest (and cheap) amount of hash rate though I point my solo hash at a well connected pool (Kano.is) to do it. Losing a block in an orphan race is just something I will not risk. PAYING $$$ for hash to point at my own node that is not set up to provide very fast & well connected links to propagate the Block Found message - out of the question.

Noted. thanks for the info

A. Renting hash to point at your node is a bad idea. Throwing $$ at your private node is insane... Do you have redundant infra and connections to the 'net to broadcast Block Found info to the multiple sites around the world that well run pools use? Odds are - no. I would NEVER risk losing a block in an orphan race against better connected pools like that...

 B. Most hash rentals require an initial connection minimum diff of 1,000,000 to run due to the size of the 'mega-miner' they are providing.

thank you thank you very much I am trying to learn the ropes much is appreciated.

Yes, you can stop the miner in the GUI and the node will continue to run
GUI options:
  1 on the miner screen at the top hit stop miner
  2 hit the power button top right and select stop miner

SSH options:
  1 sudo systemctl stop apollo-miner.service
  2 If you want to make it permanent after stopping the service sudo systemctl disable apollo-miner.service

I've been renting hash power and trying to send to my solo pool but it doesnt work because the difficulty is too low. Is there anyway to increase that or is it not worth it?

Is there a way to turn off the mining aspect on an original Apollo btc miner and just use it as a node?

I have a FullNode version of Apollo BTC1 (the latest Apollo OS 2.0.5), which suddenly broke recently. The specific symptoms are as follows:
1. The front panel flashes quickly and then stays on after powering on.
2. Unable to find IP on router
3. The display does not light up either

I tried connecting it to another normal FullNode machine, but the host doesn't recognize this machine either (using a microUSB connection)

I can't find this FullNode machine under macos and windows, use microUSB to connect

The other three FullNode Apollo BTC1 machines were normal, but the broken machine also broke suddenly without any warning.

[GraphQL error] is a known bug and will be fixed in the next release which is due very soon! It is a GUI bug and does not effect the operation of the Apollo

hello all sos plz!

can anyone have be some guidance currently running the apollo II solo mining on v2.0.5 I am getting this ( [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2179756302 ) flickering on/off the node is on but the solo mine stays off as i intend to turn it on.

I have mine set at 50 and it doesn't impact CPU or network performance at all.

I think the default is 30 which is a nice number