Seeedstudio Mr60bha1 Mmwave Breathing And Heartbeat Module User Manual

Seeedstudio Mr60bha1 Mmwave Breathing And Heartbeat Module User Manual

seeedstudio MR60BHA1 mmWave Breathing and Heartbeat Module User Manual
seeedstudio MR60BHA1 mmWave Breathing and Heartbeat Module

Description of the protocol

This protocol is applied to the communication between the company’s radar and the host computer.
This protocol includes the definition of a number of operational commands for the control, testing, upgrading and information query of the radar equipment, as well as a clear definition of the data format and command definitions for the transmission between the radar and the host computer.
The protocol outlines the radar workflow, provides a brief introduction to the interface protocol component architecture, and gives the control commands and data required for the relevant radar operation.

Scope of application of the protocol

This protocol is applicable to the 24G, 60G and 77G series of radar equipment developed by the company.

Explanation of relevant terms

  1. Uplink transmission: transmission of data and commands from the radar to the host computer.
  2. Downlink transmission: transmission of commands or other content from the upper computer to the radar.
  3. Uplink: the communication target corresponding to the radar terminal for radar data reception, radar control and other operations, the uplink may be in the form of a computer, embedded device or web server etc.
  4. Heartbeat packet: a command word that the radar device sends to the application terminal to notify the other party of its status at regular intervals, the default time interval is 1 minute.
  5. OTA: shorthand for remote upgrade.
  6. Data frames: The transmission between the radar and the host computer takes place in data frame mode.

Overview

Radar system organisation

A block diagram of the interface between the radar and the application equipment is shown in the diagram below.
Overview

The radar interface is a serial communication (UART) with a TTL (3.3V) interface level. The interface is converted via an external RS485 interface circuit if required by the user, but the format of the transmitted data remains unchanged.

interface protocol

The interface between the radar module and the application side includes a data interface and a control interface with the following interface parameters.

FunctionControl interfacesNotes
1Interface levelTTL 
2Baud rate9600bps 
3Data bits8 
4Stop bits1 
5Parity CheckNone 

Definition of transmission

Radar data transmission classification

The data transfer between the radar and the host computer includes commands for radar detection, radar testing, parameter queries, OTA upgrades, etc. The categories in turn include two-way interactive communication between the host computer and the radar, respectively.
The main data transmission between the radar and the host computer is shown in the diagram below.

Fig. 1 Radar information transmission architecture
Definition of transmission

Frame format definition

The frame format is defined as shown below.
Frame format definition

Of which:

Serial No.FieldsMarkingLength(B)Description
1Frame headersFH2Fixed to “0x53 0x59″ //”S Y”
2Control charactersCD10x01 – heartbeat pack identification; 0x02 – product information; 0x03 – OTA upgrade; 0x04 – radar test; 0x05 – operating status; 0x06 – radar location information; 0x80 – human presence; 0x81 – respiratory heartbeat.
3Command wordsOD1Identification of the current data content, to be defined
4Length markingL12Equal to DA data length
5DataDA0~2048Byte
6Checksum fieldsCH1Checksum
7End of frameFT2Fixed to “0x54 0x43″ //”T C”

Note: In the above table, the OD content may be defined differently in different radar applications.

Detailed agreement definitions

Parameter classification and address correspondence table 

Serial No.Product categoriesFunction descriptionsDirection of transmissionFrame headersControl charactersCommand wordsLength markingDataCheck -sumEnd of frameNotes
1Heartbeat package parametersHeartbeat Packet EnquiryIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x01
0x01
0x01
0x01
0x0001
0x0001
0x0f 0x0fsum0x54
0x43
0x54
0x43
2Product InformationProduct Model LookupIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x01
0x01
0x0001
len
0x0f Product informationsum0x54
0x43
0x54
0x43
3Product Model SettingIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x02
0x02
len lenProduct information Product informationSum0x54
0x43
0x54
0x43
4Product ID lookupIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x03
0x03
0x0001 len0x0f Product IDSum0x54
0x43
0x54
0x43
5Product ID settingsIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x04
0x04
len lenProduct ID Product IDSum0x54
0x43
0x54
0x43
6Hardware Model LookupIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x05
0x05
0x0001 len0x0f Hardware modelsum0x54
0x43
0x54
0x43
7Hardware Model SettingIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x06
0x06
len lenHardware model Hardware modelSum0x54
0x43
0x54
0x43
8Firmware LookupIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x07
0x07
0x0001
len
0x0f Firmware modelSum0x54
0x43
0x54
0x43
9Firmware model settingIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x08
0x08
len lenFirmware model Firmware modelSum0x54
0x43
0x54
0x43
10Protocol Information LookupIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x09
0x09
0x0001
len
0x0f Protocol informationSum0x54
0x43
0x54
0x43
11Protocol information settingIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x02
0x02
0x0a 0x0alen lenProtocol information Protocol informationsum0x54
0x43
0x54
0x43
12OTA parametersStarting OTA upgradeIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x03
0x03
0x01
0x01
0x0013
0x0001
4Byte firmware package size + 15Byte firmware version number 0x01:Consent to upgrade 0x02:Refuse to upgradeSum 

 

 

