BUG? in v3.2.0-1 in vehicle_mitsubishi - flood of BMS-error msg
There is a bug in MIEV code, that bombs the web GUI and phone APP with BMS errors. I suspect that this is because the Peugeot and Citroen branded MIEVs have a 80 cell battery pack vs MIEVs 88cells. Sample of a message:
Voltage: SD=1mV OK Temperature: SD=1.4C !6:+3.1C !16:+3.1C !18:+3.1C
The missing cells could also be used to set the voltage gauge. There are two LEV50-4 missing in the 80 cell pack, number 06 and 12. If a flagg is set while looping the CAN massages, then the flag can be used inside OvmsVehicleMitsubishi::GetDashboardConfig to set correct voltage. The float charge voltage of the 80 cell pack is 328.4 volt
The code tested on Peugeot iOn with 88 cell. Can you create a log for me from can messages about 5 sec? I can see whats the difference in 80 cell can messages. I use the following to create log from can messages. Connect to ovms via ssh: ssh -c aes128-cbc ovms@192.168.4.1 - re start - re mode serve - re serve format crtd Then, on workstation: - nc 192.168.4.1 3000 | tee log.crtd And the send me the log.crtd file. Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 14:08):
There is a bug in MIEV code, that bombs the web GUI and phone APP with BMS errors.
I suspect that this is because the Peugeot and Citroen branded MIEVs have a 80 cell battery pack vs MIEVs 88cells.
Sample of a message:
Voltage: SD=1mV OK Temperature: SD=1.4C !6:+3.1C !16:+3.1C !18:+3.1C
The missing cells could also be used to set the voltage gauge. There are two LEV50-4 missing in the 80 cell pack, number 06 and 12. If a flagg is set while looping the CAN massages, then the flag can be used inside OvmsVehicleMitsubishi::GetDashboardConfig to set correct voltage. The float charge voltage of the 80 cell pack is 328.4 volt
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 19.01.2019 14:22, Tamás Kovács wrote:
Then, on workstation:
- nc 192.168.4.1 3000 | tee log.crtd
And the send me the log.crtd file.
Is the OVMS firewalled if it's connected as a WIFI client?
nmap -P0 -p 3000 192.168.1.84
Starting Nmap 7.60 ( https://nmap.org ) at 2019-01-19 14:31 CET Nmap scan report for 192.168.1.84 Host is up.
PORT STATE SERVICE 3000/tcp filtered ppp
Nmap done: 1 IP address (1 host up) scanned in 2.12 seconds
Should not be. Are you sure the ‘re’ is running? Regards, Mark.
On 19 Jan 2019, at 9:32 PM, Michael Eric Menk <mikeemenk@gmail.com> wrote:
On 19.01.2019 14:22, Tamás Kovács wrote:
Then, on workstation:
- nc 192.168.4.1 3000 | tee log.crtd
And the send me the log.crtd file.
Is the OVMS firewalled if it's connected as a WIFI client?
nmap -P0 -p 3000 192.168.1.84
Starting Nmap 7.60 ( https://nmap.org <https://nmap.org/> ) at 2019-01-19 14:31 CET Nmap scan report for 192.168.1.84 Host is up.
PORT STATE SERVICE 3000/tcp filtered ppp
Nmap done: 1 IP address (1 host up) scanned in 2.12 seconds
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
On 19.01.2019 14:34, Mark Webb-Johnson wrote:
Should not be.
Are you sure the ‘re’ is running?
My bad, typo on IP-addr.... CAN bus http://vedlegg.uib.no/?id=79759769c40835dbbbc1cc70bbdbe6f7 Video of the error meg flooding inn: https://tjinfo.uib.no/Vedlegg?id=c24410eff775ca573e8fc9739ad3de32
First disable bms alerts in web interface/trio/bms cell monitor / alert config Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 14:49):
On 19.01.2019 14:34, Mark Webb-Johnson wrote:
Should not be.
Are you sure the ‘re’ is running?
My bad, typo on IP-addr....
CAN bus http://vedlegg.uib.no/?id=79759769c40835dbbbc1cc70bbdbe6f7
Video of the error meg flooding inn: https://tjinfo.uib.no/Vedlegg?id=c24410eff775ca573e8fc9739ad3de32
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
Please create about 10 sec log Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 14:55):
First disable bms alerts in web interface/trio/bms cell monitor / alert config
Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 14:49):
On 19.01.2019 14:34, Mark Webb-Johnson wrote:
Should not be.
Are you sure the ‘re’ is running?
My bad, typo on IP-addr....
CAN bus http://vedlegg.uib.no/?id=79759769c40835dbbbc1cc70bbdbe6f7
Video of the error meg flooding inn: https://tjinfo.uib.no/Vedlegg?id=c24410eff775ca573e8fc9739ad3de32
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
-- Üdvözlettel: Kovács Tamás
The car in ready Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 15:07):
Please create about 10 sec log
Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 14:55):
First disable bms alerts in web interface/trio/bms cell monitor / alert config
Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 14:49):
On 19.01.2019 14:34, Mark Webb-Johnson wrote:
Should not be.
Are you sure the ‘re’ is running?
My bad, typo on IP-addr....
CAN bus http://vedlegg.uib.no/?id=79759769c40835dbbbc1cc70bbdbe6f7
Video of the error meg flooding inn: https://tjinfo.uib.no/Vedlegg?id=c24410eff775ca573e8fc9739ad3de32
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
-- Üdvözlettel: Kovács Tamás
-- Üdvözlettel: Kovács Tamás
On 19.01.2019 15:07, Tamás Kovács wrote:
The car in ready
The first CAN log was made with the car charging. I have tried to make one with the car on, but the OVMS deadlocks before I'm able to complete the task. The SSH terminal do not react on <enter> , nor does the web page response. After it dead locks I'm not able to log in, but the IP-ports responds on port-scan. I'll be trying some more to see if I'm able to to it faster... -- Michael Menk
In the first log was only get 64 cell voltage and 42 cell temperature values in the log, 6E1 CAN frame is empty (on 88 cell car has 24 volt and 24 temp values), any other 6E2, 6E3, 6E4 same as 88cell cars. You can create log file when charging as same ready. Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 15:35):
On 19.01.2019 15:07, Tamás Kovács wrote:
The car in ready
The first CAN log was made with the car charging.
I have tried to make one with the car on, but the OVMS deadlocks before I'm able to complete the task.
The SSH terminal do not react on <enter> , nor does the web page response. After it dead locks I'm not able to log in, but the IP-ports responds on port-scan.
I'll be trying some more to see if I'm able to to it faster...
--
Michael Menk
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 19.01.2019 15:40, Tamás Kovács wrote:
In the first log was only get 64 cell voltage and 42 cell temperature values in the log, 6E1 CAN frame is empty (on 88 cell car has 24 volt and 24 temp values), any other 6E2, 6E3, 6E4 same as 88cell cars. You can create log file when charging as same ready. Here a new file:
CAN-Czero-charing-level1-80cell.30sec.crtd: http://vedlegg.uib.no/?id=26f63a9734b73bde8cd412d6c3643850 -- Michael Menk
I don't understand, i see all the 88 volt and 66 temp sensor data in CAN frame, your car is sure to be 80 cell? Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 16:17):
On 19.01.2019 15:40, Tamás Kovács wrote:
In the first log was only get 64 cell voltage and 42 cell temperature values in the log, 6E1 CAN frame is empty (on 88 cell car has 24 volt and 24 temp values), any other 6E2, 6E3, 6E4 same as 88cell cars. You can create log file when charging as same ready. Here a new file:
CAN-Czero-charing-level1-80cell.30sec.crtd: http://vedlegg.uib.no/?id=26f63a9734b73bde8cd412d6c3643850
--
Michael Menk
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 19.01.2019 16:30, Tamás Kovács wrote:
I don't understand, i see all the 88 volt and 66 temp sensor data in CAN frame, your car is sure to be 80 cell?
Yes, it's a 80 cell car.. I have 363 hours 7 minutes 38 seconds of logs Max volt:
select max(b_volt) from SECLOG ; 329.7
Cell volt of one missing cell:
select avg(CMU_12_CELL_D) from CELL_VOLTS; 0.000539636363636364 sqlite> select avg(CMU_01_CELL_D) from CELL_VOLTS; 3.89978060606068
The car shuts down if i cell gets down to -30
select count(*) from cell_temps where CMU_12_UNIT_3 > -30 ; 115 select count(*) from cell_temps where CMU_12_UNIT_3 < -30 ; 20510
the 115 readings is odd, seams to be some ghost readings...
select distinct(CMU_12_UNIT_3) from cell_temps ; -50 0 20
Maybe a glitch when starting the car, an initial value.. Since it's only 0 and 20°C, that's likely considering we also see the same with the QC signal of RR=255. Solution? It's likely that the the messages are sent on the bus, but it's not used by the components. We do know, from documentation from Mitsubishi that if the battery (one cell) is below -30°C, the car goes in to hibernation, and wakes up after 6 hours to check if the battery have warmed up. In other words, if one of the sensors is below -30°C of the optional battery cells, then we know that the battery has 80 cells. -- Michael Menk
Now i see your bms error message get from temperature, you can change the threshold of the error messages same place as disble this messages. On web interface you can see cell volt and temps in bar graps, you see 88volts and temps? Can you send a photo from this page. What program you create a log for long time? Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2019. jan. 19., Szo, 17:04):
On 19.01.2019 16:30, Tamás Kovács wrote:
I don't understand, i see all the 88 volt and 66 temp sensor data in CAN frame, your car is sure to be 80 cell?
Yes, it's a 80 cell car..
I have 363 hours 7 minutes 38 seconds of logs
Max volt:
select max(b_volt) from SECLOG ; 329.7
Cell volt of one missing cell:
select avg(CMU_12_CELL_D) from CELL_VOLTS; 0.000539636363636364 sqlite> select avg(CMU_01_CELL_D) from CELL_VOLTS; 3.89978060606068
The car shuts down if i cell gets down to -30
select count(*) from cell_temps where CMU_12_UNIT_3 > -30 ; 115 select count(*) from cell_temps where CMU_12_UNIT_3 < -30 ; 20510
the 115 readings is odd, seams to be some ghost readings...
select distinct(CMU_12_UNIT_3) from cell_temps ; -50 0 20
Maybe a glitch when starting the car, an initial value.. Since it's only 0 and 20°C, that's likely considering we also see the same with the QC signal of RR=255.
Solution?
It's likely that the the messages are sent on the bus, but it's not used by the components. We do know, from documentation from Mitsubishi that if the battery (one cell) is below -30°C, the car goes in to hibernation, and wakes up after 6 hours to check if the battery have warmed up.
In other words, if one of the sensors is below -30°C of the optional battery cells, then we know that the battery has 80 cells.
-- Michael Menk
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 19.01.2019 17:38, Tamás Kovács wrote:
Now i see your bms error message get from temperature, you can change the threshold of the error messages same place as disble this messages.
You can not push out an image with a temperature warning at 2°C when 15 - 25°C temperature difference is normal temperature difference when using the car. If you look at the graph linked underneath, you will see the min and max temp while charging on at 125A charger. The charge is from a 1400km trip in -18 to -10°C outside. You can see the cells closest to the air intake becoming colder while charging. Even with the active cooling, the BMS have reduced the current from the charger to save the warmest battery (protection starts at 31°C). Graph: 125A amp charge in winter: http://vedlegg.uib.no/?id=80da14370e694e5e23a9e91e8aa4df29 (link valid for 3 years) You will also get the same temperature difference in the summer, but then the AC compressor will cool the air down. With the high temperature difference, the battery will charge differently, resulting in a imbalanced pack. Since the BMS uses top-charge-balancing, they will not get fully re-balanced before you connect onboard charger. I recommend that you disable the BMS warning by default before pushing the image.
On web interface you can see cell volt and temps in bar graps, you see 88volts and temps? Can you send a photo from this page.
On the "cars website" I see 88 volts, but there are only 80 cells. Both C-Zero and Ion have for a long time used 80 cells. I suspect that the numbers from the non-existing cells are from other cells. __Dashboard config___ A solution for the dashboard voltage gauge is to use the battery voltage to set the correct min-max voltage. There is no overlap of the voltage of the 88cell pack and the 80 cell pack. 80 cells at 4.10V = 328.0V (target voltage while charging (CV)) 80 cells at 4.12V = 329.6V (max volt) 88 cells at 3.00V = 264.0V In order to get close to the max of the 80 cell the 88 cell pack have to have an average cell-volt of 2.61V, while the BMS reports in my logs reports 8.5%SOC at a average cell voltage of 3.09. if (StandardMetrics.ms_v_bat_voltage->AsFloat() > 340 ) { // set gauge for 88 cell back } else { //set gauge for 80 cell pack }
What program you create a log for long time?
CanIon, the OVMSv2 I got was DOA, I continued using CanIon in a "client server mode" while waiting for OVMSv3. The graph above was created by: select datetime ( s.timestamp/1000 , 'unixepoch' ) as logtime , s.odo , s.b_soc , s.b_amp*s.b_volt/1000 as kW ,b.mintemp, b.maxtemp , b.maxtemp - b.mintemp as tempdiff , s.ac_w from seclog s left join view_diff_temp b on s.timestamp/1000 = b.timestamp/1000 where s.fps > 200 and s.rr = 255 and s.speed=0 and s.b_amp > 0 and odo = XX;
FYI: I’ve just found this bug while porting the ‘re serve’ to ‘can log … tcpserver’. It seems we are binding to :3000 (or wherever) when we start, but not unbinding (closing the socket) when we stop. That means starting then stopping leaves the port in a weird state (where we can see a connection, but not accept it). Also can’t start, stop, start properly. I’ll commit the fix in the next hour or so. Regards, Mark
On 19 Jan 2019, at 9:34 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Should not be.
Are you sure the ‘re’ is running?
Regards, Mark.
On 19 Jan 2019, at 9:32 PM, Michael Eric Menk <mikeemenk@gmail.com <mailto:mikeemenk@gmail.com>> wrote:
On 19.01.2019 14:22, Tamás Kovács wrote:
Then, on workstation:
- nc 192.168.4.1 3000 | tee log.crtd
And the send me the log.crtd file.
Is the OVMS firewalled if it's connected as a WIFI client?
nmap -P0 -p 3000 192.168.1.84
Starting Nmap 7.60 ( https://nmap.org <https://nmap.org/> ) at 2019-01-19 14:31 CET Nmap scan report for 192.168.1.84 Host is up.
PORT STATE SERVICE 3000/tcp filtered ppp
Nmap done: 1 IP address (1 host up) scanned in 2.12 seconds
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
participants (3)
-
Mark Webb-Johnson -
Michael Eric Menk -
Tamás Kovács