Pepperl Fuchs WILSEN User Manual
Description of the Payload
Wireless Ultrasonic Sensor
WILSEN.sonic.level
WS-UCC*-F406-B15-B41-*-02
General Information on Operating the WILSEN.sonic.level in a LoRaWAN Environment
General Structure of a LoRaWAN Payload
Commands of
physical layer
Commands of
MAC layer
Application
payload
MIC of MAC
layer
CRC of physical
layer
Application data package 1
ADP2
ADP3
…
ADPn
Length
Universal Unique
identifier (UUID)
Data
0x06
0x0201
0x41C567C9
Support: fa-info@pepperl-fuchs.com
Website: www.pepperl-fuchs.com
Rejoin
The WILSEN.sonic.level rejoins (= logs in to the LoRa network server [LNS] again) during operation "only if required."
Corresponding detection mechanisms are active in the device to detect whether it is still connected to the LNS. If the
device is not connected, the WILSEN rejoins the network automatically.
Confirmed Messages
To elevate the data transmission to a level suitable for industrial use, only "confirmed messages" are used to transmit all
payloads of the WILSEN.sonic.level. This means the WILSEN requires confirmation from the LNS that each message has
been correctly received.
Downlink / Control via LoRa
The WILSEN.sonic.level is a LoRa Class A device. It can process the confirmation messages requested from the LNS, for
example.
The device does not support further control via LoRa i.e., no commands can be sent to the device via LoRa. Likewise, no
parameters in the device can be changed via LoRa. This is only possible via the WILSEN app.
The general structure of a LoRaWAN payload is as follows:
Structure of the application payload data
Content of an application data package
The WILSEN.sonic.level provides its data and information via three different payloads.
Pepperl+Fuchs Group EDM: tdoct7056__eng.docx 11/12/2020 1
Payload 1
Payload 1 contains the sensor data (excluding GPS position data) and is typically used in all applications in which GPS
ADP1
ADP2
ADP3
ADP4
Proximity in cm
Fill level in %
Temperature in °C
Battery status
Universally Unique
Identifier UUID (16 bit)
Data Package
Description
Data Type
Data Length
(Bytes)
Additional Information
0x0B01
proxx_cm
uint16
2
Proximity value in cm
0x0B06
fillinglvl_percent
uint8
1
Fill level in %
0x0201
temp_celcius
float
4
Temperature in °C
0x5101
battery_vol
uint8
1
Battery status: value is provided in
volts/10
Proximity in cm
Fill level in %
Temperature in °C
Battery status
position data is not required.
The transmission of payload 1 and its frequency are determined by the settings in the "LoRaWAN configuration submenu"
of the WILSEN app (see the WILSEN.sonic.level manual).
Payload length:
20 bytes
Structure of the application data payload:
The table below provides details on the individual data packages:
Below is an example of this payload:
04 0B 01 00 41 03 0B 06 59 06 02 01 41 00 00 00 03 51 01 23
Note
If an object is within the dead band of the ultrasonic sensor, the following values are transmitted in the payload:
• Proximity value: 0 cm
• Fill level value: 100 %
If there is no object within the sensing range of the ultrasonic sensor, the following values are transmitted in the payload:
• Proximity value: 65535 cm
• Fill level value: maintains its last value
Pepperl+Fuchs Group EDM: tdoct7056__eng.docx 11/12/2020 2
Loading...