OBDX Development - Developer Tools and Suggestions

[Tazzi]

I will be attempting to make an all in one installer for OBDX today, just to make the installation process easier on a PC since it is starting to look a bit messy on the downloads page. If possible, Ill get it ask which cable to install and it will install the driver plus J2534/DPDU with it.

Thankyou Antus for pointing out the potential confusion for our customers!


Another thing to work on today is PCMHammer to add some better debug logging so that its easier to see what the incoming RX frames are. This should help trouble shoot for those "unexpected frame received" messages in pcmhammer to narrow down exactly what frames its seen.

Then... back to the app development! Have a little video that Im exited to share with you all!
I have recently been using the app when with clients, I always get a kick out of their reaction each time (You know who you are!) when they see me pull out the phone and start programming away

[antus]

Fantastic, thanks for those it will be a great help.

[Tazzi]

Ok so we now read voltage, and also output "Network RX: " for all received network frames which are added to the input queue.

Just do the pull request now so these small additions can be released in the next version.

Code: Select all

[12:36:18:236]  PCM Hammer (14/11/2022, 12:36 PM)
... trimmed down size here... 
[12:36:19:537]  Voltage is: 13.51V
[12:36:19:546]  XPro: 41 02 01 01 BA
[12:36:19:547]  OBD Protocol Set to VPW
[12:36:19:624]  XPro: 43 03 00 F0 01 C8
[12:36:19:624]  Filter set and enabled
[12:36:19:628]  XPro: 41 02 02 01 B9
[12:36:19:628]  Network enabled
[12:36:19:629]  Device Successfully Initialized and Ready
[12:36:25:840]  XPro: 20 01 00 DE
[12:36:25:843]  TX: 6C 10 F0 3C 01
[12:36:25:855]  Network RX: 6C F0 10 7C 01 00 36 47 31 59 4B
[12:36:25:865]  XPro: 20 01 00 DE
[12:36:25:868]  TX: 6C 10 F0 3C 02
[12:36:25:879]  Network RX: 6C F0 10 7C 02 34 32 46 58 33 4C
[12:36:25:889]  XPro: 20 01 00 DE
[12:36:25:892]  TX: 6C 10 F0 3C 03
[12:36:25:905]  Network RX: 6C F0 10 7C 03 39 32 39 36 32 30
[12:36:25:909]  VIN: 6G1YK42FX3L929620
[12:36:25:921]  XPro: 20 01 00 DE
[12:36:25:924]  TX: 6C 10 F0 3C 0A
[12:36:25:941]  Network RX: 6C F0 10 7C 0A 00 BA 8A 32
[12:36:25:944]  OS ID: 12225074
[12:36:25:951]  Hardware Type: P01_P59
[12:36:25:960]  XPro: 20 01 00 DE
[12:36:25:963]  TX: 6C 10 F0 3C 08
[12:36:25:977]  Network RX: 6C F0 10 7C 08 05 7E 2F 18
[12:36:25:980]  Calibration ID: 92155672
[12:36:25:990]  XPro: 20 01 00 DE
[12:36:25:994]  TX: 6C 10 F0 3C 04
[12:36:26:002]  Network RX: 6C F0 10 7C 04 00 8F 3A 22
[12:36:26:005]  Hardware ID: 9386530
[12:36:26:017]  XPro: 20 01 00 DE
[12:36:26:020]  TX: 6C 10 F0 3C 05
[12:36:26:027]  Network RX: 6C F0 10 7C 05 32 45 42 33
[12:36:26:035]  XPro: 20 01 00 DE
[12:36:26:037]  TX: 6C 10 F0 3C 06
[12:36:26:052]  Network RX: 6C F0 10 7C 06 42 58 39 44
[12:36:26:060]  XPro: 20 01 00 DE
[12:36:26:062]  TX: 6C 10 F0 3C 07
[12:36:26:076]  Network RX: 6C F0 10 7C 07 32 32 31 33
[12:36:26:083]  Serial Number: 2EB3BX9D2213
[12:36:26:095]  XPro: 20 01 00 DE
[12:36:26:097]  TX: 6C 10 F0 3C 14
[12:36:26:113]  Network RX: 6C F0 10 7C 14 44 53 4B 57
[12:36:26:116]  Broad Cast Code: DSKW
[12:36:26:126]  XPro: 20 01 00 DE
[12:36:26:128]  TX: 6C 10 F0 3C A0
[12:36:26:136]  Network RX: 6C F0 10 7C A0 00
[12:36:26:139]  MEC: 0

