So, I finally got back home and some time to play with this again.
Running v0.4.1 and I'm still getting the PDU encoding too big warning when trying to enable some tags (both integers and strings).
You made it sound like maybe the OID tree should be browsable now in the quick client, but I only show the diagnostics folder with Address, Connected, and Status tags.
Tried it with a Cisco, MikroTik, and opnSense. (all 3 only show those 3 diagnostics tags, but only testing the strings with the Cisco right now).
Working really well now. I have one string on the Cisco that if I put it in the same tag group as the others, it breaks all of them, but that's not a huge deal. Great work otherwise!!
The OPC quick client with this Cisco is virtually unusable though due to the sheer amount of OIDs it has. Not sure if it's possible to represent them as a structured tree that can be dynamically built so you can drill down into it rather than representing as one long list?
It's the identity OID of 1.3.6.1.2.1.1.1.0
Using your diagnostics, it shows it's a datatype of OctetString with an expected size of 256. String itself is 253 characters when read.
I’m open to this, but my concern is that the tree would be super deep. Maybe some type of collapsed tree, where nodes with only one child are merged? I’m open to really any suggestions.
