Alpha Feedback - MG ZS EV

[Jason-ABRP]

To verify and improve our models we need your feedback.  There's many ways we could use help if you actually own one:

• Drive a plan and compare it to the actual battery used.
• Drive a plan with the browser active, and update your actual battery percentage in the browser.
• Contribute data via OBD or other methods.

The best way to improve the data is to provide data directly from the car.  Connecting your car not only improves the models, but allows you to follow up directly in the car while driving! We have several ways of doing that, but we need your help to figure out what will work with your car:

• An OBD reader can be used in concert with a custom app like LeafSpy, or a PID list and Torque Pro.
• If your manufacturer has an API to access data from the car we can set up access to that API, like we do for Tesla

If you're familiar with either of these, contact me at jason@abetterrouteplanner.com and I'll help figure out what we need to do to connect your car!

Thanks for providing feedback!

[MrC the MG]

Hi Jason. Found MG ZS EV is averaging 315 mpkWh. 398 seems quite high. Average range per charge is around 160

[Jpceir]

Jason,

well done on getting the new MG ZS EV up and running! I don’t own one yet ( no one does, as far as I know, with customer deliveries due to start in Sept), but hope to be one of the first owners!

May I ask where you got the reference 2.94 miles per kWh figure. There is an SpeakEV forum post saying that a dealer testing one was getting 4 miles per kWh at 60 mph......

regards

Joe

[Jason-ABRP]

The reference consumption was a conservative guess based on my modelling and estimates from a limited data set.  Based on this feedback I'll improve the consumption to 3.64mi/kWh, which keeps the 10% buffer on the estimate, and accounts for the 5mph difference a little as well.

[Jpceir]

Thanks for the reply Jason,

Although MG have released some performance data in the pre sales activities, we will, as you know, only get real world data when we get cars in the hands of customers. Of course everyone hopes that the car will do better than the laws of physics allow

My guess is that, except for the range issue of the smaller battery, this car will be about as efficient as the Kona and Kia....roughly same aerodynamic shape, power to weight ratio, and motors....roughly.....but small differences can have a big impact, like eg tyre resistance.

I hope to generate loads of data for you when I (finally) get mine!!

 

[logic]

The preset max speed of 190 km/h seems insane. Trying out different speeds for one route indicates the fastest overall speed would be about 130 km/h.

[Jpceir]

Thanks for the reply Jason,

Although MG have released some performance data in the pre sales activities, we will, as you know, only get real world data when we get cars in the hands of customers. Of course everyone hopes that the car will do better than the laws of physics allow

I have a report from a guy who drove it 9 hours a day all last week. He is telling me that he is routinely getting 4.5 mpkWh, and better, even on the motorway.

I hope to generate loads of data for you when I (finally) get mine!!

 

[Jason-ABRP]

On 8/5/2019 at 11:13 AM, Jpceir said:

Thanks for the reply Jason,

Although MG have released some performance data in the pre sales activities, we will, as you know, only get real world data when we get cars in the hands of customers. Of course everyone hopes that the car will do better than the laws of physics allow

I have a report from a guy who drove it 9 hours a day all last week. He is telling me that he is routinely getting 4.5 mpkWh, and better, even on the motorway.

I hope to generate loads of data for you when I (finally) get mine!!

 

Great! I look forward to it!

Be on the lookout for ways we can get live data, I find that very helpful when I drive my Bolt - to follow the plans live in the site (and helps us improve the models long-term).

[John Arnold]

I have had an MGZS EV for a month now. I have travelled 1000 miles in it. I am getting about 3 mi./kWh which I think is pretty poor. Perhaps it’s because the weather is getting colder. Travelling from Tiverton in Devon to my home in Hampshire the other week caused many headaches because the charging infrastructure is so poor. I tried to charge at many charge points and found them all dysfunctional. So I had to change my route with only about 30 miles left in the battery and Found charge points in Salisbury which were only 7K and only allowed an hour charging. Then onto M 27 services at Southampton and another 7K charger which just gave me enough juice to get home. What is normally a three hour journey took over 10 hours.

