Ok new issue. But this seems to be related to the cp210x. In ubuntu 18.04 LTS linux distro, I have successfully got the moonlander mining Verge coin. The problem I am having is when I connect a Gekkoscience newpac miner to the system. I am not Linux tech savy enough to correct the issue. What happens is that when moonlander is running it'll start erroring out with input/output errors. I can't have both of them running at the same time. Even with Moonlander connected to a USB2.0 port and running the newpac on a USB 3.0 port.
When I run the following command: dmesg | grep ttyUSB it appears the cp210x will disconnect from ttyusb0 (moonlander is on) and connect to ttyusb1 (gekko newpac is on) and alternate between the two causing bfgminer to fail on the moonlander.
Any ideas on how to keep it from alternating like this and have both running together? I tested on my windows machine and both are able to work together without issue. Ubuntu on the other hand no so. When I ran the below command 'before' launching the mining software, it showed correctly moonlander device on usb0 and the gekko on usb1. 'After' running the miner, the below is what happens and I believe is the reason for the issue. Soon I will be attaching an Arduino Uno for some electronic projects I am working on and believe this will possibly create issues with it as well. Help is appreciated. Just don't know how to correct. Thanks
You need to figure out which tty each is attached too, and make sure you specify in bfgminer/cgminer to not auto-scan (ie use the -S /dev/ttyUSB0) flag. My driver is pretty good at filtering out the right ASIC before injecting commands to the chip, but im pretty sure gekkosciences driver starts sending commands as soon as it finds a UART chip, which is why it screws up the moonlanders. Make sure auto-scan is not enabled will keep each driver from trying to send commands to the wrong usb miner. |
|
|
|
I have two and set them both up last night. I setup the first one and added to my wireless. Then I powered on and setup the second one and it gave me a struggle after I added to wireless. It seemed to me they stepped on each other because the first one quit mining. But its possible I screwed up because I was on NyQuil so I switched one back to wired and both hashing away. I'd like to change the dns name from local to local2 or something just to keep them straight on my network. How can I do that?
BTW, left them both set to default and hashing away at about 102HM. And I can't believe how easy the mining interface is to configure.
Best way to set up multiple right now is to just power one on a time, find its IP address set it up, power it down, power up the second one and repeat, then power on the first. Either way the wifi is buggy right now, but there is no reason why they both should not work. Can you shoot me a screen shot of the Network info side panel for both machines when you get the chance? I am having a very hard time connecting my 2nd Apollo onto my wireless network. I am using a Sprint Wireless HotSpot which will allow up to 14 devices at any given time. When I connect with wireless in the console, it still shows the connection with the enternet port as being connected on a separate IP address. Is there some settings I have to save once it has a wireless connection? After you have successfully configured wifi on the dashboard and its connected, you need to reboot the machine, and pull the ethernet plug before it reboots. If you have both the wifi and ethernet connected it will stay on ethernet (or not work at all depending on your router). |
|
|
|
I'm thinking droping voltage, step by step, to find a minimum my miner can run at 589 MHz.
What problems will I encounter ?
Can I recover on my own?
At some point when lowering the voltage, the hardware error rate will start increasing but nothing else should happen. Just in case you manage to still trip some undocumented failsafe and the unit ends up in a reboot loop due to the test settings having been saved, you'll still always have the option to re-flash the sd card and return back to the default settings. Note that it may take some minutes for the hardware error rate to stabilize so don't be in too much hurry when making voltage changes. Yea you can never cause any damage under-volting...youll just see HW errors spike, or the miner just wont startup at all. The software is actually designed so you can do this live...ie start the miner in custom mode, then slowly increase or decrease the voltage while its mining...you can just lower the voltage and keep checking the dashboard HW errors...as long as you dont see the count go up faster than a few a minute your good. |
|
|
|
I'm seeing something really weird with my second Apollo (one of the final ones in Batch 1)
In eco mode, the Apollo sees roughly 2.2% to 3.0% hardware errors; but in balanced mode, 0.8% to 1.1%. Is this likely just silicon lottery, meaning this particular apollo needs more voltage? If so, what are the settings for each of the pre-baked modes?
Yea ECO mode is slightly more aggressive with voltage than the other modes, stock ECO values are 600MHz and 750mV...you should be fine if you bump it up to 775. Were the stock ECO values changed at some point? Looking from the MCU side file /var/local/apollo/hwmon/reg_voltage with the current firmware (in ECO mode), I can see it output 28, which according to const voltageStep = parseInt((settings.voltage - 644) / 4.15) (from /opt/apolloapi/src/configurator.js) results in 760 mV. Yes hwmon controls default values which were undervolted slightly more in the latest firmware (AFAIR without looking at the source i think the step voltage was 26 which translates to around 750mv). |
|
|
|
I'm seeing something really weird with my second Apollo (one of the final ones in Batch 1)
In eco mode, the Apollo sees roughly 2.2% to 3.0% hardware errors; but in balanced mode, 0.8% to 1.1%. Is this likely just silicon lottery, meaning this particular apollo needs more voltage? If so, what are the settings for each of the pre-baked modes?
Yea ECO mode is slightly more aggressive with voltage than the other modes, stock ECO values are 600MHz and 750mV...you should be fine if you bump it up to 775. |
|
|
|
Hey everyone,
The fan on one of my moonlanders gave out a few days ago. I noticed that a few people have posted links to replacement fans earlier on this thread. I noticed however that these replacement fans do not come with a connector. That is, they come with bare wires on them. Would you happen to know where I can get the appropriate connector or where I can find a replacement fan with the correct connector?
Thanks!
I know this post is old, but I still happen to have 3 spare Moonlander fans with a connector, ready to go, never used (because Moonlanders were DOA and I settled them with $, without sending them back). If anyone is interested, I can send them out as a Large Letter envelope, shipping wouldn't be that expensive. I am in Europe. PM me if you are interested  Please use the appropriate forum for selling stuff and dont junk up this thread anymore than it already is. |
|
|
|
hmm. so far didnt get better. Got a hub with extra power but only 0.5A adapter. USB3 are 1 A arent they?  Yea .5A you won't be able to run them even at base frequency. You need at least 2A per port. |
|
|
|
I once changed the Mhz settings just a liitle bit higher and than my 2 moonlander dont work any more.   are they dead? No your USB ports/hub can not provide enough power. You will probably need a powered hub if you are running them straight off your PC ports with higher hash rates. |
|
|
|
 Just gonna leave this here...  No, they'll not pay for themselves for a year or two (though I suspect that during the bull run I feel in my bones, the coins they mined will be worth double what I paid for these gems), but it's always nice to see that they can catch blocks against the biggest mining farms anywhere. Kudos to you jstef! Nice...always good to see that the hardware CAN find real blocks haha Actually found a block as well with one of my prototypes...maybe the blockchain gods are giving underdog hardware like the Apollo some extra luck...if someone has found a a solo block that would be super cool definitely do share. |
|
|
|
Please take time to read the FAQ on the first page if your having issues, 90% of issues are addressed and your answer is there. Your anti-virus is deleting bfgminer.exe when you extracting the download, you need to put in an exception for the folder/program. |
|
|
|
I've had my Apollo for about 3 months now and love it. I started with Eco mode, then moved to Balanced mode and finally to Turbo mode. Temps were all good in the three modes except in Turbo, the miner temp raises to over 70c. I was cautious when I first started with Turbo and watched temps closely. After I felt confident things were good, I've left it mining numerous sites using Turbo. I'm currently mining at ProHashing and noticed that my hash rate is considerably less than 140MH/s. In fact I was sometimes averaging 115MH's on Turbo over a 2 hour span. Yesterday I dropped back to Balanced mode. I've watched the hash rate on ProHashing and the hash rate is better than when I use Turbo. In fact, most of the time they calculate it between 130 and 135 MH/s with a few jumps up to 140MH. I'm not sure why Balanced works better than Turbo on that site but I'm happy with the results and I'm very happy with the Apollo.
Thanks jstefanop for your fine work in building the futurebit miners. I'm looking forward to the next batch of Apollos.
Do you have a high error rate under Turbo? You should be averaging around 135 on turbo and 125 on balanced. If your error% is really high you might need to turn up the voltage manually under turbo. |
|
|
|
So the second apollo is on the wish list but I was wondering how do I hook up the second one up to the same PSU ? Do I use a Y split ? Will that be safe cause of the gauge ?? Shout out to all LTC holders looks like we are on the way to making some good money with these miners !!!!! Your PSU would need to have multiple PCIE connectors, Y splitters is definitely not safe. You can get away with running each one with one PCIE cable as long as your not running past Balanced mode, but again it depends on PSU and how well they are made and wire gauge they use. I have 2 on my current PSU (link below) https://www.xilence.net/en/power-supplies/24Is there like a breakout cable to maybe get another 2 6pin from the 20pin connector ? You could probably find an 8Pin CPU to 6Pin PCIE connector adapter that would work. |
|
|
|
So the second apollo is on the wish list but I was wondering how do I hook up the second one up to the same PSU ? Do I use a Y split ? Will that be safe cause of the gauge ?? Shout out to all LTC holders looks like we are on the way to making some good money with these miners !!!!! Your PSU would need to have multiple PCIE connectors, Y splitters is definitely not safe. You can get away with running each one with one PCIE cable as long as your not running past Balanced mode, but again it depends on PSU and how well they are made and wire gauge they use. |
|
|
|
So how many of Apollos are left to buy?
Pretty sure batch 1 is sold out now, which you can see confirmed on futurebit.io's shop's product list. Yea it’s sold out, bitshopper.de in Europe might have a few units left. I’ll be starting batch 2 next month. Batch 2 will have those nice little power supplys with them? :-D Yes, it will be an optional add-on. |
|
|
|
Perhaps a novice question, but in the past couple of weeks my Apollos haven't been producing the same 24 hours rewards at litecoinpool - it's dropped. Please tell me it's not because of anything with the Apollos. The only change I've noticed is the difficulty has gone up from 8,917,884 to 10,360,375. Am I right to conclude "difficulty" = more work required of the Apollos and therefore less payout in a given 24 hour period?
Hey - like I said, I'm a novice but confirmation would be nice.
Yes more miners have joined the network, therefore difficulty has gone up, and your rewards go down the same percentage if your hash-rate stays the same. Nothing wrong with your Apollos, this is how most block chains are designed to run. |
|
|
|
So how many of Apollos are left to buy?
Pretty sure batch 1 is sold out now, which you can see confirmed on futurebit.io's shop's product list. Yea it’s sold out, bitshopper.de in Europe might have a few units left. I’ll be starting batch 2 next month. |
|
|
|
- A super ECO mode which further undervolts and underclocks the Apollos for folks with high electricity costs and in readiness for the Litecoin halving in August to squeeze the efficiency. Although I hope the price doubles to compensate.
You can always experiment with this on your own. Just go to custom settings and start lowering frequency/voltage. You can't "break" anything when undervolting/underclocking. The ASIC chips will just produce a lot of HW errors if you undervolt too far. Things only get dangerous when you start over-volting. FYI Eco mode defaults are ~740mV voltage and 600MHZ clocks. So there is still plenty of headroom to go even more efficient. I think the best i have gotten is ~ .9 W/MH at around 80-90MH |
|
|
|
Yes I am running v.2 but it still only staying up for 5 mins and then disconnects
Ok shoot me a PM or reply to your order email with issue...I think you already emailed though. |
|
|
|
Jo guys !
So I'm running 1 apollo in turbo mode from a PSU and i'm getting 235W. I'm wondering if I would put a second apollo on the same PSU would my wattage double ? Of would it just add +-130-140 W from de extra apollo.
Some people here are running 2 whats your wattage from the wall guys ?
Yes it would double if your running the second in turbo as well. What PSU are you using turbo should not be more than 200-210 watts at the wall. |
|
|
|
|
Show Posts
