Phaeton

Phaeton documentation

Requirements and Compatibility

What you need before you buy or install Phaeton: the Victron equipment, the Venus OS version, a supported charger and the network, and how Phaeton differs from a Victron EV Charging Station.

Victron System

  • A Victron GX device running Venus OS. Phaeton usually runs on the GX itself; it can also run on another always-on Linux computer on the same network as the GX, see Install on other Linux systems.
  • For the recommended USB installation: a GX with 32-bit Venus OS, such as the Cerbo GX, Cerbo-S GX, Ekrano GX, Venus GX, Octo GX, MultiPlus-II GX or EasySolar-II GX, or Venus OS on a Raspberry Pi 2, 3 or 4. You also need physical access to the GX, an empty FAT32 USB stick with at least 256 MB free, and a computer with internet to download the installer. The installer checks for 32-bit Venus OS and stops without changes on any other device.
  • The advanced SSH installation also supports 64-bit Venus OS, which newer Cerbo GX units and the Raspberry Pi 5 run. It needs SSH access to the GX and internet on the GX; see Advanced installation.
  • Keep Settings → General → Modification checks → Modifications enabled on, so Phaeton starts after the GX restarts.

Venus OS Versions

  • Use a current Venus OS release. Every Phaeton release is tested with full installations on Raspberry Pi 5 Venus OS images from 3.79 up to the current beta, and the first steps of its USB installer are tested on a Cerbo GX image of Venus OS 3.80.
  • From Venus OS 3.80 the GX can take over Auto charging with Opportunity Loads, and from Venus OS 3.90 with Dynamic ESS. Both need Phaeton connected to the GX over MQTT. Opportunity Loads needs a system that meets its conditions: a MultiPlus, Quattro or Multi RS, a battery monitor, all solar production measured, and Dynamic ESS off. Dynamic ESS needs EV charging control switched on in its VRM settings. Otherwise Phaeton runs the charging station's own Auto mode.
  • Phaeton on another computer pairs with the GX over MQTT from Venus OS 3.80. Without pairing, or on older versions, it connects over Modbus TCP, which needs the GX's Modbus TCP server switched on, and the GX cannot take over Auto charging.

Charger

  • A charger from the Supported chargers list, with its control interface enabled: Modbus TCP, local HTTP or the vendor's cloud.
  • Phase switching depends on the charger, and the Supported chargers list shows which chargers Phaeton can switch between one and three phases. RFID authorization and fault reporting also differ per charger.
  • Each charger needs its own Phaeton license, a one-time purchase with updates included. See Pricing.
  • Each charger on a GX gets its own Phaeton. The chargers share the available power only while the GX controls Auto; see Multiple chargers.
  • For charging on solar surplus, see what Auto mode needs in EV solar charging with Victron ESS.

Network and Internet

  • Keep the GX, a local charger and the computer you set up from on the same local network.
  • Keep that network trusted and do not expose Phaeton to the internet; use VRM Control Panel for remote access. See Security.
  • Phaeton needs to reach the charger, for Modbus TCP usually on port 502, and your browser needs to reach Phaeton's web port, 8088 by default. When Phaeton runs on another computer and connects over Modbus TCP, the GX also needs to reach Phaeton's EVCS Modbus port.
  • The computer that runs Phaeton, usually the GX, needs internet for a cloud charger integration, online activation, online updates and VRM electricity prices. VRM prices also need a VRM access token.
  • The USB installation needs no internet on the GX, and activation also works offline with a license file that you move with a computer. An online-activated Phaeton checks in with the license portal regularly; without internet it keeps charging but shows a license warning, so use offline activation for a GX that stays offline.
  • VRM Control Panel access needs Phaeton on the GX itself, the GX online and VRM set to Full; see Using VRM Control Panel.

Compared With a Victron EV Charging Station

  • The GX and VRM show your charger as a Victron EV Charging Station. Phaeton follows that charging station's firmware for Auto mode, phase switching and inverter protection.
  • Where Victron's manual describes the charging station differently, as for the solar surplus Auto needs to start, the overload reduction and the input current limit, Phaeton follows the firmware. Charging modes and Phases and inverter protection describe what Phaeton does.
  • Over MQTT, Phaeton reports errors and warnings to the GX with the charging station's codes; see Codes on the GX.
  • There is no IP address whitelist for Modbus TCP. Let only the GX reach Phaeton's Modbus port.
  • There is no input for a grid operator's switch (§14a EnWG in Germany), and Phaeton does not act on a controller that writes the charging station's external lock or current limit over Modbus. Use the charger's own grid operator control if it has one.
  • There is no setting that keeps a fully charged car powered; that is up to the charger.
  • A charging station refuses Auto while its GX communication is switched off, Scheduled mode without a schedule, and Start without a car or in Scheduled mode. Phaeton accepts these, and the Charging page shows why charging waits.
  • A charging station searches the network for its GX when the connection fails. Phaeton keeps the GX address you configured.
  • Update Phaeton from its own Updates page. VRM may offer a charging station firmware update for it, which Phaeton does not install: on the GX, Phaeton refuses the upload and VRM reports code 501; in other setups VRM may report another result.

Support for customers · Ask a question before you buy