all those out there with car PCs, anyone hooked up an OBD II monitor yet?

Im looking at the obdII diagnostics part, looks good, but software seems lacking. it shows RPM, speed, throttle, load, fuel, intake temp, basicly everything... but it doesnt appear to do any critical thinking about all that.

such as, acceleration from speed and time, hp from accel and drag and weight. log of speed as you go around a track(compare runs to show faster corner speeds in one lap, or disprove the popo for a ticket) and on and on.

is there anything out there that already does all that? or do I need to find a freind to program it.

I saw one program that only works on subarus, called ecotek or something. it even let you reset the redline to whatever(their wording was valet mode, cant take it over 2500RPM or whatever you choose.), it also let you control timing, A/F ratio ect ect. very very cool.but that was subaru only.

 

Get the New G-TEch... It does all that..

 

Gtech does it through Gforce sensors, and thus subject to error. no error in the cars own data.

 

True, but the cars own sensors were not really designed for accuracy in all cases (take the O2 sensor...it's narrowband, not wideband). OBD-II also doesn't have a whole lot of speed, so as the number of logged sesnors increases, the data rate for each slows to a crawl.

 

Before you buy anything make sure it reads the New CAN protocol.
Controller Area Network. I going for the AutoXray 4000. Read all
codes and has display the tells you what the codes are, and resets
codes.

 

MacGyver is right. The OBD-II system is meant for diagnostics, not for data logging. It's not particularly accurate, and it has a very low data rate. You won't get good, consistent data out of it for the purposes you're talking about.

 

WLD350Z has it hooked up to OB2... Its sic! PM him...

 

Well my roomate bought the G-tech, and it was so sorry he returned right away. He just ordered the OBD-2 interface, and uses it with his palm. It seems pretty useful as far as readings go, although after doing the DYNO he has learned that it's ability to determine performance data is inaccurate, saying his mustang gt has 182 HP. He had to put in all kinds of info too like drag co-eofficient, elevation, weight, baro pressure.. its really a pain in the butt.

As far as tuning goes it has all kinds of readings, that are straight from the computer and seem accurate that if you know how to interperet them can help you tune your car. Its just when it tries to "think" and use this to get that it's all over

FYI, he is regretting buying it as well, and will probably send it back, not to mention the palm he had to buy to get it usable..

Dan

 

Yep, AutoTap is slow once you start tracking and sampling multiple data points. We just got a Consult-II, it is much faster, but it is only for Nissan and is stand alone.

Ares, look at www.autotap.com. I have this and it works ok for $200 (I think there is a cheaper one too). It uses serial connection on your PC. I have it hooked up to a tablet PC.

 

I was actually looking at building a OBD-II reader that will display some information to a Text LCD or a VFD unit.

What kind of information should we be looking at?

 

consult II? wonder if thats similair to what subaru has... their software is seriously incredable. but only for subaru's I think specifily the 2.0 and 2.5L models.

 

Consult-II is a $6000 handheld scanner for Nissan. Its a little more money than the $200 autotap.

I will have both units at ZDayZ if you want to check them out.

 

You can not change anything with ODB II, And the Only Performance change that can be done with the Consult-II is a slight Timing advance.

I have Tested Several ISO based ODB II Systems For the Z, and most have there good and bad points(most more bad than good) As soon as some small Details are worked out (like making some Instructions) I will be releasing an ODB II Add on for the In Z PC.

The New ODB II add on will read, but not log, all the sensors data in the Z. Like Intake Temp, Coolant Temp, MAF in gm/inch, engine Load % , Short and long term Fuel one bank 1 and 2, O2 sensors, Speed, RPMS, and more. It will also Read error codes, tell you what the code means, and allow you to turn off the CEL.

Other Features include measuring 0-60mph times, 1/8 mile times, 1/8 trap speeds, 1/4 miles times and 1/4 trap speeds. It Also has a software based DYNO. You just enter Vehicle Weight, Tire size(like 275), Tire Aspect ratio(like 40), and rim size(like 18), to get HP and Tourq #'s

But this is where the Problem is. On a Dynojet, the Software Dyno was only like 2hp off on a 4th gear run, but when I try a run on the street it reads like 700+hp or in 5th gear 1000+hp. so as soon as I can figure out how to get accurate Dyno readings, then the ODB II add on will be released. But If you want on Now and Don't Care about the above it Retails for $150.

Just PM Me

 

Has anyone tried nProbe from 300Degrees yet? I emailed them to see if it would work with the ECU we have and have not heard back. Here is the link: http://www.300degree.com/electronics/nprobe/

 

cazz that sounds real nice. why no log? just cause, or is there something preventing it from being done?

Id be very interested in it when you get it perfected, hows it hook up?

also, any chance the readout(assuming digital gauges?) are user definable? be kinda cool to create skins for it.

 

Chazz -check your PM

....data logging has been added and there are some better insights into using the dyno method properly.

I have the OBD II solution from Chazz and it is damn cool and fascintating to have the data displayed in real time while cruising around.

 

To get the software to more accurately predict the HP and TQ is to add another field to input the gear ratios and final drive ratio. That might be why the readings are off on the street. IIRC a dynojet is not a load bearing dyno so on the street it will be different.