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.

Close
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
84247members
353346posts

Dummy value in analog point alarm limit field when using time profiles

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.

Solved
rlao
Lieutenant
Lieutenant
0 Likes
1
587

Dummy value in analog point alarm limit field when using time profiles

Hi all,

 

When I attach a time profile to an alarm limit on an analog point, it replaces the property field with some 'overflow' dummy value.

 

Capture.PNG

 

 

However, the alarm limit does follow whatever the current value is in the profile even though you don't see that reflected in the Low1LimitStd field.

 

Is there any particular reason why the Low1LimitStd field can't update to be what the profile value is, or at the very least keep whatever the old hardcoded value was? Main issue is if you un-attach the alarm profile, the alarm limit stays as the dummy value which can cause a flood of false alarms if you don't change it back before saving (happened to a colleague of mine).


Accepted Solutions
AndrewScott
Commander
Commander
0 Likes
0
577

Re: Dummy value in analog point alarm limit field when using time profiles

The special value (either FLT_MAX or DBL_MAX) assigned to a limit associated with a time profile is there to 'hide' the limit from current trends and indicate that the limit doesn't have a fixed value.

 

Updating Low1LimitStd etc. with the current value of the time profile would affect current trends by incorrectly showing the limit as a straight line (fixed limit). Also, the constant re-configuring of the points with the new values of the time profiles would not be scalable.


Andrew Scott, Lead Engineer, AVEVA

See Answer In Context

1 Reply 1
AndrewScott
Commander
Commander
0 Likes
0
578

Re: Dummy value in analog point alarm limit field when using time profiles

The special value (either FLT_MAX or DBL_MAX) assigned to a limit associated with a time profile is there to 'hide' the limit from current trends and indicate that the limit doesn't have a fixed value.

 

Updating Low1LimitStd etc. with the current value of the time profile would affect current trends by incorrectly showing the limit as a straight line (fixed limit). Also, the constant re-configuring of the points with the new values of the time profiles would not be scalable.


Andrew Scott, Lead Engineer, AVEVA