Charge-status disappeared on update to 3.2.011 . The SOC is read, but it do not know that the car is charging. As you can see from the screenshot, OVMS sees the inncomming charge into the battery, but the state is "Not charging" -- Michael Eric Menk
What is the previous version of OVMS fw installed. The charge detection commited at 2019 dec 25 the next OVMS release is 3.2.009. No crash/reboot/fw update during charge? Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 17., P, 13:20):
Charge-status disappeared on update to 3.2.011 .
The SOC is read, but it do not know that the car is charging.
As you can see from the screenshot, OVMS sees the inncomming charge into the battery, but the state is "Not charging"
-- Michael Eric Menk
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 17.04.2020 20:51, Tamás Kovács wrote:
What is the previous version of OVMS fw installed. The charge detection commited at 2019 dec 25 the next OVMS release is 3.2.009.
My previous version is 3.2.008
No crash/reboot/fw update during charge?
No, completely stable. But I do not have a SD car installed for logging. But it is partially working... The DC kWh number is stored and updating when charging. the only place I find that it updates is inside : if (StandardMetrics.ms_v_charge_inprogress->AsBool()) { ms_v_charge_dc_kwh->SetValue((ms_v_charge_dc_kwh->AsFloat() + (StandardMetrics.ms_v_bat_power->AsFloat() / -360000.0))); } This indicates that the StandardMetrics.ms_v_charge_inprogress is set correctly, but there is no charge status in the app, command-line or on web-page.
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem? *me li v.c.* Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 17., P, 21:38):
On 17.04.2020 20:51, Tamás Kovács wrote:
What is the previous version of OVMS fw installed. The charge detection commited at 2019 dec 25 the next OVMS release is 3.2.009.
My previous version is 3.2.008
No crash/reboot/fw update during charge?
No, completely stable. But I do not have a SD car installed for logging.
But it is partially working...
The DC kWh number is stored and updating when charging.
the only place I find that it updates is inside :
if (StandardMetrics.ms_v_charge_inprogress->AsBool()) { ms_v_charge_dc_kwh->SetValue((ms_v_charge_dc_kwh->AsFloat() + (StandardMetrics.ms_v_bat_power->AsFloat() / -360000.0))); }
This indicates that the StandardMetrics.ms_v_charge_inprogress is set correctly, but there is no charge status in the app, command-line or on web-page. _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
If the problem appear on AC you use 230V or 110V? I tested now but not reproduce, only the type of charging (type1 ...) not show when i reboot the OVMS module when the charging at almost full. [image: Screenshot 2020-04-18 at 17.24.43.png] [image: Screenshot 2020-04-18 at 17.27.47.png] Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2020. ápr. 18., Szo, 5:41):
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem?
*me li v.c.*
Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 17., P, 21:38):
On 17.04.2020 20:51, Tamás Kovács wrote:
What is the previous version of OVMS fw installed. The charge detection commited at 2019 dec 25 the next OVMS release is 3.2.009.
My previous version is 3.2.008
No crash/reboot/fw update during charge?
No, completely stable. But I do not have a SD car installed for logging.
But it is partially working...
The DC kWh number is stored and updating when charging.
the only place I find that it updates is inside :
if (StandardMetrics.ms_v_charge_inprogress->AsBool()) { ms_v_charge_dc_kwh->SetValue((ms_v_charge_dc_kwh->AsFloat() + (StandardMetrics.ms_v_bat_power->AsFloat() / -360000.0))); }
This indicates that the StandardMetrics.ms_v_charge_inprogress is set correctly, but there is no charge status in the app, command-line or on web-page. _______________________________________________ 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
And please send some information from your car. example the "xmi vin" command, the car vin not necessary Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2020. ápr. 18., Szo, 17:28):
If the problem appear on AC you use 230V or 110V? I tested now but not reproduce, only the type of charging (type1 ...) not show when i reboot the OVMS module when the charging at almost full. [image: Screenshot 2020-04-18 at 17.24.43.png] [image: Screenshot 2020-04-18 at 17.27.47.png]
Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2020. ápr. 18., Szo, 5:41):
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem?
*me li v.c.*
Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 17., P, 21:38):
On 17.04.2020 20:51, Tamás Kovács wrote:
What is the previous version of OVMS fw installed. The charge detection commited at 2019 dec 25 the next OVMS release is 3.2.009.
My previous version is 3.2.008
No crash/reboot/fw update during charge?
No, completely stable. But I do not have a SD car installed for logging.
But it is partially working...
The DC kWh number is stored and updating when charging.
the only place I find that it updates is inside :
if (StandardMetrics.ms_v_charge_inprogress->AsBool()) { ms_v_charge_dc_kwh->SetValue((ms_v_charge_dc_kwh->AsFloat() + (StandardMetrics.ms_v_bat_power->AsFloat() / -360000.0))); }
This indicates that the StandardMetrics.ms_v_charge_inprogress is set correctly, but there is no charge status in the app, command-line or on web-page. _______________________________________________ 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 18.04.2020 05:41, Tamás Kovács wrote:
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem? _ _ _me li v.c._ I hava a 80 cell 2015 Citroën C-Zero. VIN: VF71NZKYZFU900455 230V 6A charge after 1.1kWh charged.
v.c.charging no
v.c.climit 0A
v.c.current 0A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode None
v.c.pilot no
v.c.state stopped
v.c.substate interrupted
v.c.temp 25°C
v.c.time 0Sec
v.c.timermode
v.c.timerstart
v.c.type None
v.c.voltage 0V
Fast charging (start) CC mode
v.c.charging yes
v.c.climit 124A
v.c.current 124.6A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 19°C
v.c.time 20Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 320.7V
Fast charg CV mode
v.c.charging yes
v.c.climit 38A
v.c.current 38.88A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 21°C
v.c.time 817Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 328.1V
As you can se, the v.c.kwh do not increase, but xmi.e.trip.park.energy.used while charging. An other bug, RR (Range Remaining) is set to 255 on the CAN bus while fast charging, this is now set to 255 out to the user. [1] The code earlier saved the last known value of RR and of SOC, and calculated the RR base on SOC while fastcharging. I find it weird that CC-max goes down during the CV stage of the charging. I started a change of code. The idea was to warn user about reduced speed due to temperature. I stopped when I saw the code change. Coldest cell under 1°C => Max 25A (C/2) Coldest cell under 11°C => Max 50A (C) Warmest cell over 46°C => Max 85A (looks like its more dynamic, no cell goes above 47) Warmest cell over 30°C => Max 100A (2C) Optimal (11-29°C) => Max 125A (2.5C) BTW: If someone know how to start the heater + fanspeed low when Type-1 charging (the DC-bus is energized when type-1 charging), that would bee neat. [1] https://tjinfo.uib.no/Vedlegg?id=e9d1c4031a9f03d196f07e6be82bbe2f
Please create a log file while you charging with 230V (1-2 minutes enough), start logging before connect charger and send it to me. - can log crtd /sd/file.crtd 286 - …record… - can log stop - http://ovmsname.local/file.crtd The Ideal range is based on 16.1kWh/100km consumption and the battery health (this updated during charge, quick and normal charge). My car is 2012 Peugoet iOn, with SOH 78%, and my RR at 100% is 113km, the old code calc the RR during quickcharge with last rr 20 and range 8km if soc < 20 this is too optimistic i think. Ideal range calculation is = cell_number * 3.7 * bat_cac * bat_soc / 16100. So my full charge ideal range is ~75km. In your car the bms cell monitor working? Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 21., K, 12:58):
On 18.04.2020 05:41, Tamás Kovács wrote:
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem?
*me li v.c.*
I hava a 80 cell 2015 Citroën C-Zero. VIN: VF71NZKYZFU900455 230V 6A charge after 1.1kWh charged.
v.c.charging no
v.c.climit 0A
v.c.current 0A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode None
v.c.pilot no
v.c.state stopped
v.c.substate interrupted
v.c.temp 25°C
v.c.time 0Sec
v.c.timermode
v.c.timerstart
v.c.type None
v.c.voltage 0V
Fast charging (start) CC mode
v.c.charging yes
v.c.climit 124A
v.c.current 124.6A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 19°C
v.c.time 20Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 320.7V
Fast charg CV mode
v.c.charging yes
v.c.climit 38A
v.c.current 38.88A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 21°C
v.c.time 817Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 328.1V
As you can se, the v.c.kwh do not increase, but xmi.e.trip.park.energy.used while charging. An other bug, RR (Range Remaining) is set to 255 on the CAN bus while fast charging, this is now set to 255 out to the user. [1] The code earlier saved the last known value of RR and of SOC, and calculated the RR base on SOC while fastcharging. I find it weird that CC-max goes down during the CV stage of the charging. I started a change of code. The idea was to warn user about reduced speed due to temperature. I stopped when I saw the code change. Coldest cell under 1°C => Max 25A (C/2) Coldest cell under 11°C => Max 50A (C) Warmest cell over 46°C => Max 85A (looks like its more dynamic, no cell goes above 47) Warmest cell over 30°C => Max 100A (2C) Optimal (11-29°C) => Max 125A (2.5C) BTW: If someone know how to start the heater + fanspeed low when Type-1 charging (the DC-bus is energized when type-1 charging), that would bee neat.
[1] https://tjinfo.uib.no/Vedlegg?id=e9d1c4031a9f03d196f07e6be82bbe2f
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
I've tried the command you sendt. OVMS# can log crtd /sd/file.crtd 286 Unrecognised command Ths option crtd seams not to exist. OVMS# can log ? list Logging list start CAN logging start framework status Logging status stop Stop logging OVMS# can log start ? monitor CAN logging to MONITOR tcpclient CAN logging as TCP client tcpserver CAN logging as TCP server vfs CAN logging to VFS And yes, I do get the data from the BMS.
Ideal range calculation is = cell_number * 3.7 * bat_cac * bat_soc / 16100. So my full charge ideal range is ~75km. No matter what method used, it should never set the RR from the can bus while fast-charing. In my opinion, better the value set to '' or '-' than 255.
On 21.04.2020 20:00, Tamás Kovács wrote:
Please create a log file while you charging with 230V (1-2 minutes enough), start logging before connect charger and send it to me.
* |can log crtd /sd/file.crtd 286| * …record… * |can log stop| * http://ovmsname.local/file.crtd
The Ideal range is based on 16.1kWh/100km consumption and the battery health (this updated during charge, quick and normal charge). My car is 2012 Peugoet iOn, with SOH 78%, and my RR at 100% is 113km, the old code calc the RR during quickcharge with last rr 20 and range 8km if soc < 20 this is too optimistic i think. Ideal range calculation is = cell_number * 3.7 * bat_cac * bat_soc / 16100. So my full charge ideal range is ~75km.
In your car the bms cell monitor working?
Michael Eric Menk <mikeemenk@gmail.com <mailto:mikeemenk@gmail.com>> ezt írta (időpont: 2020. ápr. 21., K, 12:58):
On 18.04.2020 05:41, Tamás Kovács wrote:
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem? _ _ _me li v.c._
I hava a 80 cell 2015 Citroën C-Zero. VIN: VF71NZKYZFU900455 230V 6A charge after 1.1kWh charged.
v.c.charging no
v.c.climit 0A
v.c.current 0A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode None
v.c.pilot no
v.c.state stopped
v.c.substate interrupted
v.c.temp 25°C
v.c.time 0Sec
v.c.timermode
v.c.timerstart
v.c.type None
v.c.voltage 0V
Fast charging (start) CC mode
v.c.charging yes
v.c.climit 124A
v.c.current 124.6A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 19°C
v.c.time 20Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 320.7V
Fast charg CV mode
v.c.charging yes
v.c.climit 38A
v.c.current 38.88A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 21°C
v.c.time 817Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 328.1V
As you can se, the v.c.kwh do not increase, but xmi.e.trip.park.energy.used while charging. An other bug, RR (Range Remaining) is set to 255 on the CAN bus while fast charging, this is now set to 255 out to the user. [1] The code earlier saved the last known value of RR and of SOC, and calculated the RR base on SOC while fastcharging. I find it weird that CC-max goes down during the CV stage of the charging. I started a change of code. The idea was to warn user about reduced speed due to temperature. I stopped when I saw the code change. Coldest cell under 1°C => Max 25A (C/2) Coldest cell under 11°C => Max 50A (C) Warmest cell over 46°C => Max 85A (looks like its more dynamic, no cell goes above 47) Warmest cell over 30°C => Max 100A (2C) Optimal (11-29°C) => Max 125A (2.5C) BTW: If someone know how to start the heater + fanspeed low when Type-1 charging (the DC-bus is energized when type-1 charging), that would bee neat.
[1] https://tjinfo.uib.no/Vedlegg?id=e9d1c4031a9f03d196f07e6be82bbe2f
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Sorry the good command is can log start vfs /sd/file.crtd 286 2020. április 25., szombat dátummal Michael Eric Menk <mikeemenk@gmail.com> ezt írta:
I've tried the command you sendt.
OVMS# can log crtd /sd/file.crtd 286 Unrecognised command
Ths option crtd seams not to exist.
OVMS# can log ? list Logging list start CAN logging start framework status Logging status stop Stop logging
OVMS# can log start ? monitor CAN logging to MONITOR tcpclient CAN logging as TCP client tcpserver CAN logging as TCP server vfs CAN logging to VFS
And yes, I do get the data from the BMS.
Ideal range calculation is = cell_number * 3.7 * bat_cac * bat_soc / 16100. So my full charge ideal range is ~75km.
No matter what method used, it should never set the RR from the can bus while fast-charing. In my opinion, better the value set to '' or '-' than 255.
On 21.04.2020 20:00, Tamás Kovács wrote:
Please create a log file while you charging with 230V (1-2 minutes enough), start logging before connect charger and send it to me.
- can log crtd /sd/file.crtd 286 - …record… - can log stop - http://ovmsname.local/file.crtd
The Ideal range is based on 16.1kWh/100km consumption and the battery health (this updated during charge, quick and normal charge). My car is 2012 Peugoet iOn, with SOH 78%, and my RR at 100% is 113km, the old code calc the RR during quickcharge with last rr 20 and range 8km if soc < 20 this is too optimistic i think. Ideal range calculation is = cell_number * 3.7 * bat_cac * bat_soc / 16100. So my full charge ideal range is ~75km.
In your car the bms cell monitor working?
Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 21., K, 12:58):
On 18.04.2020 05:41, Tamás Kovács wrote:
Please send the following command output during charge. AC (Type1) or DC(CHAdeMO charge the problem?
*me li v.c.*
I hava a 80 cell 2015 Citroën C-Zero. VIN: VF71NZKYZFU900455 230V 6A charge after 1.1kWh charged.
v.c.charging no
v.c.climit 0A
v.c.current 0A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode None
v.c.pilot no
v.c.state stopped
v.c.substate interrupted
v.c.temp 25°C
v.c.time 0Sec
v.c.timermode
v.c.timerstart
v.c.type None
v.c.voltage 0V
Fast charging (start) CC mode
v.c.charging yes
v.c.climit 124A
v.c.current 124.6A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 19°C
v.c.time 20Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 320.7V
Fast charg CV mode
v.c.charging yes
v.c.climit 38A
v.c.current 38.88A
v.c.duration.full
v.c.duration.range
v.c.duration.soc
v.c.kwh 0kWh
v.c.limit.range
v.c.limit.soc
v.c.mode CHAdeMO
v.c.pilot yes
v.c.state charging
v.c.substate onrequest
v.c.temp 21°C
v.c.time 817Sec
v.c.timermode
v.c.timerstart
v.c.type Quickcharge
v.c.voltage 328.1V
As you can se, the v.c.kwh do not increase, but xmi.e.trip.park.energy.used while charging. An other bug, RR (Range Remaining) is set to 255 on the CAN bus while fast charging, this is now set to 255 out to the user. [1] The code earlier saved the last known value of RR and of SOC, and calculated the RR base on SOC while fastcharging. I find it weird that CC-max goes down during the CV stage of the charging. I started a change of code. The idea was to warn user about reduced speed due to temperature. I stopped when I saw the code change. Coldest cell under 1°C => Max 25A (C/2) Coldest cell under 11°C => Max 50A (C) Warmest cell over 46°C => Max 85A (looks like its more dynamic, no cell goes above 47) Warmest cell over 30°C => Max 100A (2C) Optimal (11-29°C) => Max 125A (2.5C) BTW: If someone know how to start the heater + fanspeed low when Type-1 charging (the DC-bus is energized when type-1 charging), that would bee neat.
[1] https://tjinfo.uib.no/Vedlegg?id=e9d1c4031a9f03d196f07e6be82bbe2f
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
_______________________________________________ OvmsDev mailing listOvmsDev@lists.openvehicles.comhttp://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 25.04.2020 14:21, Tamás Kovács wrote:
Sorry the good command is can log start vfs /sd/file.crtd 286
Still not correct command, but I used help. http://vedlegg.uib.no/?id=a56c8b273221fc3ddca3755ccdc84488 2min charge at 6A 230V IT Both connect and disconnect is in the dump.
Thanks the log, now i modified the AC charge detection code. If you want to try add the following to config / firmware / flash from web : kommykt-nas.ddns.net:22289/ovms3.bin This is my NAS, the internet speed is not very high. Should I rewrite the old RR display during quick charging? Michael Eric Menk <mikeemenk@gmail.com> ezt írta (időpont: 2020. ápr. 25., Szo, 15:37):
On 25.04.2020 14:21, Tamás Kovács wrote:
Sorry the good command is can log start vfs /sd/file.crtd 286
Still not correct command, but I used help.
http://vedlegg.uib.no/?id=a56c8b273221fc3ddca3755ccdc84488
2min charge at 6A 230V IT
Both connect and disconnect is in the dump.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Üdvözlettel: Kovács Tamás
On 25.04.2020 20:24, Tamás Kovács wrote:
Thanks the log, now i modified the AC charge detection code.
If you want to try add the following to config / firmware / flash from web : kommykt-nas.ddns.net:22289/ovms3.bin <http://kommykt-nas.ddns.net:22289/ovms3.bin> This is my NAS, the internet speed is not very high.
It now works OVMS# stat Type1 - Charging 234.0V/5.7A SOC: 95.5% Ideal range: 73km Est. range: 92km ODO: 82155.0km CAC: 41.8Ah SOH: 87% AC charge: 0.070kWh kWh DC charge: 0.040kWh kWh
Should I rewrite the old RR display during quick charging?
Its better that its empty than 255. So, the Est. range in OVMS should not be updated if the CAN bus claims 255, or sett to null. *Future improvments* But lets us see what numbers we have. The car calculates RR from the last 24 km. When driving downhill this can be a bit optimistic, and pessimistic while driving uphill. * We have the Ah of the battery * We have the wh/km from 'xmi trip' (test if it has a valid range first) RR is 0 when CAN SOC is 10% (0% on display) So RR can CAC and xmi.v.bat.cac.rem to calculate a RR. When tha calculation is done, the lowest number of est range and ideal range is shown (in order to prevent error from downhill driving). With this method, you will get the heater usage inn to the calculation and over-optimistic range due to downhill driving.
participants (2)
-
Michael Eric Menk -
Tamás Kovács