# Custom/extra inputs within realdash

**URL:** <https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111>\
**Category:** OBD2\
**Created:** [December 9, 2024, 3:08pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111 "2024-12-09T15:08:52Z")\
**Posts on this page:** 20\
**Page:** 2

<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:** [January 9, 2025, 7:29am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/24 "2025-01-09T07:29:35Z")

</div>

I’m investigating the log. Meanwhile, try with multipid requests disabled. They seem to be on per the log file.

---

<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:** [January 9, 2025, 2:38pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/25 "2025-01-09T14:38:50Z")

</div>

> [@GR-RY](#):
>
> Hi I have just sent a debug file

Thank you for your help. Sent you an email with link to pre-release version to test on.

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 9, 2025, 9:30pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/27 "2025-01-09T21:30:07Z")

</div>

Hi I have tested it now and this now does load the xml and populates all dash I have created and even the custom pid works but the connection drops out every few seconds then comes back again. I have sent another debug log at 21:22 ish on 9th January 2024

---

<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:** [January 10, 2025, 9:40am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/28 "2025-01-10T09:40:40Z")

</div>

> [@GR-RY](#):
>
> I have sent another debug log

I think I found the issue and made another test version for you (sent email).

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 10, 2025, 8:19pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/29 "2025-01-10T20:19:47Z")

</div>

Thanks so much for your help, I really appreciate it. I have tested that this evening and all is working well. When will that version be the one you can download from the App Store?

---

<div class="post-metadata">

**Author:** ![DeLasNoches](https://forum.realdash.net/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@DeLasNoches](https://forum.realdash.net/u/DeLasNoches)\
**Post date:** [January 11, 2025, 5:54am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/30 "2025-01-11T05:54:33Z")

</div>

Once they have the latest update ready, they’ll push the fix as well

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 11, 2025, 7:08pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/31 "2025-01-11T19:08:34Z")

</div>

That’s great thanks but do we know what sort of timeframe that will be in?

---

<div class="post-metadata">

**Author:** ![DeLasNoches](https://forum.realdash.net/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@DeLasNoches](https://forum.realdash.net/u/DeLasNoches)\
**Post date:** [January 12, 2025, 4:27am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/32 "2025-01-12T04:27:52Z")

</div>

I don’t think they give timeframes on their updates. I believe it will vary depending any bug fixes and if any new features are being worked on.

---

<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:** [January 13, 2025, 7:28am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/33 "2025-01-13T07:28:08Z")

</div>

> [@DeLasNoches](#):
>
> I don’t think they give timeframes on their updates.

Yes, we usually don’t give an estimate. The next release (2.4.6) will contain this fix. Hopefully we will get it out next week the latest.

Meanwhile its safe to continue using the test version and it will automatically update from Play Store when official fix is available.

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 14, 2025, 1:59pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/34 "2025-01-14T13:59:48Z")

</div>

Thanks so much for all of your help and hopefully I can now try and add in some further custom inputs now. Assuming I’m able to convert the PIDs I have into some readable by RealDash.  
Would you be able to help me with the equivalent of this in RealDash?

Name, “ShortName”, “ModeAndPID”, “Equation”, “Min Value”, “Max Value”, “Units”, “Header”, “startDiagnostic”, “stopDiagnostic”, “scale”,“minimumRefreshDelayMillis”

Tire ID 1 Pressure “Tire ID2 Press” “0x221005” “B \* 0.01373” “0” “10” “bar” “750” “atcea2A\natta2A” “atcea” “1” “0”

---

<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:** [January 15, 2025, 6:56am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/35 "2025-01-15T06:56:04Z")

</div>

> [@GR-RY](#):
>
> Would you be able to help me with the equivalent of this in RealDash?

Sure, I will test this on our simulator and check if this can be made to work without modifications to the app.

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 15, 2025, 7:41am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/36 "2025-01-15T07:41:00Z")

</div>

That’s amazing, thanks so much

---

<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:** [January 15, 2025, 12:28pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/37 "2025-01-15T12:28:54Z")

</div>

Use RealDash-v246-prerel4 from same link I sent you earlier.

Add this line to your XML file:

```auto
<command send="221005" header="atsh750\ratcea2A\ratta2A" targetId="240" units="bar" conversion="B1*0.01373" skipCount="32"></command> <!-- front left tire pressure -->

```

Let me know if it works for you.

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 15, 2025, 8:44pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/38 "2025-01-15T20:44:57Z")

</div>

Thanks again for your help, the one you have sent me works fine for 2 seconds or so then the value just goes back to zero, I have tried to copy your formula for the other 3 but that doesn’t work so I’ll try and figure out what I’ve done wrong there with those formulas. Would sending a debug file be useful again?

---

<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:** [January 16, 2025, 6:27am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/39 "2025-01-16T06:27:34Z")

