Topic: Official FutureBit Apollo LTC Image and Support thread - page 5. (Read 49873 times)

Hello, I've had my FutureBit running consistently for almost a year now with pretty much no issues, but recently I've had some disruptions to my internet which has caused the miner to shut down  "red light " showing , since this event I've had unusual HW errors, sometimes really high even in ECO mode, and I am having a very difficult time connecting to the Apollo dashboard on my mobile or laptop computer ,  on my Net Analyzer app I show the future bit IP address listed, but when I pull up my routers IP address it does not list.  Currently my miner is mining but I can not access on dashboard or reconnect the full node , ive seen mention of reimaging the SD card, im not quite sure how to do this .  Any suggestions or support would be appreciated.  Fyi, I also have an Antminer L3+ that is running with no issues, but I would really like to get this bad boy up and fully functional again. 

Is it possible to enable RPC on a full node? I'm writing a program to monitor my balances and I'm wanting to call the JSON RPC to get the balance for a public address. Since I already have a full node apollo running, I'd like to use that instead of setting up a 2nd node and would definitely be beneficial on the BTC apollo that I have on order so I'm not running 2 BTC nodes as well.

Multipools cause issues based on how they send work data. For nicehash try putting #xnsub at the end of the url, and make sure ALL failover and donation pools are disabled.

Apologies 100% if this has been asked and answered... I did dig around through quite a few of these pages before posting.

Is there an issue with these units and Nicehash? I've tried unsuccessfully all day today to switch the pool to Nicehash, and it immediately goes to an inactive status. I can put it on any other pool and it immediately begins hashing (Sigmapool, Litecoinpool, etc.) with no issues.

Settings:

Server:  stratum+tcp://scrypt.usa-east.nicehash.com:3333

Worker: 3D***********kp.APOLLO

Pass:  x

Thanks in advance...

Also does anyone know of any suitable fan replacements? My batch 1 unit is perfectly fine at the moment just wondering if there are any better quieter options out there.

If it's the MCU board you are missing, it's the 512MB version of Orange PI Zero (not "plus", not "2") with straight pins soldered in the expansion port.

That front led is software controlled. It showing no activity suggests that the system doesn't boot at all or not correctly at least. In that situations your options are somewhat limited:

Option 1) Re-flash the sd card. In many cases that appears to help.

Option 2) Flash another sd card. The current one may be dead.

Option 3) The non-trivial option: Get a USB to TTL adapter and attach it to the uart of the mcu board. That will allow you to see what is happening during system boot and possibly give a clue what's wrong.

You can only use two or more pools, if they are both mining the same coin. If you use multipools, use only one (no failover). This is a bfgminer known problem.

Hi jstefanop, I have a gen 1 apollo and I want to be able to run a node on it. I was wondering if you are going to have the upgrade kits in stock soon. TIA Best J

@jstefanop

Hey, I don't know if this is an issue with the Apollo firmware or the way that Prohashing issues work and switches coins, but figured I'd give you a heads up in case you or anyone else had ideas on how to solve.

TL;DR: When using Prohashing and having an active and failover pool enabled in my Apollo dash, I get high error rate, reducing hashing, and hash power going to active and failover pools simultaneously.

This is what I posted on their support forums, just speculating:

I used the configurator to get the default options for my Futurebit Apollo scrypt miner and pointed it at the pool, I am noticing that it takes a long time to start up, skipping over the first coin in fact and going directly to LTC.

After a short period the hardware error rate skyrockets up to 30% and the hashrate declines dramatically. The error rate seems to slowly stabilize around 14-15%, with my hashrate ultimately being stuck around 80-90. I am using it in Eco mode, which should provide roughly at least 100 Mh/s.

Worth nothing, I don't experience this issue with others pools, such as litecoinpool. I wouldn't mind pointing my Scrypt miner at Prohashing, but this hit to hashrate is untenable and I don't want to inadvertently crash my miner, any possible solutions?

Edit: I don't know if this is the root problem or not. It looks like while having a failover pool set, perhaps because of the delay of initially getting work, the miner is considering Prohashing as simultaneously being in an active and fail state and sending some hash power to the failover pool. Perhaps this is causing a problem with the difficulty calculation from Prohashing and causing the error rate when switching between currently mined coins? Disabling the backup pool altogether, which is non-ideal, seems to resolve the HW error and reduced hashing state.

I purchased 10gh of l3+ miners and the op gave free firmware that lowers the watts used on L3+ gear saving me a lot of watts since 2018.
...
at jstefanop  thank you 🙏

One of my two apollo batch 1 after being shut down, it didn't work anymore. When turning it on, only the fan runs for 1-2 s and stops. The front led has no activity and the network card leds appear to have normal activity. I already cleaned it and tried to find any signs of damage but I can't find any.
What else can I try?

I read this if it helps

"When errors happen in the Jaxx Liberty wallet you can click on the red bar at the bottom and you get a pop-up with possible causes and solutions."

If I were you I would swipe the Jaxx wallet into ios Coinomi and Desktop version.