Author |
Message |
gbrandt Samba Member
Joined: April 04, 2006 Posts: 578 Location: Calgary
|
Posted: Wed Feb 26, 2020 7:10 pm Post subject: Scangauge not connecting to 1.9 TDI |
|
|
Hi,
I have an ASV 1.9 TDI installed in my Vanagon (T3). I have a scangauge that simply will not connect to the ECU. Actually I have two, one much newer than the other and they both do not connect.
I have a VCDS (Vag-com) that connects perfectly well.
My used pins on the OBDII connector are 4, 7, 15 and 16
I have tried forcing KWP protocols with no success. Any idea on what may be going on?
Thanks,
Gregor _________________ 'Lucky' our 1987 Red Westy, ASV 1.9 TDI ~130HP, Peloquin differential (had a GW 2.3 that we loved, but it died, we drove it hard!)
We've driven in 49 countries and 5 continents to date
Canada to Argentina and back, 2015 to 2017.
Canada to Europe and back (including Turkey, Morocco and Iceland), 2017 to 2019
Mexico 2022-2023
https://www.instagram.com/live.travel.play/
http://livetravelplay.ca |
|
Back to top |
|
|
AndyBees Samba Member
Joined: January 31, 2008 Posts: 2329 Location: Southeast Kentucky
|
Posted: Wed Feb 26, 2020 8:01 pm Post subject: Re: Scangauge not connecting to 1.9 TDI |
|
|
For the OBD port to the ALH engine in my 84 Vanagon, I used the following pins.
1. -Positive with ignition ON
4. -Ground
5. -Ground
6. -CAN data Hi Bus to T32a/27 in cluster
7. -Data link connector to T32/25 in the cluster (K-wire)
14. -CAN data Lo Bus to T32a/28 in cluster
16. -Always hot (12volts) from Fuse S12
I do realize your engine is the ASV and obviously the two are different.
Notice there are two hot pins, (1 and 16). I suspect that one of them provides power to the Scan Gauge (pin 16) for operational purposes and the other (pin 1) signals SG that systems are ON. Keep in mind, your VCDS is powered by your computer. (pure speculation and others will likely chime-in)
I have VCDS and Scan Gauge and they both work just fine with my set-up which includes the Cluster. Occasionally, I have to push one of the buttons on my SG to wake it up. But, that happens sometimes to the SG in my 03 Jetta TDI. _________________ '84 Vanagon Tin-top, ALH TDI. 1989 Tin-top
1983 Air-cool, 225k miles, 180k miles mine. Seven trips to Alaska from 1986 thru 2003. |
|
Back to top |
|
|
gbrandt Samba Member
Joined: April 04, 2006 Posts: 578 Location: Calgary
|
Posted: Wed Feb 26, 2020 9:46 pm Post subject: Re: Scangauge not connecting to 1.9 TDI |
|
|
AndyBees wrote: |
For the OBD port to the ALH engine in my 84 Vanagon, I used the following pins.
1. -Positive with ignition ON
4. -Ground
5. -Ground
6. -CAN data Hi Bus to T32a/27 in cluster
7. -Data link connector to T32/25 in the cluster (K-wire)
14. -CAN data Lo Bus to T32a/28 in cluster
16. -Always hot (12volts) from Fuse S12
I do realize your engine is the ASV and obviously the two are different.
Notice there are two hot pins, (1 and 16). I suspect that one of them provides power to the Scan Gauge (pin 16) for operational purposes and the other (pin 1) signals SG that systems are ON. Keep in mind, your VCDS is powered by your computer. (pure speculation and others will likely chime-in)
I have VCDS and Scan Gauge and they both work just fine with my set-up which includes the Cluster. Occasionally, I have to push one of the buttons on my SG to wake it up. But, that happens sometimes to the SG in my 03 Jetta TDI. |
Hmm, I do get power to the scangauge, but will try adding power to pin 1 and ground to pin 5. I have no can bus items, just the engine ecu, so I don't think that the can lines matter
Thanks. _________________ 'Lucky' our 1987 Red Westy, ASV 1.9 TDI ~130HP, Peloquin differential (had a GW 2.3 that we loved, but it died, we drove it hard!)
We've driven in 49 countries and 5 continents to date
Canada to Argentina and back, 2015 to 2017.
Canada to Europe and back (including Turkey, Morocco and Iceland), 2017 to 2019
Mexico 2022-2023
https://www.instagram.com/live.travel.play/
http://livetravelplay.ca |
|
Back to top |
|
|
gbrandt Samba Member
Joined: April 04, 2006 Posts: 578 Location: Calgary
|
Posted: Sun Oct 23, 2022 6:48 pm Post subject: Re: Scangauge not connecting to 1.9 TDI |
|
|
The Euro ASV does not support full OBD-II, although the plug is the same, the communications are not. Europe was not forced to full OBD until after my engine (2002) _________________ 'Lucky' our 1987 Red Westy, ASV 1.9 TDI ~130HP, Peloquin differential (had a GW 2.3 that we loved, but it died, we drove it hard!)
We've driven in 49 countries and 5 continents to date
Canada to Argentina and back, 2015 to 2017.
Canada to Europe and back (including Turkey, Morocco and Iceland), 2017 to 2019
Mexico 2022-2023
https://www.instagram.com/live.travel.play/
http://livetravelplay.ca |
|
Back to top |
|
|
MarkWard Samba Member
Joined: February 09, 2005 Posts: 17118 Location: Retired South Florida
|
Posted: Mon Oct 24, 2022 5:37 am Post subject: Re: Scangauge not connecting to 1.9 TDI |
|
|
Edit: Just realized your are asking about a Scan Gauge, not VCDS software. So, the info below is of no help. I would attempt to connect VCDS to your ODB 2 port. You will need this access at some point. The Scan Gauge is handy, but not all the tool you’d need to actually diagnose a problem. I have a permanent Scan Gauge for monitoring the engine, but always carry my laptop the Ross Tech genuine dongle and VCDS software. The reason is if I have a problem, I’m the one that will need to diagnose it. I will leave the info below for someone in the future that might come across this. My bet is, VCDS won’t connect either.
This has worked once for me. VCDS uses label files for each ECU configuration. Part of the connection is the software looks at the ECU part number and then to the inventory of label files it has stored.
Find the label files folder and locate a file similar to your ECU and engine. Make a copy of the label file and give it the name of your ECU part number and save it with the other files. Then open the software and try to connect.
If this works, save another copy of the label file in my documents or the desktop. The reason is when VCDS updates it over writes all the label file folder.
Edit: I was thinking that my description was not 100% correct. I’d need to have my laptop running to give exact steps. The idea is generally correct. The label file might include the engine designation too. So, if your engine is similar to an ALH, find that label file copy it and rename it using your engine data and ECU number. This will make more sense when you find and open the label file folder. You likely need to edit the copy of the label file. You can open a file using Notepad. Edit the file and save the new file using the naming convention of the other files. It was a few years ago when I did this for another owner. Thanks for understanding. _________________ ☮️ |
|
Back to top |
|
|
|