The problem
Off-the-shelf stacks cover the common cases — but your product is rarely the common case. A proprietary link between two of your own boards, a non-standard device profile, a gateway that has to bridge two networks that were never meant to talk, or a certified variant of an open protocol: when the catalogue stops, projects are pushed into a corner. Either you compromise the design to fit what exists, or you bolt on a black-box component you cannot inspect, maintain or put in front of an assessor. Both choices come back to bite at integration or certification time.
What we deliver
Custom protocol engineering from specification to production. That includes fully proprietary protocols, extensions and device profiles on top of CANopen, EtherCAT or J1939, protocol gateways, and safety variants of communication protocols. Everything is delivered as complete, documented software with a clean portability layer so it runs on any MCU, any RTOS or bare metal, together with a test harness and the architecture and integration documentation your own team needs. The result is a protocol you own and can maintain and certify — not a dependency you have to work around.
Standards we work to
Where safety applies, our coding and process align with the software requirements of IEC 61508 and ISO 26262, with MISRA C and documented verification and validation. Protocol conformance follows the relevant bodies: CiA for CANopen, the EtherCAT Technology Group for EtherCAT, SAE J1939, and IEC 61784-3 for safety communication. Requirements, tests and design decisions are traceable from day one.
Proof
More than 30 years of embedded protocol development, with stacks running in the field across industrial automation, medical devices and mobile machinery. Our safety communication stacks are independently assessed to SIL3/PLe, and everything we build is delivered with full documentation and clear ownership — so the software strengthens your roadmap instead of locking you into ours.
