Swedish ASIC miner company kncminer.com

[GenTarkin]

Original MSRP: $5000
Current Value: $0

This is how all crypto-mining ASICs ultimately end up.

[GenTarkin]

I know. But every Bridge Board I have fixed came with a Rpi that was dead shorted on the CPU. Those things are garbage for 24*7, they should have stuck with the beaglebones. So what we really should do is just port the Titan code over to the BB. Which I would do but I keep being too lame to finish it.

I don't mind the work or bitcoin, but I would prefer if people never had the problem in the first place and could mine like hell. :-)

Interesting, Ive had many pi's over the years. Not one single issue.

[carlosmnk]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)




I am worried about theese cubes...

[Tupsu]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

http://i68.tinypic.com/2moceb4.jpg


I am worried about theese cubes...

I had exactly the same thing with GenTarkin software.
Better use  Original KNC software with the same volts.

I did this and it is no problem any more. When i  replace the memory card to GenTarkin software ,  the problem is back.

[AmDD]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

[IMG ]http://i68.tinypic.com/2moceb4.jpg[/img]


I am worried about theese cubes...

Im no expert by any means but I get the same thing every few months on my titan.  WHen this happens I normally re apply the thermal paste. So far this has solved my issue every time but I cant promise it will be the same for you.

[GenTarkin]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)




I am worried about theese cubes...

This is happening because those particular dies are so unstable in any given point in time that multiple attempts were taken to get them hashing again through the form of soft / hard resets done by my firmware.
In short it means those dies are unstable and my firmware will no longer try to bring them back online to prevent bfgminer from constantly restarting.

The stock firmware will do the same thing repeatedly w/ no positive results - soft resets to infinity. While it doesnt cause bfgminer to restart constantly it can severely hamper mining performance.

You can attempt to lower the clocks on those dies and up the volts(which is stock already and I wouldnt recommend going any higher). Also, like AmDD stated, it may be an overheating issue of those dies and its causing them to become unstable, so reapplying therm paste may do the trick.   Theres no way to tell the actual temps of the dies on these Titans.

Also, if you want you can save the log files and email them to me via my website.
Lastly, hitting "CLEAR" will unflag those dies and next time bfgminer runs it will retest them.

[GenTarkin]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

http://i68.tinypic.com/2moceb4.jpg


I am worried about theese cubes...

I had exactly the same thing with GenTarkin software.
Better use  Original KNC software with the same volts.

I did this and it is no problem any more. When i  replace the memory card to GenTarkin software ,  the problem is back.

Interesting.... Im going to guess you have dies that eventually stop hashing over time w/ stock firmware?

[Tupsu]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

http://i68.tinypic.com/2moceb4.jpg


I am worried about theese cubes...

I had exactly the same thing with GenTarkin software.
Better use  Original KNC software with the same volts.

I did this and it is no problem any more. When i  replace the memory card to GenTarkin software ,  the problem is back.

Interesting.... Im going to guess you have dies that eventually stop hashing over time w/ stock firmware?

No, they are selected  cubes  which has never been a problem with hashing at default settings.

[Micky25]

using GenTarkin software is the most effective way to run the Titans, I spent weeks on testing.

[GenTarkin]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

http://i68.tinypic.com/2moceb4.jpg


I am worried about theese cubes...

I had exactly the same thing with GenTarkin software.
Better use  Original KNC software with the same volts.

I did this and it is no problem any more. When i  replace the memory card to GenTarkin software ,  the problem is back.

Interesting.... Im going to guess you have dies that eventually stop hashing over time w/ stock firmware?

No, they are selected  cubes  which has never been a problem with hashing at default settings.

Odd ... well, unless there is some unknown bug in my firmware which triggers erroneous die resets, those cubes most likely do have some sort of issue going on.  Afterall, your cubes may be one of those that after many upon many software resets the dies come back just fine. There are a small number of Titans which act like this. I guess it could be due to faulty pool work / connection problems too.
My firmware uses the same cube/die problem detection code(die amp threshold), it just handles the situation way differently then stock firmware.
Anywho, log files would give an insight as to whats really going on.

