HashFast BabyJet users thread

[jerseyjon]

All fans start up with the power up and the back fan is the right way round, blowing air in over the card
the reboot switch, the pi and the laptop all have the same impact - a boot up for a couple of seconds and then a power down, off for a few seconds and then a power cycle back up again....repeat non stop.

So I assume that rules out the pi and the usb cable/fittings as it happens with no usb attached at all when using the manual reboot/on button on the card.

cgminer sees the device but errors out, tries to hot reboot but fails.

[1714779861]

1714779861

[1714779861]

1714779861

[1714779861]

1714779861

[1714779861]

1714779861

[1714779861]

1714779861

[freddyfarnsworth]

Well the good news is my Batch 1 BJ arrived in the uk - 48 hours door to door.
Looked in good condition, no obvious wires or screw loose - although there are only 3 screws holding down the water cooling to the chip.

I have booted up with both the Rpi with a wired ethernet and also a laptop running 3.12 cgminer. 

Either way, the BJ comes to life for about 2 secs, then switches off, then repeats this forever but the BJ does not get recognised by the Pi ot the laptop.
The reboot in the BJ card causes a reboot but it still switches off after a few seconds.

Has anyone got any ideas of where to look for issues?

Thanks

If you do not fix/find the missing screw, a tilted Heatsink would kill your miner, unless only designed to use three.
You better fix that, fast.
Others will jump in to tell you how many screws HS has on theirs I am sure.
Watching thread to learn about these machines.

[jerseyjon]

freddy
I think that is exactly the problem - even squeezing the 4th corner of the cooling unit together, get it working for a minute before a high temp warning, so it must be failing instantly with an overheat warning from the chip.

Now the only problem is how to get hold of the quite special screw - the screw and its backplate are missing off the 4th corner. 
Anyone know how I get hold of this type of screw quickly ? Is it a standard cooler available in the uk?

[Big Time Coin]

4 of my 12 BJ's had air blowing IN the radiator. The rest blowing out.

That might explain why some of mine are overheating... off to check.

[edgie13]

Any deliveries today?

[ImI]

Any deliveries today?

yes

[perezoso]

4 of my 12 BJ's had air blowing IN the radiator. The rest blowing out.

That might explain why some of mine are overheating... off to check.

The fans on top of my radiator are blowing out, but what's the proper orientation for the single fan on the back?  

It should be blowing out, no?  I have one that is sucking in.

[Big Time Coin]

I did find one that had both fans blowing in instead of out.  Also have one that has no front fan action.  It is hard to tell which way the front fans are blowing or if they are both blowing in the same direction, but the one with disabled front fans is not overheating, so I think front fans are pretty unnecessary.

Any easy way to check if both radiator fans are blowing out? Some feel stronger airflow than others when i place my hand near them, I am worried that some have mismatched orientations - since the fan-putter-on-ner obviously sucked sweaty monkey balls.

I had overheating problems mostly because 4 of the BJ were 6 1/2 feet up on top of a full rack, put them down on the floor and got a 20 degree drop in temps.

[Big Time Coin]

4 of my 12 BJ's had air blowing IN the radiator. The rest blowing out.

That might explain why some of mine are overheating... off to check.

The fans on top of my radiator are blowing out, but what's the proper orientation for the single fan on the back?  

It should be blowing out, no?  I have one that is sucking in.

Right, flip it, back fan blows out.

[xunknownx]

Con is there a way to show the temps of the individual dies without turning on debug?

Check API output. Plenty of info there.

Tried asc|1

STATUS=S,When=1391035500,Code=106,Msg=ASC1,Description=cgminer 3.12.0,ASC=1,Name=HFB,ID=1,Enabled=Y,Status=Alive,Temperature=0.00,MHS av=434726.40,MHS 5s=607976.58,Accepted=6839,Rejected=22,Hardware Errors=2950,Utility=23.64,Last Share Pool=0,Last Share Time=1391035498,Total MH=7545906066.6987,Diff1 Work=1756928,Difficulty Accepted=1750784.00000000,Difficulty Rejected=5632.00000000,Last Share Difficulty=256.00000000,No Device=false,Last Valid Work=1391035499,Device Hardware%=0.1676,Device Rejected%=0.3206,Device Elapsed=17358,


