Engine ID: <WHOLE NUMBER ( 0 250 )> Used to associate the regulator with the engine it is mounted on. Specifically with regards to RPMs. The regulator monitors for a matching J1939 engine RPM (PGN: 61444) and will use it instead of measured stator RPMs. Also, if NMEA2000 messages are enabled and the regulator is able to measure RPMs – NMEA2000 PGN: Engine parameters rapid (#127488) will be sent with the RPMs indicated as being associated with this Engine ID. Default ID = 0.
BitRate :
<WHOLE NUMBER ( 0 4 )> If supported by hardware, allows CAN communications rate to be
changed from the default 250Kbps. Value Rate 0 Default (250Kbps) 1 100Kbps 2 125Kbps 3 250Kbps 4 500Kbps
DC_ Disconnected _VBat: <FLOATING POINT NUMBER ( 0.0 20.0 )> If a DC-Disconnect command is received via the CAN bus, the charging source will normally be placed into a Disabled mode. However, it may also be optional placed into a CV state using this voltage.
A value of 0.0 (default) causes transition to DISABLED mode or FAULT stat.
Aggregate BMS: <WHOLE NUMBER ( 0 10 )> Some installs utilize more than one BMS in a given battery bank. This may be done to support slightly different locations (ala, port and starboard side of a vessel due to space constraints and/or weight distribution), or more commonly to increase maximum available current by paralleling BMSes. In doing so, not all BMS devices will perform aggregation, instead they will present themselves as different Battery Instance ID’s, despi te being connected to the same physical DC bus. Aggregate BMS allow support of this type of install by monitoring for any BMS or potential RBM with not only the configured Battery Instance number (See above), but also up to 10 Battery Instances. From the base Battery Instance up to Battery Instance + Aggregate BMS. Example, if Battery Instance is set for 2 (either via the DIP switches, or Battery Instance Override above) and Aggregate BMS is set for 5, then ANY battery Instance from 2 to 7 will be c onsider all part of the same ‘battery’ and aggregated by the WS500. Aggregation will sum up the battery current, and capacity; will monitor for any given battery device coming on line or going offline. The request charge state will be the least aggressive (e.g., if ONE online battery asked for Float, then the WS500 will enter Float mode even if the remaining batteries are asking for Bulk). The battery with the most extreme temperature (Hot or cold) will be used to make temperature related decisions, and if a given battery goes off line the WS500 will continue to monitor and respond to the remaining batteries. Once if ALL batteries go offline the WS500 will enter a fault state.
58
Powered by FlippingBook