Appearance
The hardware
There is one can-enocean board and one only. Every box in the field is built on it, so there is no generation to check before ordering a spare and nothing about the wiring that depends on which unit you were sent.
| can-enocean | |
|---|---|
| Board name | muxen_can-enocean |
| Hardware ID | 990010062 |
| Microcontroller | STM32U575 @ 160 MHz |
| Program memory | 1 MB, split into a bootloader, two application slots and a settings area |
| CAN — MUXEN bus | 500 kbit/s, fixed |
| EnOcean radio | one receiver module, on an internal serial link |
| Relay outputs | none |
| Dry-contact inputs | none |
| Analog inputs | none |
| System LED | 1 |
The MUXEN bus
A can-enocean has one CAN connector, and it goes to the boat's MUXEN bus. There is no second bus and nothing to get the wrong way round.
| Speed | 500 kbit/s, fixed in the board itself — nothing configures it |
| Termination | the MUXEN bus is terminated at its two physical ends, not at the can-enocean unless the can-enocean is an end |
It is ordinary 120 Ω CAN: two wires plus a common ground, 120 Ω at each end of the segment and nowhere else. A bus with one termination too many or one too few may work on the bench with a short cable and fail on the boat; it is worth checking with an ohmmeter (60 Ω across a powered-down, correctly terminated bus).
The box keeps its CAN transceiver inhibited while it starts, and only releases it once the CAN controller itself has come up. A box that cannot start its controller therefore stays completely silent rather than disturbing the bus — which is why "nothing at all on the bus" and "a bus fault caused by this box" are not the same failure.
The EnOcean radio side
The radio module sits inside the box, on an internal serial link at 57600 baud. Nothing about it is wired or configured by the installer.
Two consequences worth knowing before you mount anything:
- The firmware only reads. It decodes the telegrams the module reports and does nothing else with it — it never sends the module a command and never transmits on the radio. Pairing a switch is therefore not a radio operation: it is a parameter written into the box over the CAN bus. The application's manual covers how.
- Placement is the whole of the radio installation. Range and reliability depend on where the box ends up relative to the switches and on what metal sits between them. The box reports a signal-strength figure for every paired switch on the bus, which is what you use to compare candidate positions — see the application's manual.
Which switch models are supported is an application question, not a hardware one.
Inputs and outputs
There are none. A can-enocean has no relays, no contact inputs, no analog inputs and no sensor supply, and it does not register a generic I/O device on the bus. If an installation needs local I/O next to an EnOcean receiver, that is a second box.
The system LED is the only local indicator, and Common mistakes explains what it can and cannot tell you.
Power and mounting
The box is powered from the boat's DC distribution. Follow the mechanical and electrical figures on the product data brief for the product ID you are installing — this manual describes behaviour, not ratings.
Firmware compatibility
A firmware image is built for one product ID on this one board, and the box checks the image's signature before it will start it. An image belonging to another MUXEN product line will not run here.
The current image series is 6.x. A box reporting a 5.x version predates the product and is not one to commission — report it rather than trying to update it. See Loading and updating a firmware.
