Pages:
Author

Topic: The Chili – 30+GH/s BFL based Bitcoin Miner Assembly - page 50. (Read 138054 times)

donator
Activity: 1218
Merit: 1080
Gerald Davis
There are thermal adhesives.

Good stuff:  http://www.arcticsilver.com/arctic_silver_thermal_adhesive.htm

It is likely the heatsinks came with thermal adhesive not thermal paste.
hero member
Activity: 681
Merit: 500
Are you going to use the glue that came with the heatsinks?

Yes I was planning on using the included glue.

Mr Teal... any advice on the placement of the heatsinks in my pics above?

Also will the glue itself be ok for use on the bottom... I do not want to short anything...

Glue? You probably mean thermal paste, which won't keep things stuck on reliably.
hero member
Activity: 630
Merit: 500
Are you going to use the glue that came with the heatsinks?

Yes I was planning on using the included glue.

Mr Teal... any advice on the placement of the heatsinks in my pics above?

Also will the glue itself be ok for use on the bottom... I do not want to short anything...
legendary
Activity: 2408
Merit: 1004
Any new firmware mr teal
Please
member
Activity: 119
Merit: 10
I think you need to wait for 7 and 8 to stop flashing before running the software.

Yes, every led must stop flashing before you can run the software.
hero member
Activity: 681
Merit: 500
I think you need to wait for 7 and 8 to stop flashing before running the software.
legendary
Activity: 1610
Merit: 1000
Well hello there!
Two out of them is harder to get them start mining, at the very first beginning. and it become harder and harder with each reboot. These two eventually cease to operate yesterday, until now (but still viewable in cgminer console)

I got 2 boards that won't boot up (2nd led keep blinking) but once I turn on the AC to cool the room they boot up in about 1 minute. After that they will hash just fine even with AC off.
When a board first starts up, the firmware makes sure the board and chips are cooled down before it starts the self test.  This helps ensure the maximum number of engines (cores) will pass self test.

LED decoder ring

The LEDs are numbered 1 to 8 with #1 closest to the USB connector and #8 closest to the power and fan connectors.  During first power up, LEDs 5, 6, 7, and 8 will light up and LEDs 1, 2, 3,  and 4 will indicate a failure code if anything is wrong with the hardware.  This happens VERY quickly - in less than a second.

If the initial hardware checks are good, #7 will blink indicating it is waiting for the board to cool down.  This will always blink for a few seconds even if the board is cold.  

Then #7 and #8 will blink indicating ASIC self test.  

After that, 1, 2, 3, 4 will indicate how many jobs from cgminer are waiting to run in the input queue.  LED 5 is just a debug output for me but it roughly indicates a job has completed - but sometimes blinks too fast for the human eye to see.  Just ignore LED 5.

I am working on some firmware updates that will fix most (or all?) of the problems the boards are having.  For example, one failure I think I have figured out is occasionally a board will jump to more than 100 GH/s but have 100% hardware errors.  I have one board that does this once per day or so and needs to be rebooted.  After chasing this for a while, I believe I have finally figured out what is going on and will have a fix in the next release.

I am having some serious difficulty getting either of my two chilis to run properly. After replacing my BFL drivers with Zadig v6.1.7600.16385 driver(s) and loading cgminer v3.6.6 I am getting the device to detect but getting the following output:
"AVA looking for AVA 0403:6001 but found 05e3:0608 instead" <---which varies at times
Any idea what may be causing this.

*Also, LED's 7 and 8 are flashing at different speeds (seven faster than eight), while LED's 2,3,4, and 5 are all solid green.

Any suggestions you might be able to offer would be greatly appreciated.

Vendor and product ID should be 0403:6014, not sure what that one is. Second id might be a hub(maybe try plugging directly into your controller). WinUSB driver installation can be a real pain when you already have a default set, like FTDI. Were you using bfgminer beforehand? I would suggest completely removing the existing drivers and then reinstalling with winusb. Once Winusb is the default driver for that device type, you won't have to go through the process again with each new device. Don't forget to unplug the device and re-plug it in after installing WinUSB drivers.

I was indeed using bfgminer beforehand. I'll go ahead and give your suggestion a try.

*Although I thought the LED's 7 and 8 where supposed to stop flashing at some point.
legendary
Activity: 1274
Merit: 1004
I just got my production boards in the mail today. It's been a long wait for these, it's shocking that I'm not more prepared.

I mounted a few with the Antec Kuhler Shelf's, but I'm not terribly happy with how much board flex I got with those stock back brackets. I was going to go out to the garage to cut up a better backplate for it, but before I did I thought I'd try a quick experiment and just used another one of the Kuhler Shelf's on the back side essentially just as a backplate. I just used the included paste as well.
Results were pretty spectacular, especially considering it is hot (and loud) in my furnace room with 3 Avalon Minis, a BFL Single and LS, along with now two Chilis. It ramped up to 39GH/s pretty much right away. The power supply got Hot Hot Hot though. It definitely needed to have some press on heatsinks added there.

