I'm working on an ECU reprogramming and coding app (iOS, Android, etc.) for a client who is part of the automotive tuning scene. I have been trying out dozens of OBD2 adapters, but most of them fall short in one or the other way. I wonder whether an OBD2 adapter manufacturer is reading here or whether anyone of you have contacts to someone in that area. We would be interested to bundle the tuning software with a white-labelled OBD2 adapter.
If we could just plug an USB adapter, we would not have a problem in the first place, but we absolutely need mobile connectivity.
As long as you only transmit OBD2 commands, even the most shabby ELM327 clone will do. Once you start sending UDS commands, it gets rough. Many adapters don't handle intermediate (NRC78) responses and most will fail sending large ISOTP buffers (4095 bytes in "one go") which are required for boot loader, application, and calibration data transfer.
The requirements are:
- Support all CAN-based protocols
- Mobile connectivity (WiFi and/or BLE5) with a simple serial protocol on top
- Powered through the OBD2 port
- Hardware ID filtering
- Enough memory for buffering a few thousands of CAN bus frames during intermittent loss of connectivity.
- Automatic ISOTP handling up to the full payload size (4095)
- Voltage reading
The STN22xx-based OBDLINK MX+ ticks a large number of these requirements and would almost be perfect, if it was available as a white-label solution.
I'm not sure whether mechanics.stackexchange.com is the proper forum to post such a question, but I figured it might reach the appropriate audience, so bear with me. Do we really need to build our own adapter?