Unable to connect with car

Ask questions relating specifically to the PicoDiagnostics NVH equipment and software here.
User avatar
VASTech
OneWave
OneWave
Posts: 34
Joined: Sat Oct 10, 2015 6:58 am
Location: Southeastern Europe

Re: Unable to connect with car

Post by VASTech »

Hello Kev,
tests have been done on a 2001 VW Golf 1.9L ALH diesel engine, 2002 New Beetle 1.6L AYD.
I`m sure it is a Pico software issue because Putty and other software are able to get pid`s from those ECU`s. In my logs i see that Pico does not even able to send ATZ command to interface...
Still hope we will "crack it" :D
Thank`s!

User avatar
VASTech
OneWave
OneWave
Posts: 34
Joined: Sat Oct 10, 2015 6:58 am
Location: Southeastern Europe

Re: Unable to connect with car

Post by VASTech »

OK!
Figured out why not show any AT commands in trace log...
Forget to tick ""Enable OBD Logging"
Anyway attached new log different system, same problem...
Attachments
trace.xml
(2.46 MiB) Downloaded 13 times

Steve Smith
Pico Staff Member
Pico Staff Member
Posts: 903
Joined: Sun Aug 25, 2013 7:22 am

Re: Unable to connect with car

Post by Steve Smith »

Thank you again for the feedback.

I can see at 17 seconds in the video the Baud Rate is set at 9600 using Putty and at 3:11 the Baud Rate is set at 38400 using ScanMaster.

I have checked and can confirm these baud rates are supported with NVH and so I am at a loss once again.

I will try to pursue a VAG vehicle of the era you mention but I feel I need to use your ELM 2.2 lead to keep variables to a minimum

I will add our findings to the bug report and ask the software engineers to review the video's and trace files

Onward and upwards, take care......Steve

User avatar
VASTech
OneWave
OneWave
Posts: 34
Joined: Sat Oct 10, 2015 6:58 am
Location: Southeastern Europe

Re: Unable to connect with car

Post by VASTech »

Hello Steve, Thank`s for reply.
I want to tell you again, that this problem is not from the interface, because as I say before I try to connect with different interfaces but no positive result.
I managed to sniff the com port while Pico was communicating with ECU with some serial port monitor. Attached the logs. You can open the file with the software from here https://cdn.eltima.com/download/serial_port_monitor.exe - free trial for 14 days. Your software engineers can get something from that.
https://drive.google.com/file/d/1ZIkguG ... tB2Y4/view ~208Mb
Thank you for implication! BR.

A preview of that log file:
Attachments
Log.png

User avatar
VASTech
OneWave
OneWave
Posts: 34
Joined: Sat Oct 10, 2015 6:58 am
Location: Southeastern Europe

Re: Unable to connect with car

Post by VASTech »

Hello!
It`s a success! :D ... but not on EDC15 VAG ECU`s ! :(
I was able to connect to a EDC16U1 VAG ECU on K-Line protocol. I think the problem is in establish comm with EDC15 ECU`s, something is different this ECU`s. Steve if you can get a VAG EDC15V ECU I am 100% sure you will encounter my problem regardless of interface type you will use. So it is not the hardware interface problem it is something with these ECU`s K-Line communication. Hope you will find the time and resources to investigate this problem and solve this. Thank You! BR
Attachments
trace.xml
(81.8 KiB) Downloaded 8 times
Success EDC16U1.mp4
(817.66 KiB) Downloaded 9 times

User avatar
PicoKev
TwoWaves
TwoWaves
Posts: 175
Joined: Thu Apr 05, 2012 9:16 am

Re: Unable to connect with car

Post by PicoKev »

Hi VASTech,
I am in no way a VAG specialist so I do not know where to start looking for an EDC15V but happy to see what I can find for Steve. If you can give me some idea of what age and model range have them fitted I will see what I can find for him.

Kev.

User avatar
VASTech
OneWave
OneWave
Posts: 34
Joined: Sat Oct 10, 2015 6:58 am
Location: Southeastern Europe

Re: Unable to connect with car

Post by VASTech »

Hey Kev.
EDC15 are fitted in many diesel vehicles including VAG Golf MK4, Polo, Bora, Passat from 1998-2005.
Thank You!

josegumby
OneWave
OneWave
Posts: 31
Joined: Sun Aug 27, 2017 3:46 am

Re: Unable to connect with car

Post by josegumby »

Hello,

I seem to be having similar issues as VAStech.

I purchased the MongoosePro/ISOCAN2 interface (as it seems highly recommended on these forums) solely for the purpose of using with NVH, but it only works with some cars for me. Most cars, it does not work for.

So far, I've found it to work with a 2001 Honda Civic, and a 2010 Hyundai Sante-Fe. But it does NOT work with a 2010 Honda Element, 2001 Ford F-150, or 2000 Ford Focus.

I had an old cheapie $40 obdlink/sx cable and that one DOES work with the 2010 Honda Element, Ford F-150, and 2000 Ford Focus (but not the element or hyundai). However, NEITHER cable seems to work with the 2010 Honda Pilot.

Attached is a table I put together based on my findings, along with the protocols used by the PCM (as best as I can tell based on the wiring diagrams I have available). Hopefully this helps.

I /will/ say that ALL of these cars do work with the Mongoose PRO ISO/CAN2 cable using the drew technologies J2534 toolbox. I can read and clear engine codes as well as receive basic data PIDs such as RPM, etc.

I've also attached pictures of the cables I'm using as well so you know exactly what I'm using. I have also sent a support request with Drew technologies as well just to make sure it's not a protocol mismatch or protocol support issue. But again, using the drew technologies software (J2534 toolsbox), I am able to see data PIDs on ALL the vehicles mentioned above and in the table attached. So I don't expect it to be a protocol or hardware mismatch, since the mongoose is able to read the data PIDs using their software.

Thanks,
Curt
Attachments
obdlinksx usb cable.PNG
mongoosepro isocan2.PNG
OBD2 cables.PNG

User avatar
VASTech
OneWave
OneWave
Posts: 34
Joined: Sat Oct 10, 2015 6:58 am
Location: Southeastern Europe

Re: Unable to connect with car

Post by VASTech »

Hello Steve,
Are you able to download that log from google drive?

Steve Smith
Pico Staff Member
Pico Staff Member
Posts: 903
Joined: Sun Aug 25, 2013 7:22 am

Re: Unable to connect with car

Post by Steve Smith »

Hello and thank you for the posts

VASTech, thank you for all the additional information. I have all the files and the Google Drive file too.

They have all been attached to an existing bug report surrounding ELM with Motorcycles as I want to keep the ELM concerns in one place

Moving onto Curt, thank you for taking the time out to list the leads used and the symptoms as they appear using each lead.

For the software team to diagnose the concerns I will need the trace files from these vehicles.

Lets take the 2010 Honda Element, this fails to function with Mongoose but works OK with Red OBDLink/SX
Could you attempt to connect to this vehicle using NVH Via Mongoose (with OBD Logging active)

Wait for the NVH to return a "connection fail" error message and then close the software. Locate the trace file and send to support@picotech.com (ref this post) if you would rather not post here.

Please feel free to post here is you choose.

I am very interested to hear that the DrewTech J2534 ToolBox will connect to the 2010 Honda Element via Mongoose ISO CAN II, this will provide additional data to the software team

Below I have included a Power Point on 2 useful pieces of information that would be really helpful if you could acquire them through the J2534 Toolbox
https://drive.google.com/file/d/1W-BE3m ... sp=sharing

If possible could you obtain the data from slides 9 & 15 in the PPP and include with your Trace file?

Thank you all again and we will resolve these concerns, I am just not sure when.

Take care......Steve

Post Reply