NI VeriStand error -307850

Hello,
I'm using Engine Demo project with VeriStand 2014. I want to execute it in cRIO-9033, so I've included in the system definition file an RT Controller selecting VxWorks for the OS, and using the same IP address displayed for the CompactRIO system in MAX. When I deploy the System Definition File, VeriStand Gateway encountered an error. The ethernet cable is connected and it's running because it's answering to a ping command.
I've read I need to install NI VeriStand Engine on the real-time target (cRIO-9033) but when I select Custom Software Installation from MAX in Remote Systems->cRIO9033->Software->Add/Remove Software, NI VeriStand Engine is not inside possible features to install. Could be this the problem?How can be resolved?
Thank you in advance
Attachments:
error307850.PNG ‏18 KB

The 9033 runs Linux
http://digital.ni.com/public.nsf/allkb/35F1FD98520D6E0E8625783A005AF557
Ni veristand does not yet support that operating system.
Stephen B

Similar Messages

J1939 WITH VERISTAND ERROR

HAI
i am working with Pxi 8108 with veristand 2011, resently i download j1939 custom devices with NI XET 1.4
when i deploy the project in verisatnd i am faceing the following problem
• Starting VeriStand PC Engines...
• 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 deployment group 1...
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details:
Error -1074384758 occurred at Project Window.lvlibroject 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 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.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
• Shutting down VeriStand PC Engines...
• Unloading System Definition file...
• Connection with target Controller has been lost.
NOTE : when tryed to test the CAN interface (PXI-8512/2) using MAX>>Tools>>NI CAN>> RT hardware configuer test. The port1(CAN0) get passed but port2(CAN1) get failed screenhot i attached below
kindly help me in this problem
please help me the problem
Attachments:
CAN error.png ‏29 KB
CAN error 1.png ‏102 KB

Hi Alex,
thank you for your guide!
I have once again remove all NI product installed on my test system, it means deleting directory National Instrument under "C:\Program Files (x86)\". I used also msiBlast.exe to clean up registry.
I installed LabVIEW 2012 SP1 and upgrade it to LV2012 SP1 f5... it's ok until this point.
I opened MAX to see my PXI. Then the same error occured. As your suggestion, i cleaned up MAX database. But, it didn't help. Same error, my RT-Controller was detected, but no chassi.
I try to upgrade NI MAX to the newer version.. then i got this error message during installation:
I am really frustating now.. 2 days just for reinstallation and no progress...
Any help/ideas would be very appreciated!!
thanks again,
Rajamodol
edited:
I have admin right on PC.

Veristand lvmodl error

I haved created a lvmodel and I am trying to execute this model in a PXI 8170 using veristand when I run the model I have this error
• Start Date: 27/05/2014 15:34
• Loading System Definition file: C:\Documents and Settings\All Users\Documentos\National Instruments\NI VeriStand 2012\Projects\Untitled 12\Untitled 12.nivssdf
• Initializing TCP subsystem...
• Starting TCP Loops...
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details:
Error -307853 occurred at Project Window.lvlibroject Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
Possible reason(s):
NI VeriStand: The VeriStand Gateway was unable to establish a connection with the target. Confirm that the target is running and that the VeriStand Engine successfully has started. If you still cannot connect to the target, use MAX to reinstall the NI VeriStand Run-Time Engine to the target.
=========================
NI VeriStand: Server TCP Interface.lvlib:TCP Connection Manager.vi:1
<append>=========================
NI VeriStand: Error 63 occurred at TCP Open Connection in Server TCP Interface.lvlib:TCP Connection Manager.vi:1
Possible reason(s):
LabVIEW: Serial port receive buffer overflow.
=========================
LabVIEW: The network connection was refused by the server.
Target: 192.168.0.2
• Unloading System Definition file...
any idea? I have the sotfware allready installed

You need to look at the real time screen of the target. Engine could seem to be installed in MAX, but it doesn't mean, that it is actually running. If you connect from LV project to the same target in between, it modifies ni-rt.ini. so the engine doesn't boot anymore.
Easy fix is to reinstall just NIVS engine component from MAX.
Certified LabVIEW Architect & Certified TestStand Architect

