I format it one more time and burn it again and it is starting now  Thank you so much !! I've got a Samsung 32 GB microSD HC 1 and I burned it this way : sudo dd if=apollo_final.img of=/dev/rdisk2s1 bs=1m Guys just use etcher if you don't know how to use DD properly. For example the above is incorrect, your imaging to the SD cards partition instead of to the root of the sdcard (not exactly sure how you got it to work with it burned this way). Proper dd command would be something like this sudo dd if=apollo_final.img of=/dev/rdisk2 bs=1m |
|
|
|
Shower thought for the Apollo: what's stopping me from running a moonlander on the Apollo?
It has a free USB port, miner software and it has a nice ring to it to equip the Apollo pod with a Moonlander?
You could! Armv6 Binaries on git should work fine on the Apollo controller, and the board has a 3 Amp rated 5v regulator so should be able to easily power one Moonlander. Apollo service module fully docked with the moonlander  How about a usb hub with multiple moonlanders? Yea the Apollo controller is essentially a raspberry pie, so anything you can do on a pi you can do on this controller (minus the GPIO pins which are obviously all used to control the hashboard). |
|
|
|
Shower thought for the Apollo: what's stopping me from running a moonlander on the Apollo?
It has a free USB port, miner software and it has a nice ring to it to equip the Apollo pod with a Moonlander?
You could! Armv6 Binaries on git should work fine on the Apollo controller, and the board has a 3 Amp rated 5v regulator so should be able to easily power one Moonlander. Apollo service module fully docked with the moonlander |
|
|
|
Thermal cutoff is set at 84C.
Thanks. Is thermal cutoff software controlled? So in theory, in future update, thermal cutoff can stop mining, spin the fans, and when temperature is back to normal, mining is resumed? Or it's hardware based and unit just die and I need to power cycle it to make it work again? No, thermal cutoffs are last line of defense, everything is shutdown if those are reached....that usually means something is wrong so its not a good idea to start it up again. For example someone might have overvoltated/overclocked and set fan to 10% by mistake...or worse the fan fails or is not working properly....this will trigger a thermal cutoff eventually and you don't want to be stuck in a loop restarting, overheating and shutting down the miner every 10 min. There is software hardware control, and in case the MCU fails there is a backup onboard cutoff which the regulator monitors to keep the thing from burning up. |
|
|
|
Definitely agree with that. And for some reason it is better in Wattage, I don't have below 130W when Fan auto displaying 630 RPM:
- Fan auto ≈ 630-2040 RPM -> 130-133W ≈ 66°
- Fan 10% ≈ 1425 RPM -> 129W ≈ 56°
Same for me with fan at 15% i save 30W on 3 units and temp is between 35-40° (with outside temp at 2°) Wow dude that's awesome!  I have mine running at 15% as well, temps 52-54° C, ambient is around 13° C Yea its a trade off between "quietness" and "efficiency". The cooler an ASIC chip runs the more efficient it is due to thermal effects on the silicon/transistors. For stock settings I chose being quiet over absolute efficiency, since most casual users running these on their desks wont care about an extra 10-20 watts. Btw you don't have to really worry about "high" temps on these ASICS, they are rated for 90C continuous operation (this translates to about 80C pcb temp which is what is reported by the miner). What is thermal cut-out temperature? When my miner stopped this morning, it was really hot to touch, I bet fan was spinning at 5% or less for minutes and minutes without knowing it's too hot, it overheat and shut down. Unless there is different reason but I don't know what. Thermal cutoff is set at 84C. |
|
|
|
Definitely agree with that. And for some reason it is better in Wattage, I don't have below 130W when Fan auto displaying 630 RPM:
- Fan auto ≈ 630-2040 RPM -> 130-133W ≈ 66°
- Fan 10% ≈ 1425 RPM -> 129W ≈ 56°
Same for me with fan at 15% i save 30W on 3 units and temp is between 35-40° (with outside temp at 2°) Wow dude that's awesome! I have mine running at 15% as well, temps 52-54° C, ambient is around 13° C Yea its a trade off between "quietness" and "efficiency". The cooler an ASIC chip runs the more efficient it is due to thermal effects on the silicon/transistors. For stock settings I chose being quiet over absolute efficiency, since most casual users running these on their desks wont care about an extra 10-20 watts. Btw you don't have to really worry about "high" temps on these ASICS, they are rated for 90C continuous operation (this translates to about 80C pcb temp which is what is reported by the miner). |
|
|
|
Hello jstefanop, quick question:
I just had situation with one pool, where I was temp-banned because I generated lots of rejected shares (it was MiningRentals, rental order gave me wrong settings). My Apollo was disconnected, and it started mining on backup pool. But after some time, it did not returned to main pool, despite temp-ban being lifted and I could just mine there easily.
So, question is, At default settings, will bfgminer continuously try to reconnect to main pool? If not, how I can change that in bfgminer.conf?
That should be the default behavior. Could be something with the ban, since a new authorization would require a bfgminer restart. |
|
|
|
|
Wired/Wireless have different MACs, they currently wont both work together though...if you have ethernet plugged in wireless wont work(so after wireless setup you should reboot then remove ethernet).
|
|
|
|
Tried a be quiet! Pure Power 11 CM 600W PSU but so far no luck getting the Apollo going.
Connected pins so it can start and PSU fan starts spinning. LAN-port leds turn on (orange, green) and the Apollo fan starts with a few spins but stops immediately, no front led light.
It will do this every time when PSU turns on so seems like some kind of protection from the PSU that shut its off. Maybe somebody has a better idea or experience?
With the Apollo attached and pins connected should normally be enough?
If nothing works I might just get one of the PSUs that seemed to work for others.
Do the LAN port LEDs flash a few times? If they come on and stay on that means its not booting from SD card (when it boots properly the LAN LEDs will flash a few times). If they don't flash that means either your using an incompatible SD card, or something went wrong with your SD card image download/flash. Ok, leds do stay on but don't blink. I'll try writing sd cards again without using dd. Tried both a 32 Gb and 64 Gb sandisk extreme plus, but both created in the same way with dd so makes sense to try different way or even using cheaper different card. Thanks, I'll report back. Yea just use etcher it’s easy and gets the job done. You might be writing to a partition with dd and not the whole disk. |
|
|
|
Quick check-in from a mining newbie. From SD card flash to mining steadily took me about 25 minutes. Running smoothly and averaging the expected 101 Mh/s for about 15 hours now on litecoinpool. Lights flashing a nice Christmas-y red and green. Set the fan to 15% which seems to cool it a lot better than the variable speed, and keeps it at a tolerable noise level for the den. Only issue so far has been getting the HDMI cable to clip into the Apollo. Happy to be a part of the home mining community!! There is no hdmi port on the Apollo... |
|
|
|
Bug report: https://imgur.com/a/6szEf9oArrows up and down don't work (tested on Mozilla Firefox and Google Chrome). I can't change priorities in pool order. Also, it's not possible to EDIT entries. These fields here are just greyed out display fields, not text entry fields. If I want to edit the main pool, for example, I need to delete all of them and enter them all again in the correct order. I believe something is messed up between UI and backend, because if you delete one pool, the backend often deletes another pool (not the one you clicked to delete). Might be that sometimes there are entries in the database with the same number in the 'index' field. I also dislike that you can't edit them (nor can't copy-paste the entries), not even directly in the apollo itself - the only way I found is mounting the apollo disk via sshfs and running sqliteman against the db in /opt/apolloapi/. This was for me necessary since at some point after some trying to shuffle, re-add, delete from the UI I suddenly got litecoinpool and a multipool running in parallel which made the apollo freak-out pretty much. On the positive side I finally managed to run them stable against a multipool, since 24hrs stable at 100MHs with ~1.6-1.9% errors. If you want to mine on profit switching pools / multipools, make sure you do not have a backup pool configured (unlike cgminer, bfgminer seemingly requires primary and failover pool to run on the same coin/network). For mine I also set the fans to 45% resulting in 56-58°C. Worth mentioning is also the fact that these are the first miners in my hands that are IPv6 capable, according to bfgminer release notes this should allow the apollo to connect to pools via IPv6 and for later releases to allow full nodes to run dual-stack which gives much more connections to the coind. However the Wifi doesn't work for me (tested just for fun, don't need it), I have 2 wireless networks (WPA2-PSK only) that the apollos should see but only saw them once upon "scan" and that was after the first boot of the image, since then I don't see them anymore on both apollos (and not even the dozen or so neighbouring WiFis that my notebook sees from the same location). Yea most of this stuff is on my bug list / to-do. Wifi is very hit or miss with the current driver for the wifi chip...were trying to get a stable driver going from the vendor. My test units work fine in a simple b/g network at home...but in my office with dozens of networks/mixed mode stations etc the wifi driver chokes and crashes all the time. |
|
|
|
Tried a be quiet! Pure Power 11 CM 600W PSU but so far no luck getting the Apollo going.
Connected pins so it can start and PSU fan starts spinning. LAN-port leds turn on (orange, green) and the Apollo fan starts with a few spins but stops immediately, no front led light.
It will do this every time when PSU turns on so seems like some kind of protection from the PSU that shut its off. Maybe somebody has a better idea or experience?
With the Apollo attached and pins connected should normally be enough?
If nothing works I might just get one of the PSUs that seemed to work for others.
Do the LAN port LEDs flash a few times? If they come on and stay on that means its not booting from SD card (when it boots properly the LAN LEDs will flash a few times). If they don't flash that means either your using an incompatible SD card, or something went wrong with your SD card image download/flash. |
|
|
|
Moonlander is really designed for people to run a few of these to get started with mining. If your going to get 34, you might as well pick up a few Apollos, still have a few in stock and will be shipping next week after holiday. The Apollo is just as quiet as the Moonlander (and probably quieter if your going to run 34 together), and it will definitely be less of a hassle to run 2-3 Apollos instead of dozens of Moonlanders (and you hashrate will be higher with less cost). Check it out here: https://shop.futurebit.io/products/apollo-ltc-pod-asic-miner-for-scrypt-algorithm-cryptocurrencies |
|
|
|
I've been unable to get the apollo to boot. I ran a checksum on the image I downloaded and it doesn't match. I've re-downloaded twice and neither matches. Anyone have advice? I'm using a windows 10 pc and downloaded using both chrome and edge.
If it’s flashing yellow it’s working fine. What are you using to run the checksum? Yellow flashing means it’s booting and not getting a network connection. You have it plugged in via Ethernet and ran an ip finder on your network? Thanks for the response. I ran the checksum with command prompt, yes it's plugged in via Ethernet but it's not being assigned an IP by my network. Anything else I plug into the ethernet is immediately assigned an IP. Did you hash check the IMG or the ZIP of the IMG? I figured out what I was doing wrong with checksum, I was using MD5 instead of SHA256. The checksum on the IMG matches. I've tried to create an ISO on the micro SD using Etcher but it doesn't seem to be working. I've tried on a sandisk 8gb and a Kingston 16gb with no luck. There doesn't seem to be any settings in Etcher to change. I read that I have to make sure the image is on the whole disk not sure how to do that. Did you figure this out yet? Its definitely something with your network...double check your router/firewall settings. You don't need to change anything on etcher other than select your SD card and the .img file. If the flashing yellow LED is coming up then the device and SD card is working right, its just not getting an internet connection from your router. |
|
|
|
hmmm...  having some troubles with my 2 miners. These are pool connection issues. Interface currently does not have a nice way to display connection errors since the interface requires bfgminer to at least connect to one pool before it starts sending data to the dashboard. Thats why your seeing the miner offline screens. High hardware errors is a byproduct of a pool going offline then coming back online (next image release will handle this better and shutdown the miner properly and wait for a connection), since it just spits back thousands of shares to the pool on reconnect and they all get rejected. Ill start checking mutipool with my devices and see if I can replicate....if you see the same issue, ssh into the device and do "sudo screen -dr miner" to bring up bdgminer and take a screenshot of it. |
|
|
|
I've been unable to get the apollo to boot. I ran a checksum on the image I downloaded and it doesn't match. I've re-downloaded twice and neither matches. Anyone have advice? I'm using a windows 10 pc and downloaded using both chrome and edge.
If it’s flashing yellow it’s working fine. What are you using to run the checksum? Yellow flashing means it’s booting and not getting a network connection. You have it plugged in via Ethernet and ran an ip finder on your network? |
|
|
|
|
ASIC development on SHA256 has been going on since 2011, with about 4-5 process node updates and 2-3 generation updates in between nodes.
Development for other algos is no older than ~2 years, and these all probably started at the very cheap 90nm node, so its very easy to get a 6x gain going from 90-45nm.
Its a little harder for SHA256 to see huge gains going from 16nm to 10 or 7. Bitcoin ASICs have pretty much caught up with the latest node tech, so there wont be any more crazy gains in the future.
|
|
|
|
Yea that’s why I didn’t really want to release a psu since regulation+ testing etc is rediculouse...plus there is the chance of electrocuting someone if don’t build it right. Think we got this one down though and it works well....plus I think it’s one of the most efficient and compact power bricks in the sub 200 watt range in the industry to boot lol. And no it’s just one of my prototype units I use for testing |
|
|
|
Was literally about to post the same thing. Yea if you don’t want to mess with wires and pins this is the safest bet. One here is a prime version of the same thing:CRJ 24-Pin ATX Power Supply Jumper Bridge Tool https://www.amazon.com/dp/B01N8Q0TOE/Really need to get the standalone psu out...think it’s the biggest barrier of entry so far for new users. Check out the working prototype below ~200 watts max @ 92% effeciency (near platinum status) 80-250V input -> 13v @16A output  |
|
|
|
|
Show Posts
