Krolow Posted December 20, 2020 Share Posted December 20, 2020 Hi I have crawled through github and a few forums and has found a few changes I think should be made to what is sent to the server. Link to my github where the csv files can be found updated with all the pids I have found from different resources: Link to Krolow's Github These files are needed for Torque to have the right pids to sent to ABRP: 002, 003, 004, 005, 006 and ABRP For ease of use I have also made a combined only the necessary pids into a single file file that has all of these for new installers: ABRP_Only Updated: 000_HV_Charging, To correctly flag if charging or not without the workaround used before Updated: !_ABRP_Fast_Charging, Changed back to refer to value of 000_HV_Charging since it's now working correctly again When Torque sends the log this sensor has pid: ec3d7f Added: 003_VMCU Real Vehicle Speed, to show the actual real speed, should be same as GPS speed Added: !_ABRP_VMCU Real Vehicle Speed, We now have a known pid for this and I saw that for Ioniq this is monitored. Would make the GPS speed no longer needed. When Torque sends the log this sensor has pid: ee4ea0 Added: !_ABRP_Cumulative Energy Charged, We have a known pid for this and I saw that for Ioniq this is monitored. When Torque sends the log this sensor has pid: e38077 Added: !_ABRP_Cumulative Energy Discharged, We have a known pid for this and I saw that for Ioniq this is monitored. When Torque sends the log this sensor has pid: e22958 Added: !_ABRP_Battery Temperature, We have a known pid for this and I saw that it is monitored on other cars. When Torque sends the log this sensor has pid: e90ea2 (Seems ABRP already understands this one since i can see it in the app) Any thoughts on my changes and why some/all of them should or should not be used are much appreciated Link to comment Share on other sites More sharing options...
Jason-ABRP Posted January 19, 2021 Share Posted January 19, 2021 We don't actually use the 'cumulative energy discharged' parameter for anything, but I've added the rest of them to supported. We also have support for odometer readings if that exists. The full list of supported data can be found here: https://documenter.getpostman.com/view/7396339/SWTK5a8w?version=latest If you want to look through to find more PIDs which would be useful. I've also redirected the setup instructions to your download file. 1 Link to comment Share on other sites More sharing options...
Krolow Posted January 26, 2021 Author Share Posted January 26, 2021 Since 'Cumulative energy discharged' is not used have removed it from ABRP and the ABRP_only file We do have odometer pid in 006 file so I have added it to ABRP and ABRP_only files. The files linked are now updated! !_ABRP_Display Odometer When Torque sends the log this sensor has pid: ec5a94 Do let me know if you want me to name it something other for consistency with other cars or such Link to comment Share on other sites More sharing options...
Jason-ABRP Posted January 29, 2021 Share Posted January 29, 2021 Actually, since the odometer has its own unique PID we don't need the !ABRP_ entry, so I've added support for 22B002 to the Torque handler. Link to comment Share on other sites More sharing options...
Krolow Posted February 3, 2021 Author Share Posted February 3, 2021 Awesome that makes it even simpler !ABRP_ entry removed and I have started sending the Odometer (22B002) instead 1 Link to comment Share on other sites More sharing options...
Krolow Posted February 6, 2021 Author Share Posted February 6, 2021 @Jason (ABRP) I started thinking yesterday, are there any benefits or drawbacks of sending both GPS speed and Real Vehicle Speed to the server? I have checked and they are showing equal speed but the Real Vehicle Speed is of course a bit faster to update changes and is also working in tunnels so in my mind it would be the better choice of the two. Link to comment Share on other sites More sharing options...
Jason-ABRP Posted February 7, 2021 Share Posted February 7, 2021 Not really, real vehicle speed is good, and when you're running ABRP on your phone we compare the phone GPS data to the vehicle speed to calibrate it, but we don't compare Torque's GPS speed to the OBD speed. The OBD speed can be wrong, due to sensor errors, or tire diameter, etc, so we calibrate that to get true speed. Link to comment Share on other sites More sharing options...