Skip to main content
Korlinx

Get Started with AS-614

This tutorial connects AS-614 to a host through TTL UART, checks the firmware, selects wall position mode, and verifies the first position packet. It starts with Mode 1 because option Modes 10-13 require separate licensing and application-specific validation.

Before you begin​

You need:

  • One AS-614 module with its ordered connector option
  • A regulated 3.3-7.0 VDC supply with adequate margin above the documented 700 mW maximum
  • A 3.3 V TTL UART adapter
  • A serial-terminal application that supports 230400 bps
  • An open indoor test area with a clear line of sight
  • The unit's firmware and license information, if available
caution

Use the documented electrical interface AS-614 uses 3.3-7.0 VDC for module power and the protocol section specifies 3.3 V UART. Do not treat the supply voltage as the UART logic voltage.

Step 1: Identify the connector and Pin 1​

Use the manual signal table and confirm Pin 1 on the actual board before wiring. P1 is the eight-pin 2.54 mm header; P2 is the six-pin connector. The required signals are VCC, GND, UART TX, and UART RX. Keep NRST open or high for normal operation.

caution

Pin 1 orientation requires confirmation Manual v5.00 page 2 places P1 Pin 1 at the bottom of the header, near the square pad. The supplied Pin List artwork numbers it from the top. Confirm the production revision before applying power; do not combine the two orientations. The signal table follows the manual.

Step 2: Wire power and UART​

AS-614 signalHost connection
VCCRegulated 3.3-7.0 VDC supply
GNDSupply ground and UART-adapter ground
UART TXHost/adapter RX
UART RXHost/adapter TX
NRSTLeave open or high for normal operation

Do not connect TTL UART directly to an RS-232 port.

Use one power input at a time. The manual defines power and UART on P1/P2; it does not provide a P3 pinout for host wiring.

Step 3: Open the serial terminal​

Use the protocol settings defined by the AS-614 manual:

Baud rate: 230400 bps
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Encoding: ASCII
Command case: lowercase
Command terminator: LF or CR

The manual does not document a baud command or alternative baud rates for AS-614.

Step 4: Power the module and identify the firmware​

After readable UART communication is established, stop continuous output and query the firmware:

stop
ver

Wait more than 500 ms between commands. The manual gives this example response:

L25Aug16102.0!

Treat it as an example only. Record the actual response, hardware revision, supply voltage, and licensed modes.

Step 5: Select Mode 1 and inspect settings​

Send commands individually and leave more than 500 ms between them:

mode 1
reset
info

The manual recommends resetting after changing modes or settings because retained values can affect detection. reset restarts the module while keeping settings. freset restores all factory settings and should be reserved for a controlled validation workflow.

warning

Persistent configuration Changed settings are retained after power cycling. Record the original configuration before using freset or changing production units.

Step 6: Start wall-position output​

Start output:

start

A normal Mode 1 target packet has this structure:

#ABBBBCCCDDD!

Where:

  • A: target index
  • BBBB: signed X coordinate in centimeters
  • CCC: positive Z coordinate in centimeters
  • DDD: reflected-power value, capped at 999

When no target is detected, the documented vacancy packet is:

#0!

The first frames after a mode change or start may reflect buffered state. Do not use them as acceptance data.

Pass criteria​

  • The board powers without supply collapse, abnormal heating, or unexpected current.
  • UART is readable at 230400 bps, 8-N-1, with no flow control.
  • ver returns a firmware identity.
  • mode 1, reset, and info produce readable command responses.
  • start produces valid #...! target packets or #0! vacancy packets.
  • Coordinates respond consistently when one person moves in the test area.
  • The detection LED turns on when an object is detected, as described by the manual.

Troubleshooting​

SymptomCheck
No UART dataSupply range, current capacity, common ground, TX/RX crossing, NRST, connector orientation, and 230400 bps
Garbled dataConfirm 230400 bps, 8-N-1, no flow control, ASCII, and 3.3 V TTL logic
Command ignoredUse lowercase, terminate with LF or CR, and wait more than 500 ms between commands
First packets look wrongDiscard the initial buffered frames after mode changes or restarting output
Unexpected settingsQuery info; settings persist across power cycles, and changing mode resets coordinate limits to that mode's defaults
False targetsMove to an open area, narrow the ROI, identify fans/curtains/metal, then tune pthold
Stationary target disappearsPosition mode needs micro-motion unless limited static-object detection is enabled

What's Next?​