Appearance
VE.Direct gateway (010010002) — Overview
This firmware brings Victron equipment that has a VE.Direct port onto the MUXEN boat: an MPPT solar charger, a battery monitor or shunt, a Phoenix inverter, a mains charger, a DC/DC converter.
The gateway has four VE.Direct ports. Each one is read independently, and each one carries exactly one Victron device. There is no daisy-chaining and no bus: VE.Direct is point to point, one cable per device, four devices per box.
It recognises the equipment, it is not told about it. Every Victron device with a VE.Direct port repeats a short text block a few times a second, and that block starts with a product identifier. The gateway reads that identifier and, when it matches one of the families it knows, creates the corresponding MUXEN device: an MPPT becomes a MUXEN solar charger, a battery monitor becomes a MUXEN battery, an inverter or a charger becomes a MUXEN converter. A device whose identifier it does not know is left alone — the port stays silent on the MUXEN side. See Reference — VE.Direct gateway for the exact list.
Nothing to declare. Plug the cables in, give the box its own instance number, and the four ports appear on the boat by themselves within a few seconds. Each device is numbered after the port it is plugged into, which you can change afterwards.
It commands, but only on and off. The gateway can switch a Victron device on or off over the same VE.Direct cable, and it does so on its own: each solar charger, charger and converter follows the charge request of the battery parc it belongs to. A MUXEN screen can override that and force a device on or off. That is the whole of the write side — there is nothing else it can set.
What it is not
- It is not a Victron configurator. Charge voltages, absorption times, current limits, load-output rules — all of that stays in the Victron device, set with the Victron tools. The gateway reads the device and switches it on or off; it changes no setting inside it.
- It is not a VE.Can or NMEA 2000 gateway. Victron equipment that talks on VE.Can rather than VE.Direct is not handled by this firmware.
- It is not Bluetooth. VE.Smart, instant readout, the Victron phone app — none of that is involved; the gateway reads the wired port.
- It is not a hub. Four ports, four devices, no more.
- It does not commission the Victron installation. Each device must already work on its own before it is of any use here.
Identity
| Serial gateway | Serial gateway v2 | |
|---|---|---|
| Product ID | 010010002 | 010010002 |
| Hardware | 990010053 | 990010063 |
| Software ID | 990050006 | 990050006 |
| Version | 5.19 | 6.2 |
| Image | 010010002-MODBUS-app_vedirect-firmware.srec | 010010002-SERIAL-V2-app_vedirect-firmware.srec |
Limits
| VE.Direct ports | 4 |
| Victron devices published | 4 — one per port |
| MUXEN instance numbers | 0 – 62 |
| Battery parcs followed at once | 4 |
Read next
- What you need — what to order and how to wire it
- Commissioning — commissioning
- Common mistakes — VE.Direct gateway — what usually goes wrong
- Reference — VE.Direct gateway — supported equipment, parameters, devices, timings
- CAN-SERIAL gateways — what is true of every serial gateway
