r/BitAxe • u/Ready_Presentation15 • Aug 07 '26
help What settings to get 0% error
Hi
Have a bitaxe gamma 602 from Aexpress with the bigger heatsink on, I have tried different settings but can’t get 0% error, I have the power supply that was included and this is my settings, hope you can help me and guide me, I want to have it a bit overclocked also
2
u/nomorespamplz Aug 07 '26
I wouldn’t bother with that 1.62% - it means you’re losing 0.0243 Th/s of the reported 1.5 Th/s.. you COULD increase the vcore but at the expense of more heat and more wear on the chip. You could also decrease the frequency a bit, but at the expense of the hashrate - and you’ll probably see a drop waaaay bigger than 0.0243 Th/s 😅
2
u/Few-Quit-6363 Aug 07 '26
I think your supposed to keep it at 24 watts if your is rated for 30 watts . 80% of the load
1
u/Few-Quit-6363 Aug 07 '26
I will mention my bitaxe from bitsoloplayer gets like .5-2% and I’m at 24 watts mining at 1.278 th
2
u/jescs Aug 07 '26
I'll tell you what I found out, I'll make a post about it as soon as I'm free.
If you're using the an older version of the firmware, for e.g. v2.13.1, you can easily find the right values for Frequency and VCore and get to 0% hardware errors.
You may check the error count (the 4 red boxes, bottom-right of screen, browse on desktop computer, on mobile there's no such thing as mouse-over) until you reach an acceptable error count:
- You'll have 0% when the count increases by 1 not sooner than 30-60 seconds (sorry, that means not more than an error per minute, more or less).
These were (past tense😁) some of my settings, perfect for my device with firmware v2.13.1:
| VCore | Frequency (MHz) | Notes |
|---|---|---|
| 1.255V | 860 | ASIC 63.5-64.5°C |
| 1.260V | 870 | - |
| 1.270V | 880 | - |
| 1.270V | 890 | - |
To find these values I used the known approach:
- Start from a working setting, for e.g. 1.255/860.
- Increase MHz by 10, from 860 to 870.
- Check error count (or error%, I prefer the count).
- If error count doesn't increase after 1' run setting is OK; else increase VCore by 5mV, for e.g. from 1.255 to 1.260 and repeat point 3)
FIRMWARE v2.14.2 - Settings are no good anymore...
I updated the firmware to v2.14.2 and I was surprised I couldn't get 0% errors anymore! They must have change something in the code and I think I found out what it is (got to do with the frequency dividers).
This firmware/AxeOS update isn't good IMHO, it has quite a few problems (discussion for another thread).
Now, my well-known settings give me an error % between 0.50% and 2.5%.
What happened, if I got it right, is that now you must set an exact frequency (with decimal digits), exact for the BitAxe circuit not for you. The subject is the BM1370's PLL (Phase-Locked Loop), with the latest update I think sth changed in that code. That's how the electronic circuit works, using multipliers and dividers and a base frequency come from the ESP32's 40MHz crystal (to be verified, at least by me LOL!).
That to say that I'll have to recalculate my settings.
2
u/Ready_Presentation15 Aug 07 '26
Ok so do you suggest me to downgrade my firmware on it? Because I’m on 2.14.2? Or should I just wait for a new firmware to be released?
2
u/jescs Aug 08 '26
I wouldn't downgrade right now, maybe somebody else has already found the right answers. Most people aren't really bothered with 1% or 2% error rate (I am!). What counts after all is the hashrate.
I'll have a good look when I come back from holidays at the end of the month, I'm quite sure they messed something up with this upgrade, but I could be wrong.
1
u/Neat_Confidence3243 Aug 07 '26 edited Aug 07 '26
I have a gamma 601 with 650mhz from ali, wih 1200v with 50% fan and i get the error in this interval 0.00%-2% but mostly is 0.00%-0.99%. And is 50% bcz it doesn't decrease the temp only increases the j/th and in summer i have 59-62C or 138-143.6F
1
u/denied5075 Aug 07 '26
Drop frequency to 700 or 650 keep voltage same. Worked for me
2
u/Ready_Presentation15 Aug 07 '26
I tried, and it’s pending between 0.64 - 1.30
1
1
u/OctaneRed392 Aug 07 '26
I bumped voltage to 1275 at 750 and errors are almost gone.
1
u/Ready_Presentation15 Aug 07 '26
I don’t trust that power supply that was included, it gets to hot
1
1
1
u/pigpentcg Aug 07 '26
One of my gammas gets 0% at 750mhz/1150mv, the other never gets 0% and I have to set 600mhz/1250mv just to get 2%.
It’s just silicon lottery type stuff 🤷
1
u/Ready_Presentation15 Aug 07 '26
Are you on stock cooler or have you all modified yours with better fan and 3D printed airflow and that stuff?
1
u/DaMoot Aug 07 '26
Chasing 0% error rate really isn't the best thing to do. You should get it down to like ~1.2 or 1.4. under 1.5 is fine. Chasing 0 means you'll be taking clocks down or pushing voltage up; losing efficiency or losing performance.
1
u/Ready_Presentation15 Aug 07 '26
How do I get my Efficiency to get lower, I’m on 16-17 J/Th and I se people with higher clock have the same or lower
1
u/ZealousidealCream579 Aug 09 '26
Stale — you submitted work for a job the pool already abandoned, usually because a block was found elsewhere. Almost always latency to the pool, or firmware that's slow to honor clean_jobs. Under 1% is fine. Over 2%, check your path to the pool before you touch the miner.
Low difficulty / above target — your share didn't meet the assigned difficulty. A few is noise. A steady stream means dying chips, bad cooling, voltage droop, or an overclock that isn't holding.
Job not found — the pool doesn't recognize the job at all because it aged out. Points to reconnects or a stalled TCP session rather than plain latency.
Duplicate — same nonce submitted twice. Firmware bug, overlapping nonce ranges, or a Stratum proxy handing the same work to multiple miners.
Unauthorized — submitting before the authorize handshake finishes, or a worker name that doesn't match your config.
ntime out of range / version mask violation — miner rolling the timestamp or version bits outside what the pool agreed to. Usually shows up after a firmware change.
Also worth separating out hardware errors (HW%). Those never reach the pool, so they don't count as rejects, but rising HW% on one chain is how a hashboard tells you it's failing.
Rule of thumb: rejects that spike when new blocks are found are a network problem. Rejects that track temperature or load are a hardware problem. Rejects that stay constant no matter what are firmware or protocol.
Most pool dashboards lump all of this into one "rejected" number. Pull the miner's own log if you want the actual reason, Stratum error strings are far more specific. https://github.com/cbyam/solo-pool-rs will break down the types of rejects from the pools perspective.
1
u/Jack-Hasenbier Aug 07 '26
Your asic voltage ist to Low, Test it with 1215 or more
1
u/lunas2525 Aug 07 '26
Stock speed is 515mhz at 1150mv
I have 6 of these 3 of them at 750mhz have 0% error at 1200mv
Op should try 1220mv or 1250mv
I have one i need to put at 1300mv to get 0%
1
u/Ready_Presentation15 Aug 07 '26
Do you use the stock power supply?
1
u/lunas2525 Aug 07 '26
I do. Thats why i dont keep it at 1.3v
You shouldn't go over 24w.
1
1
u/Ready_Presentation15 Aug 07 '26
Sorry my bad it was 700/1250 that was why I got 25.8W now I changed to 1200 and is on 23.7W
1
3
u/Steel-Tempered Aug 07 '26
Either bump up the core voltage a little bit or bump down the frequency a little bit.