Understanding Victron VE.CAN PGN Details

Key Takeaways

• Victron devices use both standard NMEA 2000 PGNs and proprietary VREG messages for communication.
• PGN 127502 (Switch Bank Control) is deprecated and replaced by PGN 127501.
• PGN 127501 (Binary Status Report) details vary significantly between different Victron products.

What are Victron VE.Can PGNs?

Victron VE.Can communication relies on NMEA 2000 Protocol Data Units (PGNs) to exchange information between devices. These PGNs are standardized messages, but Victron also uses proprietary messages called VREGs for specific parameters not covered by the NMEA 2000 standard. Understanding these PGNs is crucial for integrating Victron equipment into a broader NMEA 2000 network or for advanced system monitoring.

Understanding Victron Proprietary VREG Messages

Victron devices transmit proprietary messages known as VREGs to communicate parameters unique to their systems. These messages are essential for comprehensive monitoring and control within a Victron ecosystem, especially when standard NMEA 2000 PGNs do not cover certain data points.

NMEA 2000 PGN 127502: Switch Bank Control (Deprecated)

The NMEA 2000 PGN 127502, identified as 0x1F20E, was previously used for Switch Bank Control. However, this message is no longer transmitted by current Victron products. It has been replaced by PGN 127501 for reporting similar status information.

While deprecated, older firmware versions of some Victron products might still have transmitted this PGN. Products that historically used PGN 127502 include:

• BlueSolar MPPT 150/70 & 150/85 (up to v2.00)
• Lynx Shunt VE.Can (up to v1.00)
• Skylla-i (all models, up to v1.08)
• VE.Direct to VE.Can\NMEA 2000 interface (up to v1.06)
• VE.Bus to VE.Can\NMEA 2000 interface (up to v0.12)

If you are working with these specific product versions, be aware that this PGN might be present, but for newer installations, focus on PGN 127501.

NMEA 2000 PGN 127501: Binary Status Report

PGN 127501 (0x1F20D) is a widely used NMEA 2000 message for reporting binary status conditions. While many Victron products transmit this PGN, the specific details and meaning of its status bits vary significantly depending on the product sending the message. It is crucial to refer to the specific product's documentation to correctly interpret the signals.

Binary Status Report from BlueSolar Charger 150/70 & 150/85

For the BlueSolar MPPT 150/70 and 150/85 chargers, PGN 127501 provides insights into the charger's operational status and any active alarms.

*Note: The "Solar activity" signal is available since v2.01 of the BlueSolar firmware. When the Alarm status bit is "On," the specific alarm reason can be queried using Victron proprietary register 0xEDDA (Charger error code).

Binary Status Report from Lynx Shunt VE.Can

Since firmware version 1.07, the Lynx Shunt VE.Can transmits PGN 127501 for both alarm reasons and relay trigger reasons. The mapping of the status bits is identical for both types of messages. To differentiate between them, the Lynx Shunt uses different message instances:

• The default instance for the alarm message is 0.
• The default instance for the relay message is 1.

Alarm and relay thresholds for the Lynx Shunt can be configured using Victron proprietary registers. Specific details on these registers are not provided in the general PGN documentation.

Binary Status Report from Skylla-i

The Skylla-i charger also utilizes PGN 127501 to report its status, including relay activity and alarm conditions.

Similar to the BlueSolar chargers, if the Alarm status bit is "On," the specific alarm reason can be queried using Victron proprietary register 0xEDDA (Charger error code).

Binary Status Report from VE.Direct to VE.Can\NMEA 2000 interface

For detailed information regarding the PGN 127501 implementation on the VE.Direct to VE.Can\NMEA 2000 interface, consult the specific manual for that device.

Binary Status Report from VE.Bus to VE.Can\NMEA 2000 interface

For detailed information regarding the PGN 127501 implementation on the VE.Bus to VE.Can\NMEA 2000 interface, consult the specific manual for that device.

Safety: Interpreting Communication Data

While working with data communication protocols like VE.Can and NMEA 2000 does not typically involve direct electrical hazards in the same way as battery or inverter work, misinterpreting data can lead to incorrect system operation or diagnostics.

• Verify Data Sources: Always ensure the data you are interpreting comes from the correct device instance and is relevant to the product you are monitoring.
• Consult Specific Manuals: As seen with PGN 127501, the meaning of status bits can vary significantly between Victron products. Always refer to the specific product's manual for accurate interpretation.
• Proprietary Registers: When dealing with proprietary registers for alarm queries or threshold configurations, ensure you have the correct documentation. Incorrectly writing to these registers can lead to unintended system behavior.

When to call a technician instead

While understanding PGN details can aid in system diagnostics, complex communication issues or the need to configure proprietary registers often require specialized knowledge. You should call a qualified Victron technician if:

• You are unable to establish communication between Victron devices and an NMEA 2000 network despite verifying physical connections.
• You need to configure alarm or relay thresholds using Victron proprietary registers, and the specific register details are not publicly available or clear.
• You suspect a firmware issue affecting PGN transmission or interpretation.
• You are integrating Victron equipment into a critical system where misinterpretation of data could lead to significant operational problems.
• You are dealing with issues that require access to internal components or advanced diagnostic tools beyond standard network monitoring.