CAN messages summary The following summarizes the pgns sent and/or received via the WS500 Alternator Regulator over the CAN bus. Items in BOLD are utilized by the WS500 (Sent or received) – though the actual messages may be impacted if a subsystem is enabled as well as if the WS500 is operating as the RBM for the system.
Instances: A key concept for all the CAN based communications is Instances. Instances allow for the identification of unique devices and the messages associated with such devices. The WS500 utilizes 3 distinct ‘Instances’:
Battery Instance
Charger Instance (Alternator)
Charger Instance(s) (DC-DC Converter)
2 nd Battery (Low Side) instance (DC-DC Converter) Engine Instance
When parsing CAN based messages, it is important to keep the concept of Instance in mind. A detail of NMEA2000 messages: NMEA2000 defines the 1 st occurrence of a Battery Instance as 0, while RV-C uses 1 (0 is invalid). For NMEA2000 messages the WS500 will use ‘BatteryID - 1’.
Charger Instances will use the OSEnergy standard (RV-C compliant) representation of instances. Alternator based messages will be represented with (Charger Instance + 0x30); 0x30 being assorted with ‘Engine Driving’ charging sources. As an example: The 1 st ‘charger’ instance will be 49 (for WS500 instance #1), and 50 for a 2 nd WS500 if installed.
The user is able to configure any of these Instance numbers (Battery, or Charger) – and details are up to the installer.
DC-DC Converter: If the optional DC-DC converter is installed and configured additional status messages will be sent. The Instance number used by the DC-DC converter as associated with the primary battery will be:
DC-DC Converter Charger Instance = $CCN <Device Instance > + 0x70 2 nd (Low Side) battery Instance : o $CCN<Battery Instance Override> + 1
74
Powered by FlippingBook