Many of our devices are Omron PLCs, and they have many tags, so we can only use FINS to read them. However, the odd-numbered character strings will always be one digit less. Is this a driver bug? The driver defaults to inverting the even-numbered characters. This should be possible so that I don't have to write a script to handle it.
It's not one digit less, it looks like your string is in a different byte order when accessed by FINS.
FINS protocol has no concept of strings. A String is created by assembling the contiguous bytes of contiguous registers for some area. They must be laid out in memory in the correct order, as it does not look like any of the byte or word order modifiers apply to Strings (feature ticket exists).
If these are NJ or NX processors, I suspect my alternate EtherNet/IP driver will give the correct result out of the box. Consider trying it.
My assumption was that he's using the IA NJ driver for the "correct" string tag and comparing it to a tag from the FINS driver that is incorrect.
Ah, ok. Also explains the "many tags" reference--the IA driver doesn't perform very well. Also a motivator for checking out my alternate driver.
It probably never will unless Omron changes their mind. They explicitly declined to work with us or share documentation because they already have a NA partner (Indusoft lololol which doesn't even exist now because Aveva bought it).
Might be embarrassment. There are problems, particularly with booleans, that don't make them look good. (Best practices listed in my manual to avoid those problems.)