Topic: Official FutureBit Moonlander 2 Driver and Support Thread - page 53. (Read 71661 times)

Hi

I have a ML2-BFGMiner-RPi3b setup which gives me about 2-3Mh/s stock.

The system works well until about 3-4 hours of hashing then the red LED stops flashing and no new accepted shares on the pool.

The pool is still active and the jobs are being received but hash rate falls to zero.

I have tried a couple fo pools and different coins same thing.

I can then software restart the miner and the ML2 starts hashing away again. No hardware reset required.

Is there some setting i need to implement to allow the system to sit more stable? or a way to ether dump the memory or restart miner if it looses the red LED for over a certain time?

any help appreciated

It's on 625 now, but it seems it doesn't matter much. I used to get 3.2MH on 600 and stock settings, but hey better than nothing
I'm mainly doing this to support and because I'm interested in it, not to get rich.

oh wow..
Must be a typo, I'll see what fixing this does.

Thank you.

According to docs, it can provide from 500 mA up to 1100 mA, depends how much attached device is in some way compatible with oem apple devices. Try to lower clock speed @540... Dropping hasrate is usually all about lack of juice from usb port...

EDIT: 620 is not available clock speed listed on first page.

I have no idea, I can only tell what I saw these last 2 days.

This is what system info says

Current Available (mA):   500
Current Required (mA):   100
Extra Operating Current (mA):   0

Apple docs:

Apple computers equipped with USB 3 provide up to 900 mA (milliamps) at 5 V (Volts) to most Apple USB peripherals as well as all third-party USB peripherals that comply with USB specifications.
https://support.apple.com/en-us/HT204377

For stable 3 MH you will need more than 500 mA. Can macbook pro usb port suplly current more than that?

Hello,

I've been running a ML2 for about 2 days, pretty much at stock settings (upped freq to 620) on a macbook pro usb3 port.
It has been running stable for that time, but suddenly the hashrate dropped to 2.1 - 2.5 MH, it used to be stable at 3 - 3.2 MH.

Am I missing something right here? My setup didn't change (no other devices attached).

the plastic housing, I figured I could just push the blade off cause I couldn't get the o-ring to budge

broke what part?

tried this and broke the fan, I bought a fan on amazon but its not as powerful cause the chip gets hotter, anyone know where I can get a direct replacement fan?

Did an interesting (to me anyway) test. I have 6 Moonlanders - 3 on a Mac and 3 on a Rasp Pi both using Plugable hubs. Running at 832 on Mac and 700 on Pi - voltage about .83 on all ML. Those seem to be the sweet spots for me and they are hashing fairly close to each other and have been running for days without a hiccup. I took 6 2Pacs running on a different pi on an Eyeboot hub running at freq 150ghz. I pointed both sets of 6 to Multipool Digibyte ports - one of the few coins that can be mined with both SHA and Scrypt. After three days, the Moonlanders have generated about 15% more shares than the 2Pacs. Was pretty surprised by that. Given the pretty significant difference in power draw (ML quite a bit lower) its a good data point on just how efficient these little guys are!

That said - when you add up the cost of all of this it really has to be viewed from the lens as hobby not a money maker. I didn't do a benchmark against my Antminer L3s or T9s for obvious reasons. Think I would need roughly 55 ML to get the same output as one mildly overclocked L3, which can be had for less than $2K all in. Haven't done the math but guessing a ML rig that would but out 550mhz would run about $6K (guess I did just run the math - lol). Doesn't take anything away from the Moonlander, but does put it into context. Nice thing is you can run the ML in the house as they don't sound like a small jet engine about to take off. Or put in a $40k solar system to not get $4K utility bills every month.

Thanks!  If I had .1 LTC I would.  I have not even gotten close to that yet on litecoinpool.
I did get through all 56 pages and I saw how to do it in linux.  I missed the \\.\COMx for windows in all of the posts.
I did see an example of MLD@COMx but not the \\.\COMx.
So for the clock speed of 2 of these sticks on the same pool lets say stick 1 is COM2 and stick 2 is COM3.
I assume I have to do this for both the -S MLD and the --set commands?
Like this:
-S MLD:\\.\COM2 --set MLD:clock=600 -S MLD:\\.\COM3 --set MLD:clock=796

Thanks,
Bob

Not sure what readme you are refereing to, this thread -- all the 50+ pages -- IS the readme!, and answers all your questions!! And yes it is all possible, very easily.

The first thing you have to realize is that the link between physical USB port, virtual COM port, and MLD # is not fixed.
You need to open your computers device manager, plug in the first MLD into some USB port, and see which COM port pops up on the virtual com ports in the device manager (usually COM3). Make note of it. Then do the same for the 2nd MLD etc (usually COM4). This is before you have started bfgminer.
Then, you can set different clockspeeds for different com ports in one startup script, or create two scripts, one for each of the two com ports, one script with one clockspeed/one pool/one coin, and the other for the other clockspeed etc. The latter approach is needed for different pools/coins anyway, but I also prefer it for different clockspeeds as it is then easier to see which MLD in bfgminer is actually supposed to run at the desired hashrate. You just start each startup script (bat file) as normal.

Now the magic that you have been waiting for: the -S MLD command?? To skip over 53 pages of support thread should really cost you 0.1LTC straight into my wallet, but I will help you for free : -S MLD:\\.\COM3 instead of -S MLD:all for the script that is to mine the MLD that appeared in virtual com port #3 (use the actual number that showed up in device manager). The other script would thus have -S MLD:\\.\COM4 for example. The two scripts can have different clockspeed settings and different pools as per normal.   

Hmmm...
The restart hasn't worked - it's just stayed around that same 2.7. And the odd thing is, the miner hasn't actually been running straight ever for that long. I always give it a 5 min break every day (used to be twice a day) in fear of it overheating (I know it's stupid, but just a paranoia). Is there any other possible explanation?

Some further observations. When I start bfgminer, the D2 led stays on and D1 led blinks once. The component at L1 seems to have separated from it's base. I can press on it and it will move down slightly. I can see a slight gap when looking from the side.

I have one stick that stopped working when swapping to another hub. It was working perfectly, pulled it from one hub and installed in another to balance the power load and it won't hash anymore.

Anyone got any tips to troubleshoot?

yes, but you will need to manually restart it currently.

And just to be clear - the cores can come back online right?

Thanks - the MLD support has been the best for any product I have EVER bought... ever. Full stop. Thanks for being so on the ball!

Thanks for suggestion!