[Jpceir]

Hi Jason,

Trying to understand your planner. I have the MG EV, WLTP 163 miles. I note the performance figures above, which are clearly influenced by the cold weather in the UK. 

My question: for a trip of 88 miles, with 100% set for departure and 20% set for arrival, temperature set for 20 degrees, why does ABRP insist on one stop, for 6 minutes (71% to 79%)?? Surely this trip can be done without a stop????

Regards

Joe

[LiamWhales]

Hi Guys, I have an MG5 and have managed to get together a list of PIDs which should also work for an MG ZS. So please go and give these a try in the Torque app and see if they are reporting correctly. If there is anything out of place, put details on this thread and I'll take a look at the formulas etc. It's be great to get you guys up and running with live data.

See the thread below for the PID list.

 

[AbuG]

Hi, i just signed up to ABRP to test out its live data input for the MG ZS EV using and OBD2 and Torque Pro PIDs 

 

I am fairly new to this. The main difficulty is the Cars in different continents use some slight variation in PIDs. see the attached csv for most of the PiDS. some of these are duplicated and it may well need cleaning up abit.  Those begining with  "..eZS" ones were gathered by folks in Thailand. while "00_ " in UK and "001" in Australia. There is some considerable overlap and its still a WIP. see https://github.com/peternixon/MG-EV-OBD-PID 

 

I'm based in the UK which based on the forums on facebook and else where is likely to be the greatest market, at least in my view. 

 

I have taken the Kona ABRP file and adapted it below. the main one that may pose difficulty is "charging status" as it returns a interger and 6 is charging ( 1='idle':3='running':6='charging':10='connected not charging').

  

Name,ShortName,ModeAndPID,Equation,Min Value,Max Value,Units,Header

~Modifications by ....... for ABRP data contribution,List Credit,,,,,,

!_ABRP_Battery Current,Batt Current,,val{..eZS Current},-100,100,A,

!_ABRP_Battery DC Voltage,Batt Volts,,val{.00_BMS Volt},300,460,V,

!_ABRP_Battery Power,Energy Draw,,val{..eZS Current}*val{.00_BMS Volt}/1000,-90,90,kW,

!_ABRP_Fast_Charging,Charging,,val{.00_BMS Status},0,255,,

!_ABRP_State of Charge BMS,SOC BMS,,val{..eZS SoC},0,100,%,

!_ABRP_State of Charge Display,SOC Display,,val{ },0,100,%,

!_ABRP_State of Health,SOH,,val{..eZS SoH},0,100,%,

!_ABRP_Battery Temperature,Batt T,,val{..eZS Batt Temp},-40,50,C,

 

see attached CSV file for pids 

Let me know what else is required so we can get this up and running on the ABRP

ZS_EV 104PIDS.csv

[Jason-ABRP]

@AbuG - That's great digging! I'm out the rest of this week, but I can get the Torque receiver and PID list link updated next week.  Also, the integer charging status isn't an issue, as server-side we force it to cast to a boolean, so as long as it's zero = not charging and non-zero = charging we're good to go.  We might have to get clever with the math in the PID to account for '10', but that's not too hard I think.

[Jason-ABRP]

@AbuG I took a look through here, and came up with a few notes we should solve before implementing:

1. The "!_ABRP" notation is a little unnecessary here, that's only used on the HKMC PIDs because there's lots of parameters under the same PID, and Torque ID's them to the server by PID, so I wouldn't be able to tell which is which when I receive it.  These are all different PIDs, so no need for that.
2. Ideally we should have complete PID lists for each region to simplify installation.
3. @LiamWhales produced some equations to even out null readings, I'm not sure this is entirely necessary though, as I can do sanity checking on the ABRP server, so perhaps we should get rid of that to simplify the PID list.

If you guys could submit pull requests to the repository here:
https://github.com/iternio/ev-obd-pids/blob/main/mg/mg5_data.csv

