OBDX Development - Developer Tools and Suggestions

[In-Tech]

Hopefully kur4o can chime in with some advice to get the mdi working.

[Tazzi]

Hopefully kur4o can chime in with some advice to get the mdi working.

Click the edit filters button, and turn of the 4x checkbox.

What do you see in the edit filters section? Id assume it will show type, pattern and mask.

If so, do something like:
Pattern = 6C10F1 (Honestly doesnt matter)
Mask = 000000 (Allow ALL though)
Flow = leave blank or 00's
Type = PASS

[In-Tech]

I double checked all of that and played with a bunch of settings, disconnect/reconnect. No worky. Looking back at kur4o's screenshot. It shows him opening up some j2534 xml files. my xml logger folder is empty. I looked through the whole universal patcher folder for some j2534 xml's to no avail.

[Gampy]

You don't need anything xml for the logger.

Just set the protocol and baudrate ... then hit the connect/disconnect button to connect and you should see traffic.
You should not need to set anything else.

Play with it as the only tool connected at first, the PCM should be talking and you should see traffic once connected, if not, disconnect and change baudrate, try again.

Personally I would try J1850PWM for baudrate first ...

As for 1x vs 4x, at this point it doesn't matter, it will talk at 1x until an agreement is made to switch to 4x.

-Enjoy

[In-Tech]

Thanks for your reply Gampy.
I think I have tried every option I could. I must be missing something stupid/simple

[kur4o]

In-tech it is not on your side. As usual anything ford should be tough.
We are missing some configuration on initial connection. I just opened an mdi to elm session just to test if data can be streamed. Upon sending a message from mdi I got error pMsg related, sending data from elm didn`t get logged by mdi.

We need some initial connection log.
If you have forscan we can monitor communication between forscan and mdi and see what we are missing.

[kur4o]

Found the missing piece of configuration

In config box add

NODE_ADDRESS = f1

It have some limitation, not sure how it will be overcome.

With F1 it will log only messages that are targeted to F1 [6c f1 10 27 01] for example.
And will send only with f1 set as target.

Some kind of hardcoded filtering.

Elm seems to log without issue.
In-tech you can test obdlink elm terminal. It is called stnterm.exe for monitoring.
https://www.scantool.net/scantool/downloads/utilities/

[In-Tech]

Hiya kur4o,
Sorry for the delay. I downloaded the stnterm. What would you like me to do with it? I'll try the F1 NODE in a few mins.

[kur4o]

Select elm port and baudrate.

send

atsp1
ath1
atal
atma

It should print all bus traffic

[In-Tech]

I turned key on after typing atma and here is the data

ATSP1
OK

>ath1
ath1
OK

>atal
atal
OK

>atma
atma
41 39 10 01 00 DF
41 39 10 01 00 DF
41 39 10 01 00 DF
81 49 10 10 38 C2
81 49 10 10 38 C2
81 49 10 10 38 C2
41 53 10 3B 2E 42 02 19 E6
41 53 10 3B 2E 42 02 19 E6
41 53 10 3B 2E 42 02 19 E6
41 88 10 14 91
41 88 10 14 91
41 88 10 14 91
41 3B 10 3B 02 03 1B 07
41 3B 10 3B 02 03 1B 07
41 3B 10 3B 02 03 1B 07
41 49 10 26 02 92
41 49 10 26 02 92
41 49 10 26 02 92
81 3B 10 04 40 36
81 3B 10 04 40 36
81 3B 10 04 40 36
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
41 93 10 C6 CB
keeps scrolling this