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

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: J1850 PWM not auto detecting


Member

Status: Offline
Posts: 6
Date: Jun 28, 2013
J1850 PWM not auto detecting
Permalink  
 


Just a heads up to anyone that has the CRP123 with the latest software.

The tool will not auto detect J1850 VPW protocol for some reason, assume an instruction error in the software.

Found this when connected to my GMC truck. If I manually configure the tool for the vehicle by make, model, engine type, the tool can read the data stream and fully communicate with all modules in the truck. So the tool can read the data stream if told what to do, it just cannot auto detect the protocol/data stream.


I have notified Launch regarding this issue, hopefully the next release will resolve the problem?

 

 



__________________


Member

Status: Offline
Posts: 8
Date: Sep 6, 2013
Permalink  
 

Thought I was getting an upgrade from my old CreaderIV, but I'm having this same problem. Four different 03 GMC pickups, no autodetect... I can go in with vin specific scan, but that doesn't allow me to see global OBDII informations, such as IM Readiness monitors, something that is key when repairing a Check engine light problem, and readying the vehicle for State Inspection, or even verifying repairs. I"m disheartened to see that since July, this issues hasn't been resolved.

__________________


Member

Status: Offline
Posts: 6
Date: Nov 15, 2013
Permalink  
 

Just wanted to update this thread.

I had been wait for updates and was a bit confused at the download from the Launch site was still dated June of 2012.

What I did not realize is the download was not really and update, but the updater tool. Called Launch this wek and was told this issue was resolved with a Firmware update for the CRP tools.

I can confirm the J1850 auto detect does now work without a problem.

What was bit confusing was the update tool did work, but now requires a password. I was able to update the firmware but then the updater required a password. You can call Launch and they can reset or assign a password so the update can actually contact the web site and gather the updated manufacturer specific files.

There were many updates for almost all manufacturers. I did find a few minor bugs in a few modules and have sent them to support for future fixes.

 

 



__________________


Member

Status: Offline
Posts: 8
Date: Dec 4, 2013
Permalink  
 

I can also confirm that an update I did on about the 16th of November did resolve this issue.... ABOUT TIME I suppose the old CRP123 was saved from my home firing range target practice pile.

__________________


Newbie

Status: Offline
Posts: 3
Date: Jan 20, 2015
Permalink  
 

I was  wondering if someone had a similar issue. I found this out when I tried to have the tool read my vehicle info. It was unable to read basic VIN and Calibration info via the EVAP System tesgt



__________________


Newbie

Status: Offline
Posts: 3
Date: Jan 20, 2015
Permalink  
 

Which firmware version took care of the problem?

 



__________________


Newbie

Status: Offline
Posts: 3
Date: Jan 20, 2015
Permalink  
 

Because Currently I'm running

Boot ver-    V02.04

Display Programarrow-10x10.png ver-  V02.28

Diag Programarrow-10x10.png ver-    V11.22

Diag library ver-    V11.22

Are these the latest? I haven't seen anything later than these online so far



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard