X4M200 Datasheet

X4M200 Datasheet
Respiration Sensor
XeThru Datasheet by Novelda AS
Rev. E - Preliminary - October 18. 2018
Summary
The XeThru X4M200 Respiration Sensor is an
industrialized sensor that complies with worldwide
regulations ready for product integration. Based on
Novelda’s proprietary, highly integrated X4 system-
on-chip (SoC), the sensor provides highly accurate
measurement of a person's breathing frequency,
together with distance and movement information.
Table of Contents
List of Features __________________________________________________________________ 5
Order information ______________________________________________________________ 6
XeThru X4M200 Respiration Sensor _________________________________________________ 6
Sensor Operation ________________________________________________________________ 6
Power-up and Reset _____________________________________________________________ 6
First Power-Up ______________________________________________________________ 6
Configuration _______________________________________________________________ 6
Running Sensor Directly from Power-up or Reset __________________________________ 7
IO-pins ________________________________________________________________________ 7
Firmware Versions ______________________________________________________________ 7
Bootloader ____________________________________________________________________ 7
Fail Safe Mode _________________________________________________________________ 8
X4M200 Respiration Profiles _______________________________________________________ 9
Overview ______________________________________________________________________ 9
User Settings __________________________________________________________________ 10
Set Detection Zone __________________________________________________________ 10
Sensitivity _________________________________________________________________ 10
LED ______________________________________________________________________ 10
Frequency Band _____________________________________________________________ 11
Noise Map Control ___________________________________________________________ 11
Use Stored Noise Map ________________________________________________________ 11
Use Default Noise Map _______________________________________________________ 12
Adaptive Noise Map _________________________________________________________ 12
Default User Settings _________________________________________________________ 12
Sensor Operation in X4M200 Respiration Profiles ____________________________________ 13
Detect Presence and Breathing ________________________________________________ 13
Measure Respiration Data _____________________________________________________ 13
IO-pin Functionality _________________________________________________________ 14
Detection Range _______________________________________________________________ 15
Detection Time ________________________________________________________________ 15
Firmware Algorithms ___________________________________________________________ 16
Default Noise Map ___________________________________________________________ 17
Stored Noise Map ___________________________________________________________ 17
Start-up Time _______________________________________________________________ 18
Baseband Data Output __________________________________________________________ 18
Pulse-Doppler Processing and Range-Doppler Data Output ____________________________ 19
Certification Mode _______________________________________________________________ 19
Overview _____________________________________________________________________ 19
Certification Modes _____________________________________________________________ 19
Firmware versions _______________________________________________________________ 21
X4M200 Version 1.2.1 ___________________________________________________________ 21
X4M200 Version 1.3.1 ___________________________________________________________ 22
X4M200 Version 1.4.7 ___________________________________________________________ 22
Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

www.xethru.com Page 2
X4M200 Version 1.5.10 __________________________________________________________ 22
X4M200 Version 1.6.6 __________________________________________________________ 22
X4M200 Version 1.6.8 ___________________________________________________________ 23
Future versions of X4M200 _____________________________________________________ 23
X4M200 HW Revisions ___________________________________________________________ 23
Identifying HW revision _________________________________________________________ 24
X4M02 Revision 4 _____________________________________________________________ 24
X4M02 Revision 5 _____________________________________________________________ 24
X4M02 Revision 6 _____________________________________________________________ 24
X4M02 Revision 10 _____________________________________________________________ 24
Software Resources _____________________________________________________________ 25
XeThru Explorer _______________________________________________________________ 25
XeThru Module Connector _______________________________________________________ 25
Module Communication Protocol Wrapper (MCP Wrapper) ____________________________ 25
X4M200 Firmware Binary _______________________________________________________ 26
Mechanical Data ________________________________________________________________ 26
Electrical Specification ___________________________________________________________ 26
X4M200 Interface Options ________________________________________________________ 27
16-pin XeThru Interface Connector ________________________________________________ 27
Pin Descriptions ____________________________________________________________ 27
USB Connector ________________________________________________________________ 28
Communication Modes _________________________________________________________ 28
Power System _________________________________________________________________ 29
Schematics and Bill of Material ____________________________________________________ 29
Module User Guide ______________________________________________________________ 29
Placing the Sensor Module ______________________________________________________ 29
Connecting the X4M200 to a host system __________________________________________ 29
Interfacing via USB __________________________________________________________ 30
Interfacing via UART ________________________________________________________ 30
Interfacing via USRT _________________________________________________________ 30
Reset control of X4M200 _____________________________________________________ 31
Upgrading the Firmware Using the Bootloader ______________________________________ 31
Regulatory Approval _____________________________________________________________ 31
CE / ETSI Approval ____________________________________________________________ 32
EU Declaration of Conformity _________________________________________________ 34
FCC Approval _________________________________________________________________ 35
X4M200 Block Diagram ______________________________________________________ 35
Radar Functional Description _________________________________________________ 36
FCC Regulatory Notices ______________________________________________________ 36
ISED Approval ________________________________________________________________ 37
Regulatory Information Canada ________________________________________________ 37
RF Exposure Safety _________________________________________________________ 37
Labelling Requirements for the Host Device _____________________________________ 38
Errata _________________________________________________________________________ 38
Firmware Version 1.2.1 __________________________________________________________ 38

Firmware Version 1.5.10 _________________________________________________________ 39
Firmware Version 1.6.6 _________________________________________________________ 40
Errata in X4M02 Revision 6 and lower _____________________________________________ 40
Support and Resources ___________________________________________________________ 41
Disclaimer ______________________________________________________________________ 41

1 List of Features
Non-contact vital signs monitoring up to 5 meters
Measures distance from sensor to person
Measures respiration rate of person when person is still
Radar sensor
Baseband data output
Pulse Doppler output
Novelda Ultra Wide Band (UWB) Impulse Radar X4 system on a chip (SoC)
Built-in TX and RX antennas
Multiple interface options
Serial interface, UART and USRT
On-board USB interface
On-board multi-color LED
Certifications
FCC for USA
CE for Europe
ISED for Canada
X4M200 Respiration Sensor

1.1 Order information
Order Code Item Description MOQ MPQ Packaging
X4M200 X4M200 Respiration Sensor 1 1 1 unit in anti-static bag

FCC and CE/ETSI version
X4M200-TR100 X4M200 Respiration Sensor 100 100 100 units in anti-static tray
FCC and CE/ETSI version
MOQ: Minimum Order Quantity
MPQ: Minimum Package Quantity
2 XeThru X4M200 Respiration Sensor

X4M200 can read vital signs data such as respiration rate and breathing pattern on people that
are still, typically lying in a bed or sitting.
X4M200 is able to sense human presence by detecting any motion such as a person walking,
hand movements and even a person with no other movements than respiration. The unique
ability to sense respiration movement enables products that do not lose track of a person's
presence if he/she sits still for a longer time period. Its extreme sensitivity enables it to detect
presence up to a distance of 5.0 meters. It is also able to measure the distance between the
sensor and the person with centimeter accuracy, and is not susceptible to “dead spots” within
the detection zone.
With the XeThru technology's ability to see through light materials it also enables products that
detect a person's presence and collects vital signs data while sleeping with a blanket, duvet or
clothes covering the person's body.
3 Sensor Operation
3.1 Power-up and Reset
3.1.1 First Power-Up

At first power-up of the sensor, the default Profile will be loaded and started with its default User
Settings. Each Profile has a default message that the sensor will start sending over the serial
communication link.
3.1.2 Configuration
Profiles and User Settings can be modified and loaded as described in the Module Connector
documentation found on www.xethru.com.
User Settings vary between different Profiles and each Profile has its own default settings. See
the Profile description chapters for details.
User Settings can only be changed when the Profile is not running. To change any setting, follow
these steps:
1. Stop running Profile (if any Profile is running)

2. Load desired Profile (if not already loaded)
3. Send settings commands
a. User Settings such as Detection Zone, Sensitivity etc.
b. Output Control settings that determine which messages will be sent over the serial
communication link on X4M200
4. Start running Profile
New settings will be programmed into the sensor when a Profile is started. If new settings are
given to the sensor, but power is turned off or lost before a Profile is started, the new settings
are lost, and the sensor will remember its old settings at the next power up.
Changing between some Profiles will require the sensor to reset its microcontroller (MCU) to take
effect. In this case, when starting to run the new Profile, the sensor will give an error reply, take
all changes into affect, and reset. The host should then wait for a couple of seconds to issue new
commands to load and start running the Profile. The sensor will then reply OK and start the new
Profile. Examples of Profiles that require the sensor to reset its microcontroller are Profiles using
only internal MCU memory versus Profiles using external memory on the sensor.
Switching Profile will load the last used User Settings for the new Profile. If the new Profile has
not been run earlier, default User Settings for that Profile are used.
3.1.3 Running Sensor Directly from Power-up or Reset

At power-up or reset, the sensor will start with its last used settings.
3.2 IO-pins
Various Profiles may have different uses of IO-pins. Do not connect IO-pins that are not in use.
The sensor module will pull up these IO-pins internally. Future FW upgrades of the sensor and
any existing or future pin compatible products may use these unused IO-pins for other
functionality.
3.3 Firmware Versions

The datasheet may describe features not yet implemented in the current firmware version of the
module. The datasheet chapter Firmware Versions explains what features are implemented in
which firmware versions.
3.4 Bootloader
The module has a bootloader to allow field firmware upgrades. The bootloader is locked and
cannot be reprogrammed, thus it can never be erased, altered or removed from the module over
the serial protocol. The bootloader can be entered through the serial protocol, and it is also
possible to force the module into bootloader mode using the pin header interface. See datasheet
chapter Interface Options for details.

Bootloader flowchart
If a firmware upgrade fails (e.g. power loss) the host providing the firmware upgrade must
reinitiate the entire firmware upgrade process. The previous version of the firmware may be lost,
but the bootloader will still operate as described even after a failed firmware upgrade attempt.
If the Flash on the microcontroller is erased using an external programmer or debugger, the unit
cannot be reprogrammed to default functionality by the user.
3.5 Fail Safe Mode

To contain possible issues that could unintentionally block communication and new firmware
upgrades of X4M200, a Fail Safe Mode is implemented.
X4M200 will count the number of resets caused by issues in the firmware and enter Fail Safe
Mode after ten such consecutive resets. In Fail Safe Mode, the LED of X4M200 will be white. In
Fail Safe Mode, X4M200 will only respond to commands from the XEP interface, and a module
reset or firmware upgrade command can be issued. A reset command or power toggle will make
X4M200 resume normal operation.

4 X4M200 Respiration Profiles
A Profile is defined as a specific configuration of the sensor that covers a specific use case. New
profiles might be included based on market demand.
4.1 Overview
The XeThru Respiration Profiles work by measuring the minute periodic movements of the
human body while breathing. All respiration profiles can be used to measure respiration both for
a sleeping person in a bed with the sensor placed on a night stand, on the wall or in the ceiling,
and for an awake person sitting still with the sensor placed at the height of the chest or
abdomen, or pointing towards the chest or abdomen.
The body part generating the best signal will vary from person to person. Some breathe shallo
wly, drawing air into the chest area and thus the largest movement will come from the chest.
Others breathe deeper, expanding the abdomen rather than the chest. In this case, the abdomen
will give the largest movement.
X4M200 supports different profiles optimized for respiration monitoring of adults and babies.
Profile Settings
Name Intended use Detection Fast Slow RPM Optimizations
Zone range
Respiration_2 Adults and 0.40 - 5.00 6 20 8 - 30

children m sec sec RPM
Respiration_3 Babies and 0.40 - 5.00 6 15 15 - 65

children m sec sec RPM
Respiration_4 Adults and 0.40 - 3.00 6 20 8 - 30 Using internal MCU

children m sec sec RPM memory only
Respiration_5 Babies and 0.40 - 3.50 6 15 15 - 65 Using internal MCU

children m sec sec RPM memory only
Typically, a Profile measuring respiration rates above 30 RPM is needed for children under three
(3) years of age. Typically, a Profile measuring respiration rates below 15 RPM is needed for
children over ten (10) years of age. See https://en.wikipedia.org/wiki/Respiratory_rate or
medical publications for more detailed explanations on how resting respiration rate varies with
age and between people.
X4M200 has been designed to measure respiration of people, but can be used to measure
respiration rate of some animals. For this use case, check what resting respiration rate the target
animal has, select the Profile that fits best, and validate performance against the animal in
question.
The values for Slow and Fast in the table above shows the length of the Slow and Fast Pulse-
Doppler algorithms running in the Profile. See Firmware Algorithms section below for a
description on how these are used.
Profiles using only internal MCU memory will have lower electromagnetic interference (EMI) than
the other profiles, which uses the external memory on X4M200.

4.2 User Settings
4.2.1 Set Detection Zone

The Detection Zone is set by specifying the start and end of the Detection Zone. The end of the
detection zone sets the maximum distance for presence and respiration detection, while the start
of the detection zone sets the minimum distance.
Detection zone limits Respiration_2 Respiration_3 Respiration_4 Respiration_5
Minimum start of detection 0.40m 0.40m 0.40m 0.40m

zone
Maximum end of detection 5.00m 5.00m 3.00m 3.50m

zone
Minimum size of detection 0.20m 0.20m 0.20m 0.20m

zone
Maximum size of detection 4.60m 4.60m 2.60m 3.10m

zone
Step size between possible range settings is 5.14 cm. The desired detection zone can be set with
1 cm resolution. The actual detection zone will be set at the closest possible range setting before
the lower range desired and the closest possible range setting after the upper range desired. The
actual lower and upper range to be used by the sensor can be read back after setting the
detection zone.
Movements closer to the sensor than the Detection Zone may trigger detection because of
indirect reflection paths. Movements beyond the end of the detection zone will never trigger
detection.
4.2.2 Sensitivity
Sensitivity settings
Minimum sensitivity 0
Maximum sensitivity 9
Sensitivity step size 1
Higher sensitivity setting gives better sensing of small targets. Lower sensitivity makes the
sensor more robust against false detections.
4.2.3 LED
The module has 1 multi-color RGB LED. The module LED can be configured between "Full" state
indication, a "Simple" indication or "Off", which is convenient for sleep monitoring use.
Full

Initializing: Green (0.2sec) -> Orange (0.2sec) -> Red (0.3sec) -> Orange (0.2sec) -> Green (0.2
sec) -> Off (0.3sec)
Breathing: Blue On/Off flashing 50% duty cycle. Period = RPM (not breathing pattern, RPM =15
means LED flashes 15 times/minute)
Movement tracking: Green (0.5sec) -> Blue (0.5sec)
Movement: Green (0.5sec) -> Orange (0.5sec)
No movement: Red (0.3sec) -> Off (4.7sec)
Simple
Initializing: Green (0.2sec) -> Orange (0.2sec) -> Red (0.3sec) -> Orange (0.2sec) -> Green (0.2
sec) -> Off (0.3sec)
Breathing: Blue On
Movement tracking: Green On
Movement: Orange On
No movement: Red (0.3sec)-Off (4.7sec)
Off
Always: Off
4.2.4 Frequency Band

Low
In the low frequency band, X4M200 will operate within the 6.0 - 8.5 GHz band.
High
In the high frequency band, X4M200 will operate within the 7.25 - 10.20 GHz band.
4.2.5 Noise Map Control

See Firmware Algorithms section below for a description on how Noise Maps are used. There are
three User Settings for Noise Map Control: Use Stored Noise Map, Use Default Noise Map, and
Adaptive Noise Map. There are two Noise Maps used in all Respiration Profiles, one for the Slow
Range-Doppler matrix and one for the Fast Range-Doppler Matrix. When User Settings for Noise
Map Control describe functions to control Noise Map, this control is valid for both Noise Maps
used in the signal processing algorithms. When creating a new Noise Map, the X4M200 sensor
must be still and there must be no people within the Detection Zone.
4.2.6 Use Stored Noise Map

On
If a valid Stored Noise Map exists this will be used at reset or when the Profile is started.
If no valid Stored Noise Map exists and Use Default Noise Map is off, a new Noise Map will be
created during Initialization state. The newly created Noise Map will be stored in the sensor when
Initialization is done. A noise map created with a different Detection Zone is not valid.
If no valid Stored Noise Map exists and Use Default Noise Map is on, the Default Noise Map will
be used at reset or when the Profile is started.
Off

If Use Default Noise Map is off, a new Noise Map will always be created at reset or when the
Profile is started. Sensor will be in Initialization state during Noise Map creation. A previously
Stored Noise Map in the sensor will be ignored, but not overwritten, when the Profile starts.
If Use Default Noise Map is on, the Default Noise Map will be used at reset or when the Profile is
started.
4.2.7 Use Default Noise Map

On
If Use Store Noise Map is on and a valid Stored Noise Map exists, Default Noise Map will not be
used.
If Use Stored Noise Map is on and no valid Stored Noise Map exists, the Default Noise Map will be
used at reset or when the Profile is started.
If Use Stored Noise Map is off, the Default Noise Map will be used at reset or when the Profile is
started.
Off
The Default Noise Map will not be used.
4.2.8 Adaptive Noise Map

On
Enables Noise Map adaptation. Noise Map will still not adapt in certain conditions as described in
Firmware Algorithms section below.
Off
Disables Noise Map adaptation.
4.2.9 Default User Settings
Default User Settings for the Supported Profiles

User Setting Respiration_2 Respiration_3 Respiration_4 Respiration_5
Detection Zone 0.40 - 5.00m 0.40 - 5.00m 0.40 - 3.00m 0.40 - 3.50m
Sensitivity 5 5 5 5
LED Full Full Full Full
Frequency Band Low Low Low Low
Use Stored Noise Map Off Off Off Off
Use Default Noise Map Off Off Off Off
Adaptive Noise Map On On On On

4.3 Sensor Operation in X4M200 Respiration Profiles
4.3.1 Detect Presence and Breathing

The X4M200 sensor detects presence within its detection zone by detecting movement and
processing the data. Once the module detects movement, it will attempt to identify a breathing
movement. The target person needs to be still in order to identify breathing movement.
If more than one person is present in the detection zone, the X4M200 sensor will measure the
one who is closest to the sensor. If the intention is to not measure the closest person, the
detection zone can be set to a minimum distance that excludes the closest person, but because
of indirect reflection paths that could lead to the closer person being read at a longer distance.
This specific scenario is unlikely to work reliably in real-life scenarios as soon as the closest
person has any significant movement.
There are six states in the Respiration Profile:
No Movement No presence detected

Movement: Presence, but no identifiable breathing movement
Movement Tracking: Presence and possible breathing movement detected
Breathing: Valid breathing movement detected
Initializing: The sensor initializes after the Respiration Profile is executed
Error: The sensor is in an error state and requires a Profile and User Settings to be loaded
4.3.2 Measure Respiration Data

When running, the following data is reported:
State
In all states except Initializing and Error states, the following data is measured:
Movement Slow: Movements for the previous Slow period

Movement Fast: Movements for the previous Fast period
Normalized Movement Slow: Normalized Movements for the previous Slow period
Normalized Movement Fast: Normalized Movements for the previous Fast period
Movement Slow and Movement Fast show the degree of movement as a relative number from 0
to 100 both for 5.14 cm intervals in the Detection Zone and for the entire Detection Zone. 0
means no Doppler cells above the detection threshold, while 100 means that all Doppler cells in
the range interval are above the detection threshold.
Normalized Movement Slow and Normalized Movement Fast also show the degree of movement,
but are adjusted for distance to give approximately the same value for the same size of
movement at different distances. Outputs shows a logarithmic value of the size of the movement
and typically varies from -20, which means no movement, and 30 or above, which means very
large movements. Normalized Movement Slow and Normalized Movement Fast is provided for
5.14 cm intervals in the Detection Zone.
When in Movement, Movement Tracking, or Breathing states, the following additional data is
measured:
Distance to closest target: Distance in meters to target closest to the sensor

RCS of closest target: Radar Cross Section in dB(m2) as seen from X4M200
Signal Quality: A relative number from 0 to 10 where 10 is best
When in Breathing state, the following additional data is measured:
RPM of closest breathing target: Respirations per Minute

Distance to breathing target: Distance in meters to target RPM is measured from
Breathing pattern of closest breathing target: Detected respiratory movement in mm
perpendicular to the X4M200
Normalized Movement Interval Slow: Normalized Movements for the previous Slow period
for an approximately 1 meter zone around the distance to breathing target
Normalized Movement Interval Fast: Normalized Movements for the previous Fast period
for an approximately 1 meter zone around the distance to breathing target
Distance to closest target and breathing target may be different even when only one target
person is present in the Detection Zone. Distance to closest target measures the distance to the
closest movements the sensor can see. Distance to breathing target measures the distance to
where the respiration motion is seen. As an example, if the target person's hands are closer to the
sensor than the chest or abdomen and have some minimal movement, distance to closest target
will measure the distance to the hands and distance to breathing target will measure the distance
to the chest or abdomen where the respiration motion is.
With two or more targets in the Detection Zone, different distance to closest target and distance
to breathing target can also be experienced. As an example, if a still person is still at a longer
distance than a second moving person closer to the sensor, the sensor may lock on the breathing
of the person further away. In this case distance to closest target will be to the person moving
closer to the sensor and distance to breathing target will be on the still person further away.
Achieving breathing lock on a still person may be difficult if a moving person is closer to the
sensor due to multiple direct path and multi path reflections from the closest moving person.
Normalized Movement Interval Slow and Normalized Movement Interval Fast are intended to
show how much movement a sleeping or still person has, without having to identify where in the
Detection Zone the target person is.
4.3.3 IO-pin Functionality

All units are shipped with IO-pin functionality off (inputs with pull-up).
When enabling IO-pins, the default functionality is:
Default IO-pin functions when enabled

IO-pin Name Direction Functionality
IO1 MOVEMENT Output Low: Movement, Movement Tracking and Breathing

states (Driven low)
High: No Movement, Initializing and Unknown states (Tri-

state with internal pull-up)
IO2 BREATHING Output Low: Breathing state (Driven low)
High: All other states than Breathing (Tri-state with

internal pull-up)
IO3 Input Not in use. Do not connect

IO-pin Name Direction Functionality
Each IO-pin has the following Pin Setup options:
Input or output
Open drain or push-pull
Active high or active low
Pull-up enable or disable
Each IO-pin can have one of these Pin Features:
Disable all IO-pins. Using this feature overrides Pin Setup. Disabling all IO-pins means all IO-
pins are input with pull-up.
According to default functionality shown above. Using this feature overrides Pin Setup.
Default IO-pin functionality also specifies which pins are inputs and outputs.
Passive. Set and get IO-pin level over communication interface.
Movement. Function as described in table above, but can be set to any pin.
Breathing. Function as described in table above, but can be set to any pin.
4.4 Detection Range

Detection range varies with the size of the target person and the angle between the sensor and
the target person. The detection range varies with the size of the target person, the movement
type of the target person and the angle between the sensor and the target person.
Detection range should not be confused with the user setting Detection Zone. Detection Zone
defines at what range X4M200 is doing measurements. Detection range describes what can be
detected inside the Detection Zone.
Characterization of detection range for various targets will be included here when available.
4.5 Detection Time

Typical detection time for this Profile is:
From No Movement to Movement state: 3.5 - 9 seconds

From Movement to No Movement state: 5 seconds + length of Slow Pulse-Doppler
algorithm.
From Movement to Breathing state: 5 seconds + length of Slow Pulse-Doppler algorithm.
Detection time is given by the length of the range-Doppler matrices and the M/N detection logic
described in the Firmware Algorithm section below.

4.6 Firmware Algorithms
Adult Respiration Profile signal processing block diagram
All firmware algorithms for movement detection and respiration measurements are running in the
X4M200. The X4 UWB radar SoC is set up to provide 17 baseband data frames per second. The
radar data frames are stored in a buffer. Two Range-Doppler matrices are running in parallel. The
Slow and Fast Range-Doppler matrices are using data from different periods of radar frames.
Length of Slow and Fast periods may vary between Profiles and are shown above in the table
Profile Settings.
Both Range-Doppler matrices have individual Noise Maps to determine if a reflection at a certain
distance and frequency is above a threshold. Creating and enabling a Noise Map will give
different threshold values at different distances and frequencies.
The Noise Maps will adapt to changes in the environment unless User Setting Noise Map
Adaptation is off. Noise Map Adaptation works continuously and will over time remove presence
detection of reflectors with small movement at a fixed distance. The Noise Map will not adapt if a
still person with breathing frequency matching the RPM Range specified in the Profile Settings
table above is detected.
The Fast Range-Doppler matrix with its Fast Movement Detector will detect presence quickly,
typically when a person enters the Detection Zone. The Fast Movement Detector has two states,
Movement or No Movement. The Fast M/N Combiner uses these states to determine the
LocalStateFast. An M/N Combiner determines that M out of N detections need to be a certain
value for the output to change.
All detection algorithms are run once per second, meaning all outputs like State, Distance, RPM
etc. are updated once per second.
Logic for Fast M/N Combiner

LocalStateFast M/N
No Movement -> Movement 3/3
Movement -> No Movement 5/5

The Slow Range-Doppler matrix with its Slow Movement Detector and Respiration Detector will
detect presence of stationary people and measure respiration rate and distance to the breathing
target when the target person is still. The Slow Movement Detector and Respiration Detector
have three states, Breathing, Movement and No Movement. The Slow M/N Combiner uses these
states to determine the LocalStateSlow. An M/N Combiner determines that M out of N detections
need to be a certain value for the output to change.
Logic for Slow M/N Combiner

LocalStateSlow M/N
No Movement -> Movement 3/3
No Movement -> Breathing 3/3
Movement -> No Movement 5/5
Movement -> Breathing 6/7
Breathing -> No Movement 5/5
Breathing -> Movement 4/4
The State Machine determines the (global) State using the following logic.
Global state machine logic

LocalState Fast LocalState Slow Global state
Movement Breathing Breathing
No Movement Breathing Breathing
Movement Movement Movement
No Movement Movement Movement
Movement No Movement Movement
No Movement No Movement No Movement
4.6.1 Default Noise Map

A Default Noise Map is provided with the sensor to achieve fast start-up even when no Noise
Map has been created in the sensor earlier. The Default Noise Map represents a typical Noise Map
for the sensor placed in an environment without reflections.
4.6.2 Stored Noise Map

The Active Noise Map, which is the Noise Map in use by the firmware algorithms, can be stored
locally in the sensor as a Stored Noise Map. If a valid Stored Noise Map exists and the User
Setting Use Stored Noise Map is on, the Stored Noise Map will be used when the Profile is
started.

The Active Noise Map can become different than the Stored Noise Map due to Noise Map
adaption. The Active Noise Map can be stored as the new Stored Noise Map, and the Stored
Noise Map can be loaded as the Active Noise Map during operation of the sensor without
stopping the Profile or disrupting operation of the sensor. The Stored Noise Map can be deleted
without disrupting operation of the sensor. If the Noise Map is stored or deleted during sensor
operation, X4M200 is not able to measure radar frames during the store or delete operation. The
missing radar frames will be replaced with the next valid radar frame. For signal processing
algoithms running in X4M200, these missing radar frames will have insignificant effect of the
sensor performance.
To initialize a new Noise Map, delete the Stored Noise Map, and then stop and start the Profile
with User Setting Use Store Noise Map on. A new Noise Map will then be created during
Initialization, unless User Setting Use Default Noise Map is on, which dictates use of the Default
Noise Map.
Only one Stored Noise Map can be saved in the sensor.
The Stored Noise Map can be read and stored by the host and a new Stored Noise Map can be
loaded over the serial interface.
4.6.3 Start-up Time

The Range-Doppler matrices are filled with radar data during Initialization state. This takes 15-20
seconds for the Slow Range-Doppler matrix, depending on which Profile is used. See Profile
Settings table above for details. Total start-up time is 120 seconds when a Noise Map needs to be
created and equals the length of the Slow Range-Doppler matrix if a Default Noise Map or Stored
Noise Map is used.
4.7 Baseband Data Output

Baseband data is generated approximately 17 times per second and shows reflection at all
distances in the Radar Frames used in 5.14 cm intervals.
The length and position of Radar Frames is controlled by the actual lower and upper range
determined by the Detection Zone User Setting. The Radar Frame starts 5.14 cm before the
actual lower range and ends 5.14 cm after the actual upper range.
Baseband data is available as an option on the communication port.
Baseband data outputs either amplitude and phase information of reflections, or the same data
represented with I and Q values.
A Frame Counter is supplied with the Baseband Data. The Frame Counter increases by 1 for each
radar frame that is output from the X4 UWB radar SoC. Stopping and starting a Profile does not
reset the frame counter. Size of frame counter is 2^32. The frame counter wraps to 0 when it
reaches the maximum. With 17 frames per second, the max value is reached in approximately 8
years. A reset of the X4 UWB radar SoC or a power toggle of the sensor module will reset the
frame counter.

Example of baseband data output.
The example above shows the amplitude of reflections plotted for a 2 meter Radar Frame. This
particular measurement shows two reflections; the first reflection is about 0.1 meter into the
Radar Frame, which is the directly coupled energy from the TX to the RX antenna, and the
second reflection is about 1.2 meter into the Radar Frame.
Refer to application notes on www.xethru.com for more detailed descriptions on how to use
baseband data output.
4.8 Pulse-Doppler Processing and Range-Doppler Data Output

X4M200 uses Pulse-Doppler processing as described in more detail here: https://en.wikipedia.org
/wiki/Pulse-Doppler_signal_processing.
Pulse-Doppler processing results in Range-Doppler data, which can be output from X4M200. The
data is represented as Range-Doppler matrices that show all reflections at different distances
and frequencies over the last time period as specified in the Firmware Algorithm section for each
Profile. All reflections with Doppler frequency 0 (static reflectors) are removed before the Pulse-
Doppler processing.
5 Certification Mode
5.1 Overview
X4M200 can be set in Certification Mode to test compliance with regulations.
5.2 Certification Modes

Various certification modes can be set either using the communication interface or by using
jumpers or similar to short pins on the 16-pin XeThru Interface Connector.
Certification Jumper Setting Description

Mode

Mode
Tx Only Enables continuous UWB transmission, with all other

activities disabled. Meaning that only the digital
circuitry needed for operating the UWB transmitter,
and the UWB transmitter is enabled. This mode is
used to demonstrate the isolated emissions from the
UWB transmitter, and the emissions generated by the
digital circuitry needed to enable UWB transmission.
The UWB transmitter must be set to continuous
worst case transmission, i.e. that a pulse is sent at
every PRI interval for the given chip setting, to
maximize the average energy emitted from the
module. LED is off in this mode to minimize noise.
Tx Only Enables only the digital part used for continuous

Digital UWB transmitting, with all other activities disabled.
The exact same settings as Tx only mode is used, but
with the UWB transmitter disabled. This mode
demonstrates radiated emissions from digital
circuitry used to enable operation of the UWB
transmitter. These emissions should comply with FCC
15.521, § 15.209. LED is off in this mode to minimize
noise.
Stream Tx Disables continuous UWB transmitting, while

Off associated digital devices used to control additional
functions or capabilities on module is operating. This
mode is used to demonstrate emissions from
unintentional radiators not needed for, or generated
by, UWB transmission. LED is orange in this mode.
Stream Normal operation of the module with both UWB

transmitter and associated digital devices, used to
control additional functions or capabilities on
module, activated. This mode is used to demonstrate
typical emissions from a module during normal
operation. LED is orange in this mode.

Mode
Rx Fail In normal operation, the FW monitors the sampler

Detection outputs to ensure acknowledgement of reception. If
no such acknowledgement is received, the EUT will
shut down the transmitter within 10 seconds.
During certification test, this situation can be

provoked / emulated by forcing the receiver to not
provide an acknowledgement of reception. The
procedure is as follows: 1. Power off the device. 2. Set
the EUT in Stream mode by the appropriate jumpers
(11/12 and 15/16). 3. Power up the device by
connecting the USB cable. The EUT should now
emulate normal operation. 4. Set RX Fail emulation
jumper (13/14), this will emulate a missing
acknowledgement within 3 seconds. 5. TX should
now be shut down by the standard FW.
Alternatively, all three jumpers may be set in step 2

and then power up and omit step 4. The EUT will
start transmitting and within maximum 10 seconds
shut down. LED is orange in this mode.
End Setting this jumper setting while the device is

Certification powered will return the module to normal operation
Test after the execution of a power cycle. The module will
then respond to the normal API over USB. Note that
the EUT may be brought back to any other test mode
by the appropriate jumper setting. LED is orange in
this mode.
6 Firmware versions
The firmware version can be read over the serial interface. All firmware versions support
upgrading to a different firmware version.
In addition to the firmware versions described in this section, additional firmware versions with
potential error corrections and stability improvements should be expected.
6.1 X4M200 Version 1.2.1

The following functions are supported:
Baseband data
Distance to closest target
Distance to breathing target
RPM for closest target
RCS for closest target
MovementFast and MovementSlow data
Store Noise Map to sensor

Delete Stored Noise Map in sensor
Use Stored Noise Map
Noise Map always enabled
Noise Map always adapts
Only the low frequency band can be used
Baby Respiration Profile has limited testing on real babies and children. This Profile should be
used for evaluation only with this FW version.
6.2 X4M200 Version 1.3.1

Added features from previous version:
Breathing pattern of closest breathing target

Pulse-Doppler data output
Baby Respiration Profile has limited testing on real babies and children. This Profile should be
used for evaluation only with this FW version.
6.3 X4M200 Version 1.4.7

GPIO functions
USRT communication mode
See errata section for bug fixes. Baby Respiration Profile has limited testing on real babies and
children. This Profile should be used for evaluation only with this FW version.
6.4 X4M200 Version 1.5.10

Added features from previous versions:
Selection between low and high frequency band

Get calls to protocol interface added (get_output_control, get_led_control,
get_iopin_control, get_sensitivity)
6.5 X4M200 Version 1.6.6

The User Setting "Initialize Noise Map at Reset" has been renamed to "Use Stored Noise Map".
Communication protocol is not affected by this change, thus any software controlling this User
Setting for previous FW version will behave exactly the same with this and future FW versions.
Respiration_4 and Respiration_5 Profiles added

Use Default Noise Map added
Delete Noise Map protocol command added (delete_noisemap)
Normalized Movement added
See errata section for bug fixes.

6.6 X4M200 Version 1.6.8
See errata section for bug fixes.
6.7 Future versions of X4M200

The additional functions may be introduced in existing Profiles:
Enable / disable Noise Map adaption (Previous versions always enable Noise Map
adaption)
Load a Stored Noise Map into Active Noise Map in sensor
Load and Store Stored Noise Map to host
Some of these features may be introduced as a new Profile not yet documented in this datasheet.
Detection list for all moving targets in detection zone

RPM for multiple targets in detection zone
Radar Cross Section for all moving targets in detection zone
7 X4M200 HW Revisions
X4M200 uses the X4M02 hardware. This section describes all HW revisions of X4M02 that has
been used in production, the difference between them and how to identify what HW revision
your X4M200 is.
Some FW versions may require a specific HW revision. If applicable, this will be described in the
FW version section of this datasheet.

7.1 Identifying HW revision
How to identify HW revision of X4M02
7.2 X4M02 Revision 4

Initial HW revision used for production of X4M300.

Added WiFi filter on Tx antenna.
Functionality is identical with previous HW revisions.

Initial HW revision used for production of X4M200.
MCU change from 1MB to 2MB version.

This HW revisions is required to meet the requirements for FCC and ETSI regulation.
Added metal shield box on X4 UWB radar SoC.

Replaced 12 MHz crystal with 12 MHz oscillator.
Added components for EMI suppression.
Added additional decoupling for MCU and SDRAM.
Added filter on VDDPLLUSB domain.
Improved MCU power delivery routing.
Increased thickness of inner copper layers from 17 to 35 µm.
8 Software Resources
8.1 XeThru Explorer
The XeThru Explorer application is a visual presentation of the protocol and data output from the
sensor. It also allows for storing the measured data into a log file.
Firmware upgrades of X4M200 are deployed with new versions of XeThru Explorer.
XeThru Explorer can be downloaded from www.xethru.com.
8.2 XeThru Module Connector

The XeThru Module Connector is a software used to communicate with all XeThru radar sensor
modules from a host computer through a serial interface. XeThru Module Connector makes a
complete API of the modules available in host environments such as MATLAB, Python, C++ and
C. This makes it easy to start streaming and analyzing radar data on multiple levels (raw radar
data, baseband data, pulse doppler data, detection lists, respiration and presence) and directly to
an environment ideally suited for development of new algorithms.
XeThru Module Connector includes a SW API that implements the serial protocol of X4M200.
XeThru Module Connector can be downloaded from www.xethru.com.
8.3 Module Communication Protocol Wrapper (MCP Wrapper)

Module Communication Protocol (MCP) is the lowest level communication protocol
implementation for the XeThru modules, used on the module FW and XeThru host components, e.
g. Module Connector. The MCP Wrapper goes one step further for embedded host
implementation adding a wrapper with convenience methods around the MCP. Compared to
Module Connector, which is a more feature rich component with logging and buffering
capabilities, MCP Wrapper offers a similar interface with only the basic transport methods
wrapped in a more easy-to-use interface.
Typical use for the MCP Wrapper is when implementing a host application communicating with a
XeThru module on an embedded target that does not need or have the Module Connector
available .
MCP Wrapper is implemented in C. Example code is available in C and C++.
MCP Wrapper can be downloaded from www.xethru.com.

8.4 X4M200 Firmware Binary
Firmware upgrades of X4M200 can be done by using Module Connector, MCP Wrapper or any
other custom implementation of the serial protocol in a scenario where the modules are
deployed. In this case, the module firmware file that is used during firmware upgrade is needed.
X4M200 firmware binary (Annapurna) can be downloaded from www.xethru.com.
9 Mechanical Data
Mechanical drawing of the sensor module (in mm)
10 Electrical Specification
Parameter Value Comment
Supply Voltage VDD_EXT 3.3 - 5.5V
Supply Voltage USB 4.5 - 5.5V
IO-voltage range, nominal -0.3 - 3.3V
VIH min 2.0V Minimum input high threshold voltage
VIL max 0.8V Maximum input low threshold voltage

Parameter Value Comment
Typical power consumption TBD mW Expected around 600 mW
Operating Temperature range 0°C to +85°C
11 X4M200 Interface Options

11.1 16-pin XeThru Interface Connector
The X4M200 has a 16-pin connector intended for interfacing a host board.
11.1.1 Pin Descriptions
Pin descriptions
Pin Description Name Type Usage
no
1 Power, 3.3- VDD_EXT Power Module power input

5.5V
2 Power, GND Power Module power input

GND
3 USART RX / RX / BOOT Input USART receive /

Force Holding pin 3 low during reset or power-up will
Bootloader force the unit into bootloader mode
4 USART TX TX Output USART transmit
5 MODE MODESEL1 Input Mode select pin 1, ref table below for details /
SELECT 1 / with pull-
USART up USART serial clock (USRT mode only)
SCK
6 MODE MODESEL2 Input Mode select pin 2, ref table below for details
SELECT 2 with pull-
up
7 Reset nRESET Input Active low module MCU reset

with pull-
up
8 No N.C N/A Leave unconnected

Connect

Connect

Connect
11 IO1 IO1 I/O Functionality is Profile specific

Pin Description Name Type Usage
no
The connector is a 2x8 2.00mm pitch male pin header.
11.2 USB Connector

The X4M200 is fitted with a USB micro type B connector type supporting USB 2.0 High Speed.
11.3 Communication Modes

The sensor module will always use USB communication if USB power is present.
Additional communication modes can be selected at power-up or reset. The procedure is as

follows seen from the host system outside the sensor:
1. Assert nRESET (set low for at least 1ms)

2. Set communication mode according to table below on pin 5 and 6.
3. Release nRESET (set high)
4. Hold communication mode level for minimum 2 seconds.
5. Set IO configuration of pins 3, 4, 5 and 6 to comply with the selected communication
mode.
6. Selected communication is now activated on the sensor module
When USB is used this takes precedence over the table below. The use of USB is detected by the
presence of power at the USB 5V power wire at startup. To change communication mode
X4M200 need to be reset.
Mode MODESEL1 MODESEL2 Comments

(Pin 5) (Pin 6)
Reserved Low Low Not supported
Reserved Low High Not supported
USRT High Low X4M200 is USRT slave
UART High/Open High/Open Default UART settings are 115200 baud rate, 8 data
(*) (*) bits, 1 stop bit, no parity
This is the default mode. Enabled when pin 5 and pin

6 are left open.
(*) MODESEL1 and MODESEL2 has pull-up resistors and can be left open if a "High" is required.
Not supported modes should not be selected. Future firmware versions may use these modes.

11.4 Power System
There are 2 possible ways to power the sensor: Through pins 1 and 2 on the 16-pin interface
connector or via USB. Both power sources may be connected at the same time. When powering
via the USB connector this will always take precedence over the 16-pin connector.
12 Schematics and Bill of Material

Schematics and Bill of Material for X4M200 is available from www.xethru.com.
13 Module User Guide

13.1 Placing the Sensor Module
The sensor module should be protected from environmental surroundings such as moisture. Most
firmware algorithms assume the sensor to be still with no movement or vibrations during
operation.
When placing the sensor, pay attention to the following:
Point the sensor in the direction of the object or zone to monitor

Be aware of indirect reflections. An object 1 meter away may also give additional
reflections via the floor, the ceiling or walls at longer distances
Nearby metallic objects should be avoided, especially in the signal path to the sensor's
observation area
The sensor can be placed on static (non-moving) surfaces such as:
On a desk
On a wall
Behind a wall (*)
In the ceiling
Behind the ceiling (*)
Firmware algorithms in the sensor module are sensitive to vibrations. If vibrations occur, the
sensor may report movement in an empty detection zone.
If a sensor casing is required, the material should be of a kind that does not attenuate the high
frequency signals in the sensor´s main direction. Recommended materials are ABS and other
types of non-conductive plastics (*).
(*): Different materials will attenuate the signal. Application note regarding this topic is found at
www.xethru.com.
13.2 Connecting the X4M200 to a host system

The X4M200 can be connected to a host system in several ways:
1. Via USB
2. Via the interface connector using the UART interface
3. Via the interface connector using the USRT interface. X4M200 will be a USRT slave.

Some Profiles have GPIO interface that can be enabled and operate as the only control interface
for a sensor module. The GPIO interface is described in the Profile chapters of this datasheet.
Bootloader for firmware updates only supports USB and UART.
13.2.1 Interfacing via USB

When interfacing via USB this interface will take presence over other interfaces.
13.2.2 Interfacing via UART
Simplified schematics of host MCU using UART mode
13.2.3 Interfacing via USRT

The USRT mode is using a clock line in addition to RX and TX lines.

Simplified schematics of host MCU using USRT mode
13.2.4 Reset control of X4M200

Reset control from host is required for:
Force bootloader function

Exit from certain certification modes
Selecting communication mode. UART is used if communication mode is not selected.
13.3 Upgrading the Firmware Using the Bootloader

The module´s firmware may be updated over USB or UART.
LED will be purple during firmware upgrades.
14 Regulatory Approval
X4M200 is designed to meet UWB RF specifications of ETSI (Europe), FCC (USA) and ISED
(Canada).
Some regulatory specifications also specify how the sensor is used. Users of X4M200 must check
regulatory requirements for their own use case and determine whether the regulatory approvals
obtained from Novelda are sufficient for their product.

14.1 CE / ETSI Approval
English:
Hereby, Novelda AS declares that the radio equipment type X4M200 is in compliance with
Directive 2014/53/EU. The full text of the EU declaration of conformity is available below.
Suomi:
Novelda AS vakuuttaa, etta radiolaitetyyppi X4M200 on direktiivin 2014/53/EU mukainen. EU-
vaatimustenmukaisuusvakuutuksen koko teksti on saatavilla alla.
Nederlands:
Hierbij verklaar ik, Novelda AS, dat het type radioapparatuur X4M200 conform is met Richtlijn
2014/53/EU. De volledige tekst van de EU-conformiteitsverklaring is hieronder beschikbaar.
Francais:
Le soussigne, Novelda AS, declare que l’equipement radioelectrique du type X4M200 est
conforme a la directive 2014/53/UE. Le texte intégral de la déclaration de conformité de l'UE est
disponible ci-dessous.
Svenska:
Härmed försäkrar Novelda AS att denna typ av radioutrustning X4M200 överensstämmer med
direktiv 2014/53/EU. Den fullständiga texten till EU-försäkran om överensstämmelse finns nedan.
Dansk:
Hermed erklarer Novelda AS, at radioudstyrstypen X4M200 er i overensstemmelse med direktiv
2014/53/EU. EU-overensstemmelseserklæringens fulde tekst kan findes nedenfor.
Deutsch:
Hiermit erklart Novelda AS, dass der Funkanlagentyp X4M200 der Richtlinie 2014/53/EU
entspricht. Der vollständige Text der EU-Konformitätserklärung finden Sie weiter unten.
Ελληνικά:
Με την παρούσα ο/η Novelda AS, δηλώνει ότι ο ραδιοεξοπλισμός X4M200 πληροί την οδηγία
2014/53/ΕΕ. Το πλήρες κείμενο της δήλωσης συμμόρφωσης της ΕΕ είναι διαθέσιμο παρακάτω.
Italiano:
Il fabbricante, Novelda AS, dichiara che il tipo di apparecchiatura radio X4M200 e conforme alla
direttiva 2014/53/UE. Il testo integrale della dichiarazione di conformità dell'UE è disponibile
sotto.
Espanol:
Por la presente, Novelda AS declara que el tipo de equipo radioeléctrico X4M200 es conforme
con la Directiva 2014/53/UE. El texto completo de la declaración de conformidad de la UE está
disponible a continuación.
Portugues:
O(a) abaixo assinado(a) Novelda AS declara que o presente tipo de equipamento de radio
X4M200 esta em conformidade com a Diretiva 2014/53/UE. O texto completo da declaração de
conformidade da UE está disponível abaixo.
Čeština:
Timto Novelda AS prohlašuje, že typ radioveho zařizeni X4M200 je v souladu se směrnici 2014/53
/EU. Úplné znění prohlášení o shodě EU je k dispozici níže.

