Official FutureBit Moonlander 2 Driver and Support Thread

[dartec]

Just a bit of a dumb question ...

Do these devices need to be plugged in directly into the USB port/hub, or could you use an USB extension from the hub to the device?
Something like this:  https://www.sweetwater.com/store/detail/LokSaverCable

TIA.

[1713874376]

1713874376

[1713874376]

1713874376

[1713874376]

1713874376

[markcarline2]

I've just ordered a couple of these usb 3 right angle ones, will be reporting back when tested....

https://rover.ebay.com/rover/0/0/0?mpre=https%3A%2F%2Fwww.ebay.co.uk%2Fulk%2Fitm%2F282430334062

[soifigured]

Just a bit of a dumb question ...

Do these devices need to be plugged in directly into the USB port/hub, or could you use an USB extension from the hub to the device?
Something like this:  https://www.sweetwater.com/store/detail/LokSaverCable

TIA.

You can use them with USB extensions.  I'm using usb extensions to put a little space between mine, they still hash well.  I'm using ones from monoprice.com.  They can be had for pretty cheap through them.

[Astrali]

been using an extender cable on the moonlander directly connected to pc cause i had not enough space to directly plug it.
it ran quite stable! should work

[hercthx]

Here's something, I had to reboot my router this morning, on internet restore, I had to restart My MLD BFGminer exe's. I know this is more of a BFG question but just in case someone here has a solution, is there a way to set the MLD BFG to auto resume on internet restore? Current BFG is the 5.4.2-34 futurebit provided to run with MLDs.

[dem0nlord]

Here's something, I had to reboot my router this morning, on internet restore, I had to restart My MLD BFGminer exe's. I know this is more of a BFG question but just in case someone here has a solution, is there a way to set the MLD BFG to auto resume on internet restore? Current BFG is the 5.4.2-34 futurebit provided to run with MLDs.

Possibly fixed by the newer code if you can compile from the git tree.

[JustAnotherPLT]

So I've updated with the new coding that you have posted but I'm still running into problems. When I initially boot BGFminer it starts up fine and runs all day with no problems. The moment I add a pool to switch to, it gets hung up and flashes yellow. I'm literally stuck mining one pool. I've tried everything and cant figure it out. I'm operating on OSX 10.13.2.

https://ibb.co/fdqHPm

https://ibb.co/jQQOx6

[dem0nlord]

So I've updated with the new coding that you have posted but I'm still running into problems. When I initially boot BGFminer it starts up fine and runs all day with no problems. The moment I add a pool to switch to, it gets hung up and flashes yellow. I'm literally stuck mining one pool. I've tried everything and cant figure it out. I'm operating on OSX 10.13.2.

https://ibb.co/fdqHPm

https://ibb.co/jQQOx6

Can tell by your version number at the top that isn't the latest code, you're running code from Nov 14th. How did you git/compile it?

[soifigured]

Rasberry Pi  Raspbian OS

So this relates to the Moonlanders,  but is more of a Raspbian question

When I reboot my pi,  it reassigns all USBs   ttyUSB0 becomes 2,   4 becomes 8.....etc....

I am using 4 v1.2 Mooonlanders and 8 v2.0 Moonlanders,  so I need to specify the USB in order to get them to work with the correct bfgminer.

Any idea on how I can lock them down to their # even after reboot?

This problem may or may not continue once jstefanop enables the new bfgminer to run both,  but I'm guessing I'll still need to identify by ttyUSB#

I haven't tried this with the moonlanders yet, but I know when using bfg with older gridseeds you could call them out by serial number.  When you go to manage devices in bfg you can find the serial number of the device (It is different than what is found on the sticker).  Give that a shot, I'm very curious to see if it works out.  I don't have any syntax examples with me.  It's been a good long while since I've used a gridseed but I'll try to post one up after I get home from work tonight.

You can also call out the devices by usb bus instead of port.  Not sure if the rpi has more than one usb bus though.

[sunk818]

So I've updated with the new coding that you have posted but I'm still running into problems. When I initially boot BGFminer it starts up fine and runs all day with no problems. The moment I add a pool to switch to, it gets hung up and flashes yellow. I'm literally stuck mining one pool. I've tried everything and cant figure it out. I'm operating on OSX 10.13.2.

You're not getting accepted shares because the difficulty is too high. Are you sure you're interpreting the screen correctly? 706 difficulty is extremely high for a Moonlander2. Maybe you can try multipool and litecoinpool as your two pools. Set up worker on multipool as vardiff. Then see if you have the same issue.

[sunk818]

Here's something, I had to reboot my router this morning, on internet restore, I had to restart My MLD BFGminer exe's. I know this is more of a BFG question but just in case someone here has a solution, is there a way to set the MLD BFG to auto resume on internet restore? Current BFG is the 5.4.2-34 futurebit provided to run with MLDs.

That's really more of a question for bfgminer author. I quit bfgminer after x of shares submitted (e.g. --shares 1) 1m accepted share is .001. So, --shares 1 would mean you'd need 1000m accepted shares and bfgminer would quit. You just put bfgminer in a loop. I give it a rest for one minute, then start up again.

[jstefanop]

