Rev. 1.34

The document describes encryptions related to LoRaWAN® payloads. Relevant chapters per product of interest are marked with a cross “X”.

1. UPLINK MESSAGES from END-DEVICES

2. DOWNLINK MESSAGES to END-DEVICES

The device, after sending the message, waits for the time sync answer (2.1 TIME SYNC ANSWER).If nothing received, il will try sendind 3 more downlinks.

You have to reply before the 4th uplink.

Time sync reply must be sent after a time sync request (starting with 01), otherwise it will be ignored.

If error persists, it will try again after one week. If it receives the right answer, it aligns the internal clock and a new sync message will be sent after a week to overcome real time clock drift.

If not handled in the right way can cause a unnecessary battery consumption.

Example
message after a power-on:
01787d3c250002000203 01

Uplink ID 01 = Time Sync request
Sync ID 787d3c25 = ID of this Sync Reuest
Sync Version 000200 = Major and minor version and build
Application typ 0203 = MCF-LW06485
Option 01 = bit 0 set: first message after boot

message during a power down (only for MCF-LW06xxx family class C):
014e7d3c25000200020302

HOME

The 10 bytes for each measurement are divided as follows:

• 4 bytes LSB are for the date and time. The MSB (most significant byte) is on the right so they must be read from the right. The 4 byte in reverse order are as follows:
  • 7 bit for the offset of the year, starting from the year 2000
  • 4 bit per month
  • 5 bit for day of the month
  • 5 bits for hour
  • 6 bits for minutes
  • 5 bits for half the seconds. The seconds range is from 0 to 31, so the result should be multiplied by 2 to find the actual seconds of the measurement.

• 2 bytes LSB for temperature. The temperature is represented by a signed integer with the least significant byte first. The temperature is expressed in hundreds of a °C degree.
• 1 byte for humidity. Relative humidity is an unsigned integer corresponding to twice the percentage of humidity.
• 3 bytes LSB for pressure. Pressure is an unsigned integer with the least significant byte first; it is expressed in Pascal.

Example Sample payload: 04dc7e3721b40a47608801dd7e3721b10a43608801e07e3721b20a425d8801 Remove the first byte and divide the other 30 into 3 parts by 10 byte that correspond to 3 measurements. <color green>The 3 measurements will be:

• dc7e3721b40a47608801
• dd7e3721b10a43608801
• e07e3721b20a425d8801

Decipher the first measurement dividing it by groups and applying the necessary transformations:

• Measurement date: dc 7e 37 21
  • Byte swapping, result: 21 37 7e dc
  • The result in bits will be: 00100001 00110111 01111110 11011100
    • The bits are divided as explained above
      • Year: 0010000
        • Result: 16
          • 2000+16 = 2016
      • Month: 1001
        • Result: 9
      • Day: 10111
        • Result: 23
      • Hour: 01111
        • Result: 15
      • Minutes: 110110
        • Result: 54
      • Seconds: 11100
        • Result: 28
          • 28*2 = 56
  • The date of the measurement will be: 23/09/2016 15:54:56.
• Temperature: b40a
  • Byte swapping, result: 0ab4
    • The result (with sign) will be +2740 with two decimal places, then + 27.40 °C.
• Humidity: 47
  • In decimal is 71, the humidity is 71/2 = 35.5% rH.
• Pressure: 608801
  • Byte swapping, result: 018860
    • In decimal, the result is 100448, with two decimal places the pressure is 1004.48 hPa

HOME

HOME

The recurrent message of metering end-nodes is as follows:

After a message of metering request (2.5 METERING REQUEST), or enabled on the sensor, the uplink is as follows:

HOME

This uplink format is for 32 inputs and 32 outputs. Relevant bits depend on the device part number and its I/O capability.

In case of EGK-LW22PLG, the input status represents the status of the mains (1 for mains present, 0 for mains not present).

In case of MCF-LW12VOC or MCF-LW12CO2 with thresholds enabled, the input status represents the status of the measure (1 if over T+, 0 if under T-).

