PIDs momentarily get stuck - Torque main forum

RE: PIDs momentarily get stuck

hneel — Sun, 07 Jan 2024 12:03:10 +0000

I had a similar problem where one of the displays was no longer updated. In my case it turned out because I had changed my car model in the Advanded LE and EX modules and then used 'Add predefined set' again. From that moment one of the PIDs was missing from the list.

RE: PIDs momentarily get stuck

leipziger — Mon, 26 Oct 2015 14:30:59 +0000

Quote from HoTsHoT89 on October 26, 2015 The PID is dependent whether if the car supports it and Techstream displaying the PID. Mine doesn't have that PID. Many thanks. It is possible that the PID 83 not implemented in petrol cars. However, the NOx - PID 83 is of particular interest in diesel cars.

RE: PIDs momentarily get stuck

HoTsHoT89 — Mon, 26 Oct 2015 09:35:09 +0000

The PID is dependent whether if the car supports it and Techstream displaying the PID. Mine doesn't have that PID.

RE: PIDs momentarily get stuck

leipziger — Sun, 25 Oct 2015 15:46:00 +0000

Quote from HoTsHoT89 on October 24, 2015 Before I discovered this problem, I've been using the standard Mode01 PIDs even before I managed to obtain the Mode21 ones - I have driven with only the Mode01 PIDs for more than half an hour without the freezing issues, but I'll check at the adapter status to see if any errors are reported once I'm able. Here are the two examples of two Mode21 PIDs I added from Techstream (a dash represents a blank): OBD2 Mode and PID: 21f3 Long name: Injector pulse Short name: Injector pulse Minimum value: 0.0 Maximum value: 33.0 Scale factor: x1 Unit type: ms Equation: A / 255 * 32.64 OBD Header: Auto Diagnostic start command: - Diagnostic stop command: - I hope this above is some help to you. Thanks! Can you help me the NOx sensors at the moment: OBD2 Mode and PID: 0183 ? ? ...

RE: PIDs momentarily get stuck

HoTsHoT89 — Sat, 24 Oct 2015 08:38:40 +0000

Thanks for the in-depth explanation. I'm assuming the CAN ERROR is caused by turning off the entire car (as I did only once) which the ECU gets powered down. I've had no other notable issues when working with a terminal, Techstream, or your app either so here's guessing that it's likely the culprit. Could you explain in-depth about the header issue? As I have set the header to 7E0 in the custom init, but the Mode21 PID headers were set to Auto - was that the reason for the pausing? Also, this isn't related to the issue at hand but for the setting 'Always go to dashboard' in Settings -> General Preferences - after pressing back on the Vehicle Profile screen it immediately takes me to the realtime information screen. When set to 'Do not start dashboard screen' it goes back to the main menu, which should be the same for the 'Always go to dashboard' setting as it should follow the order of screens opened, don't you think? Lastly, thank you for the support - I can finally get back to testing :)

RE: PIDs momentarily get stuck

piemmm — Sat, 24 Oct 2015 08:06:10 +0000

Ok, hm there may be 2 problems here, one of which is fixed by using the alternate OBD2 header, however I've also seen from the log: 1445673198692 < SH 7E0 1445673198709 > OK 1445673198712 < 01051 1445673198750 > CAN ERROR 1445673198751 < 010C1 1445673198805 > CAN ERROR 1445673198806 < 010F1 1445673198878 > CAN ERROR 1445673198880 < 01451 1445673198921 > CAN ERROR 1445673198922 < 21FB 1445673198963 > CAN ERROR 1445673198964 < 01051 1445673199008 > CAN ERROR 1445673199009 < 010C1 1445673199080 > 410C0000 1445673199095 < 010F1 Which isn't supposed to happen. The 'CAN ERROR' message is from the adapter itself when it or the ECU can't talk properly to each other. From the documentation (at http://elmelectronics.com/DSheets/ELM327DS.pdf):

CAN ERROR
The CAN system had difficulty initializing, sending,
or receiving. Often this is simply from not being
connected to a CAN system when you attempt to send
a message, but it may be because you have set the
system to an incorrect protocol, or to a baud rate that
does not match the actual data rate. As with BUS
ERRORs, the CAN ERROR might also be the result of
a wiring problem, so if this is the first time using your
ELM327 circuit, review all of your CAN interface
circuitry before proceeding.

This means one of: * That there is a either a bad connection between the vehicle ECU and adapter * There is a lot of 'noise' on the data lines used to talk to the ECU (possible with systems that have issues with electrical noise or bad alternators) * Or that the adapter is suspect (unfortunately this is fairly common with the clone adapters) * Or, you stared the vehicle engine whilst connected to the vehicle and taking the debug (this can cause this issue as well, but CANBUS is designed so that this again shouldn't happen) I only see it once in the log, so if you started the vehicle whilst connected to the ECU then I'm going to put it down to that. If you didn't, then it's likely going to be the adapter that's at fault or one of the other points above

RE: PIDs momentarily get stuck

HoTsHoT89 — Sat, 24 Oct 2015 07:56:16 +0000

Hi, Ticking 'Alternative OBD header' at the Vehicle Profile seems to have fixed the issue, both Mode01 and Mode21 PIDs work upon the first connect. I've sent the debug log which logs my second workaround as well.

RE: PIDs momentarily get stuck

piemmm — Sat, 24 Oct 2015 07:45:53 +0000

Also, if you could send another debug after you start getting the Mode 01 PIDs working again (when not using the alternate) setting, that would also be useful! (edit: ta got that debug now too...)

RE: PIDs momentarily get stuck

piemmm — Sat, 24 Oct 2015 07:44:29 +0000

Got it, ta. It looks like one of the extended PIDs you're using is setting the header, and this is different to the default header that is used when the vehicle first connects when it's set back to it's default Can you in the vehicle profile tick the 'Alternate OBD header' option(or disable it if it is ticked) and see if that helps?

RE: PIDs momentarily get stuck

HoTsHoT89 — Sat, 24 Oct 2015 07:29:51 +0000

Just sent the debug log a minute ago - thanks!