IRQ timeout error while executing the custom personality fpga in veristand

Hi,
I have gone through the below link and created a custom fpga code to write analog output and digital output through NI 9269 and NI 9472 card respectively.
NI Veristand add on - fpga configuration editor.
https://decibel.ni.com/content/docs/DOC-35499
i was able to import the .fpgaconfig file in veristand system definition window.
When i execute the code, i am getting IRQ timeout error.
Could any one help me how do i debug this error?
i am interested to see how the veristand host code is executing it.

Hi,
Have you tried to simplify the FPGA code? If the issue is related to the VCE, you should post there :
- https://decibel.ni.com/content/message/67188#67188
The developers of this tool will answer you.
Posting the error message or the FPGA code will also help us
Regards,
--Eric

Error 1172 and Error 1 when opening VeriStand

Error 1172 comes up and immediately after Error 1 comes up when I try to open VeriStand. I am remote logging into the computer that this is happening to. I know that just before I logged in, a co-worker was on it and had VeriStand open just fine.
He tried to run a project and got Error -63195; which is a different issue altogether, but wanted to make sure I didn't exclude any information that might be useful.
So I remoted into the computer to try to replicate the error that he got and I can't even open VeriStand without errors. If I click continue the errors will disappear and I am shown the VeriStand start up screen. If I click on "Configure Project" I get Error 1 again. I can't go any further. Does anyone know what the problem is?
Attached are a copy of the errors.
Attachments:
vserror.png ‏49 KB

Hello,
Just saw the second post, you will have to repost to the NI Veristand forums.
Best Regards,
Jignesh P
Applications Engineer

XNET CAN stops upon errors. (PXI-8512 using RT VeriStand)

Hello, I am using the PXI-8512/2 in an electrically noisy environment so I often get errors on the CAN bus. I notice that often the 8512 stops communicating as a result. In my dual port 8512/2, LED #4 which normally blinks ends up turning off. However, I do have other devices listening on the same bus; they report errors but continue to stay alive. Is there anyway I can have the 8512 continue working in the presence of errors? I'm using the XNET custom device for VeriStand 2009 and don't see any error handling options. In fact, I don't get any notification of errors at all. I just notice that my incoming CAN signals stop and my outgoing ones have no effect. Thanks.

Howdy All,
This is a duplicat post. Since the question has to do with the NI XNET Custom Device for VeriStand we will answer on the other thread, please do not reply to this thread.
Joshua B.
National Instruments
NI Services
NI Support Resources
NI Training Resources

Install NI Veristand Engine on PXI via MAX error

The error message I get i attached.
I have avoided this problem by letting someone else install the software on the PXI for me, but I really need this feature.
When the error occurs, all the software packages on the PXI is removed, this happens for all users.
I have tried this on two different PXI's and the same thing happens.
Am I missing some software package? Or do anyone have a suggestion?
Best regards,
Jørgen
Solved!
Go to Solution.
Attachments:
nivserror.png ‏27 KB

Hi,
I've just had the same kind of problem : trying to install Veristand on PXI (8115) from MAX but the paths are not entirely visible (see attached screenshot).
I have tried the workaround by creating the missing folders and .txt files but I stll get the same error message.
For info my installation path is : C:\TST-Tools\National Instruments\
Could anyone help me ?
Regards,
Frédéric
Attachments:
MAX_error.png ‏12 KB

Intermittent, but Persistent ERR_INVALIDDEVICEINDEX Error on VeriStand Workspace

I have a VeriStand 2011 (not SP1) system that sometimes presents error -2000000008 ERR_INVALIDDEVICEINDEX on the Workspace.
If OK is pressed, the error immediately comes back up and will not go away until I kill VeriStand.exe from the Task Manager (the error dialog is of course modal).
Is there anything in the VeriStand code for the Workspace that could be creating this error?
There is some custom code in this VeriStand system, but the RT is perfectly happy (from the console output), I am not using the initDevice.vi anywhere, there are no ActiveX calls in the custom code, and I have disabled most of the host side custom devices (very simple) with no change.
The difficult thing is that this is obviously being thrown by the VeriStand.exe process (as proven by both the glyph and Process Explorer) but I cannot consistently reproduce the error with any System Defintion file found to date.
The host computer is running Windows 7, with .NET 4.0, but I have confirmed that all .NET 3.5 features are enabled.
Thought?
Thanks,
Chris
Project Engineer
Certified LabVIEW Architect
Certified TestStand Architect

Hey Chris!
This is definitely a strange one... Immediately my thought is to attach the VeriStand.exe to Windbg and what more detailed information we can get on this thrown exception.
Obtaining a WinDbg Dump File to Troubleshoot Crashes in National Instruments Software
http://digital.ni.com/public.nsf/allkb/D12F9263065435DA8625784F006ECFD4?OpenDocument
Are you using any custom workspace objects?
I know you mentioned that it shows up sometimes, but can you expand a bit more on the occurrence? Is it reproducible on the order of days, weeks?
Aside from a previous service request you opened, there is little troubleshooting information I can find on this error. However, I want to make sure we are troubleshooting this as thoroughly and quickly as possible. I will continue investigating and see if I can figure out anything else. In the mean time, please try to obtain a dump from Windbg after you run into the error.
Tim A.
National Instruments

Error -1074384569; NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your database to the real-time system.

Hello
I have a VeriStand-Project (VSP) created with my Laptop-Host (LTH) which works with my PXI, while
deploying it from my LTH. Then I have installed the whole NI enviroment for PXI and VeriStand use on a
industrial PC (iPC). I have tried to deploy my VSP from the iPC to the PXI but the following error
message arose on my iPC:
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details: Error -1074384569 occurred at Project Window.lvlibroject 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 0xBFF63147) The database information on the real-time system has been created with an
older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your
database to the real-time system. ========================= 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.
The software versions of the NI products (MAX/My System/Software) between my LTH and the iPC are
almost the same. The only differences are:
1. LabView Run-Time 2009 SP1 (64-bit); is installed on LTH but missing on iPC. The iPC has a 32-bit system.
2. LabView Run-Time 2012 f3; is installed on LTH but missing on iPC.
3. NI-DAQmx ADE Support 9.3.5; something strage on the LTH, because normally I am using NI-DAQmx 9.5.5 and all other DAQmx products on my LTH are 9.5.5. That means NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5.. On the iPC side all three products are 9.5.5.. That means NI-DAQmx ADE Support 9.5.5, NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5..
4. Traditional NI-DAQ 7.4.4; The iPC has this SW installed. On the LTH this SW is missing.
In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
1. LabVIEW Real-Time 11.0.1
2. NI-488.2 RT 3.0.0
3. NI_CAN 2.7.3
Unfortunately the above stated problem still arose.
What can I do to fix this problem?
I found a hint on http://www.labviewforum.de/Thread-XNET-CAN-die-ersten-Gehversuche.
There it is written to deploy the dbc file againt.
If this is a good hint, so how do I deploy a dbc file?
I would feel very pleased if somebody could help me! :-)
Best regards
Lukas Nowak

Hi Lukas,
I think the problem is caused by differenet drivers for the CAN communication.
NI provides two driver for CAN: NI-CAN and NI-XNET.
NI-CAN is the outdated driver which is not longer used by new hardware. NI replaced the NI-CAN driver with NI-XNET some years ago, which supports CAN, LIN and the FLEXRAY communication protocol.
You wrote:
In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
3. NI_CAN 2.7.3
NI CAN is the outdated driver. I think that you should try to install NI-XNET instead of NI-CAN on your PXI-System, to get rid of the error message.
Regards, stephan

Error 1097 while deploying

