HI All,

Been playing with the 6GT3 CAN bus and would be interested in seeing if anyone can offer any insight. The 6GT3 CAN bus messages are all 6 or 8 bytes (for the payload).

and have the following CAN bus message ids - format is decimal / hex:

• 416 / 0x1a0
• 680 / 0x2a8
• 640 / 0x280
• 649 / 0x289
• 1952 / 0x7a0
• 1248 / 0x4e0
• 1272 / 0x4f8
• 1296 / 0x510
• 1312 / 0x520
• 1185 / 0x4a1
• 1376 / 0x560

Does anyone know any of the bit-field mappings for these message id's?

I would expect to see temp, RPM, perhaps wheel speed (each wheel), and who knows what else.

Thanks

Ray

 

I think that 1A0 is Brake_1. 280 is Engine_1. Do you know if all the identifiers are 11 bits?

 

They are.

Do you know what the field representations of those 2 labels are?

I logged a bunch of data and right now am trying to identify the coolant temp and the RPM values. I may create some test files and inject some data into the CAN bus and see what the instrument panel does.

Thanks

Ray

 

I don't. It's difficult to get any of the info that isn't part of the standard itself. It must be out there, or folks like GIAC wouldn't exist. I'll keep asking around.

 

Thanks,

If I figure stuff out, I will publish it.

Ray

 

This is the info I got from Racelogic for my Video Vbox to connect the datalogger to the CAN bus:

Signals available: Steering Direction, RPM, Wheel Speeds, Park Switch, Reverse Switch, Steering Angle,
Vehicle Speed, Lights, Ignition Switch, Brake Pedal Position, Throttle Position Sensor.


I

 

Thanks,

What I am looking for is the actual messages and bitfields that support this information.

Ray

 

AFAIK Porsche doesn't publish that info. And I've sought it out. (Other automakers do publish this info or make it available say via ETI (Equipment and Tools Institutue).

I used Vehicle Spy to monitor the CAN bus traffic. With practice one can identify which CAN messages pertain to by matching the changes of say RPM with changes in the data fields of specific CAN messages.

It helped that I could with Vehicle Spy create message ID filters to reject all but the CAN frame or frames I was interested in. CAN traffic can be horrifically busy so this was a blessing to be able to just collect one or two specific CAN frames for later analysis and study/

For instance I was interested in door lock status so I locked/unlocked the various doors and from the changing bits in a specific CAN message mapped which bit represented which door lock.

For data fields that represent say RPMs the numbers might represent RPMS times 4. Thus 1000 RPMs would appear in the CAN message data field as 0x0FA0 (hex).

Odometer can be tenths or 100ths of a kilometer. One has to capture the bus traffic while driving a specific distance and then work out the resolution.

And so on for other CAN messages.

 

Yep,

I used a Raspberry PI with a CAN interface, got Wireshark running as a logging tool, have written some Python code to look at different fields over time...

Now trying to analyze what I have. The 6GT3 does not have a lot on the CAN bus, and right now the car is apart for the winter....

Ray

 

Has anyone determined the message ID and data format for RPM?
-Jon

 

Not yet,

I have a couple of options, but it will take a bit for me to test them. To many other projects...

Ray

 

Have you looked at the various Porsche damos files that are floating around the net? They contain absolute addressing info, data conversion functions, etc. Everything is in German so it will help to have the Bosch Automotive German/English dictionary too.

 

I thought the DAMOS files contained the data and maps used by the ECU for running the engine and related systems. Can you provide a reference for a sample DAMOS file?

 

I would love to see one of these. I guess the CAN bus data/PID could be defined in them...

Ray

 

Merry Christmas