Official FutureBit Moonlander 2 Driver and Support Thread

[jstefanop]

I received this one in amongst the others that I received today. All are working fine except for this one. After visually inspecting with magnifying glass I could see the 'L1" (inductor ??) appears damaged.

Question: would that be the reason that the device starts mining and then after just a minute or less, constantly drops out and can no longer be restarted by the driver?

Second Question: Does this get handled by the distributor or possibly yourself, or am I just out of luck on this one?

Thats the inductor casing chipping off..it happens sometimes due to thermal stress during reflow. Its not enough to damage an inductor...if it was damaged it would not work at all. Sounds like that stick just need to be tuned better. Trying lowering voltages/clocks and see if that helps. If not you can return it to distributor for replacement in the off chance that the inductor really did get damaged.

[1715203633]

1715203633

[1715203633]

1715203633

[1715203633]

1715203633

[1715203633]

1715203633

[jstefanop]

Well I finally got my ball bearing fans in for the stock replacements.

They work well but they are extremely loud compared to the stock sleeve fan.

They are the same type/brand as the stock fan, just ball bearing, direct replacement.

You probably bought one that is really high RPM...these fans can go up to 15k RPM. You only need about 7-10k RPM to properly cool these. Stock fans run around 9-11k.

would a 8000rpm fan cool the sticks sufficiently at 5 MH/s

http://gdstime.com/product/?99_471.html

Thats the exact same fan that ships with these...

[philipma1957]

To all please check the fan solution I use for 8 sticks

[mdtrav]

I am having a strange issue.

I am unable to adjust the clockspeed on my miner if I set it to anything other than 800 it fails to hash anything and stops responding
here are my settings
bfgminer.exe --scrypt -o stratum+tcp://poolurl.com:4224 -u bla.user -p password --no-longpoll -S MLD:\\.\COM5 --set MLD:clock=800 --verbose

This seems to be the only setting that works, If I set it higher, or lower it fails to respond. 800 is not even in your list of preset clock speeds. I've adjusted the power, lowered it, raised it, not difference. It is hashing at about 3.4Mh/s with HW:251/.20% in the last 21hrs.

What do you mean it fails to respond? At 3.4mh your defaulting to stock speed of 600mhz. Sounds like your not editing the clock speed correctly?

I figured since it was not one of your specified clock speeds it was defaulting to something.

This is the error I get.

http://puu.sh/zcuiU/7fa3e36764.png


I've done some more testing, clock speed 700 seems to work fine at around 4Mh/s I occasionally get an error(JSON-RPC non method decode failed: (null) Unknown startum msg:{"id":null, "result":[],"error": true} )Not sure if it is the miner or the pool causing that error.
Going to clock speed 720 kind of works, 3.7mhs but stops hashing and needs to restart per bfg miner.

I have the power at roughly .86

[TimBuck2]

Thats the inductor casing chipping off..it happens sometimes due to thermal stress during reflow. Its not enough to damage an inductor...if it was damaged it would not work at all. Sounds like that stick just need to be tuned better. Trying lowering voltages/clocks and see if that helps. If not you can return it to distributor for replacement in the off chance that the inductor really did get damaged.

OK. I will work with the tuning a bit more. I thought the same thing initially - that it would not work at all if it were a major problem.

I will spend a little more time trying to tune it properly and see what I come up with.

Thanks.
 

[jstefanop]

I am having a strange issue.

I am unable to adjust the clockspeed on my miner if I set it to anything other than 800 it fails to hash anything and stops responding
here are my settings
bfgminer.exe --scrypt -o stratum+tcp://poolurl.com:4224 -u bla.user -p password --no-longpoll -S MLD:\\.\COM5 --set MLD:clock=800 --verbose

This seems to be the only setting that works, If I set it higher, or lower it fails to respond. 800 is not even in your list of preset clock speeds. I've adjusted the power, lowered it, raised it, not difference. It is hashing at about 3.4Mh/s with HW:251/.20% in the last 21hrs.

What do you mean it fails to respond? At 3.4mh your defaulting to stock speed of 600mhz. Sounds like your not editing the clock speed correctly?

