Rad, that is a great point of clarification needed with the Haltech Pro. Does it keep the OBDII port intact? While the web-page that Josh links to is informative, it just does not explicitly say how the codes are delivered.

I dug into their web-site a little and there was an article about reading codes, but it was OBD-I related and using a bent paperclip. (Ah.. I remember doing that with my FD.) I wasn't able to find any other info in the time I had available.

-Dave

 

The OBDII port on the car no longer functions when you are using the Haltech Pro Plug-in. The codes are delivered/read/obtained by you plugging in a laptop into the USB port on the Haltech ECU.
I will see if my friend who's got this unit in his Evans Tuned AP1 can chime in on this thread. He's a lot more familiar with this unit than I am obviously since he's got it and I don't, although we chat on AIM a lot and I ask him a ton of questions, which is how I know some of these details.

We will actually be at Evans shop this upcoming monday, with JDV not with Evans, getting my exhaust installed, I will try and see if there are any updates on the PS500 piggyback "solution".

Thanks

 

Hey guys,

Being an owner of a Haltech pro plug in I can tell you that you have no ODBII function on this ECU at all. Haltech still monitors all the sensors and when an issue is found will generate a code that from what Jeff Evans told me is the same codes you'd expect from a stock ECU (I believe the CEL light does still work too). However, there's is nothing you can do over the ODBII port. Everything is done via the USB interface through the Haltech software. The rules state that ODB functionality must all be retained which to me means every function including readiness flags must exist and these do not on the Haltech or any plug and play as far as I know.

Steve

 

Also, Jeff said there is absolutely no problem getting a haltech to piggy back and tune on a S2K. In fact his brother in law's been running in this configuration for months now. The problem is still the random CELs (it's thrown every O2 code in the book) which apparently is caused by the stock ECU knowing the car is running (but thinks it's idle since the plug in is controlling everything else) and is confused about the readings from the sensors so it throws codes. It runs just fine but of course it would probably be a bad idea to just keep ignoring CELs whenever they occur thinking it's just "one of those things".

 

Here are photos of an MY00 ECU.

 

Thanks for chiming in Steve.

 

Oh and the haltech ECU is most definitely smaller than the OEM ECU. The OEM ECU won't even fit in the box the haltech ECU came in so I supposed this could definitely be done provided the SEB can clarify the ODB part of the rules.

 

Is there an output on the Haltech that could drive the stock ECU in a way to make it happy such as forcing open loop mode with a high throttle position? I know the eManage Ultimate has a programmable output that could do this. The OBD would still be "functional" depending on what that really means?

Here's an idea to think about...

• Put the Haltech in a stock ECU housing
• Hook up as the primary ECU
• Piggy back in a stock ECU in a way that allows the OBDII to "function"

Of course this could probably be achieved by piggy backing the Haltech in with the appropriate PNP harness mods.

Just throwing this out not necessarily as a solution, but to hopefully spark some other thoughts.

 

Well I talked to Evans today and he said it will fit.

Can someone shoot a email to the SEC and get clarification on what they mean exactly by retaining obd functionallity? Then post up the reply. To me retaining obd fuctionallity means the check engine light will throw a code when something is wrong. For example like they did on Marc's CR when he won nationals all they did was unplug a sensor to make sure the car throw a code and the obd system was working. Who give a shit how we read the code? I dont understand the need to make us (me) jump through hoops when all they are doing is slightly postponing the inevitable. Some form of this type of set-up will happen, it's just a matter of time. Then guess what? Full standalones will be in ST. Which is what they are trying to prevent even though to me flashpro, mega squarts and tuning done by ectune are all full standalones in my book.


Speaking of mega squarts, thats a standalone in the stock ecu casing right? Does their obd2 port work?

 

You don't know how to type?