When creating names for I/O channels within the project, for some reason, channel names with numerical suffixes (e.g. 1.1.1) are treated differently and out of alphabetical order to the more conventional channel names. Then when performing a programattic block read of the card, the channels and data are again ordered differently (somewhat alphabetically, prioritising suffixed channel names). Images are attached in lieu of a tedious explanation of the mechanics of this bug/"feature".
This issue only affects ethercat slave variables, and does not seem to affect channel names for I/O in the master CRio, which makes the phenomenon so much more puzzling.
Does anyone know why this occurs or how to turn it off? Or do I just need to avoid these numerical suffixes?
It is very frustrating because not only does the project seem to apply aribtrary sorting to channel names, but arbitrary (inexplicit) sorting is also applied when doing a programmatic shared I/O variable read.