Solution
Here are some frequently asked questions about configuring an XML file for the Astronics Ballard MIL-STD-1553 modules.
- How do I install the Astronics Ballard LabVIEW driver API?
- Where can I find API examples?
- What is the XML Configuration File?
- How should I create a BTI XML Configuration file?
- Where can I find example XML files?
- Where can I find the Driver API help?
- What is the meaning of the bufferMaxEntries property when adding a message buffer?
How do I install the Ballard LabVIEW driver API?
You can download the Astronics Ballard Avionics Driver here. This will install LabVIEW support for both MIL-STD-1553 and ARINC-429 modules, as well as the Ballard BTIXMLEdit application.
Where can I find API examples?
Once you have installed the Astronics Ballard Avionics Driver, examples will be installed to the <Program Files>NI\LVAddons folder. For example, if you want to find the examples for 64-bit LabVIEW, you can find them in C:\Program Files\NI\LVAddons\ballardinstr64\[driver version]\examples\Astronics Ballard Technology. In that folder you can find examples for various API operations. The BTI1553Lib folder contains the MIL-STD-1553 examples.
What is the XML Configuration File?
The Astronics Ballard Avionics Driver can use XML configuration files to define the functionality of the device. These BTI XML Configuration files can define properties such as transmission rates, buffers, number of channels, and what data will be transmitted and received on those channels. The XML file must comply with the BTI XML Schema located at C:\Program Files\NI\LVAddons\ballardinstr64\[Version]\instr.lib\BTICardLib\XML Schema\BTI.xsd
How should I create a BTI XML Configuration file?
The recommended method of creating a compatible file is to use the BTIXMLEdit application. This application installs with the Astronics Ballard Avionics Driver and allows you to create XML files from scratch or using protocol specific templates and will ensure that the created file complies with the BTI XML Schema. To create a configuration file for MIL-STD-1553:
- Launch the application in the Start menu by going to Start»All Apps»Astronics Ballard Technology»BTIXMLEdit
- Select New 1553 Configuration. You will see that a coreConfiguration and a single 1553 channel are added to the file
- To add a Bus Controller, select channel1553 ID2»simulation and then click the Add 'busController' button
- To add a Remote Terminal, select channel1553 ID2»simulation»remoteTerminals and then click the Add 'remoteTerminal' button
- Continue to add additional components to the configuration, such as messages, message buffers, subaddresses, modeCodes, etc.
- Click the Save button to save the file to disk. You can now reference this file in the LabVIEW API using the Configure All From File function
If you are unfamiliar with what needs to be configured in the XML file, you can open up one of the example XML files that ship with the driver in the BTI XML Editor to see how it is configured. Refer to the next section for information about where to find those example files.
Where can I find example XML files?
Each of the shipping examples mentioned above will contain example XML files that are compatible with these cards. Some examples will contain separate XML files for configuring the device Core (which is the main protocol interface on the card) and configuring the Channels on that Core.
Where can I find the BTI Driver API help?
The Ballard LabVIEW Instrument Driver Guide contains the fundamentals of using the BTIDriver in LabVIEW. It includes valuable topics, such as how to configure frame transmit timing, creating XML files, and protocol-specific guies. It can be found in the following locations, or by clicking on Detailed help in the Context Help tool in LabVIEW for any of the API functions:
- C:\Program Files\NI\LVAddons\ballardinstr32\[version]\help\Astronics Ballard Technology\Ballard LabVIEW Instrument Driver Guide.chm
- C:\Program Files\NI\LVAddons\ballardinstr64\[version]\help\Astronics Ballard Technology\Ballard LabVIEW Instrument Driver Guide.chm
- C:\Program Files (x86)\Astronics Ballard Technology LabVIEW Driver\Library Help\Ballard LabVIEW Instrument Driver Guide.chm
What is the meaning of the bufferMaxEntries property when adding a message buffer?
The bufferMaxEntries property defines the number of complete messages that can be stored in the buffer. Setting this value to 1 indicates that the buffer is used for "current-value messages". A current-value message contains only a single data item "slot." For transmit messages, this means that this same item is transmitted over and over until the data is updated in-place from the application. For receive messages, this means that there is only one spot to hold received data and each received message will overwrite the data in that slot.
Setting bufferMaxEntries to a value >1 indicates that messages will be buffered using either a FIFO or a circular buffer, as defined in the bufferType property. Refer to the Ballard LabVIEW Instrument Driver Guide for more information on configuring buffered messages.