APH RTLS-Netzwerkkonfiguration-V2.13.0.0 76

SIMATIC RTLS Network Configuration
Introduction 1
Security recommendations 2
3
SIMATIC RTLS Overview
Functions in the menu bar 4

Locating systems
SIMATIC RTLS Network Symbols in the tree
Configuration topology of the
Locating Manager and the 5
clients
Application Manual
Configuration 6
01/2022
C79000-G8976-C531-06
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG C79000-G8976-C531-06 Copyright © Siemens AG 2022.

Digital Industries Ⓟ 01/2022 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Introduction ........................................................................................................................................... 5
2 Security recommendations .................................................................................................................... 9
3 Overview.............................................................................................................................................. 13
4 Functions in the menu bar................................................................................................................... 15
5 Symbols in the tree topology of the Locating Manager and the clients ............................................. 17
6 Configuration....................................................................................................................................... 19
6.1 Overview of the configuration............................................................................................ 19
6.2 Gateways, anchors and transponders ................................................................................. 20
6.2.1 Adding a gateway, anchor and transponder manually ........................................................ 20
6.2.2 Gateway, anchor and transponder groups .......................................................................... 20
6.2.3 Firmware update for device classes .................................................................................... 22
6.2.4 Tolerance of the heartbeats ............................................................................................... 22
6.3 Device configurations ........................................................................................................ 22
6.3.1 System information ........................................................................................................... 23
6.3.2 Internal and external voltage ............................................................................................. 23
6.3.3 Last heartbeat.................................................................................................................... 24
6.3.4 Ping ................................................................................................................................... 24
6.3.5 Using a device in the network / enabling localization .......................................................... 24
6.3.6 System information and firmware update of individual devices........................................... 25
6.3.7 Spatial position of the infrastructure devices ...................................................................... 25
6.3.8 IP configuration of the gateways ........................................................................................ 25
6.3.9 Values on node (gateways) ................................................................................................ 26
6.3.10 LED flashing (gateways and transponders) ......................................................................... 27
6.4 System .............................................................................................................................. 27
6.4.1 Network ............................................................................................................................ 27
6.4.2 Enabling/disabling network ................................................................................................ 27
6.4.3 Exploration ........................................................................................................................ 28
6.4.4 Routing information........................................................................................................... 28
6.4.5 Routes ............................................................................................................................... 30
6.4.6 Metrics .............................................................................................................................. 33
6.4.7 Services ............................................................................................................................. 34
6.4.8 Firmware update ............................................................................................................... 35
6.4.9 License management ......................................................................................................... 37
6.4.10 Protocols ........................................................................................................................... 38

Application Manual, 01/2022, C79000-G8976-C531-06 3
Table of contents

4 Application Manual, 01/2022, C79000-G8976-C531-06
Introduction 1
Purpose of this documentation
The document supported you during the installation and configuration of the "SIMATIC RTLS
Network Configuration" client, which is a component of the locating software "SIMATIC RTLS
Locating Manager".
Validity of this documentation