In case of MCF-LW12CO2E with thresholds enabled, the inputs 0 to 2 represents the led status (Input 0 = red, Input 1 = yellow, input 2 = green).

In case of EGK-LW20L00 and EGK-LW20W00, with accelerometer enabled, the inputs 0 represents the accelerometer status (Input = 1 start of accelerometer event start, input = 0 end of accelerometer event).

HOME

Report ID for MCF-LW06485:

• 1Y for recurrent data;
• 4Y for data received after a 0x8 serial data downlink;
• 5Y for recurrent data with error;
• 6Y for data received after a 0x8 serial data downlink with error.

The ModBus frame consists of at least 3 bytes.

In case of success (1Y/4Y), the first two bytes (us16 LSB) indicate the length (including the two bytes) and the remaining bytes is the data read from the peripheral Modbus device(s).

In case of error (5Y/6Y), the first two bytes (us16 LSB) indicate the length (including the two bytes) and the remaining bytes is the data successfully read from the peripheral Modbus device(s) before the error, and the last byte is the type of error:

• 0x05 configuration error
• 0x07 error reading internal configuration
• 0x7F ModBus command not implemented
• 0xCC communication error

For backwards compatibility in case of error, it will also return 0200XX where XX indicates the type of error:

• 0x05 configuration error
• 0x07 error reading internal configuration
• 0x7F ModBus command not implemented
• 0xCC communication error

Only for MCF-LW06485B

Report:

• 7Y for recurrent data;
• 8Y for data received after a 0x8 serial data downlink;
• 9Y for recurrent data with error;
• AY for data received after a 0x8 serial data downlink with error.

The ModBus frame consists of at least 4 bytes.

In case of success (7Y/8Y), the first two bytes (us16 LSB) indicate the length (including the two bytes) and the remaining bytes is the data read from the peripheral Modbus device(s). Last byte is the battery percentage.

In case of error (9Y/AY), the first two bytes (us16 LSB) indicate the length (including the two bytes) and the remaining bytes is the data successfully read from the peripheral Modbus device(s) before the error, then the type of error:

• 0x05 configuration error
• 0x07 error reading internal configuration
• 0x7F ModBus command not implemented
• 0xCC communication error

and as last byte the battery percentage.

Example

Sample payload:
0b10000a00be87424808010000 Uplink ID: 0b Report ID: 10 (recurrent data) Frame ID: 00

Data: 0a00be87424808010000

• Byte 1…2: 0a00 (LSB) → 0x000a data length
• Byte 3…10: be87424808010000 data content

The Davis weather station frame is made up of at least 4 bytes. In the event of an error it returns XXYYZZZZ , where XX indicates the data version, YY the type of error, ZZZZ the size of the read data.

Error type (YY):

• A0 to A7 = no answer
• CB = data format error
• 22 = CRC error
• 19 = Davis type error

If case of successful reading of weather data, the data sequence will be as in the following table (data with more than 1 bytes is LSB):

Examples of Forecast icons:

Refer first to Note 3. In addition are PM readings are on a separate uplink. The field “Data”, in case of success, is as follow:
* 4 bytes LSB are for the date and time (as per Note 1)

• 6 bytes LSB are for PM measures: 2 bytes for each measurement, formatted as LSB, reporting in order PM1.0, PM2.5 and PM10 in µg/m3
• 6 bytes LSB (if present) are for PM measures: 2 bytes for each measurement, formatted as LSB, reporting in order PM1.0, PM2.5 and PM10 in #/cm3.

The 17 (23) bytes of Data are divided as follows:

• 4 bytes LSB are for the date and time. The MSB (most significant byte) is on the right so they must be read from the right. The 4 byte in reverse order are as follows:
  • 7 bit for the offset of the year, starting from the year 2000
  • 4 bit per month
  • 5 bit for day of the month
  • 5 bits for hour
  • 6 bits for minutes
  • 5 bits for half the seconds. The seconds range is from 0 to 31, so the result should be multiplied by 2 to find the actual seconds of the measurement.