[Tazzi]

Woohoo! Successful day!
PCMHammer pull request done and tested.

OBDX Pro has the "all in one" installer added to the website. Basically its just running each installer one after the other after selecting which scantool you want to install.

AND we have finally received our EV Certificate so all the software can be signed! Fingers crossed it just works first go without a massive headache, should help with any false positives people might be getting so far.

[In-Tech]

Hiya Tazzi, great work brutha
I haven't followed along well enough and I hate to barge into the thread but I am sure it will come up some time. I bought the original OBDx pro vt when it first came out a couple years ago. Is there a newer version I should buy now?
Thanks for all your hard work

[Tazzi]

Hiya Tazzi, great work brutha
I haven't followed along well enough and I hate to barge into the thread but I am sure it will come up some time. I bought the original OBDx pro vt when it first came out a couple years ago. Is there a newer version I should buy now?
Thanks for all your hard work

The OBDX GT is the latest tool that we released. This will work for canbus vehicles which basically covers 99% of GM.

Might even eventually work with FDCAN vehicles if I can get my hands on a FDCAN based ECU.

Latest prototypes has a slight mishap from the manufacture... everyone is going to have to see the monstrosity of wiring Im doing to get it up and running. Looks like the E38 mess I did when swapping over live memory chips

[In-Tech]

Hiya Tazzi,
Thanks for the reply.

I will buy whatever is needed to help you guys in your endeavor. From across the pond, let me know anything I can do to help

[Tazzi]

Hiya Tazzi,
Thanks for the reply.

I will buy whatever is needed to help you guys in your endeavor. From across the pond, let me know anything I can do to help

I wouldn't bother buying something for the sake of buying, but do appreciate the support

At the moment its more about trying to add as much software support as human possible so there is a cheap professional solution into diagnostics and programming.
We have a unit on the way to the ALDLDroid developer to add support with the OBDX GT. I believe he is going to look at using the ELM commands and basically allow all frames to come through so it will then work happily with ADX files.

Have had ALOT of questions regarding adding support for Forscan.. so... they will be next on the list once we have MSCAN support added. Technically we support the baud rate, but we need to switch pins to 3/11 to be on the correct pins.

The more developers I can get to use the tool, the better.
We even have our local Tuning company PCMTec which does the Fords, although I won't approach them until we have the FEPs and MSCAN added. Even though they don't specifically need those, its best just having everything incase they do.

Theres quite a few J2534 software's out there for tuning these days, so might be a matter of grabbing those and demonstrating them too, or find anyone which has J2534 software to test with!

[antus]

You might be able to get pcmtech working just on the j2534 driver

[rolls]

Just sent you an email Tazzi. I have a few ideas to toss around that you might be interested in. We would also love to trial your cable. I can't believe I didn't come across this earlier, I would have reached out over a year ago!

The two requests are:

Can you compile a 64bit J2534 DLL? 32bit is very limiting memory wise and we would love to have a 64bit driver DLL so we can compile PCMTEC as a 64 bit program. Tactrix have been dragging their feet despite many requests to build a 64 bit DLL.

Would you be interested in making a sample android application that can talk to the cable via USB with a Java wrapper for a J2534 interface? USB is preferable as its more performant and simpler, however direct USB access may be an issue with the latest version of android (I haven't developed for Android in a long time). I'm sure you can see where we are heading with this. Xamarin would allow us to cross compile our flashing code for android, then use a java/c wrapper library to access your cable via USB to allow flashing. This would allow us to build a very simple slave flashing application, we have huge demand for this (eg 1000+ units).