VeriStand 2011.1

Similar Questions

• Problems VeriStand 2011 RT and SCXI-1540

  Good afternoon

  As in the topic, we have problems with our card module SCXI-1540 that we use to acquire a mixed selection of RVDT and resolvers.

  Specifically, we have our facility on Veristand 2011 on a target of RT who has a device custom control map SCXI chassis PXI-1050 and the NI PXI-6221 card, everything is fine but every now and then the map 1540 suddenly start showing a rolling measure of angle for resolution programs.

  By checking with an oscilloscope, resolvers entries are good, but we notice that when the event occurs, the excitement somehow pass set 5 kHz to 10 kHz and even by the cancellation of the deployment and redeploy the project and verify that the property node DAQmx channel used to set the frequency of excitation is the correct setting of 5 kHz and does not return an error There is no way to get the channel back to 5 kHz, and it remains stuck at 10 kHz. The only way to be able to control the frequency of excitation again is through a power cycle of the RT/chassis.

  We checked also by adding debug code in the custom feature event is the channel of sin or cos channel starts showing a rolling measure voltage so our measure of angle begins to roll too.

  So far, this behaviour seems to have manifested only with programs of resolution that we mainly tested those and synchronize us excitement between a sin / cos pair.

  Please notify

  I just noticed that I never gave a solution for this.

  The problem was current flyback to another causing system glitches of EMI on the lines of resolvers somehow mess with map of 1540, which essentially stopped decoding of the resoulvers of entry correctly, I added a Reset custom device close the file and that fixed the not being able to get out of the excitement of 10 Khz on the redeployment. However the final fix was adding flyback diodes to the tokill power system high seeds. So beware of your configuration as module SCXI-1540 cards seems to be sensitive to such events.

• Cann't deploy xnet in RT with Veristand 2011

  Hello

  I can hardly deploy XNET in RT my laptop has installed labivew 2010 and 2011 Veristand. When I tried to deploy a simple application with XNET device in PXI-8106. An unknown error has occurred:

  possible reason (s):

  =========================
  NEITHER VeriStand: Open VI reference in Custom Devices Storage.lvlib-> pen device reference (Interface HW) .vi-> Custom Devices Storage.lvlib:Initialize Device (Interface HW) .vi OR VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi-> NI VeriStand Engine.lvlib:VeriStand Machine.vi engine-> Engine.vi NI VeriStand Engine.lvlib:VeriStand-> NI VeriStand Engine.lvlib:VeriStand .vi engine Wrapper (RT)
  C:\NI-rt\NIVeriStand\XNET\NI-XNET.llb\NI-XNET.VI

  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
  ? Unloading system definition file...
  ? Connection with target controller has been lost.

  The PXI-8106 monitor showed an errow as follows:

  System error.

  Detail:
  Error code: 1026
  Error message: LabVIEW: VI reference is not valid

  
  
  var sogoutip = document.getElementById ("sogoutip");
  Tip for var = {};
  Tip.Word = sogoutip.innerHTML;
  Tip.config = sogoutip.title.split(",");
  var hint = storeHint();
  sogouExplorer.extension.sendRequest ({cmd: 'show', data: {Tip: Tip, Tip: tip}});
  } else {}
  If (document.getElementById ("windowcloseitnow")) {}
  sogouExplorer.extension.sendRequest ({cmd: "closeit", data: true});
  }
  }
  }, 0);

  }

  (}) (window.external.sogouExplorer(window,7));
  //

  
  

• Best way to pass the name of the e/s DAQmx channel Veristand 2011 Custom Device?

  I'm building a custom device that will run a DAQmx task on the target of RT.

  I use VS2011 and alsoSimple custom device tool, which, at this point I'm not sure if it can work under VS2011...

  I created the fine libraries and custom device (a PWM input called InputPWM) has added to the Explorer from the system.  Running it returns the following error when I deploy:

  -----------

  LabVIEW: Type VI reference is not part of connector of VI.
  =========================
  NEITHER VeriStand: Open VI reference in Custom Devices Storage.lvlib-> pen device reference (Interface HW) .vi-> Custom Devices Storage.lvlib:Initialize Device (Interface HW) .vi OR VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi-> NI VeriStand Engine.lvlib:VeriStand Machine.vi engine-> Engine.vi NI VeriStand Engine.lvlib:VeriStand-> NI VeriStand Engine.lvlib:VeriStand .vi engine Wrapper (RT)
  c:\NI-rt\VeriStand\Custom Devices\InputPWM\InputPWM Engine.llb\InputPWM RT pilot VI.vi

  ----------------------

  On the console, it says that the error is 1026, LabVIEW: Refernece VI is not valid.

  I suspect that a potential problem is that I used a DAQmx e/s in the Configuration.ctl and the InputPWM RT pilot VI.vi in the framework can not deal with this type. So my questions:

  -What is the easiest way to pass the names of e/s to the custom device? For a quick test, I could go to hard code, but a more generic solution would also. Should be based on the address for the e/s MAX? Do I have to create the ctr under the DAQ hardware in VS?

  - or said by the way, is there a way to review these screw frame to see where the questions is, as you would with LV - RT?

  THX.

  L.

  If you use the tool of easy custom device, just put everything you need inside the cluster configuration data and these data will be in the home page of the custom (for the user to set) device and be available at runtime in the RT device custom code.

  You could have them type the name of the DAQ card and have an array of names for the channels to use. You then create the task running. or something like that. You like.

