OBDX Development - Developer Tools and Suggestions
Posted: Fri Mar 11, 2022 12:22 pm
This first post will be updated with links and information related to OBDX Pro tools and development.
OBDX Pro VT J2534 API Installer: https://obdxpro.com/downloads/
OBDX Pro VT DPDU API Installer: https://obdxpro.com/downloads/
Features and tools being worked on currently include:
• OBDX Pro VC and GT Firmware Finalization
• OBDX Pro GT J2534 API - CANBus and ALDL
• OBDX Pro DVI protocol example projects in Visual Studio
• OBDX Pro VC and GT Developers Reference Manuals
********************************************************************************************************************************
********************************************************************************************************************************
****************Original Post Below****************
Before OBDX was even an idea, it was loose wires on a breadboard, trying to get Petes hardware design to work with a custom command set I built some time ago, to say the first prototype was a bit sketchy.. is an understatement
Fast forward a couple years and we now have a few new products on the horizon to release which include:
• OBDX VC - This is the USB only (in an ELM style case) edition with VPW only, this is designed to be as cheap as humanly possibly.
• OBDX VX - This is also USB only (in an ELM style case), which will be ALDL, VPW and High Speed CAN
• OBDX GT - This is the big brother to the VT, in our normal VT style case with USB,BLE,Classic Bluetooth and WIFI which will support ALDL, VPW, HSCAN and GMLAN.
With the above said, from day 1, I have had the mind set of having useful developer options and commands inside the tools firmware, basically everything I personally would have wanted when either making software or when reverse engineering cars or tool responses. I did not want just a remake of current tools, I wanted them to allow devs to have almost direct control and access to the communication line without any restrictions.
The most recent additions into the firmware have been these two items:
1) A timer to set send off custom messages. (Useful for tester present messages)
2) Auto responder, which will automatically send off a specific message when it receives a specific message
Both of which are supported using the ELM command protocol also (just use a simple serial terminal to send string commands).
Those two are something I use on a daily basis for my own R&D. They have made reverse engineering a hell of alot faster and easier, and also made flashing modules safer since the scantool continues to send the tester present even if a software was to lockup for whatever reason.
From a scantool, is there any features anyone would want implemented? I am all for making these the most versatile scantools on the planet.
Things I have thought might be useful to implement:
• Battery voltage monitoring - auto send a message when voltage drops below certain threshold
• Eeprom area - for custom user data or software settings.
• Sleep mode - detect no communication from software after X time and go into low power mode?
OBDX Pro VT J2534 API Installer: https://obdxpro.com/downloads/
OBDX Pro VT DPDU API Installer: https://obdxpro.com/downloads/
Features and tools being worked on currently include:
• OBDX Pro VC and GT Firmware Finalization
• OBDX Pro GT J2534 API - CANBus and ALDL
• OBDX Pro DVI protocol example projects in Visual Studio
• OBDX Pro VC and GT Developers Reference Manuals
********************************************************************************************************************************
********************************************************************************************************************************
****************Original Post Below****************
Before OBDX was even an idea, it was loose wires on a breadboard, trying to get Petes hardware design to work with a custom command set I built some time ago, to say the first prototype was a bit sketchy.. is an understatement
Fast forward a couple years and we now have a few new products on the horizon to release which include:
• OBDX VC - This is the USB only (in an ELM style case) edition with VPW only, this is designed to be as cheap as humanly possibly.
• OBDX VX - This is also USB only (in an ELM style case), which will be ALDL, VPW and High Speed CAN
• OBDX GT - This is the big brother to the VT, in our normal VT style case with USB,BLE,Classic Bluetooth and WIFI which will support ALDL, VPW, HSCAN and GMLAN.
With the above said, from day 1, I have had the mind set of having useful developer options and commands inside the tools firmware, basically everything I personally would have wanted when either making software or when reverse engineering cars or tool responses. I did not want just a remake of current tools, I wanted them to allow devs to have almost direct control and access to the communication line without any restrictions.
The most recent additions into the firmware have been these two items:
1) A timer to set send off custom messages. (Useful for tester present messages)
2) Auto responder, which will automatically send off a specific message when it receives a specific message
Both of which are supported using the ELM command protocol also (just use a simple serial terminal to send string commands).
Those two are something I use on a daily basis for my own R&D. They have made reverse engineering a hell of alot faster and easier, and also made flashing modules safer since the scantool continues to send the tester present even if a software was to lockup for whatever reason.
From a scantool, is there any features anyone would want implemented? I am all for making these the most versatile scantools on the planet.
Things I have thought might be useful to implement:
• Battery voltage monitoring - auto send a message when voltage drops below certain threshold
• Eeprom area - for custom user data or software settings.
• Sleep mode - detect no communication from software after X time and go into low power mode?