Hello!
There are signals of type M_ME_TF_1 <36> on PLC which change quite rare. We send C_IC_NA_1<100> on this PLC each hour and get those signals with type of M_ME_NC_1 <13>, but the Event ignores them, so the signal timestamp also changes very rare.
How can we configure IEC-driver so Event could assign its Timestamp with every interrogation command?
In WCCOA Doc i found the entry redOldNewComp. Will it help with my task?
Thanks in advance!
Server timestamp assign IEC104
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Server timestamp assign IEC104
The config entry redOldNewComp is only used in redundant systems.
Do you have redundant system?
Which WinCC OA version is used?
Best Regards
Leopold Knipp
Senior Support Specialist
Do you have redundant system?
Which WinCC OA version is used?
Best Regards
Leopold Knipp
Senior Support Specialist
- DmSilkin
- Posts:23
- Joined: Wed Jun 03, 2020 9:26 am
Re: Server timestamp assign IEC104
I have the redundant system and 3.15 p027.
We tried to change the type of signals that come with interrogation command, so now the signal type after C_IC_NA_1<100> is also M_ME_TF_1 <36>.
But the result is the same: we dont get new timestamp If PLC has the the same value as before (however, in wireshark we can see the old value with new timestamp after interrogation).
We tried to change the type of signals that come with interrogation command, so now the signal type after C_IC_NA_1<100> is also M_ME_TF_1 <36>.
But the result is the same: we dont get new timestamp If PLC has the the same value as before (however, in wireshark we can see the old value with new timestamp after interrogation).
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Server timestamp assign IEC104
The config entry redOldNewComp only takes effect on values which are received during a general query GQ. If the same value is received during a GQ it will be smoothed by the Event Manager.
Do you have a _smooth config defined at the DP element or an old/now comparison at the _address config?
Why do you want to get the same value again?
What does interrogation command in that case?
Best Regards
Leopold Knipp
Senior Support Specialist
Do you have a _smooth config defined at the DP element or an old/now comparison at the _address config?
Why do you want to get the same value again?
What does interrogation command in that case?
Best Regards
Leopold Knipp
Senior Support Specialist
- DmSilkin
- Posts:23
- Joined: Wed Jun 03, 2020 9:26 am
Re: Server timestamp assign IEC104
Tried to attach the pics to the forum, but it didnt work.. I'll try to explain it in words.
I don have _smooth or comparison (does iec address have this ability?) on these parameters.
I dont need the same value, i need the new timestamp of this old value
For example, I manually assign the signal value to 10. Its timestamp 12-00-00. All information bits, except D are "0". Then i send GQ = 20 and get the value 15 which is contained in PLC. New timestamp is 12-01-00. The information bit G is now also "1". BUT if i send GQ = 20 again, the value timestamp wouldnt change and bit G is still "1".
So, I'd like to get new timestamps regardless to its same values. Is it possible?
I don have _smooth or comparison (does iec address have this ability?) on these parameters.
I dont need the same value, i need the new timestamp of this old value
For example, I manually assign the signal value to 10. Its timestamp 12-00-00. All information bits, except D are "0". Then i send GQ = 20 and get the value 15 which is contained in PLC. New timestamp is 12-01-00. The information bit G is now also "1". BUT if i send GQ = 20 again, the value timestamp wouldnt change and bit G is still "1".
So, I'd like to get new timestamps regardless to its same values. Is it possible?
- gschijndel
- Posts:376
- Joined: Tue Jan 15, 2019 3:12 pm
Re: Server timestamp assign IEC104
The smoothing can be disabled for the general query by setting the '_Driver<num>.SM' to 1 (always smooth except for the general query).
The other values can be found in the documentation under: Reference tables -> Internal data point types -> _DriverCommon (General driver)
The other values can be found in the documentation under: Reference tables -> Internal data point types -> _DriverCommon (General driver)
- DmSilkin
- Posts:23
- Joined: Wed Jun 03, 2020 9:26 am
Re: Server timestamp assign IEC104
Thanks!
In my case it works fine on my test project with iec-104 emulation. But on the actual project which has the same config with a larger amount of drivers, it works still by the old way regardless to change of _Driver<num>.SM..As i mentioned above, wireshark logs show that i get new values after interrogation command.
Can the big amount (emulator doesnt provide the real PLC load) of data from drivers be the reason of this problem?
In my case it works fine on my test project with iec-104 emulation. But on the actual project which has the same config with a larger amount of drivers, it works still by the old way regardless to change of _Driver<num>.SM..As i mentioned above, wireshark logs show that i get new values after interrogation command.
Can the big amount (emulator doesnt provide the real PLC load) of data from drivers be the reason of this problem?
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Server timestamp assign IEC104
No, the amount of data normally has no effect on the behaviour of the driver and how data is smoothed.
The wireshark logs only show which data is received from the PLC, they do not give information for the tasks running in the driver and which data is then send to the Event Manager.
In a redundant system you have to ensure that also the driver datapoints ending with "_2" have the correct settings. Otherwise the behaviour of the system differs based on the active/passive state of the servers.
With the debug flag "-snd 2" for the driver you can check if data is send from the driver to the Event Manager.
Best Regards
Leopold Knipp
Senior Support Specialist
The wireshark logs only show which data is received from the PLC, they do not give information for the tasks running in the driver and which data is then send to the Event Manager.
In a redundant system you have to ensure that also the driver datapoints ending with "_2" have the correct settings. Otherwise the behaviour of the system differs based on the active/passive state of the servers.
With the debug flag "-snd 2" for the driver you can check if data is send from the driver to the Event Manager.
Best Regards
Leopold Knipp
Senior Support Specialist