Quote from: MrTeal on December 21, 2013, 09:12:32 PM

Quote from: i3luefire on December 21, 2013, 12:32:12 AM

Quote from: Bargraphics on December 20, 2013, 01:49:00 PM

Quote from: i3luefire on December 20, 2013, 05:30:58 AM

i have 14 chilis and 10 of them have been running for weeks and weeks without problems. the other 4 are new. 1 of the new ones runs fine for about 1-2 minutes then starts showing an error messages then it goes sick. in the midst of starting and stopping bfgminer a million times while trying to get that one working 1 of the 10 that had been running fine stopped working and now it never shows up in bfgminer even after power cycling it and switching usb ports and switching power supplies.

What do the LED lights on the chili that has the issue look like.

Remember when you power cycle, etc.. you should wait until all of the LED lights on the chili stop blinking before starting the mining software. This can cause it to hang and not be found.

What error messages are you seeing with your other chili? Have you tried switching it to a different USB port/running it solo to see if it continues with those same issues?

Hopefully we can help you out!

the one that never shows up in bfgminer goes through the normal led bootup sequence but after the leds go out and i start bfgminer nothing happens. i have not tried that one by itself yet but i did change usb ports and cables. i am trying the one that goes sick by itself right now and am waiting on it to fail to copy the error message. but it always runs at ~41-42gh with 10-15% hw.

Edit: the message is

Code:

BFL 0: Received unexpected queue result response:
BFL 0: Error: Get temp returned empty string/timed out

Edit2: the miner that does not get recognized by bfgminer shows up as an unknown device on windows. does that mean the ftdi chip is toast? because i have never had this problem before. my normal mining machine is xubuntu but i have mined with these on windows before. and i am currently mining with the other problem child on windows currently so i dont think it is a driver issue. also the one that was getting sick before has not gotten sick for over an hour. so... i am not sure what the problem was there. but eventually i will need to move it back to the mining room and out of my living room.

I have one of mine that has been giving me issues lately, and it sounds very similar to your problem. A little debugging of the VRM to read the logged faults show that it's hitting a current limit fault and the DC/DC is tripping off. It's also a great performer, 16 engines on all 8 chips. The problem was that my cooling was good enough that the temperatures stayed under the limits, and with every engine enabled and ramping up to the full voltage (1.15V) I was pulling more than 160A out of the power supply. It was hashing over 40GH/s, but it would trip the protections on the DC/DC and shut down. Limiting the voltage to 1.1V has dropped the hashrate to 39GH/s, but it also runs stable now.

I'll email you the file I used.

Quote from: i3luefire on December 21, 2013, 07:28:10 PM

Ok I performed the test and it still came up as an unrecognized device. So that means it is the ftdi chip correct? And if so what is the mfg part number?

It sounds like it. You could try opening it up in FTDI's FT Prog utility to see if it's detected there as well.

The file you emailed to me seems to have made the problem much better. the miner got sick once since the upload but that may have been pc related. is the file you uploaded "https://www.dropbox.com/s/i4rj2k1m9vrj00e/Chili14e1V1.hex" the same as the one you emailed?

Also i tried the FT_Prog utility http://www.ftdichip.com/Support/Utilities/FT_Prog_v2.8.2.0.zip and it was not able to find that miners usb chip either so i am going to order a replacement for the ftdi chip today or tomorrow from digikey or mouser. which part number is the correct one "FT232HL" or something else?