NationalInstruments.Veristand.SystemStorageUI.WinFormsWrapper

Similar Questions

• VeriStand TreeBrowserWF display filter

  There is an object of TreeBrowserWV sub under the .net NationalInstruments.Veristand.SystemstorageUI.WinFormWrapper object. A property is the display filter (see below). Where can I find the doc detailing a list of filters? THX.

  Laurent

  

  This control is used internally to NI VeriStand and is not publicly documented. It is not currently expected to be used in custom applications.

  The property display filter determines what types of channels are displayed in the Navigator tree.

  Left to right: readable of channels

  W: channels accessible in writing

  RW: Reading and writing

  VOLT: Scalable channels, usually HW i/o

  FAILURE: Faultable channels

  ALL: any channel

  CUSTOM: Used in conjunction with a custom filter, such as a composed filter that mixes readable and faultable.

  VIS: Visible. Not hidden by the VeriStand project

• 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.

• Remote access to NI VeriStand host on windows

  Hello world!

  I have NIVS 2013 SP1 on windows remote PC, which deploys the system to his (localhost) definition file.  I would like to access the workspace on the remote PC from my local mobile through execution in NI VeriStand .NET API.  A copy of NIVS installed on my local laptop, I could indeed get and set the values of the channels on the remote PC with a console application in c# compiled on my local mobile, as long as I put the IP of the gateway to the distance.   However, without installed NIVS, my console application complains that 'NationalInstruments.VeriStand.APIInterface.dll' is not found.  This NationalInstruments.VeriStand.APIInterface.dll does not exist by itself.  Threads, I searched on this forum, it is likely integrated in one of these "NationalInstruments.VeriStand. * .dll ' installed with NIVS.

  My question is: do I really need to install NIVS on my local mobile to run the c# console application?  I tried to copy all NationalInstruments.VeriStand. * .dll (and the definition of filesystem for sure) on my laptop, but failed.    Any idea?

  Thanks in advance

  I'm not sure that's true. The license may only be necessary on the machine with the gateway. The remote client do not have the license. I think that you should just install the part Support of LabVIEW of VeriStand Installer on the remote client. You will need the complete VeriStand Installer, but you should only select this a subsection, which is not very large.

• Type of change VeriStand system channel

  Hello

  I've developed a VeriStand project and I was wondering if anyone has any ideas on how I can change the types of channels in the system of double uint32, or uint64. I see that there is a .net NationalInstruments.VeriStand.Data object that has the classes I want, but I'm not very familiar with the .net api or how to create definitions for VeriStand system in LabView.

  I thought I could create a project, import my models and then use the .net API to get the system of channels and change their type. The problem is that using the GetSystemChannels does not give a method to allow this.

  I got the VI somewhere on NEITHER, but I can't remember where.

  Thanks in advance,

  Brent

  Why do you need the channels of the system as the variants?  When you use?

  You cannot change the type of the system channels in VeriStand.  VeriStand is double.  Period.  No exception.

  However, in LabVIEW, you can easily convert a doulbe U32 or I32, almost any other type of data or elsewhere.  Just use the screw of the digital palette converstion.

• create an alias for a custom device page

  Is there a way to create an alias for a custom device page?

  I wish that a button on the home page of my device custom (in solution system Explorer) allow the user to create an alias and linking this alias on a channel of the system. My Vi is the following:

  

  This VI returns the following error:

  "Error 1172 to error creating instance of aliases in the assembly NationalInstruments.VeriStand.SystemDefinitionAPI.Alias, NationalInstruments.VeriStand.SystemDefinitionAPI, Version = 2012.0.1.0, Culture = neutral, PublicKeyToken is a6d690c380daa308, (System.NullReferenceException: determined reference is not set to an instance of an object.).

  Is there a solution?

  Hmmm... good point. You can change my original solution to configure the alias using the basic underlying storage system node type. It should work regardless of the type of channel. As for your second question, custom devices written for 2012 should be recompiled in 2013 of LabVIEW with the support of 2013 VeriStand installed. You don't have to change your code, but you must recompile the LLBs.

  

  In this workaround, you start by creating an alias that links to nothing. Then, you update the alias to set the DependentNode property, which connects it to the channel. You should not do it this way, but this will work around the original bug.

• Profile of Stimulus of departure of LabVIEW

  Hello

  I created 4 profiles of stimulation with the editor, and now I want to be able to start them with LabVIEW.

  Unfortunately most of the screws on the palette works with sequences instead of profiles. My profiles are configured with the parameter assignments and logging as well as sequence of calls. Is it possible to run profiles together instead of sequences?

  There are indeed. It is not a set of screws to use, but you can call directly the NationalInstruments.VeriStand.RealTimeSequenceDefinitionApi.dll assembly to access the functions and reminders for running a profile of stimulus.

  First of all, I would like to start by looking at the following example VI to help to start:

  \examples\NI VeriStand\API\Execution API\Sequences\Stimulus control profile Tool\Stimulus profile control Tool.vi

  It may be a little more complicated that you need, but it should have all relevant parts.

