Version 1.1 (2021-21-03)

This document describes the configuration possibilities of the IoT Sound Sensor, and also contains the decryption-logic in Javascript.
Tip: Press [F12] and watch console for detailed info.

The payload can be configured with the app, or with a downlink using the SensorTeam Dashboard+ system. Contact us for more info about downlink configuration possibilities.

This example shows the 'autonomic' parsing of the IoT SoundSensor payload. The exact sensor-configuration can be modified using the Android App.

The IoT SoundSensor has the following settings:

• LoRa settings: Device EUI, App EUI, App key, OTAA/ABP, ADR ON/OFF, Spreading Factor
• LoRa transmit interval: the time between LoRa-messages
• Number of measurements in payload: more than one measurement per LoRa-message is possible, of course dependent on the data enabled (see list below)
• GPS mode: OFF / ONCE (only at startup) / INTERVAL (1-12 hours)

Possible data per measurement:

• Message info (message type and description of the payload): Describes the configuration of the payload. Could be left blank (not recommended) when custom decryption-code is created. This example needs this value.
• dB(A) fast: dB(A) measurement with fast response
• dB(A) slow: dB(A) measurement with slow response
• dB(C) fast: dB(C) measurement with fast response
• dB(C) slow: dB(C) measurement with slow response
• Leq(A): dB(A) average over set Leq time. Between the current measurement and current measurement time minus Leq time
• Leq(C): dB(C) average over set Leq time. Between the current measurement and current measurement time minus Leq time
• Positive Peak Hold A: The highest dB(A) value in the period between previous measurement and current measurement
• Negative Peak Hold A: The lowest dB(A) value in the period between previous measurement and current measurement
• Positive Peak Hold C: The highest dB(C) value in the period between previous measurement and current measurement
• Negative Peak Hold C: The lowest dB(C) value in the period between previous measurement and current measurement
• Battery voltage: The battery voltage
• Location (latitude/longitude): The geolocation from onboard GPS
• Timestamp of first sample: Only applies if multiple measurements per LoRa-message is configured
• Timestamp of last sample: Only applies if multiple measurements per LoRa-message is configured

Note: The timestamp can be extracted from the uplink message from your provider (if they send it), but this is not so accurate. If you use the timestamp from the uplink message, you have to know the interval between the samples (for example hard-coded or from a database). Therefore we recommend to use the onboard GPS in combination with the 2 timestamp datatypes.

The payload of the example configuration is 320 bits (40 bytes) long (the payload description is also shown in the App):

| message info (16) | dB(A)f (10) | dB(A)s (10) | dB(C)f (10) | dB(C)s (10) | Leq(A) (10) | Leq(C) (10) | Pos.Peak(A) (10) | Neg.Peak(A) (10) | Pos.Peak(C) (10) | Neg.Peak(C) (10) | dB(A)f (10) | dB(A)s (10) | dB(C)f (10) | dB(C)s (10) | Leq(A) (10) | Leq(C) (10) | Pos.Peak(A) (10) | Neg.Peak(A) (10) | Pos.Peak(C) (10) | Neg.Peak(C) (10) | Bat (8) | Lat (32) | Lon (32) | first timestamp (16) | last timestamp (16) |

The 'message info' contains the type of the message and the configuration, what makes 'autonomic' parsing possible:
bit index | description
0 | Message type (2 bits)
1 | Message type (2 bits)
2 | dB(A) fast
3 | dB(A) slow
4 | dB(C) fast
5 | dB(C) slow
6 | Leq(A)
7 | Leq(C)
8 | Positive Peak Hold A
9 | Positive Peak Hold C
10| Negative Peak Hold A
11| Negative Peak Hold C
12| Battery voltage
13| Location
14| Timestamp of first sample
15| Timestamp of last sample