Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different best difficulty in AxeOs and the pool at version 2.0.7 #111

Closed
chillingbee opened this issue Feb 21, 2024 · 9 comments
Closed

Comments

@chillingbee
Copy link

There are different best difficultys in the AxeOs and the pool!
At ckpool my best dif. is about 8.19G and the AxeOs has about 4.29G

@19201003080114
Copy link

Normal.
Pool best diff is your all-time best, since day 1 that you connected to it.
AxeOS best diff is your session best. It resets after reset/power cycle.

@skot
Copy link
Owner

skot commented Feb 22, 2024

We have been saving best diff to NVM for a while now. I should persist across restarts. But I NVM can be reset when uploading a new firmware in some cases.

@0x7a617a75
Copy link

I am seeing a very similar thing and the differences are pretty drastic. I haven't updated my firmware recently, and the best hash appeared well after my last upgrade.
Running 2.0.7 as well.

  {
   "workername": "X",
   "hashrate1m": "422G",
   "hashrate5m": "442G",
   "hashrate1hr": "506G",
   "hashrate1d": "469G",
   "hashrate7d": "461G",
   "lastshare": 1708830059,
   "shares": 414621980,
   "bestshare": 209250669786.6476,
   "bestever": 209250669786
  },

and on the bitaxe

Results
Hash Rate:	443.68 Gh/s
Efficiency:	35.09 W/Th
Best Difficulty:	4.29G

@chillingbee
Copy link
Author

I am seeing a very similar thing and the differences are pretty drastic. I haven't updated my firmware recently, and the best hash appeared well after my last upgrade. Running 2.0.7 as well.

  {
   "workername": "X",
   "hashrate1m": "422G",
   "hashrate5m": "442G",
   "hashrate1hr": "506G",
   "hashrate1d": "469G",
   "hashrate7d": "461G",
   "lastshare": 1708830059,
   "shares": 414621980,
   "bestshare": 209250669786.6476,
   "bestever": 209250669786
  },

and on the bitaxe

Results
Hash Rate:	443.68 Gh/s
Efficiency:	35.09 W/Th
Best Difficulty:	4.29G

That´s funny and wierd! Two of my Bitaxe do have the exacly same difficulty of 4.29G

@weixiongmei
Copy link

I have the same issue, the I had a best difficulty of 34.9G in pool, but only showing as 4.29G in the miner

@weixiongmei
Copy link

Would like to have the session best difficulty rather than just the life time best difficulty in the Home page, because some of the pool doesn't shows the best difficulty...

@weixiongmei
Copy link

weixiongmei commented Feb 27, 2024

Hi @skot,

/Volumes/SSD/Codes/ESP/ESP-Miner/components/bm1397/include/bm1397.h:14:38: warning: overflow in conversion from 'long long int' to 'int' changes value from '4294967296' to '0' [-Woverflow]
   14 | static const u_int64_t NONCE_SPACE = 4294967296;

@JWelsh97
Copy link

JWelsh97 commented Mar 2, 2024

Yeah I have the same 4.29G best difficulty

@WantClue
Copy link
Collaborator

WantClue commented Mar 5, 2024

We have been saving best diff to NVM for a while now. I should persist across restarts. But I NVM can be reset when uploading a new firmware in some cases.

@WantClue WantClue closed this as completed Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants