SBEC3AB - Guide to disable downstream oxygen sensor

Or alter it to provide the "not supported" response. Or provide a response that is equivalent to "success" regardless of actual success or failure?

I'll bore you about the HOMOLOGATION ID.
return SCI CMD_2A_[1A:1F]

what is it?


//=============================
example (search google)
vahan.parivahan.gov.in/makermodel/forms/homologation_user_creation_from.pdf
or
www.tuvsud.com/en/industries/mobility-and-automotive/automotive-and-oem/homologation-and-global-market-access

I'm not aware of that field being used for anything in the States. Maybe by ChryCo themselves, but AFAIK it's not required to be made available via OBD2 (at least in applications of this vintage) so, it simply isn't.

Hello, first make sure you are all up to date with latest software versions (GUI / Scanner FW).

1. In GUI go to "Tools / Engine tools" menu and click "Detect" button, it will tell you JTEC or JTEC+:



From ITIL ISIS database: 56041423AH = JTEC+


2. Yes, flashing requires chip erasing beforehand but it is done automatically by the scanner:






3. With latest version I do not experience crashing.

Turn off PCI-bus transceiver.

Also, use simpler/shorter filename, without whitespace.

Very good, thanks for following up!

Check out the 4th point of the first post in this thread:

4. Equalize checksum plug in the edited flash file.

There is a MEGA.nz download link in there:
mega.nz/file/KNVnSBQC#s8V2HoWMBN7F69QP9fXfj2Z8ovSWXloBinnrnuGeTG8

Check the checkbox, load your flash file and the software will automatically equalize the checksum in place (overwriting loaded file).

There is source code in the archive if you want to understand how the calculation works.

Note that JTEC flash calibrations also use CVN verification which is not dealt with here. That is much more complicated than summing data in 256 byte blocks.

So if the PCM is ever inspected with professional tools, they will know it's modified.