Quote from: Janezki on January 23, 2014, 04:39:26 PM

Quote from: miniasic on January 23, 2014, 12:11:04 PM

Hi,

just in case someone needs a finer speed setting:

Frequency | Hashrate | value | timeout
125.00 MHz | 1000 MHs | 0481 | 042 ms
137.50 MHz | 1100 MHs | 0501 | 039 ms
150.00 MHz | 1200 MHs | 0581 | 035 ms
162.50 MHz | 1300 MHs | 0601 | 033 ms
175.00 MHz | 1400 MHs | 0681 | 030 ms
187.50 MHz | 1500 MHs | 0701 | 028 ms
200.00 MHz | 1600 MHs | 0781 | 026 ms
212.50 MHz | 1700 MHs | 0801 | 025 ms
225.00 MHz | 1800 MHs | 0881 | 023 ms
237.50 MHz | 1900 MHs | 0901 | 022 ms
250.00 MHz | 2000 MHs | 0981 | 021 ms
262.50 MHz | 2100 MHs | 0A01 | 020 ms
275.00 MHz | 2200 MHs | 0A81 | 019 ms

or even finer for tweaking your individual miner:
237.50 MHz | 1900 MHs | 1285 | 022 ms
243.75 MHz | 1950 MHs | 1305 | 022 ms
250.00 MHz | 2000 MHs | 1385 | 021 ms
256.25 MHz | 2050 MHs | 1405 | 020 ms
262.50 MHz | 2100 MHs | 1485 | 020 ms
268.75 MHz | 2150 MHs | 1505 | 019 ms
275.00 MHz | 2200 MHs | 1585 | 019 ms
281.25 MHz | 2250 MHs | 1605 | 019 ms
287.50 MHz | 2300 MHs | 1685 | 018 ms
293.75 MHz | 2350 MHs | 1705 | 018 ms
300.00 MHz | 2400 MHs | 1785 | 017 ms

But beware. While playing around with this values or better some values not respecting the forumular given in the U1 manual I somehow wrecked my antminers clock generation.

Greetings,

miniasic.

That's interesting - what does the timeout mean?
Is there any difference for example using 0981 or 1385 for 2GHz?
Can you give values for higher hashrates? I'm currently running mine steady @ 2.6 (4c81) with HW=0, just wanting to see if I could push it just a bit more. Grin

(2.8 (4d81) is too much, the miner doesn't start)

Ok, more of this:

300.00 MHz | 2400 MHs | 1785 | 017 ms
306.25 MHz | 2450 MHs | 1805 | 017 ms
312.50 MHz | 2500 MHs | 1885 | 017 ms
318.75 MHz | 2550 MHs | 1905 | 016 ms
325.00 MHz | 2600 MHs | 1985 | 016 ms
331.25 MHz | 2650 MHs | 1A05 | 016 ms
337.50 MHz | 2700 MHs | 1A85 | 015 ms
343.75 MHz | 2750 MHs | 1B05 | 015 ms
350.00 MHz | 2800 MHs | 1B85 | 015 ms
356.25 MHz | 2850 MHs | 1C05 | 015 ms
362.50 MHz | 2900 MHs | 1C85 | 014 ms
368.75 MHz | 2950 MHs | 1D05 | 014 ms
375.00 MHz | 3000 MHs | 1D85 | 014 ms

or even smaller steps:

300.00 MHz | 2400 MHs | 2F86 | 017 ms
303.12 MHz | 2425 MHs | 3006 | 017 ms
306.25 MHz | 2450 MHs | 3086 | 017 ms
309.38 MHz | 2475 MHs | 3106 | 017 ms
312.50 MHz | 2500 MHs | 3186 | 017 ms
315.62 MHz | 2525 MHs | 3206 | 017 ms
318.75 MHz | 2550 MHs | 3286 | 016 ms
321.88 MHz | 2575 MHs | 3306 | 016 ms
325.00 MHz | 2600 MHs | 3386 | 016 ms
328.12 MHz | 2625 MHs | 3406 | 016 ms
331.25 MHz | 2650 MHs | 3486 | 016 ms
334.38 MHz | 2675 MHs | 3506 | 016 ms
337.50 MHz | 2700 MHs | 3586 | 015 ms
340.62 MHz | 2725 MHs | 3606 | 015 ms
343.75 MHz | 2750 MHs | 3686 | 015 ms
346.88 MHz | 2775 MHs | 3706 | 015 ms
350.00 MHz | 2800 MHs | 3786 | 015 ms

The timeout value is for the original cgminer-bitmaint version where you had to provision a timeout-value (default 20 * 100 ms). The slower the device is, the longer it takes to calculate the hash. bfgminer uses 1.5sec timeout for all values. cgminer-bitmaint uses the deployed value. After value * 100ms it times out the calulation an no nonce was found. You can see this for bfg and cg if you run it in debug mode.

Greetings,

miniasic.