Eesti:
Kaesolevaga deklareerib Novelda AS, et kaesolev raadioseadme tuup X4M200 vastab direktiivi
2014/53/EL nouetele. ELi vastavusdeklaratsiooni täielik tekst on allpool.
Magyar:
Novelda AS igazolja, hogy a X4M200 tipusu radioberendezes megfelel a 2014/53/EU
iranyelvnek. Az EU-megfelelőségi nyilatkozat teljes szövege az alábbiakban található.
Latviešu valoda:
Ar šo Novelda AS deklarē, ka radioiekārta X4M200 atbilst Direktīvai 2014/53/ES. ES atbilstības
deklarācijas pilns teksts ir pieejams zemāk.
Lietuvių kalba:
Aš, Novelda AS, patvirtinu, kad radijo įrenginių tipas X4M200 atitinka Direktyvą 2014/53/ES.
Visas ES atitikties deklaracijos tekstas pateikiamas toliau.
Malti:
B’dan, Novelda AS, niddikjara li dan it-tip ta’ tagħmir tar-radju X4M200 huwa konformi mad-
Direttiva 2014/53/UE. It-test sħiħ tad-dikjarazzjoni ta 'konformità tal-UE huwa disponibbli hawn
taħt.
Slovenčina:
Novelda AS týmto vyhlasuje, že rádiové zariadenie typu X4M200 je v súlade so smernicou 2014
/53/EÚ. Úplné znenie vyhlásenia o zhode EÚ je k dispozícii nižšie.
Slovenščina:
Novelda AS potrjuje, da je tip radijske opreme X4M200 skladen z Direktivo 2014/53/EU. Celotno
besedilo izjave EU o skladnosti je na voljo spodaj.
Romană:
Prin prezenta, Novelda AS declară că tipul de echipamente radio X4M200 este in conformitate
cu Directiva 2014/53/UE. Textul integral al declarației UE de conformitate este disponibil mai jos.
български:
С настоящото Novelda AS декларира, че този тип радиосъоръжение X4M200 е в
съответствие с Директива 2014/53/ЕС. Пълният текст на декларацията за съответствие на
ЕС е на разположение по-долу.
Polski:
Novelda AS niniejszym oświadcza, że typ urządzenia radiowego X4M200 jest zgodny z
dyrektywą 2014/53/UE. Pełny tekst deklaracji zgodności UE jest dostępny poniżej.
Norsk:
Novelda AS erklærer herved at radioutstyr type X4M200 er i samsvar med direktiv 2014/53/EU.
Den fullstendige teksten i EU-samsvarserklæringen er tilgjengelig nedenfor.
Islenska:
Hér með Novelda AS lýsir yfir að tegund þráðlausan búnað X4M200 er í samræmi við tilskipun
2014/53/ESB. Fullkominn texti ESB samræmisyfirlýsing er að finna hér að neðan.
Hrvatski:
Novelda AS ovime izjavljuje da je radijska oprema tipa X4M200 u skladu s Direktivom 2014/53
/EU. Cijeli tekst izjave o sukladnosti EU-a nalazi se u nastavku.
Turk:
Burada, Novelda AS radyo ekipmanı türünün X4M200 2014/53/EU direktiflerine uyumlu
oldugunu beyan eder. AB uyumu beyanının tam metni aşağıda verilmektedir.

14.1.1 EU Declaration of Conformity
X4M200 EU Declaration of Conformity

14.2 FCC Approval
X4M200 has Modular FCC approval, which means it can be used in an end product without
obtaining new authorization for the end product with regard to use of UWB radar.
The X4M200 module meets FCC Part 15 requirements for UWB transmission equipment intended
for unlicensed indoor use or outdoor use when not permanently installed as specified in FCC Part
15.519, 15.521 and 15.209.
FCC ID: 2AD9QX4M02.
14.2.1 X4M200 Block Diagram
Module clock and power system

Clocks:
The systems clocks are derived from a 12 MHz crystal oscillator connected to the main
microcontroller, and a 27 MHz oscillator connected to the Novelda X4 UWB impulse radar chip.
The communication between the microcontroller and the X4 radar chip uses SPI protocol. The
SPI communication clock is set up to run at 50 MHz.

Mean output power and frequency of the X4M200 depends on the Pulse Repetition Frequency
(PRF), tx_power and Transmitter (TX) center frequency settings in the X4 radar chip. PRF must
be set to 15.1875 MHz, tx_power must be set to Medium (2), and the TX center frequency must be
set to 7.29 GHz by the host system to be in compliance with FCC regulations. For further
description of the X4 radar chip, please refer to the X4 datasheet.
Power:
The module is powered externally from either the USB port or an external power supply. If both
power sources are connected, the USB takes precedence over the external power.
Antennas:
The antennas are embedded onto the PCB and cannot be changed by users. Please refer to the
Antenna chapter in the X4M02 datasheet for details on the antennas.
14.2.2 Radar Functional Description

The module uses the Novelda X4 impulse radar chip. Please refer to the X4 datasheet for a
detailed description.
14.2.3 FCC Regulatory Notices

Modification Statement
Novelda AS has not approved any changes or modifications to this device by the user. Any
changes or modifications could void the user’s authority to operate the equipment.
Interference Statement
This device complies with Part 15 of the FCC Rules. 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.
RF Exposure Safety
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled
environment. This transmitter must not be co-located or operating in conjunction with any other
antenna or transmitter.
The X4M02 is a radio transmitter and receiver.
It is designed not to exceed the emission limits for exposure to radio frequency (RF) energy set
by the Federal Communications Commission.
FCC Class B Digital Device Notice
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 cause harmful
interference to radio or television reception, which can be determined by turning the equipment
off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:

Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver
is connected.
Consult the dealer or an experienced radio/TV technician for help.
Labelling Requirements for the Host Device
The host device shall be properly labelled to identify the modules within the host device. The
certification label of the module shall be clearly visible at all times when installed in the host
device, otherwise the host device must be labelled to display the FCC ID of the module,
preceded by the words "Contains transmitter module", or the word "Contains", or similar wording
expressing the same meaning, as follows:
Contains FCC ID: 2AD9QX4M02
UWB devices may not be employed for the operation of toys. Operation on-board an aircraft, a
ship or a satellite is prohibited.
14.3 ISED Approval

X4M200 is approved by Innovation, Science and Economic Development Canada (ISED),
previously known as Industry Canada.
Certification Number: 22782-X4M02
14.3.1 Regulatory Information Canada

Changes or modifications not expressly approved by the party responsible for compliance could
void the user’s authority to operate the equipment.
Les changements ou modifications non expressément approuvés par la partie responsable de la

conformité pourraient annuler l'autorisation de l'utilisateur d'utiliser l'équipement.
This device complies with Industry Canada’s licence-exempt RSSs. 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.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio
exempts de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne
doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage
radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.
14.3.2 RF Exposure Safety

The X4M02 is a radio transmitter and receiver.
It is designed not to exceed the emission limits for exposure to radio frequency (RF) energy set
by the ISED.
Le X4M02 est un émetteur et un récepteur radio.

