Swedish ASIC miner company kncminer.com - page 75.

GenTarkin

legendary

Activity: 2450

Merit: 1002

Quote from: vegasguy on September 02, 2015, 10:22:22 AM

Guys I need your help. Ive looked everywhere for the correct location of the die numbers, and I just cant seem to find them. I need this information badly, as I want to test some new techniques for hardware die repair. If anyone has this information or can find it , I would appreciate it. If you know which die is which, Please use the pic below and edit it and post. Please dont guess. Thanks.

Vegas

Couldnt u map it using the thermal laser probe? Install HSF, set one die to OFF, take temp readings on top of the base of the HSF, one corner should be cooler than the other 3....

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

Guys I need your help. Ive looked everywhere for the correct location of the die numbers, and I just cant seem to find them. I need this information badly, as I want to test some new techniques for hardware die repair. If anyone has this information or can find it , I would appreciate it. If you know which die is which, Please use the pic below and edit it and post. Please dont guess. Thanks.

Vegas

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

Im doing this from memory, but I beleive the factory capacitor to be 16v and 1000uf. Has anyone installed a 16v /1500 micro farad to see if it works? If it does work, is there any benefit?

Vegas

zybc

newbie

Activity: 28

Merit: 0

Quote from: TXSteve on September 02, 2015, 04:45:15 AM

Quote from: zybc on September 02, 2015, 01:55:38 AM

Thanks for this info!! Going to shop for capacitors

The Cube with higher volume capacitor value has same error..

by the way, should the Rubber filling at capacitor bottom be protruding outside the body??

on both caps I replaced, the rubber filling was protruding on the bottom. Any bulge in either end is a sign that it is bad and should be replaced. Bad electrolytic capacitors are such a common, cheap & easy repair, that they are routinely replaced when troubleshooting electronic components, especially when they are bulging.

However, to be honest I have yet to check a working board to see how low the rubber protrudes on a known working capacitor of the type knc uses, mainly because I'm not curious enough to go though the hassle to remove a pcb on a good cube just to look at it closely. From what I can see, looking thru the spinning fan in the back it doesn't appear to be protruding .... good luck

I have compared the capacitor that we have unsoldered with the images of it and it looks like new ones. Also I have tried to see if it working using multimeter and resistance measuring mode. As my logic said and internet have confirmed it - the capacitor works, BUT can't measure the capacity volume..

TXSteve

sr. member

Activity: 342

Merit: 250

Quote from: zybc on September 02, 2015, 01:55:38 AM

Quote from: TXSteve on September 01, 2015, 12:41:18 PM

Quote from: GenTarkin on September 01, 2015, 12:01:31 PM

Quote from: zybc on September 01, 2015, 11:57:17 AM

At versions 1.02-1.04 I have cycling Cubes restarts it looks as temperature rises to critical and then restart.
At higher I see no cubes.
At MANUFACTURERs version 2.00 no cubes and

Quote

[2015-09-01 16:51:31] I2C lock failure #1
[2015-09-01 16:52:29] I2C lock failure #2

message at messagedcdc.log

I believe the i2c bus is whats directly linked to the controller board, perhaps ur controller board is bad.

I was getting I2C errors in gentarkins log when I had a bad electrolytic capacitor. When advanced settings couldn't even see the bad cube, gentarkins firmware was detecting these I2C errors in the monitordcdc.log file. Replacing the capacitor fixed the problem.

Thanks for this info!! Going to shop for capacitors

The Cube with higher volume capacitor value has same error..

by the way, should the Rubber filling at capacitor bottom be protruding outside the body??

on both caps I replaced, the rubber filling was protruding on the bottom. Any bulge in either end is a sign that it is bad and should be replaced. Bad electrolytic capacitors are such a common, cheap & easy repair, that they are routinely replaced when troubleshooting electronic components, especially when they are bulging.

However, to be honest I have yet to check a working board to see how low the rubber protrudes on a known working capacitor of the type knc uses, mainly because I'm not curious enough to go though the hassle to remove a pcb on a good cube just to look at it closely. From what I can see, looking thru the spinning fan in the back it doesn't appear to be protruding .... good luck

zybc

newbie

Activity: 28

Merit: 0

