I am looking for some help in directly tagging parameter files on FT View SE.
I have experience of directly tagging parameter files when using ME, but I would appear to be failing with SE
To try and explain I created a parameter test screen on my working SE System, the display at runtime is image " ft view se parameter tags "
As you can see I have 5 multistate indicators.
The top 1-4 have their connection parameters defined from the parameter file list as in image " fr view se parameter file "
Using #2,#3,#5& #6
The multistate indicators in error are connected as per image " ft view se properties."
However the function multistate with label dt ( direct tag ) has it’s controller shortcut pointed directly at B3:0.8 in the same slc controller
I have tried various formats of {::[r]B3:0.8} & [r]B3:0.8 in my zParameterTest file.
I also have used the /P zParamterTest in the button actions selection for calling the graphics.
Does it mean I have to create HMI Tags in the HMI Tag Server and then address these tags in parameter files?
I have several screens it was planning to convert from ME to SE and that would be a massive inconvenience.
Hoping someone can help and this makes sense.
I have experience of directly tagging parameter files when using ME, but I would appear to be failing with SE
To try and explain I created a parameter test screen on my working SE System, the display at runtime is image " ft view se parameter tags "
As you can see I have 5 multistate indicators.
The top 1-4 have their connection parameters defined from the parameter file list as in image " fr view se parameter file "
Using #2,#3,#5& #6
The multistate indicators in error are connected as per image " ft view se properties."
However the function multistate with label dt ( direct tag ) has it’s controller shortcut pointed directly at B3:0.8 in the same slc controller
I have tried various formats of {::[r]B3:0.8} & [r]B3:0.8 in my zParameterTest file.
I also have used the /P zParamterTest in the button actions selection for calling the graphics.
Does it mean I have to create HMI Tags in the HMI Tag Server and then address these tags in parameter files?
I have several screens it was planning to convert from ME to SE and that would be a massive inconvenience.
Hoping someone can help and this makes sense.