• 2 bytes LSB for temperature. The temperature is represented by a signed integer with the least significant byte first. The temperature is expressed in hundreds of a °C degree.
• 1 byte for humidity. Relative humidity is an unsigned integer corresponding to twice the percentage of humidity.
• 3 bytes LSB for pressure. Pressure is an unsigned integer with the least significant byte first; it is expressed in Pascal.
• 6 bytes LSB are for PM measures: 2 bytes for each measurement, formatted as LSB, reporting in order PM1.0, PM2.5 and PM10 in µg/m3.
• 1 byte (if present) for battery percentage.
• 6 bytes LSB (if present) are for PM measures: 2 bytes for each measurement, formatted as LSB, reporting in order PM1.0, PM2.5 and PM10 in #/cm3.

Example
Sample payload:
0b3a006caf51266409338b8701170022002a0063

Uplink ID: 0b
Report ID: 3a
Frame ID: 00
Data: 6caf5126 6409 33 8b8701 1700 2200 2a00 63
* date and time are: 6c af 51 26

• Byte swapping, result: 26 51 af 6c
• The result in bits will be: 00100110 01010001 10101111 01101100
  • The bits are divided as explained above
    • Year: 0010011
      • Result: 19
        • 2000+19 = 2019
    • Month: 0010
      • Result: 2
    • Day: 10001
      • Result: 17
    • Hour: 10101
      • Result: 21
    • Minutes: 111011
      • Result: 59
    • Seconds: 01100
      • Result: 12
        • 12*2 = 24
  • The date of the measurement will be: 17/02/2019 21:59:24.
• Temperature: 6409
  • Byte swapping, result: 0964
    • The result (with sign) will be +2404 with two decimal places, then +24.04 °C.
• Humidity: 33
  • In decimal is 51, the humidity is 51/2 = 25.5% rH.
• Pressure: 8b8701
  • Byte swapping, result: 01878b
    • In decimal, the result is 100235, with two decimal places the pressure is 1002.35 hPa.
• PM1: 1700
  • Byte swapping, result: 0017
    • In decimal, the result is 23, the PM1 value is 23 µg/m3.
• PM2.5: 2200
  • Byte swapping, result: 0022
    • In decimal, the result is 34, the PM1 value is 34 µg/m3.
• PM10: 2a00
  • Byte swapping, result: 002a
    • In decimal, the result is 42, the PM1 value is 42 µg/m3.
• Battery: 63
  • In decimal, the result is 99, the battery value is 99%.

HOME

The first 10 bytes for each measurement are the same as defined in Note 1, the following 4 bytes are as follows:

• 2 bytes LSB for illuminance. Luminance is represented by an unsigned integer with the least significant byte first. The Luminance is reported in lux (lx).
• 2 bytes LSB for VOC (Volatile organic compounds). The VOC level is reported according to setup of the device made with LoRaTool APP, as unsigned with the least significant byte first:
  • index (IAQ - indoor air quality) between 0 (clean air) and 500 (heavily polluted air)
  • bVOC value between 499ppb (clean air) and 50000ppb (heavily polluted air)

The first 10 bytes for each measurement are the same as defined in Note 1, the following 5 bytes are as follows:

• 2 bytes LSB for illuminance. Luminance is represented by an unsigned integer with the least significant byte first. The Luminance is reported in lux (lx).
• 3 bytes LSB for VOC (Volatile organic compounds). The VOC level is reported according to setup of the device made with LoRaTool APP, as unsigned with the least significant byte first:
  • index (IAQ - indoor air quality) between 0 (clean air) and 500 (heavily polluted air)
  • bVOC value between 499ppb (clean air) and 16700000ppb (heavily polluted air)

HOME

Data are as follow: 4 bytes are for the date and time (as per Note 1)

• 8 byte for measurements, 2 byte for each measurement, formatted as LSB with the following meaninging:
• Bit 0..11: measured value, to be rescaled according to the type
• Bit 12: equal to 1 if error: if the measured value is 0 meanings sensor disconnected (4-20mA only); greater or equal to 0xF00 it is a generic measurement error
• Bit 13..14: measure type:
  • 0: 4-20 mA
  • 1: 0-10 V
  • 2: 0-5 V
