Safiery CANbus Alternator Controller

This interactive publication describes the best way to get maximum capacity life from an investment in Lithium Batteries in an RV, Caravan, Motorhome or 4WD. Covers the new CANbus technology and the breakthrough in cost reduction from a 48-12V Hybrid.

+ve terminal is on the side of the shunt closest to the battery. If the shunt is on the positiv power circuit, then the -ve is closest to the battery.

P-TYPE

TARGET BATTERY + TARGET BATTERY -

TARGET BATTERY CURRENT SENSING + TARGET BATTERY CURRENT SENSING -

twisted pair

CAN +

IGNITION

ALTERNATOR. GROUND

LED / Function out

CAN –

18/19

FUNCTION IN

ALTERNATOR +

16/17

* FIELD

STATOR IN

20AWG 10K NTC M10

TEMPERATURE PROBE TEMPERATURE PROBE

Grey Cable To Alternator

TEMPERATURE PROBE TEMPERATURE PROBE

¥ £

_ _ _ _ _ £ _ _ _ _ £ £¦ ¦

¡ ¢

£¢

£ ¤

POSITIVE

12V BUSBAR POSITIVE

Load Load Load Load Load Load

VRM WORLD

To Cerbo To Mini BMS

5A 5A Fuse

Smart Battery Protect

Smart Battery Protect Ori n-Tr

30A 30A Fuse 5A 5A Fuse

Jumper Pin

To AUX Power

To 12V Distribution

VE. CAN FROM CERBO

OFF

100A MAIN SWITCH

ORION-Tr

600A MAIN SWITCH

victron energy BLUE POWER

Quattro Quattro Quattro Quattro

ARGOFET BATTERY ISOLATOR

Orion-Tr 48|12-20 isolated DC/DC coverter 24 3

OFF

Scotty Buck- Boost

victron energy BLUE POWER

IP43

www.victronenergy.com

Input Output Power

I 32-70V I 10-15V I 240W (20A) 16 35 36 3

on/off

ARGOFET BATTERY ISOLATOR

INPUT OUTPUT

ENERGIZE

OUTPUT-2

OUTPUT-1

INPUT

GROUND

+ -

H L

100A 2 Output

200A 2 Output

ARGOFET Battery Isolator

100A 3 Output

200A 3 Output

victron energy BLUE POWER

www.victronenergy.com

Alternator Controller

Trailer / AUX

ENERGIZE

OUTPUT-2

OUTPUT-1

INPUT

GROUND

4 3 2 1 5

100A 2 Output

200A 2 Output

Starter Battery +

ARGOFET Battery Isolator

100A 3 Output

200A 3 Output

SMART BATTERY PROTECT 12V/65A

48V

12V

ArgoFET Buck-Boost Battery Switch

IGNITION

Ignition Switch 12V Power Battery GND

12V

SMART BATTERY PROTECT 12V/65A

4284V

D+

B+

B-

CAN Hi CAN Low

FUSE

Switch On/Off Mini BMS

Charge light

BMS-CAN FROM CERBO GX BMS-CAN FROM CANbus BATTERY

12V 24V- 10A

OFF

victron energy BLUE POWER

Switch On/Off

600A MAIN SWITCH

12.8V-100Ah Lithium Smart LiFePO4

ARGOFET BATTERY ISOLATOR

BTV CABLE

12V 48 12 24

POSITIVE BUSBAR

Smart LiFePO4 24V-200Ah

CYRIX Li CHARGE 230

victron energy BLUE POWER

www.victronenergy.com

Smart Battery Protect

Alternator Argo FET Scotty Buck-Boots

ENERGIZE

OUTPUT-2

OUTPUT-1

INPUT

GROUND

100A 2 Output

200A 2 Output

ARGOFET Battery Isolator

Battery Switch

100A 3 Output

200A 3 Output

CYRIX Li CHARGE 230

Scotty Battery Positive Sense

Scotty Power In Orion-Tr

POS.

NEG.

MPPT

victron energy BLUE POWER

MultiPlus Batt + MultiPlus Batt +

Starter Battery +

12.8V-100Ah Lithium Smart LiFePO4

CERBO

ArgoFET

IGNITION

Smart Shunt VE.BUS Smart Shunt

BMS-CAN FROM CANbus BATTERY

D+

OFF

B+

B-

mini BMS

BMS-CAN FROM CANbus BATTERY

OFF

FUSE

600A MAIN SWITCH

CHARGE DISCONNECT POWER+ LOAD DISCONNECT ALARM LED + POWER-

Load Disconnect Charge Disconnect

20A Fuse

12V

IGNITION

ON/OFF SWITCH ON/OFF SWITCH

600A MAIN SWITCH

Smart LiFePO4 12.8V-200Ah Lithium

M8 CIRCULAR CONNECTORS

MULTIPLUS

QUATTRO 15KW/48V/200V AC INVERTER/CHARGER

BMS-CAN FROM CANbus BATTERY

MULTIPLUS 3KW/12V/230V AC

INVERTER/CHARGER

CENTRAL NEGATIVE BUSBAR

victron energy BLUE POWER

Smart Battery Protect Smart Battery Protect Battery Switch Cyrix

www.victronenergy.com

12.8V-100Ah Lithium Smart LiFePO4

victron energy BLUE POWER

CERBO VE.BUS Mini BMS

charger

inverter inverter on overload

www.victronenergy.com

BMS-CAN FROM CANbus BATTERY BMS-CAN FROM CANbus BATTERY BMS-CAN FROM CANbus BATTERY BMS-CAN FROM CERBO GX

mains on bulk absorption float

Battery Sense Scotty Battery Sense

I on

AC in 1

AC out 1

victron energy BLUE POWER

charger only O off

low battery temperature

AC in 2

AC out 2

Argo FET rgo F T Argo FET 2 Buck Boots

charger

inverter inverter on overload

OFF

Quattro 48 |15000 |200

.sinewave inverter .parallel connectable

.transfer switch .three phase connectable

.battery charger .powerassist

mains on bulk absorption float

Battery

I on

AC in 1

AC out 1

charger only O off

AC transfer capacity: 2x100A | Inverter 120V

low battery temperature

AC in 2

AC out 2

600A MAIN SWITCH

Orion-Tr

.battery charger .powerassist

.sinewave inverter .parallel connectable

.transfer switch .three phase

Battery

VE.Bus-1 VE.Bus-2

MultiPlus 12 |3000 |120

MPPT

AC transfer capacity: 50A | Inverter 230V

BATTERY

Alternator Buck-Boots Scotty

BATTERY

IN 1

OUT 1

OUT 1-2

OUT 2

IN 2

BATTERY _ _

VE bus1 VE bus2

L N

L N L

L N

BATTERY + +

RELAY GND

CHARGE TRICKLE

V-SENSE T-SENSE AUX1 AUX2

+ -

S1 S2

NC NO

COM NC NO COM

GROUND

AC IN-1

AC OUT-2

AC IN-2

AC OUT-1

GROUND

VE-BUS MAINS DETECTOR

1 2 S1 S2

TRICKLE CHARGE

GROUND

build inside MultiPlus

MultiPlus Batt- MultiPlus Batt- M l s e MultiPlus Case ground Q attro Case ground

AC input

OFF

victron energy BLUE POWER

RCBO 24001000 10A 240V

SHUNT

GPOWBSP2XS

12.8V-100Ah Lithium Smart LiFePO4

600A MAIN SWITCH

Conn-A AC IN 240V AC OUT 240V AC OUT Conn-A AC IN

Conn-A AC IN 240V AC OUT 240V AC OUT

VE.BUS

VE Bus mains detector

Lynx Distributor+ Lynx Distributor+ Lynx Distributor- LynxDistributor- Battery- Battery+

Batt+ Batt+ Batt- Batt-

BTV CABLE

Quattro Case ground M ltiplus Case ground

MultiPlus Case ground

BMS-CAN FROM CERBO GX BMS-CAN FROM CANbus BATTERY

Smart LiFePO4 24V-100Ah

Earth

July 04 20

Date:

Note:

Job number:

Customer Name:

Buck-Boost 1 CAN-L CAN Bus High Level I/O ; “high” in “dominant” state CAN Lo 2 CAN-H CAN Bus Low Level I/O ; “low” in “dominant” state CAN Hi 3 ON/OFF Referenced to GND pin, used to turn converter on and off. Positive logic. - IGN Switch 4 GND Connected to GND terminal 5 POWER1 External power supply voltage (from LS battery) for powering CAN and internal bias.

Description:

Design for Victron Lithium Battery System with CAN Alternator Control i 48V Lithium Battery S stem, 12V or 24V Alternator, 12V o 24V-48V CAN-bus Buck Boost, CAN-bus Alternator Control esign for Aries Ra l: 24V Lithium Battery System, 24V Alternator, CAN-bus Alternator Control

Confidential and Proprietary Safiery Pty Ltd

® O

W AKESPEED

FFSHORE

Communications and Configuration Guide

V2.4.3a - Revised Sept , 2021

T ABLE OF C ONTENTS About this guide

ASCII communications

CAN (Control Area Network) Communications

A note on Feature-In port

Receiving data FROM the regulator:

Sending data TO the regulator:

Appendix A: CAN enabled BMS

Appendix B: CAN messages

Appendix C: Sample Yacht Devices CAN-CAN bridge scrip

Appendix D: Details of CPE (Charge Profile Entries)

Appendix E: Default System Configuration

Appendix F: Error codes and meaning

A BOUT THIS GUIDE

The Wakespeed® Offshore series of product offerings features a common set of configuration and communications capability. This guide is used to document both Serial (ASCII) communications and CAN (Control Area Network) capabilities. Refer to the individual devices user’s guide for additional details. Using the information in this guide one can access advanced configuration capabilities of the WS500 Alternator Regulator, as well as create a vertical stacked solution with tight integration between the regulator, BMS devices, Displays and engines. More so, this guide will be helpful in the development of supporting applications to aid in the configuration and use of the WS500 Alternator Regulator.

A note of NMEA2000 tm

NMEA2000 is a registered trademark of National Marine Electronics Association. In this guide there are references to NMEA2000, which are an artifact of the underlying J1939 support library used by the WS500 Alternator Regulator. The WS500 Alternator Regulator makes no claim of the correctness, compatibility, nor support for any NMEA2000 installation.

A note of edits and revisions

As this document is revised, new additions or capability will be placed in RED text. It is hoped this will aid in the quick assessment of new features. This release is intended for use with Firmware v2.4.3 or above.

2.4.3 Notes:

The v2.4.3 release fixes primarly on improved support to LiFeP04 batteries, and more specifically those in which the BMS is CAN connected. Some notable changes of this release include:

 Improved stability of battery current regulation when using CAN connected BMS’s for remote instrumentation of battery current.  Addition of new BMS Max Current to the $SCA: parameter.  Corrected CAN message “ Charger Configuration Status - 1FFC6h ”, Sending Battery Type.  Removed lockout = 2 option in $SCO. 2 now behaves the same as 1.  Documented new DEP command to allow checks of required firmware support in configuration files.

