Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[didierm]

Not wanting to high-jack this thread, but :

Concerning an always-on device such as the Arduino on the OBD, I was wondering :
1. whether the OBD connection is fed by the 12V battery, which is probably balanced by the battery pack ?
2. What would be the maximum allowed current drawn from the OBD-connection ?

[ms_smart]

didierm,

I would make bets, that the OBD port is fed by the 12V battery and decided not to go this route with an always on device.

Since i had some spare time I kicked off my project. Unfortunately I had problems connecting the Arduino with the OBD. I followed the instructions from remmie, but no success. The device I used was a Wemos D1 mini. It is small enough to fit into the OBD2 connector and I powered it through USB. This way it only sucks energy if the bike is active.

I am guessing, that the problem is the serial connection, but debugging an arduino device, that sits in the garage is not fun in winter time.

I therefore changed the setup and used a raspberry pi zero w. This is the smallest raspberry with WLAN. Why the raspberry?
I can use my TTL to USB converter that I know is working (start with a known good configuration)
I can ssh into the raspberry pi and debug from my warm desktop while the device is attached to the bike

Configuring the raspberry pi with WLAN in a headless configuration was pretty easy. I have created a config file that sits in the boot filesystem with all my passwords and parameters (this can be mounted in Windows) and a shell script, that I included into rc.local to fire it up automatically.

This is the work flow:
The bike turns on either because it charges or by the ignition key. This will initiate the boot process of the raspberry.
The script waits for wlan connection. If there is no wlan next 30 seconds it will shutdown with no action
The serial terminal /dev/ttyUSB0 will be set up (stty)
commands will be send to the tty and responds stored into a local log file
The logfile will be send to FTP server
certain parameters will be extracted from the logfile and inserted into a database table (mariadb)
Progress, Success or failure will be pushed to the smartphone using pushbullet

Although the raspberry pi is bigger in size and does not fit into the connector, it works for me since I have the charge tank and therefore the storage area in the tank is useless anyway (A smartphone still fits). Of course I currently can only test it while parking, but think it should also work while driving (the device should shutdown either because the work is done or because there is no wlan)

If you are interested I can share  the scripts.

[Hans2183]

All I see is yet another 12kW charge config... I wish my dealer responded to my requests to get one installed

Looks like a neat solution, and having the rpi power you can do so much more with it now. Haven't looked at what gets logged while riding myself since I read it with a macbook . So would love to see that. Maybe something like power consumption or even performance numbers can be extracted to add to the plotted GPS points.

[didierm]

ms_smart,

Having an unused RPi Zero lying around, I'd love to see the scripts (sharing is caring ).