I'll bring it in to the office tomorrow so I can hook some diagnostic equipment up to it and take a look at the current draw of the board and the ASICs at those power levels. For $10 though, I'm tempted to just double up the coolers on every unit and call it a day. It will save me a lot of time compared to actually making a backplate.

I can't wait to get my PDU and other equipment set up so I can run it properly where it's meant to be, with some nice 0C ambient instead of 25C ambient.
legendary
Activity: 910
Merit: 1000
Are you going to use the glue that came with the heatsinks?
hero member
Activity: 630
Merit: 500
Just wanted to put it out there that I am using Ubuntu 12.04 CGMiner 3.5.0 and all I had to do was plug it in to an open USB port and my Chili has been hashing away at 34 GH/s with temp at 70-72C. I really like this board....

This is how it should be.

Ill have mine hashing by Friday with an ARCTIC Accelero TT II and press on heatsinks under the chips and voltage regulator.

I will post my cgminer results Friday.

Please post up some pics when you have it all built. I'm interested to see how you are attaching the heatsinks.

Looking for some feedback before I make any permanent additions.

Here is the Chili...



Here is what I plan on doing with the heatsinks on the bottom... please let me know if this is worth doing or needs better placement... was going for base of mosfets and capacitors not the inductors.



Here is whaat I might do with the remaining heatsinks... is this even worth doing?


legendary
Activity: 1973
Merit: 1007
Two out of them is harder to get them start mining, at the very first beginning. and it become harder and harder with each reboot. These two eventually cease to operate yesterday, until now (but still viewable in cgminer console)

I got 2 boards that won't boot up (2nd led keep blinking) but once I turn on the AC to cool the room they boot up in about 1 minute. After that they will hash just fine even with AC off.
When a board first starts up, the firmware makes sure the board and chips are cooled down before it starts the self test.  This helps ensure the maximum number of engines (cores) will pass self test.

LED decoder ring

The LEDs are numbered 1 to 8 with #1 closest to the USB connector and #8 closest to the power and fan connectors.  During first power up, LEDs 5, 6, 7, and 8 will light up and LEDs 1, 2, 3,  and 4 will indicate a failure code if anything is wrong with the hardware.  This happens VERY quickly - in less than a second.

If the initial hardware checks are good, #7 will blink indicating it is waiting for the board to cool down.  This will always blink for a few seconds even if the board is cold.  

Then #7 and #8 will blink indicating ASIC self test.  

After that, 1, 2, 3, 4 will indicate how many jobs from cgminer are waiting to run in the input queue.  LED 5 is just a debug output for me but it roughly indicates a job has completed - but sometimes blinks too fast for the human eye to see.  Just ignore LED 5.

I am working on some firmware updates that will fix most (or all?) of the problems the boards are having.  For example, one failure I think I have figured out is occasionally a board will jump to more than 100 GH/s but have 100% hardware errors.  I have one board that does this once per day or so and needs to be rebooted.  After chasing this for a while, I believe I have finally figured out what is going on and will have a fix in the next release.

I am having some serious difficulty getting either of my two chilis to run properly. After replacing my BFL drivers with Zadig v6.1.7600.16385 driver(s) and loading cgminer v3.6.6 I am getting the device to detect but getting the following output:
"AVA looking for AVA 0403:6001 but found 05e3:0608 instead" <---which varies at times
Any idea what may be causing this.

*Also, LED's 7 and 8 are flashing at different speeds (seven faster than eight), while LED's 2,3,4, and 5 are all solid green.

Any suggestions you might be able to offer would be greatly appreciated.

Vendor and product ID should be 0403:6014, not sure what that one is. Second id might be a hub(maybe try plugging directly into your controller). WinUSB driver installation can be a real pain when you already have a default set, like FTDI. Were you using bfgminer beforehand? I would suggest completely removing the existing drivers and then reinstalling with winusb. Once Winusb is the default driver for that device type, you won't have to go through the process again with each new device. Don't forget to unplug the device and re-plug it in after installing WinUSB drivers.
legendary
Activity: 2408
Merit: 1004
From what the chilli died?
hero member
Activity: 518
Merit: 500
Every man is guilty of all the good he did not do.
Looking forward to that Firmware update guys Tongue Got two dead chilis I'd like to potentially resurrect (Happy Halloween)

legendary
Activity: 1274
Merit: 1004
I am having some serious difficulty getting either of my two chilis to run properly. After replacing my BFL drivers with Zadig v6.1.7600.16385 driver(s) and loading cgminer v3.6.6 I am getting the device to detect but getting the following output:
"AVA looking for AVA 0403:6001 but found 05e3:0608 instead" <---which varies at times
Any idea what may be causing this.