Quote from: TXSteve on September 01, 2015, 12:41:18 PM

Quote from: GenTarkin on September 01, 2015, 12:01:31 PM

Quote from: zybc on September 01, 2015, 11:57:17 AM

At versions 1.02-1.04 I have cycling Cubes restarts it looks as temperature rises to critical and then restart.
At higher I see no cubes.
At MANUFACTURERs version 2.00 no cubes and

Quote

[2015-09-01 16:51:31] I2C lock failure #1
[2015-09-01 16:52:29] I2C lock failure #2

message at messagedcdc.log

I believe the i2c bus is whats directly linked to the controller board, perhaps ur controller board is bad.

I was getting I2C errors in gentarkins log when I had a bad electrolytic capacitor. When advanced settings couldn't even see the bad cube, gentarkins firmware was detecting these I2C errors in the monitordcdc.log file. Replacing the capacitor fixed the problem.

Thanks for this info!! Going to shop for capacitors

The Cube with higher volume capacitor value has same error..

by the way, should the Rubber filling at capacitor bottom be protruding outside the body??

GenTarkin

legendary

Activity: 2450

Merit: 1002

MORE features/optimizations comin down the pipe:

So, just finished up some tweaks to hostname chars allowed & backup naming tuning. Basically KNC allowed characters that cause issues in the hostname, for example I tried ! as part of hostname and it caused webgui to go to a 500 internal server error ROFL!
So, now, hostnames are only allowed letters, numbers, spaces & - _ symbols.
Backup filename name strips out everything except letters & numbers.
Furthermore, submitting a blank name on system page now deletes the minername all together instead of saying "invalid name"

Also, Im adding a wall watts estimation to the advanced page.
Im wondering if anyone out there that has their titan hooked up to a killawatt if they could read me that measurement vs what the webgui shows for W.
That would be great!
This will help me w/ the estimation percentage I need to go with.
Also, if anyone knows, what the stock fan volts & amps are( that way I can put watts per fan into the equation) as well as I wonder how many watts the controllerboard itself uses. I estimate 20 maybe?
I know the pi uses very little.

TXSteve

sr. member

Activity: 342

Merit: 250

Quote from: GenTarkin on September 01, 2015, 12:01:31 PM

Quote from: zybc on September 01, 2015, 11:57:17 AM

At versions 1.02-1.04 I have cycling Cubes restarts it looks as temperature rises to critical and then restart.
At higher I see no cubes.
At MANUFACTURERs version 2.00 no cubes and

Quote

[2015-09-01 16:51:31] I2C lock failure #1
[2015-09-01 16:52:29] I2C lock failure #2

message at messagedcdc.log

I believe the i2c bus is whats directly linked to the controller board, perhaps ur controller board is bad.

I was getting I2C errors in gentarkins log when I had a bad electrolytic capacitor. When advanced settings couldn't even see the bad cube, gentarkins firmware was detecting these I2C errors in the monitordcdc.log file. Replacing the capacitor fixed the problem.

GenTarkin

legendary

Activity: 2450

Merit: 1002

Quote from: zybc on September 01, 2015, 11:57:17 AM

At versions 1.02-1.04 I have cycling Cubes restarts it looks as temperature rises to critical and then restart.
At higher I see no cubes.
At MANUFACTURERs version 2.00 no cubes and

Quote

[2015-09-01 16:51:31] I2C lock failure #1
[2015-09-01 16:52:29] I2C lock failure #2

message at messagedcdc.log

I believe the i2c bus is whats directly linked to the controller board, perhaps ur controller board is bad.

zybc

newbie

Activity: 28

Merit: 0

At versions 1.02-1.04 I have cycling Cubes restarts it looks as temperature rises to critical and then restart.
At higher I see no cubes.
At MANUFACTURERs version 2.00 no cubes and

Quote

[2015-09-01 16:51:31] I2C lock failure #1
[2015-09-01 16:52:29] I2C lock failure #2

message at messagedcdc.log

GenTarkin

legendary

Activity: 2450

Merit: 1002

Quote from: zybc on September 01, 2015, 11:38:39 AM

Quote from: GenTarkin on September 01, 2015, 11:13:54 AM

