Hello,
Not really sure if this falls within Module Development or is more general purpose.
I ran across an interesting difference in behavior between the driver I'm porting between when it used the XOPC transition module and when I switched it over to the newer interface.
If your tag definitions in the designer do not contain the ns=1;s= portion of the definition, then the tag bounces between a "GOOD" status and an error indicating that the tag couldn't be found in the OPC-UA gateway. I didn't copy the exact error message, it flashed up fairly quickly. Once I added in the above, the tag started working correctly, as far as reading goes anyways.
I did not see this behavior with the older style even on 8.x.
Yes, I realize that the above is the recommended/required way of defining the OPC-UA item path to the tag definitions, this project was the first I did with Ignition and it didn't seem to matter, so none of the definitions in the UDT's that I set up had it in.
Anyways, this is just an informative message, nothing to do here.
Bill S.