Good day!
I set the status64 for a correction value via CONTROL as shown in help Wincc OA, but as an archive I use RDB.
The first time the recording is correct. And I see my status64 in RDB. But if I repeat the recording to the same timestamp then status64 is reset and in RDB i see 4097.
Is there a solution to this problem?
if I use the internal database then all is well.
WINCC OA ver. 3.16 patch 12.
_corr for status64 in RDB
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: _corr for status64 in RDB
The status word 4097 (as int) refers to the information that status bit 12 (value was corrected) is set. If you only write a correction value without defining also the status word only the status bit _corr" will be set.
Possibly the RDB manager does not support to write the _status64 bit word in combination with a correction value.
What is meant that it works for the first time?
Do you set a correction value for a timestamp where no original value is written?
Do you want to write a correction value for a timestamp which is older than the current timestamp of the original value?
Best Regards
Leopold Knipp
Senior Support Specialist
Possibly the RDB manager does not support to write the _status64 bit word in combination with a correction value.
What is meant that it works for the first time?
Do you set a correction value for a timestamp where no original value is written?
Do you want to write a correction value for a timestamp which is older than the current timestamp of the original value?
Best Regards
Leopold Knipp
Senior Support Specialist
- Holden27
- Posts:7
- Joined: Thu Sep 06, 2018 9:45 am
Re: _corr for status64 in RDB
--------- What is meant that it works for the first time?
For example, I record in _corr.._status64 - 0000000000000000000000001000000000001111000000000000000000000001 in TimeStamp 2019.09.02 12:00:00.000.
I see the following entry in the RDB database - 0000000000000000000000001000000000001111000000000001000000000001.
This is correct!
Next i'm re-doing the exact same recording in _corr.._status64 - 0000000000000000000000001000000000001111000000000000000000000001 in TimeStamp 2019.09.02 12:00:00.000.
But now i see the following entry in the RDB database 0000000000000000000000000000000000000000000000000001000000000001
I see that now my user bits are gone!
--------Do you set a correction value for a timestamp where no original value is written?
Yes.
dpSetTimed(TimeStamp , str+":_corr.._value", true, str+":_corr.._status64", qual);
-------Do you want to write a correction value for a timestamp which is older than the current timestamp of the original value?
Yes.
For example, I record in _corr.._status64 - 0000000000000000000000001000000000001111000000000000000000000001 in TimeStamp 2019.09.02 12:00:00.000.
I see the following entry in the RDB database - 0000000000000000000000001000000000001111000000000001000000000001.
This is correct!
Next i'm re-doing the exact same recording in _corr.._status64 - 0000000000000000000000001000000000001111000000000000000000000001 in TimeStamp 2019.09.02 12:00:00.000.
But now i see the following entry in the RDB database 0000000000000000000000000000000000000000000000000001000000000001
I see that now my user bits are gone!
--------Do you set a correction value for a timestamp where no original value is written?
Yes.
dpSetTimed(TimeStamp , str+":_corr.._value", true, str+":_corr.._status64", qual);
-------Do you want to write a correction value for a timestamp which is older than the current timestamp of the original value?
Yes.
- Holden27
- Posts:7
- Joined: Thu Sep 06, 2018 9:45 am
Re: _corr for status64 in RDB
This problem is observed with the database ORACLE.
If I use internal database WinCC OA then there is no such problem.
If I use internal database WinCC OA then there is no such problem.