LAUNCH TECH USA 1-877-528-6249 SUPPORT@LAUNCHTECHUSA.COM

Members Login
Chatbox
Please log in to join the chat!
Post Info TOPIC: 2006 Lancer Connectivity (Moved from old forum)


Guru

Status: Offline
Posts: 972
Date: Mar 2, 2010
2006 Lancer Connectivity (Moved from old forum)
Permalink  
 


Moved from old forum:

Problems logging in

View previous topic View next topic Go down
AuthorMessage
Frank-pr



Posts: 13
Join date: 2009-05-15

vide.gif
PostSubject: Problems logging in   icon_minitime.gifFri May 15, 2009 6:47 pmReply with quote

Problem with Mitsubishi Lancer 2006. I tried V24.00- 24.10- 24-15. I tried all connectors. I coundn't log in.
Back to top Go down
View user profile Send private message
tatsess



Posts: 119
Join date: 2008-03-21

vide.gif
PostSubject: Re: Problems logging in   icon_minitime.gifSat May 16, 2009 10:32 amReply with quote

try to get into the powertrain using generic obd2
Back to top Go down
View user profile Send private message
Frank-pr



Posts: 13
Join date: 2009-05-15

vide.gif
PostSubject: Problems logging in   icon_minitime.gifSun May 17, 2009 10:43 amReply with quote

I did it, but I only got in engine. I couldn't log in SRS- ABS Mitsubichi Lancer 2006.
I tried the tool in a :
Mercedes C320- 2003. 
BMW I 325- 2004 
Yaris 2007 and 2008
and some others cars and they all worked ok.
Back to top Go down
View user profile Send private message
Coyote



Posts: 107
Join date: 2008-03-29
Location: Atlanta, GA USA

vide.gif
PostSubject: Re: Problems logging in   icon_minitime.gifMon May 18, 2009 5:31 pmReply with quote

I assume this is not an EVO Lancer. If it was built before week 26 it will use the -16C connector. After build week 26 and forward the CanbusII should be used. Make sure it is programmed at 2.2. Also try using rest of world software as well as USA and Canada.

Coyote
Back to top Go down
View user profile Send private message
Frank-pr



Posts: 13
Join date: 2009-05-15

vide.gif
PostSubject: problem logging in   icon_minitime.gifMon May 18, 2009 6:41 pmReply with quote

thanks i will try tomorrow. and yes its not a Evo lancer. Its Mitsubishi Lancer 2006. 
Today i check a Toy SR5-Runner V6 2005. tool work OK.
Back to top Go down
View user profile Send private message

Problems logging in

View previous topic View next topic Back to top


__________________


Member

Status: Offline
Posts: 6
Date: Aug 16, 2015
Permalink  
 

I recently purchased the CRP123 from Autointhe box.com

Boot Version: V02.04

Displays Program Version: V02.28

Diagnostic Program Version: V11.22

Diagnostic Library Version: V11.22

I got the tool registered successfully and also got the firmware and data downloaded sucessfully onto the tool. I have observed the following issues with the tool when I connect it to my vehicle (Mitsubishi Lancer, Model:CS3, Year of Manufacture: 2002, Country of Manufacture: Japan):

With engine idling in Neutral, and CRP123 Tool connected to the DLC, the following function does not work:

DIAGNOSE: The green communication LED never blinks, as the tool tries all its communication protocols, which report as 'fail, fail' fail ... as the tool tries to communicate with the ECU. After all communication protocols fail, the display says 'Cannot Enter'.
I am therefore unable to use the DIAGNOSE function on the CRP123 Tool.

I then try the SCAN function, and I get options to Read DTC, Clear DTC and Read Datastream from the Engine ECU, the A/T ECU, the SRS ECU, I am able to view the Datastream from the Engine ECU, the A/T ECU and the SRS ECU, but not from the ABS ECU.

I turn ON the RECORD feature and the CRP123 records several snapshots of the Datastream on the display. I use the Review Datastream option to review the recorded data.

I have observed two anomalies with the temperature readings:

AIR TEMP. S = 85 Deg.C : Question: should this be the Engine Coolant Temperature instead of the Inlet Air Temperature?

CLT TEMP.SNSR = 35.04 Deg.C: Question:should this be the Inlet Air Temperature, instead of the Coolant Temperature?

The recorded datastream from the A/T ECU indicates:

OIL TEMP.SNSR = 26.15 Deg. C, which is less than the prevailing ambient temperature of 30 Deg.C.

Also note that when the coolant is at ambient temperature (30 Deg.C) prior to starting the engine, the CLT TEMP.SNSR reading is 2.2 Deg.C, which is unrealistic, as I am located in a tropical climate.

So I have three temperature readings on the CRP123 Datastream which all seem to be incorrect or incorrectly read from the vehicle's ECU.


Please advise what actions should be taken to address these anomalies in the temperature readings, as well as the failure of the CRP123 tool to communicate via the DIAGNOSE function with the Engine ECU.

The communication protocols loaded onto the CRP123 are:

J1850 VPW
J1850 PWM
ISO 15765-4 CAN (11-bit)
ISO 15765-4 CAN (29-bit)
ISO 14230-4 KWP
ISO 14230-4 KWP (5BPS)
ISO 9141


All above protocols indicated 'fail' when "Entering System" dialog box was displayed, soon after the DIAGNOSE function was selected.

Can anyone suggest possible fixes for this problem? Thank you.


__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.