TE connectivity A6XX1N Iot Wireless Pressure Sensor User Manual

TE connectivity A6XX1N Iot Wireless Pressure Senso

Specifications

• Doc#: 20027955-11
• Revision: 0.2
• Model: 69X1N

Global Overview

The IOT Wireless Pressure Sensor is a device that allows for wireless measurement and monitoring of pressure levels. It utilizes IoT technology to provide real-time data and offers various features for data processing and communication.

Measurement Process

The measurement process of the Wireless Pressure Sensor involves collecting pressure data from the environment. The sensor captures the pressure readings and sends them for further processing and analysis.

Data Process

The Wireless Pressure Sensor offers several data processing capabilities:

1. Delta: This feature calculates the change in pressure readings over time, allowing for the detection of pressure fluctuations.

2. Trig Measurement Command: This command triggers the sensor to take a measurement at a specific time or event.

3. Datalog Data: This feature enables the sensor to store pressure data in its internal memory for later retrieval.

4. Live Mode: In this mode, the sensor
   continuously streams real-time pressure data.

5. Threshold Event Manager: This feature allows the user to set thresholds for pressure levels and receive notifications or trigger actions when those thresholds are exceeded.

6. Sync between Different Sensors: The Wireless Pressure Sensor can synchronize data with other sensors, enabling the user to monitor pressure levels across multiple locations simultaneously.

Communication

The Wireless Pressure Sensor supports various communication methods:

Preliminary Phase: During 1 Hour After Power On

This phase focuses on the initial setup and connection establishment:

• BLE Behavior: The sensor behaves as a Bluetooth Low Energy (BLE) device during this phase.
• LoRaWAN & BLE Behavior: The sensor simultaneously operates in both LoRaWAN and BLE modes, allowing for different communication options.

Nominal Mode Phase: 1 Hour After Power On

In this phase, the sensor operates under normal conditions:

• Keep Alive: The sensor maintains its connection and ensures continuous communication.
• BLE: The sensor supports BLE communication during this phase.
• LoRaWAN: The sensor utilizes LoRaWAN technology for long-range wireless communication.
• BLE Connected Mode: This mode enables the sensor to establish a dedicated connection with a specific device for more advanced features.
• Special Event: Magnet: The sensor can detect the presence of a magnet as a special event and trigger specific actions.

BLE Communication

The Wireless Pressure Sensor offers various BLE communication features:

• BLE Connected Mode: This mode allows the sensor to establish a dedicated connection with a compatible device.
• Access to Connected Mode: The user can access the connected mode to retrieve real-time pressure data and perform advanced operations.

FAQ

Q: How long does the battery last?

A: The battery life depends on the usage and configuration settings. Under normal conditions, the battery can last up to X hours.

Q: Can I use multiple sensors simultaneously?

A: Yes, the Wireless Pressure Sensor supports synchronization between different sensors, allowing for simultaneous monitoring of pressure levels across multiple locations.

Q: How do I set the threshold for pressure levels?

A: The Threshold Event Manager feature allows you to set custom thresholds for pressure levels. Please refer to the user manual for detailed instructions on configuring thresholds.

Doc# 20027955-11 Revision 0.2

REVISIONS

GLOSSARY

• Sensor is the sensing element that transform physical value to voltage value. It could have digital or analog interface.
• Platform is the generic electronic and software used to acquire data and send data over RF communication.
• System is the combination of a sensor and the platform.
• Product is specific system.
• Single point: This is a category of sensor that provide only one data per measure. This category is pressure sensors.
  • Delta detection,
  • raw data.
• Threshold can be configured. User has to choose between data to feed threshold.
• If the system has LoRaWAN connectivity, it will use BLE for local configuration during 1 hour.
• LoRaWAN connectivity will be used to send sensor data periodically. Once configure and connected to LoRaWAN network downlink frame can be also used to configure the device.

The product has two Bluetooth modes:

• Advertisement Mode: provides data periodically and help to go to Connected Mode
• Connected Mode: mode for configuration and advanced features. Each advertisement allows the opportunity to user to switch to Connected mode. It’s the only way to go into connected mode.

MEASUREMENT PROCESS

Platform acquires digital data from the sensor. On acquisition chain system uses:

• Sensor power supplies: A separate power supply is used for the sensor at 2.8V
• A communication bus (I2C or SPI): It can read data from the memory of the sensor.(Data, Calibration, …)
• The system acquires and stores data.
• It applies sensitivity to the raw value

At every measurement interval, platform power up the sensor and ask a new acquisition and the sensor provides a data and temperature. Both data are stored.
When measurement interval is changed a new measurement is done when the new value is received by the system.

DATA PROCESS

DATA PROCESSING

Delta
Time domain data are used to calculate a variation between two data.

TRIG MEASUREMENT COMMAND
When BLE connected mode is activated, user can ask a new measure without waiting measurement interval.
After a Trig measurement command, the next measurement will happen after measurement interval.

DATALOG DATA
The system store in memory 4096 data. When the memory is full the oldest data store is replaced by the new one and so on.

Data stored in memory are available on BLE connected mode.
Last data store in memory will have index 0 whatever it location into memory.

LIVE MODE

• When connected mode is activated, user can get access to a live mode. It will acquire data at new measurement interval fixed at 100ms and provide all data to be available in “real time”.
• When user stop BLE connection the system come back to its current configuration and applies regular measurement interval.
• Note: if a threshold is reached during live mode the system will use Threshold measurement interval otherwise it uses standard measurement interval.

THRESHOLD EVENT MANAGER
Threshold event manager allows user to have a specific configuration when a value reach a level (main sensor and/or secondary sensor).

• Greater than/Lower Than Threshold: Every new acquired value is compared to a threshold.

• Actions: When a threshold is reached, the system will set a flag. This flag is available on advertisement frame. Upon user configuration the system can change advertisement mode and measurement interval. This configuration can be done on BLE connected mode.

• Behavior: This new configuration can last while the threshold is reached or until user clear Threshold flag. All this configuration can be done on BLE connected mode.

At configuration the user need to define:

• Data to consider: Main sensor and/or Secondary sensor
• Data to use: Raw data and/or Delta
• Threshold : Level and type: “greater than” or “smaller than”
• Event after threshold: Flag, Measurement interval, Advertisement mode

Every new acquired value is compared to a threshold. On threshold the sensor will do a specific action and behavior defined by user:

• Set up flags to inform customer that a threshold is reached
• Change BLE Advertisement mode (only on event mode activated) or Change LoRaWAN TX mode (only if LoRaWAN connectivity is available and event mode activated)
• Change measurement interval (only on event mode activated)

If there are conflict when several Threshold are reached:

• System will use the lowest measurement interval and at each new threshold reached or released a new configuration analysis will be done
• System will use first Periodic Mode and then On measure mode

SYNC BETWEEN DIFFERENT SENSOR
If the user configuration can manage multiple BLE connection, user can synchronize several sensors. To achieve that user has to:

• Activate connected mode on several sensor
• Send a Trig measurement command to all send.

All sensors will be synchronized with a resolution of 1s. All measurement will be done during the same timeslot.

COMMUNICATION

BLE advertisement frame will have the same format as BLE only system.
BLE provide 3 main state:

– Advertisement Mode: periodic data available
– Connected mode: advanced data analysis and sensor configuration
– Idle: low power mode with no activity

LoRaWAN communication can:

– Receive configuration for central system
– Send requested configuration parameters
– Send data
– Send Keep Alive

The device includes a LoRaWAN® MAC 1.0.3 rev A compliant interface (see
LoRaWAN® 1.0.3 Specification). It operates as a Class A end-device.

PRELIMINARY PHASE: DURING 1HOURS AFTER POWER ON

BLE Behavior
When the device is powered on, a yellow LED blinks to confirm the proper battery insertion.
From the sensor startup and for 1 hour, the device advertises every 1 sec. This allows user to configure the product by switching to connected mode.

LoRaWAN & BLE behavior
When initiating a measurement and a LoRaWAN communication, BLE is disable. Between BLE advertisement OFF and LoRaWAN communication ON it takes 4000ms. The device performs an initial set of acquisition on the factory default settings.
The Join Request process allows customer identification and connection to the Lora Network. Procedure is performed as follows:

• At startup, a request to join the LoRaWAN Network (called “Join Request”) is sent from the unit to the Network.
• If Join Request is accepted, connection is made, and sensor can begin sending data via upstream links to the LoRaWAN network.
• If Join Request procedure fails, unit tries again every (x) seconds until request is accepted.

Join Request signal from the LoRaWAN Radio transmitter is never transmitted simultaneously with an advertising or connection signal from Bluetooth Radio transmitter.

If this LoRaWAN Join Request procedure succussed, the data is transmitted through uplink messages.
When initiating LoRaWAN communication, BLE is disable. Between BLE advertisement OFF and LoRaWAN communication ON it takes 4000ms.
Once LoRaWAN communication is ended, system will reactivate BLE. It takes 950ms between LoRaWAN communication OFF and BLE communication ON.
During this phase user can configure the system by using BLE connected mode.
This phase can be activated locally with magnet.

NOMINAL MODE PHASE: 1 HOUR AFTER POWER ON

Keep Alive
A keep alive can be sent at least 1 time by day. Keep Alive interval can be change by user with define value 2 hours, 4 hours, 12hours and 24hours (default value). This configuration can be made over BLE and LoRaWAN.
Keep alive frame is different than Periodic Frame.

BLE

• LoRaWAN is disable.
• The device acquire data from the sensor. Then it processes the measurements depending on the default parameters.
• Data are sent over BLE depending on BLE_ ADV_MODE
• Once BLE advertisement is ended, system go on idle state.

There is three BLE advertising mode:

• ADV Burst + Periodic Mode: (Default ADV mode)
  After each measurement the system will send advertisement every 1s interval for 15 seconds. This will give multiple chances to the gateway to connect to the device. After 15 seconds, the device will advertise at 10s interval till the next measurement. During, this phase, the connection between the system and an external device could be more difficult. Between two measurements, the data into the advertisement frames is the same. The payload is only updated after every measurement interval.

• ADV On Measure Mode:
  After each measurement the sensor will send advertisement every 1s interval for 15 seconds. This will give multiple chances to the gateway to connect to the device. After 15 seconds, the device will stop to advertise.
  This ADV Mode can be selected by using BLE services ADV_CFG for current state and THS_ADV_MODE if a threshold is activated

• ADV Silent Mode:
  After each measurement the sensor won’t send advertisement.
  This ADV Mode can be selected by using BLE services ADV_CFG.
  This mode is not recommended if threshold is not activated and THS_ADV_MODE is not configured. The only way to change configuration over BLE is to use the magnet and activate advertisement (see 3.Magnet Event).

After a measurement, if a threshold is reached, the system will use threshold configuration (ADV mode and Measurement interval).

LoRaWAN

• BLE is disable.
• The device acquire data from the sensor. Then it processes the measurements depending on the default parameters.
• If this LoRaWAN join procedure succeed, the data is transmitted depending on LoRaWAN Measurement Mode.
• Once LoRaWAN communication is ended, system go on idle state.

There is three LoRaWAN communication mode:

• LoRaWAN On Measurement Mode: a data is sent every measurement

• LoRaWAN Silent Mode: System don’t send data periodically. It measures and store data. It will send data only if LoRaWAN On Measurement Mode is selected into threshold configuration.

Note: If this mode is selected and no event is detected, configuration over LoRaWAN can be done only when keep alive is sent. TE IoT platform is a LoRaWAN Class A and will listen only when it sends uplink data to gateways.

BLE connected Mode
If the sensor advertises the user can initiates a connection, the sensor switches into BLE Connected mode. While a communication is established between the sensor and the master, measurements and LoRaWAN transmissions are frozen.
This mode is used to configure the device parameters.

Special event: Magnet
If the user wants to make an asynchronous data acquisition, or access to BLE connected mode, he can use the magnet. The magnet event will trig a measurement, then the sensor will be in Preliminary Phase.

BLE COMMUNICATION

BLE Connected Mode
User can connect to the system with a Bluetooth device like computer, smartphone or tablet. It allows to configure, get access to special functions and update firmware. Product embeds with 3 different BLE connected modes which are listed below:

Standard

| User mode to configure the sensor and activate some specific function only available when connected|

None

DFU| Mode used during FW update.| OTA update

Access to Connected mode
To get access to connected mode, the user should use a device with BLE feature. When an advertisement is sent by the system the user BLE device will have opportunities to connect.

Exiting from Connected mode
When in connected mode, there are way to disconnection:

• Use the disconnect software function on the BLE central device
• Use the magnet to disconnect.

DFU Mode: Device Firmware Update
DFU mode should be used to upgrade the sensor firmware. It is accessible from the standard mode.

The new firmware to be loaded must be signed by TE.

The DFU works with a single bank only. This means that if the firmware update is interrupted (power cut off or BLE disconnection), the application firmware will be corrupted, and the sensor will stay in DFU mode. The user will have to re-try the upgrading process. Note that the DFU MAC address is the sensor MAC address +1.

List of services available
When a user is on BLE connected mode, he can access to a list of services. Each service include characteristics which allow user to configure the sensor.
Every service and characteristic share a common UUID. Only byte #3 and #4 (XXXX) differ from the identifier.

LORAWAN COMMUNICATION

General information

Frequency plans

The LoRaWAN communication protocol operates in an unlicensed radio spectrum. The part number must be selected to match with the region of operation and be in line with the local regulation.

Data rates
Following the LoRaWAN specification, each data rate is a combination of one spreading factor and one bandwidth.

EU868
For European regions, the product supports data rate from 0 up to 7 in both uplink and downlink ways.

US915
For the US915, the data rate supported by the product are:

Direction| Data Rate (DR)| Spreading Factor (SF)| Bandwidth (BW)| Bitrate (bit/s)
---|---|---|---|---
Uplink| 0| 10| 125| 980
1| 9| 125| 1760
2| 8| 125| 3125
3| 7| 125| 5470
4| 8| 500| 12500
Downlink| 8| 12| 500| 980
9| 11| 500| 1760
10| 10| 500| 3900
11| 9| 500| 7000
12| 8| 500| 12500
13| 7| 500| 21900

TX power
RF transmitting systems must adhere to certain rules set by the regulatory bodies such as FCC or ETSI. Radio devices must not exceed certain ERP or EIRP values set by these regulatory bodies.
Depending of the regional parameter the product supports the following power.

EU868

US915

Time on air limitation

Duty cycle (EU868 only)
The European Telecommunications Standards Institute (ETSI) sets the maximum duty cycle for the EU868 at 1%, which is the maximum amount of time a device may spend communicating.
This means that in a day, a device should not transmit more than 864 seconds.

Example: On measurement mode
The table below show the effect of the data rate on the maximum number of uplink message which could be transmitted in a day. Assuming the payload size of the uplink message to be 11 bytes (see Error! Reference source not found.), it gives the following results:

Duty cycle limitation effect (EU868)

DR| 0| 1| 2| 3| 4| 5| 6
Number max of uplink per day| 582| 1165| 2330| 4662| 8396| 15265| 30530
Minimum uplink interval| 2min30| 1min15| 37s| 19s| 11s| 6s| 3s*

*the minimum configurable uplink interval is 1 min.

Dwell time (US913 only)
There are no duty cycle limitations under Federal Communications Commission (FCC) but the device has to respect a certain limit of transmission duration. This parameter is called “Dwell time” and should not exceed 400ms per channel. Dwell time is the amount of time needed for a transmission.
This parameter is always respected by the product due to its compressed payload. Note that in case of FOptsLen>3, the payload may be fragmented for DR0.

Mode of operation

Enrollment
To be recognized by the LoRaWAN server, the product must be enrolled on the final application server.
Use the LoRaWAN keys provided be TE Connectivity with the device.

Join and activation
After power on, the end-device performs a self-diagnostic then it initiates a join-request to the LoRaWAN™ network using Over-The-Air-Activation (OTAA).

Join accept
In case of a sufficient LoRaWAN™ coverage and if the device was already enrolled in the server database, the network server responds to the join- request with a join-accept message.

The possible reception windows delays are:

During that operation, the end-device shares with the server the sessions keys.
When a join request is accepted the system will send a keep alive.

Un-joined
If the LoRaWAN gateway is out of the product range, or if the end-devices is not enrolled on the network, the product won’t receive any join accept response and will be in an un-joined state.
In that state, the system tries to re-join the network every 10 second and increases the join timer in case of failure by 20%, up to 1 hour maximum.
Note that for EU868 regions, the join-request may be sent only every 8 hours due to duty-cycle restriction.

Normal mode
Once the product has joined the LoRaWAN network, it operates in normal mode.

