[C6/C6Z06]RacePak Datalogger Owners: ODBII Interface
#1
Le Mans Master
Thread Starter
[C6/C6Z06]RacePak Datalogger Owners: ODBII Interface
Some weeks ago, there was an announcement about
a new RacePak module that provides an interface enabling
C6 and C6 Z06 owners to log data from the many OEM
sensors that provide input for the ECM.
Do any of the CF members here with a C6 or C6 Z own
RacePak's G2X, G2X Pro or the new IQ3? If so, did
you look into buying the interface module?
As an aside, Pratt and Miller installed a G2X along with
the non-datalogging version of the IQ3 dash into Team
Cadillac's #005 CTS-V back in the summer of '08. Perhaps
the interface was initially developed to support that initiative?
.
a new RacePak module that provides an interface enabling
C6 and C6 Z06 owners to log data from the many OEM
sensors that provide input for the ECM.
Do any of the CF members here with a C6 or C6 Z own
RacePak's G2X, G2X Pro or the new IQ3? If so, did
you look into buying the interface module?
As an aside, Pratt and Miller installed a G2X along with
the non-datalogging version of the IQ3 dash into Team
Cadillac's #005 CTS-V back in the summer of '08. Perhaps
the interface was initially developed to support that initiative?
.
#2
Burning Brakes
Member Since: Apr 2005
Location: Cincinnati Ohio
Posts: 901
Likes: 0
Received 0 Likes
on
0 Posts
I have the black G2X and over the winter am planning on purchasing the OBDII module. That's if our whole financial system doesn't collapse in the mean time.
#3
Le Mans Master
Thread Starter
data that it gives owners access to, especially considering the price and
the absence of installation/configuration overhead.
The appeal of the G2X for me was the scalability of the D/L and the
availability of optional sensors for use on my C4. Over the time I have
owned the unit, I have added several inputs and continue feel that the
value is very good.
However, I am green with envy at how easy and cost-effective it
appears to be for C6 owners to add inputs through tapping into the
onboard ECM/PCM through the ODB interface.
.
#4
Race Director
I have a Traqmate and don't know anything about the G2X, but here's a post by member of Traqmate's systems department:
I put in the bold face above to highlight what I think the biggest problem is with inputs from the OBD port. Like mentioned above, it's okay for emissions, and analyzing engine parameters for tuning, etc.
However, if you want to gather data for analyzing track sessions, it may be too slow. Butt....YMMV!
Bob
I want to clarify that last statement so our readers are not confused. Getting a tach signal on 996 Porsches is way different than general OBD support.
First, Porsche ran a tach signal to the OBD port for a few years but that is completely non-standard and will not work with any other car. In fact, it won't even work with newer (997) Porsches.
Second, the Porsche tach signal on the OBD port is a straight signal. All the other OBD information is an encoded serial data stream. There are 3 different protocols used on the port depending on manufacturer. If it was just a plain old signal, it would be a lot easier. If/when we implement OBD-II suport in the Traqmate product line it will be by decoding and synchronizing the serial data streams so that it will work with all modern (post 1996) cars.
The biggest issue here is that the OBD data is rather slow and has a large and variable delay. This is not a problem if you are checking for emissions (the actual purpose of the OBD-II port) but a real problem if you are trying to match the tach RPM up to a 40Hz data or 30Hz video.
First, Porsche ran a tach signal to the OBD port for a few years but that is completely non-standard and will not work with any other car. In fact, it won't even work with newer (997) Porsches.
Second, the Porsche tach signal on the OBD port is a straight signal. All the other OBD information is an encoded serial data stream. There are 3 different protocols used on the port depending on manufacturer. If it was just a plain old signal, it would be a lot easier. If/when we implement OBD-II suport in the Traqmate product line it will be by decoding and synchronizing the serial data streams so that it will work with all modern (post 1996) cars.
The biggest issue here is that the OBD data is rather slow and has a large and variable delay. This is not a problem if you are checking for emissions (the actual purpose of the OBD-II port) but a real problem if you are trying to match the tach RPM up to a 40Hz data or 30Hz video.
However, if you want to gather data for analyzing track sessions, it may be too slow. Butt....YMMV!
Bob
#5
Le Mans Master
Thread Starter
My vote is that there is no issue with latency on the latest platform.
The C6 uses the GM LAN protocol which supports three different
buses: Low, Mid and High Speed.
Low speed is said to be for operator controlled functions with 100-200
msec requirements. 33.33 kbps normal mode, 83.33 kbps in programming
mode.
High speed is said to be for Real Time Data.
Mid speed is reportedly not in use at this time.
.
The C6 uses the GM LAN protocol which supports three different
buses: Low, Mid and High Speed.
Low speed is said to be for operator controlled functions with 100-200
msec requirements. 33.33 kbps normal mode, 83.33 kbps in programming
mode.
High speed is said to be for Real Time Data.
Mid speed is reportedly not in use at this time.
.
#6
Burning Brakes
Member Since: Apr 2005
Location: Cincinnati Ohio
Posts: 901
Likes: 0
Received 0 Likes
on
0 Posts
My vote is that there is no issue with latency on the latest platform.
The C6 uses the GM LAN protocol which supports three different
buses: Low, Mid and High Speed.
Low speed is said to be for operator controlled functions with 100-200
msec requirements. 33.33 kbps normal mode, 83.33 kbps in programming
mode.
High speed is said to be for Real Time Data.
Mid speed is reportedly not in use at this time.
.
The C6 uses the GM LAN protocol which supports three different
buses: Low, Mid and High Speed.
Low speed is said to be for operator controlled functions with 100-200
msec requirements. 33.33 kbps normal mode, 83.33 kbps in programming
mode.
High speed is said to be for Real Time Data.
Mid speed is reportedly not in use at this time.
.
#7
Race Director
As I mentioned in my other post, I don't (didn't) know anything about the Racepak stuff, but last night I did some searching.
I could not find anybody that sold the OBDII module, and initially couldn't even find any information about any such module.
After reading about the IQ3 and G2X units, I was quite impressed, but I still couldn't find anything about an OBDII interface.
Finally I came across this announcement dated July 31, 2008 in the Racepak forum:
You then measure from the OBDII port to where your G2X or IQ3 is mounted and order something called a Vnet extension cable to hook the module to your data-logger unit. It sounds like the quickest and easiest way to get a bunch of inputs into your data-logger, and I'd definitely consider it if I didn't already have a Traqmate.
With the Traqmate the sensor unit does your G-loads and GPS functions (speed and track map) and that info feeds into their very nice Traqview software to develop the segments on the track map. All additional sensors must be individually hooked up and fed into the sensor unit, and you can only input the RPM, 2 digital, and 4 analog signals. So far I have only hooked up RPM and throttle pedal position, and I think I'm only interested in one or two more (mainly brakes - either ON/OFF into a digital input, or maybe an analog input from the brake pedal position sensor). I had to find a wire from each of those sensors, tap into it with a splice connector, run the wire to the Traqmate sensor unit, then set it up in the software. Not too bad, but the Racepak OBDII interface sounds like it trumps other data-logger sensor connections hands down.
So.....I haven't used the Racepak OBDII, but if I didn't already have a data-logger, I'd sure be looking at their IQ3 or G2X with the OBDII module.
Bob
I could not find anybody that sold the OBDII module, and initially couldn't even find any information about any such module.
After reading about the IQ3 and G2X units, I was quite impressed, but I still couldn't find anything about an OBDII interface.
Finally I came across this announcement dated July 31, 2008 in the Racepak forum:
Racepak announces the release of a Vnet module capable of interfacing with 2006 to present C6 Corvette output. What this means is the ability to input the following data into the IQ3 (or G2X / G2X Pro):
1. Engine RPM
2. Throttle Position
3. Throttle Pedal Position
4. Oil Temperature
5. Water Temperature
6. Transmission Temperature
7. Intake Temperature
8. Battery Volts
9. Wheel RPM (all four wheels)
10. Yaw
11. Torque
12. Horsepower
13. Brake Pedal Position
14. Gear Position
The cost of this module is $499.00.
As can be seen by the above list, the extensive amount of data available quickly turns an IQ3 into a complete data system, with connection and installation requiring very little time.
After that announcement there were a couple other posts containing questions about the module, and it sounds like it's basically a plug you attach to the OBDII port and it has a short pigtail of wires.1. Engine RPM
2. Throttle Position
3. Throttle Pedal Position
4. Oil Temperature
5. Water Temperature
6. Transmission Temperature
7. Intake Temperature
8. Battery Volts
9. Wheel RPM (all four wheels)
10. Yaw
11. Torque
12. Horsepower
13. Brake Pedal Position
14. Gear Position
The cost of this module is $499.00.
As can be seen by the above list, the extensive amount of data available quickly turns an IQ3 into a complete data system, with connection and installation requiring very little time.
You then measure from the OBDII port to where your G2X or IQ3 is mounted and order something called a Vnet extension cable to hook the module to your data-logger unit. It sounds like the quickest and easiest way to get a bunch of inputs into your data-logger, and I'd definitely consider it if I didn't already have a Traqmate.
With the Traqmate the sensor unit does your G-loads and GPS functions (speed and track map) and that info feeds into their very nice Traqview software to develop the segments on the track map. All additional sensors must be individually hooked up and fed into the sensor unit, and you can only input the RPM, 2 digital, and 4 analog signals. So far I have only hooked up RPM and throttle pedal position, and I think I'm only interested in one or two more (mainly brakes - either ON/OFF into a digital input, or maybe an analog input from the brake pedal position sensor). I had to find a wire from each of those sensors, tap into it with a splice connector, run the wire to the Traqmate sensor unit, then set it up in the software. Not too bad, but the Racepak OBDII interface sounds like it trumps other data-logger sensor connections hands down.
So.....I haven't used the Racepak OBDII, but if I didn't already have a data-logger, I'd sure be looking at their IQ3 or G2X with the OBDII module.
Bob
#8
Le Mans Master
Member Since: Feb 2000
Location: Bedford NH
Posts: 5,708
Likes: 0
Received 1 Like
on
1 Post
Cruise-In II Veteran
It is my understanding that you will need more than the $499 device, you will need the data logger and GPS as well. I have been bugging every data acq company at the PRI show to do this for years and they all said the data rate was insuffcient (apparently up to now with the 06 and up). Then again, Pi, CDS, Motec et all said for years that removeable RAM and GPS were of no use either. If you can wait until December, I will quiz the Racepak guys and get a demo at PRI. In fact, I will take an action item to call them (or we should all call them!) between now and then to ask them to bring this specific unit to PRI.
#9
Le Mans Master
Thread Starter
Here is a PDF about the C6 OBD interface from RacePak
Looks like it contains similar information, plus a part number
(#230-VM-EFIC6) and a contact person for further details
(pr aht racepak.com.) The fellow I've turned to with my G2X
questions in the past has been Tim Anderson (tim aht racepak.com.)
The blue end connects to the VNet harness leading to the datalogger,
just like the cables for my discrete sensors. The other end must plug
into the diagnostic receptacle on the C6.
RacePak's VNet cabling made hooking up my discrete sensors easy
enough, but this module takes ease of installation to a new level. At
$499, it delivers 14 inputs for what just a few of my external sensors
cost.
.
Looks like it contains similar information, plus a part number
(#230-VM-EFIC6) and a contact person for further details
(pr aht racepak.com.) The fellow I've turned to with my G2X
questions in the past has been Tim Anderson (tim aht racepak.com.)
The blue end connects to the VNet harness leading to the datalogger,
just like the cables for my discrete sensors. The other end must plug
into the diagnostic receptacle on the C6.
RacePak's VNet cabling made hooking up my discrete sensors easy
enough, but this module takes ease of installation to a new level. At
$499, it delivers 14 inputs for what just a few of my external sensors
cost.
.
#10
Burning Brakes
Member Since: Apr 2005
Location: Cincinnati Ohio
Posts: 901
Likes: 0
Received 0 Likes
on
0 Posts
#11
Melting Slicks
Race Technologies just released their CAN-Bus based OBD add-on too
Latest from Traqmate:
Latest from Traqmate:
This will definitely be included in future products (NOT IMMINENT!!). As for a plug-in module for existing Traqmates, no promises at this time.
#12
Instructor
It is odd that oil pressure is missing from the Racepak ODB interface. I have one that I am planning on installing this winter.
Does anybody have any ideas on how to add oil pressure to the data?
Thx,
Bob
Does anybody have any ideas on how to add oil pressure to the data?
Thx,
Bob