Hi,
I am having a problem when deploying a model from Veristand (Windows) to a PXI equipment.
Let's start from the beggining: I have written a simulink model and compiled it for Veristand 2014 target. This generates a DLL, that I load it in Veristand at my Windows PC. From Veristand (Windows) I am able to run the model and the results are the same as Simulink. Now I want to run the model in the PXI (PXI-8176 with Phar Lap ETS 13.1). When I try to deploy the model to the PXI target, I've got the following error:
Start Date: 05/05/2015 11:16
Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2014\Projects\DC_Motor\DC_Motor_Ecosim\DC_Motor_Ecosim.nivssdf
Initializing TCP subsystem...
Starting TCP Loops...
Connection established with target Controller.
Preparing to synchronize with targets...
Querying the active System Definition file from the targets...
Stopping TCP loops.
Waiting for TCP loops to shut down...
TCP loops shut down successfully.
Unloading System Definition file...
Connection with target Controller has been lost.
Start Date: 05/05/2015 11:16
Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2014\Projects\DC_Motor\DC_Motor_Ecosim\DC_Motor_Ecosim.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 169.254.104.111...
Processing Action on Deploy VIs...
Gathering target dependency files...
Downloading DC_Motor_Ecosim.nivssdf [71 kB] (file 1 of 4)
Downloading DC_Motor_Ecosim_Controller.nivsdat [6 kB] (file 2 of 4)
Downloading CalibrationData.nivscal [0 kB] (file 3 of 4)
Downloading DC_Motor_Ecosim_Controller.nivsparam [0 kB] (file 4 of 4)
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.lvlibroject 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 might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.
=========================
NI VeriStand: Call Library Function Node in SIT Model API.lvlib:Load Model DLL.vi->SIT Model API.lvlib:Initialize Model.vi->Model Execution.lvlib:Initialize Model Loop Data.vi->NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi->NI VeriStand Engine.lvlib:VeriStand Engine.vi->NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi
Sending reset command to all targets...
After this, I cannot connect to the PXI and I have to reset it.
Any idea?
Thank you,
Jesús M. Zamarreño

Nothing to see in this VI and DLL. For one a DLL is just a compiled code so there is very little to see from the DLL alone. Also a DLL does not contain any other information as to how it is supposed to be called. The implementation of the driver is terrible with all the calls in one single VI and half a dozen booleans to select which one of them to call. It deserves maybe a 6 out of 10 for functionality, a 1 for style and a 2 for cleanliness.
Without the API documentation of that driver DLL, there is absolutely nothing possible to say about the correctness of the CLN configurations. As simple as the functions look, there is still a chance that this configuration got wrong somewhere. Another a least as likely cause is that the DLL itself is poorly written too. If the LabVIEW implementation is any hint for the quality of the DLL driver implementation, then I guess it would be simpler to throw it all away and reimplement the driver purely in LabVIEW.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Trouble with deploying models in NI Veristand to real-time target

Hi All,
I desperately need some help with some application i’m working on. I’m trying to read some accelerometer measurements into NI Veristand but coming up with an error all the time during the deployment stage to the real target which i have atttached. I can’t quite figure out what to do about it. I’m using a real-time device with a PXI-4461 module. I have checked that i can read all sensor measurements in MAX as attached. The error message is as follows:
Initializing deployment...
Waiting for the target to report its state...
Initiating FTP connection...
System Definition File -> Acquisition.in4
Restarting system...
Restarting target into run mode...
The target encountered an error and reset. Verify that the system definition file and the target resources are valid. You must deploy a new system definition file or reboot the controller to correct this problem.
Error -200757 occurred at DAQmx Start Task.vi:1
Possible reason(s):
Measurements: Sample Timing Type is set to On Demand which is not supported for analog input on this device.
Set Sample Timing Type to Sample Clock. You can achieve this whlie setting related properties through DAQmx VIs or functions for configuring timing.
Task Name: Dev6_AI

Duplicate Post.

Problem with the log file path on the Data Logging Control Veristand

Hello everyone,
My problem is that I use a computer as a gateway on the network. It is connected to PXI in Real Time. I have another computer connected to the gateway to read the given PXI. I am unable to record on my local hard drive using the Data Logging Control VeriStand on the second computer. However, it can save me on the hard disk on the network. Moreover, I have no problem to record if the computer is a gateway.
Regards,
Kamal Bouamran