Il est conçu pour ne pas dépasser les limites d'émission pour l'exposition à l'énergie
radiofréquence (RF) établie par l'ISDE.
14.3.3 Labelling Requirements for the Host Device

The host device shall be properly labelled to identify the modules within the host device. The
certification label of the module shall be clearly visible at all times when installed in the host
device, otherwise the host device must be labelled to display the IC of the module, preceded by
the words "Contains transmitter module", or the word "Contains", or similar wording expressing
the same meaning, as follows:
Contains IC: 22782-X4M02
Le’équipement hôte doit être correctement étiqueté pour identifier les modules dans l’
équipement. L'étiquette de certification du module doit être clairement visible en tout temps
lorsqu'il est installé dans l'hôte, l’équipement hôte doit être étiqueté pour afficher l'IC du module,
précédé des mots "Contient le module émetteur", ou le mot "Contient", ou un libellé similaire
exprimant la même signification, comme suit:
Contains IC: 22782-X4M02
CAN ICES-3 (B)/NMB-3(B)
15 Errata
15.1 Firmware Version 1.2.1
RPM may lock on second harmonic frequency of the respiration frequency. Future FW
upgrades are planned to improve this.
RPM frequencies higher than maximum for a Profile (30 or 65 depending on Profile) may
report as a frequency below the maximum value. Future FW upgrades are planned to
improve this.
RPM frequencies lower than minimum for a Profile (8 or 15 depending on Profile) may
report as a frequency above the minimum value. Future FW upgrades are planned to
improve this.
Distance to breathing target may occasionally report a longer distance due to lock on multi
path reflections. Future FW upgrades are planned to improve this.
Memory leak in firmware may cause X4M200 to enter Fail Safe Mode.
Workaround: Toggle power or send a module reset command.
Any reset, including intentional reset commands from a host, will cause the reset counter
to increase. Fail Safe Mode may trigger after first reset caused by issues in the firmware if
nine or more reset from any source has been experienced since last power-up.
Workaround: Leave Fail Safe Mode by toggling power or send a module reset
command.
Data messages coming from the sensor has sporadic data corruptions. For application
messages like Sleep and PresenceSingle, the checksum will be invalid. For data messages
using the NoEscape format, there is no checksum in use.
The field trx_dac_step_clog2 in the X4 register trx_dac_step is incorrectly set to value 1,
instead of the correct value of 0. This causes 3dB reduction in the signal-to-noise ratio and
can lead to lower sensitivity for practical applications.

improve this.
improve this.
Any reset, including intentional reset commands from a host, will cause the reset counter
to increase. Fail Safe Mode may trigger after first reset caused by issues in the firmware if
nine or more reset from any source has been experienced since last power-up.
Workaround: Leave Fail Safe Mode by toggling power or send a module reset
command.

improve this.
improve this.
When using UART or USRT communication, the sensor firmware will crash after 1024
received command bytes.
using the NoEscape format, there is no checksum in use. Workaround:

improve this.

improve this.
When using UART or USRT communication, the sensor firmware will crash after 1024
received command bytes.

improve this.
improve this.

improve this.
improve this.
15.7 Errata in X4M02 Revision 6 and lower

USB communication can be unstable. The issue is more frequently observed with Win7, and less
observed with Win10, Raspberry Pi, macOs and Unix.

16 Support and Resources
Development support, resources, links to development partners and resellers can be found on
Novelda's web site www.xethru.com.
17 Disclaimer
Novelda™, XeThru™ and others are registered trademarks or trademarks of Novelda AS. Other
terms and product names may be trademarks of others.
DISCLAIMER: The information in this document is provided in connection with Novelda products.
No license, express or implied, by estoppel or otherwise, to any intellectual property right is
granted by this document or in connection with the sale of Novelda products. EXCEPT AS SET
FORTH IN THE NOVELDA TERMS AND CONDITIONS OF SALES LOCATED ON THE NOVELDA
WEBSITE, NOVELDA ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS,
IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL NOVELDA BE LIABLE FOR ANY
DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES
(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS AND PROFITS, BUSINESS
INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE
THIS DOCUMENT, EVEN IF NOVELDA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. Novelda makes no representations or warranties with respect to the accuracy or
completeness of the contents of this document and reserves the right to make changes to
specifications and products descriptions at any time without notice. Novelda does not make any
commitment to update the information contained herein. Unless specifically provided otherwise,
Novelda products are not suitable for, and shall not be used in, automotive applications. Novelda
products are not intended, authorized, or warranted for use as components in applications
intended to support or sustain life.
SAFETY-CRITICAL, MILITARY, AND AUTOMOTIVE APPLICATIONS DISCLAIMER: Novelda

products are not designed for and will not be used in connection with any applications where the
failure of such products would reasonably be expected to result in significant personal injury or
death (“Safety-Critical Applications”) without a Novelda officer's specific written consent. Safety-
Critical Applications include, without limitation, life support devices and systems, equipment or
systems for the operation of nuclear facilities and weapons systems. Novelda products are not
designed nor intended for use in military or aerospace applications or environments unless
specifically designated by Novelda as military-grade. Novelda products are not designed nor
intended for use in automotive applications unless specifically designated by Novelda as
automotive-grade.


X4M200 Datasheet

Uploaded by

Copyright:

Available Formats

X4M200 Datasheet

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

X4M200 Datasheet

Uploaded by

Copyright:

Available Formats

X4M200 Datasheet

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

X4M200 Respiration Sensor

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

X4M200 X4M200 Respiration Sensor 1 1 1 unit in anti-static bag

MOQ: Minimum Order Quantity

MPQ: Minimum Package Quantity

2 XeThru X4M200 Respiration Sensor

3.1.1 First Power-Up

1. Stop running Profile (if any Profile is running)

3.1.3 Running Sensor Directly from Power-up or Reset

3.3 Firmware Versions

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

3.5 Fail Safe Mode

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

Respiration_2 Adults and 0.40 - 5.00 6 20 8 - 30

Respiration_3 Babies and 0.40 - 5.00 6 15 15 - 65

Respiration_4 Adults and 0.40 - 3.00 6 20 8 - 30 Using internal MCU

Respiration_5 Babies and 0.40 - 3.50 6 15 15 - 65 Using internal MCU

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

4.2.1 Set Detection Zone

Detection zone limits Respiration_2 Respiration_3 Respiration_4 Respiration_5

Minimum start of detection 0.40m 0.40m 0.40m 0.40m

Maximum end of detection 5.00m 5.00m 3.00m 3.50m

Minimum size of detection 0.20m 0.20m 0.20m 0.20m

Maximum size of detection 4.60m 4.60m 2.60m 3.10m

Sensitivity step size 1

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

4.2.4 Frequency Band

4.2.5 Noise Map Control

4.2.6 Use Stored Noise Map

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

4.2.7 Use Default Noise Map

The Default Noise Map will not be used.

4.2.8 Adaptive Noise Map

Disables Noise Map adaptation.

4.2.9 Default User Settings

Default User Settings for the Supported Profiles

LED Full Full Full Full

Frequency Band Low Low Low Low

Use Stored Noise Map Off Off Off Off

Use Default Noise Map Off Off Off Off

Adaptive Noise Map On On On On

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

4.3.1 Detect Presence and Breathing

There are six states in the Respiration Profile:

No Movement No presence detected

4.3.2 Measure Respiration Data

Movement Slow: Movements for the previous Slow period

Distance to closest target: Distance in meters to target closest to the sensor

Novelda AS Copyright © 2018 Novelda AS Rev. E - Preliminary - X4M200 Datasheet

When in Breathing state, the following additional data is measured:

RPM of closest breathing target: Respirations per Minute

4.3.3 IO-pin Functionality

When enabling IO-pins, the default functionality is:

Default IO-pin functions when enabled

IO1 MOVEMENT Output Low: Movement, Movement Tracking and Breathing