Apollon-Q T/R/TR NFC and Downlink Description
Are you looking for the Apollon-Q T/R/TR NFC and downlink description?
| Module | Module key | Group | Group ID | Description | T | R | TR | SW |
|---|---|---|---|---|---|---|---|---|
| Apollon | 0x1XXX |
Timings & Alarms | 0x00 |
Defines parameters for measurements and transmission behavior | ✓ | ✓ | ✓ | ✓ |
| Apollon | 0x1XXX |
ToF | 0x01 |
ToF Sensor Settings | ✓ | ✓ | ✓ | |
| Apollon | 0x1XXX |
Radar | 0x02 |
Radar Sensor Settings | ✓ | ✓ | ✓ | |
| Apollon | 0x1XXX |
Valve Opening Detection | 0x03 |
Accelerometer Settings | ✓ | ✓ | ✓ | ✓ |
| Apollon | 0x1XXX |
Motion and Vibration Detection | 0x04 |
Settings for motion tracking and vibration pattern detection | ✓ | ✓ | ✓ | ✓ |
- Radar preset during commissioning:
- Liquid (for liquid measurements):
tmod = 2– Example:S-XXXX-TR-ACC - Solid (for solids):
tmod = 0– Example:S-XXXX-SW-TR-ACC - When measuring bodies of water, ensure that water is flowing.
- FAQs can be found on the last page.
Tables for cross-product modules such as LoRaWAN, mioty, and Cellular can be found in the Generic NFC and Downlink Documentation .
For more information on configuring sensor communication, refer to the respective generic LoRaWAN®, ://docs.sentinum.de/generische-mioty?hsLang=de">mioty® or Cellular documentation, depending on the version.
APOLLON: Group Timings & Alarm 0x00 (T, R, TR, SW)
| Resource | Resource ID | Key (NFC/BLE) | Min | Max | Factory Setting | Unit | Module Key |
|---|---|---|---|---|---|---|---|
| Measurement period | 0x00 |
period |
1 | 660 | 60 | min | XXX1 |
| Specifies the interval at which measurements are taken. 60 minutes means that the sensor takes a measurement every 60 minutes. | |||||||
| Change in Absolute Level | 0x01 |
delta |
30 | 2000 | 200 | mm | XXX1 |
| Specifies the absolute change in the fill level compared to the last transmission that must occur in order to trigger an alarm transmission. This transmission is performed independently of the normal transmission interval. Always refers to the main measured value. | |||||||
| Regular transmission interval | 0x02 |
every / pause |
1 | 24 | 6 | XXX1 |
|
| Number of measurements performed prior to transmission. | |||||||
| Master Value Resource | 0x03 |
mval |
0 | 1 | 1 | XXX1 |
|
|
• 0: ToF corresponds to the ToF Algo resource • 1: Radar |
|||||||
| Temperature high | 0x04 |
thi |
0 | 100 | 70 | °C | XXX1 |
| Specifies the temperature at which a temperature alarm is triggered. | |||||||
APOLLON: TOF Settings Group 0x01 (T, TR, SW)
| Resource | Resource ID | Key (NFC/BLE) | Min | Max | Factory Setting | Unit | Module key |
|---|---|---|---|---|---|---|---|
| TOF algorithm resource | 0x02 |
algo |
0 | 2 | 2 | XXX1 |
|
|
Primary ToF algorithm: • 0: No histogram mode • 1: With histogram mode • 2: Advanced feature |
|||||||
Apollon: Radar Settings Group 0x02 (R, TR, SW)
| Resource | Resource ID | Key (NFC/BLE) | Min | Max | Factory Setting | Unit | Module Key |
|---|---|---|---|---|---|---|---|
| Minimum radar measurement distance | 0x00 |
rsta |
50 | 3000 | 150 | mm | XXX1 |
| Describes the minimum required distance at which a measurement is taken. | |||||||
| Maximum Radar Measurement Distance | 0x01 |
rend |
50 | 10,000 | 5,000 | mm | XXX1 |
| Describes the maximum distance up to which measurements are taken. | |||||||
| Radar Threshold | 0x02 |
rtre |
400 | 10,000 | 2000 | XXX1 |
|
Specifies the threshold value above which the sensor's signal peaks must lie in order to be detected (only for tmod=2).
|
|||||||
| Radar Sort Mode | 0x03 |
rsor |
0 | 2 | 0 | XXX1 |
|
|
Sets the sorting logic for detected targets: • 0: Strongest echo first • 1: Shortest distance first • 2: Farthest distance first |
|||||||
| Radar Wavelet Length | 0x04 |
wav |
1 | 5 | 2 | XXX1 |
|
| ADVANCED: Pulse Duration (Radar Pulse Duration), how long the signal is transmitted; selected automatically by the sensor. | |||||||
| Radar Range Threshold Mode | 0x05 |
tmod |
0 | 2 | 2: if Liquid is preset 0: otherwise |
XXX1 |
|
|
Mode for adjusting the threshold values: • 0: Phase Variance Mode for piece goods and Smart Waste • 1: Static Threshold Mode • 2: Dynamic Threshold Algorithm (CFAR) |
|||||||
| Radar RCS Threshold | 0x06 |
rcdt |
-10 | 40 | 0 | XXX1 |
|
| Threshold value for Static Threshold Mode. | |||||||
| Radar Signal Quality | 0x07 |
sq |
-10 | 30 | 10 | XXX1 |
|
Gain: The higher the sq value, the greater the distances that can be received. At the same time, power consumption increases.
|
|||||||
| Radar CFAR Sensitivity | 0x08 |
cfsn |
0 | 100 | 50 | XXX1 |
|
|
Sensitivity of the CFAR algorithm: • Higher sensitivity → more targets detected, but more false alarms • Lower sensitivity → fewer false alarms |
|||||||
| Radar CFAR Standard | 0x0F |
cfnr |
0 | 2 | 2 | XXX1 |
|
|
ADVANCED: Correction of RCS values for double reflections. • 0: No correction • 1: Mild correction (surfaces) • 2: Strong correction |
|||||||
Apollon: Accelerometer Group 0x03 (T, R, TR, SW)
| Resource | Resource ID | Key (NFC/BLE) | Min | Max | Factory Setting | Unit | Module Key |
|---|---|---|---|---|---|---|---|
| Decay time | 0x00 |
ocool |
1 | 600 | 120 | sec | XXX1 |
| Specifies a time interval in seconds during which another opening cannot be triggered again after an opening has been triggered (debouncing). The last counted opening serves as the reference value. | |||||||
| Alarm after | 0x01 |
oaaf |
60 | 3600 | 900 | sec | XXX1 |
| Specifies how long the lid must remain open, in seconds, before an alarm is triggered. | |||||||
| Alarm for Lid Detection | 0x02 |
osrc |
0 | 1 | 1 | XXX1 |
|
|
Enables or disables the opening alarm: • 0: disabled • 1: enabled |
|||||||
| Alarm for open flap | 0x04 |
oaen |
0 | 1 | 0 | XXX1 |
|
|
Specifies whether an alarm is triggered when a container remains open after the "Alarm after" time has elapsed: • 0: Alarm not active • 1: Alarm active |
|||||||
-
Either
Apollon Group 0x03orApollon Group 0x04can be used. Both groups activate each other and cannot be used simultaneously.
Apollon: Motion and Vibration Detection 0x04
| Resource | Resource ID | Key (NFC/BLE) | Min | Max | Factory Setting | Unit | Module Key |
|---|---|---|---|---|---|---|---|
| Move Mode | 0x00 |
lmode |
0 | 8 | 0 | 1111 |
|
|
Indicates which mode (Tracking on Activity mode or vibration detection) is enabled: • 0: Tracking on Activity feature is not active• 1: Tracking on Start – Location tracking is performed when an activity is detected.• 2: Tracking on Ongoing – Location tracking is performed during an activity that is already in progress.• 3: Tracking on Start and Ongoing – Location tracking is performed when an activity is detected and during an activity that is already in progress.• 4: Tracking on Inactivity – Location tracking is performed when an activity ends.• 5: Tracking on Start and Inactivity – Location tracking is performed when an activity is detected and when an activity ends.• 6: Tracking on Inactivity and Ongoing – Localization occurs when the activity is in progress and when the activity has ended.• 7: Tracking on Start, Inactivity, and Ongoing – Localization is performed when the activity starts, is in progress, and has ended.• 8: Vandalism detection and vibration pattern recognition.
|
|||||||
| Move Activity Threshold | 0x01 |
moat |
100 | 2000 | 400 | mg | 1111 |
|
Describes the acceleration threshold at which an event is counted and recorded as an activity. For vandalism detection ( Move Mode = 8), this is the threshold for a shock.
|
|||||||
| Move Ongoing Time | 0x02 |
Mon |
1 | 1440 | 10 | min | 1111 |
| Specifies the time that elapses between two transmissions and localizations while an activity is in progress. | |||||||
| Move Inactivity Time | 0x03 |
moit |
1 | 1440 | 5 | min | 1111 |
| Describes the time between when an activity ends and when the data is located/transmitted. | |||||||
| Move Impact Max | 0x04 |
miom |
1 | 1440 | 4 | 1111 |
|
Specifies the number of strikes or impacts. If this number is reached before the
Move Inactivity Time between strikes expires, a vandalism alarm is triggered.
|
|||||||
FAQ
1. "The sensor returns only a single echo and no further echoes. rd_2, ra_2, rd_3, ra_3 are 0."
This behavior is not a malfunction but is completely normal depending on the application or environmental conditions—and in many cases even desirable. In this case, the sensor has detected a clear, dominant target that reflects strongly enough to suppress all other possible echoes or classify them as irrelevant.
A single, stable echo means:
- High measurement reliability with a clear surface or homogeneous fill level
- Low interference reflections from tank walls, internal components, or surface structures
- Optimal conditions for reliable level or distance measurement
Only if multiple relevant echoes are expected (e.g., in the case of complex tank geometries or overhanging structures) and are consistently missing,
might it be advisable to check the sensor alignment, radar parameters, or environment.
For the "Smart Waste" setting (tmod = 0), only one echo is ever available, since the first detected object is recorded.
2. I would like to switch the sensor from the Smart Waste profile to the Liquid profile and back. How do I do that?
- "Smart Waste" or bulk solids profile:
tmod = 0 - Liquid profile:
tmod = 2
3. The sensor is detecting too many double reflections
Double reflections in radar (also known as multipath echoes or multipath reflections) occur when the radar signal does not return directly from the target but is reflected via detours, e.g., off walls, floors, tank structures, or internal components.
cfnr = 1cfnr = 2(in case of many double reflections)
4. The sensor shows no readings or "0" values
- Increase
cfsn - Increase
sq
If the sensor consistently fails to provide readings or constantly displays 0, there may be various causes. This behavior is not necessarily a defect but is often due to configuration- or environment-related factors:
- No target in the field of view
→ Check whether there is a reflective object within the configured range.
→ At very long distances or with poorly reflective surfaces (e.g., foam, open grating), the radar backscatter may be too weak. - Incorrect sensor alignment
→ The sensor may not be correctly aligned with the target surface (e.g., tilted or angled too much).
→ The main beam direction should be as perpendicular as possible to the target surface. - Inappropriate radar parameters
→ Check settings such as: radar filter type (e.g., for liquid or solid), sensitivity/gain, minimum and maximum range (r_min,r_max) - Interfering reflections or shadowing
→ Metal components, covers, grates, or proximity to walls can block the direct echo.
→ In this case, a valid measurement value may not be detected. - Data format or communication error
→ Make sure that the measurement data is being read and interpreted correctly.
→ A value of "0" can also mean: no valid measurement value received (depending on the protocol or data parser).
© Sentinum GmbH – All rights reserved.
All content in this document, including text, tables, and images, is protected by copyright and is the property of Sentinum GmbH.
All images are subject to the copyright of Sentinum GmbH, unless otherwise noted.
Reproduction, distribution, or use—even in part—is not permitted without express written permission.
Specifications are subject to change. All information is provided without warranty.