Quote from: aigeezer on July 19, 2014, 04:01:55 PM

Quote from: sjc1490 on July 19, 2014, 03:40:05 PM

Quote from: chadbu on July 19, 2014, 03:34:02 PM

for me the beep occurs once every three hours right when the network switches to a new block.
I increased the difficulty from 256 to 512. It been 3 hours and no beep yet...

Several pages back when the B1 started arriving some investigation determined the random beeps occurs when there is a HW error.

The plot thickens. Grin

One of my S3s reports 14,478 HW (I don't think I believe it) while another beside it reports 66 HW (might match the total number of beeps heard). They report 31,614 and 32,399 Accepted respectively, which I'm inclined to believe from the pool stats.

I haven't opened a case yet - gotta do unrelated things for a few hours.

Edit: detail I forgot to mention - both have "Beeper ringing" set to False and I'm not sure whether one or both actually make(s) the sounds.

Edit: more detail - both of mine have been running at 256 difficulty. They can go well over 3 hours without a beep though, then might have a few beeps in quick succession. I'll try 512 in any case.

If it's the same as the S1, you can't go by the raw numbers alone. They use this convoluted formula for some reason. I remember having an S1 that had ridiculous numbers for HW errors, I was sure it was faulty. When I plugged everything into this formula and did the math, turns out I was getting like 0.003% HW errors. I found a handy calculator. http://www.coincadence.com/antminer-s1-hardware-error/

On another topic, am I also to assume the overclocking procedures are the same as the S1? My S3's seem to be stabilizing around 440GHs which is a bit of an improvement but still low. Wanna see what happens when I crank them up a bit.