-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementing BDS decoding using fixed length definitions #41
Comments
Hi Diego, BDS decoding would be very useful feature for me as well, but unfortunately it is not so easy to implement. The problem is that the BDS format does not follow Asterix formats, and there are too many conditional formatting (e.g. format of a field depends on the value of previous field). |
BDS format is fixed, at least for the most common ones (BDS0,5 BDS0,6 BDS1,0 BDS1,7 BDS4,0 BDS5,0 and BDS6,0). On the other hand, BDS3,0 has some conditionals that are as you said. Some time ago I did my own asterix decoder, and used a similar trick (to use a dataitem definition to describe BDSs). The only addition is to write to code needed to reference the new definitions from the values in I048/250/bds1 & I048/250/bds2. These are the xml definitions I use with my own version, they can be useful as an example. (This is one of the few things remaining that stop me from using your parser for everyday tasks).
|
Thanks for that. I will try to implement it in code. |
#41 Implementing BDS decoding using fixed length definitions
There is a first version of BDS decoding using same format for BDS definition as for Asterix messages. |
Looks very good! On Fri, May 6, 2016 at 2:28 PM, Damir Salantic notifications@github.com
-- Use of a keyboard or mouse may be linked to serious injuries or |
#41 Implementing BDS decoding using fixed length definitions
Implemented BDS decoding (for now only registers 40,50,60). Merged to master. |
Hi Damir,
Do you think is it possible to define the bds contents inside I48/250 (ie. bds40, bds50, bds60) using fixed length definitions? Once defined, is it possible to reference them inside the cat48 xml?
I could provide examples for all of them, if needed, and also write the new xml files, if it is feasible.
What do you think?
The text was updated successfully, but these errors were encountered: