The Blaupunkt Travelpilot DX, a popular in-car navigation system, relies on a complex disc format for its map and guidance data. Understanding this format is crucial for anyone interested in reverse engineering the system, updating maps, or developing compatible software. This article delves into the file structure of the TravelPilot DX disc, exploring its various components and shedding light on the underlying data organization.
Unveiling the TravelPilot DX Disc’s Secrets
Initial analysis reveals that the discs are based on the GDF 3.0 specification (Geographic Data Files), a standardized format for exchanging geographic data. Efforts are currently underway to develop an Open Street Map (OSM) to GDF converter, potentially allowing for the creation of custom maps.
Bosch’s Role and Internal Components
Unlike some navigation systems that rely on data from TomTom or TeleAtlas, the TravelPilot DX discs are generated by Bosch GmbH Hildesheim. The hardware itself utilizes a V810-based processor, executing various ELF (Executable and Linkable Format) files stored on a flash chip. Dumping the flash chip’s contents is ongoing, providing further insights into the system’s inner workings. The map generation process takes place on a Linux system, with specific arguments and configuration files indicating the data sources and processing parameters. A key clue lies within the MAP00001.map file, which references “TPMAP2” – potentially the name of the underlying data structure standard.
Deciphering the Data Files
The disc contains a multitude of files, each serving a specific purpose:
- QUADIDX.DAT: Likely contains the names of all objects within the navigation data.
- RF Files (e.g., RF_1_1_F.DAT): Appear to store Point of Interest (POI) data.
- V01 Files (e.g., V01_006B.DAT): Presumed to contain speech synthesis data.
- NAVxxxxx.DAT Files: The most numerous files, featuring a
TPNAV2_COMPRESSEDheader. These potentially hold crucial navigation data, as they are significantly larger than other files. - DNL and NTL Files: Possibly related to Traffic Message Channel (TMC) information, as their headers contain references to “collect_tmc++” and “write_tmc++”.
Seeking the Missing Standard
The primary challenge lies in identifying the specific standard employed by the NAVxxxxx.DAT files, which hold the core navigation data. Knowing this standard is essential for decoding the compressed data and understanding its organization. The INFO.TXT file provides details about the map data’s origin and software versions, but it doesn’t explicitly reveal the navigation data format. It does, however, confirm the use of GDF files and offers clues about the software used in the creation process.
Potential Approaches and Future Directions
If the standard remains elusive, recreating GDF files and collaborating with Bosch to process them using their proprietary tools is a potential solution. This approach relies on understanding the GDF specification thoroughly and accurately replicating the original data structure. Further analysis of the dumped flash chip contents and the NAVxxxxx.DAT files themselves will be crucial in unlocking the secrets of the Blaupunkt TravelPilot DX navigation system. The ultimate goal is to enable the creation of updated maps and potentially expand the functionality of these devices.
