That's very interesting. So you didn't try to program it, but you hooked up the unit. Did you try reading the code? Did you get anything at all?
The reason it's el-interesting-o is that there's a little user page for data and the official page for code and all that stuff on the Atmels. You might have cleared the data field when you tried to read the code. Now, normally that would spell fuck-ola, but what if BFL used the same code load and put the "run at lower speeds" commands in the data field. By clearing it you got a default monarch (which I think has some sort of speed control like the Single/60's had, there is no way my Monarch comes up at 699gh every time)
Well, I got no firmware to program it with. Except for BFL FW from last year... I'm not entirely sure when the "reset/overclock" happened, but I think it was when I powered on the Dragon without doing anything. Or maybe when I read the chip info. Definitely the change happened before I tried to read the firmware.
And the firmware has the "security bit" set, so there's no way to read it with the Atmel Studio. Trying to read it just gives the security bit message.
Just power cycled the "550 GH" to try to get it to lower speed again but to no avail. At 700 GH indicated by cgminer the unit eats up 470W and my current psu for it is 500W, so I'm very close to danger zone again. I'd much rather have 650 GH @ 420W. But I did point more powerful fans towards the fets yesterday. The faster unit indicates 58-60 C and the slower one 50-52 C which at least sounds fine. There could still be components crying in pain but I just wouldn't know about them.