Earning bug fixed?

[Sparwen]

I´m wondering if the "bug" with low earning over I2C vs USB is fixed in this version?
Please see old reported bug at ricaun/DuinoCoinI2C#90.

Will I earn as much DUCOs with say 10 arduino I2C slaves as with 10 arduinos mining with AVR-miner?

Regards

[JK-Rolling]

I wouldn't say it's a "bug", more like a software architecture limitation. In this new DuinoI2C_ESP, I re-architected the software from scratch to fully resolve this. In my beta tester program, I did receive feedback that the earning is similar to USB. You may unlock the firmware by referring to Unlock Key <https://github.com/JK-Rolling/DuinoI2C_ESP/tree/main/esp8266#unlock-key> which allows up to 20 workers!

…

On Fri, 6 Sept 2024 at 03:53, Sparwen ***@***.***> wrote: I´m wondering if the "bug" with low earning over I2C vs USB is fixed in this version? Please see old reported bug at ricaun/DuinoCoinI2C#90 <ricaun/DuinoCoinI2C#90>. Will I earn as much DUCOs with say 10 arduino I2C slaves as with 10 arduinos mining with AVR-miner? And how can I unlock the firmeware for more than 3 workers? Regards — Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVI2YUDM3YP4HMBMMUJLSOLZVCZE5AVCNFSM6AAAAABNXGF63KVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGE2DGMZVGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[JK-Rolling]

thanks for the encouraging data!
recent experiment done (by jpx13) shows further 8% improvement if the I2C master is using 100KHz while the worker (ATtiny85) is using 400KHz.

One may also need to consider the power consumption between both setup VS the Duco earning difference too.
USB - Host + USB Hub + workers
I2C - Master + workers

[Sparwen]

Interesting!

I thought that the i2c slaves had to be on the same frequency as the i2c master?
But apparently not :D

There seems to be more or less no differens in performance regarding Shares ( -0.5% )

• 7pcs USB miners: 460680 shares for 24h
• 7pcs I2C miners: 458439 shares for 24h

But there still seems to be a slightly decrease in DUCO erning performance ( about -6% to -7% )

• 7pcs USB miners: 64.29 DUCOs/day
• 7pcs I2C miners: 59.55 DUCOs/day

That´s still awsome compared to the old code 👍

[JK-Rolling]

awesome comparison!
The earning performance is outside of the ESP control, but maybe it is justified in terms of power saving for ESP :-)

btw, I assume you're not running both USB and I2C simultaneously as Kolka dictates efficiency drops for worker that join later

[Sparwen]

No, exactly, I did not run them simultaneously. They run separately 24 hours apart :)

[JK-Rolling]

do you mind sharing more info on the setup? the table, data 7 and 8 is missing a few info
#5 (reply in thread)

[CGameDev]

Regarding the d1 mini, in the firmware can you have the option of having the onboard led be passed to one of the digital PINs as output and allow it to be turned on in the web interface. Similar to the Pico code where i change the code that i can us a LED on the PCB rather than the onBoard Pico led. I would like to design a PCB that have the ESP light on the board.

6 or 7, i think those pins dont start high or low when starting up the d1 mini, i think they are refer to as "safe" pins

[JK-Rolling]

without changing anything, pin D4 is already sharing pin with the builtin LED.
for dedicated GPIO13/D7, please use this customized DuinoI2C_ESP.ino.d1_mini.400K.ledD7.v0.20.1.bin.gz to work with Pico worker