SR226 Communication Protocol V3.26
API User Manual
Wuhan Lakeda Science And Technology Co., Ltd.
Table of Contents
1. Overview
The SR226 Communication Protocol defines the UDP-based interface between the Radar and the PC terminal for the “XW/SR226-6000XP” security radar series.
It covers:
- Link commands
- Parameter control
- Track data
- Heartbeat packets
- Parameter data
2. Communication Protocol
- Radar and PC must be on the same subnet.
- UDP datagram protocol is used with Little Endian byte order.
- Communication flow:
- PC sends Link Command.
- Radar acquires PC IP/Port.
- Radar reports Track Data and Heartbeat Packets.
Two message types:
- PC → Radar: Control commands (Link, Parameter Control)
- Radar → PC: Report messages (Track Data, Heartbeat, Parameter Data)
2.1 Control Commands (PC → Radar)
2.1.1 Link Command
- The PC sends a 10-byte fixed link command.
- Radar responds with Track Data and Heartbeat Packets.
- Radar default IP:
192.168.0.100
, Port:12580
. - Send once per minute.
Link Command Format (10 bytes):
Byte Offset | Field | Length | Format | Description |
---|---|---|---|---|
0–9 | FrameHead | 10 | char | Fixed: 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA |
2.1.2 Parameter Control
Used for querying or modifying radar parameters.
General Message Format (32 bytes):
Byte Offset | Field | Length | Format | Description |
---|---|---|---|---|
0–3 | FrameHead | 4 | uint | Fixed 0xAA 0xAA 0xAA 0xAA |
4 | InfoType | 1 | byte | Fixed 0x0B |
5–7 | Reserved | 3 | byte | Default 0x00 |
8 | ParameterType | 1 | byte | 1–255 (see list below) |
9 | DeviceType | 1 | byte | Fixed 0x01 |
10 | FaceID | 1 | byte | Fixed 0x00 |
11 | Checksum | 1 | byte | Sum of bytes 9–24 |
12–15 | Reserved | 4 | byte | Default 0x00 |
16–19 | Parameter1 | 4 | varies | Depends on type |
20–23 | Parameter2 | 4 | varies | Depends on type |
24–27 | Parameter3 | 4 | varies | Depends on type |
28–31 | Parameter4 | 4 | varies | Depends on type |
Parameter Type List:
1 – Status Query
- Param1: Device type (fixed
0x01
) - Param2: Status type (0–255, see Section 2.2.3 Table 5-1)
- Param3/4: Default
0
- Param1: Device type (fixed
2 – GPS & Orientation
- Param1: Latitude (float, -90° to +90°)
- Param2: Longitude (float, -180° to +180°)
- Param3: Altitude (float, -500m to +10,000m)
- Param4: Azimuth (float, 0–360°)
11 – Threshold Settings
- Param1: Detection Threshold (float, 11.0–40.0 dB)
- Param2: High-Speed Threshold (float, 1.0–40.0 m/s)
- Param3: Low-Speed Threshold (float, 0.0–10.0 m/s)
- Param4: Reserved
20 – Single Frame Command
- Param1: Command header (0xA5), ID (0x10), Type (0x01), Address + Data1–4
- Param2: Data5–8
- Param3: Frame ID
- Param4: Checksum
21 – Sector Parameters
- Param1: Start Angle (byte, 0–255, unit 1.4063°)
- Param1: End Angle (byte, 0–255)
22 – Silence Zone Parameters
- Param1–2: Define up to 4 angular silence zones (start/end angles, 0–255)
2.2 Report Messages (Radar → PC)
2.2.1 Track Data
Radar continuously sends track reports after receiving a link command.
Track Data Format (per packet, variable size):
Byte Offset | Field | Length | Format | Description |
---|---|---|---|---|
0–3 | FrameHead | 4 | uint | Fixed 0xAA 0xAA 0xAA 0xAA |
4 | InfoType | 1 | byte | 0x01 |
5–6 | Reserved | 2 | byte | / |
7 | DeviceType | 1 | byte | Fixed 0x01 |
8–9 | TrackCount | 2 | ushort | Number of tracks (0–999) |
10–11 | Reserved | 2 | byte | / |
Then, per target (79 bytes each):
Field | Length | Format | Description |
---|---|---|---|
Batch ID | 4 | uint | Track batch number |
Azimuth | 4 | float | 0–360°, ° |
Range | 4 | float | meters |
Latitude | 4 | float | -90° to +90° |
Longitude | 4 | float | -180° to +180° |
Radial Velocity | 4 | float | m/s |
Exist Flag | 2 | byte | 0 = disappeared, 1 = exist |
Elevation | 4 | float | ° |
Heading | 4 | float | ° |
Speed | 4 | float | m/s |
Altitude | 4 | float | m (relative) |
Timestamp | 4 | uint | ms since day start |
Amplitude | 2 | ushort | 0.1 dB |
Category | 1 | byte | 0=ship, 10=pedestrian, 20=UAV, 30=car, 40=bird, 99=unknown |
Noise Amplitude | 2 | ushort | 0.1 dB |
Reserved | 21 | byte | / |
Checksum | 1 | byte | Sum of segment data |
2.2.2 Heartbeat Packet
Format (16 bytes):
Byte Offset | Field | Length | Format | Description |
---|---|---|---|---|
0–3 | FrameHead | 4 | uint | 0xAA 0xAA 0xAA 0xAA |
4 | InfoType | 1 | byte | 0x04 |
5–6 | Reserved | 2 | byte | / |
7 | DeviceType | 1 | byte | 0x01 |
8–9 | Reserved | 2 | ushort | / |
10 | AzimuthCode | 1 | byte | 0–255 → 0–360° |
11–14 | Timestamp | 4 | uint | ms since day start |
2.2.3 Parameter Data
Returned when radar status is queried.
Format (32 bytes):
Byte Offset | Field | Length | Format | Description |
---|---|---|---|---|
0–3 | FrameHead | 4 | uint | 0xAA 0xAA 0xAA 0xAA |
4 | InfoType | 1 | byte | 0x03 |
5–7 | Reserved | 3 | byte | / |
8 | StatusType | 1 | byte | 1–255 |
9 | DeviceType | 1 | byte | 0x01 |
10 | FaceID | 1 | byte | 0x00 |
11 | Checksum | 1 | byte | Sum of bytes 9–24 |
12–15 | Reserved | 4 | byte | / |
16–19 | Status1 | 4 | varies | Depends on type |
20–23 | Status2 | 4 | varies | Depends on type |
24–27 | Status3 | 4 | varies | Depends on type |
28–31 | Status4 | 4 | varies | Depends on type |
Status Type Examples:
1
: BIT State (receiver/transmitter channel health bits)2
: GPS & Orientation (Lat, Lon, Alt, Azimuth)3
: Working Parameters (mode, frequency, face ID)11
: Thresholds (dB/m/s values)12
: Firmware IDs (Device ID, Version Numbers)21
: Sector Parameters (start/end angles)22
: Silence Zone Parameters (multi-zone definitions)
Notes
- Minimum interval between control commands: 100ms.
- Checksum: Calculated as byte sum of specific fields.
- Sector & Silence Zones: Only valid for mechanically scanning radars.
- Elevation/Height: Default to 0 if radar lacks height measurement.