When is Batch 3?  Seriously. . I'm kinda tired of getting rheemed in the keister by eBay scalpers. . THe cheapest one I found today was $16o . . pfft. . Sorry guys, once batch 2 stock hits at the end of the month there will be plenty of stock for lower pricing than what these are going off ebay. Unfortunately demand is still high so in stock units have to be priced accordingly (somewhere between pre-order pricing and ebay pricing). We needed at least two batches to gauge demand, so going forward I should be able to have a steady output to meet demand each month. We might do one more pre-sale batch 3, but after that it will be steady production. (FYI Asicpuppy put leftover $64 batch 2 pre-order stock from cancellations etc so here is your chance to pick one up super cheap if you havent https://asicpuppy.com/magentoPuppy/index.php/fbmoonlander2preorder.html ) |
|
|
|
I'm trying to setup the usb key ith latest macos ; i followed all the instructions , i can see the device in /dev/ , it flashes when i start bfgminer ( both yellow and red leds , i had to start with administrative rights ), but then i get the following message : NO DEVICES FOUND: Press 'M' and '+' to add and no way to add device(s) cfr: https://www.dropbox.com/s/ny17lbdjx1l3vuv/Screenshot%202018-01-04%2018.47.05.png?dl=0any hint ? no support in bfgminer did you download jestanop's drivers? I am pretty sure they need to be his drivers and not bfgminer's 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=0Your first issue is that your trying to connect to slushpool, which is a BTC and not LTC pool. If your on 10.13 check to see if the UART port is loaded. Open terminal and type cd /dev ls cu.* you should see something like cu.sililabs, if not you did not do the 10.13 UART driver workaround install correctly. |
|
|
|
Yes the stock heatsink is not designed for fanless operation. Even at base frequency and lowest voltage you risk overheating with no airflow.
Keep in mind those little fans have about 2cfm coming out of them, so you can easily get a ultra quiet 120mm fan and that will provide more than enough airflow at close range to keep it cool with very little noise. If your going this route I wouldn't do it unless you have a heat gun and can directly measure the temp of the small heatsink on the top (should be under 80c max).
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!! Small heatsink is the tiny one that sits on top of the ASIC...this will be the hottest part and is the best point of measurement. |
|
|
|
I'm a complete mining newbie.
Can anyone point me to instructions how to operate the moonlander silently?
Which settings etc...?
Or even without fan?
Hashrate is not so important for me, but it should be as silent as possible.
Thx in advance & sorry for the strange question.
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. Yes the stock heatsink is not designed for fanless operation. Even at base frequency and lowest voltage you risk overheating with no airflow. Keep in mind those little fans have about 2cfm coming out of them, so you can easily get a ultra quiet 120mm fan and that will provide more than enough airflow at close range to keep it cool with very little noise. If your going this route I wouldn't do it unless you have a heat gun and can directly measure the temp of the small heatsink on the top (should be under 80c max). |
|
|
|
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  It works, but initial diff for nicehash is like 64K + so it could take hours to submit shares. As long as bfgminer is showing that the sticks are hashing you'll have a chance to submit a share, it will just be very slow. If your mining on there over the course of months it wont matter since over a long time you'll submit enough shares that your average hashrate will be what its supposed to be, but if you like watching "Share Submitted" nicehash(and other pools that don't have lower diff ports) is not your best bet. Im sure if enough of you open tickets with them they will open a "low-diff" port. thanks for your reply. what should be the optimal diff for the moonlander on your opinion? For a single moonlander 256-2k diff is a good range. Anything higher/lower will produce too fast/too slow shares. Don't forget that it does not matter what diff your connected at the pool in terms of performance/payouts, its just your variance is greater the higher the diff which averages out over time. |
|
|
|
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 It works, but initial diff for nicehash is like 64K + so it could take hours to submit shares. As long as bfgminer is showing that the sticks are hashing you'll have a chance to submit a share, it will just be very slow. If your mining on there over the course of months it wont matter since over a long time you'll submit enough shares that your average hashrate will be what its supposed to be, but if you like watching "Share Submitted" nicehash(and other pools that don't have lower diff ports) is not your best bet. Im sure if enough of you open tickets with them they will open a "low-diff" port. |
|
|
|
These have been working great for me on litecoinpool.org, mine have been going for over a week now without any issues. I was thinking about trying out prohashing.com, anyone mining there with these? What do I need to enter in the start_moonlander2 file for prohashing (I have three sticks if that matters re: difficulty)? Thanks as always  Would just changing: stratum+tcp://us.litecoinpool.org:3333 to stratum+tcp://prohashing.com:3333. work? Yes...you just need to update pool URL and login credentials (if they are different). |
|
|
|
Currently out of stock.Any info when next batch gonna be available?
Batch 2 is in production, so if you got in on Batch 2 pre-order you will get them end of January. Distributors will have additional stock that will be selling for retail price into February. Check out the order thread for info on stock/ordering. |
|
|
|
|
@michelem does your Network L3+ API access require default SSH passwords? Looks like minera is detecting the L3+ correctly, but getting access denied on "addpool" api call.
|
|
|
|
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 It does not get detected at all? Does it show up on the USB port/COM ports? on windows - i see no action at all. on my raspberry pi i get this from dmesg: pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected
this is what i get in dmesg when i attach my 4th moonlander from eyeboot. ideas whats causing this? lsusb won't find the device neither it will be seen by bfgminer Green light on, fan is running! Yea sounds like the USB input port on the chip got fried. Most likely by an ESD discharge on that extender cable. Since I have had zero reports of anyone randomly frying their sticks yet (other than the unfortunate guy that plugged them in a 12v instead of 5v power source), shoot me a PM and send it back to me...I want to dissect it in the name of science and ill repair it for you. |
|
|
|
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! Solo mining is not support by bfgminer for scrypt mining. You can still do it, but you would need to setup a proxy thats connected to the coins RPC wallet, and then connect bfgminer to the stratum proxy like a normal pool. Here is a good stratum proxy that has litecoin support. Of course its a bit involved to setup, but this is the currently only working solution to solo mine scrypt. https://github.com/pocesar/node-stratum/ |
|
|
|
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 It does not get detected at all? Does it show up on the USB port/COM ports? |
|
|
|
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?
Batch 2 pre-order is now sold out! Production for Batch 2 is still on schedule and deliveries will be beginning end of January and into February. If you missed batch 2 pre-order, Batch 2 in stock units will be available end of January. |
|
|
|
This is a power related problem, sounds like your having cores drop in certain sticks due to too high frequency/power draw. Anything past 796 MHZ on stock core voltage your going to have issues, which is what your seeing. You need to turn up core voltage if you want to run past 800 mhz.
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. Yea if you are using eyeboot's hub its definitely the hub. While they are great hubs, he uses power supplies that are on the cheaper end for 5v, and I'm not sure if the USB chips he uses can handle the number of ports he has that well. I've seen similar strange behavior since I use his hubs for rapid testing. 63 cores is what its supposed to show if all your cores are healthy (Core# 0-63). |
|
|
|
are there any left?
Check out the order thread linked in OP, Batch 2 is mostly sold out but some distributors still have a few left. |
|
|
|
try to double the worker difficulty pool side..
what i found is if its too low, the usb gets saturated somehow and it cant keep up..
im not sure how to calculate scrypt worker diff, but its multiplied.. so 62m would be like d=4096 or something. that might actually be too high..
anyways yes the red lights flash on diff 1, which is internal.. only the yellow lights flash when a worker diff share is found. this is what's transmitted to the pool.
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. This is a power related problem, sounds like your having cores drop in certain sticks due to too high frequency/power draw. Anything past 796 MHZ on stock core voltage your going to have issues, which is what your seeing. You need to turn up core voltage if you want to run past 800 mhz. |
|
|
|
Hey Guys, happy holidays!! I'm setting up a 4 of these guys for a friend. The latest drivers seem to install successfully. I left the Start_Moonlander2 batch info as is, just to test that everything was working correctly, before I edit the pool info.. It doesn't seem to start mining, the command window comes up and when i press 'any key' it closes without really getting into the bfg miner window. Any ideas?  Guys you really need to start reading the first 3 posts (that included the FAQ section which has the answer to this question) in this thread before posting. The thread is already over 30 pages long and does not need to be cluttered with posts like this. Your wasting your own time by not reading the basics first, and making it hard for people with real issues to find an answer. Q: Im using windows and nothing happens when i click the start_moonlander.bat file
Your anti-virus software most likely deleted bfgminer.exe when you extracted it. Make sure you setup a rule so it does not do this. |
|
|
|
pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected
this is what i get in dmesg when i attach my 4th moonlander from eyeboot. ideas whats causing this? lsusb won't find the device neither it will be seen by bfgminer Green light on, fan is running! Greetings - Astrali That’s the error you usually get when you are using too long/bad extenender. Have you tried plugging that one into another port/PC? i had device in a 20 cm long cheap extender - but now i get same error when i plug it directly in my hub where all the others went fine. (remove 1 of 3 - plug this one in - only 2 work - remove this one and put back other one - all 3 work). (3x Bitshopper moonlander 1x Eyeboot Moonlander). The eyeboot one worked before on low mhz (600) on my windows pc on a long extender directly at an usb 3.0 port. windows doesnt recognize it as well anymore  did i lost 1 baby? Doubt an extender could fry it unless it was internally shorted. If you plug it directly into USB port do you get the same error message? |
|
|
|
pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected
this is what i get in dmesg when i attach my 4th moonlander from eyeboot. ideas whats causing this? lsusb won't find the device neither it will be seen by bfgminer Green light on, fan is running! Greetings - Astrali That’s the error you usually get when you are using too long/bad extenender. Have you tried plugging that one into another port/PC? |
|
|
|
i ordered an overall of 4 miners - 3 from Bitshopper.de and 1 from Eyeboot.com Could any of you give me an idea how i could run 2 miners in 1 process and 2 miners in single mode on same raspberry? like this: bfgbimer_double.sh (miner 1 +2) bfgminer_single1.sh (miner 3) bfgminer_single2.sh (miner 4) cause i dont want all to mine on same pool with same username. (miners not arrived yet - but most probably first 3 will arrive over the weekend). Thanks Is this doable in Windows? I have 3x Moonlanders and would like to run them separately, it’s easier to rent out in smaller blocks. Yes, just change -S all to -S /dev/USBx where x is the USB number for a single moonlander. If you want two in one instance do something like -S /dev/USB0 -S /dev/USB1 etc... For windows use the \\.\COMx format |
|
|
|
|
Show Posts