*Also, LED's 7 and 8 are flashing at different speeds (seven faster than eight), while LED's 2,3,4, and 5 are all solid green.

Any suggestions you might be able to offer would be greatly appreciated.
The AVA message is what cgminer puts out? I've never seen anything like that before, I'll have to download 3.6.6 and look into it.
legendary
Activity: 1610
Merit: 1000
Well hello there!
Two out of them is harder to get them start mining, at the very first beginning. and it become harder and harder with each reboot. These two eventually cease to operate yesterday, until now (but still viewable in cgminer console)

I got 2 boards that won't boot up (2nd led keep blinking) but once I turn on the AC to cool the room they boot up in about 1 minute. After that they will hash just fine even with AC off.
When a board first starts up, the firmware makes sure the board and chips are cooled down before it starts the self test.  This helps ensure the maximum number of engines (cores) will pass self test.

LED decoder ring

The LEDs are numbered 1 to 8 with #1 closest to the USB connector and #8 closest to the power and fan connectors.  During first power up, LEDs 5, 6, 7, and 8 will light up and LEDs 1, 2, 3,  and 4 will indicate a failure code if anything is wrong with the hardware.  This happens VERY quickly - in less than a second.

If the initial hardware checks are good, #7 will blink indicating it is waiting for the board to cool down.  This will always blink for a few seconds even if the board is cold.  

Then #7 and #8 will blink indicating ASIC self test.  

After that, 1, 2, 3, 4 will indicate how many jobs from cgminer are waiting to run in the input queue.  LED 5 is just a debug output for me but it roughly indicates a job has completed - but sometimes blinks too fast for the human eye to see.  Just ignore LED 5.

I am working on some firmware updates that will fix most (or all?) of the problems the boards are having.  For example, one failure I think I have figured out is occasionally a board will jump to more than 100 GH/s but have 100% hardware errors.  I have one board that does this once per day or so and needs to be rebooted.  After chasing this for a while, I believe I have finally figured out what is going on and will have a fix in the next release.

I am having some serious difficulty getting either of my two chilis to run properly. After replacing my BFL drivers with Zadig v6.1.7600.16385 driver(s) and loading cgminer v3.6.6 I am getting the device to detect but getting the following output:
"AVA looking for AVA 0403:6001 but found 05e3:0608 instead" <---which varies at times
Any idea what may be causing this.

*Also, LED's 7 and 8 are flashing at different speeds (seven faster than eight), while LED's 2,3,4, and 5 are all solid green.

Any suggestions you might be able to offer would be greatly appreciated.
legendary
Activity: 910
Merit: 1000
Just wanted to put it out there that I am using Ubuntu 12.04 CGMiner 3.5.0 and all I had to do was plug it in to an open USB port and my Chili has been hashing away at 34 GH/s with temp at 70-72C. I really like this board....

This is how it should be.

Ill have mine hashing by Friday with an ARCTIC Accelero TT II and press on heatsinks under the chips and voltage regulator.

I will post my cgminer results Friday.

Please post up some pics when you have it all built. I'm interested to see how you are attaching the heatsinks.
hero member
Activity: 630
Merit: 500
Just wanted to put it out there that I am using Ubuntu 12.04 CGMiner 3.5.0 and all I had to do was plug it in to an open USB port and my Chili has been hashing away at 34 GH/s with temp at 70-72C. I really like this board....

This is how it should be.

Ill have mine hashing by Friday with an ARCTIC Accelero TT II and press on heatsinks under the chips and voltage regulator.

I will post my cgminer results Friday.
sr. member
Activity: 476
Merit: 250
Just wanted to put it out there that I am using Ubuntu 12.04 CGMiner 3.5.0 and all I had to do was plug it in to an open USB port and my Chili has been hashing away at 34 GH/s with temp at 70-72C. I really like this board....
hero member
Activity: 518
Merit: 500
Every man is guilty of all the good he did not do.
Here I use newest cgminer with zadig.



"cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u myaddress -p x -G"

Not hashing, doing nothing. Try it on 2 PCs, same thing. My Bitburner Fury works fine. Change usb cable, same result.  

LED 2 blinking
LED 5,6,7 on
LED 1,3,4,8 off

Huh

This is a workaround version of BFGMiner until a new firmware update for the chilis

Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)

http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip

Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows

Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.

Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.

Let me know if this helps Smiley

Hey Bar, trying to get this tweaked version of bfgminer but this download manager crap isn't working for me. Any chance you have an alternate link available?

The newest version of BFGMiner now has Chili Support (3.4.0) Just visit http://bfgminer.org/ and you should be set Smiley
hero member
Activity: 681
Merit: 500
Try the latest windows build of bfgminer by itself. Maybe it includes support for the Chili now.
http://luke.dashjr.org/programs/bitcoin/files/bfgminer/testing/
Pages:
Jump to: