search

fenugrec / freediag

OBD2 scantool
GNU General Public License v3.0
338 stars 75 forks source link

cannot connect to Chrysler Voyager #78

Closed DavidCprog closed 2 years ago

DavidCprog commented 2 years ago

fails at scantool_diag.c Line 365 which leads to iInitbus type not supported by HW. Presently looking at C code to see for myself. There's a good possibility it has nothing to do with the program. My 2000 Chrysler Voyager passed the inspection scan but failed autoparts scanner, my sears scanner, the ELM327 with an iPhone and freediag run from Laptop. Chrysler Voyager has OBDII but there's an excellent possibility it has it's own protocol.
I'm lightly familiar with the SCI & CCD data lines. Thanks ahead for your time Dave

fenugrec commented 2 years ago

There's a good possibility it has nothing to do with the program.

If even commercial scanners (depending what they had at your autoparts) failed, it's going to be difficult to pinpoint. You'll need to be a lot more familiar than me with the J1850 protocol and its different flavours. If your ELM327 is a clone (very likely) it might not even properly support j1850-vpw / pwm at all...

DavidCprog commented 2 years ago

Thanks, the reply is appreciated. I know it's not a simple problem. I'll keep working on the C and maybe at least find out where the problem is. My sears scanner worked fine with a Merecedes. If you'd like and I get some answers I'll gladly inform. Thanks again Enjoy Dave

fenugrec commented 2 years ago

First thing to validate would be what protocol it actually uses. If it's not J1850 but rather that CCD protocol I had never heard of until 20 minutes ago, you may even need some special hardware and that would be totally out of scope for this project. I don't think even the BR-1 interface we support can even do CCD...

My understanding of OBD2 / SAE J1979 was that it offered 3 choices : CAN, K-line (iso9141 or 14230), or J1850 (PWM or VPW). And being a 2000, your vehicle should definitely be obd2 compliant...

Closing this issue for the moment, but if you confirm it's J1850 and you have hardware that at least claims to support the correct implementation, then there is hope on the software side. Feel free to reopen if this is the case.

DavidCprog commented 2 years ago

Sorry, my mistake, CCD is the name of the one of the communications lines from the DLC conn to the PCM, TCN and modules. The other is SCI. (Small Computer Interface) According to totalcardiagnostics.com 2000 Chrysler uses ISO 9141 (75%) J1850-10.4 (25%) In the year 1994 (my 1994 LHS) Chrysler had 2 different DLC connectors, I guess depending on the model or a change mid year, who knows. Get this: According to one site: 5 types of OBD protocols

  1. SAE J1850 VPW: This OBD2 protocol is used by Ford.
  2. SAE J1850 PWM: Common Motors utilize this protocol.
  3. ISO 9141-2: You will find this protocol on Asian, Chrysler, and European cars.
  4. ISO 14230 KWP2000: This protocol is found in Asian vehicles.
  5. ISO 15765-4/SAE J2480 (CAN): You’ll find this protocol in many new cars as it was invented for cars that were not subjected to OBD2 standards by law. Since it couldn’t satisfy the OBD2 requirements for U.S vehicles that came before 2003. You will find this protocol in many vehicles made after 2008. Confused yet? Sorry
aaeegg commented 1 year ago

@DavidCprog what country was this van sold in?