Quote from: JBT on January 01, 2014, 07:35:32 AM

Quote from: kabopar on January 01, 2014, 03:17:06 AM

Quote from: JBT on December 31, 2013, 10:37:39 PM

Quote from: kabopar on December 31, 2013, 10:04:34 PM

Congrats! your board seems to be doing fine

Getting
cgminer version 3.8.5 - Started: [2013-12-31 09:46:00]

DRB 0: E8 32.2C (34.7C) | 22.44G/22.44Gh/s | A:435092 R:1058 HW:14051 WU:313.5
snapshot time [2014-01-01 08:56:47] (abt 23 hours)
while running with --drillbit-options int:53:2:950

HNY
Cheers

well just stop working with those setting back to default int:40:1:850 the other i now just get asc timeouts

ed. using int:52:2:850 with lot less hw errors!?
edd. using :950 produces asic timeouts

Do the asic timeouts at :950 persist or are they just a short time transient? I think that if the configuration is changed for a 'running board', then there is a short time transient until present values from the previous session are cleared. If the timeouts are persistent, then you might try 'incremental' increases as suggested by one of the people on the drillbitsystem forum.

Cheers

total timeout no hashing message: DRB 0: timing out unresponsive ASIC 0 - 6
any setting with 950 in so using int:54:2:850 for 10 min 19.8GH/s avg 30C a:2072 HW:143 so not to bad but less way less than yesterday

On the previous (pre-mod) board, I sometimes had to disconnect/reconnect the USB cable, or to cycle power to the board to make it start at 950. The present board, in particular after the firmware update has no such problems and consistently starts at 950. I assume that your board has the latest firmware, if not you should consider applying it.
I also found that my current board doesn't 'like' cgminer 3.9.0 and works consistently with the drillbit fork of 3.8.5. It works ok with 3.9.0 on a separate PC, but when connected to my main mining laptop (with a bunch of other USB miners and multiple instances of cgminer and bfgminer), it just wouldn't run on 3.9.0. The cgminer version is another thing that you may try.

Cheers