• Namespace 'NationalInstruments' not found

  Hi all

  I create my first application with the driver in the world with Visual Studio 2010 c# MS and I added the NationalInstruments.Common and the NationalInstruments.VisaNS as references. However, when I add the command "using NationalInstruments.VisaNS;" in the header of my main program. the generation process returns the following error:

  error CS0246: the name of the namespace or type 'NationalInstruments' cannot be found (missing are you a using directive or an assembly reference?)

  What I'm missing here?

  Thank you for your support.

  These errors may be generated when you have references to assemblies OR that are constructed for a different version of the .NET Framework that the project uses. Looks like you are using .NET 4.0 assemblies. Probably your project uses the profile of the Client .NET 4.0, which is a light version of the .NET Framework 4.0 and is not compatible with the assemblies OR.

  For c# projects go to project properties > Application and change target .NET Framework 4 framework.

• With the help of a data base with VeriStand BOX

  Hello

  I use a BMS that communicate via CAN with VeriStand. I imported the database of the device with NI-XNET (with 3 nodes CAN) and I can see some parameters of acquisition under veristand correctly.

  But now I want to order a State request and check if the command is well transmitted.

  To do this, I sent a node and try to see the information in another node and it does not work.

  So is this the proper way to check transmission CAN or is there another way?

  Thank you very much

  Hi Vincent,.

  If I understand correctly, what you're doing are a loopback test. It is indeed a good practice for communication. Have you connected your ports CAN directly together? In some cases, depending on the hardware you are using, you may need an external power supply for the transmission CAN occur.

  In all cases, you can also check your good communication using the tool called NI XNET Bus monitor.

  Does that answer your question?

  Good day

  M junior

• 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!

• Custom control in the new VeriStand workspace

  Anyone know if it's possible and how to make the custom to the new UI controls? I have a custom device that creates channels 400 + and I would like to find a way to add them to the user interface without having to manually configure each channel individually.

  I have a way for the user to choose if each digital output is discreet, PWM or encoder mode. Currently, they have to drag into individual channels labeled 'Enable channels', 'Output Mode' and either 'Discrete Value,' 'PWM Duty Cycle' & 'Frequency PWM', or 'Encoder quarter' & 'encoder Index Control. " Is it possible to create a custom control that contains Boolean controls and digital necessary? I know that this was possible in the old VeriStand workspace, but I have not found a way to do in the new, as there does not appear to use a directory full of screws for its controls.

  Thank you

  Mitch

  Hi Mitch,

  I'm sure that this functionality does not yet exist for the Manager of the user interface, but I guess that NEITHER is likely to know that it is a widely used feature.

  When I asked him about this a few months ago, I think the answer is that it must continue to use the workspace controls customized with the workspace and migrate the rest of your features to the UI handler. Once the UI handler and the Worspace may operate at the same time in the same application VeriStand.

  Could you describe the feature you're looking for with screenshots?

  I hope this helps, but maybe someone of NOR can enlighten us more about it!

• Mode of scanning/FPGA for a CRIO by Veristand

  Hello!

  I have a small error using my CRIO 9081 use with CAN communication, here's what I did:

  1. I use the CRIO with scan mode and customized it "Scan engine" and Ethercat for show my analog modules under VeriStand, it's ok

  2. I use the CRIO with FPGA Scan interface (together under Labview) to detect my modules CAN, also ok

  3 - then I wanted to see the CAN and analog modules, so I use this page:

  http://digital.NI.com/public.nsf/allkb/0DB7FEF37C26AF85862575C400531690

  And here's my problem:

  with this method I am able to see the two modules with the custom device 'analytical engine and ethercat", which is really nice, BUT, impossible project VeriStand, the error message asking me to turn the chassis using FPGA, but then I lost the analog module...

  So is it possible to run a project Veristand using both Scan and FPGA interface mode?

  Thank you very much

  Hi Vincent,.

  When you tried to implement, you use the procedure described in the following document in the section use of Scan Engine and EtherCAT with NI 986 x custom device modules XNET ?

  From what I remember, because you use a cRIO-9081, you will need to compile an empty bitfile for your target and place the controller in Mode FPGA hybrid mode on your chassis.

  Could you post a screenshot of the error of deployment, you see?

