Just recording here for posterity that this issue got resolved, so the links to the revised schemas are here in this archive.

Mike,

I have successfully applied your suggestions, all works well now. The ARINC429 label is now parsed and unparsed correctly, both "standalone" and in the complete messages I have modeled. I have updated both examples on my github repo:
Thanks for your help, most appreciated! Sincerely,

Roger


Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com
Please note: Contributions to the DFDL Workgroup's email discussions are subject to the OGF Intellectual Property Policy


On Fri, Jul 14, 2017 at 3:09 PM, Champagne, Roger <roger.champagne@etsmtl.net> wrote:
Hello,

In an effort to model avionic messages that use the ARINC429 protocol, I am running into an issue with the DFDL attribute "bitOrder", which seems to have no effect.

I have prepared and documented the smallest sample I could come up with on github:

https://github.com/rchampag/dfdl/tree/master/arinc429-label

If anyone could shed some light on this problem, it would be most appreciated. Please keep in mind I am a beginner DFDL user. Thanks in advance!

Sincerely,

Roger


--------------------------------------------------------------
Roger Champagne, P.Eng., Ph. D.
Professeur agrégé, Département de génie logiciel et des TI
Associate Professor, Department of Software and IT Engineering

École de technologie supérieure
1100, rue Notre-Dame Ouest, Montréal, Québec, H3C 1K3, Canada
Bureau / Office : A-4499
Téléphone / Phone : +1 514 396 8825 -- Télécopieur / Fax : +1 514 396 8405

--
  dfdl-wg mailing list
  dfdl-wg@ogf.org
  https://www.ogf.org/mailman/listinfo/dfdl-wg