ASCII COMMUNICATIONS The WS500 Alternator Regulator features a Micro USB port to allow for advanced monitoring / diagnostics, configuration, as well as firmware updates. Simply connect a USB cable (making sure it is a proper data USB cable, and not a charger-only cable) between your computer and the USB micro port. Any needed drivers should install automatically, though you may need a connection to the internet depending on your operating systems.

Terminal Programs Many operating systems have built in terminal programs. After connecting the regulator to the computer you can use one of these to open a communications window to the WS500 Alternator Regulator. A special note, some terminal programs do not send a complete end-of-line terminator (CR+LF). To support these environments, the WS500 Alternator Regulator will recognize the character ‘@’ as an alternative EOL indicator.

Remember that any configuration changes you make to the regulator may not take effect until the regulator is restarted. When you have finished, make sure to issue the $RBT: command to not only assure changes are saved to the regulator ’s non-volatile memory, but that the changes are then utilized by the regulator. (refer to $RBT: - ReBooT system on page 65). After rebooting the WS500 Alternator Regulator verify the changes you sent were recognized by the regulator by inspecting the various status strings.

Putty: A versatile option is the free ‘Putty’ program ( www.putty.org ) . It supports a wide range of OSs and includes a very nice logging function. To use connect up the USB cable and start Putty. Configure as shown here – selecting the Serial Line which your USB serial port is associated with, and setting the speed to 115200 and clicking the Serial Connection Type redial button.

Next click on the Terminal category and click the Forced-on button for local echo (as indicated on the following page), this will assure you can see what you are typing.

Finally, if you wish to keep a logfile of the session click on the Logging category, enter a file name and select the ‘Printable Output’ button as shown here:

Logging sessions is very helpful for debugging your installations, the files are comma separated and easily import into Excel using the import wizard specifying commas (,) as the separator. Refer to Receiving data FROM the regulator: for details on the output. Once you have done your configuration press the Open button to start the terminal session. A hint for WIncows users: If you have a need to Paste anything into Putty, know it does not use the normal CTRL-V command. Instead, position the cursor in the black display windows and click the RIGHT button, that will cause the clipboard to be pasted and sent to the WS500.

Bench-top Configuration: When a USB cable is connected to the WS500 Alternator Regulator power is supplied to the logic portion of the hardware. This allows you to do bench-top configuration before completing the installation on the actual alternator. Make sure to do a $RBT: command as your last step. After the regulator reboots make sure to verify your changes before installing the regulator in a live installation.

CAN (C ONTROL A REA N ETWORK ) C OMMUNICATIONS The WS500 Alternator Regulator features CAN (Control Area Network) ports. Developed in the 1980’s by Bosch and targeted towards the transportation sector, CAN is now one of the most widely deployed communications standards covering not only the Transportation sector but also used in Industrial, Heavy Industry, Farming, Medical, Consumer, and more. Over a billon CAN nodes have been deployed, with modern automobiles contained upwards of 100+ individual nodes each! It is a proven reliable and robust communications standard with many feature to assure deterministic and prioritized communication resulting in a solid and proven reliable communications backbone. Utilizing CAN devices are able to integrate into a ‘System’ where each works in cooperation with the others. Further, the CAN allow simple and reliable way to connect computers or displays for ongoing monitoring and easy configuration. The WS500 Alternator Regulator utilizes standards covering physical wiring, message content and other communications standards. These include:

CAN Specification 2.0b / ISO-IS 11898



CiA 303



SAE J1939



 OSEnergy (Open Systems Energy - derived from the RV-C standard)

OSEnergy (Open Systems Energy) is an architectural specification who's aim is to provide a framework for the design, deployment, and operation of charging sources associated with a DC battery. Allowing them to work together in a 'systems' approach while meeting the full requirements of an associated battery as well as concurrently supplying house power needs in a consistent and efficient way. You can learn more here: https://github.com/OSEnergy/OSEnergy

Through the application of these standards the WS500 Alternator Regulator is able deliver several key benefits, including:

 Coordination of charging goals and objectives; all devices work towards the SAME goal vs. fighting each other.  Tight BMS integration. CAN communications allows for the WS500 Alternator Regulator to fully integrate with the needs and directions of a BMS at levels unattainable using simple ‘Charge Enable’ wires.  Prioritization of charging sources, e.g.: Utilization of Solar to its maximum capability while filling in the remaining energy needs from an engine driven alternator - thereby saving fuel.  Remote sensing / Port Expander: The WS500 Alternator Regulator is able to take advantage of the CAN communications capability to transfer real-time battery status: voltage, amperage, and temperature as well as operational status (e.g., off-line in the case of a LiFeP04). By using this capability wiring and installations may be simplified.  Self healing / fail over: Ability to self-recover from a failed, removed, or turned off device. The system continuously monitors all devices and adjusts as needed.  ‘Get - Home’ total system failure mode: In the event of a catastrophic total system communications failures, the WS500 Alternator Regulator will fail-to-safe and operate in a stand-alone mode. Allowing for continued charging, but perhaps with less optimization and longer times needed.

CAN wiring Use good quality CAT-5, CAT-5e, or CAT-6 cable to connect between devices in a daisy-chained fashion plugging into one of the two RJ45 connectors on the regulator. At each end of the daisy-chain install a terminator plug into the open RJ45 connector. It is important that the CAN bus be a single end-to-end chain with termination at each end. DO NOT connect an extra CAT-5 cable between the end devices making a loop – instead make sure each end point has one open RJ45 connector and then plug in the terminators.

