Difference between revisions of "BMS CANBus Loopback"

From Unofficial Zero Manual
Jump to: navigation, search
(extract from service manual)
 
(new category)
 
Line 1: Line 1:
 +
<onlyinclude>
 
BMS CANBus loopback is a function of the built-in cable communications support for the [[Power Tank]] or the second [[Power Pack Module]] in a non-longbrick X platform model (labeled ''BMS1'' by the MBB).
 
BMS CANBus loopback is a function of the built-in cable communications support for the [[Power Tank]] or the second [[Power Pack Module]] in a non-longbrick X platform model (labeled ''BMS1'' by the MBB).
  
Line 8: Line 9:
 
: It is unconfirmed what purpose the loopback mechanism serves.
 
: It is unconfirmed what purpose the loopback mechanism serves.
 
: ''Hypothesis:'' This is a hardware debugging mechanism for a loose connector.
 
: ''Hypothesis:'' This is a hardware debugging mechanism for a loose connector.
 +
</onlyinclude>
 +
 +
[[Category:Explanation]]

Latest revision as of 01:48, 12 January 2020

BMS CANBus loopback is a function of the built-in cable communications support for the Power Tank or the second Power Pack Module in a non-longbrick X platform model (labeled BMS1 by the MBB).

The cabling ends in a multi-pin connector and should either:

  1. Terminate with a Loopback Blanking Plug that wires two pins together in a loopback circuit.
  2. Connect to a Power Tank's corresponding communications cable.

If one of the above conditions do not hold, the MBB is configured to issue error code 35.

It is unconfirmed what purpose the loopback mechanism serves.
Hypothesis: This is a hardware debugging mechanism for a loose connector.