sc14wsmdata Dialog Semiconductor, sc14wsmdata Datasheet - Page 15

• Manufacturer Part Number: sc14wsmdata
• Description: Ultra Low Energy Wireless Sensor Module V1.0
• Manufacturer: Dialog Semiconductor

© 2011 Dialog Semiconductor B.V/
4.5 DATA TRANSMISSION PROTOCOL
The SC14WSMDATA data transmission protocol over
the RF interface is DECT TDMA compliant. The proto-
col does not feature encryption so payload encryption
must be handled by the user application if required.
4.5.1
When the Sensor goes out-of-range or can not find the
FP upon wake up an error message is received from
the stack after a time-out. This time-out can be config-
ured from the user application.
4.5.2
A 232 bits data packet can be transmitted or received
at every burst. Multiple packets can be send, however
this will of course impact power consumption. No spe-
cific formatting is applied. The correct transmission of a
packet is acknowledged by the API.
4.5.3
The sensor and the base (FP) must be paired using a
procedure called Registration. Without Registration,
the sensor will not be able to establish a link to a FP.
The registration uses the unique product identities and
secures the Sensor and FP communication. These
identity numbers are pre programmed in the NVS dur-
ing module production.
Using unique access codes (like a PIN code)
registration to the wrong FP can be prevented.
The sensor can be put into Registration mode in which
it automatically de-registers from the current FP. This
can be done from the user application. Using custom
Out-of-Range handling
Data packet
Registration
Count
Company Confidential
Sleep
Sleep cmd
Figure 6 Power Cycle State machine
Event or
Timer
Wakeup
Awake
Keep
15
payload messages deregistration requests can thus be
issued from the sensor itself, the FP or even another
sensor.
It is possible to pair a sensor and FP at production
time. Registration information is stored in the NVS dur-
ing production.
4.5.4 Deregistration
There are two ways to deregister a Sensor from a FP:
• Remote FP and Sensor deregistration
• Local Sensor deregistration
• The SW API supports removing all registrations at
The preferred way to deregister a Sensor from a FP
is to initiate deregistration in the FP and Sensor
through the SW API. Using a user defined payload
format the FP or PP should indicate the deregistra-
tion should take place, optionally an acknowledge
can be sent and afterwards the FP and PP both initi-
ate a deregistration. Using this method it is also pos-
sible to deregister other Sensors registered to the
FP from one Sensor. See [1] and [4] in order to
determine which AT commands are needed to send
data (alerting the PP deregistration should take
place) and how to deregister a node in the FP and
PP.
It is possible to initiate deregistration locally in the
Sensor only. This could be an option if the Sensor
should be used on another FP and the original regis-
tration should be removed.
once from the FP (e.g. in case the original Sensors
are lost).
Locked
Application
Packet
Send
Preliminary December 4, 2012 v1.0