NI VeriStand Add-Ons Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

AIT ARINC 429 Add-On Feedback

Hi

I passed to 1.7 version and I have the same error as before.

When deploying, the system copies successfully the required files, but I think when trying to initialize the board driver The error appears.

• Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2011\Projects\Prog\Prog.nivssdf

• Preparing to deploy the System Definition to the targets...

• Compiling the System Definition file...

• Initializing TCP subsystem...

• Starting TCP Loops...

• Connection established with target Controller.

• Sending reset command to all targets...

• Preparing to deploy files to the targets...

• Starting download for target Controller...

• Opening FTP session to IP 192.168.1.46...

• Processing Action on Deploy VIs...

• Serializing 429 Database...Done!

• Gathering target dependency files...

• Downloading Prog.nivssdf [51 kB] (file 1 of 3)

• Downloading Prog_Controller.nivsdat [113 kB] (file 2 of 3)

• Downloading AIT 429 RT Driver VI.vi [68 kB] (file 3 of 3)

• Closing FTP session...

• Files successfully deployed to the targets.

• Starting deployment group 1...

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:

Error 1097 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

Possible reason(s):

LabVIEW: An exception occurred within the external code called by a Call Library Function Node. The exception may have corrupted the memory LabVIEW. Save any work in progress to a new location and restart LabVIEW.

=========================

NI VeriStand:  NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

• Unloading System Definition file...

• Connection with target Controller has been lost.

Is it necessary to have a compatible board to deploy succefully ?

If we didn't have a compatible board, can we deploy anyway ?

Thanks

0 Kudos
Message 41 of 193
(5,486 Views)

Is it necessary to have a compatible board to deploy succefully ? Yes

If we didn't have a compatible board, can we deploy anyway ? No

However, you shouldn't get that error. It should be a different error. Can you right click your target in MAX and select -> Create report. Then select "Technical Support report". After creation, attach it here. (Click use advanced editor in the top right to add attachments).

Stephen B
0 Kudos
Message 42 of 193
(5,486 Views)

Hi

Sorry for the delay

Usualy we are waiting for a new ATI board

I wil contact you to debug the custom device once I get the board

Regards

0 Kudos
Message 43 of 193
(5,486 Views)

Mmonterrat,

Can you provide your flight simulyzer file for me to test with? Select "Use advanced editor" in the top right of the reply box and then upload it as an attachment. If it is private, you could send it to me in a personal message.

Thanks!

Stephen B
0 Kudos
Message 44 of 193
(5,486 Views)

Ci-joint un fichier simple créé sous Flight Simulizer que je ne peux importer sous Veristand (message d'erreur ci-dessous).

Merci de votre retour

0 Kudos
Message 45 of 193
(5,486 Views)

I think I know the problem. The custom device is failing to read TX transfer named "Transfer_1"'s scheduled data, because it is not a scheduled transfer... it is a block transfer. Change it to a scheduled transfer and it works. However, the RX labels are not working... I'm looking into that now.

Stephen B
0 Kudos
Message 46 of 193
(5,486 Views)

OK The reason the RX labels do not show up is because you have them on the same channel as the TX labels. A single ARINC 429 channel can only be RX or TX. If you move your RX labels to a different channel, it works fine

Stephen B
0 Kudos
Message 47 of 193
(5,486 Views)

Hello,

I use the ARINC custom device and I have an error when I refresh the database.

My xml configuration file contains only one Rx channel with 2 or 3 messages. If I add or delete a message and refresh the database in VeriStand it seems to be working but the error 1031 appears and the Warning on the main interface doesn't disappear.

Do you have the same error? Have you got an idea to solve this error?

(Windows7, VeriStand 2012, AIT_429_v1.7_2012)

Best regards

BugARINC.jpg

0 Kudos
Message 48 of 193
(5,486 Views)

I'm not sure why you always see the warning. Is the file read only?

I reproduced error 1031. I will post a fix.    

Stephen B
0 Kudos
Message 49 of 193
(5,486 Views)

I just posted 1.7.1 that fixes the error

Stephen B
0 Kudos
Message 50 of 193
(5,486 Views)