...
- Connect to the device with the Lobaro Tool using the Lobaro Config Adapter
- Under Configuration click "Reload Config" and change the configuration according to your needs
- Register the device in your LoRaWAN network
- Connect ER34614 3.6V D-cell Battery via XH connector / Connect external powersupply
Key Features
- Supports
Supports up to 25 DS18x20 1-Wire sensors
- 8
8-Port easy installation Hub available
- IP67
IP67 outdoor housing with pressure compensating element
- Comes
Comes with one sensor attached
- Sensor
Sensor output order can be configured
- Testmode
Testmode for easy sensor identification
- Big
Big 19Ah size "D" battery for 10 years+ possible battery lifetime (not included)
- LoRaWAN
LoRaWAN 1.0.x and 1.1 network servers supported
- LoRaWAN
LoRaWAN Class A or Class C operation
- LoRaWAN
LoRaWAN 1.1 time synchronisation
- Variant
Variant with external power-supply and or external antenna available on request
- Quick
Quick closing screws with cover retainer on housing
...
For a detailed introduction into how this values need to be configured, please refer to the chapter LoRaWAN configuration in our LoRaWAN background article.
Name | Description | Type | Values |
---|---|---|---|
OTAA | Activation: OTAA or ABP | bool | true = use OTAA, false = use ABP |
DevEUI | DevEUI used to identify the Device | byte[8] | e.g. 0123456789abcdef |
JoinEUI | Used for OTAA (called AppEUI in v1.0) | byte[8] | e.g. 0123456789abcdef |
AppKey | Key used for OTAA (v1.0 and v1.1) | byte[16] | |
NwkKey | Key used for OTAA (v1.1 only) | byte[16] | |
SF | Initial / maximum Spreading Factor | int | 7 - 12 |
ADR | Use Adaptive Data Rate | bool | true = use ADR, false = don't |
OpMode | Operation Mode | string | A = Class A, C = Class C |
TimeSync | Days after which to sync time | int | days, 0 =don't sync time |
RndDelay | Random delay before sending | int | max seconds |
RemoteConf | Not supported by this firmware | bool | false =deactivate |
LostReboot | Days without downlink before reboot | int | days, 0 =don't reboot |
Operation
Without configuration the sensors will be transmitted ordered by the 48 Bit id, ignoring the Sensorfamily prefix and the Checksum.
name | description | example value |
---|---|---|
TestMode | Run device in Testing Mode to help identify sensors. Must be false for normal operations. | true or false |
MeasureCron | Cron expression† defining when to read out sensors | 0 0/15 * * * * (every 15 minutes) |
SendInternalTemp | Toggle output of internal sensor. Will alway be sent first. | true or false |
SendSensorId | Include Sensor ID in upload. Changes Payload format and Port. | true or false |
SensorIdOrder | Semicolon separated list of 48 Bit IDs in hex (up to 25) | 22ffffff0000;44ffffff0000;11ffffff0000 |
† See also our Introduction to Cron expressions.
...
Temperature is transmitted in 10th of degrees Centigrade (d°C), to avoid having to deal with floating point numbers. Error conditions for individual sensors are transmitted as temperatures below -300°C.
temperature | hex value | error condition |
---|---|---|
-899.0°C | 0xdce2 | Sensor not found (for sensors set in SensorIdOrder ). |
-997.0°C | 0xd90e | Communication timed out. |
-998.0°C | 0xd904 | Temperature read out error. |
-999.0°C | 0xd8fa | No temperature value. |
Sensor IDs
A complete sensor ID consists of 8 bytes:
...
Payload with temperature measurements when Sensor-ID is included.
Structure:
name | len | type | description |
---|---|---|---|
success | 1 | uint8 | 0 = Read error, 1 = Success |
sensor id | 6 | uint8[6] | 6-Byte 1-Wire Sensor Id |
temperature | 2 | int16 BE | Temperature in 1/10 °C |
... | ... sensor id and temperature fields repeat ... |
When the total length of data exceeds 50 bytes, the message will be split and uploaded in multiple packets using this format.
...
Before v0.4.0 this format is sent on Port 2.
Structure:
name | len | type | description |
---|---|---|---|
success | 1 | uint8 | 0 = Read error, 1 = Success |
temperature | 2 | int16 BE | Temperature in 1/10 °C |
... | ... temperature field repeats ... |
When the total length of data exceeds 50 bytes, the message will be split and uploaded in multiple packets using this format.
...