OBDX Development - Developer Tools and Suggestions

Programs / Tools / Scripts
User avatar
Posts: 3109
Joined: Thu May 17, 2012 8:53 pm
Location: WA

Re: OBDX Development - Developer Tools and Suggestions

Postby Tazzi » Tue Jan 24, 2023 7:38 pm

MudDuck514 wrote:Hi all,

So, does this mean you are planning an Android Diagnostic App?

Mike


OBDX will have its own iOS/Android phone application to perform diagnostics.

The purpose of the template is to have something that I can use for my own company (Envyous Customs), something for OBDX to use, and also any other developers looking to make a move into the mobile market. :thumbup:

In the short time that Pete and I have been creating these tools, theres already been a huge interest in breaking free of PC applications by multiple devs. This should give everyone a working example to move forward with 8-)
Your Local Aussie Reverse Engineer
Site:www.envyouscustoms.com
Mob:+61406 140 726
Image

Posts: 258
Joined: Wed Jul 05, 2017 8:30 am
Location: North TX, USA

Re: OBDX Development - Developer Tools and Suggestions

Postby MudDuck514 » Wed Jan 25, 2023 7:53 am

Thanks Tazzi,

Awesome!
Looking forward to its release. (Whenever that may be, lol)

Mike

User avatar
Posts: 3109
Joined: Thu May 17, 2012 8:53 pm
Location: WA

Re: OBDX Development - Developer Tools and Suggestions

Postby Tazzi » Wed Jan 25, 2023 1:34 pm

Priority is for the developers at the moment since we have had alot of requests from GM and Ford devs.

Breaking free of PC applications has actually been a lot harder then most people realize for J2534 developers, since there is not a single J2534 tool on the planet which is designed to also work with smartphones or any non-PC based system.
Your Local Aussie Reverse Engineer
Site:www.envyouscustoms.com
Mob:+61406 140 726
Image

Posts: 149
Joined: Sat Apr 25, 2020 6:09 am

Re: OBDX Development - Developer Tools and Suggestions

Postby Gatecrasher » Thu Jan 26, 2023 5:15 am

Would it be that much harder to make something that accepts 3rd party XML (or similar) config files, so we could add our own module diagnostics? I've tried a few different open source projects for stuff like this, but they're either too manufacturer specific, or just too crude. Bi-directional diagnostics might be asking a bit much, but I don't feel like it should be this hard to find a cheap or free tool to read error codes from a BCM for example.

Torque on Android is really close, but it's too focused on generic OBD2 interaction.

User avatar
Posts: 3109
Joined: Thu May 17, 2012 8:53 pm
Location: WA

Re: OBDX Development - Developer Tools and Suggestions

Postby Tazzi » Fri Jan 27, 2023 9:23 am

Gatecrasher wrote:Would it be that much harder to make something that accepts 3rd party XML (or similar) config files, so we could add our own module diagnostics? I've tried a few different open source projects for stuff like this, but they're either too manufacturer specific, or just too crude. Bi-directional diagnostics might be asking a bit much, but I don't feel like it should be this hard to find a cheap or free tool to read error codes from a BCM for example.

Torque on Android is really close, but it's too focused on generic OBD2 interaction.


Torque would be the closest option, but its more of a blank slate that requires putting in all the details.
When I move onto OBDXplorer on the smartphones, Ill look at accepting user defined inputs.

The reason there are not any solutions is due to most modules only support diagnostics using DPID routine, which requires a bit more thought to setup correctly as each frame is loaded with multiple PIDs. Its not hard per say, just outside the realm of what any free apps like torque do.
Your Local Aussie Reverse Engineer
Site:www.envyouscustoms.com
Mob:+61406 140 726
Image

User avatar
Posts: 3109
Joined: Thu May 17, 2012 8:53 pm
Location: WA

Re: OBDX Development - Developer Tools and Suggestions

Postby Tazzi » Fri Jan 27, 2023 12:37 pm

New update for the J2534 API will be rolling out for the GT shortly.

This addresses some optimizations for speed when performing large read/write routines. The J2534 logging will be disabled by default since it does add a good 20-30seconds being on the main thread currently, plus handling byte->string conversions constantly is a huge resource consumer.

There are some further optimizations I will look into, specifically targeting writing to the serial port stream directly to avoid double handling and rearranging buffers before writing to the port. This may only save a few milliseconds for each iteration, but over the course of several thousands of iterations, it should cut down another 10-20seconds depending on the length of the read or write session. The constant creation of buffers would also be triggering the GC to run more often then needed so we will want to try avoid that also.

Theres a few other little tweaks that can be tested over time. I am currently waiting on a Mustang ecu to arrive so I can test more thoroughly.
Your Local Aussie Reverse Engineer
Site:www.envyouscustoms.com
Mob:+61406 140 726
Image

Posts: 38
Joined: Mon Oct 21, 2019 4:58 am

Re: OBDX Development - Developer Tools and Suggestions

Postby kostia111 » Sat Jan 28, 2023 3:09 am

Tazzi wrote:Priority is for the developers at the moment since we have had alot of requests from GM and Ford devs.

Breaking free of PC applications has actually been a lot harder then most people realize for J2534 developers, since there is not a single J2534 tool on the planet which is designed to also work with smartphones or any non-PC based system.

https://scanmatik.ru/catalog/scanmatik- ... pro-basic/

Posts: 563
Joined: Mon Mar 09, 2020 4:35 pm
Location: California

Re: OBDX Development - Developer Tools and Suggestions

Postby In-Tech » Sat Jan 28, 2023 5:38 am

kostia111 wrote:
Tazzi wrote:Priority is for the developers at the moment since we have had alot of requests from GM and Ford devs.

Breaking free of PC applications has actually been a lot harder then most people realize for J2534 developers, since there is not a single J2534 tool on the planet which is designed to also work with smartphones or any non-PC based system.

https://scanmatik.ru/catalog/scanmatik- ... pro-basic/
English?

Posts: 266
Joined: Thu Dec 20, 2012 5:28 pm
Location: Melbourne

Re: OBDX Development - Developer Tools and Suggestions

Postby Chuff » Sat Jan 28, 2023 8:31 am

In-Tech wrote:
kostia111 wrote:
Tazzi wrote:Priority is for the developers at the moment since we have had alot of requests from GM and Ford devs.

Breaking free of PC applications has actually been a lot harder then most people realize for J2534 developers, since there is not a single J2534 tool on the planet which is designed to also work with smartphones or any non-PC based system.

https://scanmatik.ru/catalog/scanmatik- ... pro-basic/
English?



Will this help?

https://mhhauto.com/Thread-Scanmatik-2- ... id=1603869
˙ʎɐqǝ ɟɟo pɹɐoqʎǝʞ ǝsǝuıɥɔ ɐ ƃuıʎnq ɹoɟ ʇɥƃıɹ ǝɯ sǝʌɹǝs

Posts: 563
Joined: Mon Mar 09, 2020 4:35 pm
Location: California

Re: OBDX Development - Developer Tools and Suggestions

Postby In-Tech » Sat Jan 28, 2023 11:03 am

Thank You,
It appears vague to me. What is this devices main purpose?

PreviousNext

Return to Tools

Who is online

Users browsing this forum: Google [Bot] and 5 guests