AIT ARINC 429 Add-On Feedback

[StephenB]

Can you try this test build? Check the loop status channels and RX data

ftp://ftp.ni.com/outgoing/test 2.0.1 ait429.zip

[BenjaminM]

I don't have right now the other card I have to wait an hour or so for data test.

But input loop duration is now updating with the new build.

If data test is also ok could you say me which VI I should modify to have everything working so that I don't have to do my specific modification again.

Thank you very much for your answers

Benjamin

[BenjaminM]

Just did data test and we get nothing in Veristand.

[StephenB]

BenjaminM wrote:

I don't have right now the other card I have to wait an hour or so for data test.

But input loop duration is now updating with the new build.

If data test is also ok could you say me which VI I should modify to have everything working so that I don't have to do my specific modification again.

Thank you very much for your answers

Benjamin

Glad that fixed input loop duration at least.

You can see which VI I changed in the commit log here:

https://github.com/NIVeriStandAdd-Ons/AIT-ARINC-429/commit/fac8b9da8f6cb033c5b93658abaf34d62c1ac5c9

[StephenB]

BenjaminM wrote:

Just did data test and we get nothing in Veristand.

OK I'll keep looking

[StephenB]

BenjaminM wrote:

Just did data test and we get nothing in Veristand.

What channel numbers are you using for RX? Any way you can share your database?

[BenjaminM]

We tried with a modified loopback not the full configuration.

Test on label ID 34. Other labels where just here to see if it didn't load the CPU to much but it doesn't look like it.

<?xml version="1.0" encoding="UTF-8"?>

<board429 xmlns="http://www.aviftech.com/Schemas/Databus/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.aviftech.com/Schemas/Databus/ file:///C:/Program%20Files%20(x86)/AIT/Flight%20Simulyzer%20(VISA)/AIT_429.xsd" sdiModeEnabled="false">

    <boardIndex>1</boardIndex>

    <channel429 channelNumber="1" name="Wheel Input" channelSpeed="HIGH_SPEED_CHANNEL">

        <Rx>

            <chronMonitor/>

            <labels>

                <label labelId="34">

                    <buffer name="1" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="07">

                    <buffer name="Right Wheel SpeedIn" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="08">

                    <buffer name="AltitudeIn" depth="1" parityEnabled="true"/>

                </label>

            </labels>

        </Rx>

    </channel429>

    <channel429 channelNumber="2" name="2" channelSpeed="HIGH_SPEED_CHANNEL">

        <Rx>

            <chronMonitor/>

            <labels>

                <label labelId="34">

                    <buffer name="2" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="07">

                    <buffer name="Right Wheel SpeedIn" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="08">

                    <buffer name="AltitudeIn" depth="1" parityEnabled="true"/>

                </label>

            </labels>

        </Rx>

    </channel429>

    <channel429 channelNumber="3" name="3" channelSpeed="HIGH_SPEED_CHANNEL">

        <Rx>

            <chronMonitor/>

            <labels>

                <label labelId="34">

                    <buffer name="3" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="07">

                    <buffer name="Right Wheel SpeedIn" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="08">

                    <buffer name="AltitudeIn" depth="1" parityEnabled="true"/>

                </label>

            </labels>

        </Rx>

    </channel429>

    <channel429 channelNumber="4" name="4" channelSpeed="HIGH_SPEED_CHANNEL">

        <Rx>

            <chronMonitor/>

            <labels>

                <label labelId="34">

                    <buffer name="4" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="07">

                    <buffer name="Right Wheel SpeedIn" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="08">

                    <buffer name="AltitudeIn" depth="1" parityEnabled="true"/>

                </label>

            </labels>

        </Rx>

    </channel429>

    <channel429 channelNumber="5" name="5" channelSpeed="HIGH_SPEED_CHANNEL">

        <Rx>

            <chronMonitor/>

            <labels>

                <label labelId="34">

                    <buffer name="5" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="07">

                    <buffer name="Right Wheel SpeedIn" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="08">

                    <buffer name="AltitudeIn" depth="1" parityEnabled="true"/>

                </label>

            </labels>

        </Rx>

    </channel429>

    <channel429 channelNumber="6" name="6" channelSpeed="HIGH_SPEED_CHANNEL">

        <Rx>

            <chronMonitor/>

            <labels>

                <label labelId="34">

                    <buffer name="6" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="07">

                    <buffer name="Right Wheel SpeedIn" depth="1" parityEnabled="true"/>

                </label>

                <label labelId="08">

                    <buffer name="AltitudeIn" depth="1" parityEnabled="true"/>

                </label>

            </labels>

        </Rx>

    </channel429>

</board429>

[StephenB]

Hi Benjamin,

I cannot seem to find any issue here. I appear to be receiving RX data fine. Are you sure your external system is writing the labels that you're set up to receive?

Keep in mind that the XML shows the label #s in hex. So label 34 is really hex 34 or octal 64 or decimal 52. You can see the label #s in your sysdef page in any format you like.

[BenjaminM]

Hello,

Yes in fact it works fine if I define data parameters in XML file.

I was trying it adding a parameter directly from VeriStand and that is not working for me when I do that.

Since I will always have all data parameters specified in the XML configuration that will not be a problem.

[StephenB]

Hi BenjaminM,

Can you post both sysdefs? The one that doesn't work and the one that does? This would help me debug. there shouldn't be anything different when creating through the GUI vs importing.

Thanks!