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

I am only running 1 stick

Yes. Try running just one at a time and see if it still does it.

https://image.ibb.co/kpUWc6/error.png

Am I getting errors? If so why? I've not done anything to the stick. No mods or anything. . Does it look alright to you guys?

so far i've got the three running at a solid 4.30mh/s each with an avarage of A:1600 and R:5 HW:550/.55% with clock speed at 756 within a 12 hour time frame just close to stock settings. I would think I would be able to max them out since the hub claims it can support the voltage and amps.we shall see in the future.

If I want to add more sticks, do I need to add a worker for each stick? If so how do I add the new workers to the mine?

How fast can you run them on that hub?

Really!? Interesting - that a Pi3 ? Any special settings?

No - I was thinking current draw (amps) maybe using something like this:
https://rover.ebay.com/rover/0/0/0?mpre=https%3A%2F%2Fwww.ebay.co.uk%2Fulk%2Fitm%2F162705351062

I currently have 1x Moonlander running at 796 from USB 3 port - 1.93A at 4.55V - 4.52MH/s.

Should I be aiming for 5V on my USB meter?

I currently have 1x pi running at 796 from USB 3 port - 1.93A at 4.55V - 4.52MH/s.

Should I be aiming for 5V on my USB meter?

Has / can anyone here share some accurate readings of current draw (with stock voltage settings) of these moonlanders.

I have a pluggable 7 port USB 3.0 hub, this one:
https://plugable.com/products/usb3-hub7bc
It has a 60W power supply.

I have 5x moonlanders connected to it running at 756 clock speed and it has a reading (at the main socket for the hub alone) of 53.08W which seems wayyy to high.

I saw in the OP that these should use 1.3W per hash.  Now for a 756 clock speed, this gives 4.278mh (which is what i am seeing) but then a watt usage of around 5.56W (current draw calc to be 1.11amps) and if I have five of them this should be around 33watts but i am actually seeing nearly double at 53watts.  I know PSUs are not 100% efficiency but thats too much loss - something isn't right.

I guess what would be mega useful is a full rundown of all the clock frequencies and the current for each one like:

Clock
384
450
480
540
576
600
612
625
636
648
660
672
684
700
720
744
756
768
796
832
852
876
900
924
954

anyone fancy trying it?

It would be really useful as this would allow more people to get stable frequencies depending on the device they where connected to (I was hoping to try one connected to a Pi3 usb port but that is limited to 1.2a max total).

I have 2 of these. Does anyone know how to edit whatever needs edited for Windows 10 to run another miner? I have 1 running right now for about 6 days with no problems. I think they’re great!
(BTW this is my first post ever on any forum)

so you need the a foolproof copy n paste "just get it to work" description?

i'll write a short version for you that is most probably not perfect - but will most probably work.


Login to your raspberry pi with putty. (if this already is a problem - let me know). - you can as well login locally if you got keyboard and screen attached!

install neccesary library files (thanks to jstefanop for providing this info)


 this will create a directory in your home directory for bfgminer.
now you are in the new folder with the name "miner"

this will download the precompiled (ready to run) bfgminer from jstefanop.

now lets unpack this tar.gz file - this is a zipped tarball (something like a .zip file in windows - atleast similar)

now theres running lots of text of the files being unpacked into a folder.

lets go into the new unpacked folder!

here is the complete bfgminer including a short startup script from jstefanop.

now you can either edit the existing start script by using editor of your choice - i am using nano.
and change the pool, the username (after -u) the password (after -p) and save the file again
or depending on keyboard layout.

now thats its saved - quit the editor.
or
you are ready to do a test run!
now bfgminer will start (hopefully).

if you dont want to edit existing config you can as well try this:
in this line you change the pool - the username - the password option.
this will create a new file called "startmoonlander.sh" with your options - which can be modified later.

this file cant be used right now cause it is not executable. lets change that!

and now you can try your new startup script!

if you encounter any errors - describe them as good as possible or show us a screenshot and i bet - we will find a solution!

Greetings - Astrali