Protocol selection
Compare CAN, Bluetooth, LoRa or MQTT against the required payload, update rate, topology, power budget and surrounding software. Select the link for the application rather than protocol novelty.
Expertise
Connected systems
Device communication from bus to browser.
Communication firmware and gateways that connect embedded devices to applications through defined messages and responses.
CAN, wireless and device-to-web communication
- Message definitions
- Gateway interfaces
- Connection recovery
Consistent data across the communication path
A browser command, radio packet and physical output have different timing constraints and failure modes. AUBRIX works across these interfaces to define what each component receives, how it responds and what happens when communication is interrupted.
Data and command definitions
Specify units, valid ranges, identifiers and command meaning. Represent release events, stale commands and unavailable positions explicitly, so placeholders cannot be mistaken for valid measurements.
Application responsibilities
Existing user or session services can remain in place while the device-control path changes. Assign responsibility for state and recovery to the relevant components.
Engineering process
Project
process.
- 01
Map the communication path
Identify devices, transports, gateways and applications. Record who produces each message and which component is authorised to act on it.
- 02
Specify the interface
Define messages, state transitions and compatibility requirements, including unavailable data and interrupted sessions.
- 03
Integrate in stages
Check individual interfaces before the complete interaction. Link test messages and observations to the implementation version.
- 04
Test connection recovery
Check disconnection, reconnection, duplicates and stale messages where relevant. Limit conclusions to the network conditions actually tested.
Depending on the agreed scope
Project
deliverables.
- An interface and message map
- Agreed device, gateway or application changes
- Integration checks for normal operation and relevant interruptions
- Configuration and handover notes without embedded credentials
Range, latency, uptime and security assurances require defined tests and evidence. Integration examples do not imply performance or certification guarantees.
Project experience
Related
projects.
Connected-device integration
Remote claw-machine control
MQTT carries browser-to-ESP32 control while Firebase retains the surrounding application services. Camera integration remains ongoing.
Project details
Embedded telemetry + browser interface
GNSS and LoRa race tracking
The race tracker covers GNSS data, LoRa packets, a gateway and browser mapping. The available evidence does not establish field range or positioning accuracy.
Project detailsTalk engineering
Which devices and applications need to exchange data?
Send a short, non-confidential summary of your requirements and current development stage.
Discuss your project with AUBRIX