Saturn Vue 3.6 E67 PIDs

[Boost]

Just wondering about this. I work in a 3rd world country called Miami where the dealer with 20 techs has one broken Tech2 for all to share. So I often end up using my FS for warranty work (which is not bad). I was diagnosing a Saturn Vue with a 3.6 and selected several PIDs I wanted to monitor. When I went live, only the estimated cat. temp was working (none of the basic misfire PIDs, to my suprise). I went back and realized that only the E67 specific PIDs are live, and there are very few. Even when I check "supported" the GM specific PIDs don't seem to read. ???

[GMPX]

So, if you choose to connect as an E67 then force a PID validation with only supported ones ticked how many PID's show as available?

[Boost]

Little tired from a long day at work so not 100% sure what you mean sir. I connected as an E67, and looked at E67 specific PIDs but there were only a dozen or less, so I picked a few of those and a few other basic ones from other categories I thought it should have (like misfire). But those didn't work (after I validated PIDs of course). What should I try?

[GMPX]

E67 specific PID's are DMA PID's, not all OS's will have these defined. It's a big job to add them in and with over 100 OS's to cover for the E38 & E67 alone we tend to pick and choose which OS's we'll support (Camaro, Vette, trucks etc) tend to get preference.

[Boost]

:) I don't blame you for not focusing on the Vue lol just making sure I was doing it right. So is there anything intelligent I can do to filter which ones I can select for monitoring that will work for sure? Thanks