Skip to main content

AS-611Bn Command and Data Reference

This page condenses the command and frame information in the supplied manual. All commands are lowercase ASCII.

note

Firmware-specific reference This page follows the supplied manual marked Ver.4.0 Jun.2026. Confirm command support for the installed function and firmware. Commands are shown without a terminator because the manual does not specify one. Examples are documented syntax, not captured transactions.

Common commands​

CommandExampleDocumented default/rangeFunction
modemode 1Default 1; 1 or 21: distance, 2: vital sign
startstart—Start data output
stopstop—Stop data output
baudbaud 460800Default 460800; 115200, 230400, 460800, 921600Save baud rate and reboot
resetreset—Software reset and reinitialize current mode
fresetfreset—Hardware/cold reset; factory-default restoration is not specified
testtest 0Default 0; 0 or 1Normal or test/debug wave output

Documented mode responses:

=DISTANCE!
=VITAL!

Distance-mode commands​

CommandExampleDefaultRangeFunction
zminzmin 2525 cm10 to zmax - 25 cmMinimum range
zmaxzmax 300300 cm50–2000 cmMaximum range
pmodepmode 000, 1, 2Balanced, fast, accurate
senasena 5050%0–100%CFAR sensitivity
sortsort 000, 1Distance-first or strength-first
outtimeouttime 110, 10: documented 15 Hz; 1: once per second

Vital-mode commands​

CommandExampleDefaultRangeFunction
zminzmin 2525 cm15 to zmax - 25 cmMinimum vital-sign range
zmaxzmax 150150 cm40–250 cmMaximum vital-sign range
wavewave 100, 10: simple, 1: waveform
extenexten 100, 10: no HRV extension, 1: add RMSSD and SDNN

Distance frame​

#ABBBBCCC!
SegmentWidthMeaning
#1Start
A1Object index
BBBB4Distance, cm
CCC3Reflected strength
!1End

Example: #10250045! = object 1, 250 cm, strength 45.

No target: #0! every 15 seconds.

Vital state​

ValueMeaning
0No target
1Target moving
2Target calculating
3Vital-sign result

Simple vital frame​

%ABBBCCDDD!
SegmentWidthMeaning
%1Start
A1State
BBB3Heart rate per minute
CC2Breathing rate per minute
DDD3Distance, cm
!1End

Rate: once per second.

Extended simple frame:

%ABBBCCDDEEFFF!

DD: RMSSD ms; EE: SDNN ms; FFF: distance cm.

Waveform vital frame​

@ABBBCCDEEEFFF!
SegmentWidthMeaning
@1Start
A1State
BBB3Heart rate per minute
CC2Breathing rate per minute
D1Heart-beat pulse: 1 at each beat, otherwise 0
EEE3Respiration waveform, 0–999
FFF3Distance, cm
!1End

Rate: 10 frames per second.

Extended waveform frame:

@ABBBCCDDEEFGGGHHH!

DD: RMSSD ms; EE: SDNN ms; F: heart pulse; GGG: respiration waveform; HHH: distance cm.

No target: %0! or @0! every 15 seconds.

Frame lengths and unresolved encoding​

The lengths below are calculated from the literal ASCII layouts, including start and end markers and excluding any additional transport terminator.

FormatLayout-derived lengthManual's length label
Distance10 bytes10 bytes
Simple vital11 bytes10 bytes — inconsistent
Extended simple vital15 bytesNot stated
Waveform vital15 bytes14 bytes — inconsistent
Extended waveform vital19 bytesNot stated

Use these as candidate layouts, not firmware-verified packet lengths. Capture actual output for every wave/exten combination before enforcing a strict parser. The manual also leaves these details undefined:

  • Encoding of object 10 in the one-character object-index field, grouping of multiple target frames, and the meaning of a complete 15 Hz cycle.
  • Numeric padding, overflow, signedness, rounding, and invalid/unavailable sentinels.
  • RMSSD/SDNN values above 99 ms and the time window used to calculate HRV.
  • Command echoes, most acknowledgements/errors, response timeouts, and status/diagnostic frames.

Output cadence does not establish how frequently each physiological value is independently recalculated. Moving/calculating states must not be treated as confirmed vital-sign measurements.

Illustration of ASCII frame fields for distance and vital-sign output
Artwork corrections: HR uses three characters (BBB), not BBBB; extended-simple SDNN uses two (EE), not EEE. The extended waveform is not shown. Use the tables and frame-length notes above as the reference; this diagram is not an exact parser specification. View full-size image.

Parser requirements​

The following are host-integration recommendations, not extra device commands:

  1. Separate measurement markers (#, %, @) from documented mode replies (=DISTANCE!, =VITAL!) and boot/status messages. Preserve unknown echoes or errors for inspection.
  2. Buffer partial messages through !, while enforcing a host buffer limit and a timeout chosen for the tested connection. Recover from an incomplete or malformed message at a recognized boundary; never wait indefinitely.
  3. Handle #0!, %0!, and @0! before fixed-width measurement parsing. Recognize the boot banner separately.
  4. Validate lengths and field encodings against raw captures for the active mode, wave, and exten settings. Do not silently truncate a value or invent an object-10 encoding.
  5. Treat only state 3 as an available vital-sign result. Keep moving/calculating and unavailable fields distinct from measured zero values.
  6. Allow multiple frames in one UART read or BLE notification and one frame across multiple reads/notifications.
  7. After a mode change or reboot, discard incomplete old measurement frames and establish the current configuration before decoding new data.
  8. Timestamp and retain raw frames, configuration, and firmware version during validation.

Boot frame​

The manual documents:

#AS_611B_4.0!

Do not parse this as distance data. Detect the prefix or validate the distance-frame length before numeric conversion.