With the updated PIDs in two or more separate CSVs, one for each region I will get them updated on the server side and update the instructions. On the instructions, we'll need to specify which regions are good for which PID lists.

[Casper]

@Jason-ABRP The PIDs currently submitted in the pull request work with my left hand drive 'Dutch' MG as well as with right hand drive MGs from the UK. Not sure about other regions, but at least all European MGs should work, which is the biggest market I assume

Also MG have released several BMS SW versions, the latest of which lowers the bottom buffer and increases the top buffer.(For better longevity and rapid charging). In the new PIDs the actual display SoC is automatically calculated based on the SW version.

[Nix]

@Casper I'm out of town at the moment so haven't looked at your pull request but I am already testing MG ZS EV integration with ABRP based on my PID list at https://github.com/peternixon/MG-EV-OBD-PID 

Would you mind letting me know if my PID list differs from yours and if so, I'd be happy to include anything I need to to support your vehicles as well.

Peter

[Casper]

@Nix I have only used your PID list from Github on my car and all PIDs work

I have currently disguised my ZS as an MG5 in ABRP so I can test it out. Apart from a different charge curve it seems to work pretty well. 

The only thing that was added in the pull request (By Vince) is the BMS version of my car, which was not used in the UK and only in other regions. (0823600P09) I am getting my car updated next week so if any other SW versions come to light I will let you know. 

[Nix]

On 6/28/2021 at 6:24 PM, Casper said:

@Nix I have only used your PID list from Github on my car and all PIDs work

I have currently disguised my ZS as an MG5 in ABRP so I can test it out. Apart from a different charge curve it seems to work pretty well. 

The only thing that was added in the pull request (By Vince) is the BMS version of my car, which was not used in the UK and only in other regions. (0823600P09) I am getting my car updated next week so if any other SW versions come to light I will let you know. 

 

@Casper it's probably best not to pollute the performance stats for the MG5 with ZS EV data 

If you use my PID list from https://github.com/peternixon/MG-EV-OBD-PID it now works for me with the MG ZS EV profile thanks to Jason. It could be that it's only enabled for testing on my account but it's worth trying as we can easily ask him to enable on your account also.

Simply set up Torque to send the following PIDs to http://api.iternio.com/1/tlm/torque

• MG BMS Charge Bool
• MG Battery Voltage
• MG Battery Current
• MG Battery State of Charge
• MG Battery State of Health
• MG HV Battery Temp
• MG Odometer Reading
• GPS Altitude
• GPS Bearing
• GPS Latitude
• GPS Longitude
• Speed (GPS)

Use the "Generic Token" as your email address in the Torque server logging setup. 

 

Let me know if it works for you or not.

 

Peter

Edited July 4, 2021 by Nix

[Casper]

@Nix 

Hi Peter, thank you, it works!

It seems like the Torque function for the ZS EV is now open for everyone. ABRP is working great and all the live data is correct

Casper

Edited July 4, 2021 by Casper

[Ngall]

This is brilliant. Works perfectly. Thanks for providing this. Enhances the app a lot. 

[Nix]

@Jason-ABRP I suggest that the Reference Consumption be changed to 205 WH/km @ 110km/H. I guess you should be starting to build up real data now from the 3 or 4 of us who are contributing via Torque but it's worth noting that the default value of 178 is almost exactly what I get around town. I don't even get close to that at 110kmph on the freeway!

[JohnGriff]

I have been able to connect TorquePro to ABRP, but the Live Data screen configured for an MG ZS EV is not displaying the SOC value, all I am seeing is "NaN%" All other values displayed in the Live data screen are correct. In TorquePro "MG Battery State of Charge" is displaying 62.3% and "MG Battery State of Charge Raw" 56.6%. When plugged in the car displays 59%. I have EU1 BMS version (4543793). I have checked that all the required PID's are selected for upload to the server. Any thoughts on a) why I am not seeing a SOC% in ABRP and b) Is the factor calculation for the BMS version calculation incorrect? Thanks in advance for help. As an FYI I have checked all the equations and they macth those in @NIX CSV file for the MGZS EV