OBDII emulator...

[GoatOfRafin]

Hi!

I decided to start an electronics pet project of my own, which in short will connect to the Apexi PFC via DataLogIt and will respond to OBDII queries. I know it seems a bit ambitious but I am quite confident I am going to make it. I have found the serial protocol of the DataLogIt so I know how to query it in order to get RPM, speed, etc...

The reason I am doing this is that I want to interface the PFC with my Informeter TOUCH in order to have all the information I need in one place and get rid of the Commander. However, I understand that this is going to be a very valuable tool for OBD inspection as well so I will keep you posted.

For now I have ordered a netduino board and two RS-232 shields which will be used in order to interface the netduino with the DataLogit and an ELM327 COM-to-OBDII interface which will act as the emulator.

[v3bahumut]

Make a rig will let my PFC pass OBD emission inspection and I'll be your friend forever.

[Cap]

You need to Talk to this Guy..
http://www.mr2spyder.net/spyderweb/i...2-kevin-beane/

and here is another place you can find him..
http://spyderchat.com/forums/member.php?39-Kevin-Beane

He knows more than any Human on the Communication Protocol of the PFC.. He Wrote Co-Pilot Software..

You can get him at either Site..

Cap

[zzt231 gr]

Very interesting!!

Subscribed!!

[GoatOfRafin]

Guyz, my boards have finally arrived and I am very excited! I 've already done a small test program which echoes COM port signals and lights up the on-board LED and it is functioning very well. I will now go to buy some OBDII adapters so that I can hook them up and start playing...

I was also thinking of "enhancing" the PFC with some features like the CoPilot does, but without having to have a PC inside the car. Here are my first thoughts:

- Knock light which will be activated according to a predefined RPM vs. knock curve
- Shift light
- Ignition retardation according to knock signal and user rules
- A/F ratio auto tuning
- Transfer of PFC data to OBDII port
- Integration with WiFi in order to make iPhone and other mobile clients for commanding the PFC

So, what do you guys think about all these? Would you use such features? I will surely do!

[Jannelle]

Originally Posted by GoatOfRafin

Integration with WiFi in order to make iPhone and other mobile clients for commanding the PFC

So my commander will stop laying around on the passenger side carpet

Very interesting project, very ambitious.
A PFC that can tell real OBD2 codes, sounds awesome..

Subscribed

[2KGTS]

Originally Posted by jannelle

a pfc that can tell real obd2 codes, sounds awesome..

Subscribed

+1

[zzt231 gr]

Originally Posted by GoatOfRafin

- Knock light which will be activated according to a predefined RPM vs. knock curve
- Shift light
- Ignition retardation according to knock signal and user rules
- A/F ratio auto tuning
- Transfer of PFC data to OBDII port
- Integration with WiFi in order to make iPhone and other mobile clients for commanding the PFC

So, what do you guys think about all these? Would you use such features? I will surely do!
__________________

You are kidding???These are awesome news!!

[Punkers7465]

Originally Posted by GoatOfRafin

- Knock light which will be activated according to a predefined RPM vs. knock curve
- Ignition retardation according to knock signal and user rules

So, what do you guys think about all these? Would you use such features? I will surely do!

These two features, especially auto ign retard, would be extremely nice to have.

Keep up the excellent work!

[vegeta4ss]

goatofrafin,

would you mind sharing which protocol you found that the pfc works with? I too am working on something in my spare time but I am mainly doing it for intense data logging and maybe data visualization.

I found the protocol mentioned on a rx-7 forum about the pfc but I do not know if all units are the same so I find it hard to trust it is right. Having a second opinion helps me not structure my libraries all wrong. The guy in that thread provided a great amount of info about the message structure but didn't mention the protocol type/id number. Knowing that would at least give me a way to establish boundaries.

I have a uno2 with a proto shield . I am just learning how to assemble/test circuits using it. Makes me want to go back to school and get an EE degree.

Good luck with your project.

[GoatOfRafin]

Hi!

Yes, my info is from the rx7 site you mentioned. I have not yet tested all of the info as of yet. I currently have just asked the PFC for its version number and get correct results. By the way, have you made any progress with your project? As I said before, I have managed to request the PFC for its version number and get it back from my PC but the same code does not work for my netduino. Specifically, I get no answer from the PFC. I have tried making my PC and netduino communicate and they succeed. So now, my PC can talk to the PFC, my PC can talk to the netduino but the netduino cannot talk to the PFC. Any guesses maybe?

PS: What do you mean by protocol type/id number? Not the connection settings, I suppose...

[GoatOfRafin]

I 've been giving some (night) time at this project and I have imported some data structures of the PFC to my code and made a test with my PC in order to see if the interpreted data is correct and... voila!

http://www.youtube.com/watch?v=lG3afKkaEAg

All sensor and external data are now monitored! Now it's time for some algorithms that will warn me for knock with respect to a knock-per-rpm curve. Stay tuned!

[zzt231 gr]

Μπραβο ρε Γιωργο!!!

Βravo!!!!If you need any electronics hardware help,let me know!Keep up!

[2KGTS]

Is there any capability in the PFC to identify engine conditions and log the equivalent of stock ECU "CEL codes" or would that be something required on the coding end with a lot of intelligence added? My assumption is it would require a lot of code and proper, technical algorithms. But thought I'd ask...

[GoatOfRafin]

Yes, you are correct, it has to be done with coding. But this is something very interesting that I haven't thought of! Thanks for sharing...

[2KGTS]

Cool. I'd love to find a reason to be able to sell my '00 ECU that hits lift at 5700. I'm holding on to it for troubleshooting purposes.

That being said, I suppose that I'd only want it around for common CEL codes. Yes, it is a good train of thought...

[GoatOfRafin]

What kind of diagnostics do you guys think would be beneficial to be implemented?

[Type-GS-R-Turbo]

What protocols are you planning on implementing? KWP2000 is probably the easiest to get off the ground since you only need a UART and a very short init sequence, but if you're going for stock compatibility, you'll likely want to do ISO 9141-2. At least I'm pretty sure that's what the RX-7 uses. Have you gotten you hands on any of the OBD II Standards docs?

As an alternative, you could bridge to the FTDI chip via a VNC1L on the OBD II Simulator seen here and feed it the data you'd like it to emulate:

http://www.youtube.com/watch?v=zZsH4O9kZJ0

The protocol is available, just ask

[GoatOfRafin]

Are you the guy at that video? If so, I really want to talk to you! My plan is to implement the ISO 9141-2 first (unless you are the guy at the video and have all these figured out) and then may go on to the others as well...