Your SICK ID gives you access to our extensive range of services. This includes direct online orders, price and availability checks, and access to our digital services.
Synchronizing the internal time of two or more scanners via Ethernet. As a time client (SNTP) the LMS5xx device is capable of synchronizing with NTP servers. As a time server the LMS5xx device is capable of being used for time synchronization by other LMS5xx devices. Each LMS5xx device can only act as either time server or time client. The parameterization is done via the device page Parameter -> System.
It works for PRO devices, only.
Time Client
If the device is parameterized as time client (and of course Ethernet as interface) the following settings should be recognized:
TC/IP Port
The standard TCP/P Port, which is used for NTP time is Port 123
Time Server IP-Address
IP address of the server being used for time synchronization.
Update Time
Interval in seconds for updating the time from the server.
Time Zone
As NTP uses UTC timestamps the time zone can be used to adapt the system time to the specified time zone.
Max. Offset and Delay
These values are read only and can be used for accuracy estimations of the synchronization. Max. Offset shows the highest offset by which the system time had to be corrected since the last reset (of the max. Offset). Delay shows the corresponding (to the max. Offset) delay value which indicates the transport time of the NTP packet. For further explanations on NTP offset and delay please refer to the NTP documentation. Attention: When considering accuracy of the synchronization, be aware that there can always be an additional inaccuracy of up to +/-2ms caused by the system time resolution which is 1ms. (Taking two timestamps, as necessary with NTP, with a resolution of 1ms can (in worst case) lead to an error of ~+/-2ms.)
Time Server
If the device is parameterized as time server, the following points should be considered. Only use the LMS5xx device as time server for other LMS5xx devices, since the time server functionality of the LMS5xx device is not a NTP server implementation (although it uses a similar packet structure). Be aware of additional inaccuracies in time synchronization, if using the LMS5xx device as time server. This is caused by its system time resolution of 1ms (see also description of time client above) which occurs in this case on client as well as on server side.
To start the time server in windows on your own PC, open a console window and use the command:
w32tm.exe
Field evaluation logging
If the NTP Server runs and the LMS is programmed like above described, the "right time" will also be shown in the Field evaluation logging.
Firmware Version
SNTP is available from following firmware versions on: LMS5xx: V1.30 LMS531: V31.39 (deprecated, LMS531 FW has been merged to standard LMS5xx FW), V2.10 LMS1xx: V1.59 LMS12x: V1.20
NTP Server IP of SICK NTP Server - Germany
IP = 10.2.32.101
Works in Waldkirch and Reute, other locations not sure For use of the Sick internal NTP Server in the Sick Network, also the Subnet Mask of the device itself must fit, so take an open one: SubnetMask = 255.0.0.0
Known Problems
If the time is not actualized in the scanner, in the most cases, the problem is on the PC side if the PC is the time server. Often some ports are blocked by the IT or the secure client blocks that function. One solution is to deactivate the secure client, maybe for tests, deactivate the firewall. Other possibilities to get it run are: Many PLC's with Ethernet supports auto adjustment of the clock by using SNTP. This requires a computer with a running NTP Server. In Windows 7, the NTP Server uses a "Authoritative Time Server", which requires authentication. The NTP server needs to be enabled without using "Authoritative Time Server" in order to work without authentication. Follow these steps to properly setup the server:
Open a command prompt as Administrator.
Run the command "regedit"
Change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags to "5"
Change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer\Enabled to "1"
Change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider\Enabled to "0"
Close regedit.
Run the command "net stop w32time"
Run the command "net start w32time"
Close the command prompt.
Problem Winter Time / Summer Time
The devices are getting from the Time Server the UTC Time only. The Time Zone itself is done in the device. UTC: (http://www.meinbergglobal.com/english/glossary/utc.htm) german: UTC (Coordinated Universal Time) ist die Bezeichnung des internationalen Zeitstandards und wurde früher als GMT (Greenwich Mean Time) bezeichnet, weil sie sich auf dem Nullmeridian in Greenwich (Großbritannien) bezieht. Die UTC-Zeit wird im 24-Stunden-Format angegeben und kennt keine Sommerzeit/Winterzeit-Umschaltung. Die deutsche Standardzeit ist die Mitteleuropäische Zeit (MEZ, oder auch CET für "Central European Time"), die der UTC einer Stunde voraus ist. Die Koordination der UTC ist Aufgabe des Internationalen Büros für Gewichte und Maße (BIPM). Diese sorgt mit dafür, dass die UTC weltweit überall gleich ist.
english: UTC (Coordinated Universal Time) is the name of the international time standard and is identical to GMT (Greenwich Mean Time), which was commonly used as a world wide time base. GMT and therefore UTC are both referring to the zero longitudinal meridian, which runs through Greenwich in England. UTC is based on a 24 hour time scale, therefore 03:00 o'clock P.M. equals to 15:00 UTC. No daylight savings time is used for UTC; there are no switchovers from DST to non-DST periods in this universal time zone. The German standard time is called central European time (CET), which is one hour ahead of the UTC. The coordination of the UTC is being managed by the BIPM which also maintains the accordance of the global UTC. Handling in SICK devices: Some devices have the possibility to switch between summer and wintertime "automatically", and some not. Example LMS1xx/5xx: No possibility to switch wintertime / summertime automatically. It has to be done "manually" (e.g. GMT +1 or GMT +2 for Central Europe)
Example MSC 800: with the possibility to switch wintertime / summertime.
The switching date / time has to be written in the device once manually.
Problem with Network setting sNTP with MS5xx:
A Ping is send from the SICK device to the NTP server before starting the communication. Some Networks block this Ping send request. So the NTP time never start.
LMS5xx: From FW 2.10 we delete this behavior. A Ping is not needed.
