SR226 Communication Protocol V3.26

API User Manual
Wuhan Lakeda Science And Technology Co., Ltd.


Table of Contents

  1. Overview
  2. Communication Protocol

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:


2. Communication Protocol

Two message types:


2.1 Control Commands (PC → Radar)

Link Command Format (10 bytes):

Byte OffsetFieldLengthFormatDescription
0–9FrameHead10charFixed: 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 OffsetFieldLengthFormatDescription
0–3FrameHead4uintFixed 0xAA 0xAA 0xAA 0xAA
4InfoType1byteFixed 0x0B
5–7Reserved3byteDefault 0x00
8ParameterType1byte1–255 (see list below)
9DeviceType1byteFixed 0x01
10FaceID1byteFixed 0x00
11Checksum1byteSum of bytes 9–24
12–15Reserved4byteDefault 0x00
16–19Parameter14variesDepends on type
20–23Parameter24variesDepends on type
24–27Parameter34variesDepends on type
28–31Parameter44variesDepends on type

Parameter Type List:


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 OffsetFieldLengthFormatDescription
0–3FrameHead4uintFixed 0xAA 0xAA 0xAA 0xAA
4InfoType1byte0x01
5–6Reserved2byte/
7DeviceType1byteFixed 0x01
8–9TrackCount2ushortNumber of tracks (0–999)
10–11Reserved2byte/

Then, per target (79 bytes each):

FieldLengthFormatDescription
Batch ID4uintTrack batch number
Azimuth4float0–360°, °
Range4floatmeters
Latitude4float-90° to +90°
Longitude4float-180° to +180°
Radial Velocity4floatm/s
Exist Flag2byte0 = disappeared, 1 = exist
Elevation4float°
Heading4float°
Speed4floatm/s
Altitude4floatm (relative)
Timestamp4uintms since day start
Amplitude2ushort0.1 dB
Category1byte0=ship, 10=pedestrian, 20=UAV, 30=car, 40=bird, 99=unknown
Noise Amplitude2ushort0.1 dB
Reserved21byte/
Checksum1byteSum of segment data

2.2.2 Heartbeat Packet

Format (16 bytes):

Byte OffsetFieldLengthFormatDescription
0–3FrameHead4uint0xAA 0xAA 0xAA 0xAA
4InfoType1byte0x04
5–6Reserved2byte/
7DeviceType1byte0x01
8–9Reserved2ushort/
10AzimuthCode1byte0–255 → 0–360°
11–14Timestamp4uintms since day start

2.2.3 Parameter Data

Returned when radar status is queried.

Format (32 bytes):

Byte OffsetFieldLengthFormatDescription
0–3FrameHead4uint0xAA 0xAA 0xAA 0xAA
4InfoType1byte0x03
5–7Reserved3byte/
8StatusType1byte1–255
9DeviceType1byte0x01
10FaceID1byte0x00
11Checksum1byteSum of bytes 9–24
12–15Reserved4byte/
16–19Status14variesDepends on type
20–23Status24variesDepends on type
24–27Status34variesDepends on type
28–31Status44variesDepends on type

Status Type Examples:


Notes