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.
Search found 88 matches
- 2022 Aug 20, 20:29
- Forum: CVAF1 - 99/01 (excludes late 2001)
- Topic: force monitors ready quickly
- Replies: 8
- Views: 4212
- 2022 Aug 07, 21:41
- Forum: Hardware, Programming & Disassembly
- Topic: How do you determine what bin file you are looking at?
- Replies: 2
- Views: 2796
Re: How do you determine what bin file you are looking at?
Thats what I thought.
Yea I see that. Was just making sure I wasn't missing it. Thanks for clarifying
Yea I see that. Was just making sure I wasn't missing it. Thanks for clarifying
- 2022 Aug 07, 21:16
- Forum: Hardware, Programming & Disassembly
- Topic: How do you determine what bin file you are looking at?
- Replies: 2
- Views: 2796
How do you determine what bin file you are looking at?
I see the "filename" at the end of a bin file when looking at a hex editor, but is there any other way you can identify the "catch code" of the file? I don't see that code in any of the bins I look at. Maybe I am missing it?
- 2022 Aug 06, 19:09
- Forum: Hardware, Programming & Disassembly
- Topic: ford box code strategy cross reference
- Replies: 10
- Views: 5669
Re: ford box code strategy cross reference
I would definitely like to add it to the OpenEEC project. Right now I want to get it straightened out and usable before we do that.motorhead1991 wrote: ↑2022 Aug 04, 02:44 I'd be happy to add whatever you like to OpenEEC as well as add you to it.
I do not get to work with excel much so this has been a nice project to learn a few more tricks. I will let you know. Thank you.
- 2022 Aug 05, 20:02
- Forum: Hardware, Programming & Disassembly
- Topic: ford box code strategy cross reference
- Replies: 10
- Views: 5669
Re: ford box code strategy cross reference
Updated with alot more information (46000 lines of data on the main page and multiple sheets from various sources). There is still alot of duplicates and sorting to do. I have mostly been concentrating on EEC-v stuff. If you have anything to contribute, please send it my way.
- 2022 Aug 05, 12:21
- Forum: Additional Support
- Topic: Service information request - post request here
- Replies: 0
- Views: 5267
Service information request - post request here
Post request here for Ford related service information on a job you are doing, as built information per VIN, etc...
- 2022 Aug 03, 08:42
- Forum: Additional Support
- Topic: Motorcraft Wiring pigtail kits ID guide
- Replies: 5
- Views: 4023
Re: Motorcraft Wiring pigtail kits ID guide
added motorcraft catalog from 2005 and 2020
- 2022 Jul 31, 14:16
- Forum: Hardware, Programming & Disassembly
- Topic: ford box code strategy cross reference
- Replies: 10
- Views: 5669
Re: ford box code strategy cross reference
Any idea what the "A" designation stand for in the hardware codes? According to the information at obdtester.com, they have the same part numbers as the non "A" designated modules. (as in MLC-462 and MLC-462A codes)
- 2022 Jul 31, 10:51
- Forum: Hardware, Programming & Disassembly
- Topic: ford box code strategy cross reference
- Replies: 10
- Views: 5669
Re: ford box code strategy cross reference
I have been pulling info from obdtester.com
I haven't looked at the openeec project in a while. I will look at it.
Thanks
I haven't looked at the openeec project in a while. I will look at it.
Thanks
- 2022 Jul 30, 23:02
- Forum: Hardware, Programming & Disassembly
- Topic: ford box code strategy cross reference
- Replies: 10
- Views: 5669
Re: ford box code strategy cross reference
If you have any data that you think could help that isn't posted on this site or linked from this site (I have already read the majority of information here), send it my way please. Thanks