For simplicity, let's call the computer running Veristand Computer A and the gateway computer Computer B.
So, just to clarify, you're running the Veristand workspace on Computer A, which is connected to your network and the RT PXI (on which the system definition file is deployed) through a gateway, Computer B. With this setup, you can't use a data logging control to save a file to Computer A's hard drive. However, you are (from the workspace running on Computer A) able to save a file to Computer B's disk or to another drive elsewhere on your network. Is that all correct?
What happens when you try to configure the control to log to computer A's disk? Do you get an error (and if so, what error)? Does the file path default to a different location?
Also, what version of Veristand are you using? What version of Windows are you PCs running?
Regards,

Veristand

Hi everyone.
I'm trying to compile a simulink model (.mdl) for NI Veristand 2013 by using NIVeriStand.tlc.
Error message occured as following (Under the MATLAB 2009b)
"Real-Time Workshop error in block: "Sample2/Matlab Fcn", block type "MATLABFcn": Not yet supported by Real-Time Workshop"
In this case, I can't use the Embedded Matlab function block (w/ coder.extrinsic(-))instead of MATLABFcn, becasue the function tried here use a "COM-object library" call. (And, when I try to use the Embedded Matlab Function block, Some errors related to the COM-object library call occured.)
your help would be a great help.
thx

Am I understanding you correctly that you wish to access some IMU sensor through a COM port from your model to acquire data? If you have to use an activeX COM-object to communicate with its driver, then I don't personally see any options to do that within your model itself.
One thing you might look into would be to replace the block that gets data from your sensor in your model with a VeriStand Inport block available in the VeriStand palette. This will create an input to the model where the IMU sensor block used to be.
Then when you build your model and import it into VeriStand, it won't directly be reading the IMU sensor through its driver. It will just have a generic input that you can map to from VeriStand. To complete the link, what you might do is look to build a Custom Device for use in VeriStand that can acquire your IMU sensor data through an appropriate driver. You can then add that custom device to the system definition with your model and use the Mappings dialog in System Explorer to connect the IMU sensor output to the input of your model.
This is very common for models in VeriStand. They don't generally directly access any of their IO. Instead, the IO is configured in the VeriStand system definition separately and then mapped into model.
Jarrod S.
National Instruments

Call Stimulus Profile with Veristand API leads to failing test

I wan´t to call a stimulus profile file programmatically. I discovered that there is no VI for that in the LabVIEW VeriStand API (for the legacy stimulus profile editor such a VI exists). But in the Example finder exists a VI which uses the .NET VeriStand API to acomplish this (http://forums.ni.com/t5/NI-VeriStand/Start-Stimulus-Profile-from-LabVIEW/m-p/1789162). Furthermore someone created a Custom Control for the workspace which uses this .NET invoke (http://www.ni.com/example/31335/en/). Both examples work in general but I have one problem which i´m not able to fix:
If I use a "Update Model Parameters From File" step in the stimulus profile to change the parameters of a model the step is going to fail with the error: "Error: -307650. Details: Object reference not set to an instance of an object." This only happens if i use the .NET VeriStand API invoke to call the stimulus profile. If I start the stimulus profile out of the Stimulus Profile Editor this error doesn´t occur and the Model Parameter Update works correctly.
If I delete the "Update Model Parameters From File" step the whole stimulus profile passes just fine.
Has anyone an idea how to fix this issue or how to programmatically call a stimulus profile file with the VeriStand API? Thanks for any suggestions in advance and have a nice day.
H.
Solved!
Go to Solution.

I can reproduce what you are seeing. You can work around this very quickly by making a call to the StimulusProfile method CheckForErrors before starting its execution. This method is called by the Stimulus Profile Editor before it starts execution, and it must have some side-effect that causes the Update Parameters step to work correctly.
Jarrod S.
National Instruments

Execute a .vi in Veristand

I have a model in labview and I want to execute that model in Veristand the problem is that many times I have this error what could be the problem? I don't have any path in my model
I have created .lvproj without problem the problem is when I add the simulation model in Veristand
Attachments:
Error.PNG ‏19 KB

I have followed all this steps and I have the error as well
http://digital.ni.com/public.nsf/allkb/CA90EB4B327B2E5C86257C3D0032F998
Do I need special software?

NI VeriStand error -307850

Similar Messages

Maybe you are looking for