Uplink message
Every measurement determined by the measurement interval or new threshold event will trigger an uplink message.
If the server does not send back the LoRaWAN ACK flag, the product increments an error counter. After 10 consecutive fails it will try to re-join the network.
To ensure that the sensor is still alive a keep alive frame is sent. Interval between keep alive frame can be change by user. This frame be a dedicated frame (see 5.9.2.1.1).

Downlink message
Following each uplink transmission, the end-device (LoRaWAN Class A) opens one or two receive windows for potential downlink message. If no packet is destined for the product in RX1, the device does open the second receive window (RX2).
The possible reception windows delays are:

If the sensor is configured with LoRaWAN Event Mode the system will receive configuration only when keep a live is sent.
This frame be a dedicated frame (see 5.9.2.1.1).
Keep alive frequency can be configure by user.

Message Priority
The measurement process has priority over sending. If a measurement must be done, the sending of frame over LoRaWAN is rescheduled 30 seconds later. Also, LoRaWAN communication data rate (DR) depends on network quality et coverage. So, upon system location, LoRaWAN communication can have restriction. The system prioritizes or skips frame to be sent as following:

• When a downlink requests a response, while the response is not sent, the sending of keep alive or payload frame are skipped. Measurement data are stored into memory. The sending of downlink response is rescheduled 2 minutes 30 seconds later at each failed.
• When a Keep Alive occurs, while the keep alive is not sent and no response from downlink is waiting, the sending of payload frame is skipped. Measurement data are stored into memory. The sending of keep alive is rescheduled 2 minutes 30 seconds later at each failed.
• When the sending of a payload frame is failed, the sending is skipped and not rescheduled. Measurement data are stored into memory.

PAYLOAD DESCRIPTION

Specific BLE Frame format

Keep alive [Not implemented]

BLE Generic Advertising message format

This advertising is sent during phase 1. When using a BLE only system this frame will be sent to external system.

• CI: Company identifier, 0x08DE.
• DEVTYPE: Information about the product (see 5.5.1.10)
• CUSTOM ADV DATA: 4-byte array
• CNT: measurement counter
• DEVSTAT: System global status (see 5.5.1.9)
• BATT: Battery level (see 5.5.1.11)
• TEMP: Secondary data from sensor 2-Byte. Note for Temperature generic sensor temperature will be platform internal temperature.
• SENSOR32: Main data from the sensor 4-Byte (Pressure) SENSOR32 data type is defined by DEVTYPE output field.

Specific LoRaWAN Frame format
Uplink message (Platform - > Gateway)
Keep alive

• DEVTYPE: Information about the product (see 5.5.1.10)
• CNT: measurement counter
• DEVSTAT: System global status (see 5.5.1.9)
• BATT: Battery level (see 5.5.1.11)

Nominal Data uplink
The uplink “sensor data” message follows the standard format.

• DEVTYPE: Information about the product (see 5.5.1.10)
• CNT: measurement counter
• DEVSTAT: System global status (see 5.5.1.9)
• BATT: Battery level (see 5.5.1.11)
• TEMP: Secondary data from sensor 2-Byte. Note for Temperature generic sensor temperature will be platform internal temperature.
• SENSOR32: Main data from the sensor 4-Byte (Pressure) SENSOR32 data type is defined by DEVTYPE output field.

Uplink Information Response frame

RESPONSE: Context about response from the system.

Note: (Only for software version upper 3.3.X) After a Read (0x00) or Write+Read(0x02) request, the sensor automatically sends a Response (fPort 20) as soon as possible
(directly in US915 or when Duty Cycle limitation elapsed in EU868).
Also, the sensor sends a responses (fPort 20) if a error is detected when a Write (0x01) is performed. This should not impact the Periodical Uplink messages.

OPERATION RESPONSE

byte| 0
bit| 7| 6| 5| 4| 3| 2| 1| 0

field

|

UUID_UNK

| OPERATION_E RR|

READ_ONLY

|

NET_ERR

|

PERIOD_SKIP

|  |

OPERATION

• UUID_UNK: set if characteristic does not exist

• OPERATION_ERR: set if invalid payload or configuration

• READ_ONLY: set if not able to write because field is read only

• NET_ERR: set if partial response sent (check DR vs payload max)

• PERIOD_SKIP : If conflict with Periodic msg, system inform network it prioritize operation frame. Measurement is store but not send.

• OPERATION
  Read/Write| Value
  ---|---
  Read| 0
  Write + Read of last data written Note: Read the value from the register even if the write fails.| 2

• UUID: Service ID to identify the service answer.
  Note1: UUID for LoRaWAN operation request and response are UUID characteristic.

• PAYLOAD: Information form the service

Downlink message (Gateway - > Platform)
The downlink frame formats are defined as below

Information and configuration Request downlink

Frame format for Write or Write/Read request

LoRaWAN Read Request Downlink format (fport:20)

byte| 0| 1| 2
field| OPERATION

REQUEST

| UUID

OPERATION REQUEST: Define if user want to read, write or write with system acknowledge a data

OPERATION REQUEST

byte| 0
bit| 7| 6| 5| 4| 3| 2| 1| 0

field

|  |  |  |  | Fragmented data|  |

OPERATION

Note: Read function is not available for Threshold and Datalog. To read Threshold or Datalog user should use Write/Read operation frame with Threshold or Datalog read function.

Write| 1| Write a configuration/data over LoRaWAN. Note1: If the configuration is Read Only the system will send back an operation error

Note2: Read function is not available for Threshold and Datalog. To read Threshold or Datalog user

 |  | should use Write/Read operation frame with

Threshold or Datalog read function.

---|---|---
Write + Read of last data written| 2| Write a configuration/data over LoRaWAN and then the system will read and send the value store into configuration.

If a write error occurs value read will be the same as before.

• UUID: Service ID to identify the service answer
  Note1: UUID for LoRaWAN operation request and response are UUID characteristic.

• PAYLOAD: Information form the service. Payload is empty is a read is asked.

GENERIC PAYLOAD FORMAT

Global overview of payload available depending on communication

Function

| ****

Service Address

| ****

Information

| Characteristic Address

UUID to use for LoRaWAN

communication

| ****

Payload size (Bytes)

| ****

BLE

| ****

LoRaWAN

---|---|---|---|---|---|---

Generic access

| ****

1800

| Device Name| 2A00| 25| Connected: R| /
Appearance| 2A01| 2| Connected: R| /
Peripheral Preferred Connection Parameters| 2A04| 8| Connected: R| /
Central Address Resolution| 2AA6| 1| Connected: R| /
Generic Attribute| 1801| Service Change| 2A05| 0| Connected: R| /

Device information

| ****

180A

| Model Number| 2A24| 6| Connected: R| Operation Msg: R
Serial Number| 2A25| 13| Connected: R| Operation Msg: R
Firmware revision| 2A26| 23| Connected: R| Operation Msg: R
Hardware revision| 2A27| 7| Connected: R| Operation Msg: R
Manufacturer| 2A29| 9| Connected: R| Operation Msg: R
Device| FC00| Device status| FC01| 1| Connected: R/N Advertising: R| Periodic Uplink Keep Alive Msg

Battery

| ****

180F

| ****

Battery level

| ****

2A19

| ****

1

| ****

Connected: R/W Advertising: R

| Periodic Uplink Keep Alive Msg

Operation Msg: R/W/W+R

Bluetooth

| ****

CD00

| Customer Specific Data| CD01| 4| Connected: R/W Advertising: R| /
BLE Adv Mode Configuration| CD02| 1| Connected: R/W| Operation Msg: R/W/W+R
Change Device Name| CD03| 25| Connected: R/W ScanResp: R| /
Environmental sensing| 181A| Internal platform temperature| 2A6E| 2| Connected: R/N| Operation Msg: R
Keep Alive| CE00| Keep Alive configuration| CE01| 1| Connected: R/W| Operation Msg: R/W/W+R

Data collection

| ****

B300

| ****

Measurement Counter

| ****

B301

| ****

2

| Connected: R/W/N Advertising: R| Periodic Uplink Keep Alive Msg

Operation Msg: R

Measurement interval| B302| 3| Connected: R/W| Operation Msg: R/W/W+R
Trig measurement| B303| 1| Connected: W| Operation Msg: W/W+R
Last data from sensor| DA00| Last data acquired| DA01| 6| Connected: R/N Advertising: R| Periodic Uplink Operation Msg: R

Live Mode

| ****

B400

| Live Measurement interval| B401| 1| Connected: R| /
Live mode configuration| B402| 1| Connected: R/W| /
Threshold| B200| Threshold| B201| 5| Connected: R/W/N| Operation Msg: W/W+R
Datalog Raw value| DB00| Datalog data| DB01| /| Connected: R/W/N| Operation Msg: W/W+R

LoRaWAN

| ****

F800

| LoRaWAN Mode Configuration| F810| 1| Connected: R/W| Operation Msg: R/W/W+R
DevEUI| F801| 8| Connected: R| Operation Msg: R
AppEUI| F802| 8| Connected: R| Operation Msg: R
Region| F803| 1| Connected: R| Operation Msg: R
NetID| F804| 4| Connected: R| Operation Msg: R
Status (Reserved)| F805|  | Connected: R| Operation Msg: R
Percentage of confirmed uplink| F806| 1| Connected: R/W| Operation Msg: R/W/W+R
DFU| FE59| OTA process| –| /|  |
Engineering| DD00| Reserved| DD01| /| Connected: R/W| /

– GENERIC ATTRIBUTE
– GENERIC ACCESS

They are mandatory for BLE use.
Note1: UUID for LoRaWAN operation request and response are UUID characteristic. Note2: All bytes into a frame are code in BigEndian when use into a TE custom services

All bytes into a frame are code in LittleEndian when linked with BLE standard When specific code is implemented, a note is added into description.

Note3: All bits into a byte are code in BigEndian
Note4: Serial Number is the BLE MAC Address

Device status

DEVICE STATUS

byte| 0
bit| 7| 6| 5| 4| 3| 2| 1| 0

field

| ****

SENSOR

| ****

CONFIG.

| ****

MISC

| ****

CONDITION

| SYSTEM PHASE|

• SENSOR: Open Circuit, Short Circuit, No Communication, Calibration corruption (CRC), Out of range reading
• CONFIGURATION: Wrong parameter (unproper config), Conflicting configuration, User configuration corruption (CRC)
• MISC: Self diag fails (memory access, ref reading …), No Network coverage, Fail to join network
• CONDITION: Threshold trig
• SYSTEM PHASE:

DEVTYPE: Information about the product

DT VALUE

Bit| 15| 14| 13| 12| 11| 10| 9| 8| 7| 6| 5| 4| 3| 2| 1| 0
 | SW Platform| Sensor| Wireless| Output Type SENSOR32
0        Error| 0        Error| 0     Error| 0     Error
1        Platform_21| 1        Vibration| 1     BLE| 1     Float
 | 2        Temperature| 2     BLE /

LoRaWAN

| 2     Integer
 | 3        Pressure|  |
 | 4        Humidity|  |

Example for a pressure BLE only product will be:

Battery

BATTERY

bit| 7| 6| 5| 4| 3| 2| 1| 0
field| BATTERY8

BATTERY8: percentage of remaining battery. Writing 0xFF in this register will reset the battery algorithm to 100%. (0x00= 0% and 0x64= 100%)
Other value written here will be ignored.

Bluetooth

Customer specific data

CAD: Custom Advertisement Data: 4Byte

BLE Adv Mode Configuration

• ADV_MUTE: when the external device is connected, the system stops the advertising till the next event or measurement if set. Flag is reset on next event.
• ADV_MODE:

measurement then. every 10 sec
ADV On Measure Burst Mode| 1| Advertisement 15 times every 1s only after a measurement.
ADV Silent Mode| 2| No advertisement included even after measurement.

Note: On LoRaWAN device this service will be hidden during BLE discover.

Advertisement interval [Not Implemented]

Change Device Name

Change device name characteristic allows customer to change device name.

DEVICE NAME: Device name when BLE scan: 25Byte

Internal platform temperature

• INTERNAL_TEMPERATURE16 (signed): Internal temperature of the platform

????°C = ????LSB ∗ 0.01

Keep Alive
Interval between two keep alive frame.

Keep Alive Interval

Note: Default value is 24 hours.

Keep_Alive_Mode:

Keep Alive Active and not emitted if a data is sent between Two keep alive. Keep alive interval is reset when a frame is sent| 1
Keep Alive Disable| 2

Note: Default value is 0.
Note1: A Keep Alive is sent at every reboot or power up.

Data Collection

Measurement Counter

MEASUREMENT COUNTER (R/W)

Bit| 15| 14| 13| 12| 11| 10| 9| 8| 7| 6| 5| 4| 3| 2| 1| 0

CNT16: Number of measurements done. When reach 0XFFFF it will restart to 0x0000. Write 0x0000 the counter is reset to 0x0000. Other value won’t affect current counter.

Measurement interval
Interval between two measurements.

MEAS_INTERVAL

Byte| 0| 1| 2
field| HOUR8| MINUTE8| SECOND8

• HOUR8: Number of hours [0-255]
• MINUTE8: Number of minutes [0-255]
• SECOND8: Number of seconds [0-255]
• MEAS_INTERVAL = “HOUR8” & “MINUTE8” & “SECOND8”

Note: Default value is 10min. Minimum value is 1s. Value 0x000 (0h0min0s) is not consider
Note2: It’s possible to write value only in minute (ex:120min). The system will automatically transform value into standard time representation (ex:120min => 2hours). Note3: When measurement interval is modified by user, next new measurement will be done after new measurement interval. System won’t wait to end current measurement interval.

Trig Measurement
When using a TRIG the system will send the data first over BLE and then LoRaWAN if the product is eligible.

TRIG MODE

bit| 7| 6| 5| 4| 3| 2| 1| 0
field| DISCON|  |  |  |  |  |  | TRIG

TRIG: trig a new measurement flow (read raw values, temperature, battery and process the data)

DISCON: force BLE disconnection before measurement trig.

Note1 : Only 0x81 and 0x01 are allowed.
Note2: The goal of this function is not do force a BLE disconnection.

Last data from sensor
Last data acquired from the sensor:

Last data

Byte| 0| 1| 2| 3| 4| 5
field| TEMP16| SENSOR32

In case of Pressure generic

TEMP16: Temperature of the sensor

SENSOR32 (signed): Data from the sensor

Temperature

|

T°C from Tsys

| Big Endian Signed 32bit 1LSB = 0.01°C

Pressure

|

Pressure from IS405

| Big Endian Float 32bit

Humidity

|

Humidity from HTU21

| Big Endian Signed 32bit 1LSB = 0.01%RH

Live mode

Measurement interval
This mode is only available over BLE.

LIVE_MODE_MEAS_INTERVAL

bit| 7| 6| 5| 4| 3| 2| 1| 0
field| LIVE_MODE_MEAS_INTERVAL8

MEAS_LIVE_INTERVAL8 : Read Only Value in millisecond.

Live mode configuration

LIVE_MODE_CFG

bit| 7| 6| 5| 4| 3| 2| 1| 0
field|  |  |  |  |  |  |  | ENABLE

ENABLE: enable or disable Live mode.

NOTE : Two way are available to stop “Live mode”:

• BLE disconnection from the central device or with the magnet
• Send Live Mode disable into LIVE_MODE_CFG

Threshold
To ask threshold parameters use the following frame:

Request Threshold information

byte| 0| 1
field| ID DATA| PARAM SEL

Sensor will answer with the following frame:

Answer after a Read requestion

byte| 0| 1| 2| 3| 4| 5
field| ID DATA| PARAM SEL| DATA32

To write threshold parameters

Write Threshold Configuration

byte| 0| 1| 2| 3| 4| 5
field| ID DATA| PARAM SEL| DATA32

ID_DATA : defines the source for threshold

PARAM SEL: Select parameters to be changed (more details below)

Value

THS_CONFIG| 0x0
THS_LEVEL| 0x1
MEAS_INTERVAL| 0x2
Communication_MODE| 0x3

PARAM SEL=0x0 (Threshold configuration)

This command can be used with multiple parameters. Data32 format:

THS_CONFIG

Byte| 3| 2| 1| 0
bit| 7| 6| 5| 4| 3| 2| 1| 0| 7| 6| 5| 4| 3| 2| 1| 0| 7| 6| 5| 4| 3| 2| 1| 0| 7| 6| 5| 4| 3| 2| 1| 0

field

| EVT_FLAG| THRESHOLD ENABLE| CONDITION| AUTO_CLR| ACTION: MEAS INTERVAL| ACTION: ADV MODE BLE| ACTION: COMM MODE LoRa|  |  |  |  |  |  |  |  |  |  |  | |  |  |  |  |  |  |  |  |  |  |  |  |

EVT_FLAG: Forcing this bit to 0 clears the event flag until next trig.

THRESHOLD ENABLE: Enable threshold

 | State| Value|
---|---|---|---
Disactivated| 0
Threshold activated| 1

CONDITION: Define the threshold condition

AUTO_CLR: Auto clear once event condition:

ACTION: MEAS_INTERVAL: Change Measurement Interval after the threshold level reached:

ACTION: ADV MODE BLE: Change Advertisement Mode after the threshold level reached

ACTION: COMM MODE LoRaWAN: Change LoRaWAN Communication Mode after the threshold level reached

PARAM SEL=0x1 Data32 format: Threshold level

THS_LEVEL

Byte| 3| 2| 1| 0

field

| INT32 / FLOAT32
N/A| INT16

Same data format as SENSOR32 /TEMP16 Default value: 0x0

PARAM SEL=0x2 Data32 format: Measurement interval after a threshold

MEAS_INTERVAL

Byte| 3| 2| 1| 0
field| HOUR8| MINUTE8| SECONDE8| 0 (Not Use)

Note: Default value is 1min. Minimum value is 1s but user shouldn’t use it. Value 0x000 (0h0min0s) is not consider

PARAM SEL=0x3 Data32 format: Communication mode after a threshold

THS_COMM_MODE

Byte| 3| 2| 1| 0
bit| 7| 6| 5| 4| 3| 2| 1| 0| 7| 6| 5| 4| 3| 2| 1| 0| 7| 6| 5| 4| 3| 2| 1| 0| 7| 6| 5| 4| 3| 2| 1| 0

field

|  |  |  |  |  |  |

BLE_ADV_MODE

|  |  |  |  |  |  |

LoRaWAN COMM MODE

|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |

BLE_ADV_MODE:

sec

On Measure

mode

| 1| Advertisement only after a measurement (15 consecutives

ADV)

ADV Silent

mode

| 2| No advertisement included even after measurement.

LoRaWAN_COMM_MODE:

Datalog

Datalog array access request

ARRAY ACCESS REQUEST

byte| 0| 1| 2| 3
field| TYPE8| INDEX16| LENGTH8
---|---|---|---

• TYPE8: Data (0 = TEMPERATURE16, 1 = SENSOR32, 2 = TEMPERATURE16 + SENSOR32).

• INDEX16: start index from 0 up to 4095 for Raw data (MSB first).
  =lastest data acquired, 4095= oldest data acquired

• LENGTH8: number of values to be read. Admissible range depends on TYPE8:

  • 1-120 for TYPE8=TEMPERATURE16
  • 1-60 for TYPE8=SENSOR32
  • 1-40 for TYPE8= TEMPERATURE16 + SENSOR32
    If the required length is larger than network capabilities, the frame will be filled with the max possible data. No data will be truncated.
    Over LoRa, if network does not allow to provide desired number of data, a Network_Error flag will be set into Operation Response field.

Datalog array access response with notification

ARRAY ACCESS RESPONSE

byte| 0| 1| 2| 3|  |  | –| m-1| m
field| TYPE8| INDEX16| LENGTH8| VALUE_0|  | VALUE_n

• TYPE8: Data (0 = TEMPERATURE16, 1 = SENSOR32, 2 = TEMP16 + SENSOR32).
• INDEX16: start index of the value
• LENGTH8: number of values has been really sent.
• VALUE_n: SENSOR32 or TEMP16 or SENSOR32 + TEMP16. For TEMP16 the 1rst Byte is filled of 0.

Note: In case of error, ARRAY ACCESS RESPONSE will be 0xFFFFFF00. 5.5.1.20 LoRaWAN platform
If the platform is BLE only this service is not loaded.

LoRaWAN Mode configuration

LoRaWAN TX Mode Config

bit| 7| 6| 5| 4| 3| 2| 1| 0

LoRaWAN Communication Mode:

(Default)

| LoRaWAN Communication at every measurement
On Silent Mode| 1| No LoRaWAN communication at each measurement

Note: CNT will be the latest measurement.

Note2: Uplink frame will have the same header but sensor data will be added ones after others.

DevEUI
This number is the 64-bit Device Extended Unique Identifier of the sensor. It is generated by TE and must be derived from the TE Organizationally Unique Identifier (OUI) assigned from the IEEE Registration Authority.

AppEUI
This number is the 64-bit application Extended Unique Identifier of the sensor.

NET ID
Contains the operator network identifier coded on the 4-byte value (LSB first). The list of all possible operator is listed below.
https://www.thethingsnetwork.org/docs/LoRaWANwan/prefix-assignments/
For example, 0x00000013 identifies “The Things Network”.

Region
LoRaWAN configured region. US or EU.

Status
Reserved

LoRaWAN percentage of confirmed uplink messages
It is possible to reduce the number of acknowledgements between the LoRaWAN gateway and the device.

 | byte| 0|
---|---|---|---
bit| 7| 6| 5| 4| 3| 2| 1| 0
field| PERCENTAGE = 100

PERCENTAGE: Percentage of LoRaWAN uplink confirmed messages. From 0%up to 100%. Default is 100%.

Note: Value 0% should not be used by end user.
Note1: LoRaWAN percentage of confirmed uplink is only applied on Nominal d (Keep alive frame are confirme) data uplink

LoRaWAN deactivation [Not Implemented]

BATTERY

SAFT LS17330
The system should be exclusively powered with an LS17330 battery.