• Bit 15: RFU
• 1 byte (optional) for battery percentage, only for MCF-LW06420B, MCF-LW06010B, MCF-LW06424B.

HOME

Data are as follow:

• The first 14 bytes for each measurement are the same as defined in Note 5
• Following 2 bytes LSB are for CO2. CO2 concentration is represented by an signed integer with the least significant byte first. The CO2 is expressed in ppm.

Data are as follow:

• The first 15 bytes for each measurement are the same as defined in Note 5A
• Following 2 bytes LSB are for CO2. CO2 concentration is represented by a signed integer with the least significant byte first. The CO2 is expressed in ppm.

HOME

Data are as follow:

• 4 bytes for the date and time (as per Note 1)
• 1 byte for communication status:
  • Bit 0 (mask 0x01): equal to 1 is communication with the reader is OK
  • Bit 4 (mask 0x04): equal to 1 if card present

If card present, data frame also contains:

• 1 byte card identifier: equal to 0x01 for ISO14443 type
• 1 byte for UID legth
• 1 byte for SAK number
• n byte for UID

Example
Sample payload:
0f006caf512611010408447b8043
Uplink ID: 0f
Type: 00

Date and time: 6caf5126
* The date of the measurement will be: 17/02/2019 21:59:24. Communication status: 11

• bit 0 = 1 (communication OK), bit 4 = 1 (card present)

Card identifier: 01 UID Length: 04 SAK byte: 08 UID: 447b8043

—————

HOME

Type 1: 2 bytes LSB per input counter (inputs 1 to 16).

Type 2: 30 byte for 5 measures (6 byte for every measure, 4 bytes date and time as defined in Note 1, 2 bytes LSB for counter value) and 1 byte (optional) for battery percentage.

Type 1: 4 bytes for the date and time, 2 bytes LSB for frequency value (base 0.1Hz), 1 byte (optional) for battery percentage.

Type 2: 4 bytes for the date and time, 2 bytes LSB for frequency value (base 0.1Hz), 2 bytes LSB for input counter, 1 byte (optional) for battery percentage.

Output counters: 1 bytes per output counter (inputs 1 to 8). Counter increases every ON to OFF or OFF to ON cycle.

Output remaining time: XX YY YY YY YY
XX 1 bytes for output number (n output - 1)
YY YY YY YY 4 bytes uLSB remaining time

Output full status data (15 byte):

HOME

Data Option is LSB and formatted as follow:

• Bit 0..11: index of the first byte of the current frame
• bits 12…15:
  • 0x0 standard payload
  • 0x8 last frame of the buffer
  • 0x4 one BUFFER DOWNLINK frame missing, offset reports the expected one
  • 0x2 BUFFER DOWLINK frame too big, exceeds internal buffer
  • 0xE full buffer successfully saved (only after 0xC downlink type)

Data received from the device are buffered and sent via LoRa starting with index 0. Maximum data length is 1024 bytes. Empty data means receiving errors on RS232.

Example

Sample payload:
1100000103F4000400010324010400010334010400010366010200010376010200010380
1121000102000103880102000103900102000103A8010200FF6604000000020301000700
114280000000000000

Uplink ID: 11
Data option: 0000

• Bit 0…11:0x000 first byte index = 0
• Bit 12…15: 0x0 standard payload

Data: \\0103F4000400010324010400010334010400010366010200010376010200010380 Uplink ID: 11
Data option: 2100

• Bit 0…11:0x021 first byte index = 33
• Bit 12…15: 0x0 standard payload

Data: \\0102000103880102000103900102000103A8010200FF6604000000020301000700
Uplink ID: 11
Data option: 4280

• Bit 0…11:0x042 first byte index = 66
• Bit 12…15: 0x8 last frame of the buffer

Data: 0000000000000

HOME

In case the sensor’s frame length is too long for the selected datarate (eg. for AS923, US915 devices). This means a problem with LoRa coverage or with the position of the sensor. If the NS receive the 0xEE, it should try with a lower SF.

