Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Connect to the device with the Lobaro Tool using the Lobaro Config Adapter
  2. Under Configuration click "Reload Config" and change the configuration according to your needs
  3. Register the device in your LoRaWAN network
  4. Connect ER34614 3.6V D-cell Battery via XH connector / Connect external powersupply

Key Features

  • Supports (tick) Supports up to 25 DS18x20 1-Wire sensors
  • 8(tick) 8-Port easy installation Hub available
  • IP67 (tick) IP67 outdoor housing with pressure compensating element
  • Comes (tick) Comes with one sensor attached
  • Sensor (tick) Sensor output order can be configured
  • Testmode (tick) Testmode for easy sensor identification
  • Big (tick) Big 19Ah size "D" battery for 10 years+ possible battery lifetime (not included)
  • LoRaWAN (tick) LoRaWAN 1.0.x and 1.1 network servers supported
  • LoRaWAN (tick) LoRaWAN Class A or Class C operation
  • LoRaWAN (tick) LoRaWAN 1.1 time synchronisation
  • Variant (tick) Variant with external power-supply and or external antenna available on request
  • Quick (tick) 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.

NameDescriptionTypeValues
OTAAActivation: OTAA or ABPbooltrue= use OTAA, false= use ABP
DevEUIDevEUI used to identify the Devicebyte[8]e.g. 0123456789abcdef
JoinEUIUsed for OTAA (called AppEUI in v1.0)byte[8]e.g. 0123456789abcdef
AppKeyKey used for OTAA (v1.0 and v1.1)byte[16]
NwkKeyKey used for OTAA (v1.1 only)byte[16]
SFInitial / maximum Spreading Factorint7 - 12
ADRUse Adaptive Data Ratebooltrue= use ADR, false= don't
OpModeOperation ModestringA= Class A, C= Class C
TimeSyncDays after which to sync timeintdays, 0=don't sync time
RndDelayRandom delay before sendingintmax seconds
RemoteConfNot supported by this firmwareboolfalse=deactivate
LostRebootDays without downlink before rebootintdays, 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.

namedescriptionexample value
TestModeRun device in Testing Mode to help identify sensors. Must be false for normal operations.true or false
MeasureCronCron expression defining when to read out sensors0 0/15 * * * *(every 15 minutes)
SendInternalTempToggle output of internal sensor. Will alway be sent first.true or false
SendSensorIdInclude Sensor ID in upload. Changes Payload format and Port.true or false
SensorIdOrderSemicolon 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.

temperaturehex valueerror condition
-899.0°C0xdce2Sensor not found (for sensors set in SensorIdOrder).
-997.0°C0xd90eCommunication timed out.
-998.0°C0xd904Temperature read out error.
-999.0°C0xd8faNo temperature value.


Sensor IDs

A complete sensor ID consists of 8 bytes:

...

Payload with temperature measurements when Sensor-ID is included.

Structure:

namelentypedescription
success1uint80 = Read error, 1 = Success
sensor id6uint8[6]6-Byte 1-Wire Sensor Id
temperature2int16 BETemperature 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:

namelentypedescription
success1uint80 = Read error, 1 = Success
temperature2int16 BETemperature 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.

...