• CAN communicate with Veristand

  Hello

  I use a CRIO9081 with a module CAN 9268. I made a good configuration with detection of MAX module, power module, adding CAN wear under a Veristand project and I have NI-XNET...

  Now I want to interact with a sensor using CDN per Veristand, but I am a novice with CAN communication: you know some "user manual" on how to use CAN by Veristand to interact with another material?

  Thank you

  Hi vincentlg,

  In order to communicate with an external sensor via CAN, it is likely that you will need to set up a database BOX. You can create this with the OR-XNET database editor that is included with the XNET driver. The data BOX is responsible for converting frames in 'real' values (see: http://www.ni.com/white-paper/2732/en/#toc6). This also means that you can add a frame/signal to VeriStand. In doing so, signal will appear as a channel in the environment in which you can get (or set) the value of the channel in the VeriStand workspace.

  You can see that the manufacturer of the external sensor will provide a database or the scale that is required to convert the images into meaningful data. It is very unlikely that this will correspond to the sample database.

  Journal of tiara Bus converter allows to take the raw image data and convert it acquisition AFTER meaningful data. You will always need a data BOX to do this.

  To sum up: you can acquire data from a database, but you will have the raw images, which may not mean something to you. If you create a database, you will be translated these frameworks of the relevant data.

  I hope this helps, but I would like to know if I can clarify anything.

• NEITHER 9871 best way to create the customization to veristand

  I would use a NI 9871 module with NEITHER veristand to connect with over RS-485 devices using the modbus Protocol. I know that this device can be used in mode of scanning and orders VISA, but won't work with the custom device EtherCat Scan Engine.

  I was wondering the best way to change NOR veristand.

  1. Create custom FPGA personality and write the drivers to directly interface with the ports on the device by modifying cRIO Modbus.lvproject http://www.ni.com/example/31166/en/. Expose the commmands as channels passed from the FPGA personality to the workspace and command those from the workspace.Current limitation, I am unsure how to modify this into a custom device or model due to the FPGA IRQ in the RT application used for timing. Can this be included in the custom device?

  2 use the 9871 in scan mode and write a custom device to interact with it using the VISA. Deploy with e/s Modbus device custom servier and send orders to shared variables in the workspace. It would be easier and more robust driver, but I'm not sure how to implement if my other 7 modules use the custom scan engine. I can't apply it in scan mode and the other seven in FPGA because of the DMA only 3.

  3. change the Scan Engine custom device to support 9871? Not sure if this is possible.

  Thank you

  Mike

  4. do not use the NI 9871 and use the serial port on the Crio with a custom modbus device. This leads to a problem of timing, as five devices I want to interact with, I a port. Can reduce functionality.

  An update, since I've found a method that worked well enough and was easier than I expected.

  If you use the cRIO in scan mode with custom device of the scan engine, the ports will appear in MAX for the module 9871. I didn't when I started at the beginning of the post above. From there, you can use all the functions of ports similar to the rs232 port which is included on the NI 9074.

  I wrote a custom device which opened a VISA session at my port and then was able to apply the code I need to communicate with my camera rs485. I worked with modbus Protocol and functions worked within my device custom without modification. I could also adjust VISA settings in MAX and could run a VI of my pc that would send/recieve data ports. This will be useful as an additional way to test or change the settings on my outside NIVS rs485 devices.

  It should be noted in my last post, deploying a Modbus Library did not work. Shared variables of Veristand work incorrectly with the variables that they have been configured in the modbus library that I deployed. I was able to set these manually from the Distributed System Manager. I could also do standard shared variable variables and would update the workspace NIVS in distributed systems manager, they would not change the value in the modbus server. I decided to abandon it and create a custom device that just use VISA vs. shared variables.

• Help interpret the VeriStand crash report

  If VeriStand 2014 is left on for a few days, he will break eventually. I run VeriStand on other test systems and very stable. On this basis, I am sure that the accident is related to a unique piece of code (custom, device model, etc.) or the installer for VeriStand on this test bench.

  The error log is attached. I need help to interpret the error log to refine the question. Normally I would remove just a piece of code, and let it run to see if it crashes, but this project is big enough, it would take some time to solve the problems in this method.

  Through the error log, I found this message, but I do not really understand how to solve this problem.

  C:\Users\Public\Documents\National Instruments\NI 2014\Custom Devices\NHR Power Module Rack\Data\NHRDCPowerModule.dll VeriStand

  ExtFuncDWarnOnCorruption: connectorTDR is
  TDR (1/2): @0 x 0000: 'NHRDCPowerModule_ReadArray': 8
  @0 x 0000: 'return type:
  @0 x 0004: "Vi":
  @0 x 0008: 'MeasurementsBufferSize ':
  @0x000C: 'Measures': [V0]
  @0 x 0000: ":
  @0 x 0010: "method":
  @0 x 0014: ' ValBuff
  TDR (2/2): erSize':
  @0 x 0018: "Val": [V0]
  @0 x 0000: ":
  @0x001C: ":
  @0 x 0000: 'ValActualSize ':

  Little background for this project:

  VeriStand deploys on windows for NH Reseach Power Supply target and she deploys on cRIO9081 with 9144 chassis EtherCAT. The project contains multiple models and custom devices.

  

  This type of report should be sent to support NEITHER.

  They could provide a solution to this, or at least be aware of this problem.