Hi,
I just observed with WinCCOA 3.16 on linux, that the OriginTime (DpHLGroup::getOriginTime(), C++ API, described as time when value change occured) of DpQueryConnect hotlinks is not set. Is this intended behaviour? In alertConnect and dpConnect hotlinks this value holds the time of the value change.
BR,
Giri
OriginTime of QueryConnect hotlink not set
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: OriginTime of QueryConnect hotlink not set
Where in the API did you find this information?
In a query result (in CTRL) you do not get the information for the _stime if the item is not added to the list of queried attributes.
Possibly it is the same in API.
In case of a connect to _alert_hdl attributes you have to be aware that the time information is the time when the alert was changed and this must not be the time when the values was set in some cases.
Best Regards
Leopold Knipp
Senior Support Specialist
In a query result (in CTRL) you do not get the information for the _stime if the item is not added to the list of queried attributes.
Possibly it is the same in API.
In case of a connect to _alert_hdl attributes you have to be aware that the time information is the time when the alert was changed and this must not be the time when the values was set in some cases.
Best Regards
Leopold Knipp
Senior Support Specialist
- dgi
- Posts:11
- Joined: Wed May 09, 2018 4:28 pm
Re: OriginTime of QueryConnect hotlink not set
Within the C++ API documentation (see attached screenshot).leoknipp wrote: ↑ Mon May 17, 2021 9:57 am Where in the API did you find this information?
Yes I know, but I am talking about HotLinkCallbacks, these are the messages which are received when DpConnect/QueryConnect(Single/All) callbacks are triggered and encapsulated by objects of the type DpHLGroup. This type features the getOriginTime() function (inherited by DpVCGroup), which is described to return the TimeVar of the value change. For DpConnect this is true, but for DpQueryConnect(Single/All) this time is not set, which does not make sense to me.leoknipp wrote: ↑ Mon May 17, 2021 9:57 am In a query result (in CTRL) you do not get the information for the _stime if the item is not added to the list of queried attributes.
Possibly it is the same in API.
In case of a connect to _alert_hdl attributes you have to be aware that the time information is the time when the alert was changed and this must not be the time when the values was set in some cases.
BR,
Giri
Last edited by dgi on Tue May 18, 2021 7:20 pm, edited 1 time in total.
- dgi
- Posts:11
- Joined: Wed May 09, 2018 4:28 pm
Re: OriginTime of QueryConnect hotlink not set
I am not able to attach screenshots... ("Sorry, the board attachment quota has been reached.")
Opening this uri with any webbrowser on a Windows System with WinCCOA installed should open up the documentation I am refering to:
file:///C:/Siemens/Automation/WinCC_OA/3.16/api/docu/class_dp_v_c_group.html
Opening this uri with any webbrowser on a Windows System with WinCCOA installed should open up the documentation I am refering to:
file:///C:/Siemens/Automation/WinCC_OA/3.16/api/docu/class_dp_v_c_group.html