BTW; @jstefanop:
What i'd love to see in BFGminer / the MLD's if possible; a way to identify them. BFG sets them up as MLD 0, MLD 1, MLD 2.... etc. But there's no way of telling (as far as i am aware of) to figure out which stick is MLD 0 or MLD 1 etc. Troubleshooting can be made so much simpler with unique ID's. After a reboot, the ID's get swapped now so MLD 0 could then be MLD 2 etc. I know that my gridseed dual miners had unique ID's, so if you plugged them in 1 at a time, you could make a note of which ID that miner had and if there ever was a problem you knew exactly which miner to fix.
Moonlanders have UIDs as well. Just press "M" while its running, then select the device number you want, and it will show its ID under serial number. You can then match the last couple digits to the actual serial number sticker on each device.
Hehe, if it was that easy: I regularly have that bfgminer fails to recognise the type of device and thereby extract the serial number, BUT it still hashes away!
I also used the bfgminer debug mode to look in more detail and see it happens when the usb/com ports are pinged. It finds the port but not what is attached to it. Still it starts hashing, without knowing what is attached to it.
Next update will also have enable/disable functions implemented, so that will be another way to quickly check which is which since toggling enable/disable will cause the LEDs to flash.
I have something weird: I have one MLD flashing red LED but it doesn't show up in bfgminer!! That means it kept hashing but probably got disconnected from bfgminer. It is not in bfgminer anymore, bfgminer is one MLD short. I don't know when it happened or how it happened. I am not sure exactly which physical device it is. Later today I will just restart bfgminer and it probably will get connected again.