Ignition launched from Groov accessing Opto22 PAC data tables


PROBLEM: Ignition Designer can’t read data table tags from Opto22 SNAP-PAC, but the Groov box can see the data table tags!

I’m trying to take a few screens running in a Groov project and recreate them in an instance of Ignition Designer launched from the same Groov Box.

I’m using Ignition Designer with an installed, running Opto22 PAC device Module. Tags have been imported from OPC UA. So in the Groov project, there’s a group of Range Indicator objects that are assigned to data table items, with names like “tData[0],” tdata[1]," “tdata[2],” etc. Within Ignition Designer, I’m trying to make the same tag assignments to some Moving Analog Indicators, but I can’t find the same data tables in Ignition that I can see in Groov Build - the Ignition Tag Browser only seems to show variables.

Is it possible that Ignition can’t read data tables through the Opto22 device Module? Are there some steps to take to make them visible? I’ve listed this as a Groov topic because it’s all accessed and launched from within Groov.

Any help would be appreciated.


Welcome to the forums.
Glad to see some fast adopters here… When you get a chance, we would love to hear more about your application.

(BTW, Hope you don’t mind, but I created a new Forum Category “Ignition” and moved your post to it).

As far at the tables go, it is a limitation of the way Ignition import and handle tables.
If you look at the Cirrus Link docs page, you can see that they mention this;
You can see that tables are not supported the way you are currently using the driver.

You will need to use the public string table method to get your table elements to show up in Ignition.

(Basically, Ignition ‘strong type’ all their tags and so the driver has to break out each table element into its own tag).


There’s a misleading implication in the document “Scanning Specific Tags.” On the table showing the acceptable syntax for data types, the data type “f32te” doesn’t work for table elements. Use “f32t” for both table elements and ranges.

stPublicListOfStrategyTags[1] = “f32t.onething[1].rw”;
stPublicListOfStrategyTags[2] = “f32t.rangeofthings[0-50].rw”;


Hi, @acrucet. The two examples you gave are correct (and we will ask Cirrus Link to update the Example on https://docs.chariot.io/display/CLD/Scanning+Specific+Tags).

I’m not sure why the f32te data type didn’t work for you. It works for me (to get a single element from a float table).

Opto 22 Tech Writer