HOME

Frame lenght for each type:

Example Sample payload:
1403dc7e3721b20b8518d3025ff9082d278a0163

14 03 dc7e3721 b20b 8518 d302 5f f908 2d 278a01 63

The meaning is:

• Uplink ID 0x14
• Type 0x03. The device is a EGK-LW20WTxx
• Timestamp 0xdc7e3721
  • Byte swapping result: 21 37 7e dc
  • The result in bits will be: 00100001 00110111 01111110 11011100
    • The bits are divided as explained above
      • Year: 0010000
        • Result: 16
          • 2000+16 = 2016
    • Month: 1001
      • Result: 9
        • Day: 10111
          • Result: 23
    • Hour: 01111
      • Result: 15
        • Minutes: 110110
          • Result: 54
    • Seconds: 11100
      • Result: 28
        • 28*2 = 56

The date of the measurement will be: 23/09/2016 15:54:56.

• Battery voltage 0xb20b. Byte swapping result: 0x0bb2. The result (with sign) will be 2994 mV
• Height 0x8518, Byte swapping result: 0x1885. In decimal, the result is 6277mm
• Distance 0xd302, Byte swapping result: 0x02d3. In decimal, the result is 723mm
• Fill level % 0x5f, in decimal, the result is 95%
• Temperature 0xf908, Byte swapping result: 0x08f9. In decimal, the result is 2297 with two decimal places, meaning 22.97°C
• Humidity 0x2d, in decimal the result is 45, the humidity is 45/2 = 22.5% rH.
• Pressure 0x278a01. Byte swapping, result: 018a27. In decimal, the result is 100903, with two decimal places the pressure is 1009.03 hPa.
• Battery % 0x63. In decimal, the result is 99%.

HOME

Data are as follow:

Data are as follow:

• 1 byte is for thresholds enable:
  • Bit 0: enable threshold high channel 1
  • Bit 1: enable threshold low channel 1
  • Bit 2: enable threshold high channel 2
  • Bit 3: enable threshold low channel 2
  • Bit 4: enable threshold high channel 3
  • Bit 5: enable threshold low channel 3
  • Bit 6: enable threshold high channel 4
  • Bit 7: enable threshold low channel 4

• 2 bytes LSB for threshold:
  • Channel 1 threshold high +
  • Channel 1 threshold high -
  • Channel 1 threshold low +
  • Channel 1 threshold low –
  • .
  • .
  • Channel 4 Threshold low –

MCF-LW06420, MCF-LW06010 and MCF-LW06424: Thigh and Tlow in bit for every channel (up to 4)
MCF-LW12VOC: Thigh only for channel 1 for bVOC [IAQ/ppm]
MCF-LW12CO2: Thigh only for channel 1 for bVOC [IAQ/ppm], Thigh only for channel 2 for CO2 [ppm]
MCF-LW12CO2E: channel 1 for bVOC [IAQ/ppm], channel 2 for CO2 [ppm]

Data are as follow:

HOME

The 7 bytes for each measurement are divided as follows:

• 4 bytes LSB are for the date and time. The MSB (most significant byte) is on the right so they must be read from the right. The 4 byte in reverse order are as follows:
  • 7 bit for the offset of the year, starting from the year 2000
  • 4 bit per month
  • 5 bit for day of the month
  • 5 bits for hour
  • 6 bits for minutes
  • 5 bits for half the seconds. The seconds range is from 0 to 31, so the result should be multiplied by 2 to find the actual seconds of the measurement.

• 2 bytes LSB for temperature. The temperature is represented by a signed integer with the least significant byte first. The temperature is expressed in hundreds of a °C degree.
• 1 byte for humidity. Relative humidity is an unsigned integer corresponding to twice the percentage of humidity.

HOME

The 7 bytes for each measurement are divided as follows:

