Car diagnostics have ceased to be the prerogative of expensive service centers with the advent of affordable OBDII scanners and powerful mobile applications. Among the variety of software for Android, the undisputed leader remains Torque Pro, which turns your smartphone into a full-fledged on-board computer. However, a standard set of sensors is often insufficient for an in-depth analysis of the operation of the engine or specific vehicle systems.
This is where custom ones come into the picture. These are commands that the application sends to the vehicle's electronic control unit (ECU), requesting specific data. While basic parameters like speed or engine rpm are read automatically, many hidden metrics such as transmission temperature, real-time boost pressure or throttle angle require manual adjustment. PID (Parameter ID). These are commands that the application sends to the vehicle's electronic control unit (ECU), requesting specific data. While basic parameters like speed or engine rpm are read automatically, many hidden metrics like transmission temperature, real-time boost pressure or throttle angle require manual adjustment.
Adding new IDs can seem like a complicated process, requiring knowledge of programming and CAN bus architecture. In fact, modern versions Torque have greatly simplified this procedure, providing a convenient interface for entering formulas and display configurations. In this article we will analyze in detail the process of integrating new sensors, from the theory of the OBDII protocol to the practical implementation of complex calculations.
Preparing equipment and basic communication setup
Before you start creating custom profiles, you need to make sure the connection between your smartphone and the adapter is stable. The quality of data transmission directly affects the accuracy of the readings of new sensors. To work, you will need an adapter ELM327 version 1.5 or higher, since cheaper Chinese clones version 2.1 often have reduced functionality and do not support advanced commands.
The first step is to pair the device via Bluetooth or Wi-Fi in the Android settings. After that, launch the application Torque Pro and go to the settings menu. Here it is critical to choose the right connection type and communication protocol. If the application cannot automatically detect the protocol, you will have to select it manually from the list of supported standards.
⚠️ Attention: Using low-quality ELM327 adapters can lead to incorrect reading of the PID and even freezing of the vehicle ECU while driving. Always check the stability of the connection in the parking lot before starting your trip.
In the section Settings → OBDII → Adapter make sure that the correct COM port is selected. For Bluetooth adapters, this is usually a fixed port that is assigned by the system when first paired. If you are using a Wi-Fi scanner, you need to register the device's IP address, which by default is most often 192.168.0.10, and the port 35000.
☑️ Checking readiness for setup
Search and verification of the necessary identifiers
The main difficulty when adding new parameters is finding the correct hexadecimal codes for your specific vehicle. The OBDII protocol is standardized only for basic environmental parameters, such as exhaust gas composition or crankshaft speed. All other data, including automatic transmission oil temperature or accelerator pedal position, are proprietary and vary between manufacturers.
There are several sources for obtaining these codes. The most reliable way is to use specialized forums of owners of your car brand, where enthusiasts share data dumps and transcripts. You can also use open PID databases, which are constantly updated by the user community Torque.
- 🔍 Official documentation of the car manufacturer (Service Manual), which often provides tables of ECU memory addresses.
- 🌐 Specialized forums and communities dedicated to chip tuning and diagnostics of specific brands.
- 📂 Databases within the Torque application itself, accessible through the profile loading menu.
- 🛠 PC software such as ScanMaster or FORScan, which can show active PIDs in real time.
When searching for the code, pay attention to the mode of operation (Mode). Most custom sensors operate in Mode 01 (Show current data) mode, but some systems may require access to other modes. The code is usually a sequence of two bytes, for example 22 01 05 for Ford extended data or 01 0C for standard engine speed.
Where can I find PIDs for rare cars?
If there are no ready-made lists on the Internet for your model, you can try the brute force method. In the Torque settings, enable logging of raw data and compare them with the readings of the factory on-board computer when operating conditions change. This is a time-consuming process, but it allows you to identify the correlation between the HEX code and the physical parameter.
Creating a new custom sensor in the interface
Once you have found the required code, you can begin implementing it into the application. The process of creating a new sensor is intuitive, but requires care when entering mathematical formulas. Go to the main menu of the application and select User Settings → Manage additional PIDs.
In the list that opens, click the add new element button. You will be asked to fill out several fields, each of which plays an important role in the correct display of information. The "Long Name" field is intended for the full name of the sensor, which will be visible in a detailed report, and the "Short Name" is for compact display on dashboard widgets.
Particular attention should be paid to the "OBD Command" field. The command is entered here in hex format. For standard requests, just enter the code, for example 010C. If an extended request with a specific data byte is required, the format may vary depending on the ECU manufacturer. Sometimes it is necessary to use a prefix 22 to access specific memory blocks.
| Parameter name | Field description | Example value |
|---|---|---|
| Long Name | Full description of the sensor | Automatic transmission oil temperature |
| Short Name | Short name for the widget | ATF Temp |
| OBD Command | HEX code of the request command | 22 F1 5E |
| Min/Max Value | Range of acceptable values | 0 - 150 |
| Unit Type | Unit of measurement | °C (Degrees Celsius) |
Don't forget to specify the units of measurement and range of values. This is necessary for correct drawing of graphs and triggering of an alarm when parameters go beyond acceptable limits. The application allows you to select standard units from a list or specify your own notations.
When entering HEX commands, do not use spaces between bytes unless the application explicitly requires it. Most adapters handle continuous strings of characters correctly, reducing the risk of syntax errors.
Mathematical formulas and data scaling
Raw data received from the ECU rarely corresponds to the final value that we are used to seeing on the dashboard. Most often, the electronics unit returns an integer value that must be converted using a linear equation. In Torque Pro for this, a powerful system of formulas is used that supports variables A and B.
The variable A denotes the high byte of the response, and B the low byte. If the sensor returns a one-byte value, only the variable Ais used. The classic formula for converting data into a familiar form looks like (A*256)+B for two-byte values or simply A for single-byte values. However, for temperature sensors, subtraction of the offset constant is often required.
For example, for many VAG cars, the oil temperature formula looks like (A*256)+B-40. Here -40 is the offset correction adopted in the ISO standard. For boost pressure sensors, you may need to divide by a factor, for example (A*256)+B)/100to get the bar value from the original millibars.
⚠️ Warning: An error in the scaling formula may result in completely incorrect data being displayed. Always check the obtained values with known standards or readings of other devices before trusting a new sensor.
In the "Equation" field, enter your formula using standard mathematical operators. The application supports complex logic, including conditional statements, which allows you to create smart sensors that change the calculation logic depending on the range of incoming data. This is especially useful for the nonlinear characteristics of some sensors.
Proper data scaling (formula) is more important than the HEX code itself. Even a valid query will return a meaningless number without correct mathematical conversion to units.
Visualization and customization of the dashboard
After saving a new PID, it automatically appears in the list of available sensors, but for ease of use it must be displayed. Torque Pro allows you to flexibly customize the appearance of the dashboard by adding dials, graphs and text fields. Go to real-time mode and click on any existing widget.
In the sensor selection menu that appears, scroll to the end of the list. Your user PIDs will be in a separate category or in a general list labeled "User Defined". Select the sensor you created, and the widget will update, displaying new data in real time.
You can customize the color display for a more visual representation of the data. In the settings of a specific widget, set threshold values, upon reaching which the color of the scale will change from green to yellow or red. This will allow you to instantly assess the critical states of the engine without looking at the numbers.
- 📊 Use a graphical display to analyze the dynamics of parameter changes over time.
- 🎨 Set up design themes so that the new sensors fit harmoniously into the overall style of the dashboard.
- 🔔 Enable sound alerts for critical values so as not to be distracted from the road by viewing the screen.
If you plan to use your smartphone as a permanent on-board computer, it is recommended to create a separate dashboard profile with only the most important user sensors. This will reduce the load on the phone's processor and ensure smoother rendering of the animation.
Error diagnosis and troubleshooting
During the setup process, you may encounter a situation where the new sensor displays zero values, dashes, or incorrect data. This does not always mean there is an error in the formula. Often the problem lies in the support of a specific PID by the electronic control unit of your car itself.
Some ECUs simply ignore requests for non-existent or blocked addresses, returning an empty response. In this case, Torque may interpret this as a zero or a communication error. Check the application error log, which is kept in the background and may suggest the reason for the missing data.
It is also worth considering the delay in updating data. Complex formulas and a large number of active PIDs can overload the Bluetooth communication channel, especially on older adapters. Try disabling unnecessary standard sensors to free up bandwidth for your custom settings.
⚠️ Attention: Application interfaces and functions may be updated by developers. If the described menus differ from those you see on the screen, check the "Help" section inside the application or the official developer forum to clarify the current location of the settings.
For deep debugging, use the "Debug" mode in the adapter settings. It allows you to see the raw HEX packets that are sent and received. By comparing the sent request with the ECU response, you can understand whether the information is coming from the car at all or whether the problem is on the data processing side in the application.
What to do if the sensor shows chaotic values?
Chaotic jumps often indicate poor contact in the OBDII connector or interference from the generator. Try cleaning the connector pins with alcohol or using a ferrite bead on the adapter wire to filter out high-frequency interference.
Advanced features and profile sharing
Ecosystem Torque built so that users can share their work. If you have successfully configured a complex sensor for a rare car model, you can export this profile and share it with other users. This saves the community time and allows you to quickly implement new functions without the need to independently select formulas.
Export is done through the PID control menu, where the function of saving the profile to a file is available. This file can be imported on another device, instantly receiving the entire set of configured sensors. In addition, there are ready-made PID packages for popular brands that can be downloaded directly from the application repositories.
Using ready-made profiles also allows you to access hidden functions such as resetting service intervals or adapting the throttle, if these commands are implemented through the PID sequence. However, such operations require special care and understanding of the consequences.
Is it possible to add PIDs without rooting on Android?
Yes, you do not need rooting to add and use custom PIDs in Torque Pro. The application runs in user mode, interacting with the adapter via the standard Android Bluetooth or Wi-Fi stack. Root may be needed only for specific functions of writing logs to system partitions or integration with other system applications.
Why do some PIDs work when parked, but disappear while moving?
This may be due to the limitation of the Bluetooth channel bandwidth at a high frequency of sensor polling. While driving, the ECU can also prioritize critical engine control tasks, ignoring low-priority diagnostic requests. Try increasing the update interval for the problematic sensor.
Is it safe to send custom commands to the ECU?
Reading data (Mode 01 and similar) is absolutely safe for car electronics. There is only a risk when using write or execute commands (Mode 02, 03 and manufacturer specific commands) that can change the settings of the control unit. When creating conventional sensors, you only read the information, so the risk of damage is minimal.
How do I know if my adapter supports extended PIDs?
Most adapters on the ELM327 chip support the standard set of commands. Support for extended commands depends on the firmware version of the adapter itself. Cheap clones often have stripped-down firmware. The best way to check is to try sending a command through the terminal in the application settings or use PC software for diagnostics.
Where to store PID profile files for import?
Profile files are usually saved in the internal memory of the device in the folder /torque/ or /Android/data/org.prowl.torquefree/files/. When importing, the application will prompt you to select a file through a standard explorer. Make sure that the file has the correct extension, usually .csv or a specific Torque export format.