Support Portal

Ethernet settings

Related Products
LiDAR sensors

Table of Contents

Ethernet Protocol / Output Format

No Output

the normal measurement data telegram is given out, they are not changed or converted. It comes from the CLV-world, there you can choose between "No function", "Outputformat1" and "Outputformat2, because there you have the output formatter. No function menas in the CLV-world also, the data are given out in the raw format.


Also the normal measurement data telegram is given out, they are not changed or converted. This parameter was implemented because of compatibility downwards.

Customer output format

The device can handle two different scripts. The active Script and the passive script. the passive script is for processing of the measurement data and formatting.If that passive script is active, the measurement data were processed by that script and there they can be formatted. The telegram will then be given out at the ethernetport like it is formatted via the script. But that passive Script function is not fully implemented and not usable at the moment and there is no plan for a release up to now.




DHCP can be used in different sensors. If you use it, be sure that in the network there is a DHCP-Server which can provide and manage DHCP addresses.

Otherwise this addressing mode will not work.
If the DHCP mode is used, we recommend to use as "DHCP Fallback strategy" a static IP address, otherwise the sensor may not be reachable if the DHCP server stops working or if there is no DHCP server.
The Situations are as follows:

  • If everything is correct, the device is set to DHCP and also there is a DHCP server, the server provides an IP address to the device.
  • Is there no DHCP server and the fallback strategy is set to static IP, then the static IP behaviour is used and you can connect that way to the device.

In one case the device cannot be found, and that is if the device is set to DHCP and also the fallback is set to DHCP but there is no DHCP server. In that case, the sensor doesn't get a valid IP-address and a communication by ethernet is not possible.
DHCP timers and procedure:

  • If you chose in the DHCP Mode the option "Retry DHCP" the LMS tries to connect / to get an IP Address from the DHCP Server.
  • If the DHCP Server is not available, the LMS is trying to get an IP address more or less endless.
  • If the first request failed he tries directly again. If this failed, too, the LMS tries again after 10s.
  • Also if this failed then after 20s, then after 30s, after 40s, 50s and so on upto 240s.
  • Is the timer upto 240s, the timer stands fix on this value and tries continuously all 240s again.
  • This happens then "endless".
  • If you chose the option "Fallback Mode- Static IP", then the LMS tries it once, if this failed, he uses then directly the Static IP Address which is parametrized.
  • All the timings and procedures which are described above, are fixed and could not be changed by the customer.

Device Ethernet ports

The Scanners have normally 2 Ethernet ports: 2112 and 2111
On both ports up to 10 connections can be established.
(LMS5xx - 10 connections; LMS1xx - max 5 connections per port; LMS/MRS1000 - 10 connections)

POE Switch and LMS/TiM

The POE standard defines that there must not be any problem connecting devices without POE by Ethernet to a POE switch.
That is also valid for our devcies.

All the TiM and LMS have not PoE, so they cannot be powered up by that.


Telnet is not supported.
EDP devices are not supporting Telnet.

number of connections, DHCP, Ports, POE, TelNet