Skip to main content

CODESYS Safe Time Provider for Linux

CODESYS logo

The independent clock that CODESYS Virtual Safe Control SL is paired with.

Category: CODESYS

The Safe Time Provider is a small sender. It streams time-sync telegrams to a Safe Control over UDP so the safety PLC has a second time base to check against. EmberNet packages version 4.21.0.0 as its own chart.

What it does​

  • Sends time-sync telegrams to a CODESYS Virtual Safe Control SL on 60000/udp.
  • Runs a cyclic send loop every 3 ms by default.
  • Has no web interface and listens on nothing of its own, so its card offers nothing to open.

When to use it​

Deploy it whenever you run CODESYS Virtual Safe Control SL, which needs it as its independent time base.

Running on EmberNet​

  • You choose the target. When you install it, the App Store lists the Safe Control releases it can reach and defaults to one on a different node.
  • Production means another node. The CODESYS manual says the time provider must not run on the same host as the Safe Control it serves, because one host is one clock. Same host is a commissioning and test setup. The chart's install notes and the pod's log both say which layout you got when the provider is pinned to a node.
  • It checks its target. It resolves the Safe Control once at start and exits with a message if it is not there. A health check looks again every 30 seconds, so a removed or reinstalled Safe Control restarts the provider instead of leaving it sending to a stale address.
  • Same namespace. The Safe Control it targets must be in the same tenant namespace as the provider.
  • amd64 only. Safe Control is an i386 product, and the time provider ships for amd64.
  • Privileged by default. The send loop sets a real-time scheduling priority, and the chart runs privileged to grant it.
  • Sized small by default. It requests 100m of CPU and 64 MiB of memory.
  • Stops by force. The sender does not shut down cleanly on a stop request, so expect it to be killed after the grace period. It keeps no state, so nothing is lost.

To check that it is sending, read its log and look for "Started sending" with no permission error above it.

Learn more​

EmberNet packages and deploys this application; it is developed by CODESYS Group. Product names and logos are trademarks of their respective owners.