Official FutureBit Moonlander 2 Driver and Support Thread

[Astrali]

Linux question - Once the new driver is released for Pis, what specifically do we need to type to install and use it?

depends on the way how it is released.

you dont need to "install" a precompiled binary - just download, maybe extract and use it

as soon as link to new binarys are here i'll help you out

Greetings - Astrali



This way you could compile it on your own - but i guess thats not the best opinion for a linux starter.

Code:

git clone -b futurebit2_driver https://github.com/jstefanop/bfgminer
sudo apt-get install libevent-dev
cd bfgminer
./autogen.sh
./configure --enable-scrypt --enable-futurebit
make


1 will download the bfgminer source
2 will install some dependencies to compile bfgminer (maybe you need some more - we can fix it together - or a little google will help)
3 enter bfgminer directory
4 run automatic script ..
5 configure the source code to use scrypt algo and include the futurebit driver as well (i didnt excluded other mining hardware! takes longer to compile but more devices will work)
6 compile the sourcecode

[1714183568]

1714183568

[1714183568]

1714183568

[1714183568]

1714183568

[aarons6]

i like the new version, its going strong at 798 just over 9 hours with just under 1% HWE..

have you tried to get the v1 and v2 to work together? i have an idea im going to try..
im going to rename MLD to MLD2 in the new driver then compile it with the old and new drivers activated.. will that work?

[RdStrcklnd]

Linux question - Once the new driver is released for Pis, what specifically do we need to type to install and use it?

depends on the way how it is released.

you dont need to "install" a precompiled binary - just download, maybe extract and use it

as soon as link to new binarys are here i'll help you out

Greetings - Astrali



This way you could compile it on your own - but i guess thats not the best opinion for a linux starter.

Code:

git clone -b futurebit2_driver https://github.com/jstefanop/bfgminer
sudo apt-get install libevent-dev
cd bfgminer
./autogen.sh
./configure --enable-scrypt --enable-futurebit
make


1 will download the bfgminer source
2 will install some dependencies to compile bfgminer (maybe you need some more - we can fix it together - or a little google will help)
3 enter bfgminer directory
4 run automatic script ..
5 configure the source code to use scrypt algo and include the futurebit driver as well (i didnt excluded other mining hardware! takes longer to compile but more devices will work)
6 compile the sourcecode

Thanks as always Astrali! I'm definitely a linux starter, so I'll wait for the link to the new binaries, but once they're released I'll take you up on that offer for help!

[jstefanop]

i like the new version, its going strong at 798 just over 9 hours with just under 1% HWE..

have you tried to get the v1 and v2 to work together? i have an idea im going to try..
im going to rename MLD to MLD2 in the new driver then compile it with the old and new drivers activated.. will that work?

No, needs a complete reorganization, and separation of driver files etc. Its not as simple as changing the driver name. Configuration and make files etc need to be updated. Ill start work on that as soon as I have the moonlander 2 driver in a stable form.

[jstefanop]

I'm used to cgminer where the accepted share is a multiplication of the share difficulty. Is it me, or is bfgminer weird about how it displays accepted shares? It shows it as one share regardless of difficulty. But then with rejects and hardware errors, I'm not really sure what the numbers really mean.

Is there a way to fix this, or is this just wonky programming by bfgminer?

Also, adjunct... --shares 1000 parameter doesn't seem to work. When I quit with 800 accepted shares, it tells me only 21 shares were accepted before quitting.

1 Accepted share is a share that is equal to or higher than the pool difficulty assigned to your miner. The device itself operates at a much lower hard fixed difficulty (scrypt difficulty 16 to be exact). Each red blink you see is actually a difficulty 16 share returned by the miner. This is needed in order to monitor the hardware and hash rates in near realtime.

 Hardware errors are based on on this driver level difficulty, so thats why even though you might only have 20 accepted shares at pool diff 512, you might have 100 hardware error shares, yet the HW error % is under 1%. Thats because the miner is returning an average 2-3 shares per second to the driver, but ~ 1 share a minute to the pool depending on pool diff.

I believe bfgminer --shares parameter uses the device level shares and not pool shares.

[Astrali]

Thanks as always Astrali! I'm definitely a linux starter, so I'll wait for the link to the new binaries, but once they're released I'll take you up on that offer for help!

a man - a word!
i'll be there buddy

[dvsrk]

Alright, I've been playing with this thing all day. I've targeted it down this issue.

Code:

[2017-12-10 16:15:41] Network difficulty changed to 20.4k (146.3G)

Any time this happens the miner stops running. You can hear the fan wind up a little as if there's an increase in juice that was being used for the processor. Now the yellow light just flashes every few seconds. Once at this point, unless I restart everything, it won't work on any changes. I'm at a loss... please help.

Honestly looking for some help please.

Whenever network diff changes  new work gets sent to the ASIC and its restarted, sounds like your USB port/Hub is not providing enough power. When new work is sent to the ASIC is when it has the highest chance to get stalled because of power transients the hub can't keep up with.

Beta testing of my new update that resolve this issue and similar issues that cause the sticks to go dead and need restarting is going well and should have a binary release tomorrow. This should also keep sticks alive from poorly tuned/unstable voltages etc.

Pic below is a bunch of sticks running the new driver that I have purposely undervolted so they are unstable....driver has kept them alive and hashing for over a day now with no manual restarts needed!

https://farm5.staticflickr.com/4730/27199602779_08298b6e0b_c.jpg

changes are already pushed to my GitHub for anyone that dosent want to wait and can compile on their own.

Hi,
do you have this for windows. can anyone share instructions to apply this on windows machine?
thanks

[hilti30]

Thanks for the help for some reason was only giving me read only option but using the get info option i was able to change things.. Thanks again for the help

What macOS version are you using?

How are you editing the file?

In Finder, go to the folder, click on the file, and do Command+I (or right-click Get Info). See what your Sharing & Permissions is set at. You (me) should have Read & Write privilege.

Make sure you quit out of the script (terminated) is not being used (running).

Hi i'm total newb and not sure if i am doing it right but can't get this to work on my mac followed the work around but when i try to edit the start-moonlander-2 file with my pool details it says its read only and won't allow me to change it.

So how do i enter my details?

[hercthx]

Has it been discussed on how to run 1 moonlander2 per instance of bfgminer in win10 in this thread ? I saw instructions regarding rpi, but cant for the life of me see about win10 cheers.

[jstefanop]

Alright, I've been playing with this thing all day. I've targeted it down this issue.

Code:

[2017-12-10 16:15:41] Network difficulty changed to 20.4k (146.3G)

Any time this happens the miner stops running. You can hear the fan wind up a little as if there's an increase in juice that was being used for the processor. Now the yellow light just flashes every few seconds. Once at this point, unless I restart everything, it won't work on any changes. I'm at a loss... please help.

Honestly looking for some help please.

Whenever network diff changes  new work gets sent to the ASIC and its restarted, sounds like your USB port/Hub is not providing enough power. When new work is sent to the ASIC is when it has the highest chance to get stalled because of power transients the hub can't keep up with.

Beta testing of my new update that resolve this issue and similar issues that cause the sticks to go dead and need restarting is going well and should have a binary release tomorrow. This should also keep sticks alive from poorly tuned/unstable voltages etc.

Pic below is a bunch of sticks running the new driver that I have purposely undervolted so they are unstable....driver has kept them alive and hashing for over a day now with no manual restarts needed!



changes are already pushed to my GitHub for anyone that dosent want to wait and can compile on their own.

Hi,
do you have this for windows. can anyone share instructions to apply this on windows machine?
thanks

Binaries for new Build will be posted soon, keep an eye on the releases page on my GitHub.

[jstefanop]

Alright, I've been playing with this thing all day. I've targeted it down this issue.

Code:

[2017-12-10 16:15:41] Network difficulty changed to 20.4k (146.3G)

Any time this happens the miner stops running. You can hear the fan wind up a little as if there's an increase in juice that was being used for the processor. Now the yellow light just flashes every few seconds. Once at this point, unless I restart everything, it won't work on any changes. I'm at a loss... please help.

Honestly looking for some help please.

Whenever network diff changes  new work gets sent to the ASIC and its restarted, sounds like your USB port/Hub is not providing enough power. When new work is sent to the ASIC is when it has the highest chance to get stalled because of power transients the hub can't keep up with.

Beta testing of my new update that resolve this issue and similar issues that cause the sticks to go dead and need restarting is going well and should have a binary release tomorrow. This should also keep sticks alive from poorly tuned/unstable voltages etc.

Pic below is a bunch of sticks running the new driver that I have purposely undervolted so they are unstable....driver has kept them alive and hashing for over a day now with no manual restarts needed!



changes are already pushed to my GitHub for anyone that dosent want to wait and can compile on their own.

Hi,
do you have this for windows. can anyone share instructions to apply this on windows machine?
thanks

Same deal as in linux, you need to specify the com port you want bfgminer to connect to instead of -S all (this searches for all moonlanders connected on the system) below is the format

Linux: -S /dev/ttyUSBn
Windows: -S \\.\COMn

where n is the COM port number moonlander is connected on (use device manager to find it).

[hercthx]

Hmm I tried -S \\.\COM6 as Device Manger located my Miner as COM6 and it wont run, bfgminer just throws some errors and shuts down. perhaps my syntax is off? is the \\.\ indicating a path I must fill out?

 UPDATE, I found the solution, by entering -S MLD@COMn, where n=COM number as per Device Manager. Thanks for putting me on the right track

[mrgoldy]

i like the new version, its going strong at 798 just over 9 hours with just under 1% HWE..

have you tried to get the v1 and v2 to work together? i have an idea im going to try..
im going to rename MLD to MLD2 in the new driver then compile it with the old and new drivers activated.. will that work?

No, needs a complete reorganization, and separation of driver files etc. Its not as simple as changing the driver name. Configuration and make files etc need to be updated. Ill start work on that as soon as I have the moonlander 2 driver in a stable form.

awesome!   would love to see v1 and v2 with 1 bfgminer.
anxiously awaiting the armv6 (I fully admit to not being a linux user)

