 Show Posts
|
|
Pages: [1] 2 »
|
|
What about burning power socket?? How to avoid this effect?
I have -0.0513 Voltage. The Mhz were 300/300/325/325
|
|
|
|
You need to be careful.Your going to destroy that cube. Please wait for the video.
Vegas
I would like to make two phase immersion cooling for it, but have no resources for it  But I do not see the problem to cool without cap if I place the radiator carefully. The part of a problem actually I think is that the airflow and radiator are in different levels. And also can't understand why the temp off DCDC-1 raises after my intrusion... |
|
|
|
We used BICs razor blade Cut a half of it to make it thinner and inserted it between the cap and chip to extract the glue (actually it seems to be a thermal grease) As there are many elements around it took I think 3 hours. (can try makinng some drawings to understand the way) The second one will be faster because we know how to and have som exp. Now I am testing it without cap. We placed indium foil instead of grease and put the cooling radiator on it. We set additional radiators on the aluminium clamp. But as I see the temperature is not lower than on not modified boadrs but higher! CPU is higher 3-5 degree (Celsium) and DCDC 4-5 degree Yes, the chip cap (heat spreader) is there for a reason. You should put it back on. I only asked because I was interested in replacing the thermal compound under the heat spreader. That being said, I just performed an interesting heat sink modification, which worked OK, but only lowered the temps maybe 3C in total. If I actually machined a new heat sink, instead of modifying the old one, it might work better. We have second CUBE that we modified. We just replaced the thermal grease under heat exchanger to Indium foil. The situation is the same - temperatures are higher! Actually I need to reduce Frequency to lower the temp of DCDC because it reach 95 degree.. |
|
|
|
You may have already done this ...PM this guy glen tarken see if his firmware mods work...if nothing else they have some more bells and whistles to set stuff at https://bitcointalk.org/index.php?action=profile;u=34888anyway his stuff is legit..I got some..have not installed it yet..but others on the above thread say it has helped you can also yank the LCD and use that port I"m running 6 cubes on a Titan controller ...may help get you around the problem maybe? Yep I've tried that. As their FW is based on ver 2.0 original firmware it is also not working on my system..  |
|
|
|
Yestarday we have removed the Titan chip CAP Today will test it using chip water cooling, to check if the thermal grease was a problem..  How did you remove the Titan chip cap? We used BICs razor blade Cut a half of it to make it thinner and inserted it between the cap and chip to extract the glue (actually it seems to be a thermal grease) As there are many elements around it took I think 3 hours. (can try makinng some drawings to understand the way) The second one will be faster because we know how to and have som exp. Now I am testing it without cap. We placed indium foil instead of grease and put the cooling radiator on it. We set additional radiators on the aluminium clamp. But as I see the temperature is not lower than on not modified boadrs but higher! CPU is higher 3-5 degree (Celsium) and DCDC 4-5 degree |
|
|
|
I have some issues with my titan board, that look same as yours. We can make some tests. If you would like to discuss it in PM in Russian (will be faster I think) I'm pretty sure there is no way to use anything but a titan board with a raspberry pi .....the boards are different.....so beyond getting a titan board or somehow 'breadboarding' or 'fixing your own" titan owners don't have an option of finding a jupiter/mercury/saturn card and bootstrapping it up to network firmware if you have a NEPTUNE the only hardware option I heard of that works (from a knc tech) for Titans is you can swap put in a diffrerent Raspberry PI B+ 512mb on the off chance that is what is wrong...and/or re-seat the pi to the daughter board some folk also took a magnifying glass and saw stress points on solder connection of the power plug to the controller board and a touch up of solder fixed that connection just saying long odds but still My problem is that when I'm on latest 2.0 firmware my Pi does not see any CUBEs, but version 1.02 work and see.. After hours of tests I have discovered that my Controller board has some I2C problem with one of the ports. So if some cube is connected there (even without power) the system works pretty good BUT only on versions lower than 2.0!!! Now thinking how to make dummy connector to imitate the cube and use the fifth one |
|
|
|
I have some issues with my titan board, that look same as yours. We can make some tests. If you would like to discuss it in PM in Russian (will be faster I think) |
|
|
|
Just looked once again at logs and figured out!!! (It's like a glowing lamp nead my head ) Try to folow me: 1. I have a problem with ASIC4 connector. In web it does not show temp! And cube not working. 2. The voltage on one pin ov ASIC4 connector is differrent from others connectors. 3. The 1.04 ver log show continious Die 3-2 restarted Restarting bfgminer Die 3-0 came UP 4. Ver 2.00 show I2C error 5. What a stupid guy was I!!!! THIS ASIC4 Connector F#CKs BRAIN to the system board!!! That's why nothing is working!!!! You had the cable around the wrong way? I am not sure. But if I plug one cube to bad port and one cube to any other port and set 50MHz at Cube on bad port system works continiously without restarts!!! I need to make some plug for bad port to imitate Cube!!! Need some advice on that please Here is the official answer on my issue Hi,
It is as I stated in my previous email to you: "The only reason a controller board would perform in that way that you have described is if something is not connected correctly, or is causing an interference with the communication between the controller and cubes."
It would appear that there is a short on the controller board which is causing the issue, it could be some debris or something on some point of the circuit which is causing the short, or the main I/O board has failed in some point.
The only way to resolve this would be to change the main I/O board completely.
Med vänlig hälsning | Best regards Now system is good working if Cube with no power is plugged to bad port. I need some cube imitator to create |
|
|
|
Just looked once again at logs and figured out!!! (It's like a glowing lamp nead my head ) Try to folow me: 1. I have a problem with ASIC4 connector. In web it does not show temp! And cube not working. 2. The voltage on one pin ov ASIC4 connector is differrent from others connectors. 3. The 1.04 ver log show continious Die 3-2 restarted Restarting bfgminer Die 3-0 came UP 4. Ver 2.00 show I2C error 5. What a stupid guy was I!!!! THIS ASIC4 Connector F#CKs BRAIN to the system board!!! That's why nothing is working!!!! |
|
|
|
Yestarday we have removed the Titan chip CAP Today will test it using chip water cooling, to check if the thermal grease was a problem.. |
|
|
|
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
I had set 1500 uF. The result is the same as original cubes.. cycle restarts at low versions of firmware (1.02-1.04) and no cubes at higher (I2C com error at 2.0) Will try to set all new 1000uF but a bit later.. |
|
|
|
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.. |
|
|
|
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 [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?? |
|
|
|
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 [2015-09-01 16:51:31] I2C lock failure #1
[2015-09-01 16:52:29] I2C lock failure #2
message at messagedcdc.log |
|
|
|
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?? |
|
|
|
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.99aIt 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 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?? |
|
|
|
how long should it take when upgrading 2.00 ver?? I am looking for 2 hours at this line System upgrade in progress
Copying files... files copied No wget found, syncing apt & installing wget Syncing apt-get... Can I refresh a page or smth? It should only take a good 5mins or so... Not 2 hrs unless ur inet is shit or your SD card is dead or ur inet is crap to the pi. If its hanging there that means apt-get is failing to sync & download wget. =( If thats happening to a lot of installs, I may have to rethink the whole upgrade process. All I can say is hit browser back button and try upgrading w/ the .bin file again. This screen stays for an infinite time Waited 3hrs then 5hrs.. internet is 6Mbit and SD 10class NEW one! |
|
|
|
how long should it take when upgrading 2.00 ver?? I am looking for 2 hours at this line System upgrade in progress
Copying files... files copied No wget found, syncing apt & installing wget Syncing apt-get... Can I refresh a page or smth? |
|
|
|
You were able to fix dead or zombie dies? If so, please share details! I've got 6 dies that I'd like to get working again.
he's having problems with the whole cube Actually, now it seems to be a Controller Card problem.. But no idea how to fix it yet. Previously it was workin on 2.0 ver, than came to 1.97, now working versions are 1.02-1.04 but with cycle restarts.. every 20 secs. So no real coins to find.. ^( |
|
|
|
did you try plugging the "bad" cube into one of the other asic connectors? and try putting a known good cube on the "bad" asic4 connector, -- just to double check before you tear the board apart btw the worst that should happen from replacing that cap is that it wasn't bad and you still have the same problem after it is replaced. Since you replaced it with a different cap and now you are getting different symptoms, that just seems to say it isn't the right cap for this circuit? just trying to think logically before you dissect the whole board  after this everything stops The asic6 was thermally modified with Indium and some screws and thrmal grease between plates.. |
|
|
|
|
