I have been running a UTEC for years, all has gone well. I am really on the fence and am considering going Haltech. Passing emissions is realisticaly my #1 priority. Been able to do that with my current setup for 3 years. My question for curent Haltech USERS is what is your experiance with OBDII tests and CEL's? I believe if it's not broken, dont F with it, however there's something to be said about progress.
Thanks for ON TOPIC response! (results are not a reflection about quality of Haltech!!!)
Sean

 

I had problems with CEL's while running haltech, po300, 1278,1279,1281,1282,(I think )and a couple of other codes dealing with cam sensor position. The random misfire code probably had more to do with my cam selection than with the Haltech. I could clear the codes but they would always come back after 3 start-run-warm up-stop cycles. I think rcdash had solved some/maybe all problems with CEL's while running Haltech. For me It was cheaper/less time consuming to have UpRev in Austin reprogram my factory cpu with Osiris.

 

The UTEC is not at control off load, so has an easier time keeping the stock ECU happy. The Haltech is in control of fuel, timing, and cams 100% of the time. If the stock ECU makes a change and it doesn't see a sensor respond, it will throw a code. Very hard to avoid with any of the stand alones unless you spend forever trying to get your stock ECU tune to match the Haltech tune. I have similar AFR targets and it is still not perfect.

I don't run with CELs because I have them disabled with Osiris. When it's time to pass emissions, I re-enable them and follow a procedure to get me through the OBD testing processing, where a gap exists that allows sensors to be ready but not have thrown codes yet (you can pass with pending status). The key is to clear the codes, follow the driving patterns specified in the FSM for setting sensors to ready, and then not restart the car again until you are ready to drive the car to the testing station. Having an OBD scanner (Osiris/Cipher unfortunately does NOT report sensor ready status) is helpful for determining what pending codes you have.

I have passed OBD testing twice this way with the Haltech - once with cats, once with test pipes (luckily no visual inspection this time around).

EDIT: It is important to identify how many "not ready" sensor codes your state allows to pass emissions. NC allows only 1. I had to leave that for my evap sensor status as it would never go to "ready" even with all DTC enabled. Not sure why... If I could've gotten EVAP to go ready, I would've disabled the O2 sensor codes and it would've made life much easier. If you can pass with 2 sensors not ready, then it's easy.

 

Thanks guys, so far pretty interesting info. As far as dash says, that sounds like launch sequence at Norad. I want to drive my car without so much thought. Again, I think Haltech is a better EMS, but the calibration and prep for this sounds kinda extensive. However I have a stock block so maybe I wouldn't have issues. I'm getting from you guys that there are "procedures" you have to go through for emission....I currently dont have to do any of that. I want true EMS full control but at no price. Is that asking too much?