I am trying to add tags with an OPC connection to an RMC200 Motion Controller with the SLC driver, as this the supported protocol for the RMC200. Tag group details are: Mode=Direct, Rate=1000ms, Data Mode=Subscribed. Values and tag qualities are good until I create more than 16 tags, at this point all the tag qualities turn to bad, tag values turn red, and tags stop communicating with RMC200.
What am I doing wrong?
It probably means you're addressing a tag that doesn't exist or otherwise results in an error when read.
The tags you've configured are likely all read as part of a single request, and once you include this bad tag the entire request fails.
After some more testing I have found this behaviour.
My address map inside the RMC200 motion controller for the tags I want to access start at address F19:0 and end at address F19:255. It seems I can only access tags in a range of 22. For example:
Is there a driver limitation to SLC driver on the ignition trial period?
Not that would result in this behavior.
Maybe you can get some Wireshark captures. Something like one capture while successfully reading F19:0 - F19:22, another capture where you've added F19:23 and it starts to fail.
I think I solved this. In my connection path for the SLC Driver I had to put a 1, since on this RMC200 it looks like the cpu is in slot 1. This forced the slc connection protocol to Bridged_EIP which is now working with all my tags.