Jeep Commander Forum banner

1 - 4 of 4 Posts

·
Registered
Joined
·
4 Posts
Discussion Starter #1
Has anyone connected a scanner to their commander? Should I see two ecu's? I must ask again. This is like a rubic's cube. i have the OBDwiz from Scantool. :brickwall:
 

·
Registered
Joined
·
16 Posts
I have the OBD2Wiz software and can help with this. Yes you will see more then one ECU. Normally the software will talk to the correct one by default. Make sure your set the correct protocol in the setup page - ISO 15765-4 CAN. I like to use the 11 bit but the others will work as well.
 

·
Registered
Joined
·
3,037 Posts
There has been several different protocols to communicate with PCM/ECU's over the years. Scan tools have to try each protocol until they hear a reply back from the PCM/ECU. Some scan tools display the protocol they are trying at the moment and goes through a list of them until they actually establish communication and stop going the thru the list of different protocols.

I suppose its possible someone could mistake the process being displayed on the OBDII scanner as it talking to more than one PCM/ECU. The Commander has only one PCM and it should communicate on the "CAN" bus.

The Commander does have multiple Electronic Control Modules (ECM's). Most basic OBDII scanners will only retrieve the OBDII codes and monitor outputs from the PCM. But perhaps others might communicate with additional ECM's, and it might be hard to tell one apart from another. Its possible you're seeing the Central Gateway, you might have to go through that before reaching the PCM. Or perhaps your OBDII scanner says it can read and interact with the ABS or Air Bags as well? If it can, you might be seeing the ABS module or the Air Bag module?

I don't know anything about the OBDWiz, so perhaps its just something peculiar to the OBDWiz that it is showing the 1 PCM twice?
 
1 - 4 of 4 Posts
Top