So I've updated with the new coding that you have posted but I'm still running into problems. When I initially boot BGFminer it starts up fine and runs all day with no problems. The moment I add a pool to switch to, it gets hung up and flashes yellow. I'm literally stuck mining one pool. I've tried everything and cant figure it out. I'm operating on OSX 10.13.2.

You're not getting accepted shares because the difficulty is too high. Are you sure you're interpreting the screen correctly? 706 difficulty is extremely high for a Moonlander2. Maybe you can try multipool and litecoinpool as your two pools. Set up worker on multipool as vardiff. Then see if you have the same issue.

Actually 706 is the network difficulty (which is 706 * 65k scrypt dif). Your pool diffs are 1 and 1m which is actually 64k diff (way too high for MLD2) and 1m which is diff 64 which is fine. Im assuming your having difficulties with pro-hashing, which has a default diff of 64k.

[JustAnotherPLT]

I've probably royally messed this up but here is steps and pictures of EVERYTHING I've done. Maybe someone can help.

1) Downloaded BGFminer-5.4.FutureBut2-Mac64

2) Control clicked on "start-moonlander-2" and used textedit and change the code to this'

Code:

#!/bin/sh
cd -- "$(dirname "$0")"
cd bin
./bfgminer --scrypt -S MLD:all --set MLD:clock=756
pause
exit

3) Went to GitHub and clicked on the comments. Then cut and pasted the coding in the picture below to "driver-futurebit.c", saved and closed.
https://ibb.co/nCDtx6

4)Everytime I start up BFGminer using the start-moonlader-2 it automatically starts mining the picture below.
https://ibb.co/jzhH76

5) I deleted the pool that's misbehaving.

6)Moonlannder runs fine until I add another pool. Password for any pool I add is d=128.

7) Pro-Hash AND Mining-Dutch are the ones I'm trying to mine. Mining-Dutch has no issues with Litecoin but anything else is a problem.

[dem0nlord]

3) Went to GitHub and clicked on the comments. Then cut and pasted the coding in the picture below to "driver-futurebit.c", saved and closed.
 

Yeah that's not going to do anything for you. You need to clone that branch of the git tree and then compile a new binary. I don't use Macs or Windows so I can't comment on exactly how to do that process on them.

[Dischg]

Got my moonies running at a clock speed of 796 and they're running totally SOLID at 4.52Mh/s and the error rate is averaged at .09% (which I know is nothing). How far can I get the error rate up to til it becomes a problem or unprofitable?

Also, really ridiculous question here...

I actually started ASIC mining because my office is the coldest room in my house. I could've just bought a stupid little heater, but I thought I could do this and add a little heat my room AND make a little scratch on the side. Right now, these babies are barely even warm so I'm gonna have to jack them up a lot to create any heat. For now, I'm just seeing how long they'll go without locking up (I'm at almost 11 hours!). So what is the sweet spot in temp that people are encountering? Speed vs. errors and lock ups?

[sunk818]

6)Moonlannder runs fine until I add another pool. Password for any pool I add is d=128.

7) Pro-Hash AND Mining-Dutch are the ones I'm trying to mine. Mining-Dutch has no issues with Litecoin but anything else is a problem.

Try leaving the password empty. prohashing.com has vardiff (variable difficulty). You're setting the difficulty too high for scrypt algorithm. scrypto algorithm is not the same as SHA256 algorithm.

For mining-dutch.nl 3321 is the low diff for litecoin so that seems to be the right port for you.

[sunk818]

So what is the sweet spot in temp that people are encountering? Speed vs. errors and lock ups?

You might want to get an Antminer L3+ if you want to generate more heat (and noise). These aren't going to warm up your room. I have ten ML2 running and they barely generate a swarm breeze @ 832Mhz.

[JustAnotherPLT]

6)Moonlannder runs fine until I add another pool. Password for any pool I add is d=128.

7) Pro-Hash AND Mining-Dutch are the ones I'm trying to mine. Mining-Dutch has no issues with Litecoin but anything else is a problem.

Try leaving the password empty. prohashing.com has vardiff (variable difficulty). You're setting the difficulty too high for scrypt algorithm. scrypto algorithm is not the same as SHA256 algorithm.

For mining-dutch.nl 3321 is the low diff for litecoin so that seems to be the right port for you.

I tried that as well. It's almost as if by adding another pool it locks things up.

[jstefanop]

New driver release is out, sorry for the delay and thanks for being patient. I added some last minute debugging code to better help people with issue and rule out any hardware problems. The compile binaries include the big restart fix, so these should technically hash forever without needing any manual restarts (as long as the power supply is semi-stable and you haven't really screwed up the voltages).

Let me know if the binaries run fine on respective systems...might have mis-compiled something while trying to keep track of every architecture 

https://github.com/jstefanop/bfgminer/releases/tag/bfgminer-5.4.2-futurebit2-beta2

[sunk818]

https://github.com/jstefanop/bfgminer/releases/tag/bfgminer-5.4.2-futurebit2-beta2

I'm seeing note now, MLD 7: ASIC has stopped hashing, attempting to restart.

It does this several times before the message goes away. The ASIC typically has the lower hash rate, so maybe this will give me a boost overall in terms of hashrate.