IM Log Double record
Hello,
I have a IM Log who is configured with a sample time and storage time to 1 minute, looking at the log data we saw double records every minute.
What could be the reason?
This is a 5.1 FP4 RevA
I have a IM Log who is configured with a sample time and storage time to 1 minute, looking at the log data we saw double records every minute.
What could be the reason?
This is a 5.1 FP4 RevA
Asked 9 months ago
Voted best answer
4
I see two issues:
Example 1:
BH MinTime=10sec:MaxTime=15sec/1day --> BH MinTime=1min:MaxTime=NO/1week TimeAverage --> IM SampleInterval=1min/5years StoreAsIs
Example 2:
BH MinTime=10sec:MaxTime=15sec/1day --> IM SampleInterval=1min/5years TimeAverage
- Basic History primary log has Min Time = Max Time
This is NOT recommended since extrapolation will take place exactly at Max Time. If the source OPC server is just one microsecond late with the next sample, there will be two samples recorded by Basic History, very close to each other. First, the extrapolated value (on exact Max Time intervval since last received value) then secondly a new raw value (with slight delay).
Always set Max Time > Min Time, preferably with some margin. - IM log has "Store As Is"
As others have explained, that is a "copy source log content" setting - the storage setting in the IM template is not in effect.
IM logs may wrap prematurely keeping this configuration.
Example 1:
BH MinTime=10sec:MaxTime=15sec/1day --> BH MinTime=1min:MaxTime=NO/1week TimeAverage --> IM SampleInterval=1min/5years StoreAsIs
Example 2:
BH MinTime=10sec:MaxTime=15sec/1day --> IM SampleInterval=1min/5years TimeAverage
Answers
0
I believe this is due to time synchronization problem between nodes. Request you to confirm time sync. Refer attached manual, section 7 for more information.
Answered 9 months ago
1
Hi,
Since your calculation algorithm is "Storage As Is", IM Log Data Collection/sampling is bypassed and system is using your "Log1m_4w" (OPC log) data collection configuration.
Share your "Log1m_4w" Data Collection and other tabs of log configuration.
Since your calculation algorithm is "Storage As Is", IM Log Data Collection/sampling is bypassed and system is using your "Log1m_4w" (OPC log) data collection configuration.
Share your "Log1m_4w" Data Collection and other tabs of log configuration.
0
Answered 9 months ago
0
Here are other IM Log configuration tabs.
Answered 9 months ago
0
Hi,
I think you see both direct and hierarchical values each minute. You should define a different sample times for direct and hierarchical logs.
There is no sense to set the same sampling for direct and hierarchical logs.
Try to set 10 min sampling time for hierarchical log.
I think you see both direct and hierarchical values each minute. You should define a different sample times for direct and hierarchical logs.
There is no sense to set the same sampling for direct and hierarchical logs.
Try to set 10 min sampling time for hierarchical log.
0
Hi,
Looking at the screenshot below, Only once it has happened that values get changed but logged with same time stamp.
I think rest of the time values get changed and logged with different time stamp (with a difference of one or two seconds)
Just check direct logs "Log1m_4w" are getting stamped/logged in same pattern.
Looking at the screenshot below, Only once it has happened that values get changed but logged with same time stamp.
I think rest of the time values get changed and logged with different time stamp (with a difference of one or two seconds)
Just check direct logs "Log1m_4w" are getting stamped/logged in same pattern.
Add new comment