dev
STATUS=S,When=1391035718,Code=9,Msg=2 ASC(s) - 0 PGA(s),Description=cgminer 3.12.0,ASC=0,Name=HFB,ID=0,Enabled=N,Status=Alive,Temperature=0.00,MHS av=18080.34,MHS 5s=84166.69,Accepted=301,Rejected=1,Hardware Errors=125,Utility=0.98,Last Share Pool=0,Last Share Time=1391018115,Total MH=332052511.5110,Diff1 Work=77312,Difficulty Accepted=77056.00000000,Difficulty Rejected=256.00000000,Last Share Difficulty=256.00000000,No Device=true,Last Valid Work=1391018114,Device Hardware%=0.1614,Device Rejected%=0.3311,Device Elapsed=18365,ASC=1,Name=HFB,ID=1,Enabled=Y,Status=Alive,Temperature=0.00,MHS av=435529.15,MHS 5s=514642.31,Accepted=6939,Rejected=22,Hardware Errors=2987,Utility=23.69,Last Share Pool=0,Last Share Time=1391035712,Total MH=7654799950.7847,Diff1 Work=1782272,Difficulty Accepted=1776384.00000000,Difficulty Rejected=5632.00000000,Last Share Difficulty=256.00000000,No Device=false,Last Valid Work=1391035712,Device Hardware%=0.1673,Device Rejected%=0.3160,Device Elapsed=17576,

In these its just shows 0 for temp. Looked through other api commands, not sure where temp is. Will keep looking.

stats | grep temperature

Code:

   [die temperature] => 67.933594
   [board temperature] => 62.016445
   [die temperature] => 75.257812
   [board temperature] => 66.099457
   [die temperature] => 74.320312
   [board temperature] => 61.283451
   [die temperature] => 74.378906
   [board temperature] => 59.855595
   [die temperature] => 76.195312
   [board temperature] => 51.296085
   [die temperature] => 73.968750
   [board temperature] => 54.895332
   [die temperature] => 72.914062
   [board temperature] => 54.429279
   [die temperature] => 76.019531
   [board temperature] => 51.440483
   [die temperature] => 73.031250
   [board temperature] => 50.580704
   [die temperature] => 73.500000
   [board temperature] => 53.663273
   [die temperature] => 74.554688
   [board temperature] => 52.464256
   [die temperature] => 75.667969
   [board temperature] => 50.438923

where do i enter stats | grep temperature?  when i tried it after i ssh to minepeon, i get stats: command not found.  sorry im a linux noob

[HF-Engineer]

Hi Guys,

My name is Phil, and I'm one of the engineers working crazy hard on getting your mining rigs to you and working great.

We've had to do a lot of work to get to this point (I've been averaging 4 hours a night sleep over the past few months), and we still are cranking as hard as we can, so please bear with us.

If you received a BabyJet and it's not working well, I advise you first to try our special MinePeon distribution on your Raspberry Pi.  It has a patched version of cgminer which helps stability, and also the distribution has a mechanism to enable firmware and software updates to be pushed out to you as we develop them.  Many of the first shipments didn't have this package, but you can download it.

Our #1 priority has been to get you your products, and now we are working hard on making sure they work well for you.  We are hiring people as fast as we can so that we can build a world-class support system for you.

Until then, I'll try and help as much as I can, time permitting.  The best use of my time is in the lab, as I'm sure you'll agree.

If you are running on the Raspberry Pi and your status screen doesn't show your MinePeon Version to be at least 0.2.4.3hf4, then you could benefit from an update.  It also includes cgminer version 3.11.0hf1, which should help solve some reliability issues until we (and Con Kolivas) can get a better version to you.  The known issues on this version are that reported hashrates are too high.  (I've seen it 2X)  Just use your pools stats, as they are going to be the most accurate.  Also, if there is a warm-boot on the RPI with your HashFast boards connected, something in the RPI's USB Hub/Controller gets left in a strange state and it sometimes takes a handful of tries before cgminer can successfully get connected.  We've set up the system to keep trying over and over again, and usually within a minute or two it "takes" and begins mining.  To avoid this, be sure to disconnect the USB before rebooting.  The goal in this special distribution was to ensure mining automatically runs and gets going again if there is a problem, that way you don't wake up to find it died right after you went to sleep.

We hope to get these issues  fixed soon!  Please let me know if you have any problems or possible ideas that may help, so we can try to incorporate them. 


To install the new version:
1. If running MinePeon, first make a backup from the Settings tab (near the bottom).

2. Download this SD card image: Windows: http://setup.hashfast.com/hashfast-minepeon-1.0.zip  Linux: http://setup.hashfast.com/hashfast-minepeon-1.0.img.bz2

