$CCN: - Change parameters in the CAN Configuration table
Configure the CAN Configuration Table for this regulator
$CCN: <Battery Instance Override>, <Device Instance >, <Device Priority>, <AllowRMB?>, <ShuntAtBat?>, <Enable-OSE?>, <Enable-NMEA2000?>, <Enable_ALT_CAN?>, <Engine ID>,<BitRate>,< DC_ Disconnected _VBat>, <Aggregate_BMS>
Battery Instance Override:
<WHOLE NUMBER ( 0 100 )> What battery instance is this device associated
with? (1..100). Set = 0 to use DIP switches for selection.
Device Instance: <WHOLE NUMBER ( 1 13 )> Which instance of charging devices is this? Allows unique identification of charging sources. Device Instance is mostly used by external displays. It is considered good practice to give each regulator a unique Device Instance number, however if the installer fails to do that the WS500 will automatically adjust the Device Instance number in case of a conflict. (Default = 1)
Device Priority: <WHOLE NUMBER (1 250)> What is the relative priority of this charging device?
A key value of the OSEnergy protocol is the ability to prioritize charging sources. This value is what is used to decide a given charging sources priority. If the needs of the associated battery (and any additional loads) can be met by higher priority charging sources the regulator will reduce its output to 0A. However, if the battery/load needs cannot be meet the regulator will deliver current to its limits as needed. If there are two or more charging sources with the same priority, battery /load needs will be split between them. (Useful in dual engine installations to balance loads between both engines). (Alternators Default=70) Device priority is also used to decide who should act as the Remote Battery Master, or the overall coordinator in the system to assure all charging devices are working towards the same goal. If AllowRBM? Is enabled, the WS500 Alternator Regulator will assume the RBM role if no other higher device exists. This can be useful in simple installations where no Battery Monitor is installed or as a fall- back for a failed battery monitor.
Allow RBM?: <WHOLE NUMBER (0..2)> Should the WS500 Alternator Regulator attempt to act as the Remote Battery master?
0 = Do not allow the regulator to assume the RBM role. 1 = Allow the regulator to potentially assume the RBM role. (Default) 2 = Allow the regulator to potentially assume the RBM role as a ‘Virtual’ device.
Used in combination with <enable_ALT_CAN?>, a Virtual RBM, is a mode where the “alternative supported CAN” data is re-transmitted as a RV-C compliant RBM. Note that in this mode, though the WS500 will represent the alternative CAN supported BMS as an RV-C compliant device, if another device with higher priority is present the WS500 will following RV-C spec and stop transmitting as an RBM. Also, in the lack of an active alternative CAN device, Virtual RBM mode will defer back to a standard RBM mode.
55
Powered by FlippingBook