Please take this post as purely inquisitive!

This (and related) issue has enjoyed repeat mentions in the release notes as having been fixed.

Has anyone noticed anything like this in the latest rev? (3.10.2.1)

Longtime forum member may recall that I am a bit apprehensive when it comes to updating to a new firmware/software for my PAC projects. In my mind, I think that I have a handle on (most of) the issues that live in the versions that I have maintained and I neither desire nor have time to find, understand and mitigate any new issues with the progression of new releases.

I think that now, the time has come for me(us) to jump to the latest FW/SW version and examine the underbelly.

I think that this issue may be a cause of a problem that I am seeing in Vers 1.7.1.1, and 1.9.2.0

release note references

Ver 1.8.0.19 bugfix 13

Ver 1.10.0.11 bugfix 18

Ver 2.2.1.1 bugfix 1 (* somewhat related*)