[lightfoot]

Interesting, Ive had many pi's over the years. Not one single issue.

I know, it's odd. And I've never seen a BB that did this either.

It is *possible* that the gpio pins are being overdriven running the various spi signals to the boards and the fpga, but that sounds like a bit of a stretch. Still it's possible, I've got a total of four dead Pi's from various people who sent things in for repairs. In all cases the Pis blew out the CPU and sink a lot of current.

Fortunately fix-able.

[alh]

Interesting, Ive had many pi's over the years. Not one single issue.

I know, it's odd. And I've never seen a BB that did this either.

It is *possible* that the gpio pins are being overdriven running the various spi signals to the boards and the fpga, but that sounds like a bit of a stretch. Still it's possible, I've got a total of four dead Pi's from various people who sent things in for repairs. In all cases the Pis blew out the CPU and sink a lot of current.

Fortunately fix-able.

While I don't any KNC gear, my experience with Raspberry Pi has been quite favorable. I can also say that my sum total experience involves ZERO use of the GPIO pins. Everything I have done has been USB based one way or another. My recollection is that the GPIO pins are designed for 3.3V and NOT 5V. Might that explain anything, or do I have my figures wrong?

[pandalion98]

Interesting, Ive had many pi's over the years. Not one single issue.

I know, it's odd. And I've never seen a BB that did this either.

It is *possible* that the gpio pins are being overdriven running the various spi signals to the boards and the fpga, but that sounds like a bit of a stretch. Still it's possible, I've got a total of four dead Pi's from various people who sent things in for repairs. In all cases the Pis blew out the CPU and sink a lot of current.

Fortunately fix-able.

While I don't any KNC gear, my experience with Raspberry Pi has been quite favorable. I can also say that my sum total experience involves ZERO use of the GPIO pins. Everything I have done has been USB based one way or another. My recollection is that the GPIO pins are designed for 3.3V and NOT 5V. Might that explain anything, or do I have my figures wrong?

Your figures are correct. It can only output 3V3 and can NOT accept/output 5V input.

I repeat, the GPIO pins should NOT be exposed to anything above 3V3.

[s1gs3gv]

I''ve decided to offer my KNC Titan for sale.

Mining is going to take a back seat while I  focus on finishing my trading engine and asset management software. PM me for details if you are looking for extra cubes or a whole system with dual EVGA 1300s. Its a good one. BTC accepted and escrow is ok.

Would be nice to sell here instead of on ebay.

[Unacceptable]

I''ve decided to offer my KNC Titan for sale.

Mining is going to take a back seat while I  focus on finishing my trading engine and asset management software. PM me for details if you are looking for extra cubes or a whole system with dual EVGA 1300s. Its a good one. BTC accepted and escrow is ok.

Would be nice to sell here instead of on ebay.

You'll get ALOT more from Ebay though 

Folks here know exactly what their worth 

[s1gs3gv]

Folks here know exactly what their worth  

Well, that sounds like it should be true, but it isn't. No one knows what is going to happen to LTC difficulty and prices in the future. Titans have been profitable from day 1, and will probably continue to be. Mining with a Titan is still probably the most cost effective way of generating BTC income via mining and the Titan lifecycle looks set to beat any other mining equipment past, present or future.

[GenTarkin]

Folks here know exactly what their worth  

Well, that sounds like it should be true, but it isn't. No one knows what is going to happen to LTC difficulty and prices in the future. Titans have been profitable from day 1, and will probably continue to be. Mining with a Titan is still probably the most cost effective way of generating BTC income via mining and the Titan lifecycle looks set to beat any other mining equipment past, present or future.

True that!
Although, scrypt hashrate has increased a decent amount past few weeks(perhaps A4's or perhaps the ASICs which coinhop are comin back on litecoin chain). When A4 indeed does come out mass quantities, Titans will be worth a lot less ... not because they are more effecient(by a bit) but because the sheer hashrate which will be introduced.
And
LTC has been on a steady price decline(vs BTC) the last year. So ... who knows...

In the end, crypto / mining is all a gamble anyways =)

[s1gs3gv]

True that!

Why thank you General. You are a gentleman and a scholar.

When considering the profitability of scrypt mining you must also, of course, take into consideration all the little side opportunities presented, like XPY, GAME and others which were briefly (but handsomely).

Mining scrypt with Titans is profitable. Capital costs amortized over the lifetime of the miner are less of a factor than many assume. Operating costs (electricity) is what matters most. I'd expect that most Titan owners have recovered their initial investment by now and are earning 30% a year on their capital with potential for improvement.

[carlosmnk]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

http://i68.tinypic.com/2moceb4.jpg


I am worried about theese cubes...

I had exactly the same thing with GenTarkin software.
Better use  Original KNC software with the same volts.

I did this and it is no problem any more. When i  replace the memory card to GenTarkin software ,  the problem is back.

Im no expert by any means but I get the same thing every few months on my titan.  WHen this happens I normally re apply the thermal paste. So far this has solved my issue every time but I cant promise it will be the same for you.

Well, i did some test, i tried to change the controller (i have 19 cubes), tried the "official 2.0 KNC controller software" and repaste the 2 cubes with issues and one went back to live (only with repaste); the other one not. I have 4 Titans, and the issued cubes were from diferent titans. Now, there are some more cubes with same issue; some dies are not responding with same "Die flagged for bypass[...]", but now from 3 different titan sets. What is happening??? Some one now anything more?

I'm worried with all the cubes...

EDIT: I forgot; the miners are rebooting every some time, and i don't know why (and the crontap is empty)

[s1gs3gv]

Hi, i have a problem with some cubes; strangelly, they suddenly appear a message that sais "Dies flagged for bypass of health checking: 3:1 3:2 3:3 4:1 6:1" and theese dies are not hashing and i can do nothing to fix it (reboot, change the controller, change the psu, change config...). Here is summer, but i have them with a low configuration to mantain them below 70-75ºC, so i don't think it could be because it is too hot. Here is a pic:

PS: I'm using GenTarkin 1.0.3 and 1.0.4 (i tryed both)

http://i68.tinypic.com/2moceb4.jpg


I am worried about theese cubes...

I had exactly the same thing with GenTarkin software.
Better use  Original KNC software with the same volts.

I did this and it is no problem any more. When i  replace the memory card to GenTarkin software ,  the problem is back.

Im no expert by any means but I get the same thing every few months on my titan.  WHen this happens I normally re apply the thermal paste. So far this has solved my issue every time but I cant promise it will be the same for you.

Well, i did some test, i tried to change the controller (i have 19 cubes), tried the "official 2.0 KNC controller software" and repaste the 2 cubes with issues and one went back to live (only with repaste); the other one not. I have 4 Titans, and the issued cubes were from diferent titans. Now, there are some more cubes with same issue; some dies are not responding with same "Die flagged for bypass[...]", but now from 3 different titan sets. What is happening??? Some one now anything more?

I'm worried with all the cubes...

EDIT: I forgot; the miners are rebooting every some time, and i don't know why (and the crontap is empty)

I would try analyzing your problem via a process of elimination. You could have a cabling problem, a controller problem, a cube problem, a power supply problem or a combination of any of these.

I'd try taking 1 controller that you know works with a set of cables that you know works, and a psu you know that works and attach a single cube (one at a time) to the controller to find out if it works. Once you have done this and characterized your cubes as working/not working, try taking a working cube and a working cable and psu and attach it to a new controller, once in each position. This will let you identify which controllers are suspect.

Working thru this methodology should give you some clarity into what is working and what isn't. When you've done that, you'll know which controllers, cubes and cables are good and which are bad and you can analyze the faults further.

The key is to eliminate as many variables in your testing as possible.