Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

Geo SCADA Registry values (feature request)

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.


Geo SCADA Registry values (feature request)

In the past, when using the registry in older ClearSCADA versions, we would open up the local Windows Registry Editor to review the current keys and values that have been configured on client machine in question.


Moving to the integrated registry in Geo SCADA 2019 and 2020, we have found it difficult to manage and review the keys and values during development. The 'view status' on the CDBUser object allows review of the total registry keys, but I feel that it would be very advantageous to be able to review all available and configured keys for a client.


And a clarification... the 2019 release notes mention:

To facilitate Virtual ViewX, for which multiple instances may be executing on the same host, we have moved these settings from the registry to the database and associated them with the logged in user, dynamically saved to the database.Therefore,the local PC registry will no longer be read by ViewX, and a user will share these 'registry' settings on sessions when logged in to different devices.This affects both Virtual ViewX and ViewX.

In my basic tests (GS 2020 December 2020 release), I have found that the registry keys are shared per client, not per user. Connecting to a remote Geo SCADA server, my local ViewX client reported the same value for registry key x for two different users - whereas the ViewX on the server (localhost) had a different registry value for key x. Is this expected? Just wanted to make sure I'm not crazy.

I'd also like to confirm that the registry values are stored on the Main server.



2 Replies 2
Janeway Janeway

Re: Geo SCADA Registry values (feature request)

Hi Aaron,


the 'registry' had to move for good reasons, and the user account was the best place to put it. However, there are some gaps to be examined.

a) It's no longer possible to have workstation-specific data, so a user with two sessions on one server from different PCs share the same settings. Adding a workstation name function would allow some separation.

b) No way to inspect and set values from an API


I don't understand how you get per client settings, unless your client is communicating with older servers?


Re: Geo SCADA Registry values (feature request)

I've used this Registry functionality quite a bit recently.


There's obviously the potential to have confusion here in regards to the term 'user'.

The "old" Registry behaviour considered a 'user' to be a Windows User (and depending on the Windows settings this may or may not have been replicated across logical computers.. Windows default domain behaviour is that the LOCAL_USER HKEY is not replicated, and so different logical computers would have had different registry settings, in addition to different users on the same logical computer).


The "new" Registry behaviour is very much per GeoSCADA user.  I've tested this and can confirm that the Registry settings are shared for the same GeoSCADA user across logical computers, and across Windows user accounts (just as the GeoSCADA help documentation suggests).


As noted by Steve: to get 'per logical computer' settings, or 'per Windows user' settings, you would need to add something extra to the Registry key being used, and that will get "difficult".  Whilst VBscript has some ability to access the local machine name, and the local user name, animation expressions do NOT have such a capability, so you would typically need to try to get this information migrating from the script environment into an animation expression... and that seems like a hill I would not want to climb.



Given that ClearSCADA already had the capability to write to the local Windows Registry, it may be worth considering adding another set of methods etc to essentially keep the old behaviour still.

i.e. where the "new" functionality is via SetRegistry / GetRegistry / REGISTRY() items... perhaps there could be another group like SetLocalRegistry() / GetLocalRegistry() / LOCALREGISTRY().. which were just renamed versions of the "old" ClearSCADA functionality.

Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..