PC Time not showing in fault logger screen of Drive Window.
Following massage is coming in fault logger screen
Active warning START INHIBIT (FF7A) at 3391:29:57.0590
How to know actual PC timing of this fault/warning.
Active warning START INHIBIT (FF7A) at 3391:29:57.0590
How to know actual PC timing of this fault/warning.
Asked 1 year ago
Answers
0
Hi,
PC Time, which is real time stamp calculated by DriveWindow from the system time stamp,
DriveWindow is not always able to show the PC Time. It cannot be shown and the field is empty if any of the following is true: • The drive has a real time clock and it is used for stamping faults or events. In this case Drive Time contains the time stamp as calendar time. • A fault or event was happened before the last power-up of the drive. • The time stamps are not directly based on system time counter of the drive. • The system time counter is not available in the drive.
DriveWindow calculates the PC Time from the time stamp by using the system time counter of the drive and the computer clock as references. To increase accuracy, DriveWindow “measures” the frequency of the system time counter of the drive. The measurement takes some time (about 40 seconds), which means that the PC Times are not available within that measurement time when DriveWindow is connected to the OPC Server. Although the PC Time is shown with great resolution, its accuracy depends on, how long time has passed since the fault or event happened, and whether you were viewing the corresponding item set when it happened or not. If the item set containing the fault or event was visible and on-line at the time the fault or event happened, the error in PC Time is typically less than 0.03 ms. Otherwise the error is typically less than 200 ms for each hour passed before DriveWindow detects the fault or event. Because the crystals on drive control boards are usually much more stable than the crystal of your PC, the PC Time differences of faults or events in different drives do not change so much in time as the PC Time error does. So, it is usually possible to determine the order of faults or events in different drives even if some time has passed. Note that the faults and events are handled on some time level in the drive, which means that the time stamp accuracy is actually the cycle time of the handler.
PC Time, which is real time stamp calculated by DriveWindow from the system time stamp,
DriveWindow is not always able to show the PC Time. It cannot be shown and the field is empty if any of the following is true: • The drive has a real time clock and it is used for stamping faults or events. In this case Drive Time contains the time stamp as calendar time. • A fault or event was happened before the last power-up of the drive. • The time stamps are not directly based on system time counter of the drive. • The system time counter is not available in the drive.
DriveWindow calculates the PC Time from the time stamp by using the system time counter of the drive and the computer clock as references. To increase accuracy, DriveWindow “measures” the frequency of the system time counter of the drive. The measurement takes some time (about 40 seconds), which means that the PC Times are not available within that measurement time when DriveWindow is connected to the OPC Server. Although the PC Time is shown with great resolution, its accuracy depends on, how long time has passed since the fault or event happened, and whether you were viewing the corresponding item set when it happened or not. If the item set containing the fault or event was visible and on-line at the time the fault or event happened, the error in PC Time is typically less than 0.03 ms. Otherwise the error is typically less than 200 ms for each hour passed before DriveWindow detects the fault or event. Because the crystals on drive control boards are usually much more stable than the crystal of your PC, the PC Time differences of faults or events in different drives do not change so much in time as the PC Time error does. So, it is usually possible to determine the order of faults or events in different drives even if some time has passed. Note that the faults and events are handled on some time level in the drive, which means that the time stamp accuracy is actually the cycle time of the handler.
Add new comment