![6.7 torque pro extended pids csv 6.7 torque pro extended pids csv](https://i2.wp.com/torqueproapk.org/wp-content/uploads/2021/07/cropped-torque-pro.png)
![6.7 torque pro extended pids csv 6.7 torque pro extended pids csv](https://www.motorcarsoft.com/tuto_img_youtube/h/Tor47que-Pro.jpg)
Specify the minimum and maximum value expected from this sensor. Valid operation supported: +, -, *, /, (). A valid expression in OBD dash allows you do interpret up to 33 bytes of return values. Use the letter 'A' in the expression to represent the value of the 1st return byte, 'B' to represent the value of the 2nd return byte, 'C' to represent the value of 3rd return byte, so on and on. Specify the expression to interpret the return of the queries. For mode 23 access, the parameter is a three bytes value. Note that you may need to clear set first (especially if you imported before the Dec 2020 update) Upper right menu, add predefined set, and the CSV file should be one of them. For mode 22 access, parameter is a 2 bytes value (16bit). Open Torque, main menu (sprocket in bottom left corner), Settings, Manage extra PIDs/Sensors. For mode 21 access, parameter is a one byte value.
#6.7 torque pro extended pids csv iso#
For mode 01 access, parameter ID is a one byte value, see ISO standard for more details. Specify the parameter ID (in HEX) of this sensor. * mode 23: request data by memory address, you can use this to request manufacturer specific sensor data * mode 22: request data by parameter ID, you can use this to request manufacturer specific sensor data * mode 21: request data by address offset, you can use this to request manufacturer specific sensor data * mode 01: for requesting power chain data from sensor listed on standard ISO 15031-5/SAE J1979 Select the service ID /Mode ID for the sensor, this can either be: Specify the ECU address for this data stream, if this field is empty, the default address will be used Specify a red line value if you want the gauge to show alert when reading exceed the specified. Specify a display string as the measurement unit (such as MPG, 'F etc) Reason being requesting data more often than required results to the same reading anyway, and each query sent to the ECU distracts the ECU from its main function, which is controlling the car. For things that doesn't change much in short period of time, like fluid temperature, choose something like "every 5 seconds" or even "every 10 seconds". This defines how often the app should request information from the ECU. Select an appropriate data sampling rate for this data stream. Specify a short (no more than 8 characters) display name for this data stream, this is the name showing on the gauge's name tag Extended diagnostic queries are different from vehicle to vehicle. Specify the make/model of the vehicle that can use this custom data stream. Tap the "Add data stream" button to open the 'New custom data stream' page Tap the "Custom PID" button on the Home page, this opens the custom data stream database. To enter these information to OBD dash app: The format of the ECU reply and the mean to interpret these replies. The access mode and parameter ID that identifies these sensors The ECU address which these sensors reported to OBD dash.Pro and OBD dash.Sports gauge can access any manufacturer specific sensors (extended PIDs) using OBD extended diagnostic mode $23, $22, $21. The precondition is that you must obtain the following information in related to these manufacturer specific sensors: