Installed devices stay offline
Field equipment relies on wired interfaces such as RS-485 and M-Bus. Replacing every meter or rebuilding communications is slow and expensive.
EdgeBus · Programmable field collection
Bring installed wired devices into IoT without replacing them
Run collection on low-power MCUs and DTUs, process multiple field queries into efficient LoRaWAN uplinks, and keep logic, parameters and business programs adaptable as site requirements change.
ADDR 01Water meterRS-485
ADDR 02Heat meterM-Bus
ADDR 03Industrial meterModbus
EDGE RUNTIMEEdgeBus
- Validate
- Transform
- Aggregate / COV
01 UPLINKLoRaWANOne useful payload
EB / 01
EdgeBus overview
Connecting installed devices takes more than moving a protocol onto wireless
POSITIONING STATEMENT
Buildings, campuses, utilities, energy sites and factories already contain large fleets of working wired devices. Scaling their connection means solving interfaces and protocols while controlling radio traffic, power and the delivery cost of continuous change.
Network capacity is finite
Forwarding every read directly creates many small messages. As device counts grow, they consume LoRaWAN airtime and system capacity.
Customer needs keep changing
Addresses, periods, thresholds and protocol logic continue changing after delivery, making repeated site visits impossible to scale.
From field device to application data
- 01
Installed wired devices
Water · power · heat · industrial meters
- 02
KC / DTU
RS-485 · M-Bus · sensor power
- 03
EdgeBus
Multi-query · aggregate · COV
- 04
LoRaWAN
Low-power · fewer messages · wide-area
- 05
ThinkLink
Sub-devices · models · RPC · applications
Technical scenarios
Four mechanisms turn field connectivity into a system that scales
EdgeBus combines protocol collection, on-device processing, dynamic configuration and collector hardware to address capacity, power, continuous change and installed-base conversion.
Collect many responses, send one uplink
Run multiple queries on the local field bus, then validate, parse, scale and combine their responses into one LoRaWAN uplink payload.
- Automatic Modbus RTU, DL/T 645-2007 and CJ/T 188 frames
- EBSDK-defined commands, responses and processing for private protocols
- One KC / DTU polls many devices while the cloud retains sub-device identity
Keep collection logic aligned with changing needs
When protocols, data layouts or site requirements change, use code, runtime parameters and remote updates at the right layer instead of turning every adjustment into a field reflash.
- TypeScript, EBSDK and EBHelper define collection behavior
- APP parameters and RPC change addresses, periods and thresholds
- Cloud-compile .obin packages and deliver them with LoRaWAN FUOTA
Sample frequently, uplink only on change
EdgeBus can read a field sensor frequently while COV compares the latest value with the previous uplink snapshot and transmits only after the configured threshold is crossed.
- Configure query cadence independently from uplink conditions
- setupCov stores and compares snapshots in SENSOR_DATA
- Adjust COV thresholds remotely through APP parameters
Power the sensor and convert installed assets to LoRaWAN
Collectors with external-device power can wake and supply a wired sensor during a read. KC21, for example, provides a 15V output for installed RS-485 sensors.
- Reuse working installed sensors
- Collect periodically without permanent site power
- Combine power, collection, processing and LoRaWAN in one endpoint
Software-defined collection
Turn field collection logic into remotely maintainable software
EdgeBus organizes queries, processing and uplinks as configurable events. Developers describe device protocols with TypeScript, EBSDK or EBHelper, then run the compiled business program directly on a low-power collector.
- Reuse the existing field bus instead of replacing every meter
- Decouple collection logic from hardware and evolve it by model and project
- Configure standard protocols quickly while retaining deep control for private devices
EdgeBus: low-power collection runtime
Focused on field protocols, lightweight processing and LoRaWAN uplinks without requiring Linux, containers or a full edge server.
TKE / TKG: local platform and edge services
Runs local databases, dashboards, BACnet, Modbus TCP Server and the complete ThinkLink platform capability set.
Built for installed-base modernization and repeatable delivery
DELIVERY LOOP
Define once, deliver continuously
- 01Write configuration
- 02Cloud compile
- 03Save package
- 04Create task
- 05LoRaWAN FUOTA
- 06Run new logic
EdgeBus devices
Choose a collector by field interface and power model
The KC family covers DIN-rail and IP65 installation, RS-485 and M-Bus interfaces, and runs the same continuously updateable EdgeBus collection logic.
DIN-rail RS-485 collector
Built for switch rooms, equipment rooms and control cabinets, connecting devices on an RS-485 bus to LoRaWAN.
- Industrial DIN-rail installation
- Designed for permanently powered sites
- Multi-slave polling with EdgeBus business programs
IP65 RS-485 collector
Built for pits, utility corridors and sites without mains power. It can supply 15V to an external sensor during collection and reuse installed RS-485 equipment.
- IP65 enclosure
- Wake and power the sensor for scheduled reads
- Convert installed sensors to LoRaWAN quickly
IP65 M-Bus collector
Provides a low-power LoRaWAN collection path for M-Bus heat and water meters in outdoor or unpowered locations.
- IP65 enclosure
- M-Bus meter hardware interface
- EdgeBus processing and remote updates
Ready to connect your installed field devices?
Start with one device protocol and build a collection path you can maintain over time.