Custom config params in ETM-standard config.redu file

[NikolayLevchenko]

Hi,

While trying to understand the idea with fwdDp config entry in REDU sustem, I came acress something a little strange in ETM-standard "config.redu" file:

Code: Select all

# General settings
[general]

# modified value for connectRetries
# timespan for connectRetries x connectDelay has to be longer than
# passiveRecoveryTimeout for the data-manager
connectRetries = 120

# Stop manager/PVSS has to be executed via different DP per system
($host1) DP_ManagerExit = "_Managers.Exit"
($host2) DP_ManagerExit = "_Managers_2.Exit"

# Refresh manager (UI) per DP has to be executed via different DP per system
($host1) DP_ManagerRefresh = "_Managers.Refresh"
($host2) DP_ManagerRefresh = "_Managers_2.Refresh"

# Datapoints for message and config statistics  
($host1) DP_StatisticsPrefix = "_Stat"
($host2) DP_StatisticsPrefix = "_Stat_2"

Can someone explain what is the idea with these strange entries: DP_ManagerExit, DP_ManagerRefresh, DP_StatisticsPrefix?
They don't seem to be "standard" config file entries, not described in Help, etc...
What do they mean and what do they do?

[leoknipp]

With those entries you can define which dp elements shall be used for a specific task:
DP_ManagerExit - which dp element can be set to stop a manager
DP_ManagerRefresh - which dp elements shall be used to send a refresh
More information for the _Managers datapoint type you can find in the WinCC OA Documentation.
DP_StatisticsPrefix - prefix for the statistics datapoints

You can ignore these entries and there is no need to modify them.
In future versions the entries will not be defined any more in config.redu as the manager used the correct datapoints by default.

Best Regards
Leopold Knipp
Senior Support Specialist

[NikolayLevchenko]

Thanks for the information, Leopold.

I am not planning to touch ETM-supplied "config.redu" file but I do need to have some of my project specific DP's to work the same way. That is why I was trying to understand how to configure this.

I have a simple diag script that runs on each server and collects some server specific diagnostic info into a DPs called "Diag_ServerA" and "Diag_ServerB" (DPT: DiagnosticServer).
Since it runs on both ACTIVE and PASSIVE servers, I need to set this up so it works properly so that even when server B is PASSIVE it could still write to "Diag_ServerB" and the data is accepted.

So is it enough for me to put smth like this into my project-specific "confiug.redu"?

Code: Select all

[event]
fwdDpType = "DiagnosticServer."

Or do I need to define some "special" variables like in ETM-standard "config.redu"?

[leoknipp]

Yes, if a script on a passive server shall be able to set a dp element you only have to add fwdDp or fwdDpType entries in the config.redu file.

Best Regards
Leopold Knipp
Senior Support Specialist

[NikolayLevchenko]

Thank you, Leopold!