Guru Meditation Error: StoreProhibited when using PID_ENGINE_TORQUE_DEMANDED

[AberrantAeon]

Hello All,

I have a question on if the following error is expected behaviour...

Code was cloned from https://github.com/stanleyhuangyc/Freem ... datalogger.
Vehicle: Dodge Grand Caravan 2015 SXT

When I add the PIDs PID_ENGINE_TORQUE_DEMANDED and/or PID_ENGINE_TORQUE_PERCENTAGE application causes a panic and Freematics One+ reboots...

here is the Code change:
PID_POLLING_INFO obdData[]= {
{PID_SPEED, 1},
{PID_RPM, 1},
{PID_THROTTLE, 1},
{PID_ENGINE_LOAD, 1},
{PID_FUEL_PRESSURE, 1},
{PID_RUNTIME, 1},
{PID_ETHANOL_FUEL, 1},
{PID_ENGINE_OIL_TEMP, 1},
//{PID_ENGINE_TORQUE_DEMANDED, 1}, <-- When un-commented the panic occurs
//{PID_ENGINE_TORQUE_PERCENTAGE, 1}, <-- When un-commented the panic occurs
{PID_FUEL_PRESSURE, 2},
{PID_TIMING_ADVANCE, 2},
{PID_COOLANT_TEMP, 3},
{PID_INTAKE_TEMP, 3},

};

Here is the console output:

Rebooting...
ESP32 240MHz 16MB Flash
MEMS...9-DOF OK
ACC Bias:-0.12/-0.00/0.88
SD...30618MB
OBD...OK
VIN...<removed>
/DATA/22.CSV
File: /DATA/23.CSV
Guru Meditation Error: Core 1 panic'ed (StoreProhibited)
. Exception was unhandled.
Register dump:
PC : 0x400dfc81 PS : 0x00060d30 A0 : 0x800df949 A1 : 0x3ffca810
A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00002710

Again is the expected behaviour?

Seconds question I guess is how do i find out what PID's are supported by my vehicle?

Thank you all for your time. I look forward to replies.

David.

[AberrantAeon]

OK, I think i figured it out. I was looking at and using the OBD.h file as a reference however it seems that I should have been using the logdata.h as a reverence. The logdata.h file did not have an entry for the PID_ENGINE_TORQUE_DEMANDED and PID_ENGINE_TORQUE_PERCENTAGE, so the likely cause of the error is because there was no value assigned to a definition. I have updated my logdata.h file and will be compiling and testing again in the next few days. If there are no more posts from me then adding

#define PID_ENGINE_TORQUE_DEMANDED 0x161
#define PID_ENGINE_TORQUE_ACTUAL 0x162

to the logdata.h file solved my issue.

Cheers!

[AberrantAeon]

That did not solve my problem. Back to the drawing board

[rosch]

Hi,

the PIDs are already defined in the file Freematics/libraries/FreematicsPlus/utility/OBD.h

Also look at the hex values, according to the file it seems you have to skip the mode number

#define PID_ENGINE_TORQUE_DEMANDED 0x61
#define PID_ENGINE_TORQUE_PERCENTAGE 0x62

rgds
rosch

[AberrantAeon]

@rosch - Thanks for the input I will have to try this out as I am just coming back to trying to develop something on the One+.