Pages:
Author

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

hero member
Activity: 681
Merit: 500
OK I will asked differently. Did anyone find graphic card cooler that gets out 40GH? I found 2 CPU coolers that gets 40 out but not a GPU that will get more then 36GH. And I'm looking at less then 30$...

I think the real key is cooling the VRMs.
hero member
Activity: 826
Merit: 1000
OK I will asked differently. Did anyone find graphic card cooler that gets out 40GH? I found 2 CPU coolers that gets 40 out but not a GPU that will get more then 36GH. And I'm looking at less then 30$...
sr. member
Activity: 267
Merit: 250
BTC1  =  $420

I'm waiting on 4 Chili's at an average price of 4.5 BTC.
member
Activity: 86
Merit: 10
BTC1  =  $420
sr. member
Activity: 267
Merit: 250
Anyone found a graphic card cooler that would work good with this board?

I have been using the Arctic Accelero Twin Turbo II for these with good results.  I bought the Arctic back plates as well to give the board more support.

Do you have a link to the back planes?

The page is messed up on the Arctic site but here it is:

http://www.arctic.ac/us_en/eva-foam-and-gpu-back-plate.html

Here is the cooler:

http://www.arctic.ac/us_en/products/cooling/vga/accelero-twin-turbo-ii.html

Yeah, shipping on that site is ridiculous.
member
Activity: 71
Merit: 10
Anyone found a graphic card cooler that would work good with this board?

I have been using the Arctic Accelero Twin Turbo II for these with good results.  I bought the Arctic back plates as well to give the board more support.

Do you have a link to the back planes?

The page is messed up on the Arctic site but here it is:

http://www.arctic.ac/us_en/eva-foam-and-gpu-back-plate.html

Here is the cooler:

http://www.arctic.ac/us_en/products/cooling/vga/accelero-twin-turbo-ii.html
sr. member
Activity: 267
Merit: 250
Anyone found a graphic card cooler that would work good with this board?

I have been using the Arctic Accelero Twin Turbo II for these with good results.  I bought the Arctic back plates as well to give the board more support.

Do you have a link to the back planes?
legendary
Activity: 2408
Merit: 1004
Me too twin turbo 2 hashing at 32 to 36 gh per board
member
Activity: 71
Merit: 10
Anyone found a graphic card cooler that would work good with this board?

I have been using the Arctic Accelero Twin Turbo II for these with good results.  I bought the Arctic back plates as well to give the board more support.
hero member
Activity: 826
Merit: 1000
Anyone found a graphic card cooler that would work good with this board?
jr. member
Activity: 59
Merit: 10
Any updates on batch 2 production status?
0-25%
25-50%
50-75%
75%-finished
full member
Activity: 198
Merit: 100
Any updates on batch 2 production status?
0-25%
25-50%
50-75%
75%-finished
0-25%
member
Activity: 86
Merit: 10
Any updates on batch 2 production status?
0-25%
25-50%
50-75%
75%-finished
legendary
Activity: 1274
Merit: 1004
cgminer is stopping work because one of the cores is too hot. I find that will happen if I haven't done a good job of mounting the heatsink; I'll see most of the chips sitting at 60-70 and one will shoot up to 100. The back and forth with cgminer is something we'll fix in a FW update, but the root cause is bad heatsink contact.
Will look into it but since reported temperature starts at 35 and go to 66 I don't think this is it... Unless we don't see highest temperature reported...
Replaced thermal pads... And problem fixed... But why I didn't see this hi temperature reported in cgminer? And got speed for 37.2 to 39.8 Smiley
I'm actually not sure, obviously it's getting reported to cgminer since it is throttling. It must be displaying just one of the temps and not the other.

As for reporting all of them, it's in the works probably through a custom Z*X command. We just need to implement it, and then get support added to the mining software.
Throttling should be reduced in the next firmware release.  Part of the problem was that if Chili was idle because the host mining software was not sending any jobs (perhaps it's not started yet or there is a problem with the pool connection), then Chili would cool off and notice that it could crank up the frequency and voltage.  This is bad when work unit start coming again because it is now running too fast & hot.

New firmware will not change frequency or voltage when there are no work units in the queue.  I'm testing that and other fixes now.

Edit: The temperature that is reported is the temperature of the hottest ASIC chip.

Is there also a temp sensor in the VRM area that the firmware watches but doesn't report?
Yeah, it's the little 3 pin chip marked U25 between the middle two MOSFETs.
hero member
Activity: 681
Merit: 500
cgminer is stopping work because one of the cores is too hot. I find that will happen if I haven't done a good job of mounting the heatsink; I'll see most of the chips sitting at 60-70 and one will shoot up to 100. The back and forth with cgminer is something we'll fix in a FW update, but the root cause is bad heatsink contact.
Will look into it but since reported temperature starts at 35 and go to 66 I don't think this is it... Unless we don't see highest temperature reported...
Replaced thermal pads... And problem fixed... But why I didn't see this hi temperature reported in cgminer? And got speed for 37.2 to 39.8 Smiley
I'm actually not sure, obviously it's getting reported to cgminer since it is throttling. It must be displaying just one of the temps and not the other.

As for reporting all of them, it's in the works probably through a custom Z*X command. We just need to implement it, and then get support added to the mining software.
Throttling should be reduced in the next firmware release.  Part of the problem was that if Chili was idle because the host mining software was not sending any jobs (perhaps it's not started yet or there is a problem with the pool connection), then Chili would cool off and notice that it could crank up the frequency and voltage.  This is bad when work unit start coming again because it is now running too fast & hot.

New firmware will not change frequency or voltage when there are no work units in the queue.  I'm testing that and other fixes now.

Edit: The temperature that is reported is the temperature of the hottest ASIC chip.

Is there also a temp sensor in the VRM area that the firmware watches but doesn't report?
full member
Activity: 198
Merit: 100
cgminer is stopping work because one of the cores is too hot. I find that will happen if I haven't done a good job of mounting the heatsink; I'll see most of the chips sitting at 60-70 and one will shoot up to 100. The back and forth with cgminer is something we'll fix in a FW update, but the root cause is bad heatsink contact.
Will look into it but since reported temperature starts at 35 and go to 66 I don't think this is it... Unless we don't see highest temperature reported...
Replaced thermal pads... And problem fixed... But why I didn't see this hi temperature reported in cgminer? And got speed for 37.2 to 39.8 Smiley
I'm actually not sure, obviously it's getting reported to cgminer since it is throttling. It must be displaying just one of the temps and not the other.

As for reporting all of them, it's in the works probably through a custom Z*X command. We just need to implement it, and then get support added to the mining software.
Throttling should be reduced in the next firmware release.  Part of the problem was that if Chili was idle because the host mining software was not sending any jobs (perhaps it's not started yet or there is a problem with the pool connection), then Chili would cool off and notice that it could crank up the frequency and voltage.  This is bad when work unit start coming again because it is now running too fast & hot.

New firmware will not change frequency or voltage when there are no work units in the queue.  I'm testing that and other fixes now.

Edit: The temperature that is reported is the temperature of the hottest ASIC chip.
full member
Activity: 198
Merit: 100
Is there any way we can get the source to the FW?
Not at this time.  I have no current plans to release it but might change my mind later. 
jr. member
Activity: 59
Merit: 10
cgminer is stopping work because one of the cores is too hot. I find that will happen if I haven't done a good job of mounting the heatsink; I'll see most of the chips sitting at 60-70 and one will shoot up to 100. The back and forth with cgminer is something we'll fix in a FW update, but the root cause is bad heatsink contact.
Will look into it but since reported temperature starts at 35 and go to 66 I don't think this is it... Unless we don't see highest temperature reported...
Replaced thermal pads... And problem fixed... But why I didn't see this hi temperature reported in cgminer? And got speed for 37.2 to 39.8 Smiley
I'm actually not sure, obviously it's getting reported to cgminer since it is throttling. It must be displaying just one of the temps and not the other.

As for reporting all of them, it's in the works probably through a custom Z*X command. We just need to implement it, and then get support added to the mining software.
how is the production going on?
member
Activity: 86
Merit: 10
Is there any way we can get the source to the FW?
legendary
Activity: 1274
Merit: 1004
cgminer is stopping work because one of the cores is too hot. I find that will happen if I haven't done a good job of mounting the heatsink; I'll see most of the chips sitting at 60-70 and one will shoot up to 100. The back and forth with cgminer is something we'll fix in a FW update, but the root cause is bad heatsink contact.
Will look into it but since reported temperature starts at 35 and go to 66 I don't think this is it... Unless we don't see highest temperature reported...
Replaced thermal pads... And problem fixed... But why I didn't see this hi temperature reported in cgminer? And got speed for 37.2 to 39.8 Smiley
I'm actually not sure, obviously it's getting reported to cgminer since it is throttling. It must be displaying just one of the temps and not the other.

As for reporting all of them, it's in the works probably through a custom Z*X command. We just need to implement it, and then get support added to the mining software.
Pages:
Jump to: