Did we get only total lap time, or sectors as well?![]()
Feature: "C" telemetry format discovered · Issue #18 · Nenkai/PDTools
I’ve discovered a new 368 byte telemetry packet that can now be accessed by sending the "C" heartbeat. The XOR constant is the same as Packet B (0xDEADBEEF). • [0:4] SurfaceType (char): Indicates t...github.com
I've already found some of the new datapoints, you can see further technical details here. ^
The current stuff I've found is:
Surface Type Indicator (what kind of surface your tyre is in contact with, such as tarmac, dirt etc)
Current Laptime (!!!) (You can now see your exact current lap time, finally.)
Category Type (Which car category you are currently driving)
I'm going to do some more research in the morning, the other fields appear to be harder to decode for me at least.
Only lap-time right now, I don’t see how that would be implemented easily (as there are only 12 bytes left to find out the meaning of, and some tracks have multiple sectors). It looks the last 4 bytes of the 12 bytes sequence is tied to the steering or some kind of yaw. Not really sure as of right now though.Did we get only total lap time, or sectors as well?
Yeah I was able to read the new data by looking at your code, thank you!Only lap-time right now, I don’t see how that would be implemented easily (as there are only 12 bytes left to find out the meaning of, and some tracks have multiple sectors). It looks the last 4 bytes of the 12 bytes sequence is tied to the steering or some kind of yaw. Not really sure as of right now though.
You can now test out my current findings using my library for ESP32/ESP8266 devices.
![]()
GitHub - MacManley/gt7-udp: A Gran Turismo 7 UDP Telemetry Parser for the ESP32 / ESP8266 Boards
A Gran Turismo 7 UDP Telemetry Parser for the ESP32 / ESP8266 Boards - MacManley/gt7-udpgithub.com
I don't have a Github account so I'm posting here:![]()
Feature: "C" telemetry format discovered · Issue #18 · Nenkai/PDTools
I’ve discovered a new 368 byte telemetry packet that can now be accessed by sending the "C" heartbeat. The XOR constant is the same as Packet B (0xDEADBEEF). • [0:4] SurfaceType (char): Indicates t...github.com
I've already found some of the new datapoints, you can see further technical details here. ^
The current stuff I've found is:
Surface Type Indicator (what kind of surface your tyre is in contact with, such as tarmac, dirt etc)
Current Laptime (!!!) (You can now see your exact current lap time, finally.)
Category Type (Which car category you are currently driving)
I'm going to do some more research in the morning, the other fields appear to be harder to decode for me at least.
Hi, sure feel free to test it https://github.com/chrshdl/instrument-clusterpresent I'm using EZIODASH Pro as main dash board. And I love the motivation from the box … 😇😊
additional a Android tablet with PRO Sim Dashboard on the side for more information with a little bit bigger letters for my old eyes 🤪
But I like to test @chrshdl solution also 😍
PI4 and a dashboard display 14,5" are on board … I'm curios
Thanks to all developers .. great job 👍🥰
I would assume it’s the same functionality as the GT7Tracks project and they just went to the effort of mapping the sectors. I’m not aware of any telemetry data that let’s you see which sector you are on.Was anyone able to identify which sector are you on based on Telemetry data?
I know you can draw the track using the coordinates. And with GT7Tracks project you can identify the track. But you still need to map the coordinates of each track that represent Sector 1, Sector 2 and so on.
Coach Dave Delta and Victory Dash has been able to do this, but their code isn't available, neither their track/sector mapping.
Yeah they did that, it was discussed it a few pages behind on this thread.I would assume it’s the same functionality as the GT7Tracks project and they just went to the effort of mapping the sectors. I’m not aware of any telemetry data that let’s you see which sector you are on.