LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-XNet Application Does Not Work Outside of Host Computer

Hello,

 

I have developed an application that logs analog voltage signals and CAN messages. I can sucessfuly run the application on the host computer that the application was programmed on, however after creating the installer and distributing the installer to other computers, only analog voltages can be recorded. When I attempt to record CAN messages on computers on which the installer was brought over, the application does not respond. 

 

I don't think it is a hardware problem since I can view CAN messages on NI's bus monitor using the computers which the application was installed on.

Also, when creating the installer on the host computer, I chose to include recommended installers as per the project installer build specifications.

 

Is there anything I am missing that is preventing the application from viewing and recording CAN messages?

 

additional info:

I have sucessfully provided a signal list to "XNET Create Session (Signal Input Waveform).vi", however this .vi is unable to provide an XNET session output to "XNET Read (Signal Waveform).vi".  

I know this because if I place an indicator between the XNET Create Session.vi and XNET Read.vi, the host computer indicates: ___xnetSesn#00000001, whereas other computers indiciate: ___xnetSesn#00000000

0 Kudos
Message 1 of 2
(2,886 Views)

I would try to create a debuggable executable to get additional information.

 

http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70

 

This will give you more debugging options which I am sure will give you information.  My first guess would be to look at how you are referencing the hardware.  If you have a constant input for your create XNET session (CAN 1 for instance) make sure your alias is identical. Another thing to check would be whether you can run the executable you built on the same computer you were developing on. If you are able to do that I would suspect that the problem is with how you are referencing your hardware.

Matt J | National Instruments | CLA
0 Kudos
Message 2 of 2
(2,815 Views)