Mobile application Torque Pro has long become the de facto standard for car enthusiasts who want to gain full control over the diagnostic data of their car via a smartphone. However, the standard set of sensors available “out of the box” often does not cover all the needs of an advanced user, especially when it comes to specific engine parameters, transmission temperature or boost pressure in tuned cars.
This is where custom PIDs (Parameter ID) come into the picture, which allows you to expand the functionality of the app beyond recognition. Adding your own codes requires understanding the structure of OBD2 requests, but the result is worth it: you gain access to hidden ECU data that is not displayed in basic mode. In this article we will analyze in detail the process of creating, importing and debugging new sensors.
It is worth immediately noting that the successful addition of a parameter depends not only on the correctness of the entered formulas, but also on the support of a specific request by your engine control unit (ECU). Some units, especially on older cars or specific brands like VAG or BMW, may ignore non-standard requests, even if the syntax in the application is entered correctly.
Preparing for work and selecting an adapter
Before proceeding with complex settings within the application, you need to make sure the physical connection is reliable. The quality of data transfer directly affects the stability of user scripts. Cheap Chinese clones of adapters ELM327 version 1.5 often work unstable when asked, which is critical for custom PIDs.
It is recommended to use proven adapters with chip ELM327 version 2.1 or original scanners from car manufacturers. They provide a more stable communication protocol and support extended command sets. If you plan to actively use the data logging function with new sensors, connection speed becomes a critical factor.
⚠️ Warning: When working with custom PIDs in real time, the load on the adapter increases. If you notice a loss of communication or severe delays, try disabling unnecessary standard sensors in your profile settings to free up the communication channel.
It is also important to check the version of the application itself. The developer periodically updates the data processing engine, and old formulas may behave differently in new builds. Make sure you have the latest stable version installed Torque Pro from the official store or trusted source.
Navigation through the sensor settings menu
The app interface may seem overloaded for a beginner, but the path to creating new parameters lies through a clearly defined menu structure. You need to go to the main settings of the application by clicking on the gear icon on the main screen or in the sidebar.
In the list that opens, find the section Settings, and then scroll down to the item Managing additional sensors. This is where all the tools for working with user data are concentrated. This section allows you to both create sensors from scratch and import ready-made databases.
When you first enter this section, you will see a list of already active additional PIDs. If the list is empty or only contains standard extensions, this is normal. To get started, click the button Add sensor, which is usually located at the bottom of the screen or in the action menu (three dots).
The system will prompt you to select the type of parameter to be created. You can create a new sensor based on an existing template or start from scratch by selecting the Empty sensoroption. The second option is preferable for those who know exactly the HEX request code and the conversion formula.
Use the search function in the list of sensors if you have many of them. Enter part of the name or HEX code to quickly find the desired parameter for editing.
Custom PID structure: Fields and values
The most important step is to correctly fill out the configuration fields of the new sensor. An error in one character of the HEX code or in a sign of a mathematical formula will cause the sensor to show zeros, random numbers, or not be polled by the ECU at all.
First field - Title. Here you enter the name that will be displayed on the dashboard. Use clear abbreviations, for example Temp Oil for oil temperature or Boost PSI for boost pressure. Long titles may not fit on the main screen widgets.
Next is the field Long name, which is used in logs and detailed reports. Here you can write in detail, for example, “Engine oil temperature (sensor in the pan).” This will help you not get confused when analyzing the recorded data after a while.
| Settings field | Description | Example value |
|---|---|---|
| Header | Initiation command (rarely changes) | 41 |
| OBD Request | HEX code of the parameter | 5C |
| Response | Response length in bytes | 4 |
| Formula | Calculation mathematics | (A*256+B)-40 |
| Units Type) | Value display type | Temperature (C) |
Field OBD Request requires entering a HEX code. For standard modes (Mode 01), the first digit is often already substituted, so you only need to enter the parameter identifier itself, for example 5C. If you are using advanced modes, the syntax may differ.
The most difficult field is Formula. Data coming from the ECU is often presented in “raw” form (bytes A, B, C, D). You need to convert them into understandable quantities. For example, a formula is often used for temperature (A*256+B)-40, where A and B are the high and low bytes of the response.
How do bytes A, B, C, D work?
In the OBD2 protocol, the response from the ECU is divided into bytes. Byte A is the first data byte after the response header, B is the second, and so on. If the parameter occupies 2 bytes, A and B are used. The formula allows you to scale these values.
Math formulas and scaling logic
Understanding how the ECU encodes data is the key to success. Most parameters are passed as unsigned integers, which require shifting or scaling. The application Torque Pro supports standard arithmetic operations: addition, subtraction, multiplication, division, as well as exponentiation.
Consider an example of calculating pressure. Let's say the ECU returns a value in kPa, and you need to see Bars. The formula will look like (A*256+B)/100. Here we first collect a number from two bytes and then divide by 100 to convert the units.
For floating point parameters or specific logic, more complex structures may be required. In some cases it is necessary to use conditional statements, although the basic version of formulas in Torque is limited to arithmetic. If the sensor shows incorrect values, try changing the byte order (use B before A).
⚠️ Attention: Do not use too complex calculations in PID formulas if you have an old smartphone or a slow adapter. This may lead to a drop in the data refresh rate (FPS) on the screen.
It is important to do it correctly select Minimum and Maximum values in the sensor settings. This is necessary for correct display of the graph and color indication. If you set the maximum to 100, and the real value reaches 150, the graph may be “cut off” or the sensor will be highlighted in red as an emergency.
Always check the conversion formula with the documentation for the specific ECU of your car. There are no universal formulas for all brands, especially for temperature and pressure.
Import of ready-made databases. PID
You don’t have to reinvent the wheel and select formulas at random. The user community Torque Pro has created a huge database of ready-made configurations for thousands of car models. Importing such files is the fastest way to get working sensors.
Extension files have the format .csv or. specific Torque export format. They can be found on specialized forums dedicated to chip tuning and diagnostics. After downloading the file, place it in the device memory, preferably in the folder Download or the root of the internal memory for ease of search.
To import, go to the menu Managing additional sensors and select the option Importing sensors (folder icon with an inward arrow). Find the downloaded file in the application's file manager. After selection, the system will prompt you to confirm adding new entries to your database.
- 📂 Files can contain hundreds of lines - import only those that your car needs so as not to clutter the list.
- 🔄 After After importing, be sure to restart the application to correctly initialize new profiles.
- 🔍 Check the checkboxes next to the imported sensors - they must be active to display on the screen.
Please note that naming conflicts may arise during import if you have already created sensors with similar names. The app usually suggests skipping duplicates or overwriting them. Be careful with overwriting if you have previously configured these sensors manually to suit your needs.
☑️ Checking import
Diagnostics and resolution of display problems
Even with ideally entered data, the new sensor may stubbornly display dashes (---) or zeros. This does not always mean there is an error in the formula. Often the problem lies in the fact that a particular ECU does not support the requested PID in the current operating mode.
The first diagnostic step is to check mode support. Go to the adapter settings and make sure that the option OBD Extended Mode or similar is enabled. Some blocks require explicit permission to read non-standard parameters.
If the sensor is still silent, try changing the refresh rate. Polling too quickly may cause the adapter buffer to overflow. Set the polling interval for a specific sensor to 500 ms or 1 second and see if the data appears.
⚠️ Note: Interfaces and menu names in the application may vary slightly depending on the version of Android and the specific build of Torque Pro. If you don’t find the item, look for it in the related settings sections.
It’s also worth checking the application error log. The settings have a logging function that records all sent and received commands. By viewing the log, you will see whether the request is sent at all and what response (or lack of response) comes from the machine.
In case of complete failure with a specific PID, try to find an alternative code. For example, oil temperature can be transmitted through different identifiers depending on the year of manufacture of the car. Experiment with adjacent HEX codes from the SAE J1979 standards table.
What are modes 01 and 02?
Mode 01 (Show current data) requests current data in real time. Mode 02 (Show freeze frame data) requests frozen data at the time of the last error. Custom PIDs most often operate in mode 01.
Frequently Asked Questions (FAQ)
Why is my added PID showing 0 or dashes?
Most likely, your engine control unit (ECU) does not support this particular parameter ID. Not all machines provide all the data. Also check the correctness of the conversion formula and make sure that the adapter is connected stably.
Is it possible to add a PID to control fans or other components?
No, the OBD2 protocol in read mode (which Torque Pro uses) is only for data monitoring. Active control of vehicle components (writing to the ECU) requires other operating modes and specialized equipment, which is beyond the scope of the application functionality.
Where can I find HEX codes for my specific car model?
There is no universal database for all cars. Look for information on specialized forums for your brand (for example, BMW, VAG, Toyota forums). Enthusiasts often post tables of supported PIDs for specific ECU firmware versions.
Is it safe to add custom PIDs for the engine?
Yes, it is absolutely safe. You only read data from the car's computer memory. Adding a PID to the application does not affect the operation of the electronics in any way, does not erase errors or change firmware settings. This is passive observation.