GenTarkin, in november (30/11) I've purchased your 0.99e firmware on ebay via bitcoinlasvegas.net. It works great on my Titan, no more babysitting for it

A few days ago, I sent to you an e-mail to have access to your new firmware on the new shop but I didn't receive your answer. I know that I am an "unverified customer" and I read the problems with bitcoinlasvegas and you, but I would know if you can give access to the new firmware to the customers in the same situation.

Thanks for you great work !

The Eth pool at the NiceHash pay out in Bitcoin. But the price is lower than if you mine with other pools. That is the price to pay.

Have been running for 30 hours now on the new firmware, not particularly happy with it, bfgminer shuts down every 4 hours, nicehash reported down time 20min, then 30 min.

Had to downgrade back to 0.99e version for now.

I have noticed that when multiple dies fail at the same time that this is a great signal that there is a power problem. I have alarms set when mh/s drops below a certain level I can manually monitor the advanced page. On the last alarm 2 dies failed at the same time, on the same cube and your firmware soft restarted them. A few hours later the whole cube failed because the psu shutdown so I checked the cube and discovered the fried pcie connector.  And this PCIE was seriously burnt, there wasn't much left of it, the male/female were melted/fused together, I needed pliers to separate them.  In this case restarting the dies earlier certainly didn't help.

So maybe some logic that when 2 or more dies fail at the same time just shut the whole cube down till it is cold started or rebooted.  I don't know if or how often this would generate false alarms, but I've never noticed 2 dies failing at the same time except in this instance.

I suppose. However when someone puts a cube on your doorstep that did this:

You wonder if that cube plug is just a limiting factor.

Ultimately it's up to everyone to do what is best in their circumstances. :-)

Well, these two units are currently running approximately one (1) inch away from each other, so the environment is pretty constant. The difference between the two is the difference between an average DC-DC temp of

ASIC slot   Temperature   DC/DC avg temp   Clock   Type
1   ---   ---   ---   OFF
2   32.5 ℃   47.4 ℃   225 MHz   TI
3   ---   ---   ---   OFF
4   ---   ---   ---   OFF
5   ---   ---   ---   OFF
6   41 ℃   62.0 ℃   275 MHz   TI

Which is pretty big for that extra 10mh.

You mentioned that your power supply cables melted at least once, and I just saw a picture of a guy's power supply that basically started to set fire to his house. Glad his house did not burn down, but the problem was the same, power supply cables melted. Fixing melted units that blow the PCB connectors is a real bear and I just got a Neptune in that had a blown power cable that led to a short on pin 6 (this time to the .7 line which allows it to work, but very weird) which proves board burns can damage other Neptunes and Titans due to the lack of signal isolation on the controllers and/or the units.

Perhaps a good code release would be a "do not pull more than X watts from the supply lines" so people could put in 180 to be nice and comfortable up to 260+ if they really want to see things go foom or something. As always I stand by to fix the blown cubes, but it would be better if they didn't blow in the first place.

Some hard data for you Titan users: Moral: These things were built to hash at 60mh, going faster makes miner sad.

I'm running two miners here, one is a stock reference one running at 275mhz, the other is a client's repaired one (with bypass wires) running at 225mhz. Note the power, DC-DC temp difference, and other differences. It's a lot of extra oomph to get that magical extra 10mh....

ASIC 2 (Speed 225mhz)
Temp : 31.0 °C
Power : 187.445 W

DC/DC   Voltage (V)   Current (A)   Power (W)   Temperature (°C)
0   0.7878   28.781222.674   47.500
1   0.7874   29.1875   22.982   46.900
2   0.7886   29.4062   23.190   45.900
3   0.7883   29.9062   23.575   45.300
4   0.7920   30.0938   23.834   44.100
5   0.7922   29.3438   23.246   43.900
6   0.7892   30.3750   23.972   43.900
7   0.7892   30.3750   23.972   45.100

ASIC 6 (275mhz)
Temp : 38.5 °C
Power : 232.520 W

DC/DC   Voltage (V)   Current (A)   Power (W)   Temperature (°C)
0   0.7858   36.5000   28.682   61.600
1   0.7863   36.5625   28.749   63.400
2   0.7819   36.8750   28.833   61.400
3   0.7841   36.9375   28.963   60.400
4   0.7836   37.3125   29.238   55.900
5   0.7847   37.9375   29.770   55.700
6   0.7826   37.3125   29.201   57.700
7   0.7861   37.0000   29.086   57.100

 KNC 0:       | 59.00/61.52/61.57Mh/s | A:315 R:1+0(.32%) HW: 64/.59%
 KNC 1:       | 71.02/72.75/72.66Mh/s | A:385 R:2+0(.52%) HW: 73/.57%

I would recommend slowing down to 60mh total. That is what these were designed for.

So, I have been running v1.0.0 for over 48 hours. It took awhile to complete auto-tuning but I am impressed, it lowered power consumption by 25-30 watts and has been running stable. It's time to get another license Nice background BTW  

The die pulls power, but throws errors from time to time on the die that shuts down either the die or the die next to it as well. Fixed by cycling the miner, but then it comes back. Sometimes you see the current on the supplies drop to zero.

I don't have a unit now that does this, but did awhile back.

Other annoyances include dies that hash fine for awhile, then the supplies drop to zero. Rebooting the cube fixes it, sometimes dropping the supplies to zero does so as well. Also an odd one, I had a unit that once had a power supply simply disappear. Because I was running it at 200mhz the other supply handled the load fine but it was odd.

These are the days of our lives. :-)