3. If running windows, we recommend the Win32DiskImager: http://sourceforge.net/projects/win32diskimager/, If running Linux, you can simply type:

Code:

bzcat hashfast-minepeon-1.0.img.bz2 | sudo dd bs=1M of=/dev/xxx

(Where /dev/xxx is the device name of your SD card.  If unsure, type "dmesg" after inserting your card.)

4. Boot RPI with the new SD image.  Note that it may take up to 2 minutes to collect current updates from us before it will begin mining.  You can browse here to see when your system comes online and what it's IP address is: http://setup.hashfast.com/.  If for some reason it doesn't come up after a few minutes, power-cycle it.  (We've seen some brands of SD card cause it to hang on reboot)

5. Log into the web interface and restore your backed up MinePeon settings (if any).  Note that the RPI will generate a new wallet when you first boot from the new SD image, and will begin mining using that wallet.  It's important to switch your mining settings using the "Pools" tab so that your mining proceeds end up in the right wallet!

6. If you have any problems, please post them here and I'll do what I can to help.  I'll try to check in here at least once a day.


If you don't want your RPI checking in for updates, you can disable this in the Settings tab, but I advise you to at least do it manually once in while.  We hope to have some new firmware and software soon!  We also advise you to set a password on MinePeon, especially if exposed to the outside internet.  (not behind a router/firewall)

I know the difficulty just went up and it stinks, but please bear with us.  All of us really are working our butts off to ensure we have the best mining products in the world!

-Phil

[HF-Engineer]

Well the good news is my Batch 1 BJ arrived in the uk - 48 hours door to door.
Looked in good condition, no obvious wires or screw loose - although there are only 3 screws holding down the water cooling to the chip.

I have booted up with both the Rpi with a wired ethernet and also a laptop running 3.12 cgminer. 

Either way, the BJ comes to life for about 2 secs, then switches off, then repeats this forever but the BJ does not get recognised by the Pi ot the laptop.
The reboot in the BJ card causes a reboot but it still switches off after a few seconds.

Has anyone got any ideas of where to look for issues?

Thanks

If you do not fix/find the missing screw, a tilted Heatsink would kill your miner, unless only designed to use three.
You better fix that, fast.
Others will jump in to tell you how many screws HS has on theirs I am sure.
Watching thread to learn about these machines.

Yes, if your cooler head is missing a screw, that's likely the problem that's causing the shutdown.  You'll see an entry in the cgminer log that shows "thermal overload".  The cooling head is designed to only work properly with about 60psi of even force across the 4 die substrate.  If it's unevenly loaded you will get thermal overload events.  Our firmware will detect the hot die and shut the system down to prevent damage.

Also, we did have some early BabyJets escape the factory with the fans installed the wrong way.  The top radiator fans should be blowing out (up) and the other chassis fans should be blowing in.  You should be able to reverse them with a phillips screwdriver if you feel comfortable.  This will help cooling.

-Phil 

[ImI]

Hi Phil,

i am running 5 BJs at the moment via laptop and cgminer 3.12.

Whats the update situation in case somebody isnt using rpi/minepeon? Firmwareupdates manually?

Greets

ImI

[ninjarobot]

Also, we did have some early BabyJets escape the factory with the fans installed the wrong way.  The top radiator fans should be blowing out (up) and the other chassis fans should be blowing in.  You should be able to reverse them with a phillips screwdriver if you feel comfortable.  This will help cooling.

Thanks Phil, really appreciate your support on this forum! It was sorely needed.

Looks like one of the chassis fans (the one next to the board) was incorrectly installed in my case as it is blowing out. I'll try to reverse it to see if it helps cooling/stability.

[spectre2112]

Hi Phil - and thanks for your help!

Can you tell me: what is run off of the Auxiliary Power connector?
Is it used for stability or to power the fan headers?

Thanks!

[HF-Engineer]

Sorry, I have to combine my posts, the forum is restricting how much I can post.

ImI:  We will begin releasing utilities and updates soon.  Initially only for Linux-based systems though.  I'll post them as soon as they are ready!

ninjarobot: Thanks, let me know if you still have stability problems.

spectre2112: I'm not sure what aux connector you are referring to.  If you can attach a picture, that will help.  If it's the 5-pin white connector, that's the one that provides +5v standby power to the board, and also enables the board to turn on the PSU. (+12v)



If anyone else is having stability problems, it would help to have a detailed log of the issue.  You can create a temporary log by putting the following line in your "Extra cgminer prarmeters" which is located under the "Settings" tab in your MinePeon web interface:

Code:

--verbose --monitor 'cat > /opt/minepeon/http/log.txt'

Be sure to get the single quotes and spaces correct.  Incorrect data entered in this box can break your system!  Note that this will now be logging a large volume of text to your SD card, which is a bad idea, as it will rapidly wear out if it has to log all that data.  So be sure to restore the original settings (default is blank) after your logging session.

If your log is getting overwritten too much because the session keeps dying, simply add an additional ">" to the existing one, with no extra spaces.  This will cause it to append the logs instead of overwriting them.

Once you have seen the problem occur, you can access the log file at: http://ip.of.your.minepeon/log.txt

If you are not sure of your IP, you should be able to find it by visiting http://setup.hashfast.com/.

If you can then zip up the log file and upload it somewhere where you can share it, such as https://mega.co.nz/ , We will then be able to take a look and see what's going on.  This feedback is useful to us so we can improve things!


-Phil

[Melbustus]

Hi Phil - thanks for jumping into this thread.

In my case, the update a little over 14hrs ago (judging by my system's uptime) seems to have made my stability considerably worse than when I took it out of the box two days ago. For the first day, all cores ran between 69C and 72C, the monitor read a steady 424GH/s, and Eligius reported around 412-420GH/s.

After this update, now I'm getting:
1) Periodic "Bad CRC....discarding packet" errors. I didn't notice a single one of these before the update; now I get them periodically.
2) Temps are considerably higher: 74C-77C
3) Hashrate is lower: 775GH/s reported on the monitor, so I assume that's 2x, meaning: 387GH/s. Eligius reports 374GH/s.

