Safiery CANbus Alternator Controller

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.

18

Powered by