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

It is 2020, another capacitor plague would not surprise anyone in the slightest.

Woh never seen that happen. Thats an aluminum cap that looks like it was defective. Shoot me a DM well take care of it.

Bump

No, the hashing hardware is on the PCB itself, not on the controller. It would run at the same rate and dont need more power than a small micro controller to control the hashboard (it would run on the same rate on an arduino or your gaming PC). The only thing that would run faster on your PC is the full node, but then you would need to run your PC 24/7, which would probably consume more power than the whole Apollo while mining AND running a full node, so defeats the purpose.

Sure not. Scrypt mininig is ASIC.

I noticed in the right sidebar under operating system, it lists Ubuntu.  Is it possible to run the Apollo firmware on a PC either directly or by emulation?  Maybe my PC could hash faster than the Apollo?

I am still not able to login remotely - any advice?

Is it port 9333 for internal and external?  TCP?

@jstefanop

My Apollo was shutting down on its own and on visual inspection I found this capacitor(?) hanging on by a thread, just touching it took it off the rest of the way with a sad crunch. :/

Any ideas on what happened or how I can try and get it fixed?

https://ibb.co/JHCVKKw

Update: I opened the case to take a look and it is identified as slot C268 on the board. Idk if you are offering repairs on these, if I can get the specs or a link to purchase a replacement I can try and solder a new part back in.

I love my 2 apollos - might get more once I have more deskspace lol - I have 5 miners on it currently - 2 apollos - 2 r606's and 1 hs1 plus

How did you not mine 1 LTC over 9 months? You should have been averaging about .2 LTC a month over the past year. Either way you backed out at the bottom unfortunately. The whole point of our device is that 100 watts won't burn a hole in your pocket, so just should have kept running it and forgotten about it and came back 2 years from now

Either way thanks for supporting us and glad we were able to bring another person into the crypto fold through our devices. I hope you at least kept your LTC and dont sell it!

Same experience with 5 mooners and 3 Apollos. Dumped LTC mining back in May and redirected to DigiByte. Although not the same value at least I hit about a block a month since May and now have over 3,400 DigiBytes. I also modified the software for the moons (on Linux) which seems to have pepped them up a bit.

9+ month, almost 7*24 running 8 Moonlander 2 and 1 Apollo 2nd gen and still not 1 well-deserved full LTC!

LTC price keeps going down down down then up a little and again down down down.

Lots of noise and smoke and no action from LTC developers.

So - I officially shut them all and after almost a month hard work got rid of them at less than 1/2 price!! Not too many fans, I guess.

Considering electricity at around $.10 and difficulty mining, I should’ve known better.

Interesting fact: at litecoinpool I used to be at the very bottom like faster than 16% - recently noticed I got promoted to faster than 26%. A quick look at stats, the number of users were about 3500 something - compare to 5700+.

Good luck to you all and thanks to Futurebit developers, I had fun learning.

is it possible to ad some sort of timer. So at night the Power Setting is Eco and Turbo on day.
The Power at daytime is for free. so i us Custom Setting 143Mh and around 70°C, 380W.

Thanks a lot ....
THX Dominik

1) Cool TIL

2) Node is sync'd, Ill play around with it some more tonight to see if having the node running or not impacts the wifi issue

3) I was not shutting down between wifi setup and unplugging Ethernet, is that listed in the support material anywhere?

Is there any kind of logging being generated I can dig through? Looking back at some charts looks like my miner shut down from 8pm and recovered this morning at 9am running on eco.

Few things here:

1) Windows/Mac will always show disk image corrupted after you flash since its flashing a linux system it cant understand

2) Its normal for dashboard to lock up when you first boot when the node is syncing, I could remain this way for hours until the node has finished syncing since the sync takes up almost all CPU cycles and RAM on the controller

3) Setup your miner/wifi first by booting WITHOUT node USB drive. Trying to setup pools/wifi etc while the node is syncing in the background will probably cause the corruption issues you are seeing. Remember to setup wifi, shutdown the miner, then unplug ethernet and reboot. Setting up wifi then unplugging ethernet won't connect you to wifi until you reboot.

Hey All but mostly jstefanop,

Ive had my Batch 2 for a while now and upgraded to full node a couple months back.

For the past week or two I have experienced repeated crashes where my apollo locks up and has to be powered-off and rebooted.

Node seems to recover alright even though Im not following the shutdown procedure listed in this thread but the whole thing locks up again after an hour or two.

This morning I tried to re-flash my SD but keep getting Windows 10 alerts that the disc image file is corrupted. Ive started from a fresh download 2 or 3 times now.

I continued regardless and flashed the SD with Etcher.io, verify I have removed the USB for full node, boot up my miner, setup, and go.

The Miner will start hashing as verified on litecoin.org but the miner dashboard is failing to load with Error "SyntaxError: Unexpected token in JSON at position 1497"

Node is up and running and I can access the node dashboard just fine.

Please let me know if I am doing something wrong or if there is anymore information I can provide.

Update 202009111156:
Was able to get past the broken dashboard by flashing another microSD I had laying around. Miner seems to be working as expected, node is working as expected.

Wifi is out though, and looks like unplugging Ethernet and switching to wifi has caused the same crash condition I started with and killed the dashboard with the ""SyntaxError: Unexpected token in JSON at position 1464"
code

Update 202009111439:
Confirmed switching to wifi appears to somehow crash the miner, break the dashboard, and lock up the whole unit. Re-flash and sticking to Ethernet seems to be the temporary fix

The post below saved my bacon - Testimony time.....

I retired the other brands ASIC miners and my GPU racks months ago, kept some ML2s chirping away,  and recently happened up the Apollo.....   Sure!    Why not?

The order was "smooth", the packaging sound, the initial bench start up perhaps too easy (?!?!?!), the location into a heat flow friendly spot in the office (very quiet and aesthetically "cool" to look at), I was missing out on chances to learn....    So......   

Proceeded to make on operator error trying to connect to the pool to a point where I "finally" get to learn something - How to download and flash an image onto an SD card.....  Never had done this before and with the notes on this thread, this old dog learned a new trick!    Now I've a backup card and wondering what else I've laying around that I can go flash....

Connecting to the pool with this second worker took some relearning but that's another thread.

Thanks for hearing my testimony, thumbs up on Apollo, thanks to all for leaving instructions and tips on this thread.

Cheers!

Thx for the advice.
yeah, two full nodes are not meaningful, as I experienced too late.
Anyhow, I try to NAT it manually.

Cheers
WB

This has been already answered a few pages ago. Please search...

OK, more easy for you https://bitcointalksearch.org/topic/m.54298707 https://bitcointalksearch.org/topic/m.54301554

To have two or more full litecoin nodes using same IP it is not a great idea. Too much trouble, few benefits. Better one node only with one IP.