![background image](http://html.mh-extra.com/html/sick/lms511-se/lms511-se_operating-instructions-manual_1264310042.webp)
3
SYSTEM DESCRIPTION
42
8017768/12AX/2019-05-31|SICK
O P E R A T I N G I N S T R U C T I O N S | TIC
Subject to change without notice
3.5
System interfaces
Communication between the system components and the downstream components takes
place via TCP/IP interfaces. The interfaces can, for example, be utilized by a traffic
checkpoint or system operator.
Fig. 35: Interfaces of the profiling system
All the sensors are connected to the Traffic Controller via an Ethernet interface. The
TEMS Recorder with profiling functionality comes pre-installed on the Traffic Controller.
The recipients of the data output via the TCP/IP interface are:
•
The web-based
TEMS Manager
allows you to check that the profiling system is
operating correctly from any computer that is connected to the Traffic Controller.
It also provides a detailed view of the measurement results. TEMS Manager is used
by operators and service technicians.
Provided that you have the relevant access authorization, you can also use
TEMS
Manager
to configure and monitor the system. As an alternative to TEMS Manager, you
can also use
TEMS Manager Command Line
if you wish to configure the system using
command lines.
•
TEMS Info interface
. This receives measurement results as messages. The interface
distinguishes between messages containing vehicle information and messages
containing data on the positioning of the vehicle in the lane. The TEMS Info interface
also delivers all system status messages.
Integrators
can use the TEMS Info interface to integrate the system into third-party
systems (traffic routing system, alert systems, etc.).
•
FTP interface
. This can be used to download vehicle data stored in the Traffic
Controller and the TEMS Recorder log files. Alternatively, vehicle data can also be
uploaded automatically to a customer FTP server (see chapter
and downloading the vehicle data
and