Issue
A utility is being used to record Sigma log data and store it in the cloud. There is a requirement for log timestamps to occur every 15 minutes, precisely synchronized to the hour (e.g., 00:00, 00:15, 00:30, 00:45).
Product Line
Satchwell BAS & SigmaEnvironment
Satchwell Sigma
Cause
Sigma does not provide a native mechanism to define the exact start time for a log set. When configured to log at timed intervals, the log bucket file is downloaded to the controller and begins processing from that moment—resulting in unsynchronized timestamps.
Resolution
An engineering workaround can be implemented to achieve synchronized 15-minute logging. This involves using a program point for each value that needs to be logged.
Sample Program Code
10 XFlo = POINT 0|41 ; Object to be logged
20 IF MINUTE = 0 OR MINUTE = 15 OR MINUTE = 30 OR MINUTE = 45 THEN GOTO 40
30 RETURN VIA TEXT 92 VALUE YFlo
40 IF SECOND DOWN THEN GOTO 60
50 RETURN VIA TEXT 92 VALUE YFlo
60 YFlo = XFlo
70 RETURN VIA TEXT 92 VALUE YFlo
Instructions
- Replace
POINT 0|41with the actual object reference you wish to log. - Configure the log set to use "Change of Value" as the logging trigger.
- Ensure each required value has its own program point using the logic above.
Additional Notes
- This method ensures that values are captured exactly at 15-minute intervals aligned with the hour.
- It is particularly useful when integrating with external systems or cloud-based analytics that rely on consistent timestamping.