I figured since it was not one of your specified clock speeds it was defaulting to something.

This is the error I get.




I've done some more testing, clock speed 700 seems to work fine at around 4Mh/s I occasionally get an error(JSON-RPC non method decode failed: (null) Unknown startum msg:{"id":null, "result":[],"error": true} )Not sure if it is the miner or the pool causing that error.
Going to clock speed 720 kind of works, 3.7mhs but stops hashing and needs to restart per bfg miner.

I have the power at roughly .86

Your overclocking higher than your power hub can support...this is why it works at default frequency and you start getting issues as you go higher. Turn down the voltage, as the stock setting for these are higher than they need to be, and that will allow you to pull less power and clock higher.

[mdtrav]

I wonder if my Amazon Hub is just not putting clean power down. I put it back to stock power and I can run it at clock=796, it's seems to working fine now. averaging 4.5mhs

[lennyNO]

To all please check the fan solution I use for 8 sticks

Hi, it seems you are using the (expensive! ) eyeboot hub. What clockfrequency are you using? As you have just above 4Mh/s per MLD it seems you are running these at 724Mhz? I I found that placing the mld's in this way they get rather close, i.e. the backside heatsink of one mld is almost touching the front heatsink of the next.

I have 11 MLDs on the same hub, of which 6 I am running at 924Mhz (all still with stockfan) and 5 at 824Mhz (all without stockfan), and -- as per jstephanop's instructions -- dialed the core and mem AS LOW AS POSSIBLE. The temps are managable, because I suck in cold air right now (winter here), but as summer comes I have to do something. I for sure are not going to have units run at 924Mhz back to back in this hub, it would get way too hot!! Right now I use all the every-other USB ports on the top (2x4) and the 3 side usb ports (total 11), but I hope to be able to move all 11 units to the top (first and foremost to save space). That is a little challenge because I have the impression that the MLDs that are the end of the internal powerlines see too much of a voltage drop and don't get enough power. I have problems with that earlier when trying all units on the top of the hub. I need to look into that again too, maybe I am stuck with the side-usb slots no matter what.

I also looked at the 3D printed casing someone showed here earlier, with push/pull fans on either end. For the eyeboot hub it would have to be like you have the fans, on the side. Maybe I can use some smaller fans. Still looking into that as well.

[bakuna]

I think I had one of mine die sometime this morning -- it shoes 100% HW error rate at 700mhz. It hashes at like 83.2kh and constantly stops hashing/restarts.

This is a completely different unit than the one I mentioned a few posts ago.

What frequency were you running it before it died?

700mhz, highest I've ever run it was 756mhz.

I’m so lost right now. I’m helping my 10 year old son build a rig with a Moonlander 2 on a RPi3.... I’m running at a 100% HW..... it just showed up in the mail today... first , I’m sorry to attach this to your post... I’m so new I don’t even know how to start my own post... please help a dad who’s trying his best.... thanks

[Astrali]

To all please check the fan solution I use for 8 sticks

Hi, it seems you are using the (expensive! ) eyeboot hub. What clockfrequency are you using? As you have just above 4Mh/s per MLD it seems you are running these at 724Mhz? I I found that placing the mld's in this way they get rather close, i.e. the backside heatsink of one mld is almost touching the front heatsink of the next.

I have 11 MLDs on the same hub, of which 6 I am running at 924Mhz (all still with stockfan) and 5 at 824Mhz (all without stockfan), and -- as per jstephanop's instructions -- dialed the core and mem AS LOW AS POSSIBLE. The temps are managable, because I suck in cold air right now (winter here), but as summer comes I have to do something. I for sure are not going to have units run at 924Mhz back to back in this hub, it would get way too hot!! Right now I use all the every-other USB ports on the top (2x4) and the 3 side usb ports (total 11), but I hope to be able to move all 11 units to the top (first and foremost to save space). That is a little challenge because I have the impression that the MLDs that are the end of the internal powerlines see too much of a voltage drop and don't get enough power. I have problems with that earlier when trying all units on the top of the hub. I need to look into that again too, maybe I am stuck with the side-usb slots no matter what.