The total length of the CAT-5 daisy- chain should be kept under 100M (300’) with no more than 100x nodes total f or best reliability.

The RJ45 connectors follow the CiA-303 standard, as shown here:

Figure 1 – CiA 303 CAN RJ45 connector specification

Connect the CAN_H and CAN_L signals. If supported, CAN_SHLD may also be optional connected as needed. It is generally NOT recommended to connect the CAN_GND to anything, as this may create a ground loop between it and ALT-

NMEA-2000® Support NMEA2000 is a Registered Trademark of the National Marine Electronics Association, at the time of this writing Wakespeed is not a member of NMEA and makes no claims of the TM, nor is making climes of official support of the NMEA2000 standard.

The WS500 Advanced Alternator Regulator CAN protocol shares the same foundation and electrical specifications as NEMA2000, and is able to produce messages which may often be displayed on a NMEA2000 device. It needs to be noted, the WS500 is NOT a certified NMEA2000 compliant device, and its support is a byproduct of the J1939 library used. But in many cases connecting to a NMEA2000 network is successful. If you have issues with either the NMEA2000 or OSEnergy communications capabilities disconnect the regulator; alternatively one may try using a NMEA2000 certified CAN bridge such as the Maretron USB100 Gateway, or Yacht Devices YDNB-07 Bridge. In both cases it might be helpful to configure the bridges to filter out non-NMEA2000 messages (See Appendix C: Sample Yacht Devices CAN-CAN bridge scrip for a sample YDNB-07 script to accomplish this). Wiring: To connect into an existing NMEA-2000 network you will need to make up a patch cable. The simplest way to do this is to cut one end off a common CAT-5 cable and attach a Micro connector. Referring to “ Figure 1 – CiA 303 CAN RJ45 connector specification “ above as well as “ Figure 2 - NMEA2000 connector pinout “ below only the CAN_H and CAN-_L wires need to be connected. With either approach take care not to exceed the maximum Drop-cable length of 6 meters, take care to properly terminate the CAN network and use the following as a wiring guide:

CAT-5 Cable

NMEA2000 Cable

Signal

POSITION

COLOR

POSITION

COLOR

CAN_H

White/Green --OR-- White/Orange

White

CAN_L

Green --OR-- Orange

Blue

Figure 2 - NMEA2000 connector pinout

There is no need to connect the CAN-GND, and in fact doing so may cause reliability issues due to ground-loops.