If (if) the 12V battery is balanced by the main battery (which I guess it is, otherwise the power consumption by the cellular connection probably wouldn't last the battery during extended winter storage, would it ?), is there any reason not to take power from the always-on OBD pins ?

[ms_smart]

See attached. I am sure you can do this more elegant, but it works for me. Obviously you can configure "wait for wlan" with raspi-config, but this would cause a hard shutdown if you are riding with no access to wlan. I therefore prefer to test it in my local script and do what I please if there is no connection (in my case: shutdown).

This is in my opinion the main drawback compared to the arduino device. You will boot from the SD card and actually need the filesystem. This may get corrupted if you kill the power without proper shutdown. I therefore still would prefer the arduino device, that actually could also log data in the flash space. Arduino boots much faster (4 seconds until wlan is connected compared to 20 seconds) and should be more reliable. May be I give it an other try once it gets warmer.

To avoid file system problems, my current script is always shutting down. But this makes it hard to run while driving as suggested by Hans. You may need to implement something to allow a proper shutdown before the USB power drops.

BTW: I got confirmation from a Zero dealer, that pack_capacity_ah is indeed a proxy to calculate SOH. Zero is also using this parameter to validate warranty claims. My number is now down to 108 (from 109)

[Hans2183]

Some more numbers, this time from a demo model SRF seabright blue standard edition with ODO 645 km

Code: [Select]

ZERO MBB> bms interface
BMS 2 interface data:

 - status 0x80000076
 - pack_current_ma 369
 - time since status_rpdo_received 73

 - max_charge_voltage 117.6 V
 - target_charge_voltage 116.3 V
 - pack_soc_pct 92
 - discharge_allowed 59
 - max_charge_current 56
 - max_discharge_current 760
 - time since power_rpdo_received 83

 - pack_capacity_ah 109
 - min_pack_temp_c 8
 - max_pack_temp_c 9
 - lowest_cell_voltage_mv 4043
 - time since pack_rpdo_received 92

 - pack_open_circuit_voltage_mv 113343
 - pack_voltage_mv 113343
 - time since voltage_rpdo_received 95
 - Contactor recently closed 0

 - bms_compatibility_field 0x01


Code: [Select]

ZERO MBB> stats



*************************************************************
*                       MBB Settings                        *
*************************************************************
  To change settings, type:
    "set <setting name> <value1> <value2> ..."


 Setting Name                             Setting Desc                             Value         Units
+----------------------------------------+----------------------------------------+-------------+-----
 firmware_rev                                                                                 13
 num_resets                                                                                10816
 trip1_motor_revolutions_at_last_reset                                                   1525558
 total_on_time_sec                                                                       2091508 sec
 total_run_time_sec                                                                        54864 sec
 total_charger_time_sec                                                                   124890 sec
 longest_runtime_sec                                                                           0 sec
 nv_write_cycles                                                                           10815
 max_pack_temp_c                                                                              38 C
 min_pack_temp_c                                                                               0 C
 max_motor_temp_c                                                                             14 C
 max_controller_temp_c                                                                         7 C
 max_motor_speed_rpm                                                                           0
 watt_seconds_per_mile                                                                    396000
 watt_seconds_per_km                                                                      169565
 trip1_watthours_at_last_reset                                                             64424 Wh
 highly_filtered_batt_current_millamps                                                     41162
 highly_filtered_speed_kph_x100                                                             5133
 trip2_motor_revolutions_at_last_reset                                                         0
 trip2_watthours_at_last_reset                                                                 8 Wh
 event_log_read_pointer                                                             0x00001004
 event_log_write_pointer                                                            0x00BFB6BF
 event_log_entry_counter                                                                      65
 num_key_cycles                                                                              269
 charger_attached_before_last_hib                                                              0
 total_watt_milliseconds                                                            231929966528
 obd_fault_code_0                                                                             18
 obd_fault_code_1                                                                             20
 obd_fault_code_2                                                                            255
 obd_fault_code_3                                                                            255
 obd_fault_code_4                                                                            255
 obd_fault_code_5                                                                            255
 obd_fault_code_6                                                                            255
 obd_fault_code_7                                                                            255
 obd_fault_code_8                                                                            255
 obd_fault_code_9                                                                            255
 obd_fault_code_freeze_frame                                                                  20
 obd_key_cycle_num_last_dtc                                                                   45
 obd_odometer_m_last_clear                                                                 21080
 obd_odometer_m_first_mil                                                                      0
 obd_freeze_frame_field_0                                                                      0
 obd_freeze_frame_field_1                                                                      0
 obd_freeze_frame_field_2                                                                 465152
 obd_freeze_frame_field_3                                                                      0
 obd_freeze_frame_field_4                                                                      0
 ambient_ave_temp_c                                                                            5
 logging_fault_counter                                                                         0
 last_logging_fault_type                                                                       0
 ccm_ota_update_requested                                                                      0
 ccm_ota_update_ecu_id                                                                         0
 ccm_ota_update_fw_bank                                                                        0
 ccm_ota_update_fw_rev                                                                         0
 ccm_ota_update_fw_size                                                                        0
 curr_time_source                                                                              2
 utc_offset_source                                                                             3
 ccm_ota_update_failed_attempt_count                                                           0
 ccm_ota_update_success                                                                        0
 bms_fw_rev_low                                                                              255
 bms_fw_rev_low_bank                                                                           0
 bms_fw_rev_high                                                                               0
 bms_fw_rev_high_bank                                                                          0
 heated_grips_mode                                                                             0
 offset_from_dash_time_sec                                                                     0 sec
 wait_for_next_active_to_charge                                                                0
 event_log_last_sec                                                                   1613418516
 ccm_fw_version_encoded                                                                        0


[Gary]

Hi All,

Last week, I charged the bike to 100% and she went into cell balancing mode.  Unfortunately, it took over 40 minutes to do this so I checked the data from the bms.  I have listed the results below, but two values are particularly concerning.  They are:

. - pack_capacity_ah 76
. - lowest_cell_voltage_mv 1977

Does this look like I have a dead cell?

Cheers

Gary

=========================================

.ZERO MBB> .bms

.*************************************************************
.*                           BMS Data                        *
.*************************************************************
.Additional options:
. - bms interface        Shows Interface data
. - bms commands         Shows commands sent to bms
. - bms eligibility/elig Shows eligibility information about the modules
. - bms module           Shows module data
. - bms status           Shows bms status data
. - bms info             Shows bms information

.   use -v for verbose printout including unregistered modules

. - bms login <bms> <level>  Log in to <bms> at <level>
.
Module Management:
. - LTSM state: DIS
. - Selected to:
.    - precharge: 255
.    - close contactor: 2
.    - isolation: 2
.
BMS snapshot:
. - BMS 2
.     Module 2 info:
.     - time since last PDO received 80
.     - is registered     1
.     - eligible for HV   1
.     - pack voltage      115911
.     - pack voltage oc   115127
.     - soc               100
.     - precharge command 0
.     - precharge state   1
.     - contactor command 1
.     - contactor state   1
.     - lock command      1
.     - pack full         0
.     - storage mode      Inactive
.     - num_bricks        0
.     - batt serial       20HM0354

.ZERO MBB> .bms info
BMS 2 info:
. - Batt serial:         20HM0354
. - Board part num:      40-08201-01
. - Board serial:        SJ4919ZER0227
. - Board rev:           1
. - Firmware part num:   75-08156
. - Firmware build num:  375
. - Firmware build hash: 00060d3ee9
. - Firmware id:         0
. - Firmware rev:        19
. - Firmware bank:       1
. - Firmware timestamp:  Tue, 01/05/2021 22:23:00

.ZERO MBB> .bms interface
BMS 2 interface data:

. - status 0x80000036
 - status2 0x0000
- pack_current_ma -2975
 - time since status_rpdo_received 93

. - max_charge_voltage 117.6 V
. - target_charge_voltage 116.3 V
. - pack_soc_pct 100
. - discharge_allowed 82
. - max_charge_current 3
. - max_discharge_current 1060
. - time since power_rpdo_received 103

. - pack_capacity_ah 76
. - min_pack_temp_c 14
. - max_pack_temp_c 17
. - lowest_cell_voltage_mv 1977
. - time since pack_rpdo_received 2

. - pack_open_circuit_voltage_mv 116083
. - pack_voltage_mv 116475
. - time since voltage_rpdo_received 2
. - Contactor recently closed 0

. - bms_compatibility_field 0x03
.
.ZERO MBB> .bms commands
BMS 2 commands state:
.
 - close_contactor 4
 - precharge_enable 3

. - isolation_pull_down 0
 - isolation_pull_up 0
 - isolation_inhibit no

. - control 0x003b
 - mbb_compatibility_field 0x03

.*************************************************************
.*                           BMS Data                        *
.*************************************************************
.Additional options:
. - bms interface        Shows Interface data
. - bms commands         Shows commands sent to bms
. - bms eligibility/elig Shows eligibility information about the modules
. - bms module           Shows module data
. - bms status           Shows bms status data
. - bms info             Shows bms information

.   use -v for verbose printout including unregistered modules

. - bms login <bms> <level>  Log in to <bms> at <level>
.
Module Management:
. - LTSM state: DIS
. - Selected to:
.    - precharge: 255
.    - close contactor: 2
.    - isolation: 2
.

.ZERO MBB> .charging

.*************************************************************
.*...Charging                            *
.*************************************************************
.
.          Measurement,      Value,     Units,    Valid,   In Test
. EVSE_Connector_State,          1,   Disconn,      Yes,         0
.         EVSE_Command,          0,        No,      Yes,         0
.         Inlet_Region,          2,        EU,      Yes,         0
.          Latch_State,          4,          ,      Yes,         0
.        Pilot_Current,          0,         A,       No,         0
.             Charging,          0,        No,      Yes,         0
.   Chargers_Connected,          0,          ,      Yes,         0
.   Max_Charge_Current,          0,         A,      Yes,         0
.   Charge_Current_Sum,        0.0,         A,      Yes,         0
.   Max_Charge_Voltage,        0.0,         V,      Yes,         0
.      Target_Charge_V,        0.0,         V,      Yes,         0
.      Storage_Voltage,      106.0,         V,      Yes,         0
.      Target_Override,          0,        No,      Yes,         0
.    SOC_Charge_Target,         86,    Pct(%),      Yes,         0
. Charge_Target_Enable,          1,       Yes,      Yes,         0
.   Charge_Target_Init,          0,        No,      Yes,         0
.      Charge Complete,          0,        No,      Yes,         0
.   Scheduled_Charging,          1,       Yes,      Yes,         0
.    Schedule_Override,          1,       Yes,      Yes,         0
.   Sched_Charging_Now,          1,       Yes,      Yes,         0
.   Plugin_Window_Init,          0,        No,      Yes,         0
.   Charge_Window_Init,          0,        No,      Yes,         0
.   Sched_Charge_Delay,          0,       min,      Yes,         0
.
******************* Charging Schedule ***********************
. Day, Start_Time, Offset, Plugin_Start, Plugin_Offset
. Sun,       4:00,   1:00,        16:00,         12:00
. Mon,       4:00,   1:00,        16:00,         12:00
. Tue,       4:00,   1:00,        16:00,         12:00
. Wed,       4:00,   1:00,        16:00,         12:00
. Thu,       4:00,   1:00,        16:00,         12:00
. Fri,       4:00,   1:00,        16:00,         12:00
. Sat,       4:00,   1:00,        16:00,         12:00
.
******************* Chargers Connected **********************
.Charger,  En,  DC V,  DC A,  AC V,  AC A, AC HZ, Limit A,  Ver,   Serial,    ID, Status
.
.ZERO MBB> .

[Auriga]

Hi All,

Last week, I charged the bike to 100% and she went into cell balancing mode.  Unfortunately, it took over 40 minutes to do this so I checked the data from the bms.  I have listed the results below, but two values are particularly concerning.  They are:

. - pack_capacity_ah 76
. - lowest_cell_voltage_mv 1977

Does this look like I have a dead cell?

Cheers

Gary

=========================================

.ZERO MBB> .bms

.*************************************************************
.*                           BMS Data                        *
.*************************************************************
.Additional options:
. - bms interface        Shows Interface data
. - bms commands         Shows commands sent to bms
. - bms eligibility/elig Shows eligibility information about the modules
. - bms module           Shows module data
. - bms status           Shows bms status data
. - bms info             Shows bms information

.   use -v for verbose printout including unregistered modules

. - bms login <bms> <level>  Log in to <bms> at <level>
.
Module Management:
. - LTSM state: DIS
. - Selected to:
.    - precharge: 255
.    - close contactor: 2
.    - isolation: 2
.
BMS snapshot:
. - BMS 2
.     Module 2 info:
.     - time since last PDO received 80
.     - is registered     1
.     - eligible for HV   1
.     - pack voltage      115911
.     - pack voltage oc   115127
.     - soc               100
.     - precharge command 0
.     - precharge state   1
.     - contactor command 1
.     - contactor state   1
.     - lock command      1
.     - pack full         0
.     - storage mode      Inactive
.     - num_bricks        0
.     - batt serial       20HM0354

.ZERO MBB> .bms info
BMS 2 info:
. - Batt serial:         20HM0354
. - Board part num:      40-08201-01
. - Board serial:        SJ4919ZER0227
. - Board rev:           1
. - Firmware part num:   75-08156
. - Firmware build num:  375
. - Firmware build hash: 00060d3ee9
. - Firmware id:         0
. - Firmware rev:        19
. - Firmware bank:       1
. - Firmware timestamp:  Tue, 01/05/2021 22:23:00

.ZERO MBB> .bms interface
BMS 2 interface data:

. - status 0x80000036
 - status2 0x0000
- pack_current_ma -2975
 - time since status_rpdo_received 93

. - max_charge_voltage 117.6 V
. - target_charge_voltage 116.3 V
. - pack_soc_pct 100
. - discharge_allowed 82
. - max_charge_current 3
. - max_discharge_current 1060
. - time since power_rpdo_received 103

. - pack_capacity_ah 76
. - min_pack_temp_c 14
. - max_pack_temp_c 17
. - lowest_cell_voltage_mv 1977
. - time since pack_rpdo_received 2

. - pack_open_circuit_voltage_mv 116083
. - pack_voltage_mv 116475
. - time since voltage_rpdo_received 2
. - Contactor recently closed 0

. - bms_compatibility_field 0x03
.
.ZERO MBB> .bms commands
BMS 2 commands state:
.
 - close_contactor 4
 - precharge_enable 3

. - isolation_pull_down 0
 - isolation_pull_up 0
 - isolation_inhibit no

. - control 0x003b
 - mbb_compatibility_field 0x03

.*************************************************************
.*                           BMS Data                        *
.*************************************************************
.Additional options:
. - bms interface        Shows Interface data
. - bms commands         Shows commands sent to bms
. - bms eligibility/elig Shows eligibility information about the modules
. - bms module           Shows module data
. - bms status           Shows bms status data
. - bms info             Shows bms information

.   use -v for verbose printout including unregistered modules

. - bms login <bms> <level>  Log in to <bms> at <level>
.
Module Management:
. - LTSM state: DIS
. - Selected to:
.    - precharge: 255
.    - close contactor: 2
.    - isolation: 2
.

.ZERO MBB> .charging

.*************************************************************
.*...Charging                            *
.*************************************************************
.
.          Measurement,      Value,     Units,    Valid,   In Test
. EVSE_Connector_State,          1,   Disconn,      Yes,         0
.         EVSE_Command,          0,        No,      Yes,         0
.         Inlet_Region,          2,        EU,      Yes,         0
.          Latch_State,          4,          ,      Yes,         0
.        Pilot_Current,          0,         A,       No,         0
.             Charging,          0,        No,      Yes,         0
.   Chargers_Connected,          0,          ,      Yes,         0
.   Max_Charge_Current,          0,         A,      Yes,         0
.   Charge_Current_Sum,        0.0,         A,      Yes,         0
.   Max_Charge_Voltage,        0.0,         V,      Yes,         0
.      Target_Charge_V,        0.0,         V,      Yes,         0
.      Storage_Voltage,      106.0,         V,      Yes,         0
.      Target_Override,          0,        No,      Yes,         0
.    SOC_Charge_Target,         86,    Pct(%),      Yes,         0
. Charge_Target_Enable,          1,       Yes,      Yes,         0
.   Charge_Target_Init,          0,        No,      Yes,         0
.      Charge Complete,          0,        No,      Yes,         0
.   Scheduled_Charging,          1,       Yes,      Yes,         0
.    Schedule_Override,          1,       Yes,      Yes,         0
.   Sched_Charging_Now,          1,       Yes,      Yes,         0
.   Plugin_Window_Init,          0,        No,      Yes,         0
.   Charge_Window_Init,          0,        No,      Yes,         0
.   Sched_Charge_Delay,          0,       min,      Yes,         0
.
******************* Charging Schedule ***********************
. Day, Start_Time, Offset, Plugin_Start, Plugin_Offset
. Sun,       4:00,   1:00,        16:00,         12:00
. Mon,       4:00,   1:00,        16:00,         12:00
. Tue,       4:00,   1:00,        16:00,         12:00
. Wed,       4:00,   1:00,        16:00,         12:00
. Thu,       4:00,   1:00,        16:00,         12:00
. Fri,       4:00,   1:00,        16:00,         12:00
. Sat,       4:00,   1:00,        16:00,         12:00
.
******************* Chargers Connected **********************
.Charger,  En,  DC V,  DC A,  AC V,  AC A, AC HZ, Limit A,  Ver,   Serial,    ID, Status
.
.ZERO MBB> .

Really difficult to say. Zero doesn't publish any details about their bike firmware. We have no way of knowing, for example, if lowest_cell_voltage_mv is the lowest cell voltage since last key on, or over the entire life of the bike. There are also lots of ways to estimate capacity, some of which might not always be accurate or maybe the feature is incomplete or buggy.

I usually suggest to go by your gut. Are you experiencing range issues or bike errors? There is a fault for a battery cell that gets too low as well. Typically if one cell is low you can't charge to 100%, as its based partially on lowest cell.

You can always use the app to pull logs and send them to Zero in a message if you want confirmation

[Hans2183]

What Auriga says. Solid advice. Sending logs doesn't hurt but if you don't have issues I wouldn't bother too much.

[Gary]

Hi Hans and Auriga,

The last time I tried to download logs to the app, it took 40 minutes!  It is a pity other apps are not available.  Out of interest, how long do you expect a battery balance operation to take?

Cheers

Gary

[Richard230]

Hi Hans and Auriga,

The last time I tried to download logs to the app, it took 40 minutes!  It is a pity other apps are not available.  Out of interest, how long do you expect a battery balance operation to take?

Cheers

Gary

On my 2018 S with PT it seems to take about 15 minutes.

[Gary]

Hi All,

After experimenting with Serial Port Comms packages, Linux and Windows, I have found that the easiest software package to use is CoolTerm running on a Windows 7 to 10 laptop.  The return key does what is required and the results are correctly formatted.  The results remain on screen after disconnecting the serial cable.

I have been looking at the BMS data by going through the help list of commands.  One thing I can't find is the list of bank voltages that Hans displayed in a previous post.  How do I get to this menu choice?

Does anyone know how to get to any other menus below the top level ones listed in 'help'?

Cheers

Gary

[Hans2183]

Which one? I think I've used bms interface mostly.

[Gary]

Hi Hans,

I can't remember the exact post

It referred to BMS #0 and Bank Voltages #1 to #28 and listed individual voltages like 4147mV.  Should you take some readings with the key off and some with the key on?

Cheers

Gary

[Gary]

Hi Hans,

Herewith the printout of the Bank Voltages:

Code: [Select]


ZERO MBB> bms
****************************************
*               BMS Data               *
****************************************

*************  BMS #0  ***************
  - BMS Board Rev             :  01
  - BMS Firmware Rev          :  39
  - BMS Serial Number         : 2014_bms_03b9fb_05452
  - Battery Serial Number     : 14qd0389
  - CAN Rx in last second     :  160

  - Pack SOC                  :  100%
  - Fuel Gauge                :  100%
  - Age of SOC Data           :  12 ms

  - Model Year                : 2014
  - Pack Capacity             :  92 AH
  - Pack Capacity Remaining   :  92 AH
  - Total Energy Used         : 464 KWH
  - Number Of Bricks          :   4

  - Pack Discharge Current    :   0 A
  - Pack Sum Voltage          :  116.088 V
  - Sag-Adj Pack Sum Voltage  :  116.118 V
  - Bank Voltages             :     1    2    3    4    5    6    7    8    9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28
                              :  4144 4145 4145 4146 4145 4145 4147 4145 4146 4146 4146 4146 4145 4146 4146 4145 4146 4146 4145 4146 4147 4146 4147 4146 4147 4147 4146 4147
  - Lowest Cell Voltage       :  4144 mV ( Cell 1 )
  - Highest Cell Voltage      :  4147 mV ( Cell 7 )
  - Pack Balance              :  3 mV
  - Lowest Cell mV            :  4144 mV
  - Age of Bank Voltage Data  :  64 ms

  - Isolation Resistance      :  15633 KOhms (0x3D11)
  - Least Isolated Cell       :  12

                              :      0     1     2     3     4     5     6     7
  - Pack Temps                :    14C   14C   14C   15C   14C   14C   14C   14C
  - Lowest Present Pack Temp  :  14 C
  - Max Pack Temp This Ride   :  15 C
  - Min Pack Temp This Ride   :  14 C
  - Age of BMS Temp Data      :  172 ms

  - Min Discharge Temp        :  -30 C
  - Max Charge Temp           :  50 C
  - Min Charge Temp           :  0 C
  - Max Charge C-Rate         :  1.0
  - Min Discharge C-Rate      :  7.5
  - Discharge Scale Value     :   255/255

  - Num Charge Cycles         :  163

  - BMS Total Bike Run Time   :  00:04:34
  - BMS Clock                 :  03/25/2017 10:34:21 ( 1490463261, 0x58D6AA1D )
  - Age of BMS Time Data      :  287 ms

  - Age of BMS Status Data    :  301 ms
  - Discrete Throttle En      :  Enabled

  CAN Status
  - Charger Attached          :   No
  - Batt Unbalanced           :   No
  - Batt Low                  :   No
  - Batt Full                 :  Yes
  - Batt Critically Low       :   No
  - Batt Temp High            :   No
  - Batt Temp Critically High :   No
  - Batt Temp Low             :   No
  - Contactor Closed          :  Yes
  - Isolation Fault           :   No
  - BMS Internal Fault        :   No
  - Cell Too High For Charge  :   No
  - Cell Too Low For Charge   :   No
  - Charge Halt               :   No
  - BMS Internal Disable      :   No

  CAN Commands
  - Close Contactor           :   No
  - Connect Module            :  Yes
  - Key On                    :  Yes
  - Charger Connected         :   No
  - Time Since Cmds Last Sent :  543 ms

1.  Which menu choice is this from?  I have been through all the main and daughter menus but can't find this information.

2.  How many BMS levels are there and how do you log into them?  Whenever I try, I get bounced back to BMS 2

Regards

Gary