search

ni / niveristand-synchronization-custom-device

Enables timing and synchronization using NI hardware in VeriStand
MIT License
2 stars 6 forks source link

When changing or initially setting the timekeeper, system time is not synchronized to timekeeper time on PharLap until the system is rebooted #10

Closed rtzoeller closed 2 years ago

rtzoeller commented 5 years ago

When the timekeeper is changed in the system definition for PharLap targets, the change does not take effect upon deployment. Rebooting the target after the deployment will result in the correct synchronization occurring for future deployments (unless the timekeeper is changed again).

The timekeeper used by NI-TimeSync to drive the system time is read from a configuration file upon boot. The configuration file is updated to reflect the requested timekeeper upon deployment, but until the system is rebooted the previously configured timekeeper will be used.

This behavior is not described in the custom device.

Karl-G1 commented 2 years ago

Pharlap support was dropped in #49. Closing this issue since we will not have Pharlap support in releases 21.0 and later.