EFIDynoTuning Forum

i tried out "force monitors ready quickly" patch on your latest cvaf1 xdf. when i enable this patch and monitor using torque app on my phone (my quickie ride around tool for monitoring for codes and readiness monitors) i can see all my readiness monitors ( including the secondary air monitor, which it is not equipped with) shows complete. then about 10 seconds later, all of them show "not supported". 10 seconds later, they show "completed". i get a similar result when i change obd_mil_sw to 0, then set to 247 with the engine running, it will show pretty much the same results, (all monitor show not supported with 0 is selected and then all monitors show complete when 247 is selected). this is the method i have used in the past to quicly force monitors to pass for various reasons.

is there a way to turn the secondary air monitor off in this patch?
is there a way so that this only happens once at key on and not constantly cycling on and off? i believe the way it is currently will cause a failure during emission inspection.

you turn monitors on and off with the bitmasks that 247 your referring to

its going to not complete cuz your at part throttle.

Yes

Are you talking about when I manually switch them? It completes. I have done it multiple times over the past 2 yrs I have been running cvaf1.

I guess I am not explaining it well enough. Will record what I am seeing.

what im saying it when you go part throttle to switches to not complete

Your saying sets not ready at part throttle and sets complete at idle?
What I am seeing could be also be something wierd with the software I am using. It(torque) is not pro grade, but have found it useful for non critical, personal stuff.

correct

So in vehicle testing now. That is pretty clever.
I looked back thru the calibration and verified that with the patch not applied, the secondary air shows not supported. When I apply it. It shows complete secondary air completed. . OBD-II_TST_SW and mil sw set at 247. The OBDII sw sair test switch is set to not set. If I set it to set, then the obd tst sw changes to 255 (as it should). Seems like there is something wrong with the patch that is forcing it to act like it is at 255. Thoughts?

thats how i wrote it

obdii bits dont exist

Ok. In that case I may have to revert back to my old way of flipping the bits manually when needed. Having a monitor showing complete on a vehicle not equipped with that specific item would be a red flag.