VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

J1939 Custom Device - Veristand 2017

I have the built in files for 2017 version to add this custom device. But if I click on the outgoing or incoming messages there is an 1162 (PFA) , while if I deploy this error comes:

 

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

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

 

Details:

Error -307608 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi

 

Possible reason(s):

 

NI VeriStand:  The custom device does not provide a valid source distribution for the target specified. Specify a different target or contact the creator of the custom device for further support.

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

NI VeriStand:  NI VeriStand Gateway.lvlib:VeriStand Server Wrapper.vi >> NI VeriStand Server.lvlib:NI VeriStand Server.vi >> NI VeriStand Server.lvlib:System Storage FG.vi >> System Storage Compiler.lvlib:System Storage To Multiple Engine Binary.vi >> Engine Data Compilation.lvlib:System Storage to Engine Binary.vi >> RT Data Management.lvlib:Populate Binary Tree Storage for RT.vi >> RT Data Management.lvlib:Populate Binary Tree.vi >> RT Data Management.lvlib:Copy Custom Device Node Properties.vi >> Custom Devices Storage.lvlib:Get Device Driver VI.vi

 

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

 

Dies anyone has any solution for this? I tried source code from github but it doesnt builds, due to unending dependencies. So if anyone has any built files or know how these errors can be fixed for the 2017 version, will really help.

0 Kudos
Message 1 of 9
(233 Views)

The error has to do with your built file.

Try the built file from Release j1939-addon-2017_4.2.0+028 · NIVeriStandAdd-Ons/J1939-Custom-Device · GitHub

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
0 Kudos
Message 2 of 9
(208 Views)

I already have this source code link but it doesn't built, due to dependencies & sometimes there are other errors. Is there a link from where I can access the built files directly?

0 Kudos
Message 3 of 9
(187 Views)

The built file is available in the released link I shared.

Capture.JPG

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
0 Kudos
Message 4 of 9
(160 Views)

Thank you for that!

 

But after adding the custom device to the sysdef & after deploying the project, following error is coming:

 

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

Details:
Error -1074384758 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi

Possible reason(s):

NI-XNET: (Hex 0xBFF6308A) The interface name given does not specify a valid and existing interface. Solution: Use a valid and existing interface. These can be obtained using MAX, XNET system properties, or the LabVIEW XNET Interface IO name. If you are using CompactRIO, refer to the topic "Getting Started with CompactRIO" in the NI-XNET Hardware and Software Help.
=========================
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

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

 

Any idea how can I fix this? I don't think I can change the vi & do a rebuilt.

0 Kudos
Message 5 of 9
(148 Views)

The custom device has nothing wrong.

Are you using a valid NI-XNET interface name same with the one defined in NI MAX?

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
0 Kudos
Message 6 of 9
(111 Views)

I dont know where I can check that. When I add the custom device it only asks for XNET database & XNET Cluster name which auto-populates, so

 

1. There is no option to select XNET Interface Name.

2. If I remove the Custom Device from my sysdef, my project gets deployed successfully, this error is coming only when I added the J1939 AddOn.

0 Kudos
Message 7 of 9
(91 Views)

You can change the XNET Interface in the Main Page.

ZYOng_1-1746919163156.png

 

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
0 Kudos
Message 8 of 9
(78 Views)

The name comes by default in Veristand & attaching the snapshot of that (Left side NI MAX, Right Side is Sysdef)

 

Star101_0-1748094105832.png

 

 

 

But the error is still same during deployment:

 

• Closing WebDAV 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 -1074384704 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi

Possible reason(s):

NI-XNET: (Hex 0xBFF630C0) A property value was out of range or incorrect. Solution: specify a correct value.
=========================
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

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
• Sending reset command to all targets...
• Stopping TCP loops.

0 Kudos
Message 9 of 9
(21 Views)