how to view MALF codes 1994 F-body

[Vapor]

I made a cable
works good, i don't get any errors packets when I send the stop communication command first

I am also using a MOSchip for the rs232

clear codes command works as well, but I can't find the actual trouble codes. when I connect, it only tells me 1 trouble code is in the history, not the actual code number

I am using EE.xdf and 16184737.ads with tunerpro rt4 on a 1994 F-body 3.4L camaro with 8192 12pin connector

I get a trouble code about 5 seconds after i start the car, and it is only 1 code showing up, and it won't clear out while the car is running

[robertisaar]

is your computer capable of running tunerpro RT V5? if so, i have a definition built that will work for you. i'm not certain if i have one made for V4 though.

[Vapor]

IRT5 says it is connected but gives me random readouts

I have tried EE.xdf and 2E_tpv5.xdf
and EE-auto.adx and importing 16184737.ads

16184737.ads works fine in RT4, altho i have noticed if i am not using the ground at the 12-pin connector, it only gets error packets when the car is running, so maybe my ECM isn't grounded well

it still doesn't show any errors by the stored or history of the flags list, while the car is running. it just says 1 in history, in RT4, right after i start it. when I start my car, about 5 seconds later check engine light comes on, I send clear code while it's running but is still there.

I have noticed the knock counter adds 1 every time my cars starts, the engine sounds fine, but it seems it logs exactly one every start, never fails, and is never 2 knocks. so I am thinking the knock sensor is doing it, yet it never goes away

[robertisaar]

the knock counter is acting normally, picking up knock counts during cranking is entirely normal since the knock filter works based off of fast changes to the signal the knock sensor picks up on.