BATTERY LIFE
Depending on customer settings (measurement interval) battery life could go up to 4 years (depends on measurement interval and RF communication).
The number of measurements per day will affect the battery life. More measurements will reduce the battery life.

BATTERY REPLACEMENT
The system battery can be changed if empty. Unscrew the plastic housing and remove it from the base. Carefully use a small tool (such as a flat screwdriver) to take off the battery. Note that it MUST be replaced by the same battery reference (others may damage and/or bring uncontrolled behavior of the sensor). Double check the polarity and then insert the new battery inside the holder. Re-position the plastic cover on the sensor.
Once done, the user must have to use the BLE “battery” characteristic value to reset the battery estimation algorithm.

This action is mandatory otherwise battery level will stay at 0%!

MAGNETIC SWITCH

The system has an internal reed switch.
This switch is activated when a strong magnet is close to the magnetic sensor location. The magnetic switch location is indicated by the magnet icon on the plastic housing. The magnet must be of sufficient strength and proximity to create a magnetic field of 25 mT at the switch location..

Two different functions are available depending on the user action:

Activates BLE for another one hour Trigs a new measurement and a

LoRaWAN™ transmission (uplink if joined, else join request

Disconnect from BLE connected mode

|

Short tap

| One short blink. If user holds the magnet close to the switch for a longer duration, the LED will blink faster.

Remove the magnet to only initiate a transmission. Else it going to initiate a sensor reset.

Restart the sensor and keep current configuration

| Hold the magnet for 10 seconds.| Wait for at least 10 seconds, to see the very fast blink. Release the magnet once a very long orange led appears

LED

A yellow led is used to indicate user some specific event:

Maintaining Magnet

| <3s| Slow blinking
[3s-10s]| Fast blinking

10s| OFF -> reboot

DIMENSIONS

MOUNTING CONSIDERATIONS

The pressure sensor should be stud mounted on a clean, flat surface. The mounting torque for the sensor is not exceed 30 N-m.

• WARNING – Do NOT tighten the sensor by twisting on the housing. Damage to the sensor WILL occur. Tighten to the correct torque using a wrench on the hex base.

• WARNING – Install in a process connection with enough room to allow the use of
  Spanner/Wrench.

• WARNING – To reduce the risk of burns or frost bite, wear protective personal equipment when installing or removing from high or below-freezing temperature process or environments.

• WARNING – After installation carefully check for leaks.

CERTIFICATIONS & COMPLIANCES

CERTIFICATIONS
69X1N Wireless Sensors with characteristic (EX) in model name are certified for Intrinsic Safety to the following classification:
IS Class I, Div1, Groups A, B, C, and D;
Class I Zone 0, AEx ia IIC T4 Ga;
Ex ia IIC T4 Ga;
ll 1 G Ex ia IIC T4 Ga
Please see section 14 for details on how to order.

REGLUATORY STATEMENTS

FCC and IC
This Radio Equipment is Certified for FCC (US) and ISED (Canada).
This equipment does not support simultaneous transmissions.
Changes or modifications not expressly approved or authorized by TE Connectivity for compliance could void the user’s authority to operate the equipment.

FCC Warning:
THIS DEVICE COMPLIES WITH PART 15 OF THE FCC RULES.OPERATION IS SUBJECT TO THE FOLLOWING TWO CONDITIONS: (1) THIS DEVICE MAY NOT CAUSE HARMFUL INTERFERENCE, AND (2) THIS DEVICE MUST ACCEPT ANY INTERFERENCE RECEIVED, INCLUDING INTERFERENCE THAT MAY CAUSE UNDESIRED OPERATION.

Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does not cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to correct the interference by one or more of the following measures:

• Re-orient or relocate the receiving antenna
• Increase the separation between the equipment and the receiver
• Connect the equipment to an outlet on a circuit that is different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

Industry Canada (IC) Warning:
This device complies with ISED Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.

IMPORTANT NOTE:
Radiation Exposure Statement: This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment. End users must follow the specific operating instructions for satisfying RF exposure compliance. To maintain compliance with IC RF exposure compliance requirement, please follow operation instruction as documented in this manual.

EU CONFORMITY

The products below were tested by approved agencies and found compliant with EU regulatory standards.

Model Families: 69X1N
Product Description: Wireless Pressure Sensor
Manufacture/Brand : TE Connectivity Ltd

Manufacturer:

Measurement Specialties (China) LTD
No 26 LangShan Road
518057 Shenzhen-Nanshan District, China

European Contact:
TE Connectivity Sensors France
4 Rue Gaye Marie
31027 Toulouse – France
OPERATING FREQUENCY (the maximum transmitted power)
2402MHz—2480MHz(EIRP 3.4dBm)
863MHz~870MHz(EIRP 7.1dBm)

ORDERING INFORMATION

LoRa + BLE Sensor Model Number

Sales and technical support

NORTH AMERICA
Measurement Specialties, Inc.,
a TE Connectivity Company
Phone: +1 800-745-8008
Email: TEsensors-CCMeas@te.com

EUROPE
Measurement Specialties (Europe), Ltd.,
a TE Connectivity Company
Phone: +31 73 624 6999
Email: customercare.Icsb@te.com

ASIA
Measurement Specialties (China), Ltd.,
a TE Connectivity Company
Phone: +86 0400-820-6015
Email: customercare.shzn@te.com

Manufacturer: Measurement Specialties (China) Inc., a TE Connectivity Company
No. 26 Langshan Road, Shenzhen High-Tech Park (North), Nanshan District, Shenzhen, 518057
Tel: +86 0400-820-6015
customercare.shzn@te.com

20027955-11 Rev. 0.2, 2023-04-06

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>