Non-OEM modules V2.0

[BillyTheKid]

I'm one of the people in the US Ford Ranger community that is working on adding the EATC to a 2004 Ranger that never had this option available, and I've got a few questions. First, some info on the vehicle and EATC module

aa) 2004 Ford Ranger 4.0 Gas SOHC USA
Networks: HSCAN >>> Inst cluster
SCP >>>> PCM
ISO >>>> ABS, RCM, 4x4 and GEM (officially known as, SJB, SmartJunction Box)

bb) EATC head unit to be added is from a 1998 - 2000 Ford Expedition, gas, 5.4 USA. In fact, I have two of these modules. Both were on the SCP bus in the Expedition, and nothing else was on that network. Both of these Expeditions had EATC as OEM equipment.

There may well be more questions, but I'd like to start with these.

a) Per the thread http://forscan.org/forum/viewtopic.php?f=5&t=1690, I downloaded and installed FORscan V1.3.9. It does not find the Expedition EATC module when added to the SCP bus in the 2004 Ranger, but ironically, it also doesn't find the OEM Ranger inst cluster, which seemed odd. Should I use an earlier version of V1.X.X in the quest to see if the EATC module will be detected and if so, which one(s)?

b) As mentioned in the previous thread on this subject, FORScan V1.?.?, when initiated, does a "who is here", looking for modules. With that said, shouldn't I be able to hook a powered up ELM327 adapter to the SCP wires and ground on a powered up EATC module, and FORScan finds it?

***This question because, I have EATC modules for the USA Ford Expedition, USA Ford Crown Victoria, USA Ford Explorer and a USA Lincoln Continental. All of the modules communicated on the SCP bus and available to be tested as noted in b), if that test is valid and works.

The above will clear up a few concerns; thank you in advance for the support, awesome software and the android app, an incredible diagnostic tool!

-Bill

[FORScan]

aa) 2004 Ford Ranger 4.0 Gas SOHC USA
Networks: HSCAN >>> Inst cluster
SCP >>>> PCM
ISO >>>> ABS, RCM, 4x4 and GEM (officially known as, SJB, SmartJunction Box)

Just to confirm: FORScan v2 (latest one from site) is able to connect to this vehicle with the ELM327 adapter and detect all the modules mentioned above, right? We're asking to make sure adapter is ok, as these are 3 different circuits of ELM327 adapter and some may not work in case of CCC (cheap china clone).

a) Per the thread http://forscan.org/forum/viewtopic.php?f=5&t=1690, I downloaded and installed FORscan V1.3.9. It does not find the Expedition EATC module when added to the SCP bus in the 2004 Ranger, but ironically, it also doesn't find the OEM Ranger inst cluster, which seemed odd. Should I use an earlier version of V1.X.X in the quest to see if the EATC module will be detected and if so, which one(s)?

FORScan v1 is quite old development and some of it's logic may look weird from today. One of the weirdnesses is that it doesn't look for CAN modules if primary module (PCM) is on the SCP bus. This was done to cut the connection time, as when it was done we had no experiences with vehicles that had 3-4 bus on the board. In other words, the fact v1.3.9 it cannot find instrument cluster on CAN is normal. However, the fact it cannot find EATC module is not normal. We see 2 possible reasons for it:

1. There is a problem with hardware connection to SCP bus.
2. The module is available on network address not known by FORScan .

If possible, please provide the following (via PM or email):

A. Logs from FORScan v1.3.9 ('log' subfolder of the installation folder)
B. Any information to identify the Expedition that had the EATC installed.

b) As mentioned in the previous thread on this subject, FORScan V1.?.?, when initiated, does a "who is here", looking for modules. With that said, shouldn't I be able to hook a powered up ELM327 adapter to the SCP wires and ground on a powered up EATC module, and FORScan finds it?

***This question because, I have EATC modules for the USA Ford Expedition, USA Ford Crown Victoria, USA Ford Explorer and a USA Lincoln Continental. All of the modules communicated on the SCP bus and available to be tested as noted in b), if that test is valid and works.

FORScan (even 1.3.9) starts from PCM detection. If no PCM is detected, it will not continue with other modules. So there is no ability yet to test it alone.

[BillyTheKid]

aa) 2004 Ford Ranger 4.0 Gas SOHC USA
Networks: HSCAN >>> Inst cluster
SCP >>>> PCM
ISO >>>> ABS, RCM, 4x4 and GEM (officially known as, SJB, SmartJunction Box)

Just to confirm: FORScan v2 (latest one from site) is able to connect to this vehicle with the ELM327 adapter and detect all the modules mentioned above, right? We're asking to make sure adapter is ok, as these are 3 different circuits of ELM327 adapter and some may not work in case of CCC (cheap china clone).

Yes verified once again today. Also, OBDII also appears on the SCP network (I overlooked that one but it is also SCP). These items also appear on the FORScan Android app. The CCC is working.

a) Per the thread http://forscan.org/forum/viewtopic.php?f=5&t=1690, I downloaded and installed FORscan V1.3.9. It does not find the Expedition EATC module when added to the SCP bus in the 2004 Ranger, but ironically, it also doesn't find the OEM Ranger inst cluster, which seemed odd. Should I use an earlier version of V1.X.X in the quest to see if the EATC module will be detected and if so, which one(s)?

FORScan v1 is quite old development and some of it's logic may look weird from today. One of the weirdnesses is that it doesn't look for CAN modules if primary module (PCM) is on the SCP bus. This was done to cut the connection time, as when it was done we had no experiences with vehicles that had 3-4 bus on the board. In other words, the fact v1.3.9 it cannot find instrument cluster on CAN is normal. However, the fact it cannot find EATC module is not normal. We see 2 possible reasons for it:

1. There is a problem with hardware connection to SCP bus.
2. The module is available on network address not known by FORScan .

If possible, please provide the following (via PM or email):

A. Logs from FORScan v1.3.9 ('log' subfolder of the installation folder)
B. Any information to identify the Expedition that had the EATC installed.

PM being sent.

b) As mentioned in the previous thread on this subject, FORScan V1.?.?, when initiated, does a "who is here", looking for modules. With that said, shouldn't I be able to hook a powered up ELM327 adapter to the SCP wires and ground on a powered up EATC module, and FORScan finds it?

***This question because, I have EATC modules for the USA Ford Expedition, USA Ford Crown Victoria, USA Ford Explorer and a USA Lincoln Continental. All of the modules communicated on the SCP bus and available to be tested as noted in b), if that test is valid and works.

FORScan (even 1.3.9) starts from PCM detection. If no PCM is detected, it will not continue with other modules. So there is no ability yet to test it alone.

Thank you, I did not know this.