Time out error while deploying custom device with CAN...

[swbpnole]

I am attempting to deploy a custom device with a CAN Frame Out session. I am getting what looks like a timeout error:

• Start Date: 4/28/2016 11:50 AM
• Loading System Definition file: \\tsclient\G\stash\Sample-integration\veristand\Sample CAN Device\Sample CAN Device.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 PXI RT PharLap.
• Sending reset command to all targets...
• Preparing to deploy files to the targets...
• Starting download for target PXI RT PharLap...
• Opening WebDAV session to IP 10.64.244.90...
• Processing Action on Deploy VIs...
• Deploying XNET database: j1939
• Gathering target dependency files...
• Downloading Sample CAN Device.nivssdf [285 kB] (file 1 of 4)
• Downloading Sample CAN Device_PXI RT PharLap.nivsdat [806 kB] (file 2 of 4)
• Downloading CalibrationData.nivscal [0 kB] (file 3 of 4)
• Downloading Sample CAN Device_PXI RT PharLap.nivsparam [0 kB] (file 4 of 4)
• Closing WebDAV session...
• Files successfully deployed to the targets.
• Starting deployment group 1...
• Deployment group 1 is ready.
• Preparing to synchronize with targets...
• Querying the active System Definition file from the targets...
• Target synchronization complete.
• Target PXI RT PharLap is online.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error -1074384886 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):

NI-XNET:  (Hex 0xBFF6300A) The operation timed out. Solution: specify a timeout long enough to complete the operation, or change the operation in a way that it can get completed in less time (e.g. read less data).
=========================
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 >> HP Loop.lvlib:HP Loop Main.vi

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
• Stopping TCP loops.
Waiting for TCP loops to shut down...
• TCP loops shut down successfully.
• Unloading System Definition file...
• Connection with target PXI RT PharLap has been lost.

I request a Frame Out Stream session in the initialization stage:

The "Claim by Addr" VI is a LV-provided VI in that I lifted it from the J1939 example VI. I have used it before.

Can anyone see or know of anything that I am missing?

[swbpnole]

Further investigation: There is a possibility this maybe related to the size of the database. I will continue on that vector...

[Queen_Nadine]

Hi swbpnole,

Thanks for the update. Please let us know if your tests reveal anything. Some other steps to try:

1. Start with a blank SysDef file and import one component at a time. (i.e. start by just deploying blank sys def. then just one CAN port defined. then customer device. etc)

2. When you say you've been working from the VI template, have you been working from the Github J1939 Custom Device source?

Regards,

[swbpnole · Accepted solution]

I have not been working with the J1939 Addon, but further thinking has lead me to realize I probably should. I will close this issue.