# Target IDs for Catalyst Temperature

**URL:** <https://forum.realdash.net/t/target-ids-for-catalyst-temperature/8246>\
**Category:** Feature requests\
**Created:** [May 8, 2025, 12:29pm UTC](https://forum.realdash.net/t/target-ids-for-catalyst-temperature/8246 "2025-05-08T12:29:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frongus](https://forum.realdash.net/user_avatar/forum.realdash.net/frongus/32/2040_2.png) [@frongus](https://forum.realdash.net/u/frongus)\
**Post date:** [May 8, 2025, 12:29pm UTC](https://forum.realdash.net/t/target-ids-for-catalyst-temperature/8246/1 "2025-05-08T12:29:34Z")

</div>

The standard OBD2 protocol does feature PIDs for catalyst temperatures, as following (using the 01 “Show Current Data” mode):

- `013C` – Catalyst Temperature: Bank 1, Sensor 1
- `013D` – Catalyst Temperature: Bank 2, Sensor 1
- `013E` – Catalyst Temperature: Bank 1, Sensor 2
- `013F` – Catalyst Temperature: Bank 2, Sensor 2

The conversion formula is `((256*A+B)/10)-40`, yielding values between –40 °C and 6,513.5 °C. For °F, take the °C value, multiply it by `1.8` and add `32`.

However, as far as I know, there are no Target IDs for these in RD, or they aren’t documented in the [Target ID list](https://realdash.net/manuals/targetid.php).

For example, I can read data for `013C` from my vehicle via OBD2 and have it displayed in RD with a custom XML file. Right now, I can do this by either using `name=""` instead of `targetId=""` in the XML file, yielding a new input in “ECU Specific”, or linking the target ID of one of the “Dummy” inputs, since I don’t know how to use values from `name=""` in custom equations or Gauge Math, or if that is even possible.

---

<div class="post-metadata">

**Author:** ![realdashdev](https://forum.realdash.net/user_avatar/forum.realdash.net/realdashdev/32/6_2.png) [@realdashdev](https://forum.realdash.net/u/realdashdev)\
**Post date:** [May 9, 2025, 7:46am UTC](https://forum.realdash.net/t/target-ids-for-catalyst-temperature/8246/2 "2025-05-09T07:46:18Z")

</div>

These (and any other) values can be used with RealDash without built-in Target IDs. Specify ‘name’ attribute in XML file, and RealDash creates new input into ‘ECU Specific’ category.