EOS Radar operating Manual

1. General Warnings and Safety Instructions

2. Additional Documentation

Please refer to the information and limit values in the technical data sheet.

The sensor-specific factory settings (Sentiface), as well as the keys and permissible values for the sensor, can be found in the NFC and Downlink Description . The Senticom and Sentivisor tables can be found in the NFC and Downlink Documentation . The special functions for vandalism detection and LoRaWAN® , Mioty® or Cellular (NB-IoT and LTE-M1) documentation.

All documents related to the generic documentation can be found at https://docs.sentinum.de/wichtig-produktübergreifende-dokumentation-für-sensoren .

3. Intended Use

The sensors of the EOS Radar series are designed for non-contact level measurement of liquids, bulk materials, and solid goods using radar technology. They are intended for industrial applications, particularly in the field of tank and inventory monitoring (e.g., IBC containers).

The devices are designed for use in indoor and outdoor applications and must only be used within the specified environmental and operating conditions.

Installation is performed using suitable mechanical interfaces (e.g., 1.5" threads) or, alternatively, using screws, adhesive bonds, magnetic mounts, or suitable brackets, in accordance with the respective installation instructions.

Data is transmitted wirelessly via the supported IoT communication standards for connection to higher-level systems, platforms, or cloud services. Depending on the device model, additional integrated location functions (GPS) may be used for position determination.

Intended use exclusively encompasses operation in accordance with the technical specifications, the permissible operating and environmental conditions, and the manufacturer's installation, configuration, and operating instructions.

4. Product Versions

5. Scope of Delivery and Versions

5.1 Scope of Delivery and Optional Mounting Accessories

Scope of Delivery:

• 3 × batteries (already installed)
• EOS Radar Sensor
• Instruction Manual (digital)

6. Key Components

7. Positioning and Localization

The EOS Radar Series features integrated GNSS functionality for global positioning. It processes signals from multiple satellite navigation systems such as GPS, GLONASS, Galileo, and BeiDou to enable reliable and precise localization.

Positioning is performed via a patch antenna integrated into the device, eliminating the need for an external antenna and ensuring a compact, robust design.

This allows for flexible use in mobile and stationary applications, such as tracking the location of containers, tanks, or movable assets, even under demanding environmental conditions.

8. External Antenna

The sensor features an SMA connector and is equipped with an automatic RF switching function.

By default, the internal chip antenna is used. When a specific external antenna is connected, the system automatically switches to it, ensuring optimized wireless performance.

If no antennas listed in the following table are used, the switch must be made manually via BLE.

9. Assembly and Installation

9.1 Warning and Safety Instructions for Assembly

Please note:

• Do not insert any objects or body parts into the sensor's openings.
• Do not mount the sensor on the ceiling or floor.
• Do not install the sensor at heights exceeding two meters.
• Install the sensor only indoors on a wall in a standard room at a height of 1.50 m to 1.80 m.

The standard versions of the EOS sensor are designed for a wide range of industrial and logistics applications and feature robust housings with a high protection rating.

The following points must be observed during installation:

• Select a mounting location that falls within the specified ambient temperatures and conditions (see technical specifications).
• Do not cover the housing: Wireless communication (e.g., LoRaWAN, BLE) must not be obstructed by metallic objects, solid enclosures, or structurally shielding materials .

• Secure the sensor firmly, ideally using the provided mounting holes. Low-vibration or solid surfaces are recommended.
• Orientation: The standard version does not require any special orientation and can therefore be mounted flat, vertically, or horizontally, depending on the application.
• Do not install in the immediate vicinity of strong electromagnetic sources to avoid signal interference.

9.2 Recommended Mounting Methods

9.3 Mounting Accessories

9.4 General Installation Instructions

9.5 Important Note for Devices with an External Antenna

If you have ordered a device with an external antenna, which can be identified by the gold SMA connector, install the antenna first.

9.6 Wall Mounting with Screws (without SMA and M12)

A drilling template can be found at the end of the operating instructions. This type of mounting is typically used to attach the sensor to the ceiling.

Insert the appropriate screws into the designated holes on the front panel.

Alternatively, suitable wood or plastic screws can also be used if the sensor is to be mounted on those materials. To do this, use the included two-point mount.

Use the included two-point mounting bracket for this purpose.

9.7 Mounting the Sensor with a 1.5-Inch Thread

The sensor has a 1.5-inch external thread and is designed for installation in corresponding 1.5-inch internal threads.

To ensure a secure seal, use suitable sealing materials such as sealing cord or PTFE tape (Teflon tape). When screwing in the sensor, make sure it is positioned straight and mounted without any tilting.

Excessive resistance when screwing in the sensor indicates improper installation and can lead to damage to the thread. In this case, stop the installation process and check the installation.

If the thread sizes differ, use suitable and approved adapters . Installation must be performed in accordance with the instructions in the user manual.

Improper installation of the sensor can lead to leaks, medium leakage, and damage to the thread. This can cause malfunctions or hazards during operation.

9.8 Mounting with M4 Threads

The sensor has four integrated M4 threaded inserts for mechanical fastening. Use standard M4 screws and suitable fasteners for installation.

The maximum permissible screw-in depth is 7.7 mm. Exceeding this screw-in depth can result in damage to the threaded inserts or internal components.

Installation must be performed evenly across all four mounting points to prevent stress in the housing. Screws must be tightened to the specified torque; over-tightening must be avoided. Ensure that the mounting surface is level and sufficiently load-bearing. If necessary, use suitable washers or mounting adapters. Installation must be performed in accordance with the instructions in the user manual.

9.9 Wall Mounting with Magnets

A drilling template can be found at the end of the operating instructions. The magnets shown below are neodymium magnets. Other versions may differ.

Although neodymium magnets offer greater holding force on metallic surfaces, they are only suitable for long-term outdoor use to a limited extent. Please contact us for advice if needed.

Insert the appropriate magnets into the designated holes on the back of the sensor. The magnets shown here are neodymium magnets. Alternatively, ferrite magnets can also be used for this step.

Insert the screws from the opposite side into the designated holes and securely fasten the magnets to the sensor housing.

Optionally, anti-slip covers can be placed over the magnets . The anti-slip cover prevents the magnet from slipping if the mounting object is exposed to vibrations or if its position is changed.

In addition to the rear-panel mounting shown, front-panel mounting is also possible. To do this, swap the positions of the magnet and screw. The magnets are mounted on the front and the screws on the back.

9.10 Wall Mounting with Adhesive Strips

Before using this mounting method, ensure that the surface is clean, dry, smooth, and suitable for adhesion, as an uneven or dusty surface can impair the adhesive strips' hold.

Avoid mounting on rough, porous, or damp surfaces, as this can reduce the adhesive strength and cause the mount to come loose.

After applying the adhesive strips, press the mount firmly for a few seconds to ensure optimal adhesion between the adhesive strips and the surface .

Apply the double-sided adhesive tape to the area shown on the back of the sensor. The tape should be large enough to ensure a secure hold.

When mounting with adhesive strips, make sure that the adhesive strips adhere completely and that no corners come loose.

This mounting option can be used for both the threaded T-variant and the F-variant ("flat variant").

9.11 Front-wall mounting with blind rivet nuts

A drilling template can be found at the end of the operating instructions. Front-panel mounting is used when you want to attach the front of the ApolloN-O sensor to the wall of the object on which the sensor is to be installed.

The front side is the side with the opening in the center, on which the logo is also visible.

This mounting method is the preferred option because it allows for easy battery or SIM card replacement by simply loosening the screws (unlike front-panel mounting with blind rivets).

Step 1: Depending on the sensor type (radar and ToF only), drill the appropriate holes in the wall where you want to mount the sensor. Use the drilling template for this.

The holes for the blind rivet nuts should have a diameter of 6.1 mm.

Step 2: Now secure the blind rivet nuts using a suitable tool. Use the spacer plate and insert the screws into the tabs as shown in the illustration.

Tighten the screws to a maximum torque of 2 Nm.

If continuous vibration is expected during operation, we recommend using threadlocker.

9.12 Installation with Flange

Use standard M4 screws for fastening. When screwing in the screws, be sure not to exceed the maximum screw-in depth of 7.7 mm into the thread. Screwing in too deeply can damage the housing

Screwing the screws in too deeply can damage the housing or the internal components.

Select the screw length according to the installation conditions .

9.13 Installation with 90° Stainless Steel Bracket for Wall and Ceiling Mounting

The optional 90° stainless steel bracket enables secure wall or ceiling mounting of the EOS sensor. The sensor is secured to the mounting adapter using four M4x10 screws.

The mounting adapter is attached to the threaded holes provided for this purpose on the back of the sensor. Ensure that all screws are tightened evenly to ensure a stress-free installation.

The stainless steel bracket can then be secured to the desired mounting surface using suitable M8 screws and appropriate fastening materials. The selection of fastening materials depends on the nature of the wall or ceiling structure.

During installation, ensure that the sensor is in the intended measurement position and that the detection range is not obstructed by structural components or other objects .

10. Commissioning and Configuration

10.1 Commissioning and Configuration of the Sensor via BLE

1. All Eos variants can be activated via BLE using a smartphone. To do so, simply use our LinOs app from Sentinum GmbH, which you can find in the App Store or Google Play Store .
2. Activate the sensor by briefly triggering the lower-left Hall sensor (M1) with a magnet for at least 2 seconds. The sensor should now emit a series of beeps. Advertising mode will then start automatically.
3. You can now conveniently control the sensor via BLE from your device. Make sure that Bluetooth is turned on on your phone and that you are within range of the sensor to be able to connect to and control it.

10.2 Audible Signal and Flashing Pattern

• When the device is turned on, an audible signal sounds, consisting of several rising tones. This sequence of tones indicates that the sensor has been successfully activated.
• When the device is turned off, several descending tones are played, which acoustically confirm that the device is shutting down.
• When establishing or disconnecting a Bluetooth (BLE) connection, the sensor also emits an audible signal that confirms the connection status.
• There are also flashing codes described in the following table .

11. Flap Opening Detection with Accelerometer and Tilt Detection

The Apollon sensor is equipped with an integrated 3-axis accelerometer of the type used for the reliable detection of changes in motion and orientation. One of the key functions of this sensor is the detection of the opening of flaps, lids, or housings, as typically found in industrial applications.

1. Position Detection in Standby Mode:
   • When the flap is closed, the sensor is in a defined, stable position.
   • The LIS2DTW12 continuously measures acceleration along the X, Y, and Z axes.
   • The so-called static acceleration (caused primarily by Earth's gravity) allows the absolute position of the flap to be uniquely determined.
2. Change in tilt or movement:
   • When the flap is opened or moved, the sensor's orientation in space changes.
   • The sensor detects this change through a significant deviation in the measured acceleration values on at least one axis.
   • This change is interpreted as a trigger event.
3. Threshold-based detection:
   • In the Apollon's firmware setup, a tilt angle or motion threshold can be defined (e.g., a change of 15, not ultra-low power mode)
   • As soon as the measured values exceed this threshold, a flap opening event is registered.

4. Optional: Interrupt-controlled operation:
   • The sensor supports low-power modes triggered by interrupts.
   • This means that the sensor remains in a power-saving state and only triggers an interrupt to the microcontroller when motion is detected—ideal for extending battery life.
   • Disadvantage: The angle cannot be adjusted and is fixed at 65°.

5. Event processing and data transmission:
   • After an opening is detected, the event is logged in the internal memory.
   • Depending on the configuration, a data packet can be sent immediately via LoRaWAN, BLE, or another network protocol to report the event.

Advantages of this method

• No mechanical components required (compared to reed or magnetic switches)
• Insensitive to magnetic field interference
• Easy retrofitting or customization via software parameters

12. Communication with the Interface

Detailed information on configuring sensor communication, including join behavior, can be found—depending on the version—in the respective generic LoRaWAN® , Mioty® or Cellular (NB-IoT and LTE-M1) documentation.

Furthermore, you can find all documents related to the generic documentation at https://docs.sentinum.de/wichtig-produktübergreifende-dokumentation-für-sensoren .

12.1 LoRaWAN Join Behavior

Before telemetry data can be sent via LoRaWAN, the device must establish a connection to the network. To do this, the device sends join requests until a join accept is successfully received.

As a compromise between power consumption and a rapid join, the transmission intervals for the join requests gradually increase. In addition, the data rate is varied (initially a high data rate or small spreading factor, then a lower data rate or larger spreading factor).

The join behavior strictly adheres to the requirements and recommendations of the LoRa Alliance specification. Sentinum sensors implement these requirements through so-called join bursts, the intervals between which increase.

A join burst consists of a maximum of 6 join requests with a decreasing data rate (DR5–DR0) or increasing spread factor (SF7–SF12).

The intervals between requests increase quadratically to ensure compliance with the LoRa Alliance's specific duty cycle guidelines.

The LoRa Alliance mandates a decreasing duty cycle for join requests according to the following table:

Time Duty Cycle <1h 1% <11h 0.1%

This means that in the first phase (<1h), exactly as much transmission budget is available as in the second phase (<11h), even though only one-tenth of the time is available.

To make maximum use of the budget, the intervals between join bursts (consisting of a maximum of 6 join requests) are initially short and then become longer.

Specifically, 2 bursts are performed in Phase 1. In Phase 2, 2 additional bursts are performed; starting in Phase 3, 1 burst per day is performed.

The duration of the bursts increases from approximately 10 minutes in Phase 1, to approximately 100 in Phase 2, up to 16 hours in Phase 3.

12.2 Mioty Join Behavior

Before telemetry data can be sent via mioty, the device must establish an initial communication link with the base station.

An explicit join process, as required by LoRaWAN, is not necessary. Instead, the device immediately begins transmitting so-called telegrams, which consist of 512-bit data packets that are in turn fragmented into up to 12 subpackets and distributed across different frequencies and time slots (telegram splitting).

The first successful delivery of a telegram with a valid device ID is interpreted by the backend as joining the network.

The device's configuration (e.g., Device ID, Application Key) is defined in advance and must match the backend's settings.

If no confirmation is registered in the backend (e.g., due to missing reception timestamps or missing evaluation results), the device begins retrying the transmission.

These retries occur in so-called mioty transmission cycles. The cycle duration increases progressively from an initial 5 minutes (after the first attempt), through 30 minutes, up to 12 hours, to comply with duty cycle specifications (<1%) while simultaneously minimizing energy consumption.

The transmission frequencies (868.0–868.6 MHz in Europe) and channels are cyclically switched to avoid multiple collisions.

The device does not actively change the data rate, as this is specified by the protocol (15.625 kbit/s for the uplink, optionally 4.882 kbit/s for the downlink).

The telegrams are resistant to interference because, upon reception, only 3 out of 12 subpackets need to be received correctly (Forward Error Correction).

A complete transmission attempt consists of a telegram with 12 subpackets lasting approximately 1.2 seconds (including guard time).

Upon successful registration, the device switches to a regular operating mode with fixed transmission intervals.

If no reception occurs after several transmission cycles (typically 10–12), the device pauses for 24 hours before a new initialization attempt is initiated.

12.3 Cellular Join Behavior (NB-IoT and LTE-M1)

Before telemetry data can be transmitted via cellular (NB-IoT or LTE-M1), the device must perform the standardized network join procedure according to 3GPP (Release 13 and later).

To do this, the device first scans the LTE frequency range (e.g., Band 8 or Band 20 for Europe) and searches for available cells.

After successful synchronization (PSS/SSS) and decoding of the System Information Block (SIB), the device initiates the attach process.

This process includes an RRC Connection Request, NAS Authentication, Security Setup, and the establishment of a PDP or PDU context (APN, IP address).

If the initial network attachment fails (e.g., due to no reception, rejected authentication, or no PDU context), a retry cycle begins.

The retry cycles are subject to an exponential backoff: After the first failure, the next attempt occurs after approximately 15 seconds, followed by 60 seconds, 5 minutes, and up to 6 hours.

The maximum number of join attempts per day is limited by the carrier, e.g., to 6 or 8 attempts.

The cellular modems strictly adhere to the 3GPP and GSMA guidelines for network access control (Access Control Mechanism).

Both NB-IoT and LTE-M1 use Coverage Enhancement Levels (CE Levels 0–2) to ensure successful connection even in areas with poor reception.

At CE Level 2, a message can be transmitted with up to 2,048 retransmissions.

Data rates vary significantly: NB-IoT typically operates at up to 250 kbit/s in the uplink and 26 kbps in the downlink, while LTE-M1 achieves uplink rates of up to 1 Mbit/s.

The connection duration depends on the network status and, in the worst-case scenario (CE Level 2 + backoff), can last several hours.

To reduce energy consumption, cellular devices employ power-saving mechanisms after a successful join:

• PSM (Power Saving Mode): The device remains in power-saving sleep mode for several hours or days and only registers itself again at the time of the next scheduled transmission.
• eDRX (Extended Discontinuous Reception): The device checks for downlink messages only at specified intervals (e.g., every 20 minutes to 3 hours).

If no network is found, the device stops its search after 60 minutes at the latest and enters a deep sleep state for several hours. Only then does a new network search and join cycle begin. This behavior is optimized by the manufacturer and is based on recommendations from network operators as well as requirements for high energy efficiency in mass IoT deployment.

13. Maintenance and Cleaning

To ensure that the sensor functions reliably and has a long service life, it should be maintained regularly. Please observe the following instructions:

• Clean the housing, especially the sensor's ventilation slots, with a dry or slightly damp microfiber cloth. Make sure that no moisture enters the device.
• Clean the device regularly, especially in dusty or pollen-rich environments, to ensure the sensor's long-term functionality.
• Do not use cleaning agents containing alcohol or solvents, as these can damage the sensor's surface.
• Do not use compressed air or other aggressive cleaning methods, as these can damage sensitive sensor components.
• Hard deposits (e.g., limescale, oil, or grease) can impair measurement accuracy. If necessary, clean the sensor promptly using a soft, damp cloth and a mild cleaning agent.
• For optical or radar-based sensors, the lenses or antenna surfaces should be checked regularly for dirt or scratches.
• Regularly check that the sensor and its mounting are securely fastened.

14. Battery Replacement and SIM Card Replacement

15. Inserting SIM Cards

16. Marking and Certification