</div>

> [@GR-RY](#):
>
> Would sending a debug file be useful again?

Yes it would, please send one.

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 16, 2025, 6:36pm UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/40 "2025-01-16T18:36:52Z")

</div>

Debug file sent 18:35 gmt Thursday 16th jan  
Thanks

---

<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:** [January 17, 2025, 8:18am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/41 "2025-01-17T08:18:41Z")

</div>

I believe I found the issue. Please install RealDash-v246-prerel5.apk from the same link I provided before. Please send a debug log if it is still not working.

I see from the log that PID 221005 is called 4 times on the row. That confused me a bit, but I assume you added this PID to XML for each tire? As response to 221005 only contains 2 bytes, it cannot contain pressure for other tires. Could you share the original CSV lines for all 4 tire pressures?

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 17, 2025, 8:43am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/42 "2025-01-17T08:43:07Z")

</div>

Thanks I will try this later and hopefully that works nicely.  
This below is the information I have on each tyre, I’d imagine I have put some info in wrong for the other 3 tyres then;

| Tire ID 1 Position | Tire ID1 Pos | 0x222021 | LOOKUP(A::1=FL:2=FR:3=RL:4=RR) | 0 | 100 | | 750 | atcea2a\natta2a | atcea | 1 | 0 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Tire ID 1 Pressure | Tire ID2 Press | 0x221005 | B \* 0.01373 | 0 | 10 | bar | 750 | atcea2A\natta2A | atcea | 1 | 0 |
| Tire ID 1 Temperature | Tire ID1 Temp | 0x221004 | A-40 | -30 | 100 | °C | 750 | atcea2a\natta2a | atcea | 1 | 0 |

|Tire ID 2 Position|Tire ID2 Pos|0x222021|LOOKUP(B::1=FL:2=FR:3=RL:4=RR)|0|100||750|atcea2a\natta2a|atcea|1|0|  
|Tire ID 2 Pressure|Tire ID2 Press|0x221005|D \* 0.01373|0|10|bar|750|atcea2A\natta2A|atcea|1|0|  
|Tire ID 2 Temperature|Tire ID2 Temp|0x221004|B-40|-30|100|°C|750|atcea2a\natta2a|atcea|1|0|

|Tire ID 3 Position|Tire ID3 Pos|0x222021|LOOKUP(C::1=FL:2=FR:3=RL:4=RR)|0|100||750|atcea2a\natta2a|atcea|1|0|  
|Tire ID 3 Pressure|Tire ID3 Press|0x221005|F \* 0.01373|0|10|bar|750|atcea2A\natta2A|atcea|1|0|  
|Tire ID 3 Temperature|Tire ID3 Temp|0x221004|C-40|-30|100|°C|750|atcea2a\natta2a|atcea|1|0|

|Tire ID 4 Position|Tire ID4 Pos|0x222021|LOOKUP(D::1=FL:2=FR:3=RL:4=RR)|0|100||750|atcea2a\natta2a|atcea|1|0|  
|Tire ID 4 Pressure|Tire ID4 Press|0x221005|H \* 0.01373|0|10|bar|750|atcea2A\natta2A|atcea|1|0|  
|Tire ID 4 Temperature|Tire ID4 Temp|0x221004|D-40|-30|100|°C|750|atcea2a\natta2a|atcea|1||

---

<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:** [January 17, 2025, 8:58am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/43 "2025-01-17T08:58:34Z")

</div>

This does not seem right. Here is what your vehicle is responding:

RD SENDS: 221005  
RESPONSE: 7582A100D62100500A0\>

The 621005 in the response indicates that following bytes are a response to PID request 221005- hence we have data bytes 00 A0.

Converting 0xA0 with \* 0.01373 will give us 2.2, which seems sensible tire pressure.

But with quick look all 4 requests for tire pressure seem identical in except for conversion formula, which are:

Tire 1: B \* 0.01373  
Tire 2: D \* 0.01373  
Tire 3: F \* 0.01373  
Tire 4: H \* 0.01373

As bytes in Torque CSV format are identified as ‘A’ first byte, ‘B’ second byte etc, we can see that there is no bytes ‘D’, ‘F’, nor ‘H’ in the reply.

---

<div class="post-metadata">

**Author:** ![GR-RY](https://forum.realdash.net/letter_avatar_proxy/v4/letter/g/ba8739/32.png) [@GR-RY](https://forum.realdash.net/u/GR-RY)\
**Post date:** [January 17, 2025, 9:22am UTC](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111/44 "2025-01-17T09:22:40Z")

</div>

So would that suggest that each tyre should have its own PID then? As there is no more data in that PID?

[Previous page](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111.md?page=1)

[Next page](https://forum.realdash.net/t/custom-extra-inputs-within-realdash/7111.md?page=3)
