Liquid Synergy Designs Inc. -ASIC mining hardware - page 42.

chadtn

sr. member

Activity: 672

Merit: 250

Quote from: zipiju on November 02, 2013, 09:52:15 PM

Quote from: chadtn on November 02, 2013, 09:46:33 PM

fasmax...Is this the correct data sheet for the 1.2v regulator you were talking about?

https://github.com/bkkcoins/klondike/blob/master/datasheets/AP7217D.pdf?raw=true

Did you take a temp reading on the part while you were experimenting? That sheet is saying it's rated to operate in ambient temps up to 80C, max junction temp of 125C. The part itself has thermal throttling at 150C and comes back up when temps drop to 120C.

I can't wait to get my hardware in...I love to tinker. Hope I don't burn anything up. heh..

Chad

1.2V Core is this one https://github.com/bkkcoins/klondike/blob/master/datasheets/IR3895.pdf?raw=true

So much good information...Thanks!! Looks like that regulator thermal throttles at 145C. Junction voltage max is still 125C.

Thanks!

Chad

kronut

member

Activity: 86

Merit: 10

For those that have gotten units, just to confirm, the shipped units come with the latest firmware installed?

fasmax

sr. member

Activity: 378

Merit: 250

Quote from: ionstorm on November 02, 2013, 09:17:02 PM

Quote from: Bogart on November 02, 2013, 09:00:21 PM

Quote from: ionstorm on November 02, 2013, 07:18:07 PM

One of my K16's had thermal paste all over the bottom in between all the chips and circuits, doesnt hash at all says unknown work and 0,0 hash/s. All other miners are perfect, just someone went a lil crazy with the thermal paste lol, hoping steamboat will replace this for me.

Edit: tried my best to clean it with a q-tip, nothing, gonna set this aside and hope steamboat keeps his word which I think he will, real decent guy imho

I don't think the thermal paste is the cause of the problem.

Have you tried any other clockspeeds besides 350MHz?

Thanks for asking, yes 300,325 as well, wonder how I can troubleshoot this

Does the board get worm while running? If it does at lease you know the 32 MHz oscillator is running.
Did you check projectklondike.org there is a section for troubleshooting.
Might need an oscilloscope and or volt meter to find the problem.

zipiju

member

Activity: 93

Merit: 10

Quote from: chadtn on November 02, 2013, 09:46:33 PM

fasmax...Is this the correct data sheet for the 1.2v regulator you were talking about?

https://github.com/bkkcoins/klondike/blob/master/datasheets/AP7217D.pdf?raw=true

Did you take a temp reading on the part while you were experimenting? That sheet is saying it's rated to operate in ambient temps up to 80C, max junction temp of 125C. The part itself has thermal throttling at 150C and comes back up when temps drop to 120C.

I can't wait to get my hardware in...I love to tinker. Hope I don't burn anything up. heh..

Chad

1.2V Core is this one https://github.com/bkkcoins/klondike/blob/master/datasheets/IR3895.pdf?raw=true

chadtn

sr. member

Activity: 672

Merit: 250

fasmax...Is this the correct data sheet for the 1.2v regulator you were talking about?

https://github.com/bkkcoins/klondike/blob/master/datasheets/AP7217D.pdf?raw=true

Did you take a temp reading on the part while you were experimenting? That sheet is saying it's rated to operate in ambient temps up to 80C, max junction temp of 125C. The part itself has thermal throttling at 150C and comes back up when temps drop to 120C.

Edit: zipiju pointed me to the correct part.

I can't wait to get my hardware in...I love to tinker. Hope I don't burn anything up. heh..

Chad

zipiju

member

Activity: 93

Merit: 10

Quote from: chadtn on November 02, 2013, 08:28:33 PM

Quote from: fasmax on November 02, 2013, 08:23:10 PM

No I didn't see HW errors but the 1.2 volt regulators were really hot.
I was worried about the regulators and didn't want do damage my miner so I stopped the experiment at about 68 deg C.

Is that what burned up on the board kano pushed to the limit? I was just looking at the picture posted in the gallery on projectklondike.org. I've been wanting to ask if anyone knew if he had posted any on his results/process info.

Chad

Yep, it's the 1.2V core regulator.
We have just concluded that there probably was a loose solder residue which shorted some of the regulator pins and that was the result.
Those regulators have all sorts of protections built in, so no way you can destroy them like that under normal conditions. Usually when there is something abnormal (they are too hot, they are pushing out too much current), they will simply shut down.
And that is the reason, why you should keep your boards at some reasonable temperatures.
Because if they get too hot, they will stop hashing (because regulators will shut down), and only option to restart them in this case is to repower them.

ionstorm

sr. member

Activity: 266

Merit: 250

Quote from: Bogart on November 02, 2013, 09:00:21 PM

Quote from: ionstorm on November 02, 2013, 07:18:07 PM

One of my K16's had thermal paste all over the bottom in between all the chips and circuits, doesnt hash at all says unknown work and 0,0 hash/s. All other miners are perfect, just someone went a lil crazy with the thermal paste lol, hoping steamboat will replace this for me.

Edit: tried my best to clean it with a q-tip, nothing, gonna set this aside and hope steamboat keeps his word which I think he will, real decent guy imho

I don't think the thermal paste is the cause of the problem.

Have you tried any other clockspeeds besides 350MHz?

Thanks for asking, yes 300,325 as well, wonder how I can troubleshoot this

Bogart

legendary

Activity: 966

Merit: 1000

Quote from: ionstorm on November 02, 2013, 07:18:07 PM

One of my K16's had thermal paste all over the bottom in between all the chips and circuits, doesnt hash at all says unknown work and 0,0 hash/s. All other miners are perfect, just someone went a lil crazy with the thermal paste lol, hoping steamboat will replace this for me.

Edit: tried my best to clean it with a q-tip, nothing, gonna set this aside and hope steamboat keeps his word which I think he will, real decent guy imho

I don't think the thermal paste is the cause of the problem.

Have you tried any other clockspeeds besides 350MHz?

fasmax

sr. member

Activity: 378

Merit: 250

I don't think anyone knows ( including Kano) why that board burned like it did.
My guess is a loose solder ball got wedged into the wrong place. Or maybe the regulator was defective.
I am sure it was an unpleasant surprise when it smoked.

chadtn

sr. member

Activity: 672

Merit: 250

Quote from: fasmax on November 02, 2013, 08:23:10 PM

No I didn't see HW errors but the 1.2 volt regulators were really hot.
I was worried about the regulators and didn't want do damage my miner so I stopped the experiment at about 68 deg C.

Is that what burned up on the board kano pushed to the limit? I was just looking at the picture posted in the gallery on projectklondike.org. I've been wanting to ask if anyone knew if he had posted any on his results/process info.

Chad

fasmax

sr. member

Activity: 378

Merit: 250

No I didn't see HW errors but the 1.2 volt regulators were really hot.
I was worried about the regulators and didn't want do damage my miner so I stopped the experiment at about 68 deg C.

chadtn

sr. member

Activity: 672

Merit: 250

Thanks for the info! Just out of curiosity, what started happening in your experiments when the temp got much over 65? Did hardware errors start spiking?

Chad

fasmax

sr. member

Activity: 378

Merit: 250

Quote from: chadtn on November 02, 2013, 07:31:31 PM

Quote from: zipiju on November 02, 2013, 12:53:30 PM

Quote from: Xian01 on November 02, 2013, 12:42:40 PM

Quote from: ionstorm on November 02, 2013, 11:59:55 AM

I am getting allot of KLNX:X went idle before work was sent messages, why does this happen and how can it be avoided?

Ditto. Also, seems to force an overheat sitatuion @ ~ 54C and ignores whatever I've set in --klondike-options clock:temp

Running with "--klondike-options 325:65"

Should I just ensure that these guys are in an environment that runs near 50C ?

Temp in klondike-options is target temperature which firmware tries to hold by adjusting fan speed. It has nothing to do with overheat - this is a value in CGM driver. When that temperature is reached, CGM disables the board untill temperature falls to around 45°C.
You can edit it in CGM driver-klondike.c at line 63

Quote

#define KLN_KILLWORK_TEMP 53.5

Try to set it for example to 63.5 and recompile cgm.

Does anyone have a link to the thermal specs on the gen 1 Avalon chips? I wasn't having much luck finding technical specs, but I did run across this on the Avalon Batch 3 wiki page:

The batch3 machine have some hardware improvment, one is the temperature sensor was mounted on PCB. (no long glue to the heatsink) so the temperature will be ~20℃ higher compare to the old design (temperature tip) on same condition, so by default we set the:
New Batch3 Machine: Target Temperature to 70℃ and Overheat Cut Off Temperature to 90℃
Before Batch3 Machine: Target Temperature to 50℃ and Overheat Cut Off Temperature to 70℃

Are the chips in the K16 identical to what the batch 3 Avalon people received? I'm getting ready to run a new build of cgminer for when my Klondikes arrive. According to zipiju's post, cgminer's default overheat temp is 53.5. Would it be safe to change that to 70 or 90 depending on where the temp sensor is mounted?

Thanks!

Chad

I would not change it to 70 or 90 the 63.5 setting that zipiju mentioned should be good.
I have done some experiments with my units and recommend setting this below 65.5
For my miners I am using the recommended setting of 63.5.
With extra fans my miners are running at about 45 deg C.

Crindon

sr. member

Activity: 434

Merit: 250

Thank-you for the update Steamboat.

If there is any way that the assembly refunds, hosting set up refunds, and shipping refunds could be made sooner rather than later, it would really be appreciated. As I have lost a small fortune already in assembly fees, I am getting nervous about the rising Bitcoin prices and don't want to lose out on more Bitcoins.

I realize how busy you must be with work and this project among other things in your life. Good job with managing this difficult project.

chadtn

sr. member

