VeriStand PXI-2510

Similar Questions

• PXI-2510 has no reaction when using NI VeriStand

  Hi all

  I want to use a PXI-2510 in NI VeriStand and I read a document named NI VeriStand module - fault Insertion units OR to: http://zone.ni.com/devzone/cda/epd/p/id/6248

  After deployment, I change my state of the controls in the workspace, but PXI-2510 has no reaction.
   
  Here are my steps:

  1. download the file - 2510_add_on_nivs2011.zip

  2. copy the files in the folder named Custom Device llbs in \National Instruments\VeriStand peripheral 20xx\Custom

  copy files into the folder named models display in \National Instruments\VeriStand models 20xx\Display

  3. open NI VeriStand and use the PXI-2510 as a custom device.

  4 deploy and open the workspace. the default fault chains station is cross with channels of dut. but when I change its station in an open State, PXI-2510 has no reaction.

  Please help me with the problem.

  Best wishes.

  If you use the console Viewer (Tools-> display console), you see error messages published on the screen?

• The PXI-2510 module for 2013 has different names

  Hi, I'm upgrading of VeriStand 2011 to 2013. I downloaded the new device custom of the add-on for the injection of PXI-2510 or http://www.ni.com/example/31248/en/unit. I noticed, however, that the channel names are now different. Instead of strings being 'Ch. 00' thru 'Ch. 67', they are now preceded by the word "Fault", becoming "fault Ch. 0" to "Fault Ch. 67", without the zero not significant.» Therefore, it is difficult to make an upgrade without breaking the mappings for each channel. There are several other functional changes to equipment custom 2013? At the moment I intend just mass compilation my 2011 version into something usable for VeriStand 2013. Thank you.

  Hey Harris,.

  I was surprised to hear this feedback as custom device actually only has a source code that is built in 2011, 2012 and 2013. So there shouldn't be any change in behavior.

  Looking into the source, the chain is indeed "fault c." to which is added a number: ".

  

  So I think that if you have downloaded version 2011 from the Web site, you would also see this behavior. The channels are not rename protected. You are sure that the user not the do not rename them at one point? Speaking of which, you should not re-add the device custom during the upgrade of your system definition. If the custom device was present in the definition of system of 2011, it should be also present in the system 2013 defintiion. Make sure that the custom device is installed on the computer and you should be good to go.

• Install NI Veristand Engine on PXI via error MAX

  I get the error message that I have attached.

  I have avoided this problem by letting someone else install the software on the PXI system for me, but I really need this feature.

  When the error occurs, all the software on the PXI system packages is removed, this occurs for all users.

  I tried this on two different PXI system and the same thing happens.

  Am I missing some package? Or someone has a suggestion?

  Best regards

  Jørgen

  I found a solution that works. Do not know why these files were missing and / or why MAX could not just create them himself.

  I did the following:

  Created a folder + file text for what has been reported missing.

  This resulted in the following structure:

  D:\National Instruments\Shared\Errors\English

  D:\National Instruments\Shared\Errors\French

  D:\National Instruments\Shared\Errors\German

  D:\National Instruments\Shared\Errors\Japanese

  I then added two files for each folder:

  NIVS-modelframework - errors.txt

  NEITHER VeriStand - errors.txt

  And now it seems to work.

• CAN PXI-8461 with VeriStand using

  I have two cards CAN in my chassis: 8512 and a 8461.  The chassis has the latest NI-CAN driver installed and XI-NET 1.0.0.  I can see/access the 8512 without any problem.  I cannot see/do not know how to configure the 8461 for use with VeriStand.  Under MAX, XI-NET does not list the 8461, but I see it in PXI - 1 chassis system.  It don't will not, however, let me do something with it from there.  Any help is appreciated.

  The 8461 is map of series 2, which cannot be used with the NI-CAN driver (OR-XNET has no effect at this point).

  To begin, start in MAX the NI-CAN by accessing tools configuration tool-> NI - CAN-> RT Hardware Configuration.

  Once you have configured the flow rate in bauds, termination, etc etc etc go to System Explorer (SE), add a CAN Port and specify the baud rate according to the settings you selected in MAX. Then import the incoming and outgoing images and you're good to go...

  Tom

• Veristand does co with target rt (pxi) and simulink simulation

  Veristand supports simulation of co with target RT (pxi) and simulink MDL... If he is well wanted to share me partners implementation document

  (Note: we have already implemented .dll depending on model)

  Only the PC engine can do directly co-simulation with Simulink. You cannot use a MDL file directly on a target of RT. This type of co-simulation is certainly not in real time and is not suitable to run on an RT target that performs other urgent tasks. You can have multiple targets in your system definition, then you might have an RT target and a target PC. But you need means of communication between the two target types. Which may include a model or a custom device.

• AutoStart VeriStand using LabView project

  Hi all
  I want to manage through selection LabView and deployment of projects on my PXI system.

  In order to know which project is running that only, I founded the solution to create an ad-hoc ALIAS that appears at the top of the list. Is there anyone who knows a smarter way?
  Attached is my example .VI
  Thank you very much for your answers

  You can watch the NI VeriStand - Get function System State.vi located in the NIVS palette. Notably, she returns the path to the definition file deployed where he is already running a (and you can use Connect to System.vi to run a definition instead of a project file). It is perhaps more convenient than your alias workaround solution!

• readings of Veristand instruments with a remote system

  I'm new to the National Instruments and Veristand material and I'm trying to use an instrument with Veristand to see if I can get readings of this instrument. I use a PC with Windows Vista and I am connected via a network to a PXI-8108 controller in a PXI-1050 chasiss chassis. The instrument is just a thermocouple which I use to become familiar with everything. The thermocouple is connected and the connection SCB-68 block which is connected to a PXI-6221 multifunction data acquisition in the chassis. I am able to create a task in MAX under remote system and everything seems to work. What I want to do is to get the readings in Veristand, and I don't know if I need to create a custom device that is related to the acquisition of data somehow, or if there is another way to do it. I created the DAQ hardware in the system Explorer, but I see no way to link the real DAQ hardware on the remote system. I wonder if anyone can help with this.

  All advice is appreciated.

  Thank you

  You can read the value of your thermocouple directly from VeriStand channel, but the process is different than using MAX.

  In the system Explorer, add your DAQ hardware that is wired to your SCB-68. Make sure that you specify the same name (i.e. ' Dev1'), which is the make up something, you also that you have imported the peripheral canal which hangs to the thermocouple (i.e. "ai0"). There is no way in System Explorer to specify that this channel should be scaling of thermocouple. VeriStand initially served this string value value brute power. However, you can set the limit high and low for this channel to something small as +/-1V, since thermocouples have very small readings.

  You add the balance to your system separately after the deployment of the system definition, you have created the target of RT. For this to connect to the target using the workspace and select the tool to the workspace on the Tools menu called channel scaling and Calibration Manager.

  In this dialog box, you will see your TV listed DAQ. Navigate in the dialog box assign an appropriate scale of thermocouple to your channel. Once this is done, the target will remember the scale for this channel until what crush you.

  I would like to know how it goes...

• DAQ in Veristand readings do not match the MAX readings

  I have three accelerometers attached to a block of SCB-68 connection that is connected to an NI PXI-6221 data acquisition on a RT system. I have created a task for each accelerometer in MAX and have tested each one to see that it works and gives appropriate readings. Veristand, I created a workspace file to test the accelerometers and I the acquisition of data created in the system Explorer. After the deployment of the system definition and running workspace, I created three simple graphics and connected ways appropriate to each curve. I reduced tensions in the same way exactly, I put on the scale the to the MAX, but for some reason, one of the accelerometers gives tensions that are far away from where they should be. The other two accelerometers work perfectly and one that does not works perfectly in MAX. So I don't think that there is a problem with the accelerometer, it just would not work in Veristand for some reason any. I wonder if there is someone who can at least have an idea of why something like this could happen. I have all three accelerometers that are related to the same connector block and I wonder if put too much in a block would do something like that.

  Any help would be appreciated.

  Thank you

  For all those who can do I understand what the problem is. The default setting in Veristand read channels of differential measures, so anything connected to channels 8 or below is mapped to both channels, (e) and has (n + 8), where n is the number of the channel. For me to use the accelerometers in the way I set up the I just need to go to unique benchmark measures ended (CSR) in the system Explorer.

  Once again thanks for your help.

• Multiple problem templates Veristand 2014

  Hello.

  I have a strange behavior with my models running in Veristand. I am a very experienced with Labview Veristand user and this is the first time I've seen this problem.

  My HW is a pXI8110 with bit of Council set up to 1000 Hz.

  I have compiled several models of Labview in Veristand (14 to simulate the ECU of a vehicle plant). There is not so complex. These models read data from the CAN, run the code and connect the outputs to other models or CAN. I have also a custom device consumes 50% of 4 hearts.

  When I begin to test the system, I can verify that several code in some models is not running. I mean, I have 6 entries in a single model can and I see all the values on the 5 entries are working properly, but the code corresponding to the last entry does not work correctly. I checked that the maps are good and I also had the last value entered without any positive result.

  I also tried to change the order of execution of models, but it still does not work. I also increased the decimation of this model (instead of 10ms to 100ms), but it does not work.

  If I try the model in a project Veristand PC it works well, so I wonder if it can occur due to a leak of cycle time, because PXI is not able to run all the code model.

  You have any idea what to check?

  Thanks in advance.

  Miguel.

  Hello.

  I did several tests and model works again increase the decimation.

  To avoid this again once I generated a "code execution time-out" in each model using counters and I check if this time is greater than the actual runtime set in Veristand. In this case, I generate a warning. Then I manually adjust orders and the model run time. Unexpected results can be found if this happens again.

  BR,

  Miguel.

• VeriSTAND deployment stage bottleneck...

  After hit [F6] on the keyboard, VeriSTAND begins deployment of model tasks. However, I keep noticing it gets stuck at some point in the process. Using the web console for the particular machine, I see computing seems stuck in State "waiting for models lines stop...» ». So far, the only cure for this is the reboot of the machine using NI MAX.

  What could be the cause of this? Is there a better use the VeriSTAND?

  Notes:

  The deployment computer target: OR PXI-e 1085 BONE PharLap RT of running

  Development machine: Dell laptop running Windows 7 OS

  Software: VeriSTAND and LabVIEW 2015

  Currently implementing my model as a device for VeriSTAND.

