ATL100

GPS Trackers

ATL100

Protocol

ATL100 Cold Chain Data Logger IoT Protocol

Revision 1.06 — Sep 21, 2025 — BLE scan settings (AT@BSS)

ATL100 Cold Chain Data Logger IoT Protocol R1.06 defines the data stream format, configuration commands, and message structures used between the ATL100 temperature data logger and backend server over CAT-M1 / NB-IoT / EGPRS. Use the sections below for a structured overview, or open the full PDF for complete command parameters and field definitions.

Revision history

RevisionDateDescription
1.002022-05-01Initial release
1.012023-03-21SACK Enable in AT@SIS; AT@ETS external temperature; temperature zone in +RPT and GCS Data Mask; RTO sub-commands 8/9; Sample RTC Time Mask in AT@CCS; PT100 and DS18B20 1-Wire in AT@ETS
1.022023-09-03Optimized AT command structure; GNSS enable logic for motion / stillness
1.032024-04-10eMTC and EGPRS network scan mode in AT@NIS; Sensor Data Number in +RPT
1.042025-03-16Search No Signal Cover in AT@NIS; Button Working Mode in AT@GCS; AT@DOG software watchdog
1.052025-06-24No Moving Send Interval in AT@RRS; regular report mode 2
1.062025-09-21Added AT@BSS BLE scan settings command

Data stream format

Communication includes upstream (device → server) and downstream (server → device) data streams over the cellular network. Upstream carries responses to downlink commands and unsolicited reports. Downstream carries configuration, query commands, and responses to uplink messages.

Frame types

DirectionEncodingFrameUsage
DownstreamPrintable ASCIIConfiguration CommandConfigure terminal parameters (AT@…=)
DownstreamPrintable ASCIIQuery CommandQuery current parameters (AT@…?)
DownstreamPrintable ASCII+SACKServer acknowledgement when the terminal sends a +RPT frame
UpstreamPrintable ASCII+QRYTerminal response to a query command
UpstreamPrintable ASCII+ACKConfirms a valid configuration command was received
UpstreamHexadecimal+RPT / -RPTReal-time and buffered report messages
All upstream and downstream frames end with the character "#" (0x23). In printable ASCII frames, "," separates adjacent parameters. Hexadecimal frames have no parameter separator.

Configuration commands

Configuration commands use the format AT@<KEY>=<password>,<parameters>,…,<serial># . Each command is protected by a password (default bcc100) and ends with a 4-digit hexadecimal serial number and "#".

Example — main server settings:

AT@SIS=bcc100,0,1,255.255.255.255,12345,,,0,0001#

Network commands

CodeCommandDescription
SISAT@SIS=Main server IP, port, report mode (0 Stop / 1 TCP / 2 UDP), buffer mode, SACK enable
NISAT@NIS=APN, credentials, network scan mode (0 auto, 1 EGPRS, 2 NB-IoT, 3 eMTC, 4 eMTC+NB2, 5 eMTC+EGPRS), Search No Signal Cover

General commands

CodeCommandDescription
GMTAT@GMT=Greenwich Mean Time / time zone setting
GCSAT@GCS=Global configuration: +RPT Data Mask, LED mode, GNSS mode, GNSS Info Mask, power saving, power-on mode, button working mode
RRSAT@RRS=Regular report: mode (0 off / 1 mode1 / 2 mode2), sensor sample interval, send interval, no-moving send interval

Cold chain commands

CodeCommandDescription
CCSAT@CCS=Cold chain settings: Cold Chain Info Mask, tilt, flight mode, motion/stillness, crash, light, built-in temperature/humidity alarms
ETSAT@ETS=External temperature sensors (PT100, DS18B20 1-Wire) alarm thresholds and duration

Operations, OTA, and BLE

CodeCommandDescription
RTOAT@RTO=Real-time operation (reboot, power off, quick server debug, delete buffer messages, and more)
DOGAT@DOG=Software watchdog: mode and interval
UPFAT@UPF=Firmware upgrade over the air
BMSAT@BMS=Device management system: BMS server, report interval, +BMR Data Mask
BSSAT@BSS=BLE scan settings (added in v1.06)
Report mode (SIS/BMS): 0 = Stop, 1 = TCP, 2 = UDP. Buffer mode: 0 = disabled, 1 = low priority, 2 = high priority. When buffer is enabled and the device loses coverage or does not receive +SACK, reports are stored locally and sent when connectivity returns.

Query commands

Query commands retrieve the current working parameters of the terminal. They use printable ASCII with comma-separated fields:

AT@<KEY>?<password>,,<serial>#

  • AT@SIS?bcc100,,# — query main server settings
  • AT@NIS?bcc100,,# — query network (APN) settings
  • AT@GMT?bcc100,,# — query time settings
  • AT@GCS?bcc100,,# — query global configuration
  • AT@RRS?bcc100,,# — query regular report settings
  • AT@CCS?bcc100,,# — query cold chain settings
When sent by the backend server, parameters are returned to the server. When sent by SMS, parameters are returned via SMS.

Message format

Report messages share a common frame structure with header, data, and tail zones:

ZoneFieldsEncoding
HeaderHead (5 B) + Length (2 B) + IMEI (8 B) + Device ID (1 B)ASCII / HEX / HEX / HEX
DataVariable payload + G-time (7 B)HEX or ASCII
TailSerial number (2 B) + Tail "#" (1 B)HEX / ASCII
  • +RPT / -RPT and +BMR / -BMR — data zone encoded in hexadecimal (big-endian for multi-byte values)
  • +SACK — fully ASCII encoded
  • +ACK, +QRY, +ALL, +QNI, +VER — data zone in ASCII with comma separators

Report messages (+RPT / -RPT)

+RPT frames are real-time reports generated and sent within 3 minutes. -RPT frames are historical reports stored in the device buffer and sent when connectivity is restored.

All event-driven and regular reports share the same +RPT/-RPT hex-encoded format. The Data Mask in AT@GCS controls which information zones are included in each report.

Key +RPT Data Mask bits (AT@GCS)

BitFieldContent
0Multi-packetFrame count and frame ID
1Network typeCellular network type
2BatteryVoltage (mV) and level (%)
3GNSS informationFix type, HDOP, speed, azimuth, altitude, lat/lon, UTC time
4Cell informationMCC, MNC, LAC, Cell ID, CSQ
5Neighboring cellAdjacent cell information
6Cold chain informationTemperature, humidity, light, motion, 1-Wire sensors
7Upgrade informationFirmware upgrade status
19BLE informationBLE scan results

Event types

TypeEvent
0Terminal power
1Regular report
2Moving
3Battery alarm
4Free fall alarm
5Tilt alarm
6Flight mode
7Crash alarm
8Light alarm
9Built-in temperature alarm
10Humidity alarm
11Upgrade firmware
12External temperature alarm
30BLE common info
The full PDF lists every event state, Cold Chain Info Mask bit, sensor data field, and byte length with value ranges.

Buffer messages (+BMR / -BMR)

+BMR frames are real-time BMS reports generated and sent within 3 minutes. -BMR frames are buffered BMS reports sent when connectivity is restored. Configure BMS reporting via AT@BMS.

ParameterDescription
Report Mode0 = Stop, 1 = TCP
Buffer Mode0 = disabled, 1 = enabled
BMS Server IP / PortDevice management server address
Connection Life0 or 5–300 seconds
Report Interval1–2880 minutes
BMR Data MaskComponent mask for +BMR/-BMR message content (set via AT@BMS)
+BMR/-BMR use the same header/tail frame structure as +RPT/-RPT with a hexadecimal data zone.

Acknowledgement

FrameDirectionDescription
+ACKDevice → serverConfirms a valid configuration command was received
+SACKServer → deviceServer acknowledgement when SACK Enable is set in AT@SIS

Command query responses

FrameDescription
+QRYResponse to a single query command
+ALLBulk response with all configured parameters
+QNINetwork information query response (APN, IMSI, ICCID, CSQ, cell ID)
+VERFirmware and hardware version information

Terms and abbreviations

TermMeaning
ACKAcknowledgement
APNAccess Point Name
BLEBluetooth Low Energy
CCSCold Chain Setting
EGPRSEnhanced General Packet Radio Service
G-TimeGenerated Time
GNSSGlobal Navigation Satellite System
IMEIInternational Mobile Equipment Identity
IoTInternet of Things
NB-IoTNarrowband IoT
RPTReport message
SACKServer acknowledgement
TCP / UDPTransmission Control / User Datagram Protocol
UTCCoordinated Universal Time
In this document, "terminal", "device", and "equipment" refer to the ATL100 cold chain data logger unless otherwise specified.

ATL100 — Protocol

v1.06 · 2025-09-21 · Release

ATL100 — Protocol — Page 1 of 43

Page 1 of 43

If the preview does not load, use Download or Open in new tab.