• 4 bytes LSB are for the date and time. The MSB (most significant byte) is on the right so they must be read from the right. The 4 byte in reverse order are as follows:
  • 7 bit for the offset of the year, starting from the year 2000
  • 4 bit per month
  • 5 bit for day of the month
  • 5 bits for hour
  • 6 bits for minutes
  • 5 bits for half the seconds. The seconds range is from 0 to 31, so the result should be multiplied by 2 to find the actual seconds of the measurement.

• 2 bytes LSB for temperature. The temperature is represented by a signed integer with the least significant byte first. The temperature is expressed in hundreds of a °C degree.
• 1 byte for humidity. Relative humidity is an unsigned integer corresponding to twice the percentage of humidity.
• 1 byte battery percentage. Battery percentage is an unsigned integer
• 1 byte for diagnostic. Diagnostic is 1 byte, bit masked:
  • bit 2: set if time sync expired - new time syncronization needed
  • bit 1: set if measure successfully sent
  • bit 0: set if measure sent, otherwise only logged

HOME

Date/time GMT in DOS format with epoch 2000. Sent as LSB. In bits, will be:

• 7 bits for year, starting from the year 2000
• 4 bits for month
• 5 bits for day in the month
• 5 bits for hour
• 6 bits for minutes
• 5 bits for half of seconds

Example

For date 23/09/2016 15:54:56:

• Year 2016 = bit 0010000
• Month 9 = bit 1001
• Day 23 = bit 10111
• Hour 15 = bit 01111
• Minutes 54 = bit 110110
• Seconds 56 ( / 2 = 28 ) = bit 11100

The sequence in bits is “00100001001101110111111011011100”, corresponding to the hexadecimal “21377edc”, which will be sent as LSB: dc 7e 37 21

HOME

HOME

If both the enable and the disable bit are equal to zero, the current status will be sent (I/O, input counters, output counters, frequency).

Example

Payload to set out#1

04000100000000000000

