Your browser doesn't support the features required by impress.js, so you are presented with a simplified version of this presentation.

For the best experience please use the latest Chrome, Safari or Firefox browser.

Introducing CaNX: new open protocol
for building control, m2m, IoT and other
remote control and measurement applications
No installer will use wireless
when high reliability is required

It's a fact!
KNX was made 25 years ago

The only new specifications that are appearing now are wireless-based

There are interesting approaches, but still a lot of unsolved issues when used in large projects
Why have we decided to make a new protocol specification based on wired media?

When newest specification was made 25 years ago, such things as data encryption and security, usability was not important

Nobody thought about ecosystem concept: not only protocol specification, but also a universal way of commissioning
We decided to build upon existing wired home and building automation standards (KNX, ModBus, BacNet)

We chose KNX for several reasons, including centralized software for programming and commissioning
But KNX has plenty of disadvantages!
  • Low speed: 9.6 kbit (way too low for today's projects)

  • Security (cannot be made without full redefinition of standard)

  • Not fully open standard (meaning you can participate if
you are part of the alliance and pay your fees)

  • Commissioning and operation with KNX is centralized
through ETS which is a property of KNX Association.
Only those companies who are members of KNX Association
have possibility to manufacture devices for KNX

  • KNX only targets home and building automation. It is
missing concepts for modern IoT approach (universal bus for
any automation systems)

  • KNX is also missing some modern features like semantics

We've improved upon drawbacks of KNX while leaving the same user-experience and compatibility

We've chosen to build something new
but based on time-proven technologies

In aviation industry absolutely new plane
is the one that has maximum 25% of changes, because you must use only proven solutions.

We are maximizing the use of positive/negative experiences of other protocols

Without any compromise in quality/functionality we have
created our specification based on K.I.S.S. approach
(Keep it simple stupid)

  • It should be possible discover, identify and configure installed devices in a uniform way

  • Autonomous/distributed device operation

  • Uniform way of device firmware upgrade
We have chosen CAN FT as base media

Fault-Tolerant (FT) CAN physical layer maintains functionality in the case of a broken or shorted bus wire. This is of great importance in areas where such failures can occur. If a fault condition occurs, bus node simply switches to single-wire operation. Automatic detection of bus system recovery automatically returns the transceiver to differential mode when the failure has been cleared.

CAN FT is the latest version of international standard ISO 11898-3:2006
Main features

1:1 mapping to KNX: you don't need to change group addresses and adjust data-types, it's fully plug&play

Bus speed is improved >10 times compared to KNX, 100 kbit instead of 9.6 kbit (using same max cable length)

Two types of communication are possible: either direct or group-based
System can work as a plug&play solution. Just plug the device and push the programming button. It will send its hardware and software version to the master controller. The master will know the exact info about this device and will provide an individual address for it. Extra device configuration is done via a programming tool
CAN is time and harsh environment proven technology. It is a popular fieldbus system in space, automotive, aerospace and railway industries

Devices do not require an additional termination resistor, Any topology (except loop) can be used: Line, Star, Tree
Besides fault-tolerant version, CAN FD can be used - providing speeds up to 10 Mbit/s and up to 6km of distance (even more with repeaters)
The only drawback is that additional 2 wires must be used for powering

  • It is not possible to combine both powering and high transfer speed with the same wiring. Additional 2 wires of standard KNX cable can be used for device powering

  • Many KNX devices still require an additional power supply because the capacity of bus-provided power is very limited

  • External power supply helps making fully galvanically isolated CAN devices much easier
More about media

  • Any IP network can be used as a transport: Ethernet, WiFi, Optics, 3G/4G etc

  • CaNX can operate over BLE version 4.0 or 5.0

  • Any implementation of 802.15.4 protocol (6LoWPAN, ZigBee) can be used as well
User experience

  • Same WAGO connectors are used as in KNX which are easy to plug and easy to maintain

  • Additional features like an ability to blink device's LED to find it, locate devices in programming mode

  • Each device has a communication status LED which blinks during message reception
Line repeater handles automatic individual and group address assignment: simple devices like push button inputs and relay actuators can be linked together without any additional configuration

Security and maintenance

  • Direct telegrams can be disabled, so parameters and addressing cannot be changed. This way only group communication works

  • Device status can be checked via ping telegram, it replies with a number of errors (how many telegrams were not sent/received well)

  • Object status (input/output) can be checked via ping telegram, device replies with error code - broken wire, short-circuit etc

  • Telegrams can be filtered to isolate devices/telegrams from passing to unwanted segments
Commissioning tool

  • Common for all CAN devices, works either as a web-application (part of LogicMachine) or stand-alone application for MAC, Windows and Linux (coming later)

  • Each device has a unique hardware and software ID. Configuration profile is downloaded by the commissioning tool automatically

  • ETS project files can be imported and enriched with semantics

  • CaNX is an open standard protocol for m2m, IoT and other remote control and measurement applications

  • It enables simple, low-cost devices to be networked together with high-end computers and/or to work as an autonomous system, whatever the communication media is

  • Free and Open. No usage, patent or other costs for its implementation and use

  • CAN is very reliable and widely-supported, it allows to manufacture low cost nodes that can work reliably, efficiently and can be trusted in their day-to-day operation.

  • CaNX can be used equally well in other environments other than CAN: IP networks, wireless etc
47 Katolu street, Riga, LV 1003, LATVIA
Phone: +371 67648888


Use a spacebar or arrow keys to navigate