The 'distance' channel is broken on your sample session for the accelerometer device. It should fix the accelerometer issue, but on new sessions only. Ok, there's several things going on so, let's start clearing them up one by one.ġ) Please update to RaceChrono v7.0. This behavior happens on 2 different android phones and 1 iPhone that i've tried it on personally. Maybe a simple bug? It's kind of annoying I can't use my internal phone's sensors. Looks like it's just recording random noise around a certain value, definitely not what it showed in the preview window. 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. However once I test the connection, it shows only the raw data.ģ: Just to see if the byte function worked at all, I tried just putting 'A' as well.Īll of these resulted in the parameter showing '6A4100000500001D' and not being data logged.Īlso, unrelated, but also a bug i've noticed on Android and iOS. When I manually type '41 00 00 05 00 00 1D' into the 'source data' for my math, it does the math correctly there. Note the headers and parity byte are also included (first 3 bytes are header, and last byte is parity). Here's an example of the data back and forth for my custom PID. 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). However, because of these different headers, my data glitches.

I can't seem to post a picture, but I'll try to explain.ġ) 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)Ģ) 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. 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'm trying to pull some parameters that must come from the ABS module (brake pressure, wheel speed, etc). I've got an older GM vehicle with VPW bus instead of CAN.

Gm pid list