2001 lincoln town car unidentified "contact developers"

[spdy]

i have the elm327 MS/HS switch USB adapter, and i have the elm327 interface v1.5 USB adapter. The adapters have no problem connecting with the software. For the most part I'm able to connect with the vehicle, but after the log states that the vehicle has been connected to there is a prolonged duration of time that goes by. It then asks for the vehicles module code, then it states vehicle could not be identified. contact the developers.

[rbentnail]

2001 is a really old vehicle to be using Forscan with. I've found it basically useless for trucks 2009 and earlier. Good luck!

[spdy]

I just found it odd how it worked flawlessly with a 2002 ford focus lx. I wouldn't think there was much of a different from 2001 to 2002 year models.

[tractmec]

I just found it odd how it worked flawlessly with a 2002 ford focus lx. I wouldn't think there was much of a different from 2001 to 2002 year models.

There is no difference between the two vehicles as far as the Module communication network is concerned! If the Town car is not connecting, the problem is likely not in FORScan or in the adapters(Much as the adapters you are describing ELM327 switched or un switched are no longer FORScan recommended and the HS/MS switch on the adapter has no function on either of the posted vehicles as there is no HS or MSCAN network)!
Only Two networks are used in either of these vehicles PWM/SCP(Pins 2 And 10) and ISO9141(Pin 7)

With what you have, FORScan should be able to at least connect and read DTC's and run live data PID's.

The problem is in the car some where! The first Pin point test would be checking for Battery voltage on DLC pin 16 (12 Volts+ at all times From Fuse 23 20A Central Junction Box and also powers the Cigar lighter/Power Point) and for a resistance of less than 5 ohms to Ground on DLC pins 4 and 5!
FTDI/ELM327 Based adapters must have 12 volts on DLC pin 16 in order to power them and be grounded(-) on pins 4 and 5 before a connection can even begin!

If that checks out then the DLC pins 2 And 10 will need to be checked for continuity to the PCM!
With out a good connection between the DLC pins 2(TN/OG) and 10(PK/LB) to the PWM Pins (16 TN/OG and 15 PKLB) pins on the PCM(Connector C123) and there should be no continuity to Ground or any Voltage reading(PCM disconnected with Key Off), FORscan will just fail the connection and ask for a PCM Part number and stop!

If that checks out then the PCM likely has an internal problem with the PWM Network circuit(Rare but not Impossible).

As far as the comment of FORScan being useless on older than 2009, I do not quite agree! There is no Module firmware ability or VinID block configuration as yet on these PWM and ISO based modules but that is not generally available in IDS unless using PMI for module replacement, or except for the PCM(PCM Calibration updates and VinID block in Ford VCM2 adapter only) which The team has informed me is very tricky and has been and still is in development!

Module (As built or other wise) configuration is very sparse in these model years even in IDS! In a Town car you may see one or two plain English configurations in the RCM, LCM DDM DSM and I have as yet found no one that knows anything about what any of the Asbuilt codes code for other than the VIN number in the ABS and the RCM modules and any other that are VIN specific!

This is a limitation of the vehicle and not necessarily a limitation in FORScan!

PCM Module Firmware With VinID block configuration, has recently become available(experimentaly) on HSCAN PHF file based PCM's from about 2004/2005 to 2008 in FORScan 2.4.09 and newer(I may tell a 2005 F150 story about how experimental some day)!

Don't know if that explains it clearly?