Compatibility Report Obelisk SC1 Slim

Original I posted this in General by mistake, so I reposted it here i BitCoin. I tried to delete the post in General but do not have access

ASIC compatibility report

Device: Obelisk Obelisk SC1 Slim Gen2
Firmware: 1.60
Stratum user agent: cgminer/4.10.0

Jobs received, nothing submitted. The miner is not hashing this work. Likely a work-format or algorithm mismatch.

Outcome

  • TCP connections: 1

  • stratum sessions: 1

  • jobs received: 58 (1 with clean_jobs)

  • shares: 0 submitted, 0 accepted

  • session: 1374s

  • blocks: none submitted this session

Dialect

subscribe        : 1 param(s), widths [14]
extranonce1      : 4 bytes
extranonce2_size : 8
difficulty       : [64]
methods used     : mining.authorize, mining.notify, mining.set_difficulty, mining.subscribe
non-standard     : none

Environment

  • datum-blake2b image (gateway 39f9c3c82df72736f0ac9417ac388885ce32340e, tooling 140b8ccab213)

Notes

Spins up and Hashrate on Obelisk Dashboard climbs but not on Datum Gateway Dashbord

Worker names are hashed and passwords dropped at capture time.

Share this in the Bitcoin section of the forum:
Bitcoin - PaulsCode (a free account is needed to post)
or, if you already use GitHub:

Today I ran a second test, using the RC5 release on my Start9 setup and I added another hashboard, factyory reset and ran AutoTune, when I was connected to the a officiel Sia Coin pool.
I found a post where Paul was testing on this setup
Pool URL:
stratum+tcp://sc.f2pool.com:7788

Worker:
26117c19ca3975b315d663dcbbc19cf9c07274f441689d4392ed380b2337589ef1aacfbdc93f.ObeliskSC1

Password:
x

And I did the same and the miner was hasning as expected on this pool climbing to about 950 Gh/s

I then updated to mine (solo) on my Start9 setup, but the same result as previous, Datum showed 1 client connected but no hashrate. I tested for about 1 hour with no changes.
On the Datum config I tried with and without Allow hasher time rolling for BLAKE2b jobs

A extract from the Datum log