Binary raw data file conversion

[jpnovak]

Just a quick update. I changed some code and now have things working. Sort of...

I can generate an .frd file that will convert from TS. I am getting a few extra bytes on the end of my header that create parsing problems for the MS outpc string. I am getting so close now. Just the fact that it will write to the card is a good thing.

There are also some timing issues to work out to speed things up a bit. I am currently getting about 22Hz logging frequency. This should be sufficient but I think I can do better.


Thanks for your help. I will update when I have this working well.

[jpnovak]

Fixed my bugs. Everything is working well now. I am going to try and run some boards. I started a new thread in the expansion board section.

viewtopic.php?f=67&t=37342

[LT401Vette]

Cool... It would be nice to see one of these get going.

Now if you can make it populate the header signature with the queryCommand and adjust the outpc length based on that, it will work for multiple firmwares.

[jpnovak]

Phil, Do you have any documentation on the query command? Is it buried in the base code or .ini file?

I don't recall reading of that function. I am already changing the code for MSII extra since the outpc is different byte length.

[jpnovak]

I just thought about this for two seconds and forgot the "Q" sends back the code variant. Ahh now I have new ideas...

[LT401Vette]

Yep, they are in the ini.

It is Q for MSII, MS1 Extra uses S

[jpnovak]

I don't recall. Between S and Q... One is board revision and one is code variant.

time to code some If () statements related to the above information.

[LT401Vette]

There is no board version... They are both the firmware signature depending on what firmware

There is another command, versionInfo but that is just a more descriptive representation of the firmware.

What get confusing is that in MS2 S is the versionInfo and Q is the signature (queryCommand), in MS1 S is the signature (queryCommand)...

Here is pretty much the whole break down for the signature by MS family:
MS1 base code: Q
MS1 Extra: S
MS1 HiRes: S
MS2: Q
MS3: Q

So it is really MS1 Extra and Hires that are the od ones. One other point to consider there is that MS1 Base code returns a single byte instead of a string based signature. 0x14 But I don't know how many people are actually using the MS1 base code any more any way.