• VeriStand 2015 honor assignment processor PCL

  By using a PXI-8110 and NI Veristand 2015, no matter what I put the assignment of processor PCL to in the system definition, the PCL always land on the CPU 0. I can confirm it with the CPU load monitor and a backtrace (attached).

  The data processing loop moves to my assignment as expected.

  Thanks for reporting this, Stephen! R & D focuses on this issue. We believe that we have reduced the cause of this problem, and we are evaluating a solution.

• Increase the rate of target on Veristand

  Hello

  I am a novice user of Veristand. I'm doing a feedback from control with the help of a compactRIO:

  RT OR cRIO-9024

  Chassis cRIO-9113

  9220 and 9263 modules.

  I use Veristand with a compiled since Simulink model to make my will.

  I want to be able to reach frequencies of 10 KHz loop or more, but the loop of the target rate freezes the system when I try to go beyond 700 Hz.

  Is it possible to do?

  My model is very simple, for now, I'm simply connect the 9220 1 entry at the exit of the 9263.

  Thank you in advance,

  Kind regards

  Rates

  Hi prices.

  The 9024 is unable to run NI VeriStand at your desired pace. As you can see, it tops out around 700 Hz. There are several reasons for this, but the end result is that you will need different hardware to run at your desired pace. A 9082 will be much faster, and a SMU-8135 will be even faster than that. Also if you use PXI, if you only need of IO and no treatment only Co, our PXI DAQ devices allow you to hit the NIVS rates much faster than the PXI FPGA devices.

  Good luck!

• Deployment of TestStand asking Veristand

  Hello

  I'm trying to deploy a Teststand system. Usually, I try to install with all the necessary drivers test computers before hand, but this time I need to create a full installation package.

  The components that I need to install are:

  TestStand TERM 2014

  Runtime LabVIEW 2015 (32 bit)

  DAQmx run-time engine

  VISA run-time engine

  When I select the addiational components a few ones are selected as well.

  Some modules of LabWindows/CVI runtime (Teststand seems to need them)

  Performance of PXI Platform Services (DAQmx seems to need)

  NEITHER engine VAriable 2015 (Teststand seems to need)

  A couple of them seems a little weird but of course, no problem.

  I plugged my USB with the software bundle 2015 he asks.

  But now he also asks me for multimedia path NI Veristand 2015. It is not included on my USB drive apparently have, but even if that were the case, why a deployment using standard drivers and LabView Teststand should Veristand installation media?

  TestStand deployment is a little tricky with even with the new versions, but that's all just ridiculous.

  Someone at - it had the same problem and if so, how do solve you?

  Best regards

  Nimgaard

  Hi Nimgaard,

  It is possible that on your development system, one of the required common components was originally installed in the media Veristand.  for this reason, the framework of the installation program will ask you the mdeia where the product has been installed from.  Part of the Setup program does include that which is indicated on the installation in TestStand Deployment Utility dialog box, i.e. the products you select and all dependencies of these products.  If you do not have media veristand, you can download it from the Web site of OR here:

  http://www.NI.com/download/NI-VeriStand-2015/5542/en/

• Adding personality to VeriStand FPGA

  Hello

  I am trying to add a personalized my VeriStand configuration FPGA. I use PXI-7853R in 1044 with PXI-8110 controller chassis.

  The FPGA model itself is running properly and the fpgaconfig file is modified. The fpgaconfig and the bitfile are added to the propper directory. Now when I want to add it as a target FPGA, I get the following error:

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

  LabVIEW: File not found. The file could be
  moved or deleted, or the path may be incorrectly formatted for the
  Operating system. For example, use- as Windows path separators: on Mac OS
  X, and on Linux. Check that the path is by using the command prompt or
  File Explorer.

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

  NOR-488: The non-existent GPIB interface.

  C:\Documents
  and All Users\Documents\National Instruments\NI VeriStand
  2010\FPGA\PXI-7853R HighSpeed Interfaces.lvbitx

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

  I checked

  but the http://Digital.ni.com/public.nsf/allkb/2FA525A8585A92E9862566EE002A3755 was not able to address the issue.

  I enclose a few screenshots to give an image of my installation.

  p.s. I'm not planning to use the GPIB.

  Error 7 is a generic "file not found" error in LabVIEW.  Unfortunately, I think the NOR-488 driver also uses the error code 7 for a GPIB interface to the nonexeistent, and the error description lists all possible sources.  In your case, the error is due to a missing file and has nothing to do with the GPIB.

  I re - check the bitfile name in the .fpgaconfig and verify that it is the path listed:

  C:\Documents
  and All Users\Documents\National Instruments\NI VeriStand
  2010\FPGA\PXI-7853R HighSpeed Interfaces.lvbitx

  If you can get the files .fpgaconfig and .lvbitx, we try here and I hope that give you the best guidance.