More updates!
I had a developer identify a unique issue where disabling the OBDX's auto formatting for CAN was causing the CAN frames to send as 29bit instead of 11bit as desired.
This really only affects individuals which were needing to handle every single last CAN frame individually with zero auto formatting which is not very common and is why this one has snuck past us!
This fix will roll out in the next OBDX firmware updates.
Next on our list (finally), remote J2534 programming.
I have been itching to get back to this project, since there has been a lot of requests for this over the years.
There are various options out there for sharing a USB over the internet or streaming CAN data over the internet, both options have quite strict latency requirements to work.
Where J2534 over the web differs, is the command/request is transferred over the internet, rather then trying to stream the USB data, what this means is:
1) Less strict latency requirements, since the actual communication to the tool is done at the client side directly and not passing USB data over the web.
2) USB and wireless can be used since the host application is not needing to explicitly connect to the tool.
3) A client can use a smartphone instead of a PC.
4) Allowing both local or even international programming (International would take a long time for flashes!!)
The main aim here is to have a client application as both a PC and android app and eventually implement iOS (This requires more attention being iOS is so particular with everything).
Majority of the work has already been implemented, it is just a matter of stress testing the API to identify when a server should auto scale to handle higher traffic.
If interested in testing this out, now is the time to contact! Currently I am testing between computers locally, internationally and also while using a VPN to give various different circumstances, but will be good to get live user feedback
