already processed by the Strapdown algorithm, GPS messages, and (onboard) processed data.
how to split an MTB file in two parts and how to safely remove data from an MTB file.
mistake of only one byte (e.g. forgetting to copy a checksum), will make the file corrupt.
support on individual, edited MTB files that don’t work in MT Manager.
configuration message in order to process data.
Locate the first data message, starting with FA FF 36 (FA FF 32 for legacy devices and legacy mode). In Hex Editor Neo, this is done by pressing CTRL-F, choose ‘Hex’ and type FAFF36. Confirm that this pattern of FA FF 36 is an actual data message and not a coincidence in the configuration message by looking at the length, displayed in hexadecimal format after FA FF 36: e.g. “FA FF 36 35” … means that after 54 bytes a new sequence of FA FF 36 should appear.
Copy (don’t cut) everything before this first FA FF 36. Copy this into a new file (CTRL-N).
Split the original data file. Go to e.g. the middle of the file by scrolling down and locate a random tart of a data message (FA FF 36). Select the FA-byte and scroll to the end of the MTB file, press shift and select the position after the last byte in the file. Cut the bytes selected.
If you did this correctly in Hex Editor Neo, the pasted data is red and starts with FA FF 36.
if you want to part an mtb file in more than 2 parts.
Close the original file without saving.
It is not possible (or at least not recommended) to delete a middle part of an MTB file, as this will give large disruptions in the filter algorithm.
Load the MTB file into a hex-editor, e.g. Free Hex Editor Neo.
An MTB file first contains the configuration message, starting with FA FF 0D. You need this configuration message in order to process data.
Locate the first data message, starting with FA FF 36 (FA FF 32 for legacy devices and legacy mode). In Hex Editor Neo, this is done by pressing CTRL-F, choose ‘Hex’ and type FAFF36. Confirm that this FA FF 36 is an actual data message and not a coincidence in the configuration message, by looking at the length, displayed in hexadecimal format after FA FF 36: e.g. “FA FF 36 35” … means that after 54 bytes a new sequence of FA FF 36 should appear.
Remember the byte before FA FF 36 (this is the checksum of the configuration message). After this step, this byte should still be in the data and followed by FA FF 36. Select FA and scroll to that part of the MTB file that you want to remove. Press shift and select the first byte of a random FA FF 36 (so click on FA).
Save the file. It is recommended to save the newly created file as a copy (e.g. File -> Save as -> MT_0770005A_001-copy.mtb).
An MTB file first contains the configuration message, starting with FA FF 0D. You need this configuration message in order to process data. Leave this configuration message in the file.
Go to the part of the file from where you want to delete data by scrolling down and locate a random start of a data message (FA FF 36). Confirm that this FA FF 36 is an actual data message by looking at the length, displayed in hexadecimal format after FA FF 36: e.g. “FA FF 36 35” … means that after 54 bytes a new sequence of FA FF 36 should appear. Select FA and scroll to the end of the MTB file, press shift and select the position after the last byte in the file.