Appearance
CAN/EnOcean gateways — Overview
A can-enocean is the small box that puts EnOcean radio switches on a MUXEN boat's bus.
An EnOcean switch is a wireless wall switch: nothing runs back to a panel, nothing goes through a bulkhead. The can-enocean listens for those switches on its radio and republishes each one on the MUXEN CAN bus as an ordinary MUXEN switch device. From the rest of the boat there is no radio at all — there are switch devices, addressed and read like any other, and the screens do not know where they came from.
It only listens. The box receives radio telegrams; it never transmits one. It cannot command a switch, wake one, or write anything into one. Everything an installer sets is set over the CAN bus.
One box, one job. There is a single can-enocean board — hardware ID 990010062 — and every can-enocean ships on it. There is no second generation and no variant: one box, one image series. What a box does is decided by the firmware loaded into it, and that firmware carries a product ID, the nine-digit number that names the finished product in the MUXEN catalogue. The boat's Brain uses it to know which firmware belongs in which box.
Unlike some other MUXEN gateways, a can-enocean is not a generic I/O device. It has no relay outputs, no dry-contact inputs and no analog inputs. The radio and the MUXEN bus are the whole of it.
The catalogue
| Product ID | Application | What it does |
|---|---|---|
| 010010033 | SFSP EnOcean | republishes up to 63 EnOcean radio switches on the MUXEN bus |
One product, one released firmware. If you are looking for a can-enocean that does something else, it does not exist yet, and asking for it is a question for MUXEN rather than a matter of loading a different file.
The application has its own manual — follow its name in the table above. Start there for the switches it supports, for pairing and for commissioning. What you are reading covers what is true of every can-enocean, whatever firmware it carries.
What is common to all of them
- The MUXEN side. One CAN connector, always 500 kbit/s, always the same addressing: a function (what kind of device this is) and an instance (which one of them). See Reference.
- The radio side. An EnOcean receiver module inside the box, on an internal serial link. Receive only. The box never configures it and never talks back to it.
- Configuration. No screen, no buttons, no web page. Every setting is read and written over the CAN bus from the Brain, with
muxen-uds. A factory-fresh box answers on the bus but publishes nothing until it has been given an instance number. - Firmware updates. Over the same bus, without opening the box — see Loading and updating a firmware. An update that fails part-way leaves the box running the firmware it already had.
- One LED. The single system LED is the whole local diagnostic, and it says only one thing: the program is running, or it is not. See Common mistakes.
Where to go next
| I want to… | Read |
|---|---|
| know what the box is and how to wire it | The hardware |
| load or update a firmware | Loading and updating a firmware |
| understand why it is not working | Common mistakes |
| look up an ID, a function code, a LED code, a timing | Reference |
| pair switches and commission a boat | its own manual — see the catalogue |
