I've got an older GM vehicle with VPW bus instead of CAN. I'm trying to pull some parameters that must come from the ABS module (brake pressure, wheel speed, etc). When I use the custom header for a custom PID, I can get the data, but the bytes I get back is longer than your standard PIDs and the bytesToUint function (or any function for that matter) only returns the same value as raw.
I can't seem to post a picture, but I'll try to explain.
There's a few bugs I've seen with this
1) Once I set a custom header for a custom PID, it breaks every other standard PID, because the header is wrong I'm guessing (they all no data)
2) I have to then create custom PIDs for all the standard PIDs I want, with "custom headers" entered back to default so I can get data again. However, because of these different headers, my data glitches. Sometimes the "corrected" intake temperature PID from the ECU shows the same value as my brake pressure custom PID (different target addresses in VPW, so not sure what's happening here in the back end).
Here's an example of the data back and forth for my custom PID. Note the headers and parity byte are also included (first 3 bytes are header, and last byte is parity).
6C 28 F1 2A 03 41 A6
6C F1 28 6A 41 00 00 05 00 00 1D F5
When I manually type "41 00 00 05 00 00 1D" into the "source data" for my math, it does the math correctly there. However once I test the connection, it shows only the raw data.
1: bytesToUint(raw,7,1) / 2.55
3: Just to see if the byte function worked at all, I tried just putting 'A' as well.
All of these resulted in the parameter showing "6A4100000500001D" and not being data logged...
I'm on version 6.4.1 on Android.
Also, unrelated, but also a bug i've noticed on Android and iOS. The internal accelerometers show that they are collecting data when viewing the live data during a session, but when I go to view the data after, it's always invalid/flat. Looks like it's just recording random noise around a certain value, definitely not what it showed in the preview window. Maybe a simple bug? It's kind of annoying I can't use my internal phone's sensors. This behavior happens on 2 different android phones and 1 iPhone that i've tried it on personally.