Developer
Ask a QuestionBlecon WebsiteBlecon Console
  • Learn Blecon
    • Introduction
    • Blecon Modems
      • Device Identity and Network Security
      • Modem Firmware vs Modem Library
      • Using the Modem
      • Communicating with the cloud
      • Sending data from the cloud to a device
    • Blecon Hotspots
    • Blecon Networks
      • Blecon Accounts
      • Registering devices
        • The Blecon Scanner
        • Blecon Scanner Developer Guide
      • Blecon Events
      • Cloud Integrations
  • Cloud Integrations
    • Webhook
    • AWS S3
    • AWS SQS
    • AWS EventBridge
    • Memfault
  • Getting Started Guides
    • Getting started index
    • Install the Blecon Modem Firmware
    • Set up a Blecon Hotspot
    • Use Blecon from your computer with the Blecon CLI
    • Create a Network and register a device
    • Send device requests and events to your web service
    • Use Blecon from a Development Board
    • Use the Blecon Modem from an MCU
  • Device Guides
    • KKM S5-BCN
  • Development Board Guides
    • Supported Development Boards
    • Ezurio DVK-BL54L15
    • Fanstel EV-BM15C
    • InsightSiP ISP2454-LX-EB
    • Nordic nRF52840DK
    • Nordic nRF54L15DK
    • Minew ME54BE01
    • Panasonic PAN-B511 EVB
    • Raytac AN54L15Q-DB
    • u-Blox EVK-NORA-B20
  • Modem Reference
    • Modem Firmware Releases
      • nRF54L15 DK
      • nRF52840 Dongle
      • nRF52840 DK
    • CLI Releases
    • SDK Releases
    • Modem API Reference
    • Modem Protocol Reference
      • Request Frames
      • Command Protocol
      • UART Transport
    • Guides and best practices
      • Retrieve a device's identity
  • Cloud Reference
    • Configuration API
    • Advanced event routing
  • Hotspot Reference
    • Blecon Hub
Powered by GitBook

Get Support

  • Ask a question
On this page
  • Request frame
  • Response frame
  • Event frame
  1. Modem Reference
  2. Modem Protocol Reference

UART Transport

Connecting to the Blecon Modem over UART

The Blecon modem supports UART as a transport protocol. The UART must be used with a 115200bps baudrate, no parity and one stop bit, and hardware flow control (RTS/CTS) for physical UARTs.

Modems with a USB interface also expose the UART transport as a virtual serial port on a device with Vendor ID 0x36ca and Product ID 0x0001.

All data sent on the UART link is hex-encoded, as little endian. All frames are separated by a carriage return (CR) and line feed (LF) control character. The CR character is optional when sending frames to the modem.

A transaction is made of a request frame (on the modem's RX line) and response frame (TX line). The modem only supports one request to be pending at a given time.

When the modem needs to signal an event to the host MCU, it sends an event frame on the modem's TX line. Please note the event frame can be received at any time.

Request frame

The structure of a request frame is:

2 characters
4 characters
n*2 characters
2 characters

RX

01

Request size

(hex-encoded, LE)

Request

(hex-encoded)

<CR><LF>

Response frame

The structure of a response frame is:

2 characters
4 characters
n*2 characters
2 characters

TX

01

Response size

(hex-encoded, LE)

Response

(hex-encoded)

<CR><LF>

Event frame

The structure of an event frame is:

2 characters
2 characters

TX

02

<CR><LF>

PreviousCommand ProtocolNextGuides and best practices

Last updated 11 months ago