A limited number of NMEA2000 TM like status output messages are supported. These messages may be useful when the WS500 is connected to a NMEA2000 network and will allow the operational status of the alternator and battery to be displayed. Refer to Appendix B: CAN messages for a list of supported messages. Note that the WS500 will send two groups of some of the NMEA2000 messages, one set for the Battery and one set for the Regulators operation. Refer to the details of each PGN. Be sure to properly configure the regulator when using these messages, specifically the `Engine ID’ and ‘Charger Instance’ using the $CCN: command, and note also that the Battery Instance number transmitted in NMEA2000 messages is reduced by 1 from the WS500 Battery Instance (NMEA2000 uses 0 oriented numbering, while RV-C uses 1 oriented numbering).

A NOTE ON F EATURE -I N PORT The Feature-in port allows a wide range of optional capabilities in the WS500 to be selected in real time. Throughout this configuration guide there are a number of places where the Feature-In port may be enabled to be looked at to select a given capability. There are also options to modify the behavior of the Feature-In port from its normal behavior. Care should be exercised when configuring the WS500 to assure that the desired behavior of the Feature-in port is selected, and that some other expected use has not inadvertently been disabled. Example, by utilizing the Feature-In port to allow to selection of an alternative DC-DC converter set point, the default behaviors of forcing the regulator mode to Float with CPE #8 will be overridden; this could cause unexpected behaviors if the system design expects to use the Feature-in port for a legacy BMS integration.

Feature-In can be used as

1. Force Equalize (when using CPE #7) 2. Force Float (when using CPE #8)

3. Force whitespace (setting RMP to positive value in CNG when in CPE #8. Negative value of RPM in CNG forces whitespace on all the time ignoring Feature-In. Pos/New values of RPM in CNG are ignored when in CPE 7.)

4. Force regulator power (setting dHalf 0 in SCA) 5. Feature-In polarity change for any of the above.

R ECEIVING DATA FROM THE REGULATOR :

Receiving data FROM the regulator:

AST; -- ALTERNATOR STATUS

DST; -- DC-DC ENERGY TRANSFER STATUS

DCV; -- DC-DC ENERGY TRANSFER CONFIGURATION

$DEP: - DEPendency

CST; , -- CAN STATUS

CPE; -- CHARGE PROFILE ENTRY

NPC; -- NAME & PASSWORD CONFIGURATION

SCV; -- SYSTEM CONFIGURATION

SST; -- SYSTEM STATUS

FLT; -- FAULTED

AOK; -- ACKNOWLEDGE

NAK; -- NEGATIVE ACKNOWLEDGE

DBG; -- DEBUG

RST; -- RESET

All status outputs are suspended during the receiving and processing of a command string. In this way, a command which expects a response (ala $RSC:) can be assured the next string sent back by the regulator is the response to the requesting command (though one should still do error checking and validation, as the simple regulator will often ignore commands containing a syntax error in them) Formats are in clear ASCII using comma separated fields. Note the presence of double commas (separated by a space) between major ‘sections’, this is to simplify manual reading of the strings. Each string is delivered as one continuous line with a CR/LF termination.

Additional details of each status may be discovered by examine the command string for changing those parameters.

AST; -- ALTERNATOR STATUS AST: “AST ;, Hours, , BatVolts, AltAmps, BatAmps, SystemWatts, ,TargetVolts, TargetAmps, TargetWatts, AltState, ,BTemp, ATemp, ,RPMs, , AltVolts, FTemp, FAmps, FLD% ”

Hours:

Time regulator has been powered up, in hours and fraction (to 2 digits) of hours.

BatVolts:

Derived Battery Volts, in volts and fractions of volts (to 1mV resolution). Used to decide change mode changes.

Measured Alternator Amps, in Amps and fraction of Amps (to 1/10 th of an Amp).

AltAmps:

BatAmps:

Derived Battery Amps being used to decide charge modes.

Voltage and current readings made by the WS500 Alternator Regulator are directly reported as AltVolts and AltAmps . Unless overridden by an external source (example via a Remote Battery Sensor) those same values will be assumed to be BatVolts and BatAmps and used by the regulator to make charge state decisions.

SystemWatts: Current measured System Watts being delivered.

TargetVolts:

Volts the regulator is attempting to bring the battery to. This value is the ACTUAL voltage value being driven to, and reflected the adjusted Charge profile entry and the sysVolts index value.

TargetAmps*: Amps the regulator will limit the alternator to. This value is the ACTUAL amperage being driven to, and reflecting the derating and half power mode adjustments.

TargetWatts*: Watts the regulator is actually working to limit the system to.

AltState:

Current state of the Alternator, per the following table:

Value 0,1,4

- Alternator Off

2,3

- Alternator FAULTED (See Fault Code) - In special DC-Disconnected CV mode.

6 - Alternator in Idle (Ala, Half-power Mode with active DCDC converter) 9 - In CONFIGURATION mode 10 - Alternator Standby mode, or in delay mode while engine warms up. 11,15 - Ramping towards BULK mode. 12,20 - In BULK mode 21 - In ACCEPTANCE mode 22 - In OVER CHARGE mode 30 - In FLOAT mode 31 - In FORCED_FLOAT mode (via Feature_in pin and CPE = #8) 36 - In OFF (Post Float) mode 38 - In EQUALIZE mode 39 - In CVCC mode (only available in system under direction of CAN master)

BTemp:

Measured temperature of NTC sensor attached to B-port in degrees C or battery temperature received via external CAN sensor. -99 indicates temperature has not been measured, NTC sender has failed, not attached, and there is no remote temperature information available via the CAN connection. Measured temperature of NTC sensor attached to A-port in degrees C. -99 indicate temperature has not been measured, or NTC sender has failed. -100 indicates the Alternator temp NTC probe is shorted (to select ½ power mode)

ATemp:

RPMs:

Measured RPMs of engine (Derived from Alternator RPMs and the Engine/Alternator drive ratio)

(The following additions are available with Firmware version 1.0.0 and above) Measured Alternator Volts, in volts and fractions of volts (to 1mV resolution)

AltVolts:

FTemp:

If equipped, this is the temperate of the FETs in degrees C. -99 indicated FET temperate cannot be measured.

FAmps:

If equipped, this is a measurement of the current (amperage) being delivered to the field. -99 indicated field current is not being measured.

FLD %:

% (0..100%) field is being driven.

Note: * If the WS500 Alternator Regulator is configured with no limits for Alternator Amps and/or System Watts a self- impose limits of 1,000A / 15,000W as max values. AST; will report these working values.

DST; -- DC-DC ENERGY TRANSFER STATUS “D ST;, DCDC_State, Volts, ,SecondBatVolts, SecondBatCurrent, PrimBatCurrent, DCDC_Temp ”

DCDC_State:

Operational status of optional DC-DC converter. See AltState table above for additional details.

Value 0

- Converter Off (or not present) - Converter in Standby mode

1,4 2,3

- FAULTED (See Fault Code below) 10..40 - Charge Assist Modes: (Reference AST Table above) 71 - 2 nd Battery augment mode.

Volts:

Presently active target Voltage goal/trigger. (See $CDD on page 60 for details)

SecondBatVolts: Measured Secondary battery voltage as reported by the DC-DC converter. Note this may be remotely senses battery voltage, or it may simply be the voltage at the DC DC Converts Secondary Battery terminals.

SecondBatCurrent: If DC-DC Converter is capable, this is the measured current of the secondary battery.

PrimBatCurrent: If DC-DC Converter is capable, this is the measured current of the primary battery.

Note: In both the Primary and Secondary battery current, the values reflect current supplied/consumed by the DC-DC Converter only, not the entire battery. A Positive value indicated energy transfer out of the DC-DC Converter and INTO the respective battery

DCDC_Temp: Internal temperature of the DC_DC Converter, in degrees C

Note: DST: will only be sent if the optional DC-DC converter has been configured and enabled (See $CDD: command on page 60 ). If enabled, it will alternated with the AST status string.

DCV; -- DC-DC ENERGY TRANSFER CONFIGURATION “D CV;, Model, Mode, , Volts, Volts_HalfPower, ,Assist Limit Amps, ,Aug Limit Amps, Aug Limit Volts, Aug Limit SOC ”

Model:

Model of DC-DC Converter configured to support (See $CDD: command)

Mode:

Operational mode of optional DC-DC converter bridging the Primary(Target) and Secondary battery.

2 nd battery Target voltage, above this charge assist mode is enabled.

Voltage:

2 nd battery Target voltage when regulator is in Half-power mode

Volts HalfPower:

Assist Limit Amps: Max current while in primary battery Charge Assist mode.

Aug Limit Amps: Max current while in 2 nd battery augmentation mode.

Aug Limit Volts: Primary battery voltage cutoff, below this 2 nd battery augmentation mode is disabled.

Aug Limit SOC: Primary battery SOC cutoff, below this 2 nd battery augmentation mode is disabled.

Note: DCV: will only be sent if the optional DC-DC converter has been configured, ala the Model is not set = None. (See $CDD: command on page 60 )

$DEP: - DEPendency Dependency is a way to allow the device to confirm both the correct device type, as well as a minimum firmware version required to utilize this configuration. In most cases sending in configuration strings with additional parameters (ala, new capabilities) that the present level of firmware, the device will simply ignore the extra parameters; and this might cause undesirable behavior. Beginning with firmware version 2.4.2, an optional $DEP may be used to allow the device to check to see if the firmware is able to support all configuration commands and parameters.

$DEP: <Version>, <Version> …

Version: (String) ‘ Version’ is in the same form as that reported out by $SST: and contains both the device type as well as a minimum release of firmware needed. Take care when declaring <version> as the format is well defined: mmmmxx.yy.zz

mmmm: a 4 character string containing the device type. Supported devices types are:

 AREG: WS500 Alternator Regulator; OEM branded are also an AREG device.

 DCDC: WS3000r DCDC Converter. OEM branded is also a DCDC device.

xx, yy, zz: Numeric values separated by two ‘.’ xx, yy, zz must be complete and numeric (No wide cards allowed). The device firmware must be equal to or greater than the defined xx, yy, xx

Examples of $DEP are:

 WS500 Alternator Regulator, firmware must be 2.4.2 or above

AREG2.4.2

 WS3000r DCDC Converter, firmware must be 2.4.3 or above.

DCDC2.4.3

$DEP: DCDC2.4.3, AREG2.4.2 @

CST; , -- CAN STATUS “CST;, BatteryID, IDOverride, Instance, Priority, ,Enable NMEA2000?, Enable OSE?, ,AllowRBM?,IsRBM, ShuntAtBat?, ,RBM ID, IgnoringRBM?,Enable_ALT_CAN, ,CAN_ID, ,EngineID, BitRate, Aggregate BMS ”

BatteryID:

Battery number (or Instance) the regulator is associated with. 1..100 The following ‘convention’ is suggested – but not required: 1. Main House Battery 2. Primary Engine Starter battery (port engine) 3. Secondary House Battery 4. Secondary Engine Starter battery (starboard engine)

5. Generator Starter Battery 6. Forward Thruster battery 7. Aft Thruster Battery

IDOverride:

Battery number (or Instance) is set via the DIP switches, however it is possible to ‘override’ the DIP switches using the $CCN: command. (0= no override)

Instance:

Charger Instance (1..13). Set with $CCN: command (Default = 1)

Priority:

Device priority, used to decide which devices should provide charging current, as well as who will be potential ‘master’ device. Set with $CCN: command (Default = 70)

Enable NMEA2000?:

0 or 1, Is regulator configured to send NMEA-2000 like messages? (1 = Yes)

Enable OSE?:

0 or 1, Is regulator configured to send OSEnergy type messages? (1 = Yes)

By using the $CCN: command, the user may disable portions of the CAN message stack. One would do this in cases where conflicts exist with existing devices on a shared CAN bus. An example might be the regulator is installed into an existing NMEA-2000 system, and it is desired to have NMEA-2000-like status be sent out; however some of the OSE messages cause issues with existing NMEA-2000 instruments. In this case the user may choose to disable OSE messages. CAUTION: If OSE messages are disabled, all CAN-based value-add capabilities of the regulator will also be disabled. Including remote instrumentation, common charging goal, and charging device prioritization. DISABLE OSEnergy MESSAGING WITH CAREFUL CONSIDERATION and perhaps consider setting up isolated networks instead with a CAN bridge to forward the NEMA2000 messages to the proper NMEA2000 bus.

AllowRBM?:

0..2: Is regulator configured to attempt to act as the Remote Battery Master? (1 = RBM, 2 = ‘Virtual RBM’ )

IsRBM?:

0..2: Does regulator currently think it is the Remote Battery Master? (1 = RBM, 2 = ‘Virtual RBM’)

ShuntAtBat?: 0 or 1, Does regulator currently think its shunt is directly connected to the battery? (1 = Yes, default = 0)

The WS500 Alternator Regulator is able to assume the role of the Remote Battery Master, thereby acting as the central coordinator for all charging sources. In practice, using the regulator as the RBM typically would occur only with small installations, twin engines installations are a common example. However, one is also able to configure a more extensive system where the WS500 Alternator Regulator is configured as a backup device. Set this via the $CCN: command

RBM ID:

Remote Battery Master ID: ID number of remote device which is currently recognized as the Remote Battery Master. 0 = WS500 Alternator Regulator has not associated itself with RBM.

IgnoringRBM?: 0 or 1, Is the regulator ignoring the Remote Battery Master? (1 = Yes)

If the Remote Battery Master sends information which seems unbelievable, this flag will be set and the regulator will ignore it. Such a condition indicates something is wrong in the overall system and that should be investigated and resolved. Conditions which will cause this fault include:  Indicated Battery Voltage too high, or too low. (8..18v for normalized 12v battery)  Indicated Battery Current too high (> +/- 2,000A)  Voltage difference between battery and alternators > 1.5v (indicating issue with alternator wiring)  Enable_ALT_CAN: Bit-mask enabling alternative CAN based remote sensing and/or RBMs. See $CCN: on page 55 for details.

CAN_ID:

This is the current CAN Node ID, or node address which the WS500 Alternator Regulator has been assigned.

EngineID:

Engine ID (or number) the WS500 Alternator Regulator with the engine it is mounted on. Used for monitoring J1939 RPMs messages as well as sending NMEA2000 RPMs back out. Note by convention EngineID = 0 is the default value.

BitRate

Data communication rate CAN is set for.

Aggregate BMS: Indicates optional aggregation of BMS / RBM ’s.

CPE; -- CHARGE PROFILE ENTRY In response to RCP: command, this displays the current values of a Charge Profile Entry. Special note on Charge Profile Entries: All voltage and cu rrent values in Charge Profile tables are displayed in their normalized ‘12v’ val ues. See Defining Charging Voltages and Amps for additional information. “CPE;, n, ac ptVBAT, acptTIME, acptEXIT, res1, , ocAMPS, ocTIME, ocVBAT, ocAEXIT, , floatVBAT, floatAMPS, floatTIME, floatRESUMEA, floatRESUMEAH , floatRESUMEV, ,pfTIME, pfRESUME, pfRESUMEAH, , equalVBAT, equalAMPS, equalTIME, equalEXIT, , BatComp, CompMin, MinCharge, MaxCharge, ,RdcVolts, RdcLowTemp, RdcHighTemp, RdcAmps, ,floatSOC, ,MaxAmps, , pfVBAT, ”

Charge Profile ‘n’ is being displayed/returned (1..8)

acptVBAT:

Target battery voltage during BULK and ACCEPT phase

acptTIME:

Time limit to stay in ACCEPT mode – in Minutes.

acptEXIT:

Amp limit to trigger exiting ACCEPT mode

res1:

Reserved for future use (dV/dT exit criteria, currently = 0, disabled)

ocAMPS:

Max Amps which will be supplied by during OVERCHARGE mode.

ocTIME:

Time limit to stay in OVERCHARGE mode – in Minutes.

ocVBAT:

Target battery voltage during OVERCHARGE phase

ocAEXIT:

Amp limit to trigger exiting OVERCHARGE mode

floatVBAT:

Target battery voltage during FLOAT phase

floatAMPS:

Max Amps which will be supplied by during FLOAT mode.

floatTIME:

Time limit to stay in FLOAT mode – in Minutes.

floatRESUMEA: Amp limit to trigger resumption of BULK charge mode

floatRESUMEAH: Amp Hours withdrawn after entering Float to trigger resumption of BULK charge mode

floatRESUMEV: Volt limit to trigger resumption of BULK charge mode

Note: If the regulator is in FORCED_FLOAT mode via the FEATURE-IN pin, then none of the above checks to exit float mode (e.g., floatTIME) will be performed. However, regulation will still occur to floatVBAT and floatAMPS .

pfTIME:

Time limit to stay in POSTFLOAT mode – in Minutes, before resuming FLOAT charge mode.

pfRESUME:

Battery Voltage that will trigger resumption of FLOAT charge mode

pfRESUMEAH: Amp Hours withdrawn after entering Post Float to trigger resumption directly to BULK charge mode

equalVBAT:

Target battery voltage during EQUALIZE phase

equalAMPS:

Current limit of Alternator while in EQUALIZE mode

equalTIME:

Time limit to stay in EQUALIZE mode – in Minutes.

equalEXIT:

Amp limit to trigger exiting EQUALIZE mode

BatComp:

Temperature Compensations value per 1-degree C (normaliz ed to ‘12v’ battery)

CompMin:

Minimum temperate to apply compensation at. In degrees C

MinCharge:

Minimum temperate to charge the battery at, below this will force into FLOAT mode.

MaxCharge:

Maximum temperate to charge the battery at, above this will force into FLOAT mode.

RdcVolts:

Battery low Volts trigger for Reduced Charging

RdcLowTemp: Battery low Temperature trigger for Reduced Charging.

RdcHighTemp: Battery high Temperature trigger for Reduced Charging.

RdcAmps:

Current limit while in Reduced Charging state.

flaotSOC:

SOC level to trigger resumption of BULK charge mode .

MaxAmps:

Maximum battery charge current during any charge phase.

pfVBAT:

Target battery voltage during POST-FLOAT phase

NPC; -- NAME & PASSWORD CONFIGURATION "NPC;, Use BT?, Name, Password, , DeviceID ”

use BT?

0 or 1: Enable Bluetooth? (1 = yes)

Name:

Name of Regulator (Used for CAN device ID) (ASCII up to 18 characters)

Password:

Password (ASCII up to 18 characters)

DeviceID

Semi-Unique device ID of WS500 Alternator Regulator

SCV; -- SYSTEM CONFIGURATION "SCV;, Lockout, BTS2ATS? , RevAmp, SvOvr, BcOvr, CpOvr, ,AltTempSet, drtNORM, drtSMALL, drtHALF, PBF, ,Amp Limit, Watt Limit, , Alt Poles, Drive Ratio, Shunt Ratio, ,IdleRPM, TachMinField, Warmup Delay, Required Sensor, DC_Disconnected_VBat, FeatureIN_mod, TriggerHalfPowerRPM, Ignore Sensor, Feature-OUT mod, , BMS Amp Cap ”

Lockout:

Current lockout level. (0..2), see $SCO: command.

0 or 1: Is BTS being used as 2 nd Alternator Temp Sensor? (1 = yes)

BTS2ATS?:

RevAmp:

0 or 1: Reverse polarity of Amp Shunt readings? (1 = yes)

System Voltage auto-detect (=0), or force (1.0x .. 4.0x  12v .. 48v)

SvOvr:

BcOvr:

Override Battery Capacity DIP switches (Dip 5/6). ( 0.00 = No)

CpOvr:

Override Charge Profile DIP Switches (Dip 2..4) (0 = No)

AltTempSet:

Target max running setpoint for Alternator, in degrees C

drtNORM:

Normal Amp reduction (de-rating) fraction

drtSMALL:

Amp reduction (de-rating) fraction when in SMALL - MODE

drtHALF:

Amp reduction (de-rating) fraction when in half-power mode.

PBF:

Pull-back factor, for reducing Field Drive at lower RPMs.

Amp Limit:

Defined Alternator size, or -1 to enable auto-sizing. Set this = 0 for installations where Alternator Sizing is not to be regulated (ala, battery focused installations). Note: During startup, and unless defined, this value will present: 1,000 Defined System size, or -1 to enable auto-sizing. Set this = 0 for installations where Watts loading is not to be regulated (ala, battery focused installations). Note: During startup, and unless defined, this value will present: 15,000

Watt Limit:

Alt Poles:

Number of poles on Alternator

Drive Ratio:

Ratio of engine and alternator drive pulley

Shunt Ratio:

Amp Shunt ratio in Amps / mV

IdleRPM:

Idle RPM value used as basis for Field Drive Reduction at lower RPMs.

TachMinField: Minimum % of field drive that will be applied if TACH MODE is enabled.

Warmup Delay:

Number of seconds after power on before entering RAMP mode.

Required Sensor: Key indicating critical sensors which have been configured via the $SCA: command

DC_ Disconnected _VBat: Indicated how charging device should behave when it received a DC-Disconnect message via the CAN.

FeatureIN_mod: Is the behavior of Feature-In being modified from default?

TriggerHalfPowerRPM: RPM value under which Half-power mode will be selected.

Ignore Sensor: Which sensors should be ignored? (Prevents unwanted noise from causes false readings)

FeatureOUT_mod: Is the behavior of Feature-Out port being modified from default?

BMS Amp Cap: Has a BMS Amperage Limit been defined?

SST; -- SYSTEM STATUS “SST;, Version , ,Small Alt Mode?, Tach Mode?, , CP index, BC Mult, SysVolts, ,AltCap, CapRPMs, , Ahs, Whs, ,ForcedTM?”

Version:

Firmware revision identifier. Will have format of “AREG” followed w/o a space by the version number. E.g., “AREG1.0.1”

Small Alt?:

0 or 1, has the user selected Small Alternator Mode? (1 = yes)

Tach Mode?

0 or 1, has user selected Tach Mode? (1 = yes)

CP Index:

Which Charge profile (1..8) is currently being used?

BC Mult:

What adjustment factor for Battery Amp Hour Capacity (1-10x) is currently being used? Fractional values may also be used to fine tune the system to a given battery size. This needs to be entered via the $SCO: command.

SysVolt:

Detected system voltage. Adjusts target Charge Profile Volts per the following table:

Detected System Voltage

Charge Profile VOLTAGE Adjustment Factor

SysVolt

12v

24v

2.67

32v

2.667x

48v

Fractional values may also be used to support battery voltages such as 8v, 32v, 42v. Those values will need to be selected manually via the $SCO: command.

Alt Cap:

If regulator is configured to auto-determine the capacity of the alternator, this will be the current high-water mark noted.

CapRPMs:

And this will be the RPMs at which that capacity was noted at.

AHs:

The number of Amp-Hours that have been produced in the current charge cycle.

WHs:

The number of Watt-Hours produced in the current charge cycle.

ForcedTM?:

0 or 1, has user forced Tach-Mode on via the $SCT: command.

Page 1 Page 2 Page 3 Page 4-5 Page 6 Page 7 Page 8 Page 9 Page 10 Page 11 Page 12 Page 13 Page 14 Page 15 Page 16 Page 17 Page 18 Page 19 Page 20 Page 21 Page 22 Page 23 Page 24 Page 25 Page 26 Page 27 Page 28 Page 29 Page 30 Page 31 Page 32 Page 33 Page 34 Page 35 Page 36 Page 37 Page 38 Page 39 Page 40 Page 41 Page 42 Page 43 Page 44 Page 45 Page 46 Page 47 Page 48 Page 49 Page 50 Page 51 Page 52 Page 53 Page 54 Page 55 Page 56 Page 57 Page 58 Page 59 Page 60 Page 61 Page 62 Page 63 Page 64 Page 65 Page 66 Page 67 Page 68 Page 69 Page 70 Page 71 Page 72 Page 73 Page 74 Page 75 Page 76 Page 77 Page 78 Page 79 Page 80-81 Page 82-83 Page 84-85 Page 86-87 Page 88-89 Page 90-91 Page 92-93 Page 94-95 Page 96-97 Page 98-99 Page 100-101 Page 102-103 Page 104-105 Page 106-107 Page 108-109 Page 110-111 Page 112-113 Page 114-115 Page 116-117 Page 118-119 Page 120-121 Page 122-123 Page 124-125 Page 126-127