I've got a conversation going with someone at Cosworth about opening these files up. I will post more info when I hear back from them.

 

^^^that would be fabulous.

I've started down the rabbit hole this morning on this. The PDR files have an additional track called "ctbx". I'm guessing that this is where the data lives. I'm pretty sure I can find a way to extract it, but reverse engineering the format is a whole next level of voodoo.

 

If you can get the file extracted, I have some nerdy friends who could look at it the format.

 

I just pulled the whole file up in a hex editor. There are some strings in that stream but I think it's mostly the roll-up report data you see in the PDR. I guess it's possible that the specific point it time data is in the edts atom the audio or video stream (useful article here - http://www.adobe.com/devnet/video/ar...ovie_atom.html

Here are some of the more interesting strings I saw though so there does appear to be some undisplayed but interesting data available.

System Power Mode
System Backup Power Enabled
System Backup Power Mode
Steering 1 Switch
Steering 2 Switch
Transport Storage Mode
Infotain Op Mode
Valet Mode
Boost Pressure Ind
Coolant Temp
Intake Boost Pressure
Oil Pressure
Oil Temp
RPM
Accel Pos
Clutch Pos
Brake Pos
LF Tyre Pressure
RF Tyre Pressure
LR Tyre Pressure
RR Tyre Pressure
LF Tyre Temp
RF Tyre Temp
LR Tyre Temp
RR Tyre Temp
Gear
Trans Oil Temp
Fuel Level
Fuel Capacity
Steering Angle
Distance
Speed
ABS Active
Traction Control Active
Vehicle Stability Active
Corner Exit Setting
Speed Request Intervention
Speed Control Response
Engine Speed Request
Engine Torqure Req
Battery Voltage
Lateral Acceleration
Longitudinal Acceleration
Vertical Acceleration
Latitude
Longitude
Altitude
Heading
GPS Fix
Beacon

 

progress is progress

 

I could probably make some progress on reverse engineering the protocol if someone could send me the extracted data stream.

 

It's probably just easier to crack open a file with data in winhex or the like and look at it there. The additional track you can find by looking for the string "Marlin PDR 1.0" and the MP4 spec will at least give you the header info for the track.

I think there might be data in the edts atom on the audio and video tracks as well though. You can just look for edts to find those atoms in the file.

Below is a dump of the structure of a PDR file that was edited and as such it lost its data, following by one that is unedited.

***Edited file***
[ftyp] size(24), hasSubBox(0)
[uuid] size(44), hasSubBox(0)
[mdat] size(230219797), hasSubBox(0)
[moov] size(37843), hasSubBox(1)
[mvhd] size(108), hasSubBox(0)
[trak] size(16890), hasSubBox(1)
[tkhd] size(92), hasSubBox(0)
[mdia] size(16790), hasSubBox(1)
[mdhd] size(32), hasSubBox(0)
[hdlr] size(45), hasSubBox(0)
[minf] size(16705), hasSubBox(1)
[vmhd] size(20), hasSubBox(0)
[dinf] size(36), hasSubBox(1)
[dref] size(28), hasSubBox(0)
[stbl] size(16641), hasSubBox(1)
[stsd] size(165), hasSubBox(0)
[stts] size(24), hasSubBox(0)
[stsc] size(2932), hasSubBox(0)
[stsz] size(12124), hasSubBox(0)
[stco] size(1276), hasSubBox(0)
[stss] size(112), hasSubBox(0)
[trak] size(20769), hasSubBox(1)
[tkhd] size(92), hasSubBox(0)
[mdia] size(20669), hasSubBox(1)
[mdhd] size(32), hasSubBox(0)
[hdlr] size(45), hasSubBox(0)
[minf] size(20584), hasSubBox(1)
[smhd] size(16), hasSubBox(0)
[dinf] size(36), hasSubBox(1)
[dref] size(28), hasSubBox(0)
[stbl] size(20524), hasSubBox(1)
[stsd] size(100), hasSubBox(0)
[stts] size(24), hasSubBox(0)
[stsc] size(160), hasSubBox(0)
[stsz] size(18956), hasSubBox(0)
[stco] size(1276), hasSubBox(0)
[udta] size(68), hasSubBox(1)
[meta] size(52), hasSubBox(0)
[Xtra] size( 8), hasSubBox(0)

***Unedited file (with data)***

[ftyp] size(32), hasSubBox(0)
[mdat] size(1130908646), hasSubBox(0)
[moov] size(969124), hasSubBox(1)
[mvhd] size(108), hasSubBox(0)
[trak] size(395129), hasSubBox(1)
[tkhd] size(92), hasSubBox(0)
[edts] size(48), hasSubBox(0)
[mdia] size(394981), hasSubBox(1)
[mdhd] size(32), hasSubBox(0)
[hdlr] size(45), hasSubBox(0)
[minf] size(394896), hasSubBox(1)
[vmhd] size(20), hasSubBox(0)
[dinf] size(36), hasSubBox(1)
[dref] size(28), hasSubBox(0)
[stbl] size(394832), hasSubBox(1)
[stsd] size(136), hasSubBox(0)
[stts] size(1744), hasSubBox(0)
[stsc] size(28), hasSubBox(0)
[stsz] size(194292), hasSubBox(0)
[stco] size(194288), hasSubBox(0)
[stss] size(4336), hasSubBox(0)
[trak] size(548748), hasSubBox(1)
[tkhd] size(92), hasSubBox(0)
[edts] size(48), hasSubBox(0)
[mdia] size(548600), hasSubBox(1)
[mdhd] size(32), hasSubBox(0)
[hdlr] size(45), hasSubBox(0)
[minf] size(548515), hasSubBox(1)
[smhd] size(16), hasSubBox(0)
[dinf] size(36), hasSubBox(1)
[dref] size(28), hasSubBox(0)
[stbl] size(548455), hasSubBox(1)
[stsd] size(103), hasSubBox(0)
[stts] size(24), hasSubBox(0)
[stsc] size(28), hasSubBox(0)
[stsz] size(274148), hasSubBox(0)
[stco] size(274144), hasSubBox(0)
[trak] size(25131), hasSubBox(1)
[tkhd] size(92), hasSubBox(0)
[edts] size(48), hasSubBox(0)
[mdia] size(24983), hasSubBox(1)
[mdhd] size(44), hasSubBox(0)
[hdlr] size(47), hasSubBox(0)
[minf] size(24884), hasSubBox(1)
[mmhd] size(12), hasSubBox(0)
[dinf] size(36), hasSubBox(1)
[dref] size(28), hasSubBox(0)
[stbl] size(24828), hasSubBox(1)
[stsd] size(24176), hasSubBox(0)
[stts] size(392), hasSubBox(0)
[stsc] size(28), hasSubBox(0)
[stsz] size(20), hasSubBox(0)
[stco] size(204), hasSubBox(0)

 

Bump. Has anyone made any progress with extracting data?

 

 

I actually sent Cosworth a mail yesterday to ask how much the API key costs. I'm so in to the Pi Toolbox stuff now I'm thinking of writing some add-ons. We'll see what it costs and what sort of functionality the API provides.