There is no such thing as 2.00 LOG which has those messages in it. Only my firmware will have those temperature thresholds & protection methods mentioned in it. So, Im not quite sure what you are referring to.
If you really are running a stock v2.00 firmware and the log is really spitting that out, then you have something completely wrong.
If you are running my firmware and u did tamper w/ donations then... Im not inclined to support ur issues. This will further force my hand in no donation version even existing, may all end up prepaid only.
On another note the I2c lock theoretically doesnt have anything to do w/ my firmware. Cuz I dont mess w/ that script at all. AFAIK my mods to the monitor script dont mess w/ the i2c bus except for when waas is called which is only if there are die issues.

May be it is my fault and missunderstanding of your donation/payment strategy. I just wanted to try what it will look like if I set a original firmware upgrade.. So I have published that screenshot.. May be you can help me clearing this situation..
So can you explain what is the source of I2C error??

First off, how did u upgrade to my firmware? Did you just do a git pull and call it good? cuz there are further steps to fully install my mod, all of which are taken care of if you flash the .bin file listed on my v99a release. Flash it via the SYSTEM->upgrade section.
If all went well as per the output of the flashing process then reboot.

Once my mod is installed correctly, or optionally completely reflash the stock v2.00 full img file, either way report back w/ any i2c issues. If they still persist then something is clobbering and preventing the i2c bus from being readable via the pi. Hence causing the lock.

zybc

newbie

Activity: 28

Merit: 0

Quote from: GenTarkin on September 01, 2015, 11:13:54 AM

There is no such thing as 2.00 LOG which has those messages in it. Only my firmware will have those temperature thresholds & protection methods mentioned in it. So, Im not quite sure what you are referring to.
If you really are running a stock v2.00 firmware and the log is really spitting that out, then you have something completely wrong.
If you are running my firmware and u did tamper w/ donations then... Im not inclined to support ur issues. This will further force my hand in no donation version even existing, may all end up prepaid only.
On another note the I2c lock theoretically doesnt have anything to do w/ my firmware. Cuz I dont mess w/ that script at all. AFAIK my mods to the monitor script dont mess w/ the i2c bus except for when waas is called which is only if there are die issues.

May be it is my fault and missunderstanding of your donation/payment strategy. I just wanted to try what it will look like if I set a original firmware upgrade.. So I have published that screenshot.. May be you can help me clearing this situation..
So can you explain what is the source of I2C error??

GenTarkin

legendary

Activity: 2450

Merit: 1002

Quote from: zybc on September 01, 2015, 03:06:06 AM

Quote from: GenTarkin on August 31, 2015, 03:38:00 PM

Quote from: zybc on August 31, 2015, 01:36:10 PM

This screen stays for an infinite time

Waited 3hrs then 5hrs..
internet is 6Mbit and SD 10class NEW one!

Please attempt installing the new released v.99a firmware .bin file here:
https://github.com/GenTarkin/Titan/releases/tag/v.99a

It wont attempt to install wget anymore, should have no problems with this release.
Upgrade should finish in a few mins.

Yes

it happened. Firmware flashed.
But still no cubes Sad

may be I can find some helpfull info at system logs?? (/var/log/)

here is monitordcdc log screenshot

what does these line mean??
[2015-09-01 10:30:24] I2C lock failure #1
[2015-09-01 10:31:17] I2C lock failure #2
[2015-09-01 10:32:22] I2C lock failure #3
[2015-09-01 10:32:22] Rebooting due to I2C lock
This is 2.00 LOG

may be someone can advise how to compile knc-miner files to make changes incide??

There is no such thing as 2.00 LOG which has those messages in it. Only my firmware will have those temperature thresholds & protection methods mentioned in it. So, Im not quite sure what you are referring to.
If you really are running a stock v2.00 firmware and the log is really spitting that out, then you have something completely wrong.
If you are running my firmware and u did tamper w/ donations then... Im not inclined to support ur issues. This will further force my hand in no donation version even existing, may all end up prepaid only.
On another note the I2c lock theoretically doesnt have anything to do w/ my firmware. Cuz I dont mess w/ that script at all. AFAIK my mods to the monitor script dont mess w/ the i2c bus except for when waas is called which is only if there are die issues.

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