This documentation is valid for version 2.13.0.0 of the "SIMATIC RTLS Locating Manager".
Additional information
You can find additional information on the SIMATIC RTLS products mentioned in this
documentation in the Readme file or on the Siemens support pages.
Link: (https://support.industry.siemens.com/cs/en/en/ps/25277)
Trademarks
SIMATIC RTLS ® is a registered trademark of the Siemens AG.
Industry Online Support

In addition to the product documentation, the comprehensive online information platform of
Siemens Industry Online Support offers support at the following Internet address:
(https://support.industry.siemens.com/cs/us/en/)
Apart from news, there you will also find:
• Project information: Manuals, FAQs, downloads, application examples etc.
• Contacts, Technical Forum
• The option submitting a support query: (https://support.industry.siemens.com/My/us/en/)
• Our service offer:
Right across our products and systems, we provide numerous services that support you in
every phase of the life of your machine or system - from planning and implementation to
commissioning, through to maintenance and modernization.
You will find contact information on the Internet at the following address:
(https://www.automation.siemens.com/aspa_app/?ci=yes&lang=en)

Introduction
SITRAIN - Training for Industry

The training offer includes more than 300 courses on basic topics, extended knowledge and
special knowledge as well as advanced training for individual sectors - available at more than
130 locations. Courses can also be organized individually and held locally at your location.
You will find detailed information on the training curriculum and how to contact our
customer consultants at the following Internet address:
(https://new.siemens.com/global/en/products/services/industry/sitrain/personal.html)
RTLS Technology and Practice (ID-RTLS-TP)

Training and certification
After completing the RTLS certification training, you will be able to plan and implement small
and medium-sized RTLS projects and provide efficient and multifaceted support in large
projects. Your RTLS basics will be strengthened and, building upon them, you will receive
new tools of the trade in order to offer customers the optimal solution for them. The
complete project sequence is taken as a reference and important steps, resources and work
results for each phase are presented. Comprehensive practical exercises in connection with
troubleshooting techniques and a great deal of input from industrial projects allow you to
internalize a confident approach to working with different types of localization projects. With
the training documents, you also receive extensive reference material for your daily work.
Link: (https://www.sitrain-learning.siemens.com/EN/en/rw35251/Industrielle-Identifikation-
RTLS-Technologie-und-Praxis)
Security information
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines, and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions form one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. These systems, machines and components should only be
connected to the enterprise network or the Internet if and only to the extent necessary and
with appropriate security measures (firewalls and/or network segmentation) in place.
You can find more information on protective measures in the area of industrial security by
visiting: (https://www.siemens.com/industrialsecurity).
Siemens’ products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends performing product updates as soon as they are
available and using only the latest product versions. Use of product versions that are no
longer supported, and failure to apply latest updates may increase customer’s exposure to
cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under (https://www.siemens.com/industrialsecurity).

Introduction
Note on firmware/software support

Siemens only provides bug and security fixes for the last released firmware/software version.
This means that Siemens only monitors the current firmware/software version for security
vulnerabilities.
Recycling and disposal

The products are low in harmful substances, can be recycled and meet the requirements of
the Directive 2012/19/EU for disposal of waste electrical and electronic equipment (WEEE).
Do not dispose of the products at public disposal sites.
For environmentally compliant recycling and disposal of your electronic waste, please contact
a company certified for the disposal of electronic waste or your Siemens representative.
Note the different national regulations.

Introduction

Security recommendations 2
General
Note the following security recommendations to prevent unauthorized access:
• You should make regular checks to ensure that the devices meet these recommendations
and/or other security guidelines.
• Evaluate your plant as a whole in terms of security. Use a cell protection concept with
suitable products (https://new.siemens.com/global/en/company/topic-areas/future-of-
manufacturing/industrial-security.html).
• Keep the software up to date. Check regularly for security updates for the device. You can
find information on this at the Industrial Security
(https://new.siemens.com/global/en/company/topic-areas/future-of-
manufacturing/industrial-security.html) website.
• Only activate protocols that you require to operate your system.
• Whenever possible, always use the variants of protocols that provide enhanced security
(e.g. SNMPv3).
• Connections over unsecured network areas must be secured by security mechanisms such
as SSL VPN.
• Always click on the "Disconnect" button when you have finished working with the clients.
Especially when you work remotely on the host on which the clients are located.
• Restrict access to the software and its add-on programs (e.g. database) to qualified
personnel.
• Use the user and role administration to configure the rights of the users according to their
authorizations.
Users, roles and passwords

• Define rules for the use of the software and assignment of passwords. Configure these
roles using UMC and Active Directory.
• Regularly update the passwords to increase security.
• Change user names and default passwords of the databases before you use the software.
For the SIMATIC RTLS Locating Manager, a changeable user and an editable password is
used for each installation. You can change the password via the respective DBMS version.
• Create users and roles that are tailored to the scope of authorization required by each
user. Do not exclusively use the "System administrator" role that is present by default, and
disable the "System administrator" user that is present by default after new users with
corresponding rights have been created. You disable the "System Administrator" rights for
the UMC administrator by assigning this role to a specific user or a user group.
• Only use passwords with a high password strength. Avoid weak passwords, for example
password1, 123456789, abcdefgh.

Security recommendations
• Make sure that all passwords are protected and inaccessible to unauthorized personnel.
• Do not use the same password for different users and systems or after it has expired.
Physical access
Restrict physical access to the device to qualified personnel.
Automation License Manager

If you do not require the network functions of the Automation License Manager, deny access
to its functions in your firewall.
Software (security functions)

• Keep the software up to date. Check regularly for security updates for the product. You
can find information on this at the website
(https://new.siemens.com/global/en/company/topic-areas/future-of-
manufacturing/industrial-security.html).
• Only activate the protocols, functions and interfaces that you require to operate your
system.
• Restrict access to the device with a firewall or rules in an access control list (ACL - Access
Control List).
• The option of VLAN structuring provides good protection against DoS attacks and
unauthorized access. Check whether this is practical or useful in your environment.
• Enable the logging functions to record changes and access attempts. Check the logging
information regularly.
Secure and non-secure protocols

• Check whether the use of SNMPv2c is necessary. SNMPv2c is classified as non-secure. The
product provides you with suitable setting options.
• When SNMP is enabled, change the community names. When no unrestricted access is
necessary, restrict access with SNMP.
• Use secure protocols when access to the device is not secured by physical protection
measures. The following protocols provide a secure alternative:
– SNMPv2c → SNMPv3
– SMTP (simple) → SMTP via SSL
– NTLM → Kerberos (UMC connection to Active Directory)
• Avoid or disable non-secure protocols. For historical reasons, these protocols are available,
however not intended for secure applications. Use non-secure protocols on the device
with caution.
• To prevent unauthorized access to the device or network, take appropriate protective
measures against non-secure protocols.

List of available protocols (local access via a local network)

The following is a list of all available protocols and their ports through which the RTLS
devices/products can be accessed. Note the list when you configure a firewall.
Explanation for table:
• Services/protocols
Services or protocols that support the RTLS devices/products.
• Port number
Port number assigned to the protocol/service.
• Default port status
– Open
The port is open by default.
– Closed
As default the port is closed.
• Authentication
Specifies whether the communication partner is authenticated.
• Loopback only
Specifies whether the protocol only needs local connections.
– Yes: No port must be open within the firewall. Access restrictions are recommended.
– No: The functionality requires this port to be accessed. Restrict access to necessary
hosts.
– Optional: The functionality depends on your system. Restrict access to necessary hosts
if your system requires remote access.
Service/Protocol Port number Default port status Authentication Loopback only

Data export modules TCP/variable Closed No Optional
Internal server TCP/8001 Closed No Yes
communication
Client connection TCP/9500 Open Yes Optional
Client connection TCP/9501 Open No Optional
E-mail TCP/variable Closed Optional No
Wireless network TCP/8000 Open No No
WAMP router TCP/12344 Closed Yes Optional
Microsoft SQL Server TCP/1433 Open Yes Optional
Microsoft SQL Server UDP/1434 Open No Optional


Overview 3
General
This document describes how to use the "Network configuration" client for the
Locating Manager.
Note
The client may only be used by experienced and trained users.
Application
With the "Network configuration" client, you can create, manage or delete gateways, anchors
and transponders of the RTLS locating system. These devices can also be grouped together. In
addition, the "Network configuration" client provides a variety of configuration and
management options.
Start client
You start the "Network configuration" client (NWConfig.exe) under "Start >
SIMATIC RTLS Locating Manager > Network configuration"
Definition of terms
Term Description
Gateway Infrastructure device that uses the Ethernet port
Transponder (TAG) Mobile device to be localized in RTLS localization network
Infrastructure devices Gateways with and without using the Ethernet port
Nodes All gateways and transponders of an RTLS localization network
Locating Manager server Software that processes the localization data into position data that can be visualized
Client Software for management and control of the RTLS locating system and the nodes
Localization Position determination
Ranging Distance measurement between a transponder and a gateway
Position calculation Calculation performed by the Locating Manager server of the position coordinates based on
the localization data and various filters
Virtualization Graphical representation of the determined position data
Exploration Automatic search process to find unknown, for example, newly installed nodes within the
wireless range of the RTLS localization network
MHI Multi-hypothesis initialization
Determines the final position from multiple individual positions
TWR Two-Way Ranging
Determines the delays of the signal and calculates the distance between the nodes.

Overview
Term Description
TDOA Time Difference of Arrival
Time-based process to determine the positions of the transponders
UWB Ultra-wideband
Radio technology with wireless transmission

Functions in the menu bar 4
Connecting and disconnecting
After the client starts, click the "Connect" button to connect to the Locating Manager and log
in. As an alternative, you can make a connection using the menu "File > Connect".
You can use the "User Configuration" client to assign roles to additional users. Fill in the
"Domain" text box when the user is an Active Directory user.
The status of the connection is displayed on the left in the status bar.
When a connection has been established, the connection symbol changes to "Disconnect",
indicating an existing connection. The red connection symbol "Connect" indicates that there
is no connection.
If a connection to the RTLS locating system could not be established, an error message is
issued after about 20 seconds. The connection symbol changes to "Connect" and
"Disconnected" appears in the status bar.
Connection configuration
Proceed as follows to configure the connections:
1. Adapt the server name and port accordingly if a valid connection to the Locating Manager
has not yet been established. The default port is 9500. The server name is the name of the
server in the RTLS localization network on which the Locating Manager server was installed.
By default, "localhost" is set. You can change these configurations at any time in the
"Options > Connections" menu.
2. Enter "localhost" in the "Host name or IP" text box if the Locating Manager server is on the
same PC as the current client. This is the default setting.
3. Otherwise, enter the appropriate name or the IP address of the Locating Manager server in
the RTLS localization network.
Note
Ensure that communication between the Locating Manager server, the infrastructure and the
current client is not blocked by a firewall or incorrect configuration on the local network.
Change password
You can change the password of the current user under "Options > Change password..". The
password is valid for access of this user to all clients within the Locating Manager.

Functions in the menu bar
Changing the language

You can switch between "German" and "English" under "Options > Language" .
Search
Under "Options > Search", you can search for any terms, descriptions or even addresses. Any
hits found are displayed in the user interface. If there are several search results, the main
window switches to the selected hit. Using the F3 key, you can switch from one result to the
next.
Search options
Under "Options > Search options", you can restrict the search range to specific node types,
transponders, transponder names, antenna positions or types, or specific text boxes. The text
boxes for selection for the transponders can be individually assigned. You can also open the
"Search options" dialog box by clicking on the "Options" button in the search window.
Check for update

If the "Check for update" option is selected, the system checks to see if new version of the
client is available on the server.
Automatically look for a better picture and display it

You can find this setting under "Options > Automatically look for a better picture and display
it".
When this option is selected, the client automatically tries to switch to the view area that best
matches the currently displayed area. This allows you to use detailed images for close zoom
levels or overview images.
Clear log
Under "Options > Clear log", you can delete the messages displayed in the output window for
logging data. Newly added messages are displayed again.
Update picture automatically

You can find this option under "Options > Update picture automatically". This option allows
you to specify whether clients automatically check for and use updated maps on the server
when they start.
List devices without a license in the tree

If you enable this option, devices that do not have a license at the given time are nevertheless
displayed in the tree topology.

Symbols in the tree topology of the
Locating Manager and the clients 5
In all clients of the Locating Manager in which anchor, gateways and transponders are
displayed, you can determine the operating status of the device using the following symbols:
Anchor Gateway Transponder Description

Device is offline and does not send a heartbeat
Device is online and ready for operation
Device is online and ready for operation, but with low voltage
warning
Check the supply voltage. Replace the batteries or charge the
rechargeable battery.
- - Transponder is online, operational and being moved
- - Transponder is online, operational and being moved, but

with low voltage warning
Check the supply voltage. Replace the batteries or charge the
rechargeable battery.
- - Transponder is in "via static configuration" operating mode
...

Symbols in the tree topology of the Locating Manager and the clients

Configuration 6
6.1 Overview of the configuration
You can make the following configurations in the "Network configuration" client:
• Create, configure and delete nodes
• Create, configure and delete gateway groups
• Create, configure and delete anchor groups
• Create, configure and delete transponder groups
• Perform firmware updates
• Create and manage routes
• Create and manage metrics
• Start exploration
• Enable or disable localization globally
• Update the status of the Data Export Service
• Reload statistics
• Manage the license
• Manage the logging of localization results
• Export and import device coordinates
• Display system information
• Configuring event management
Most of the configurations of the respective device types are managed in the tree topology
under "Gateways", "Anchor" and "Transponder". New anchors can be created manually or
localized automatically via exploration ("Tree topology > System > Network > Start"). The
exploration procedure is described in more detail in the section "Exploration (Page 28)".
Note
Any changes to the device configurations must be confirmed by clicking the "Save" button.

Configuration
6.2 Gateways, anchors and transponders

The gateway establishes the connection between the wireless network and the
Locating Manager server and is used as a measuring point for the localization and as a
collection and transmission point of the anchor data.
Transponders are the mobile units of the RTLS locating system. Their positions are
determined by the Locating Manager server, e.g. from measurements between the
measuring points and the transponders.
Select "Gateway", "Anchor" or "Transponder" in the tree topology to add corresponding
devices and groups.
Select a specific device in the tree topology to rename, delete, move it to a group, update its
firmware or set and configure the position of gateways and anchors.
6.2.1 Adding a gateway, anchor and transponder manually

You can manually add devices to the Locating Manager using the respective buttons "New
gateway", "New anchor" and "New transponder". However, gateways are localized
automatically by the Locating Manager. You can automatically add anchors using exploration
(section "Exploration (Page 28)") and transponders are also added after startup, so that
manual addition of devices is only necessary in exceptional situations.
The network address of the device (see nameplate of the respective device), the freely
selectable name, the device group to be determined via the drop-down list and the position
for gateways and anchors are queried via the text boxes. The IP address and the port within
the local network are also required for gateways. Select the "Use in network" check box to use
the device for localization within the Locating Manager. Clicking on the "Create" button adds
the device to the RTLS locating system.
6.2.2 Gateway, anchor and transponder groups

You cannot delete the "DEFAULT" gateway group, "DEFAULT" anchor group or "DEFAULT"
transponder group created by default, but you can rename them.
Create a new device group

Proceed as follows to create a new device group:
1. Click the "New gateway group", "New anchor group" or "New transponder group" button.
2. Enter a name and description for the device group.
3. Click the "Save" button.

Configuration
Moving devices to other groups

To move devices out of one group into another, follow the steps below:
1. Click the button "Move/Delete Gateways", "Move/Delete Anchor" or "Move/Delete
Transponder".
2. In the "Source group" drop-down list, select the group in which the device you want to move
is located.
3. In the "Target group" drop-down list, select the group to which you want to move the
device.
4. Select the check boxes for the devices you want to move.
Use the "All" button to select all devices at once.
Use the "None" button to deselect all devices at once.
5. Confirm your selection by clicking "Move".
Note
Alternatively, you can select an individual device in the tree topology to move it to another
group. To do this, select the desired group in the "Group" drop-down list and click the "Save"
button.
Deleting devices
Proceed as follows to delete a device:
1. Click the button "Move/Delete Gateways", "Move/Delete Anchor" or "Move/Delete
Transponder".
2. In the "Source group" drop-down list, select the group that contains the device you want to
delete.
3. Select the check boxes for the devices you want to delete.
Use the "All" button to select all devices at once.
Use the "None" button to deselect all devices at once.
4. Confirm your selection by clicking "Delete".

Configuration
6.3 Device configurations
6.2.3 Firmware update for device classes

In the tree topology under "Gateway", "Anchor" or "Transponder", there is a "Firmwareupdate"
section for each device. In this section, you can determine all devices of the respective type
and transfer a specific firmware to all devices of the selected type. The firmware update for
individual devices is described in the "System information and firmware update of individual
devices (Page 25)" section. Under "System > Firmwareupdate", you can perform more
differentiated updates with extended selection and sorting options (section "Firmware update
(Page 35)").
Only Siemens firmware may be used for the Locating Manager. You can recognize files of the
Siemens firmware by the "*.cagl" extension. The installation or storage path for the firmware
is the installation folder of the Locating Manager, by default "C:\Program Files
(x86)\SIMATIC_RTLS_LM\Server\Firmware".
Clicking "Select firmware" displays all available firmware versions. Select the desired software
from the drop-down list and transfer it to all devices of the selected type by clicking the
"Transfer…" button. The firmware transfer process may take a few minutes. Do not switch off
the devices during the process. Status messages and errors are displayed in the output
window for logging data.
6.2.4 Tolerance of the heartbeats

The tolerance (cycles) in the heartbeat configuration determines how many heartbeats of a
device in the respective group may fail until the connection to the device is displayed as
terminated. The additional tolerance [ms] indicates the waiting time between two heartbeats
to compensate for signal propagation delay effects. Click "Save" after a change has been
made.

The network address output in the view of a specific gateway, anchor or transponder
represents the wireless address of the device in the Locating Manager. It is indicated on most
devices and must be entered when creating devices manually. You can change the name of
the device. It is also possible to move a device to another group using the "Group" drop-down
list.
Note
Any changes to the device settings must be confirmed by clicking the "Save" button.

Configuration
6.3.1 System information

Information about the firmware of the device is displayed in the "System information"
section.
If the firmware file of a node does not exist on the Locating Manager server, you cannot
configure this device or update it with a new firmware. This is highlighted in red. If you move
the mouse pointer over the display, information is displayed about the firmware file.
You can find additional information on the firmware files on the Support pages:
(https://support.industry.siemens.com/cs/search?search=rtls&type=ProductSupport%2CCatalo
g%2CCertificate%2CCharacteristic%2CDownload%2CDownloadSoftwareArchive%2CExample
OfUse%2CFaq%2CManual%2CProductNote%2CSlk%2CForum&lc=en-US)
6.3.2 Internal and external voltage

The information fields "Internal voltage" and "External voltage" not only indicate the input
voltage currently measured by the device, but also provide information about the received IO
signals (input/output). For transponders, the information field additionally indicates whether
the transponder is currently moving (Acc: 1) or do not move (Acc: 0).
Example:
Voltage 5.8V 0% (IO 0x00 Virt0x01) (Acc: 1)
External voltage is the voltage transmitted from outside to a device, for example by a power
supply unit. Internal voltage, on the other hand, describes the status of a device-internal
power supply, such as batteries or rechargeable batteries built into the device. The voltage
value shown in each case depends on the device type being used.

Configuration
6.3.3 Last heartbeat

The "Last heartbeat" information field indicates when the last heartbeat was received by the
device. You manually request a heartbeat by clicking "LS" in the "System information" section.
Example:
Last heartbeat 2019-09-27 14:45:38.000
This line is missing for devices that have never sent a heartbeat to the server. Transponders
are not always ready to receive. This may delay the request for a heartbeat.
6.3.4 Ping
You can send text message to the device using the "Ping" button in the "System information"
section. The duration until the response to the request of a ping is output in the output
window for logging data. Transponders are not always ready to receive. Requesting a ping
may be delayed as a result.
6.3.5 Using a device in the network / enabling localization

Select the "Use in network" check box in the display of a device to use the gateway, anchor,
or transponder in the RTLS localization network.
If you do not select this option for devices, then they will only be displayed in the "Network
configuration" and "Integration Wizard" clients and will not be visible in the other clients.
These devices are not used for exploration.
The infrastructure devices (gateways and anchors) detected by the exploration are
automatically enabled for use in the network. You need to perform this activation manually
for transponders. In addition, select the "Localization" option for each transponder that is to
be localized.

Configuration
6.3.6 System information and firmware update of individual devices

The "System Information" dialog box allows you to query the system information and transfer
firmware to the device highlighted in the tree topology .
When you click the "Read" button, the firmware version and other information about a
gateway, anchor or transponder is updated in the text box below.
You can select the firmware to be transferred in the drop-down list. You confirm the selection
by clicking the "Select firmware" button and the firmware is transferred to the device by
clicking the "Transmit..." button. Status messages and errors are displayed in the output
window for logging data.
6.3.7 Spatial position of the infrastructure devices

The spatial positions of the individual gateways and anchors with the respective x, y and z
coordinates must be entered manually if there is no corresponding file in "*.csv" format with
this data. The user interface appears for the respective infrastructure devices selected in the
tree topology. The position of the infrastructure devices refers to a freely selectable
coordinate origin, which represents the reference point for all measurements and for the
visualization. Click "Save" after entering the coordinates.
Under "System > Network", you can export all entered position coordinates as a file in "*.csv"
format to import them later. The information in the file with "*.csv" format must be
structured as follows in order to be read and correctly assigned by the Locating Manager.
Name;x;y;z
Gateway 2;-618;-66;0
Gateway 1;96;-43;85
The name is the name freely assigned to the device in the Locating Manager (section "Device
configurations (Page 22)"). You can create the file in "*.csv" format from the Excel table with
the position data of the surveyor.
6.3.8 IP configuration of the gateways

If a gateway is not automatically localized in the wireless network, you can perform the IP
configuration via the "IP Configuration" application ("Start > SIMATIC_RTLS_LM > IP
Configuration").
The IP address identifies a gateway in the local Ethernet. This address depends on the device
and is provided by the default configuration with "192.168.1.232". If you use "DHCP", then
the gateway receives its address automatically from a DHCP server in the local network. The
port is 1010.

Configuration
Make configuration settings via the TCP/IP protocol

You can only configure using this protocol if the gateway is not connected to the
Locating Manager server. Proceed as follows to make configurations via the TCP/IP protocol.
1. Stop the Locating Manager server under "Start > SIMATIC_RTLS_LM > Stop tasks".
2. Change the address in the "TCP-IP configuration" section according to the address setting in
your network.
A list of all available devices is displayed by clicking the "..." button to the right of the address
field.
3. Click "XPort Search" to search for missing devices.
4. Select the desired device and click the "Select" button to transfer the IP address directly into
the address field.
5. Click "Open" in the "IP Configuration" application to read out the data of the selected
gateway and display it in the "Gateway Configuration" section.
The wireless network address is displayed in the Locating Manager ("NWAddr." text box) for
security purposes and to check whether the correct gateway is actually configured. The
network address is located on the device itself.
6. Check all configurations, including, for example, whether the gateway is in the correct
subnet.
7. Click "Set" to transfer any changes to the gateway.
6.3.9 Values on node (gateways)
NOTICE
Qualified personnel
All IP configuration related configurations may only be performed by qualified personnel
with expertise in the client "Network configuration".
In the "Values on node" section, you can read the values set on the device relating to its
network operation, set new values or the default value by clicking the respective button.
After each change, click "Reset" to enable the new values for the device.
The values to edit are Duplex mode, DHCP mode, Device IP, Server IP, Subnet mask, and
Gateway IP. It may be necessary to change these values, for example, during the
commissioning of the Locating Manager to adapt to the local IT network or to change your
local network infrastructure.

Configuration
6.4 System
6.3.10 LED flashing (gateways and transponders)

For gateways and transponders that have an LED and support the functionality to make it
flash, you can start the flashing of the LED via a button in their device configuration. To do
this, click the "Flash LED" button. This sends a command to the device that causes the LED to
flash for 15 seconds with a specific pattern. The log window will then show you a message
about whether or not the command was successfully delivered.
6.4 System
You can perform the following actions under "System" in the tree topology:
• Network-specific actions, such as exploration
• Enable and disable localization service
• Update of the firmware of the devices
• Back up database settings
• Manage licenses
• Make configurations for logging.
You can also see information about the current server version and the scope of licenses.
6.4.1 Network
You can control the wireless network and its functionalities under "System > Network" in the
tree topology.
You can perform the following actions:
• Enable or disable the wireless network
• Start exploration
• Import pre-configured device coordinates or save existing coordinates
• Import saved coordinates
• Query and display routing information
The "TDOA time master" sub-item enables the definition of the time master for the "Time-
Difference-Of-Arrival" (TDOA) technology. The cyclically transmitted signals of the
transponders are received in a time-synchronous network and the propagation time
difference of the signals is measured. The Locating Manager server uses the propagation time
difference to determine the position.
6.4.2 Enabling/disabling network

Click "Stop tasks" or "Start tasks" to disable or enable the Locating Manager's communication
services that are relevant for localization. This is displayed in the output window for logging
data. You can only perform localization when the network is enabled.

Configuration
6.4 System
6.4.3 Exploration
If at least one gateway has been configured and enabled, you can automatically search the
topology of the RTLS localization network via the exploration in the tree topology under
"System > Network". Starting from this gateway, exploration searches the wireless network
for additional infrastructure devices. All wireless receivers are located within range,
integrated into the network via static routes, automatically assigned to the respective
"DEFAULT" group in the tree topology and configured. Based on the resulting network, a
search is conducted for further wireless systems which could not be reached in the first step.
If no further gateways or anchors have been located, the exploration is complete. Exploration
may take several minutes depending on the size of the RTLS localization network. The "Start"
button below the exploration configuration is disabled during this time. The exploration
progress is recorded in the output window for logging data.
Note
If gateways with Ethernet are used, you need to perform an exploration. At the end of the
exploration, enable the gateways to connect to the transponders.
When you integrate new gateways into an existing production system, this setting is not
active to avoid affecting the existing production system.
Transponders are not localized with exploration. Instead, they are automatically added and
included in the tree topology if the RTLS localization network has been set up correctly. If you
have enabled the "Localization" option in the transponder display screen (section "Using a
device in the network / enabling localization (Page 24)"), the transponders can be located. If
you have enabled "Partial exploration", you can select individual nodes which serve as new
starting points for partial exploration.
6.4.4 Routing information

Define the device positions so that the functions offered under "Routing information" can be
meaningfully used. You can get a better visualization if you have created and scaled a
location view in "Localization Configuration" client beforehand. You can find details on the
procedure in the "Location view" section of the "Localization Configuration" client
documentation. The "Routing information" section includes the routes and metrics. The
routes describe which path the data take from the transponders to the server and vice versa,
i.e. the communication relationships between the devices. The metrics show which devices
are accessible to each via wireless and how good this wireless connection is. Routes and
metrics are generated automatically with each exploration and are selected accordingly in the
drop-down list. Move the mouse pointer over the route / metric selected in the drop-down list
to get a complete display of the route or metric name.

Configuration
6.4 System
Displaying routes or metrics

The operation for routes and metrics is identical. Clicking "List" displays all existing route or
metric data records as a drop-down list. Select the desired data record and then click "Select".
The graphic representation of the data record then appears immediately.
You can use the "Create" button to manually generate route or metric data records. A view
without any routes or metrics is displayed. Use the "Delete" button to permanently delete the
selected route or metric record.
The infrastructure devices are represented by gray dots, with gateways having a small black
bar in their circle symbol.
Note
Navigation in the map
You can use the scroll wheel of the mouse to navigate faster through the routing or metric
map. Rolling the wheel shifts the display range vertically and holding down the shift key
moves it horizontally. By using the scroll wheel and the control button at the same time, you
can zoom in and out of the map.

Configuration
6.4 System
6.4.5 Routes
Basically, it is recommended to use the routes automatically generated during the
exploration. In individual cases, such as with variable wireless accessibility of the device
infrastructure (e.g. an occasionally high bus or pallet stack covering devices), it is
recommended to create additional routes. This ensures permanent accessibility of the
Locating Manager server by the infrastructure devices. Routes with the highest priority are
shown in red, routes with lower priority in blue.
Show Locating Manager server

You can show or hide the Locating Manager server by selecting the "Server" option and
setting any position. Displaying the Locating Manager server is usually not helpful in large
RTLS localization networks, since each individual connection to a gateway is displayed and
the display quickly becomes confusing.
Selecting routes
If you enable the arrow symbol to the right of the graphic, you can select routes or
individual devices in the graphic. If you select a device or the Locating Manager server, the
devices for which there is a direct route are displayed. The selection displays the route
information of the selected route.
You can delete all routes of the selected device with the "Remove routes" button. With this
option, make sure that new routes are created if required so that the device remains
accessible. If a device does not have a route to the Locating Manager server, it no longer
participates in the communication. It can still be used for locating if it was configured as last
active for locating.
Creating routes
It is generally recommended to use the automatically generated routes and only create
additional alternative routes. Proceed as follows to create a route:
1. Click to create a route.
2. Select the target device by clicking the mouse while pressing the Shift key.
3. Now select the device or devices through which the target device is to communicate with
the server, up to the server if it is shown.
If the Locating Manager server is hidden, double-click the last device before the server (i.e. a
gateway) so that the route is extended to the Locating Manager server.
4. Click the button if you want to create several routes in order to remain in creation mode
after creating a route.

Configuration
6.4 System
5. Click the button if the routes are to be created in both directions, i.e. from the device to
the Locating Manager server and in the opposite direction.
The route for the respective opposite direction is created automatically when the first route
direction is created.
Note
When you select the "Server warning" check box, a warning appears in the output window
for log data to indicate that a created route does not extend to the server.
6. Enable the crosshairs and click on the desired position on the map. The x and y
coordinates of the position are displayed in the output window for logging data.
It may be helpful to query positions (in each case to the reference point/coordinate origin) in
the map.
7. Click "Save" to save all the changes you have made. Click "Enable" to apply the changes and
transfer them to the node.
You can find more options for creating routes in the "Routing" section.
Button Description
Restore This button allows you to restore deleted routes.
This only works if the deletion has not yet been saved.
Delete The button deletes the entire routing set.
Copy Use the button to create a new routing set that corresponds to the one currently
displayed. This enables you, for example, to add additional routes based on the
automatically generated routing data record without changing the old data
record. This allows you to reactivate the old routing set at any time.
Validate You can test the routing set using the button. Any errors such as the missing
server connection of individual devices are displayed in the output window for
logging data. You can use the "Only routes" check box below to check devices for
which there are routes.
Clear Use the button to delete all routes in the routing set. The "Gate <-> Server"
button is then the first action to be performed. This creates routes from Locating
Manager server to all gateways.
List The button triggers the output of all routes in the output window for log data.
The devices are identified by their network address and the priority ("weight") of
the respective route is also displayed.
From metrics Click the button to create new routes from the last available metric set if a metric
set has been loaded in the client.
Check device Use the button to check whether the routes in the user interface match those
saved on the devices. The result of the check is displayed in the output window
for logging data.

Configuration
6.4 System
Display routing information (list)

When you click the "List (all)" button, a table is created in a dialog box for the infrastructure
device selected in the map. It lists all routes communicated through this device. The table
created by clicking the "List (from/to)" button shows only the routes between the selected
device and the Locating Manager server.
Read the routing table from left to right.
Columns Description
Column 1 Describes the costs of a route
For the routes automatically created with exploration, this information indicates
how good and fast a route is (internal calculation from the number of hops to the
server and the corresponding reception field strengths on the route). As a rule,
the most effective routes are always used.
Column 2 Describes the message source
The device whose data is to be transmitted to the Locating Manager server or the
Locating Manager server in the reverse direction.
Column 3 to n-1 Intermediate routers that transfer messages from the message source in column
2 to the message sink (Locating Manager server or reception node) in column n.
Column n Message sink
Priority of the route

Additionally created routes get the value "Hops + 1", so they are not used preferentially. You
can change the sequence in which routes are used manually by entering a different number
in the "Costs" column of the corresponding cell. The lower number always has priority. As
soon as a cost field has been changed, the "Weights > Cost" button appears at the bottom of
the table. Click this button to transfer the changes made to the nodes. From this point on, the
newly defined priority will be used when selecting routes. Note that there are two entries for
each route, one for the route from the device to the server and one for the route from the
server to the device. The costs must be changed for both directions. Accordingly, the route
that is primarily used is displayed in red.

Configuration
6.4 System
Selection bar and menu in the table

The selection bar enables more settings to be made.
Setting Description
Remove both ways Select this check box to delete routes for both directions if the
corresponding action is executed via "Right-click > Menu".
Highlight node Select this check box to highlight the corresponding route and device by
highlighting the table cell on the map.
On top You can use this check box to keep the displayed table in the foreground.
If this check box is cleared, the table is moved to the background of the
user interface.
The shortcut menu in the table allows you to make further settings.
Setting Description
Remove route Click this button to delete the route selected in the table. Note here
whether "Remove both ways" was enabled beforehand.
Remove route highlight Click this button to show all routes and devices displayed on the map in
the same way.
6.4.6 Metrics
The metrics are relevant when routes are optimized or created manually. You can also use the
metric to run error diagnostics, especially to determine whether an infrastructure device is
wirelessly accessible. A metric data record shows which devices can reach each other
wirelessly and how well at the respective time they were set up. A metric set is created with
each exploration. All potential wireless connections or metrics between the individual devices
are displayed.
Click the button to select objects in the map. You can decide whether you want to display
the selection of infrastructure devices and/or metrics by selecting the corresponding
and/or buttons.
As soon as you select an infrastructure device, a section for this device appears. The device
type, the network address and the name are displayed.
Button Description
Readout Clicking the button measures the current reception field strength and stability of
the wireless connections.
Remove metrics The button allows you to delete the metrics of the selected device or metric.
Relocate in map You can reposition a device by clicking the button.
To do this, select the device. Click "Relocate in map" and then on a new position
within the map.
Save This button becomes active when you have selected a new position for a device.
Click the button to save the position.
Restore This button becomes active when you have selected a new position for a device.
Click the button to undo the change.

Configuration
6.4 System
After selecting a single metric, the associated metric data appears. The network and device
names of the two devices involved are displayed as source (Src - Source) and destination (Dst
- Destination). If you click the "Src <-> Dst" button, you can swap the direction of the data
transfer. The button allows you to edit or create metrics simultaneously in both directions.
RSSI is an indicator for the quality of the reception field strength, where 127 is the maximum.
If you click the "Range" button, a distance measurement between the two devices is triggered
and the result is displayed in the "Dist cm" text box.
"Stability" shows the stability of the radio connection between the devices on this router. The
value range is from the value "0" to the value "100".
You can use the metrics to create alternative routes. To do this, read the metrics of the device
to be connected via a route several times in succession at short intervals. This quickly
analyzes which other device is the most stable for the route.
If the metric data record contains nodes that no longer exist (e.g. because the device has
been replaced), an error message appears. If the affected node served as an intermediate
point of a route, it is recommended that you manually create a new route to the destination
device or perform a new exploration.
6.4.7 Services
Enabling/ disabling localization

You can enable or disable localization via "System > Services". If localization is disabled, no
position data is calculated. Once the localization is enabled, the wireless network starts
measuring distances and sends the results to the Locating Manager server, which converts
them into position data.
WAMP router
The port of the WAMP router can be enabled for incoming connections from other PCs when
the programming interface "ExportEpaperAPI" is to be reachable from other PCs. After
changing this configuration, the Locating Manager server must be restarted for the change to
become effective.
TCP port for gateway connections

The TCP port of the Locating Manager server for the gateway connections can be configured,
for example, when the "TeeRevProxy" service is used. After changing this configuration, the
Locating Manager server must be restarted for the change to become effective.

Configuration
6.4 System
Data Export Service state

You can operate the "Data Export Service" with one and with multiple interfaces. An example
is the use of different depot management systems at different locations within a transport
company. The localization data from the Locating Manager is transferred to the depot
management systems and the data from the different locations is compared via several
modules of the "Data Export Service".
Click "Update" in the "DataExportService state" section to display a list of all configured
modules of the "Data Export Service". Modules operating error-free are displayed green,
modules that not operating error-free are displayed red and modules that are not connected
are displayed orange. The list contains buttons for enabling and disabling the individual
modules. You can find more information on error messages in the documentation for the
"Log Viewer" client.
You can use the "Logging" check box to determine whether the data transfer of a module to a
file should be logged. You can find additional information in the "Data Export Service"
documentation. You can configure the modules during the module runtime.
Statistics
Certain processes in depots, plants or other localization areas are monitored and statistically
recorded by the Locating Manager as a process model. The statistics are used, for example, to
detect and evaluate how many vehicles are in the depot and which of these vehicles have not
been detected in the entrance area. If you click the "Load configuration" button in the
"Statistics" section, the configuration files for the Locating Manager statistics module are re-
read without stopping the Locating Manager server to do this. This is useful if you have made
changes to configuration files. Clicking this button signals all Locating Manager services that
they must read the modified "StatisticConfig.xml" and "StatisticProjectConfiguration.xml"
configuration files.
6.4.8 Firmware update

This functionality is especially intended for updating a larger number of similar devices. You
can update the firmware of individual devices by selecting the device in the tree topology and
then going to the "System Information" subsection (section "System information and
firmware update of individual devices (Page 25)"). To perform a firmware update, you need
the corresponding firmware file in "*.agl" or "*.cagl" format. By default, these files must be
located in the directory "C:\Programs (x86)\SIMATIC_RTLS_LM\Server\Firmware" on the
Locating Manager server.
In the tree topology under "Firmware update", the "Selection of nodes to update" section
contains a list of all devices of the RTLS locating network, including devices currently inactive
or switched-off. The firmware update is performed with a time delay as soon as the device is
active again or can be reached via the RTLS localization network. For smaller networks, you
can select the desired nodes by selecting the check box of the device. To make the update
function practical for larger networks, there is a shortcut menu. This provides self-explanatory
sorting options for the node list.

Configuration
6.4 System
The "Select" command in the shortcut menu offers options according to which the devices are
automatically selected in the list. The option representing the best solution in the specific
case depends on the respective project status. Note that the selections are added together.
This means, for example, that if you first select "Transponder" and then "Anchor", all
transponders and all anchors are selected.
In the "AddNode" section, all available firmware files are displayed in the shortcut menu. You
can use the "R" button to update this list after you have copied a new file into the firmware
directory, for example. Select the firmware to be transferred to the previously selected
devices. Select the "List only matching" check box to improve the clarity of this list. After you
click the "R" button, firmware files that do not match the selected devices are hidden.
If you select the "Show idle nodes" check box, devices whose firmware update has been
completed will continue to be displayed in the list. If the check box remains cleared, these
devices will be hidden after a certain period of time. The update process starts as soon as you
have selected the "Add" button.
The "State counter" section shows the number of devices updated via the selection made, as
well as the status the devices have.
All devices to be updated are listed individually below.
Name Description
Address Shows the network address of the device
Description Shows the name of the device
Current Shows the current firmware version
Target Shows the firmware version after the update
State Shows the current status of the update
StateId Shows the corresponding status number
Counter Shows the number of attempts of the update
If you select a firmware version that does not match, the update is not performed for the
corresponding device. Instead, a warning is issued.

Configuration
6.4 System
6.4.9 License management

In addition to checking the sufficient size of the license, license management enables
assignment of licenses to individual devices. You can open the license management by
clicking the button in the menu bar once.
Select "System" in the tree topology to see how many transponders the license is valid for.
License management provides a much more detailed view of the licensing scope.
No license
If no license is available, the following view appears:
Localization is disabled. Devices are no longer displayed in the "Localization Configuration"

client. In this case, you can add or renew the license via the "Read license" button. As an
alternative to reading in the license using the button, you can wait about one minute for the
system to automatically read the license.
Allocating licensing capacity

Each sub-item of the license management in the tree topology enables the assignment of the
license quota to the respective device types or functionalities. You can temporarily make the
assignment to a device without a license by selecting the respective option and automatically
release it by deleting the device.
"Allocate temporarily" means that free (unused) licenses are automatically, but only
temporarily, assigned to devices without a license.
"Deallocate licenses when deleting" causes manually assigned licenses to be automatically
released as soon as the node is deleted from the system.
Manual assignment
If one or more devices have no license and licenses are not assigned automatically, this is
displayed in the overview of the respective device group. A warning appears in the view of
the affected device itself.

Configuration
6.4 System
Select the corresponding sub-item in License Management to assign a license from the quota
to the device. Select the affected device in the "Transponder known to the system" section
and click the arrow button to move it to the "Mobile nodes with license" section. As soon as
you click the "Save" button, the device is available for localization. You can use the "Restore"
button to undo the changes you have made.
Note
In general, it can be assumed that the license is sufficiently large for the number of devices.
Therefore, it is recommended to use the automatic (temporary) assignment as described
above. Manual, individual assignment of licenses only makes sense in exceptional cases.
6.4.10 Protocols
With "System > Protocols", you can configure whether and for how long the localization data
of the transponders should be stored and whether old log entries should be deleted
automatically.
Note
Only make changes to these settings in consultation with Siemens AG or very experienced
users.
Setting Description
Restore button This button is enabled when you change one of the settings. Click the
button to undo the change.
Save button Click this button to save the settings you have made.
TrackDist The log stores the distance debug data of the transponders to the nodes.
TrackPos The log stores the calculated position data of the transponders.
Save You can configure whether or not the log is to be saved in this column.
Double-clicking on the column name selects or clears all check boxes below.
Duration You can configure the storage duration of the logs in hours in this column.
If you move the mouse pointer over the "Duration" text box, the duration is
displayed in days. You can also enter days or weeks in the text box. To do
so, enter "2d" for "2 days" or "3w" for "3 weeks", for example. This input is
automatically converted into hours.
Delete You can configure whether or not the old logs are to be deleted in this
column.
Double-clicking on the column name selects or clears all the check boxes
below.


APH RTLS-Netzwerkkonfiguration-V2.13.0.0 76

Uploaded by

Copyright:

Available Formats

APH RTLS-Netzwerkkonfiguration-V2.13.0.0 76

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

APH RTLS-Netzwerkkonfiguration-V2.13.0.0 76

Uploaded by

Copyright:

Available Formats

SIMATIC RTLS Network Configuration

Functions in the menu bar 4

Siemens AG C79000-G8976-C531-06 Copyright © Siemens AG 2022.

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

Validity of this documentation

Industry Online Support

SIMATIC RTLS Network Configuration

SITRAIN - Training for Industry

RTLS Technology and Practice (ID-RTLS-TP)

SIMATIC RTLS Network Configuration

Note on firmware/software support

Recycling and disposal

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

Users, roles and passwords

SIMATIC RTLS Network Configuration

Automation License Manager

Software (security functions)

Secure and non-secure protocols

SIMATIC RTLS Network Configuration

List of available protocols (local access via a local network)

Service/Protocol Port number Default port status Authentication Loopback only

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

Changing the language

Check for update

Automatically look for a better picture and display it

Update picture automatically

List devices without a license in the tree

SIMATIC RTLS Network Configuration

Anchor Gateway Transponder Description

Device is online and ready for operation

- - Transponder is online, operational and being moved, but

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

SIMATIC RTLS Network Configuration

6.2 Gateways, anchors and transponders

6.2.1 Adding a gateway, anchor and transponder manually

6.2.2 Gateway, anchor and transponder groups

Create a new device group

SIMATIC RTLS Network Configuration

Moving devices to other groups

SIMATIC RTLS Network Configuration

6.2.3 Firmware update for device classes

6.2.4 Tolerance of the heartbeats

6.3 Device configurations

SIMATIC RTLS Network Configuration

6.3.1 System information

6.3.2 Internal and external voltage

SIMATIC RTLS Network Configuration

6.3.3 Last heartbeat

6.3.5 Using a device in the network / enabling localization

SIMATIC RTLS Network Configuration

6.3.6 System information and firmware update of individual devices

6.3.7 Spatial position of the infrastructure devices