• Replies 4 replies
  • Subscribers 583 subscribers
  • Views 282 views
  • Users 0 members are here
Options
Related

Adding Operator Inputs to SOE Page

Justin

Hi all,

I'm using a SOE template page and trying to get it to display any operator inputs on the HMI (setpoint/CO changes, pumps on/off, valves open/closed, modbus devices enabled/disabled, etc).

For all of these devices (PID control, pumps, valves, modbus devices) we are using genies that have pop-up pages. The buttons that allow new tuning values or on/off functionality are in these pop-ups. I've gone to the Input tab on the buttons in the pop-up pages and tried to enter:

SOEEventAdd(TimestampCurrent(),"Modbus Device Enabled",?TagName?)

TagName is what I named the %TAGNAME% value in the metadata of the genies to be passed to the pop-up pages. I'm also using Desc and Desc2 for the device names. ?Desc? and ?Desc2? work elsewhere in the pop-ups to get the Device ID to display (ex: Pump 1), but seem to do nothing to pass that information along to the SOE page, either.

The above function does cause the message (Modbus Device Enabled) and timestamp to appear on the SOE page (titled User Events Page), as well as the User who did it. I can't, however, figure out how to get the device name/tag name to appear. Does anyone know how to make this work?

Kind Regards,

Justin Lane

Parents
  • Hi Justin,

    the SOEEventAdd, can only add events to Alarm tags.
    So if you use ?TagName? the event will be added to the matching Alarm Tag. If this tag does not exists then the function will fail (returns 537).

    Typically it is easiest to define a "Dummy" alarm tag per equipment which could be part of a operator events separate category and add the operator events to that. This will allow for easy filtering as well.
    Combined with changing the sMessage you pass in to e.g "Modbus Device Enabled - " +?Desc? should get you the desired functionality..
Reply
  • Hi Justin,

    the SOEEventAdd, can only add events to Alarm tags.
    So if you use ?TagName? the event will be added to the matching Alarm Tag. If this tag does not exists then the function will fail (returns 537).

    Typically it is easiest to define a "Dummy" alarm tag per equipment which could be part of a operator events separate category and add the operator events to that. This will allow for easy filtering as well.
    Combined with changing the sMessage you pass in to e.g "Modbus Device Enabled - " +?Desc? should get you the desired functionality..
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.