• Tables with LV in Veristand 2011 models

  In my file system definition, I have several models. All models are coded in LabVIEW, they are pretty simple at the algorithm level. Some of the outputs of the model are used by the next model etc...

  Each model has a few entries (defined as required in the connection pane) and parameters (defined as recommended in the pane). I'm running out of space of real connection, because some models will have a many inputs/parameters. I wonder what is the best way to get around this?  I am currently group entries in the tables (see attachment file), but the compilation fails with the following message:

  ------------------------------------

  VI D:\BSI\Project - Active\5030 - 02 DeltaQ - HIL\Software\Models\ArrayModel_Test.vi treatment

  Get information from subsystem... done.
  Copy model project... done.
  Definition of project of model properties... done.
  Script model_info.vi... done.
  Script model_core.vi... done.
  Construction of the model DLL's.
  Copy of model... ERROR:
  Code: 8
  Source: Copy of copy LVSV DLL.vi-> LVSV create subsystem.vi-> LVSV Dialog.vi DLLS
  D:\BSI\Project - Active\5030-02 DeltaQ - HIL\Software\Models\ArrayModel_Test.lvmodel

  Error has occurred. No DLL not produced.

  -------------------------

  Can what type of command I use in a model of LV next digital and Boolean?

  THX.

  L.

  Supported data types are listed in the present document.  It will be important to a cluster that is supported as a virtual folder.  Clusters can be nested to provide an additional organization within the system definition.

  

  -Steve K

• I can't install NI Veristand engine RT to LabVIEW RT 2012 2011

  Hi all

  Since I'm pretty new to this Board, excuse me I'm double questions...

  I work with:

  System RT: PXI-8135

  Software:

  LabVIEW 2012

  NEITHER Veristand 2011 SP1

  NEITHER Teststand 2012

  I am currently trying to get my simulation Veristand work correctly. So this means I have to install NOR Veristand Engine to RT target using MAX.

  I heard the message (see attachment) when installing.

  Question:

  Is it possible to install NI Veristand engine 2011 my RT controller that has motor in time real Labview 2012 without downgrading my 2012 LabVIEW for 2011?

  Any help would be appreciated...

  Thank you

  Rajamodol

  Hi Rajamodol,

  the following document describes the compatibility of facilities of LabVIEW VeriStand:

  http://digital.NI.com/public.nsf/allkb/2AE33E926BF2CDF2862579880079D751

  VeriStand 2011 SP1 requires a LabVIEW 2011 or 2011 SP1 installation.

  Best regards

  Peter

• Custom device error VeriStand-307603: no specified main page?

  I get the 307603 error when I try to add a custom device, I developed a VeriStand project on a client computer.  The message error window States:

  «Error 307603 occurred at Custom Devices Storage.lvlib:Initialize New Custom Device.vi > Custom Devices Main Page Data.vi Storage.lvlib:Get.»

  Possible reasons: NI VeriStand: the required custom device doesn't have a specified master page. Contact the creator of custom feature to correct the error. »

  I get this error when you add the device custom VeriStand on my development computer; only on the client computer.  I tried to copy the custom device built on top of the client computer and the custom device of source based on the customer's computer.  I also have three other devices custom that I developed that work fine on the same computer, so I don't know why it does not work.  I checked the specification of the build configuration to ensure that the VI home page is included in the source files, and to generate test preview shows only the custom device LLB and the XML from the file in the build directory, as expected.  The XML file is also oriented the correct path for the homepage VI and the GUID in the XML is the GUID file matches in overall search GUID variable.  I can't think of anything to check.

  Development computer:

  Windows 7, 64-bit

  LabVIEW 2011 SP1

  VeriStand 2011 SP1

  The client computer:

  Windows XP SP3, 32-bit

  LabVIEW 2011 SP1

  VeriStand 2011 SP1

  Everybody knows such a question or give me additional troubleshooting tips?

  I got it to work, but I don't know exactly what the problem was.  I made a copy of the part of the XML file that adds the device custom menu right-click and commented of the original, then edited the part I copied it to give the device custom a different name in the menu.  It worked fine on my development computer at the time I made the change, so I thought it was OK.  I just went and restored the file in the original version and now it works on my customer's computer.

