Acyclic messages configured with SDI tag do not set SDI bits correctly
Karl-G1 opened this issue · 0 comments
Karl-G1 commented
Describe the bug
As implemented today, the SDI bits are not getting set in the transmitted data word, so different label + SDI combos will be transmitted as the same message (if they contain the same parameter values).
This was found while implementing more thorough system tests in #227
To Reproduce
Steps to reproduce the behavior:
- loop back connectors P2 and P3 on the same core of a 32-channel ARINC 429 module
- Use the attached configuration files to configure an instance of the custom device, and enable logging
- Toggle the trigger channels for Acyclic Tx messages Label 10_1 and Label 10_2
- Un-deploy to save the log file
- Inspect the log file to see that Channel 0 does have 2x received label 10 messages, but both report the SDI value as 0
Ballard Multichannel Tx and Rx.zip
| time stamp | channel | label | sdi | data word |
|---|---|---|---|---|
| 6.533898 | 7 | 10 | 0 | 2148098058 |
| 3.549434 | 0 | 10 | 0 | 2147995658 |
| 3.549794 | 0 | 10 | 0 | 2147995658 |
Expected behavior
Acyclic Tx messages configured with the SDI tag set to 01, 10, or 11 in the parameters file should be able to be looped back to unique channels for Rx with the same settings.