x70 Configuration Points InService Property Override

[DStobie]

For configuration points in GeoSCADA for x70 RTU's, the InService property cannot have the property override for the InService property set to False....

This means if i create a template and write some logic that has certain tags within it, i cannot enforce that in the template instance that the end user keeps the point in service to avoid errors with having mismatch between configuration and logic. 

In all templates i've made, i want to be able to enforce that all instances have the logic variables that are required permanently enabled - I let the user change the Inservice property of the connected DNP points if they dont actually need that point - but not to disable the configuration point. 

I also can't see how to enforce them to use the logic from the template, and not to be able to export it and modify it - perhaps i'm missing how to do this ?

  Currently, if i remove the property override for the InService property of a configuration point, it just turns it back on automatically, is this intended operation ? Does the same behavior apply to the logic itself, i can't spot how to stop the instances logic being exported and modified ?

[AndrewScott · Accepted solution]

The in-service setting on SPx70 configuration items is always overridden. This is to ensure that a configuration import from RemoteConnect or upload from the SPx70 device can always enable or disable the item based on whether or not it exists in the imported/uploaded configuration (in lieu of deleting the item when missing). This ensures there are no mismatches between the imported/uploaded logic application and the configuration items used by the logic application.

The 'In Service' Check Box and Items Taken Out of Service 

The special "DocumentContent" property override on the SPx70 device controls whether or not the logic application is shared with the template instances or if the device in each instance has its own logic application. NB. This property also covers other settings, such as firewalls, DNP3 routing table, Modbus store & forward table, IP routing table, NAT table and object browsers.

[DStobie]

I understand the reasoning, to prevent errors on an import, but it stops me from preventing errors from a user fiddling with points. Given i don't want them to able to import the logic, for me this takes preference. Rather than locking the point, can not generate errors in the report and configuration so we know we have things to fix ? 

The document content property override affecting all those manner of things is also a problem. It means that if if i want to add custom routes to each of my sites, as is the case for me, i have to enable to the property override. If i then find errors in the logic program and correct it in the template, it doesn't propagate to the sites because the property override is set. If i clear the property override to force the logic to propagate, to the site instances, i lose the custom DNP routing.  It was much better when the route table was a separate object with separate property overrides, this hasn't been well thought out. Now, when i correct the logic, i have to export it from the template and then import it into each and every site instance. This is fine whilst i have three, but it's not fine if i roll this out to 500 sites that i want to be running the exact same application. In fact i would suggest this is a major problem that would prevent from ever considering going past the few bespoke sites we are doing at present.

The other gaff i am finding. If i have template set up and realise i have an extra point that i want to put into the logic, i go into the configuration point and edit the logic data type. I then expect that i will export my project to remote connect so I can modify the logic to use this new variable. Instead GeoSCADA tells me there is a mismatch in my logic and my configuration and prevents me exporting the logic so i can correct the issue ? the only way to fix it is to go back and undo your changes and export the logic first, or clear the logic project altogether and just export the config (but you need to have exported the logic first or you've lost it !)

[geoffpatton]

Since it is designed that way a work around to that is you could have you logic place the points in service.

Probably the best way is to have a logic program that makes sure they are in service and then it executes the logic program of the actual logic you need performed.