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.
Topic: Official FutureBit Moonlander 2 Driver and Support Thread - page 88. (Read 71760 times)
I'd imagine you just need to modify your batch file so that it only points at the correct serial port instead of all, then the bogus one won't be showing there.
Woot worked u rock ty 4 your help
I'd imagine you just need to modify your batch file so that it only points at the correct serial port instead of all, then the bogus one won't be showing there.
y is only one of my mdls working
only have 1 miner
So which is it?
only 1 miner so only 1 mdl ok ...... so y is it showing 2 and 1 is 100% error
if im just being stupid cause this is my first miner just tell me .... im just a lil confused by what mine is doing and what the ann says it supposed to do sry
y is only one of my mdls working
only have 1 miner
So which is it?
said it runs stable at 800 on presets its all set to default 600 speed and all
Still doesn't mean you have enough power either. Have you ran them individually?
only have 1 miner
said it runs stable at 800 on presets its all set to default 600 speed and all
Still doesn't mean you have enough power either. Have you ran them individually?
y is only one of my mdls working on yours it shows both r hashing i just plugged it in and this is what i noticed
error im getting
Because one of yours has 100% hardware errors. Try lowering the speed first. If that works then try raising core voltage some at the speed you are using now.
said it runs stable at 800 on presets its all set to default 600 speed and all
tried all 5 speeds under still the same
https://i.imgur.com/siRsDXV.png
y is only one of my mdls working on yours it shows both r hashing i just plugged it in and this is what i noticed
https://i.imgur.com/GQJtZWt.png
error im getting
y is only one of my mdls working on yours it shows both r hashing i just plugged it in and this is what i noticed
https://i.imgur.com/GQJtZWt.png
error im getting
Because one of yours has 100% hardware errors. Try lowering the speed first. If that works then try raising core voltage some at the speed you are using now.
y is only one of my mdls working on yours it shows both r hashing i just plugged it in and this is what i noticed
error im getting
Stock cooling solutions is good up to ~800 MHZ, after that you get into overheat territory (not to mention parabolic increase in current draw). The buck and ASIC can handle max frequency but I wouldn't run them unless you can measure temperature and its under 80C on the top of the small heatsink (translates to about 90C ASIC core). Anything past that your reducing the lifetime of the ASIC/buck. This will be even worse if you have a bunch of them together (since they are sucking each others hot air).
At 600Mhz they were fine, but at 796Mhz (at stock pot settings) I thought they were getting really hot, I got not hold my finger against the heatsink for more than maybe 10s (so I guess around 50Centrigrade or so). So in came the fans, that helped a lot. I then went up to 832 (adjusting core and memory by about 1/8th of a turn) and although they got a bit warmer again, it feels totally ok, maybe 40C. max. Tomorrow I will increase to 852Mhz, just to keep somewhat up with the rapidly increasing difficulty. But I don't want to sacrifice lifetime for just a further few percent increase in hashing power.
I bought two and went to set them up on my Macbook Pro (running High Sierra and I followed the instructions on how to install the driver) and I am able to get one Moonlander mining but the other one keeps giving me the error message, "device not configured." How do I actually configure the device?
Ahm, yes, it´s ancient hardware indeed. But it´s what I have and it consumes very little power, about 10W.
It has just 512MB RAM and therefore W7 should not be supported.
So no other XP users here? Really?
Any good reason to not run Linux on it?
Anyone here running bfgminer on Windows XP? I really need that to work here.... But just stuck on 99% CPU workload.... Is there any alternative to bfgminer?
That's some ancient hardware you're running there. Upgrade to Windows 7 or 10? Licenses are cheap on eBay. I doubt jstefanop tested on Windows XP, nor should he have to. Maybe you can research how to compile the bfgminer source manually and it will work better for XP. Upgrading your OS will actually be easier to do IMO.
Ahm, yes, it´s ancient hardware indeed. But it´s what I have and it consumes very little power, about 10W.
It has just 512MB RAM and therefore W7 should not be supported.
So no other XP users here? Really?
I was on XP 32bit, but just switched over to a Raspberry Pi this week. Feel free to PM me with questions, although I'm not sure I'll be able to help much.
Anyone here running bfgminer on Windows XP? I really need that to work here.... But just stuck on 99% CPU workload.... Is there any alternative to bfgminer?
That's some ancient hardware you're running there. Upgrade to Windows 7 or 10? Licenses are cheap on eBay. I doubt jstefanop tested on Windows XP, nor should he have to. Maybe you can research how to compile the bfgminer source manually and it will work better for XP. Upgrading your OS will actually be easier to do IMO.
Ahm, yes, it´s ancient hardware indeed. But it´s what I have and it consumes very little power, about 10W.
It has just 512MB RAM and therefore W7 should not be supported.
So no other XP users here? Really?
Is there a way to display the info form the bfgminer software on a I2C connected LCD display.
Like the PiMiner solution to a Adafruit LCD display.
If possible in easy code
Thx in Advance
Like the PiMiner solution to a Adafruit LCD display.
If possible in easy code
Thx in Advance
Today I got a voltage meter that I plugged my USB hub into to measure the overall energy consumption of the MLDs over time.
I got a KillAWatt myself and introducing this device doesn't change anything for me. The simplest answer for you though is that the voltage meter is causing some sort of issue. If you don't use it, your setup works correctly? If so, then maybe it is a defective USB meter? Is it a generic from China, or a well known brand like KillAWatt?
Set the dial to 20 (clockwise 1 step) and it should work.
this can measure from 0 up to 20V
and then place the pins on the points stated in the "tuning" section
this can measure from 0 up to 20V
and then place the pins on the points stated in the "tuning" section
Thanks. I tried placing the black & red on each metal side but I get unreliable readings. Maybe it is a cheap multimeter, IDK. I got it free from a friend, but maybe I need to invest in a thermal gun and multimeter. Thanks for validating that I wasn't doing anything wrong...
When I reboot my pi, it reassigns all USBs ttyUSB0 becomes 2, 4 becomes 8.....etc....
Any idea on how I can lock them down to their # even after reboot?
Any idea on how I can lock them down to their # even after reboot?
Kind of a wonky suggestion, but are the ML1 and ML2 on different hubs? If you power off one HUB, then the others should be recognized sequentially? Then after the first set is running, perhaps you can turn on the other hub and have those USB devices recognized in the next set of sequences.
Thanks for this warning. I would have thought the MLD would recognize by order placed in the USB HUB, but it sounds like it is more of a first come first served type of situation? Not sure how far bfgminer forked from cgminer 4.10, but cgminer 4.10 lets your blacklist USB devices for a particular instance... so conceivably you could run two instances with specific hardware tied to each instance. The Manage Devices on bfgminer is very different from cgminer 4.10 though.
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#
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#
Jump to: