'04 CTS -- can I get the VIN through a J2190 message?
01-31-2010, 10:32 PM
#1
Launching!
Thread Starter
iTrader: (2)
Join Date: Jan 2003
Location: Downtown Chicago
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
'04 CTS -- can I get the VIN through a J2190 message? And now for my Random Question of the Evening...
So my homebrew scan program can talk to my '04 CTS using the CAN protocol. I can send and receive all the J1979 messages that the car implements.
It sounds like CAN vehicles are supposed to support getting the VIN over Service 9. However, when I poll Service 9 PID 0, the car doesn't seem to support PID 2 (get the VIN). I've tried this same technique on an '07 Buick Enclave, and that particular vehicle does implement the PID. So when I request Service 9, PID 2, I actually get a VIN.
At least on LT1/LS1 J1850-based PCM's, you could send a J2190 command to get the VIN in several parts. Is there a trick for getting the VIN on a newer-model vehicle that doesn't support the Service 9 technique?
Thanks!
So my homebrew scan program can talk to my '04 CTS using the CAN protocol. I can send and receive all the J1979 messages that the car implements.
It sounds like CAN vehicles are supposed to support getting the VIN over Service 9. However, when I poll Service 9 PID 0, the car doesn't seem to support PID 2 (get the VIN). I've tried this same technique on an '07 Buick Enclave, and that particular vehicle does implement the PID. So when I request Service 9, PID 2, I actually get a VIN.
At least on LT1/LS1 J1850-based PCM's, you could send a J2190 command to get the VIN in several parts. Is there a trick for getting the VIN on a newer-model vehicle that doesn't support the Service 9 technique?
Thanks!
02-01-2010, 07:20 AM
#2
And now for my Random Question of the Evening...
So my homebrew scan program can talk to my '04 CTS using the CAN protocol. I can send and receive all the J1979 messages that the car implements.
It sounds like CAN vehicles are supposed to support getting the VIN over Service 9. However, when I poll Service 9 PID 0, the car doesn't seem to support PID 2 (get the VIN). I've tried this same technique on an '07 Buick Enclave, and that particular vehicle does implement the PID. So when I request Service 9, PID 2, I actually get a VIN.
At least on LT1/LS1 J1850-based PCM's, you could send a J2190 command to get the VIN in several parts. Is there a trick for getting the VIN on a newer-model vehicle that doesn't support the Service 9 technique?
Thanks!
So my homebrew scan program can talk to my '04 CTS using the CAN protocol. I can send and receive all the J1979 messages that the car implements.
It sounds like CAN vehicles are supposed to support getting the VIN over Service 9. However, when I poll Service 9 PID 0, the car doesn't seem to support PID 2 (get the VIN). I've tried this same technique on an '07 Buick Enclave, and that particular vehicle does implement the PID. So when I request Service 9, PID 2, I actually get a VIN.
At least on LT1/LS1 J1850-based PCM's, you could send a J2190 command to get the VIN in several parts. Is there a trick for getting the VIN on a newer-model vehicle that doesn't support the Service 9 technique?
Thanks!
03-15-2010, 12:54 PM
#6
Launching!
Thread Starter
iTrader: (2)
Join Date: Jan 2003
Location: Downtown Chicago
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
Random bump...
Just what is Class II? My LDV6U seems to think that the connection to the car is 11-bit CAN (and that seems to be true, since I can send and receive multiple PID's in a single data packet). Are there two data protocols that are active on that communications line?
Thanks
Just what is Class II? My LDV6U seems to think that the connection to the car is 11-bit CAN (and that seems to be true, since I can send and receive multiple PID's in a single data packet). Are there two data protocols that are active on that communications line?
Thanks
Trending Topics
03-17-2010, 01:09 PM
#9
Launching!
Thread Starter
iTrader: (2)
Join Date: Jan 2003
Location: Downtown Chicago
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
Did some digging on Google last night. Here's the technique that works on my CTS:
Send a physically-addressed message to the first ECU using service 0x1A.
Request parameter ID 0x90.
The ECU will return the VIN, split into multiple messages.
Send a physically-addressed message to the first ECU using service 0x1A.
Request parameter ID 0x90.
The ECU will return the VIN, split into multiple messages.
