@jstefanop Is there any news about the pre batch 2 delivery date...

If ML2 is recognized when directly plugged in, how is this an ML2 issue?

Do you have a different computer which you could try attaching USB HUB to? For a USB HUB to be recognized, make sure you have no devices attached to it. Attach USB HUB solo to your computer and see if it is detected. After USB HUB is detected, then you attach other USB devices to it.

Does anyone know what the error "FutureBit Write error: Device not configured" means?

Every once in a while, all ten of my ML2 will stop hashing and give this error repeatedly every second.

Not sure about misbehaving, but you can get rid of that password argument, that will tell it to only mine Verge (you want it to mine whatever happens to be the most profitable at the moment). You can still take 100% of your payout in Verge.

Seriously. . I'm kinda tired of getting rheemed in the keister by eBay scalpers. . THe cheapest one I found today was $16o . . pfft. .

I followed all instructions reported in 1st message of this thread, even the workaround for macos 10.13
The result is that the port seems active but the bfgminer ( the one included in jstefanop package ) does not see the device , that seems correctly installed

cfr:
https://www.dropbox.com/s/wj1y44z3puw09u8/Screenshot%202018-01-04%2019.45.57.png?dl=0

Thanks for the info, I was thinking (for the other guy) that one may get away with it at lowest core/mem voltage/freq but I believe you if not. Yes I will get the IR temp meter from work, currently I am measuring anywhere between 30-40degs on the heatsink that is on the component side of the PCB (other side than stock fan), that's at 832Mhz. I have some others at 900Mhz but can't measure those as easily without the gun. I assume by small heatsink you mean the one that is where the minifan is?

This is in fact what I enjoy soooo much about the MLD2, the way we can tune and customize and play with it. That's just so much fun and awesome. So, great job!!

sell it to me  it will be completely silent


To be serious  it needs a fan.  So I think  you won't have silence.

Even if you set  low settings it would over heat.

I suppose if you attach a monster heat sink it could work silently.

thanks for your reply.
what should be the optimal diff for the moonlander on your opinion?

Hi, is therae also NICEHASH Support on that bfgminer for Moonlander? I didn't get a connection to nicehash with 5 Moonlander connected to Raspi/Minera+bfgminer-5.4.2

Would just changing:

stratum+tcp://us.litecoinpool.org:3333

to

stratum+tcp://prohashing.com:3333.

work?

Currently out of stock.Any info when next batch gonna be available?

on windows - i see no action at all.
on my raspberry pi i get this from dmesg:

Hi all,

I received my Moonlander 2 via HolyBitcoin.com this afternoon and it works great out of the box. I set up a hash-to-coins.com account as per TimBuck2's suggestion and while pool mining is a breeze with bfgminer, I get "invalid address" errors when I try to solo mine new/small scrypt altcoins like I would with cpuminer. I've searched this thread and haven't come across specifics on this - any suggestions? Or can I hash with cpuminer via my Moonlander? Thanks!

i still got my most probably partial fried moonlander that doesnt get proper detected ..

i admit it will most probably have been my fault cause 1 cable on my usb connection got loose in the extender i used (seen that later).

is there any way to check whats broken on the device or repair it?
or is it an 1 ltc decoration element now?

would be happy to hear any ideas.

i dont blame anyone but myself!

Thanks - Astrali

Anyone know what is up with asicpuppy site?  Moonlander 2 are no longer listed?

Luckily I got in on the pre-order last week, but I would expect the site to say 0 available, not have the item completely missing from inventory.  Maybe it is being updated?

jstefanop, thanks for your feedback. Yeah I have adjusted core/mem since long. It seems more complicated than that. As I wrote, I had what semeed 2 culprit MLDs, when I finally identified them and moved them to different USB sockets, the problem came on two different MLDs. Uncertain if the same USB sockets as before. I had 6 units run at 952Mhz (with adjusted core/mem) no problem whatsoever. I received a last batch of 5 from you last friday (but I did not write down which serial numbers they were), since then it's a problem. Yes, I have turned up core/mem on all units.

I monitor HW errors, and they never exceed 1-1.5%, usually less < 1%. I would think that if core voltage is too low that would be the first that shows up? So I have a hard time seeing that it is pot settings.

I also noted that bfgminer has (sometimes) difficulty recognizing the type and serialnumber of some of the MLDs and it may require a restart of bfgminer before these fields are properly populated. In the debuglog there is an error related to this "Failed to ioctl in lowl-vcom.c ..."

I also noted that on initial startup, the function futurebit_coretest reports 63 cores on all devices, not 64 which I thought was interestesting. ALL report 63.

I am still suspecting it may be something to do with the USB hub (even if it is good one), I have now been running back at 832 all night without any problem on 11 MLDs. I will now again split in two, and one by one add COM ports to the set that I want to run at 900Mhz and try to push this as many as possible. I probably start with the 6 COM ports that never gave me a problem when I only had 6 units.

are there any left?

I went all the way up to 500m (normally the starting value with vardiff), d=32875 or so, but it did not help, still getting the same problem.
I also tried lower and lower frequencies (not changing the core/mem voltages), at 600Mhz no problem, at 832Mhz no problem, at 856 problem but took some time, at 876, 900Mhz: problem.
I looked at the source code and I also enabled debugging, but the latter did not help me much. Unless jstefanop pitches in I need to look more closely at the source code. But as long as I am running with 10.5 MLD I won't be messing around too much.