0x54
0x43
0x54
0x43

13Upgrade package transmissio nIssuing 0x53 0x59

Response 0x53 0x59

0x53
0x59
0x53
0x59
0x03
0x03
0x02
0x02
0x0404
0x0001
4Byte packet offset address + 1024Byte data packet 0x01:Received successfully 0x02:Reception failuresum0x54
0x43
0x54
0x43
14Ending OTA upgradesIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x03
0x03
0x03
0x03
0x0001
0x0001
0x01:Firmware packet delivery completed 0x02:Firmware packet deliverySum0x54
0x43
0x54
0x43
 
    not completed 0x0f  
15Operating status parametersWorking mode settingsIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x05
0x05
0x01
0x01
0x0001
0x0001
1Byte operating mode
1Byte operating mode
sum0x54
0x43
0x54
0x43
16Working mode enquiryIssuing 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x05
0x05
0x02
0x02
0x0001
0x0001
0x0f 1Byte operating modeSum0x54
0x43
0x54
0x43
17Hours of Work EnquiryIssuing 0x53 0x59
Response 0x53 0x59
Response 0x53 0x59
0x53
0x59
0x53
0x59
0x53
0x59
0x05
0x05
0x06
0x03
0x03
0x09
0x0001
0x0004
0x0002
0x0f Working hours 2Byte FOV angleSum0x54
0x43
0x54
0x43
0x54
0x43
18Human presence radarExistence informationIssuing 0x53 0x590x50
x59
0x800x010x00010x00:Nobody 0x01:occupiedsum0x54
0x43
Report on status changes
19Campaign informationIssuing 0x53 0x590x53
0x59
0x800x020x00010x00:None 0x01:Close 0x02:away 0x03:Disorderly motionsum0x54
0x43
Report on status changes
20Body motion parametersIssuing 0x53 0x59 

0x53
0x59

0x800x030x00011Byte body motion parametersum0x54
0x43
Periodical reporting
21Number of people in the current environmentIssuing 0x53 0x590x53
0x59
0x800x040x00011Byte Number of people informationSum0x54
0x43
Report when numbers change
22Respiratory Heartbeat RadarHeart rate informationIssuing 0x53 0x590x53
0x59
0x810x010x00061Byte heart rate information + 1Byte heart rate value + 4Bytesum0x54
0x43
Heart rate information 0x01:Normal 0x02:Heart rate too high
        heart rate waveform0x03:Heart rate too low
23Respiratory informationIssuing 0x53 0x590x53 0x590x810x020x00061Byte respiratory information + 1Byte respiratory values + 4Byte respiratory waveformssum0x54
0x43
Breathing information 0x01:Normal 0x02:
Hyperventilation 0x03:
Hypopnea
24Respiratory informationIssuing 0x53 0x590x53
0x59
0x810x030x00051Byte position warning + 2Byte standstill distance + 2Byte standstill anglesum0x54
0x43
Warning when a target is detected out of detection range
25Respiratory informationIssuing 0x53 0x590x53 0x590x810x040x00011 Byte Respiratory informationsum 

0x01:Normal 0x02: Hyperv entilati on 0x03: Hyperv entilati on 0x04:D

etectio n in progre ss

26 Respiratory valuesIssuing 0x53 0x590x53 0x590x810x050x00011 Byte Respiratory valuessum
27Respiratory waveformsIssuing 0x53 0x590x53 0x590x810x060x00011 ByteSum0x54
0x43
28Location detection anomaliesIssuing 0x53 0x590x53 0x590x810x070x00011 ByteSum0x54 0x43
29Resting distanceIssuing 0x53 0x590x53 0x590x810x080x00021 ByteSum0x54 0x43
30Stationary angleIssuing 0x53 0x590x53 0x590x810x090x00021 Bytesum0x54

0x43

Note: The Breathing Heartbeat Radar protocol has only been completed for Human Presence Radar and Breathing Heartbeat Radar (29-36), with subsequent functionality to be improved

Data description

Heartbeat data

The total length of the data is 4Byte, temporarily reserved.

Feedback on product models

Equipment complete information query, feedback information including equipment hardware information, firmware information, protocol information, etc., respectively, according to the hardware information feedback, firmware information feedback, protocol information feedback in order to report.
Product model query, feedback the product model, the length is 10Byte.

Product ID feedback

Product ID query to feed back the product ID, 12bit in length.

Hardware information feedback

The length of the hardware feedback is 12Byte and the message specification is given in the Device Coding Specification.

firmware information feedback

The firmware information is 15Byte in length and the information specification is described in the Device Coding Specification.

protocol information feedback

The protocol message length is 8Byte and the message specification is given in the Device Coding Specification.

OTA content transmission

The first 4Byte is the firmware package offset address, followed by 1024Byte of firmware content.

Logo

Documents / Resouces

Download manual
Here you can download full pdf version of manual, it may contain additional safety instructions, warranty information, FCC rules, etc.


Related Manuals