I also looked at the 3D printed casing someone showed here earlier, with push/pull fans on either end. For the eyeboot hub it would have to be like you have the fans, on the side. Maybe I can use some smaller fans. Still looking into that as well.

hi, its my case

its designed to use short USB cables to connect to the hub. this way you can use every port of the hub no matter how close spacing is.
i normally dont run my moonlanders above 800 but i tried going up to 5 mh/s and the air coming out of the printed case was just slightly warm - so i would say airflow is doing a good job

i cant measure inside cause i would stop a fan on doing that.. but they ran stable for many hours until i decided to move back my speed again.

so if you got someone with a 3d printer close to you - this is a nice solution - and you can use all your usb hub ports in the way you like

Greetings - Astrali

[sandacus]

Hi,

Thank you for the excellent and detailed instructions for installing and using BFG Miner with the Futurebit Moonlander 2. I have the latest BFG Miner up and running on a Raspberry Pi 3, running Raspbian.

My problem; the RPi will not recognise, (i.e., it doesn't detect it all) the Futurebit Moonlander 2 when I put it either directly into the RPi, or when I plug it into a powered USB port, although the Moonlander does show the green LED and the fan spins when in the all the USB ports.

Troubleshooting I have done so far; 1) Checked that a regular USB memory stick works on both the RPi directly and the powered USB hub, which it does; 2) checked whether the Moonlander shows up on my laptop (MacBook Pro, OSX High Sierra), which it does not (but the green LED comes on and the fan spins).

Please can someone suggest some more troubleshooting, or perhaps something I have overlooked (I am a noob after all!)?

Thanks,
Sandacus.

[aballen]

Questions on difficulty

• is 128 the best setting for ML2?  Would 256 get better performance, more hashes etc?
• Does setting the difficulty mean it is fixed, or is that just a recommended start point?

[blockchain49er]

I ordered 2 Moonlander 2 and have them hashing. The problem is that no matter what I do one of the sticks have an error rate of 5-10%. I've tried modifying clock settings, different USB ports, different computers, powered USB hubs, etc.

One stick is <.5% error rate and the other is 5-10% consistently. I've gone as low at 600MHz and as high as 796 each with similar results.

I've purchased directly from the developer on eBay. Not sure if I have a defective unit or I need to tweak the pots maybe?

Interested to hear any ideas on how to troubleshoot this.

[mdtrav]

I ordered 2 Moonlander 2 and have them hashing. The problem is that no matter what I do one of the sticks have an error rate of 5-10%. I've tried modifying clock settings, different USB ports, different computers, powered USB hubs, etc.

One stick is <.5% error rate and the other is 5-10% consistently. I've gone as low at 600MHz and as high as 796 each with similar results.

I've purchased directly from the developer on eBay. Not sure if I have a defective unit or I need to tweak the pots maybe?

Interested to hear any ideas on how to troubleshoot this.

Could be your powered hub, I have issues with my junky amazon basics hub if I try to go too high on power.

You pretty much need a powered hub for these guys.

[lennyNO]

hi, its my case

Yes I know Have you got it all working yet? Last time you were waiting for cables and fans...

its designed to use short USB cables to connect to the hub. this way you can use every port of the hub no matter how close spacing is.

I hope you have control over the resistance of the powerwires in these usb bridge cables!! A 30cm cable can have as much as 0.2Ohm. I am running at 924Mhz and at that clockspeed may draw 2-3A. 0.5V voltage drop is a lot, it can be make or break.
Also you would be burning another I^2*R = 1.5W/MLD is dissipation per jumper cable alone! Below 800Mhz of course it ends up noticably less. Good for you, not for me hehe.

If you are in the US, you can order anything cheap and at no or minimal shipping cost, but where I live I have to import everything meaning high shipping costs and importduties. It's crazy. So I try to avoid it if I can.  Impossible to get short bridge cables here locally.

so if you got someone with a 3d printer close to you - this is a nice solution - and you can use all your usb hub ports in the way you like

