OBDX Development - Developer Tools and Suggestions

[In-Tech]

Looks like we are onto a winner here. Intech, what do you have in the way of J2534 tools which supports PWM?

Yay
I have a ford VCM that I have never used, One of your original XPro VT's(not sure that works on Ford, only tested on GM) I have a tactrix that doesn't have FEPS, GM MDI, GM vxdiag nano, AVT 838/852 and probably a few other things. I am in uncharted Ford territory here. My KESS garbage is extremely slow to read and write the EecV but it seems to get the job done. And of course the OBDLink SX.

[Tazzi]

Looks like we are onto a winner here. Intech, what do you have in the way of J2534 tools which supports PWM?

Yay
I have a ford VCM that I have never used, One of your original XPro VT's(not sure that works on Ford, only tested on GM) I have a tactrix that doesn't have FEPS, GM MDI, GM vxdiag nano, AVT 838/852 and probably a few other things. I am in uncharted Ford territory here. My KESS garbage is extremely slow to read and write the EecV but it seems to get the job done. And of course the OBDLink SX.

Is KESS using PWM also??

Ok, we can use the GM MDI since that works with PWM. Ill throw something together for unlocking, and can try send a few other commands.
Might thry 27 03 and see if your EECV responds.

[In-Tech]

I'm really interested in kur4o's MDI setup for passive logging and maybe bidirectional traffic. I haven't researched how to set it up yet. It appears my AVT-838 can do all the FEPS and PWM too. The only reason I even lean that way is the 838 is serial and I have an incredible serial sniffer a bud did back in the 90's. I will need some guidance on how to progress, sorry to be a pain to anyone. I do want to help

Pretty awesome you have the seed/key worked out. I'm glad the info was helpful.

I didn't look through my KESS logs yet. I figured it was useless since it takes so long. A read is almost 30 minutes.

Of course have the Hpt interface as well as EfiLive, doubtfull either do a straight pass through, I dunno.

[Tazzi]

I'm really interested in kur4o's MDI setup for passive logging and maybe bidirectional traffic. I haven't researched how to set it up yet. It appears my AVT-838 can do all the FEPS and PWM too. The only reason I even lean that way is the 838 is serial and I have an incredible serial sniffer a bud did back in the 90's. I will need some guidance on how to progress, sorry to be a pain to anyone. I do want to help

Pretty awesome you have the seed/key worked out. I'm glad the info was helpful.

I didn't look through my KESS logs yet. I figured it was useless since it takes so long. A read is almost 30 minutes.

Of course have the Hpt interface as well as EfiLive, doubtfull either do a straight pass through, I dunno.

Seeing what all the tools send for reading and writing does help. It means an alternative method can be made for anyone that wants to create.

My main task is just getting highspeed PWM going, which... from what I can tell... we are SO close.

If I can see how its requesting each section of memory, Im sure I can through together a quick loop to cycle through each of the addresses.

I haven't tried Kuros tool for logging before, I would assume you can select the protocol, then set the mask to 0 which should allow all messages to come through freely.

[In-Tech]

I think it was in the early 90's that Texas introduced a peripheral change allowed on the bus. It was a simple xor feature at its' infancy, it could be many things depending. Later they used an embedded asic to handle higher things like sha, AES and a bunch of other crap. I am not sure anyone ever beat Pierre's PGP. Anhoosit, we are just logging traffic on the bus. Hpt tried to throw some trickery with their interface, booo, lol. We just trapped the bus. The new GM stuff I bet is similar to internal asic commands. I had to do the impossible and dump the asic way back in the day. Got sued for a few BILLION dolllars(not gm) and had to play in federal court for over a year.
Anyhoosit. Tazzi has the seed/key for the EecV handled. It's old crapola but still fun to play.

Thank you for the reply Tazzi. I hope kur4o will chime in with advice. I'd like to play with almost unlimited logging with the mdi and his software.

[In-Tech]

I made a bench harness for a later ford computer I was doing. I'll dig it out and the 'puter' in the next few days and see if I can trap the high speed calls.

[kur4o]

Some basic instruction how to log with a j-tool.

I marked the important settings in red. Where is yellow line you can type custom commands
6c fe f0 3f for example and use enter to send it.

On destination box you can select

buffered mode= print only last messages on screen, previous are saved in buffer[preferred settings is off for low bus traffic and on for very high bus traffic->Raw CAN for example]
File= you can save all traffic to file while logging
screen= print traffic on screen

I tried to make a disassembly of the bin but no luck so far. Can`t figure cpu type in IDA or byte order.

[Tazzi]

I tried to make a disassembly of the bin but no luck so far. Can`t figure cpu type in IDA or byte order.

What I found online suggested its intel 8056 or along those lines. Theres some free online decompilers made by the community as well.

[kur4o]

https://rusefi.com/forum/viewtopic.php?t=429
https://eectuning.org/forums/viewtopic.php?t=21286

Found 2 threads the are worth looking. In depth info for early ford stuff and lots of documents.
Now it is time to figure why IDA don`t like this cpu code.

[In-Tech]

kur4o, Is there a particular environment better than another. I have winXP, 7, and 10. The win10 is used for gm SPS when I have to. Does the MDI need a particular version of the "wrapper"? I am up to date on the win10 'puter, not sure what I would have to do on the others. Sorry for boring questions. Your software looks way cool. Thanks for the screenshots Mine is an original MDI(not a clone) and not an MDI2.