The key is temps. They must be held to a minimum at all times. Also dont EVER run them over 300mhz. They will run at 325mhz for months, but then fail. Havent had a failure yet at 300mhz.

Vegas

LongAndShort

legendary

Activity: 1078

Merit: 1050

Quote from: vegasguy on September 01, 2015, 08:00:22 AM

Quote

the chips were getting so hot that it discolored the machined edge on the copper pipes used to make contact with the chips

Ya, many of the failures are from the wafers getting so hot, the solders balls scorch and lose contact with the pcb. I may have to look into a reball machine. Problem is there is no stencil made to my knowledge for this chip.

Vegas

I dont know of one in the public either, had my finger on the pulse so to speak since inception too. As have many of you.

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

Quote

the chips were getting so hot that it discolored the machined edge on the copper pipes used to make contact with the chips

Ya, many of the failures are from the wafers getting so hot, the solders balls scorch and lose contact with the pcb. I may have to look into a reball machine. Problem is there is no stencil made to my knowledge for this chip.

Vegas

LongAndShort

legendary

Activity: 1078

Merit: 1050

Please chime in if you remember, anyone. I vaugly remember Keith saying the temps were an average. I cannot quote as the knc forum is now gone as far as im aware.

They possibly then changed the status screen on the webgui to say : DC/DC Avg Temp. I really cant remember what came first to be honest.

By the way i noticed that the chips were getting so hot that it discolored the machined edge on the copper pipes used to make contact with the chips!

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

You can order a precompiled firmware with no donations. Look in my signature for the order page. Thanks for testing the security system

Vegas

TXSteve

sr. member

Activity: 342

Merit: 250

Quote from: zybc on September 01, 2015, 03:06:06 AM

Quote from: GenTarkin on August 31, 2015, 03:38:00 PM

Quote from: zybc on August 31, 2015, 01:36:10 PM

This screen stays for an infinite time

Waited 3hrs then 5hrs..
internet is 6Mbit and SD 10class NEW one!

Please attempt installing the new released v.99a firmware .bin file here:
https://github.com/GenTarkin/Titan/releases/tag/v.99a

It wont attempt to install wget anymore, should have no problems with this release.
Upgrade should finish in a few mins.

Yes

it happened. Firmware flashed.
But still no cubes Sad

may be I can find some helpfull info at system logs?? (/var/log/)

here is monitordcdc log screenshot

what does these line mean??
[2015-09-01 10:30:24] I2C lock failure #1
[2015-09-01 10:31:17] I2C lock failure #2
[2015-09-01 10:32:22] I2C lock failure #3
[2015-09-01 10:32:22] Rebooting due to I2C lock
This is 2.00 LOG

may be someone can advise how to compile knc-miner files to make changes incide??

"Donations tampered with advanced firmware mode disabled!!"

looks like you were busted ...

that msg should read "Donations tampered with, your rig has been bricked, send 50 LTC to TarkyTarkin"

zybc

newbie

Activity: 28

Merit: 0

Quote from: GenTarkin on August 31, 2015, 03:38:00 PM

Quote from: zybc on August 31, 2015, 01:36:10 PM

This screen stays for an infinite time
http://static1.keep4u.ru/2015/08/31/Asic-44.th.png
Waited 3hrs then 5hrs..
internet is 6Mbit and SD 10class NEW one!

Please attempt installing the new released v.99a firmware .bin file here:
https://github.com/GenTarkin/Titan/releases/tag/v.99a

It wont attempt to install wget anymore, should have no problems with this release.
Upgrade should finish in a few mins.

Yes

it happened. Firmware flashed.
But still no cubes Sad

may be I can find some helpfull info at system logs?? (/var/log/)

here is monitordcdc log screenshot
http://static2.keep4u.ru/2015/09/01/asic-5.th.png
what does these line mean??
[2015-09-01 10:30:24] I2C lock failure #1
[2015-09-01 10:31:17] I2C lock failure #2
[2015-09-01 10:32:22] I2C lock failure #3
[2015-09-01 10:32:22] Rebooting due to I2C lock
This is 2.00 LOG

may be someone can advise how to compile knc-miner files to make changes incide??

Topic: Swedish ASIC miner company kncminer.com - page 75. (Read 3049514 times)