Quote from: jarvisparvis on June 18, 2020, 02:22:00 PM

Ive had my batch 1 since day 1 and has always been a sturdy little machine with relatively few glitches. Since upgrading the MCU to enable node support ive had problems.
I have a feeling its because the MCU runs hot and causes problems i.e network disconnects and then the machine fails. It seems to happen when the MCU hits 45 degrees at about 1hour even in ECO.

Tried with out node and still no luck, downgraded to image 1.29 and still the same. Finally replaced the original MCU and every things fine again obviously with out node support though.

So now running back on 1.29 image with original batch 1 MCU and its running sweet even in turbo mode the MCU bearly reaches 27 degrees. Compared to the Masternode version which runs upto 45 degrees and then glitches the machine.

Is this something software could fix i.e change the parameters to let the MCU run hotter if thats what is does, or make it run cooler.

Thanks sticking to no maternode batch 1 setup until further advice.

Any device running additional background / foreground services requires additional resources.

Apollo is a small device with an absolute min amount power (RAM, CPU etc). So running it as node pushes it even further - plus higher temp.

I ran mine with node for a while (batch 2) and noticed was getting more invalid shares than before! It was also running a little hotter. So, I stopped it.

Certainly if it was making some amount of respectable LTC, I would take one for the team of giant LTC miners for sure!!

Those who mine like 50+ LTC / day, they should purchase as many Apollo as Futurebit can produce and run their own nodes to help secure the LTC world!