Hey folks, I was curious about if the OBD-II feature on the ECU+ interfere's with the ability to reflash the ECU with it installed?

And is there any possibility to arrange to get an evaluation unit?

I've been looking at some of the piggyback options more closely now that its possible for an End-user to reflash his ECU, and I like the logging the ECU+ has to offer.

 

I just purchased a AEM EMS with the built in UEGO, but am going to hold up on the install because I have the ECU+ and also recieved the ECUFLASH cable. To answer your question all you would have to do is remove a jumper on the mainboard in order to free the OBD port since the ECU+ when installed with the jumper is always connected. The datalogging capabilities are definitely the perfect match for the ecu flash.

 

I had to disconnect the ECU+ before I was able to download the map via EcuFlash. I did the wire mod via ECU+ instructions but that didn't seem to work, but I haven't gotten a chance to remove the jumper on the board to see.

 

The OBD-II connection is just one wire. As others mentioned, I have a jumper on the circuit board to disconnect it, or you can just insert a switch or spade lug within that wire from the ECU+ to the stock ECU.

Tom

 

Tom could you be more specific? Would that be pin #22 "OBDII Data In?

 

Yep, that's it. The black wire to the ECU+.

Tom

 

Thank You.

 

Thats exactly what I was thinking about doing, running a switch to make it easier to bypass when needed..

The ECU+ definitely seems like a really good match for the ECUFlash since it offers alot of features that are great, but without being able to flash your ECU with baseline configuration, was difficult for me to justify.. Now that you do all this great stuff with the ECU, this bad boy is a perfect addition.. It has some of the best logging and data collection tools that I've seen, I spent alot of time amassing tools or writing code for other stuff to work together, and its all there on this unit.

But like I said, I like experimenting and working with new tools, and I figured now was a good time to test it out.

 

This is exactly why I wish I wouldn't have gotten rid of mine. I need the data logging feature badly now =/

 

could someone please elaborate? so the switch would go somewhere in the "black wire to the ecu+"?... does it just need to break continuity in the wire, or does it need to switch it to another wire? I need to get this done soon.

 

You can put a switch in the line that goes to the OBD-II data line, or you can do what I did, which was put a switch and header on the jumper inside the unit, this way I can flip open my glove box door, reach behind, and flip the switch.. This was done intentionally but can easily be replaced with a remote switch.

I really love the ECU+, the logging features have made my life so much easier.. If it we could figure out the load algorithm used by the ECU, technically there could be MAP Tracing (of the ECU) It works so well in conjunction with the ECUFlash reflashing tool that I recommend it to everyone.

The only issue I occasionally get, which is similar to any piggyback that alters the crank angle sensor to shift timing, is an occasional P0300, but fortunately I only alter timing while I tune..

 

so all I need to do is break continuity to that line correct?
BTW: I totally agree, teamed with ecuflash, ecu+ can be a tuner's dream, it already is really cool, all that needs to happen is for Tom to reprogram the unit to also act as a conduite for flashing. (calc load, etc)

 

Yep, I made a few suggestions like that to Tom, but he has his plate full at the moment so I don't want to bombard him with anything for awhile..

But yes, you need to break continuity so it doesnt initialize the OBD-II interface and you can use the port.. Remember that it has to be done in the line that goes to the ECU+ or the jumper inside, and not the line on the jump harness (or neither the interface or ECU+ will read OBD-II)

Map tracing and reading load would be something I find most interesting.. I'm not sure what kind of chip the ECU+ uses for interfacing with the OBD-II diagnostics, but the ECUFlash cable is able to get a really high sample rate compared to the regular RS232 based ones..

 

It's not an OBD-II chip per se, but another dedicated microcontroller. I needed to support the diagnostics of the 1st generation DSMs as well as OBD-II, so I did my own circuitry and software for OBD-II. The only real limitation I have is that the microcontroller has a limited (2k bytes!) amount of code space, so I can't do any really sophisticated stuff there.

Tom

 

so... don't break the line on the harness ey? ....uh... oops I think. I cut the "black wire" that was referenced some many posts upward. I snipped the little black line that goes into the plug that goes into the ecu+. I didnt snip one of the large black wires in the harness... is that okay? ...I hate electronics.