Yes neat. I will probably try to make something from simple materials. Step by step. I have seen videos on youtube of people putting a L3+ into a cooler boxes, and that's probably the route I have to go, I need to get the fan noise down, temp down, and make it easy to move around. I have 11MLDs and like to keep it simple as possible. I don't have a garage like the other guy!

[lennyNO]

I ordered 2 Moonlander 2 and have them hashing. The problem is that no matter what I do one of the sticks have an error rate of 5-10%. I've tried modifying clock settings, different USB ports, different computers, powered USB hubs, etc.

One stick is <.5% error rate and the other is 5-10% consistently. I've gone as low at 600MHz and as high as 796 each with similar results.

I've purchased directly from the developer on eBay. Not sure if I have a defective unit or I need to tweak the pots maybe?

Interested to hear any ideas on how to troubleshoot this.

1) What happens if you put the 'bad' stick into the usb port where you otherwise have the good stick, and only run one stick. Do you then still see the same problem???
2) Run at the very lowest clock frequency, 384Mhz. Try again. Do you still get the problem?

If 1) solves the problem you have a powersupply issue. It is not always given that you can run 2 MLDs on one PC, it depends on how the ports are powered. (and in any case there is a limit to the powerdraw even on one port, depends on type of PC). Even powered hubs are not very reliable, unless you get the seriously heavy duty ones.

If 1) makes no difference, but 2) solves the problem, yes maybe something isn't right with the pots and you need to turn the one for the MLD with the higher hw rate a bit up (especially if not only the core potmeter).

Good luck!

[TimBuck2]

I’m so lost right now. I’m helping my 10 year old son build a rig with a Moonlander 2 on a RPi3.... I’m running at a 100% HW..... it just showed up in the mail today... first , I’m sorry to attach this to your post... I’m so new I don’t even know how to start my own post... please help a dad who’s trying his best.... thanks

First, are you running the USB Miner on a external powered USB hub and not just sticking it in the pi3? If you are trying to just plug it into the pi3 USB port you will never get anywhere since the power the pi3 provides is nearly 0

Second, if you are using an external powered USB hub, describe the one that you are using. It seems as though the majority of the problems arise from inadequately powered USB hubs.

Third, if all the above is good to go, what are the parameters you are using in the command line - mainly what is the core frequency that you are setting?

[jstefanop]

I ordered 2 Moonlander 2 and have them hashing. The problem is that no matter what I do one of the sticks have an error rate of 5-10%. I've tried modifying clock settings, different USB ports, different computers, powered USB hubs, etc.

One stick is <.5% error rate and the other is 5-10% consistently. I've gone as low at 600MHz and as high as 796 each with similar results.

I've purchased directly from the developer on eBay. Not sure if I have a defective unit or I need to tweak the pots maybe?

Interested to hear any ideas on how to troubleshoot this.

Try raising the memory and core voltage. Also some units do show higher error rate, but does not actually affect the hashrate (i.e. the uart controller sometimes spits out garbage, but all the "real" shares still come out properly). Are you also seeing a corresponding 5-10% drop in hashrate?

[jstefanop]

I think I had one of mine die sometime this morning -- it shoes 100% HW error rate at 700mhz. It hashes at like 83.2kh and constantly stops hashing/restarts.

This is a completely different unit than the one I mentioned a few posts ago.

What frequency were you running it before it died?

700mhz, highest I've ever run it was 756mhz.

I’m so lost right now. I’m helping my 10 year old son build a rig with a Moonlander 2 on a RPi3.... I’m running at a 100% HW..... it just showed up in the mail today... first , I’m sorry to attach this to your post... I’m so new I don’t even know how to start my own post... please help a dad who’s trying his best.... thanks

Are you running it directly off the pi? If so thats the issue...the pi itself can't provide enough power for these. Otherwise try lowering the clock down to base 384 frequency and see if your still getting 100% errors. If you have a windows machine try running it on that to rule out issues with the stick itself.

[crawlingspleen]

quick question.

I have 1 stick that will hash just happy at 924, another won't budge past 796. Can I set them to run those frequencies on the same scrypt?