It’s understandable that you’re seeking clarity on connecting your tracking device, which outputs RS232 data, to both OBD2 displays and Arduino platforms. Let’s address the core issue and chart a path forward.
You’ve correctly identified that your tracking device communicates using RS232 protocol with UART. You’ve also successfully verified the data output via Serial Monitor, confirming the source data is accurate. This is a crucial first step – knowing your data source is reliable.
The primary challenge lies in interfacing this RS232 output with your intended devices: an off-the-shelf OBD2 data display and an Arduino Uno. The technical support from your supplier rightly pointed out the RS232 to TTL level incompatibility with Arduino. Standard Arduino boards, including the Uno, operate with TTL (Transistor-Transistor Logic) voltage levels for their UART communication, whereas RS232 uses different voltage levels. Directly connecting an RS232 output to an Arduino’s UART pins can lead to signal issues and potentially damage the Arduino.
To successfully use the RS232 data with your Arduino, you’ll need to bridge this voltage level difference. This typically involves using an RS232 to TTL converter module. These modules handle the voltage translation, allowing the RS232 signal to be correctly interpreted by the Arduino’s UART.
Once you have the RS232 data correctly converted to TTL and feeding into your Arduino, you can then process this data as needed for your Arduino display. This foundational step is essential before considering the complexities of OBD2.
Regarding your goal of displaying data on an OBD2 display, it’s important to understand that OBD2 is a specific vehicle diagnostic protocol. While your tracking device outputs data via RS232, it doesn’t inherently mean this data is formatted or compatible with the OBD2 standard. OBD2 displays are designed to read specific parameters (PIDs) defined by the OBD2 protocol from a vehicle’s diagnostic port.
If your tracking device is intended to simulate or provide OBD2 data, it would need to be programmed to output data in the correct OBD2 format, beyond just the RS232 physical layer. Simply having RS232 output does not automatically make it OBD2 compatible.
Therefore, focusing on getting the RS232 data successfully into your Arduino via a TTL converter is the most logical next step. This will allow you to work with the data and understand its format. After establishing reliable data flow to the Arduino, you can then investigate further into how this data might be used, if at all, in the context of OBD2 – either by potentially formatting it to mimic OBD2 data or by using the Arduino as an intermediary to process and display relevant information in a way that is useful alongside or instead of OBD2 data.
Achieving reliable RS232 data output from your Arduino will indeed lay a solid groundwork. From there, you can then explore the possibilities of integrating with OBD2 systems, keeping in mind the distinct nature of RS232 data and the specific OBD2 protocol requirements.
