This document describes the communication protocol for a pulse oximeter to communicate with PC software, including:
1. The protocol uses packages of varying lengths to send data in a two-way communication between the device and computer via COM port or wireless transmission.
2. Various package types and data segments are defined for real-time data, storage data, user information, commands, and notifications.
3. Detailed explanations of byte ordering, package formatting, and interpretations of data fields in different package types are provided.
Original Description:
Contec Pule Oximeter Communication Protocol Bluetooth pin 7762
This document describes the communication protocol for a pulse oximeter to communicate with PC software, including:
1. The protocol uses packages of varying lengths to send data in a two-way communication between the device and computer via COM port or wireless transmission.
2. Various package types and data segments are defined for real-time data, storage data, user information, commands, and notifications.
3. Detailed explanations of byte ordering, package formatting, and interpretations of data fields in different package types are provided.
This document describes the communication protocol for a pulse oximeter to communicate with PC software, including:
1. The protocol uses packages of varying lengths to send data in a two-way communication between the device and computer via COM port or wireless transmission.
2. Various package types and data segments are defined for real-time data, storage data, user information, commands, and notifications.
3. Detailed explanations of byte ordering, package formatting, and interpretations of data fields in different package types are provided.
-ZContec Medical System. Communication protocol of pulse oximeter V7.0
Communication Protocol of Pulse Oximeter V7.0
1 Document layout description.
2 Protocol description..
2.1 Communication direction 1
22. Interface description 1
3 Data Format Description. 2
3.1 Byte Description 2
3.2 Package format Description. 2
3.3 Package definition 2
3.3.1 Package types list. 2
3.3.2 Interpretation of the data fields. 4
3.3.2.1 Realtime data package(Table 3). 4
5
5
5
5
6
6
7
3.3.2.2. String data segment
3.3.2.3, Reasoncodes data segment(Table 4).
3.3.2.4 Pl identifiers(Table 5)
3.3.2.5 Storage data (0x0F)
3.3.2.6 Device notice (Table 6)
3.3.27. Command data segment(Table 7)
3.4, Additional instruction
Page 1 ofS 2010-07-08,-ZContec Medical System. Communication protocol of pulse oximeter V7.0
1 Document layout description
Please do not randomly add spaces in the document (Of course, except for the English
word segmentation)
Layout using styles.alignment, indent and so on.
2 Protocol description
This protocol is used for pulse oximeter communicating with PC software
Th SL hat di dd id
detecting retransmission
2.4 Communication direction
Two-way
2.2 Interface description
The communication between device and host computer uses the COM port (or virtual
COM) or wireless mode.
COM port transmission parameters are as follows:
Baud rate:115200
Frame format'Start bit(1);Data bits(B);Stop bit(1):Check bit(no)
Wireless transmission ignores COM port transmission parameters.
3 Data Format Description
3.1 Byte Description
8 bits of 1 byte from high to low are numbered 765 4.3.2.1.
3.2 Package format Description
Data is Sended by package, and each package length which is decided by the data
type is unequal. You can look-up table and the package format is as a part of the protocol
Package format is as follows in Table 1
Byte 0 1 2 Following date
‘Synchronization bit 0 1 1 Allfor 1
Meaning Datatypes | High-byte Package
Bit7 of data type byte is always O, and the other byte Bit7 are always 1
High-byte include the other byte bit7 data in the same package by order, and bit7 must
be transferred from the high-byte before using the data All packages are as this,
3.3 Package definition
3.3.1 Package types list
There are two kinds of package currently used,and they are uplink (From device to PC)
and downlink(Fram PC to device). Uplink data packages code up from 0x01 and downlink
data packages code down from Ox7E
Package types are as follows in Table 2:
Data description | Directlo | Len Res
Type | Coy {starting from byte 2) n— | gth ency | non
Page 20f8 2010-07-08,-ZContec Medical System. Communication protocol of pulse oximeter V7.0
se
Realtime Real-time data 6042
data 0x01 | ackage(7byte) Uplink | 9 | packages/sec
Device By request
0x04 | String(7byt Uplink | 9
identifiers | °™ ring(7byte) en (send 1)
User User index number(t byte) By request
x05 Uplink | 9
Information | "> | string(6byte) eum (send 1)
on | Sys
start 0x07 9° seg Uplink | a | -Y9
heotdat number(tbyte) High-year, (send 1)
ime(date) Lower-year, Month, Day
swom | [ocr Sys
start oxt2 9° seg Uplink | a | -Y9
timettime) number(t byte), Hour, (send 1)
Minute, Second, Invalid byte
User index number (Tbyte),
storage Data segment number.Low, by coquest
‘te ee th | 0208 | The second lowest,The Uplink | 8 (cond)
9 second highest, High
(32-bit nonnegative)
Storage | gyog | SPO2 Pulse rate.Pllow.Pl | 4, | g | Send data
data high completely
Storage
data xan, | User index number, Uotinx | 4 [Bysequest
segment Segment amount (send 1)
amount
c d By request
fouthech 0x08 | Command, Reason code Uplink | 4 (cond)
Free Device is free
feedback | MC | No Uplink | 2 | currently
When device
D R de(Sent by th
isconnect | 4 op | Reason code(Sent by the Uplink | 3. | disconnectes
notice device to disconnect )
initiativ ely.
PI Whether to support Pl in By request
Owe Uplink | 3
identifiers realtime data eum (send 1)
Page 30f8 2010-07-08,