So....any suggestions? What version of CGMiner did my unit ship with (or update to on first boot on Tuesday)? How do I revert?

Note that I haven't touched my unit since I first turned it on, nor has anything changed regarding ambient temp in the room, etc.

[dbbit]

Thanks a lot for joining us Phil!

I just received my BabyJet today.

Below is the current performance graph I'm getting (from Eligius). The green line is the BabyJet:

The average is around 370gh/s over the last 3 hours.

Is this pretty normal for the hashrate to vary THAT much throughout the day? Or should I troubleshoot? (The ambient temperature is pretty stable at 62F right now.).

I'm using the enclosed Pi. Minepeon shows an almost perfectly straight line at about 420ghs.

[ninjarobot]

I flipped the chassis fan to blow in and that lowered the die temperature  by 2 degrees (80C > 78C).

I'm still seeing a lot of USB errors though:
                                                          

Code:

 [2014-01-30 18:55:53] HFB 0: Bad CRC 180 vs 213, discarding packet                                                             
 [2014-01-30 18:55:53] HFB 0: Bad CRC 0 vs 241, discarding packet                                                               
 [2014-01-30 18:55:53] HFB 0 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE                                                    
 [2014-01-30 18:55:53] HFB 0: device disappeared, disabling                                                                     
 [2014-01-30 18:55:53] HFB 0 failure, disabling!                                                                                
 [2014-01-30 18:56:00] Hotplug: Hashfast added HFB 1                                                                            
 [2014-01-30 18:56:18] Accepted 82e4dc8d Diff 501/450 HFB 1 pool 0

Code:

 [2014-01-30 19:08:04] HFB 1: Bad CRC 180 vs 213, discarding packet                                                             
 [2014-01-30 19:08:04] HFB 1: Bad CRC 0 vs 241, discarding packet                                                               
 [2014-01-30 19:08:05] HFB 1 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE                                                    
 [2014-01-30 19:08:05] HFB 1: device disappeared, disabling                                                                     
 [2014-01-30 19:08:05] HFB 1 failure, disabling!                                                                                
 [2014-01-30 19:08:11] Hotplug: Hashfast added HFB 2                                                                            
 [2014-01-30 19:08:28] Accepted 0a3af57d Diff 6.41K/450 HFB 2 pool 0 

   

I understand the USB errors are addressed in cgminer 3.12 so looking forward to that update rolling out to HF minepeons soon.

The good news is that my BJ seems to recover well from these errors now, so I don't have huge gaps where mining stops altogether anymore.

                                                      

[minternj]

HF-Engineer - can you tell me  how are the dies are positioned on the chip? is core 0 top left? Trying to figure out which one is running hot.