ElectricMotorcycleForum.com

  • September 02, 2026, 05:45:34 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Electric Motorcycle Forum is live!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Gary

Pages: [1] 2
1
Parts, Mods And Hacks / Re: PP and CP control on a type 2 charger cable
« on: February 23, 2022, 02:29:30 PM »
Hi David,

We experienced the same issue on the day we read your post, having modified a granny charger!  Up to now, we have built a very small relay into the charging handle.  The relay is connected to the 12Vdc adapter and the normally open contacts connect the resistor between PP and PE.  So, when you unplug the charging handle, you disconnect the resistor.  If you use a manual switch for PP to PE resistor, unplug the handle first.  That way, you won't trip the RCD/GFI.

Have a look at our previous posts for the circuit.

Cheers

Gary

2
Hi Auriga,

Thanks for the information.  I definitely cannot get to the cell voltages from the current menu.  I guess there are undisclosed commands that would access this information, perhaps known only to the 'authorised' dealers.  It has always annoyed me that the automotive, etc, industries keep useful information from their customers.

Regards

Gary

3
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

4
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

5
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

6
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

7
Hi Auriga,

Thanks for the info.  I'll try those products

Cheers

Gary

8
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> .

9
Hi All,

Results of access tests via a Linux laptop

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

LINUX MINT 19.3 (TRICIA)
 
PUTTY - Set up the configuration as follows:

Category: Terminal
- tick 'implicit CR in every LF'
- tick 'implicit LF in every CR'

NOTE:  This ensures that the returned text is correctly formatted.

Category: Connection/Serial
- Serial Line to connect to: /dev/ttyUSB0
- Speed: 115200
- Data: 8
- Stop: 1
- Parity: None
- Flow Control: None
 
Click on 'Category: Session'
Click on 'Serial', a radio button
In 'Saved Sessions' click on 'Default Settings'.
Click on 'Save'

 PUTTY METHOD#1
Open:  a Terminal window
Type:  'sudo chmod -R 777 /dev/ttyUSB0'
Enter: [password]
Type:  'sudo putty'
Select 'Open'
Enter: 'CTRL + m' then 'CTRL + j' to wake up the Zero MBB and display the '>'.
After each entry, ie, 'help', finish with 'CTRL + m' then 'CTRL + j' to make the MBB respond.

 PUTTY METHOD#2 - I forgot to try this one!
By default, PuTTY sends the Telnet New Line code when you press Return, instead of sending Control-M as it does in most other protocols. 
PuTTY emulates xterm which emulates vt100. To have putty send CR/LF when pressing enter, type ESC[20h in putty after connecting to the serial device. This sets VT100 LNM true.
 
 PUTTY METHOD#3
Sending CR+LF is possible in modified PuTTY. Source code is available at https://github.com/gniemirowski/putty-crlf and Windows binary at https://www.grzegorz.net/pliki/putty-crlf.zip When you run this version just go to Terminal -> Keyboard and select "CR LF" for "The Enter key" option.
 
===========================================
'CTRL + m'   CR  13 or 0D
'CTRL + j'  LF  10 or 0A
===========================================
COOLTERM

http://freeware.the-meiers.org/CoolTermLinux32Bit.zip

Open:  a Terminal window
Type:  'sudo chmod -R 777 /dev/ttyUSB0'
Enter: [password]
Run CoolTerm
- Speed: 115200
- Data: 8
- Stop: 1
- Parity: None
- Flow Control: None
Select Connect

===========================================
INSTALL PUTTY CR-LF

1.  Delete all the putty files from any previous install attempts on the laptop, if exist.
2.  sudo apt-get install build-essential libgtk-3-dev
3.  git clone https://github.com/gniemirowski/putty-crlf
cd putty-crlf
./mkauto.sh
./configure --disable-git-commit
make
4.  Run new putty-crlf:
cd putty-crlf
./putty

===========================================
CREATE BASH SCRIPT - serial.sh

path to serial.sh: /home/username/

touch /path/to/serial.sh
chmod a+x /path/to/script.sh
'mcedit /path/to/script.sh' and paste this code:

#!/bin/sh
echo logan | sudo -S chmod -R 777 /dev/ttyUSB0
/path/to/putty-crlf/putty

==========================================
TERMINAL
/home/username/serial.sh

LAUNCHER
/home/username/serial.sh
==========================================

I hope the above is of use to you.  Whatever method I use, I always have to enter ctrl+m and ctrl+j after each command to get the MBB to respond.  I don't know why.  I maybe a Linux thing.  I'm going to try the above using a windows 10 laptop.  I'll let you know how I get on.  Thanks to all of you for your help on this forum.

Cheers

Gary

10
Hi Karlh,

The final 'N' refers to the flow control, so set this to 'None'.

Cheers

Gary

11
Hi Ninja62,

The penny has just dropped.  I only selected 'Implicit LF in every CF'.  I forgot the 'Implicit CR in every LF'.  OK, back out to the bike now.

Cheers

Gary

12
Hi All,

Using PuTTY and Mttty I can connect to the SR/F (at last!).  Herewith the process and the results I achieved:

1.  DO NOT key on the bike
2.  Plugin the USB connector into the laptop
3.  Plugin the OBDII connector into the SR/F
4.  Run up PuTTY
5.  Set 115200,8,n,1,N and hit connect

The cursor will just sit at the left hand edge of the PuTTY window
6.  Now enter Ctrl + m
7.  Now enter Ctrl + j

The SR/F will wake up and reply:
ZERO MBB>

8.  Type in 'help' (without the ' symbols)
9.  Now enter Ctrl + m
10. Now enter Ctrl + j

The SR/F will reply:
ZERO MBB> help

*************************************************************
                                                             *                 Main Menu                           *
                                    *************************************************************

                   help            - Display this Help screen
                                                               login           - Display login level, or login

                                -- MBB Operational Information --
                                                                   version         - Board and firmware revision
                                  dash version    - Dash and Telit firmware revision
      time            - Current time
                                      in              - State of all inputs
                                                                             faults          - Active faults (-v for verbose)
                                               notif           - Active notifications
       stats           - All statistics


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

As you can see, the information is there, it is just difficult to read.  The SR/F does not appear to send CR/LF's

Cleaning up the poor formatting give this:


*************************************************************
*                 Main Menu                           *
*************************************************************

help            - Display this Help screen
login           - Display login level, or login

-- MBB Operational Information --
version         - Board and firmware revision
dash version    - Dash and Telit firmware revision
time            - Current time
in              - State of all inputs
faults          - Active faults (-v for verbose)
notif           - Active notifications
stats           - All statistics

Any ideas on how to fix this?

Cheers

Gary

13
Hi jjfinn,

Brilliant.  Well done on finding that.  I'll try that on the bike tonight.

Cheers

Gary

14
Hi Auriga,

That is a good point.  I'll check that.

Thanks

Gary

15
Hi Hans,

Thank you for clarifying that.  I'll try the IDE to connect to the bike.

Regards

Gary

Pages: [1] 2