Anyone have a list of what USB hubs these will run correct speeds on? Really want to get these little frustrating things working.
Mine run OK with an Orico 10 port metal hub. I also run a couple of gekkoscience compac on the same hub. 
Topic: [ANN] FutureBit MoonLander: A Modern and Efficient Scrypt USB Stick Miner! - page 5. (Read 30579 times)
May 10, 2016, 12:24:00 PM
May 06, 2016, 03:20:38 PM
Hi guys,
Awesome job jstefanop. Is this still available for purchase?
Awesome job jstefanop. Is this still available for purchase?
Im sold out of the last batch...my resellers Asicpuppy and holybitcoin (bitshopper.de if your in europe) might still have a few left.
May 06, 2016, 03:15:37 PM
Hi guys,
Awesome job jstefanop. Is this still available for purchase?
Awesome job jstefanop. Is this still available for purchase?
May 06, 2016, 01:01:38 AM
Anyone have a list of what USB hubs these will run correct speeds on? Really want to get these little frustrating things working.
I am running 8 on 2 superbpag 7 port hubs. They are running at 304 and take amlost 1.6a and are set to about .9v
Most hubs cap out at .9a which is only good for around 240 or so.
yes im running them on linux with minera.. but that hub also works in windows 10 with no issues.. besides the regular issues.. i cant get them to run for more then 30 minutes before they start shutting off one by one.
May 06, 2016, 01:00:27 AM
i have that hub and it wont even initialize mine..
the blue lights on the hub just blink?
May 05, 2016, 10:52:40 PM
May 05, 2016, 05:57:41 PM
Anyone have a list of what USB hubs these will run correct speeds on? Really want to get these little frustrating things working.
I am running 8 on 2 superbpag 7 port hubs. They are running at 304 and take amlost 1.6a and are set to about .9v
Most hubs cap out at .9a which is only good for around 240 or so.
May 02, 2016, 01:39:32 PM
it seems 2 of my sticks are holding me back.
i can run 6 of them at 320 @ .9v with only 1 or 2 hwe per hour and they are spot on the rated speed.. 320x2.77= 886.4
if i add the other 2 they produce about 10 or so hwe per minute and they only run around 500kh/s
lowering those 2 to around 256 make them happy.
there doesnt seem to be a way to set those 2 at 256 while the others are at 320 on the same hub.
i can run 6 of them at 320 @ .9v with only 1 or 2 hwe per hour and they are spot on the rated speed.. 320x2.77= 886.4
if i add the other 2 they produce about 10 or so hwe per minute and they only run around 500kh/s
lowering those 2 to around 256 make them happy.
there doesnt seem to be a way to set those 2 at 256 while the others are at 320 on the same hub.
Check out the FAQ, instructions are there and about every other question people keep asking over and over
May 02, 2016, 01:24:13 PM
it seems 2 of my sticks are holding me back.
i can run 6 of them at 320 @ .9v with only 1 or 2 hwe per 10 minutes or so (i still cant get them to run very long before one drops down to 0) and they are spot on the rated speed.. 320x2.77= 886.4
if i add the other 2 they produce about 10 or so hwe per minute and they only run around 500kh/s
lowering those 2 to around 256 make them happy.
there doesnt seem to be a way to set those 2 at 256 while the others are at 320 on the same hub.
i can run 6 of them at 320 @ .9v with only 1 or 2 hwe per 10 minutes or so (i still cant get them to run very long before one drops down to 0) and they are spot on the rated speed.. 320x2.77= 886.4
if i add the other 2 they produce about 10 or so hwe per minute and they only run around 500kh/s
lowering those 2 to around 256 make them happy.
there doesnt seem to be a way to set those 2 at 256 while the others are at 320 on the same hub.
April 30, 2016, 07:58:15 PM
out of the 8 of these i got. one is acting strange..
the red and orange lights stays on all of the time. (looking at the 8 i have 2 do this) it also produces 10x more hwe then the other 7.
ive settled on speed 288 with them all at or around .9v
6 of the 8 give zero hwe.. 1 gives about 10 an hour and this one is 100+
any ideas?
the red and orange lights stays on all of the time. (looking at the 8 i have 2 do this) it also produces 10x more hwe then the other 7.
ive settled on speed 288 with them all at or around .9v
6 of the 8 give zero hwe.. 1 gives about 10 an hour and this one is 100+
any ideas?
April 30, 2016, 04:22:05 PM
can someone tell me what the rated voltage and speed is for this chip? its the alcheminer scrypt-1?
i decided to try to crank these up, im at 304 speed at around .9v looking at the pot i put the flat spot on the left |O with the usb pointing down.
a few give me hwe but some are at 0..
i decided to try to crank these up, im at 304 speed at around .9v looking at the pot i put the flat spot on the left |O with the usb pointing down.
a few give me hwe but some are at 0..
April 29, 2016, 12:40:15 AM
Cool I will try a couple of them tomorrow.
Hi, received my 5 sticks and actually testing which multipool with low diff can be used to avoid sick problem :
- Ipominer https://www.ipominer.com/ : diff start at 64
- multipool.us https://www.multipool.us/index.php : diff start at 32
- Ispace http://scrypt.ispace.co.uk/ : diff start at 32 not tested yet
- Coinking https://coinking.io/dashboard : suggested minimum diff 64 not tested yet
too high diff pools : hash-to-coins, clevermining, coinotron, prohashing.
- Ipominer https://www.ipominer.com/ : diff start at 64
- multipool.us https://www.multipool.us/index.php : diff start at 32
- Ispace http://scrypt.ispace.co.uk/ : diff start at 32 not tested yet
- Coinking https://coinking.io/dashboard : suggested minimum diff 64 not tested yet
too high diff pools : hash-to-coins, clevermining, coinotron, prohashing.
April 28, 2016, 04:19:16 AM
Hi, received my 5 sticks and actually testing which multipool with low diff can be used to avoid sick problem :
- Ipominer https://www.ipominer.com/ : diff start at 64
- multipool.us https://www.multipool.us/index.php : diff start at 32
- Ispace http://scrypt.ispace.co.uk/ : diff start at 32 not tested yet
- Coinking https://coinking.io/dashboard : suggested minimum diff 64 not tested yet
too high diff pools : hash-to-coins, clevermining, coinotron, prohashing.
- Ipominer https://www.ipominer.com/ : diff start at 64
- multipool.us https://www.multipool.us/index.php : diff start at 32
- Ispace http://scrypt.ispace.co.uk/ : diff start at 32 not tested yet
- Coinking https://coinking.io/dashboard : suggested minimum diff 64 not tested yet
too high diff pools : hash-to-coins, clevermining, coinotron, prohashing.
April 25, 2016, 01:55:12 PM
FYI if you guys want a 100% sure way to test whether its a pool issue or something wrong with your computer/setup just run the script file with the --benchmark flag. This sets bfgminer in benchmark mode and does not rely on pool diff settings to test your setup. It essentially generates local work using a VERY low diff(lower than what a pool can do). This will produce about 30-60 shares a SECOND based on what frequency you set, so its a sure proof way to test everything is working correctly hardware side.
I use a variation of this method to test your moonlanders before I ship them out. It allows me to have the stick return thousands of shares in the order of minutes, which would normally take a pool hours/days to do, and can quickly identify issues with the ASIC/stick.
I haven't posted this before because it completely stresses out your system/stick, so don't try this on a RPi for example and get worried if something freezes up
I use a variation of this method to test your moonlanders before I ship them out. It allows me to have the stick return thousands of shares in the order of minutes, which would normally take a pool hours/days to do, and can quickly identify issues with the ASIC/stick.
I haven't posted this before because it completely stresses out your system/stick, so don't try this on a RPi for example and get worried if something freezes up
April 20, 2016, 03:44:20 AM
Quote
Yea sorry guys the sick issue is on my to-do list since I knew people would have a problem with it with var diff pools. I just figured most pools have options for really low diff or can be set manually. I guess I was wrong.
The problem with the watchdog logic is that it was originally written for GPU miners, and was designed for locked up GPU mining threads. A lot of that logic has to be rewritten for ASICs, and I was talking with Luke-jr about it but it was a lot of work at the time so never got around to it. At the very least Ill uploaded compiled version with longer timeouts as a "dirty" work around.
BTW adding a low diff port takes a pool operator a couple minutes and a few lines of code to do, so I would email them and tell them if its possible to set a port for low diff.
The problem with the watchdog logic is that it was originally written for GPU miners, and was designed for locked up GPU mining threads. A lot of that logic has to be rewritten for ASICs, and I was talking with Luke-jr about it but it was a lot of work at the time so never got around to it. At the very least Ill uploaded compiled version with longer timeouts as a "dirty" work around.
BTW adding a low diff port takes a pool operator a couple minutes and a few lines of code to do, so I would email them and tell them if its possible to set a port for low diff.
Great!!!.
I was reading the windows-build.txt at BFGminer folder, in order to do it by myself...
Not sure if possible for me...
Please let us know when new binaries are available.
I will like a lot to test MLs on more pools...
Thanks.
April 18, 2016, 01:58:14 PM
so i was checking these things out on a thermal camera and i think its the heatsink.
the chips are around 150F or so but the heatsinks are like 80F
you can clearly see the heatsinks are not as hot as the board.. and the chip is the hottest.
i might order some tiny heatsinks for the top of the chips and then double space them on the usb hub..
that means only 3 can fit per superbpag
the chips are around 150F or so but the heatsinks are like 80F
you can clearly see the heatsinks are not as hot as the board.. and the chip is the hottest.
i might order some tiny heatsinks for the top of the chips and then double space them on the usb hub..
that means only 3 can fit per superbpag
150F is nice and cool for these...I wouldn't worry unless temps go above 80c/175F on the ASIC itself. Of course it doesn't hurt to have more cooling...cooler ASIC=more efficient.
April 18, 2016, 01:46:13 PM
Yea sorry guys the sick issue is on my to-do list since I knew people would have a problem with it with var diff pools. I just figured most pools have options for really low diff or can be set manually. I guess I was wrong.
The problem with the watchdog logic is that it was originally written for GPU miners, and was designed for locked up GPU mining threads. A lot of that logic has to be rewritten for ASICs, and I was talking with Luke-jr about it but it was a lot of work at the time so never got around to it. At the very least Ill uploaded compiled version with longer timeouts as a "dirty" work around.
BTW adding a low diff port takes a pool operator a couple minutes and a few lines of code to do, so I would email them and tell them if its possible to set a port for low diff.
The problem with the watchdog logic is that it was originally written for GPU miners, and was designed for locked up GPU mining threads. A lot of that logic has to be rewritten for ASICs, and I was talking with Luke-jr about it but it was a lot of work at the time so never got around to it. At the very least Ill uploaded compiled version with longer timeouts as a "dirty" work around.
BTW adding a low diff port takes a pool operator a couple minutes and a few lines of code to do, so I would email them and tell them if its possible to set a port for low diff.
April 15, 2016, 11:03:26 PM
so i was checking these things out on a thermal camera and i think its the heatsink.
the chips are around 150F or so but the heatsinks are like 80F
you can clearly see the heatsinks are not as hot as the board.. and the chip is the hottest.
i might order some tiny heatsinks for the top of the chips and then double space them on the usb hub..
that means only 3 can fit per superbpag
the chips are around 150F or so but the heatsinks are like 80F
you can clearly see the heatsinks are not as hot as the board.. and the chip is the hottest.
i might order some tiny heatsinks for the top of the chips and then double space them on the usb hub..
that means only 3 can fit per superbpag
April 15, 2016, 02:21:31 PM
Quote
I found a workaround for this, if you're compiling bfgminer from source. Open up miner.c, and find the line that reads:
Code:
#define WATCHDOG_SICK_TIME 60
This is the timeout, in seconds, before a device is declared SICK. You can set it to any value less than or equal to 600, though I recommend setting it to a divisor of 600. (300 works well for me.) For example...
Code:
#define WATCHDOG_SICK_TIME 60
This is the timeout, in seconds, before a device is declared SICK. You can set it to any value less than or equal to 600, though I recommend setting it to a divisor of 600. (300 works well for me.) For example...
Thanks a lot for the info. Only problem is I have no idea about how to compile BFGMiner.
Maybe you can share your binaries? I need Windows binary... Maybe only needed the .exe file...
I will try anyway to recompile BFGMiner if no binaries available, but sure I will fail
About to damage ML, well I have four. I will test it with only one for a few days...
Not worried about this. If ML only works with LTC pools on low diff, they are not very
interesting for me.
Thanks again!
I don't have any way to build this for Windows, sorry about that...for Linux though, you can follow the excellent compile instructions in the OP and just change that line in miner.c before you run "make".
April 15, 2016, 12:00:41 PM
Quote
I found a workaround for this, if you're compiling bfgminer from source. Open up miner.c, and find the line that reads:
Code:
#define WATCHDOG_SICK_TIME 60
This is the timeout, in seconds, before a device is declared SICK. You can set it to any value less than or equal to 600, though I recommend setting it to a divisor of 600. (300 works well for me.) For example...
Code:
#define WATCHDOG_SICK_TIME 60
This is the timeout, in seconds, before a device is declared SICK. You can set it to any value less than or equal to 600, though I recommend setting it to a divisor of 600. (300 works well for me.) For example...
Thanks a lot for the info. Only problem is I have no idea about how to compile BFGMiner.
Maybe you can share your binaries? I need Windows binary... Maybe only needed the .exe file...
I will try anyway to recompile BFGMiner if no binaries available, but sure I will fail
About to damage ML, well I have four. I will test it with only one for a few days...
Not worried about this. If ML only works with LTC pools on low diff, they are not very
interesting for me.
Thanks again!
Jump to: