Nice.

Is there a way for me to access this through my gopher client?

A little update from my side: I added an oled display and an arduino to my I2C setup to generate some traffic. While testing some changes to make things faster I ran into issues with unreliable communication. Errors will pop up several times a day, causing my reboot logic to trigger. I just undid th...

The pin 1 dot wouldn't line up with pin 1 if it was on the 14 pin side...

Cheers

Hi Angus, thx.


It might be a while until I get up to speed with the IDF. I'm working on a little arduino project right now, and rather would finish this first.

Cheers

Hi Angus, thanks for the feedback! I had a look at the performance penalty of using the slower address. I counted the cycles used for a call to "i2cSetCmd" for both variants. Using the 3xxx address, I get at 0.733µs,while the 6xxx address makes i2cSetCmd take 1.046µs or 142.7% of the original versio...

FWIW, you can't have lambdas inherit any context if you want to use function pointers.

I looked them up a while ago because I wanted to add some context to an ISR, but no dice...

Hans, Others have been having this problem as well and I shared your post with them. Thanks to your discovery, the problem may be resolved. An issue has been raised on Github regarding this: https://github.com/espressif/arduino-esp32/issues/286 . You might want to subscribe to that issue on there t...

I'll give that a look - define "much better" though... are you seeing errors still, but fewer, or no problems at all (so far)? Well, since I just made the change, I didn't want to jinx it :) It's now been running for 63000 seconds at a cycle time of 14ms = 4,500,000 updates so far, and I haven't sp...

Heh, I read that one a while ago.

Problem is, some hardware vendors require RTR's if you want to communicate with their equipment.

Guess they failed to read the linked post

RTR's are a nuisance.


Cheers

Nice.

Dont't forget about those pesky RTR frames

Cheers