Hi,
WinCC OA version: 3.15 64bit
Patches: none
operating system: Windows7 64bit
system configuration: redundant system
In my current project, supervisor users should be able to adjust limiting values of some analogue inputs. To avoid giving "para" access rights to manipulate this limits, I was thinking to create a specific panel for this purpose, where supervisors could deactivate the alarm (_alert_hdl.._active), make the necessary limits adjustment and the reactivate the alarm.
Can you help me to understand where are these limiting values kept in the database? And if it's possible to dpset their value?
Thank you
Nuno
Operator defined limiting values
Search
Re: Operator defined limiting values
The settings for an _alert_hdl config can be changed using dpSet().
A list of attributes for the _alert_hdl config you can find in the WinCC OA Documentation: Reference tables --> Data point configs --> _alert_hdl.
When changing the limits for the thresholds you have to keep in mind that the values for the attributes _l_limit and _u_limit for both ranges need to be changed using the detail numbers (_config.detail._attribute).
With an ASCII export for a _alert_hdl config you can see which attributes are configured.
In case of master datapoints and power configs please keep in mind that the changeable attributes are defined at the power conifg. If other attributes are changed by your own functionality it may cause an undefined configuration which does not fit the predefined settings.
Note: With the _auth config you can define which user permission is required to be able to modify a config and its attributes. Maybe you can use this config to limit the access to the supervisor.
Best Regards
Leopold Knipp
Senior Support Specialist
A list of attributes for the _alert_hdl config you can find in the WinCC OA Documentation: Reference tables --> Data point configs --> _alert_hdl.
When changing the limits for the thresholds you have to keep in mind that the values for the attributes _l_limit and _u_limit for both ranges need to be changed using the detail numbers (_config.detail._attribute).
With an ASCII export for a _alert_hdl config you can see which attributes are configured.
In case of master datapoints and power configs please keep in mind that the changeable attributes are defined at the power conifg. If other attributes are changed by your own functionality it may cause an undefined configuration which does not fit the predefined settings.
Note: With the _auth config you can define which user permission is required to be able to modify a config and its attributes. Maybe you can use this config to limit the access to the supervisor.
Best Regards
Leopold Knipp
Senior Support Specialist