Rig porn
4 v1.2 moonlanders
8 v2 moonlanders
cable management in progress along with a jig to hold each stick in place for airflow
  How do embed pics in here?
https://imgur.com/a/wGrX0

[sunk818]

Serial numbers - Does the hex serial number in bfgminer under [M]anage Devices correspond with the gold sticker on the PCB?

Can someone help me figure out how to make a voltage reading correctly? I have a multimeter, but can't figure out how to get the proper reading.
What is the dial I need to set it at?
For the black & red tips, do I just put each on the metal squares that are on the side?



To embed an image, you have to go to IMGUR and get the Direct Link URL.

[sunk818]

@jstefano -

Are you using Windows?

I'm on MBP with running with Sipolar A-400 10-(http://www.sipolar.com/page172.html?product_id=18) port so it is supposed to be able to handle 120W (12V 10A).

I'm trying to run at 852 freq. Not sure if I have the right voltage. See multimeter question above.

bfgminer starts with a bang, 5-6 Mh/s. Then it settles down at something much lower 2-4Mh/s.

My kill-a-watt says 95 watts at stable, initial goes past 120w according to killawatt.

[aironeous]

Some guy made a Crypto Christmas Tree using a whole bunch of Moonlander 2 USB miners


https://youtu.be/Et3jgHnTjZ8

hahah that is brilliant...nice find.

I was going to make a cryptmas tree but nah, too much expense.

Litecoinpool does not work for me at all. I'm in the US on KDE Neon. I switched to http://give-me-coins.com/litecoin-pool and I haven't had any problems.
In fact I'm getting 3 other coins free if I mine litecoin.
PTC, DOGE and VIA
If I'm understanding merge mining correctly.

[Tahoebound777]

Hello all! Just scratching the surface with mining and trying to wrap my brain around it, there sure is a lot. I just received 3 Moonlanders in the mail and excited to get started. Couple quick questions for all the seasoned veterans out there, I appreciate the tips for the newb. For the 3 Moonlanders, they will be on a 7 port HUB, new laptop with Windows 10 and BFGminer running only the sticks, nothing else with 24 hour availability.

1) With 3 sticks is it feasible/profitable to solo mine or better off joining a pool?

2) If solo, can you mine fractionals or must one wait until the entire blockchain has been solved?

3) If pool is better, which pool are people getting the best success on? There are so many with mixed opinions.

Any and all help is genuinely appreciated, even if you are hyperlinking me to something else. I've done quite a bit of internet searching and still left scratching my head. Thank you in advance!

[dem0nlord]

I'm trying to run at 852 freq. Not sure if I have the right voltage.

There's no universal answer for the voltage, there will be some variance from one stick to another. You need to raise the core voltage until the hardware error rate is at an acceptable level. I didn't even actually measure it, just adjusted it upward until the errors came down. In my case both sticks needed the core voltage pot rotated approx 90 degrees clockwise to achieve an acceptable error rate when operating at 954mhz as you can see here: https://image.ibb.co/cSvWxw/moonlanders.jpg

For your 852mhz you won't need to turn the pots nearly as much, probably less than 45 degrees.

[dvsrk]

I have got my moonlander 2 & facing couple of issues,

I have connected the USB device to my laptop with clock set to the lowest frequency ("--set MLD:clock=384"). I'm using the low frequency setting until i get my new USB HUB. The issue is the hashing stops/halts after running for few minutes. Below are the two cases i have observed.

case 1:
hashing stops/halts when it encounters "stratum connection to pool 0 interrupted". I have waited for almost 30 minutes after this last message in my screenshot & it never progressed.
https://imgur.com/rpn2Fre

case 2:

hashing stops/halts when it encounters "pool 0 stratum share submission failure...pool o http://litecoinpool.org:3333 not responding". I have waited for almost 30 minutes after this last message in my screenshot & it never progressed.

https://imgur.com/uNVoNwj


Below is the summary report generated after Quit.

https://imgur.com/PXHiiux


Please help me if I'm missing anything here or to tweak anything to make it run continuously without restarts for every few minutes.

Thank you.  

[slanislaw]

I have got my moonlander 2 & facing couple of issues,

I have connected the USB device to my laptop with clock set to the lowest frequency ("--set MLD:clock=384"). I'm using the low frequency setting until i get my new USB HUB. The issue is the hashing stops/halts after running for few minutes. Below are the two cases i have observed.

case 1:
hashing stops/halts when it encounters "stratum connection to pool 0 interrupted". I have waited for almost 30 minutes after this last message in my screenshot & it never progressed.


case 2:

hashing stops/halts when it encounters "pool 0 stratum share submission failure...pool o http://litecoinpool.org:3333 not responding". I have waited for almost 30 minutes after this last message in my screenshot & it never progressed.




Below is the summary report generated after Quit.




Please help me if I'm missing anything here or to tweak anything to make it run continuously without restarts for every few minutes.

Thank you.  

Edit your power options. In Windows search Power Options. Change to High Performance. Click Change Plan Settings. Adjust the sleep settings.