• VeriStand engine in real time

  Hello

  The engine in time real Veristand would give me access to the library of Veristand API using c code #/Labview?

  Via Labview or c#, call the API Veristand: I am looking to open a workspace in a pre-created definition file, set the channels and read channels - stroke engine real Veristand would be able to do this?

  Thanks in advance for your answer.

  Hello

  I had the same issue using VeriStand 2011 here is the link: http://forums.ni.com/t5/NI-VeriStand/license-for-gateway-usage/m-p/2584077#M3156. But maybe the police changed?

  Best regards

• Use of custom in Veristand files

  Hi all

  Have not been able to find a lot of documentation related to the use of "Personal files" in Veristand.  I would like to know some examples of the types of files users have set up.  Specifically, I would like to know if you can "call" some types of models or devices personalized (i.e. for databases or configuration settings).

  Thank you very much

  GSinMN

  Hi GSinMN,

  It has custom there some documentation in the help of VeriStand, which deals specifically with files.

  Adding custom files

  http://zone.NI.com/reference/en-XX/help/372846D-01/VeriStand/add_custom_files/

  Although aid is not quite fully reveal the capabilities of this feature. There are two distinct use cases that I could identify for the custom in VeriStand files option. I'm going to the list of people the more detail and show you an example.

  Make easily accessible to the driver files in the development environment.

  When a file is added in the custom files in the project section, it will have its own icon in the project and is included in the project dependencies. Having the file to display in the project is useful if there is a picture of troubleshooting or a specific document (calibration sheet, how to run a test, etc.) that you would like as your operator to have access to. For example, in the sample project, I realized, there is an added file called "TestA1_PreTestSetup.txt". Of the project (on the toolbar), the operator has the option "Open a file" (to view) or "export...". "to investigate his path on the computer of the operator.

  

  Please note that the file is now added to the dependencies of the project.

  If you start to investigate the project file and lets say you do a right click on it and notice that there is a Properties option. You may notice that the Description of this file is empty. In fact, it can be filled by modifying the XML source of the .nivsproj. It also leads in the second case of the use of custom files.

  Transferring files to the aim of RT which can be used by the VeriStand engine.

  If you were to investigate the .nivsproj XML, you could first find the section of the custom files, then the tags of the element that you configured.

  

  Here are the relevant tags and a jump down,

  -It points to the source of the custom file. In this case, I added the file in the directory "C:\Users\Public\Documents\National Instruments\NI VeriStand 2011\Test procédures". He is able to solve the first component 'In common Doc Dir' because it's the common directory for VeriStand, and he added then the folder of the test procedures and the name of the file that I created.

  -Fill this tag gives us the opportunity to complete the description information that occurs when we right click on the file in the project.

  -Fill this tag gives you the ability to also send the file to the target deployment. Your VeriStand engine can then access this file during the operation. With respect to the types of files that you want to use, the link in the post above should help guide only.

  Please Note: change the XML of the project offers more customization and functionality of your project, but these changes should not be made whole. An incorrect change tags in the XML file can lead to results and poor execution. Then move forward with caution and only make minor changes at the same time.

  I hope this helps. Have a nice day, GSinMN

• Deploy and use the shared library in VeriStand for several VCD

  Hello world

  I'm using LabVIEW 2011 SP1 and VeriStand 2011 SP1.

  We have developed many custom features that use a shared code (C++ and LabVIEW code).

  For now, there is a copy of the C++ shared in each custom device dll.

  The problem is when we change the C++ dll and we forget to copy a new one to each custom devices, the oldest one that can be used by each custom devices.

  We would like to do is not to have only a single dll shared in a specific folder.

  My questions are how we can deploy this dll to a specific shared folder in VeriStand?

  Is there a specific folder that we can use to do this?

  Is it possible to deploy using the measurement and Automation Explorer?

  If someone has an idea, you are welcome!

  Best regards

  CFOE

  You can display this question in another forum that I don't think there's anything directly to do with NI VeriStand.