Downlink ID: 04 Option: 00 (IO message) Enable: 01000000 → 0x01 0x00 0x00 0x00 → u32 LSB → 0x00 0x00 0x00 0x01 → 0x01 → 00000001b (out #1)
Disable: 00000000 –> No output disable Payload to reset out#1

04000000000001000000

Downlink ID: 04
Option: 00 (IO message)
Enable: 00000000 –> No output enable
Disable: 01000000 → 0x01 0x00 0x00 0x00 → u32 LSB → 0x00 0x00 0x00 0x01 → 0x01 → 00000001b (out #1)

Payload to set out#1 for 5 seconds:

040001000000000000003200

0x04 = Downlink ID
0x00 = Io type
Enable: 01000000 → 0x01 0x00 0x00 0x00 → u32 LSB → 0x00 0x00 0x00 0x01 → 0x01 → 00000001b (out #1)
Disable: 01000000 –> No output disable

0x3200 = Ton output[1] 0x32 0x00 → LSB → 0x00 0x32 → 50 * 100ms → Ton[1] = 5s

Ton is mandatory only if you want to use the pulse feature Payload to set out#1 as normal and out#3 only for 1 second:

04000500000000000000000000000A00

0x04 = Downlink ID
0x00 = IO type
0x05000000 = Bit mask enable output 0x05 0x00 0x00 0x00 → u32 LSB → 0x00 0x00 0x00 0x05 → 0x05 → 00000101b → enable output[1]and output[3]
0x00000000 = Bit mask disable output–> No output disable
0x0000 = Ton output[1] 0x00 0x00 → LSB → 0x00 0x00 → 0 → 0 means infinite (as a normal output)
0x0000 = Ton output[2] 0x00 0x00 → LSB → 0x00 0x00 → 0 → 0 means infinite (as a normal output), in this case unused but mandatory to fill the space
0x0A00 = Ton output[3] 0x32 0x00 → LSB → 0x00 0x0A → 10 * 100ms → Ton[3] = 1s

HOME

HOME

HOME

Only for MCF-LW12xxx environmental sensors.

HOME

Data are as follow:

• 1 byte is for thresholds enable:
  • Bit 0: enable threshold high channel 1
  • Bit 1: enable threshold low channel 1
  • Bit 2: enable threshold high channel 2
  • Bit 3: enable threshold low channel 2
  • Bit 4: enable threshold high channel 3
  • Bit 5: enable threshold low channel 3
  • Bit 6: enable threshold high channel 4
  • Bit 7: enable threshold low channel 4

• 2 bytes LSB for threshold:
  • Channel 1 threshold high +
  • Channel 1 threshold high -
  • Channel 1 threshold low +
  • Channel 1 threshold low –
  • .
  • .
  • Channel 4 Threshold low –

MCF-LW06420, MCF-LW06010 and MCF-LW06424: Thigh and Tlow in bit for every channel (up to 4)
MCF-LW12VOC: Thigh only for channel 1 for bVOC [IAQ/ppm]
MCF-LW12CO2: Thigh only for channel 1 for bVOC [IAQ/ppm], Thigh only for channel 2 for CO2 [ppm]
MCF-LW12CO2E: channel 1 for bVOC [IAQ/ppm], channel 2 for CO2 [ppm]

MCF-LW12PLG: Thigh only for channel 1 for Power [W]

EGK-LW22PLG: Thigh only for channel 1 for Power [W]

EGK-LW22CCMxx: channel 1 for temperature [°C/100], channel 2 for RH [%*2]

HOME

Data sent to the device are buffered starting with index 0 and sent on the serial port after the last frame.

Data Option is LSB and formatted as follow:

• Bit 0..11: index of the first byte of the current frame
• bits 12..15:
  • 0x0 standard payload
  • 0x8 last frame of the buffer
  • 0xC last frame of the buffer, data has to be saved into the enginko sensor (i.e. Modbus configuration table)
  • 0xD last frame of the buffer, data has to be saved into the enginko sensor (i.e. time schedule table)
  • 0x4 one BUFFER DOWNLINK frame missing, offset reports the expected one

Maximum data length is 1024 bytes.

Example

Sample payload:

0500000103F4000400010324010400010334010400010366010200010376010200010380
0521000102000103880102000103900102000103A8010200FF6604000000020301000700
054280000000000000

* Downlink ID: 05
* Data option: 0000

• Bit 0…11:0x000 first byte index = 0
• Bit 12…15: 0x0 standard payload

Data: 0103F4000400010324010400010334010400010366010200010376010200010380

Downlink ID: 05
Data option: 2100

• Bit 0…11:0x021 first byte index = 33
• Bit 12…15: 0x0 standard payload

Data: 0102000103880102000103900102000103A8010200FF6604000000020301000700

Downlink ID: 05
Data option: 4280

• Bit 0…11:0x042 first byte index = 66
• Bit 12…15: 0x8 last frame of the buffer

Data: 0000000000000

HOME

HOME

Only for MCF-LW06DAV and MCF-LWWS0x

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

HOME

• Start [mm]: starting point of the measurement (in mm from “REFERENCE” point).
  • Option = 1B
  • Value: 2 byte (u16 LSB)

• End [mm]: Range of measure (in mm, from “REFERENCE” point) - from FW version 2.89.
  • Option = 1C
  • Value: 2 byte (u16 LSB)

• Lenght [mm]: Range of measure (in mm, from “Start” point) - up to FW version 2.88.
  • Option = 1C
  • Value: 2 byte (u16 LSB)

• Signal threshold: Minimum target detection threshold.
  • Option = 1D
  • Value: 2 byte (s16 LSB)

• Power: power setting for target detection.
  • Option = 1E
  • Value: 1 byte (values can be set from 1 to 5)

• Sort: data sorting.
  • Option = 1F
  • Value: 1 byte (values can be set from 0 to 3)

• Algorithm: type of analysis.
  • Option = 20
  • Value: 1 byte (values can be set from 0 to 255)

(from FW version 00.02.69)

HOME

HOME

Start and Stop data are as follow:

• 1 byte for the offset of the year, starting from the year 2000
• 1 byte per month
• 1 byte for the day of the month
• 1 byte for hour
• 1 byte for minutes

HOME

HOME

HOME

HOME

Rev. 1.36