EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2019-11-26 02:07 PM . Last Modified: 2023-05-03 12:21 AM
>>Message imported from previous forum - Category:ClearSCADA Software<<
User: kvacola, originally posted: 2019-10-03 21:05:46 Id:531
I'm trying to get a relative reference to Parameter String, based on the integer value of an Analog point, and shove this into a DataSet row field. The Analog Point just has a value from 1-10 (int), and this feeds into which well I'm currently testing. So a fully-qualified reference for this Parameter String value would look something like this:
"~MAIN.SCADA.Field_1.SAT_Test_01.Test Separator.Well ##.Well LSD.String"
Where the '##' is the Analog Point value. The first part, "~MAIN.SCADA.Field_1.SAT_Test_01" is the variable part, the rest of the structure would stay the same no matter which "SAT" I'm looking at.
Am I asking too much? Should this be stored in another Parameter String, perhaps filled by a logic program running in the background?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2019-11-26 02:07 PM
>>Responses imported from previous forum
Reply From User: adamwoodland, posted: 2019-10-03 22:56:08
If you're not using templates you might want to use data grids rather than data sets.
If you are using templates then the data set row object should be in the template (so the fullname is irrelevant) and can only reference objects in that template
Reply From User: kvacola, posted: 2019-10-04 14:43:34
Yes I'm using data grids and templates. This dataset row is a template that gets instantiated within another template (Test Sep within a Facility). I've referenced things outside a nested template before, it's just this complicated concatenation.
Reply From User: BevanWeiss, posted: 2019-10-04 22:41:57
It seems like your Data Set Row should actually be defined within the Well Template. It appears that you are defining a number of them within a higher level template that contains multiple wells (which wouldn't be the best way to do this).
Then within the Data Set Row definition you should really only have a relative expression such as
".Well LSD.String"
You may have other fields in your Data Set Row which are ".Well Production Rate", ".Well Depth", "Well Expected Production Rate", "Well Projected Volume" etc etc.
You would probably also want one that is "..Separator ID", possibly one that is "...Site ID" etc
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2019-11-26 02:07 PM
>>Responses imported from previous forum
Reply From User: adamwoodland, posted: 2019-10-03 22:56:08
If you're not using templates you might want to use data grids rather than data sets.
If you are using templates then the data set row object should be in the template (so the fullname is irrelevant) and can only reference objects in that template
Reply From User: kvacola, posted: 2019-10-04 14:43:34
Yes I'm using data grids and templates. This dataset row is a template that gets instantiated within another template (Test Sep within a Facility). I've referenced things outside a nested template before, it's just this complicated concatenation.
Reply From User: BevanWeiss, posted: 2019-10-04 22:41:57
It seems like your Data Set Row should actually be defined within the Well Template. It appears that you are defining a number of them within a higher level template that contains multiple wells (which wouldn't be the best way to do this).
Then within the Data Set Row definition you should really only have a relative expression such as
".Well LSD.String"
You may have other fields in your Data Set Row which are ".Well Production Rate", ".Well Depth", "Well Expected Production Rate", "Well Projected Volume" etc etc.
You would probably also want one that is "..Separator ID", possibly one that is "...Site ID" etc
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.