Skip to main content

Supported Devices & Protocols

This page describes what the Device Configurator supports today and how clients can verify support directly from APIs.

Source of Truth​

Use these endpoints as the live support catalog:

  • GET /api/devices/types/list
  • GET /api/channels/protocols
  • GET /api/channels/status (tenant runtime status)

Protocol Families​

Vehk Axle supports ingestion through tcp, mqtt, http, and udp channels across multiple protocol families.

Common protocol keys currently present in the registry:

  • mqtt
  • http
  • tcp_itriangle
  • tcp_teltonika
  • tcp_queclink
  • tcp_calamp
  • tcp_wialon
  • tcp_wialon_ips
  • tcp_meitrack
  • tcp_coban
  • tcp_concox
  • tcp_ruptela
  • tcp_suntech
  • tcp_topflytech
  • tcp_huabao
  • tcp_digital_matter
  • tcp_xirgo
  • tcp_galileosky
  • tcp_bce
  • tcp_sinotrack
  • tcp_skypatrol
  • tcp_gosafe
  • tcp_navtelecom
  • tcp_cellocator
  • tcp_atrack
  • udp

Representative Supported Device Brands​

The registry includes multiple models for each brand. Examples:

BrandExample models in registryTypical protocol
TeltonikaFMB920, FMC130, FMB640, FMM130tcp_teltonika
QueclinkGL300, GL320MG, GV300, GV55tcp_queclink
CalAmpLMU-3030, LMU-4230, TTU-X70tcp_calamp
MeitrackT366, T399tcp_meitrack
Concox / CobanGT06N, GT06F, GT360, TK103tcp_concox / tcp_coban
iTriangleTS101, TS102, VS101tcp_itriangle
Wialon-compatibleMultiple IPS-compatible devicestcp_wialon / tcp_wialon_ips
OthersRuptela, Suntech, Topflytech, Huabao, Digital Matter, Xirgo, Galileosky, BCE, Sinotrack, SkyPatrol, GoSafe, NavTelecom, Cellocator, ATrackBrand-specific TCP protocols

OBD/CAN and Telemetry Coverage​

Supported telemetry depends on device capabilities. Common fields/features in the registry:

  • GPS location, speed, heading
  • GSM signal and network state
  • Ignition and movement
  • Battery voltage
  • CAN/OBD parameters (for supported devices), such as speed and RPM
  • Diagnostic and gateway-related metadata

How Clients Should Verify Compatibility​

1) Check device type in catalog​

curl -H "Authorization: Bearer <TOKEN>" \
  "https://<api-host>/api/devices/types/list?manufacturer=Teltonika"

2) Check protocol listener summary​

curl "https://<api-host>/api/channels/protocols"

3) Check tenant runtime channel/device status​

curl -H "Authorization: Bearer <TOKEN>" \
  "https://<api-host>/api/channels/status"

4) Check connection target details​

curl -H "Authorization: Bearer <TOKEN>" \
  "https://<api-host>/api/devices/connection-info"

This endpoint tells clients whether to use HTTP ingest, MQTT, or protocol-specific TCP ports.

If a Device Is Not Listed​

  1. Use Custom / Unlisted Device in Device Configurator.
  2. Set connection_method (tcp, mqtt, or http) and validate data in Diagnostics.
  3. Raise a support request for native model mapping if needed.

Next Steps​