Activity: 672

Merit: 250

Quote from: zipiju on November 02, 2013, 12:53:30 PM

Quote from: Xian01 on November 02, 2013, 12:42:40 PM

Quote from: ionstorm on November 02, 2013, 11:59:55 AM

I am getting allot of KLNX:X went idle before work was sent messages, why does this happen and how can it be avoided?

Ditto. Also, seems to force an overheat sitatuion @ ~ 54C and ignores whatever I've set in --klondike-options clock:temp

Running with "--klondike-options 325:65"

Should I just ensure that these guys are in an environment that runs near 50C ?

Temp in klondike-options is target temperature which firmware tries to hold by adjusting fan speed. It has nothing to do with overheat - this is a value in CGM driver. When that temperature is reached, CGM disables the board untill temperature falls to around 45°C.
You can edit it in CGM driver-klondike.c at line 63

Quote

#define KLN_KILLWORK_TEMP 53.5

Try to set it for example to 63.5 and recompile cgm.

Does anyone have a link to the thermal specs on the gen 1 Avalon chips? I wasn't having much luck finding technical specs, but I did run across this on the Avalon Batch 3 wiki page:

The batch3 machine have some hardware improvment, one is the temperature sensor was mounted on PCB. (no long glue to the heatsink) so the temperature will be ~20℃ higher compare to the old design (temperature tip) on same condition, so by default we set the:
New Batch3 Machine: Target Temperature to 70℃ and Overheat Cut Off Temperature to 90℃
Before Batch3 Machine: Target Temperature to 50℃ and Overheat Cut Off Temperature to 70℃

Are the chips in the K16 identical to what the batch 3 Avalon people received? I'm getting ready to run a new build of cgminer for when my Klondikes arrive. According to zipiju's post, cgminer's default overheat temp is 53.5. Would it be safe to change that to 70 or 90 depending on where the temp sensor is mounted?

Thanks!

Chad

ionstorm

sr. member

Activity: 266

Merit: 250

One of my K16's had thermal paste all over the bottom in between all the chips and circuits, doesnt hash at all says unknown work and 0,0 hash/s. All other miners are perfect, just someone went a lil crazy with the thermal paste lol, hoping steamboat will replace this for me.

Edit: tried my best to clean it with a q-tip, nothing, gonna set this aside and hope steamboat keeps his word which I think he will, real decent guy imho

Bogart

legendary

Activity: 966

Merit: 1000

Quote from: rascal777 on November 02, 2013, 05:09:45 PM

2. No bootloader. So that means that I cannot easily download new firmware, I have to use a special pickit controller? So, say a firmware with a bootloader got created, I would have to solder a header onto the board for a PICkit controller, then use the controller to download the firmware to each board?

I just held an unsoldered pinheader diagonally against the pads and flashed mine that way (careful not to short against R42). I had some failures, but just tried again and managed to get all 6 boards flashed in the end. It helps that the pins bend a bit and are slightly springy.

It is kinda tricky to hold it still with one hand and work the mouse with the other. You may want to have a partner work the mouse.

http://projectklondike.org/how-to-program

cardcomm

sr. member

Activity: 294

Merit: 250

Thanks for the update, Steamboat. It's very much appreciated.

I have to hand it to you, you've done a great job in a terrible situation. From what I see and read, you've done really nice work salvaging the project and producing the boards.

I know I've been very vocal here, and also somewhat negative at times. Obviously, my main issue has been with lack of communication. I DO realize you've had your reasons though.

So, thanks again for sticking it out through the mess. The outcome has been far from what we all hoped it could be, but I do believe you've done your best for us all. I'm certainly disappointed that I didn't get miners, but that's life.

I'll try and be patient for the next little while waiting for the assembly refund announcement.

Unacceptable

legendary

Activity: 2212

Merit: 1001

Quote from: rascal777 on November 02, 2013, 05:09:45 PM

If I get the units shipped in their current state, that means
1. No chaining units. I2C not working. So, can I use a USB hub and just plug every unit in via usb and that works fine?

2. No bootloader. So that means that I cannot easily download new firmware, I have to use a special pickit controller? So, say a firmware with a bootloader got created, I would have to solder a header onto the board for a PICkit controller, then use the controller to download the firmware to each board?

I'm fact checking here. Anyone who can verify, please go for it.

To your first point: Correct,no chaining as of now,& yes a hub works just fine Cool

Second point:You'll need a Pickit3,its the red one,no soldering,the "pads" on are back by the USB port.You will need a POGO adapter.

http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR3.TRC1.A0&_nkw=PICkit+3&_sacat=0&_from=R40

Edit:All info should be here:

http://projectklondike.org/how-to-program

rammy2k2

legendary

Activity: 1974

Merit: 1003

Quote from: laughingbear on November 02, 2013, 10:03:03 AM

Any news on the status, for those of us that are waiting on fully finished units?

+1

Topic: Liquid Synergy Designs Inc. -ASIC mining hardware - page 42. (Read 423279 times)