• Veristand reflective memory installation

  Hello

  I have a sytem with 2 chassis SMU-1075 each it's own controller SMU-8133 along with several analog and digital i/o modules. There is also a reflective memory network adapters installed using 2 GE Fanuc pmc-5565PIORC memory - one in each frame. I use NI Veristand 2011 and currently I display the State channels read later number of rings for both controllers and they all have two incrementing as long that the SDF is deployed. According to a white paper OR on distributed systems, there should be no settlement on these channels. There are a few configuration pages in Veristand (reflecting Configuration of the memory and reflective memory Network Configuration) with little explanation of the parameters or how they affect the performance of the RM network.

  Is it possible to get information on how to properly set them up?

  Thank you

  
  

• Is it possible to start the gateway of 2014 VeriStand using LabVIEW 2014 programmatically?

  Hello

  There is a reload of the Is-there-a-possibility-to-start-the-VeriStand-2011-SP1-Gateway because what worked in 2011 SP1 is no more in 2014.

  I've worn the code in the previous topic, do the same thing (calling "__cdecl Int32 StartVeriStandGateway (excluding handle Int32)" in "C:\Program Files (x 86) \National 2014\Data\NationalInstruments.VeriStand.Gateway.dll".)

  Do this from a .NET (console process or windows) program or directly from a node DLLS in LabVIEW 2014 seems to have no effect, knowing the .NET code worked in 2011 even when it is called from a Windows service.

  Is there a new way to do it?

  Moreover, the "NationalInstruments.VeriStand.WindowsRegistry.GetInstallationDirectory ()" method disappeared from assemblies.

  Best regards

  I remember before I saw this. There was a problem where the dll cannot run in the UI thread, but has no way to specify any thread, but the LabVIEW user interface thread. So, the solution was to put DLLS in a sub - VI, value than Subvi to run in the 'standard' thread and calls the value of the call to the DLL to run in any thread. See attachment.

• How to increase the size of the buffer veristand UDP?

  Hello!

  I'll have some lost data of veristand screen and I want to increase the size of the UDP buffer. This is a new option in veristand 2011 that I can read on this link: http://zone.ni.com/reference/en-XX/help/372846C-01/veristand/whats_new/ (improving the workspace section).

  Someone at - it now haow to do?

  Thanks in advance,

  Miguel.

  Do you mean how to do it from the VeriStand workspace? On your graphical work space click on setup to enter the chart configuration dialog box. In the configuration dialog box, you will see where you can enter a new value for the UDP buffer size.

• Error 1074384569 in NI Veristand Custom device while deplying code.

  Hello

  I'm relatively new to products EITHER, but I've been learning on the go while working. Here's the problem I've been meeting as he tried to use Ni Veristand. The code for custom device, the system definition file and the XML file was all given to me. All I had to do was connect to the target of RT (verified via MAX), checked the XML file by using the XNET database editor, checked the definition of system Explorer system file and deploy the code. But I get this error.

  Veristand gateway has encountered an error while deploying the system definition file.

  Details:

  -1074384569 error in the window.lvlib project. Window.VI of the project > Project Window.lvlib:Command Loop.vi > NI_VS Workshapce ExecutionAPI.lvlib: NI Veristand - connect to System.vi

  Possible reasons:

  NOR-XNET: (Hex 0xBFF63147) information database on the system in real time was created with an old version of NI - XNET. This version is no longer supported. To correct this error, redeploy your database for the system in real time.

  I tried this redeployment after update the XML file. I also installed newer XNET in the RT system. I still get this error. It would be awesome if I get some tips. These are the products that I installed in my laptop.

  NEITHER Veristand 2011 SP1

  OR LabView 2011 SP1

  XNET OR 1.6

  Thank you in advance.

  Vishwa.

  [ EDIT ] -------------

  Sorry I forgot to mention the equipment I use. It's the NI SMU-8133-NI PXI 7853R, NI PXI 7841R chassis and two PXI 8512 of NOR.

  Thank you very much. »

  Vishwa.

  
  

• VeriStand PXI-2510

  Hello

  I want to control automated PXI-2510. I've linked the Custom device for PXI-2510. Its operation is excellent manually.

  I have the following hardware and software

  NEITHER Veristand 2011

  OR PXI-1042 Q

  Controller OR PXI-8108

  What can I do for sequences automated in the passage.

  May there are some tutorials...

  Best regards

  YBilgin