SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

PCS 7: Some SOE alarms are logged in different time stamp

3/3/2025 10:09 AM	Rate (0)
AutoGen_9129387 Joined: 3/3/2025 Last visit: 3/3/2025 Posts: 1 Rating: (0)	Hi all, Even i face the similar problem, some of the SOE alarms are logged in a different time stamp(eg. 29/10/1984) and some of the analog danger alarms are logged in lag of two three minutes from the actual computer time. Please advice to solve this issue and in the SOE block i found the time stamp bit is 1. 0-CPU time stamp 1-IO module time stamp Thanks in advance ------------------------------------------------------------------------------------------ Split from PCS7 Time Stamp Alarm Problem.
	Last edited by: Moderator_Lan at: 03/03/2025 11:17:00 New subject after splitting
Suggestion To thank Quote Answer

3/11/2025 6:59 AM	Rate (0)
Techno_Taru Bronze-Expert Joined: 1/11/2019 Last visit: 8/14/2025 Posts: 899 Rating: (171)	Hello, If SOE alarms are showing wrong time stamps (like 29/10/1984) or delays of 2-3 minutes, here’s is the possible solutions to over come the issue Check Time Sync Settings If the SOE block is using the IO module time (`bit = 1`), the IO module’s clock might be wrong. Switch the SOE block to use the CPU time (`bit = 0`) if IO time sync is unreliable. Enable CPU Time Sync Make sure the CPU is syncing with an NTP server or network time source. Open CPU properties → Enable clock sync. Check Time Zones Ensure that the CPU, IO module, and operator station are set to the same time zone. Reduce Network Delay A 2–3 minute delay can be caused by network issues. Check network load and communication settings. Use CPU Time Stamp if Issues Persist If IO module sync keeps failing, set the SOE block to use the CPU time. And some forum links: Alarms and events have incorrect timestamp Sequence of Event Recording (SER / SOE)

Suggestion To thank Quote Answer