AbuG
Established Member
I had my first long drive of 400miles. 2 Rapids and one overnight granny charge.
Used ABRP beta (need to sign up to beta - free) pretending to be MG5 as it's already setup for MG5. (How surprising.. yes you can download from the ABRP site if you have MG5 ).
For my ZS I had to change some of the parameter used in Torque Pro (as posted below) and for SOH I initially used a 14% degradation to account for the smaller battery. On the first leg of the trip it way overestimated usuage, it predicted to arrive with 25% SOC while really got about 45% (first 100 miles). I think it also calculates consumption and adusts too. The rest of the trip used a 12% degradation and it was pretty accurate at estimating the charge for destination and adjusts slightly while your driving depending on consumption and current live SoC.
I used the free version and manually input the weather conditions and road conditions. To my surprise it was pretty accurate. Except the recharge time. I was getting 40KW/H rates with double the charge times (but that can be adjusted for too in the future). That was despite warming the battery up by umpteen regenerations from 12C to 20C (SoC was 26%, which may have been the biggest factor. Ambient temp was 6C). Post Rapid charge battery temperature was 25C so might have to aim for that next time.
I also set up a remote recharge monitoring by us8ng the torque data uploaded to GDrive using tasker and monitoring from a second mobile at a slightly remoter location. But that's a little more complicated. ABRP can do this too but it's a premium service for data that we remotely send them.
The charging status wasn't working. But negative current and battery power can confirm its charging. Also SoC is raw so includes buffers.
Torque PIDs below for ZS derived from the MG5 one. (For MG5 use the ABRP website and it will direct you to the correct PID file)
Used ABRP beta (need to sign up to beta - free) pretending to be MG5 as it's already setup for MG5. (How surprising.. yes you can download from the ABRP site if you have MG5 ).
For my ZS I had to change some of the parameter used in Torque Pro (as posted below) and for SOH I initially used a 14% degradation to account for the smaller battery. On the first leg of the trip it way overestimated usuage, it predicted to arrive with 25% SOC while really got about 45% (first 100 miles). I think it also calculates consumption and adusts too. The rest of the trip used a 12% degradation and it was pretty accurate at estimating the charge for destination and adjusts slightly while your driving depending on consumption and current live SoC.
I used the free version and manually input the weather conditions and road conditions. To my surprise it was pretty accurate. Except the recharge time. I was getting 40KW/H rates with double the charge times (but that can be adjusted for too in the future). That was despite warming the battery up by umpteen regenerations from 12C to 20C (SoC was 26%, which may have been the biggest factor. Ambient temp was 6C). Post Rapid charge battery temperature was 25C so might have to aim for that next time.
I also set up a remote recharge monitoring by us8ng the torque data uploaded to GDrive using tasker and monitoring from a second mobile at a slightly remoter location. But that's a little more complicated. ABRP can do this too but it's a premium service for data that we remotely send them.
The charging status wasn't working. But negative current and battery power can confirm its charging. Also SoC is raw so includes buffers.
Torque PIDs below for ZS derived from the MG5 one. (For MG5 use the ABRP website and it will direct you to the correct PID file)
Code:
Name,ShortName,ModeAndPID,Equation,Min Value,Max Value,Units,Header
Z_MG_SoC_RAW,SoC_R,0x22b701,INT16(A:B)/10,0,100,%,7000
Z_MG_SoH_RAW,SoH_R,0x22b061,(a*256+b)/100,0,100,%,781
!MG_SoH,SoH,,val{!MG_SoH}+((val{Z_MG_SoH_RAW}-val{!MG_SoH})*INT((val{Z_MG_SoH_RAW}/(val{Z_MG_SoH_RAW}+0.01))+0.1)),0,100,%,
Z_MG_BattAmp_RAW,BattA_R,0x22b043,(INT16(A:B)-40000)/40,-100,100,A,781
!MG_BattAmp,BattA,,val{!MG_BattAmp}+((val{Z_MG_BattAmp_RAW}-val{!MG_BattAmp})*INT((abs(val{Z_MG_BattAmp_RAW})/(abs(val{Z_MG_BattAmp_RAW})+0.01))+0.1)),-100,100,A,
Z_MG_BattVolt_RAW,BattV_R,0x22b042,(a*256+b)/4,350,480,V,781
!MG_BattVolt,BattV,,val{!MG_BattVolt}+((val{Z_MG_BattVolt_RAW}-val{!MG_BattVolt})*INT((val{Z_MG_BattVolt_RAW}/(val{Z_MG_BattVolt_RAW}+0.01))+0.1)),0,16384,V,
Z_MG_MaxCharge_RAW,MaxCharge_R,0x22b402,INT16(A:B)/10,0,160,kW,7000
!MG_MaxCharge,MaxCharge,,val{!MG_MaxCharge}+((val{Z_MG_MaxCharge_RAW}-val{!MG_MaxCharge})*INT((val{Z_MG_MaxCharge_RAW}/(val{Z_MG_MaxCharge_RAW}+0.01))+0.1)),0,200,kw,
!MG_BattTemp,BattT,0x22b056,(A/2)-40,0,50,c,781
!MG_BattPower,BattP,,val{!MG_BattAmp}*val{!MG_BattVolt}/1000,-200,200,kw,
Z_MG_Charging_RAW,CHG_R,0x22b048,BIT(A:1)*BIT(A:2),0,1,,
!MG_Charging,CHG,,VAL{Z_MG_Charging_RAW}+RDLY(2:[22B048])+RDLY(4:[22B048])+RDLY(8:[22B048])+RDLY(16:[22B048])+RDLY(32:[22B048])+RDLY(64:[22B048])+RDLY(128:[22B048]),0,1,,
Last edited:
