Similar Questions

• Model VeriStand compilation error: NEITHER VeriStand 2010 cannot find the struct parameter in CGTypes

  Hello

  I get this sequence of messages when I try to compile a model.

  ...

  # Generating API interface TLC.
  ...........................................................
  # NEITHER VeriStand 2010 modifying Pack_L500_IB_plant_fstep_io.c file
  ...................................
   
  # NEITHER VeriStand 2010 modifying Pack_L500_IB_plant_fstep_io_data.c file
  Error: # NOR VeriStand 2010 cannot find the struct parameter in CGTypes
   
   
  # NEITHER VeriStand 2010 modifying Pack_L500_IB_plant_fstep_io.h file

  # File Readme of Ports generating NI VeriStand 2010
  Could not find c:\WorkDir\Models\Pack\pack_l500_ib_plant_fstep_io_niVeriStand_rtw\*.obj
  # Time real workshop build procedure for model: 'Pack_L500_IB_plant_fstep_io' aborted due to an error.

  I tried to repair my VeriStand 2010 installation and always errors.

  I created a VM, installed Simulink and Veristand and tried to recompile the template. Error appers again.

  I changed the "target system" (tlc file) in general relativity, and the model has been compiled without errors. Same VxWorks Veristand target fails.

  If I copy the other target to target VS the second error le.obj goes but I always "error: # NI VeriStand 2010 unable to find parameter struct in CGTypes.

  How can I solve this problem?

  See you soon,.

  Claudio H.

  Hello

  I found the problem but not the reason.

  If I change the Settings of Configuration > Optimization > Parameters Inline unchecked = the template compiles without problems.

  See you soon,.

  Claudio H.

• NEITHER Veristand 2014 does not appear in the generation of Code from MATLAB R2014a

  Hello

  I installed NI Veristand 2014 after installation of MATLAB R2014a. I restarted my PC and tried to apply the example sinewave. I looked at the code generation in model configuration settings Simulink, but could not find the NIVeristand option as shown in the video. Here is a screenshot of the target file system:

  

  I missed to install something? It was my installation (since I need Veristand to compile MATLAB model):

  

  Thank you for your help in advance

  Hi Wade,.

  Unfortunately the behavior you are touched by is a flaw in our automatic installer of the MATLAB R2014a detection. The NI VeriStand 2014 node that you see in the window of parameters of the installation program hides in fact several other unique options. The default selections expected automatic selection supported MATLAB if MATLAB was detected successfully by our Installer, unfortunately, this procedure has failed.

  To work around this:

  1 restart the Installer settings window
  2. in the characteristic parameters (your second picture) window, left-click on the image next to the label of NI VeriStand 2014
  3. you should now be presented with the option, with customization - choose this option.
  4 4 proceder proceed to installation, thereafter you presented with custom product options VeriStand.
  5. in the list of features VeriStand, select NI VeriStand 2014 model framework
  6. proceed with the installation.

  After that, restart MATLAB and then again. If the installation was successful, on the revival of the command window MATLAB will display the initialization string NI VeriStnad 2014. Please note that we have documented this problem and make an effort to remedy.

  

• NEITHER Veristand DLL models simultaneous execution

  Hi all,

  I have to solve that problem is with my VeriStand workspace:

  I have a project NIVS with two models of dll (Run/Stop/Pause) execution is monitored in the Versistand workspace by two interface objects user 'Model Control'.

  I wonder if it is possible to manage the executions without a click twice, i.e. together with a click of mouse control.

  I tried to create a custom user interface object whose controls could / should manage all other objects dll controls in the workspace user interface. then I modified 'Model - model Control.vi' with the addition of a "Call by reference" block to call my user object interface custom controls; but an error occurs when trying to load the object in the workspace. The same problem using a Subvi rather than a reference call.

  I hope to be clear.

  You have a solution to this problem?

  Thank you

  Giulio

  Hi, Giulio.

  the fastest way to set values of multiple channels (aka "destinations") with a single source channel is the way user combination and maps. It is:

  (-) In the system Explorer, create a user called channel model batch start.

  (-) Press the button mappings on top and connect the channel the user to both channels of the execution of model, one for each model.

  Bind a control of the workspace to the user of the chain)

  

  In this way, you can change the execution mode of several models with a single channel model (and thus a mouse click). You can use a Boolean control if you just want to start/stop the model or an entire control if you want better control each State of execution, which are:

  0: start
  1: break
  2: reset
  3: save
  4: restore

  An interface object using custom user is honestly an overdose if you just have to set several values at once.

  Hope this helps

  Concerning

  Fabio

• NEITHER Veristand in Windows Server

  Has anyone tried having multiple developers to share a NI Veristand installation on a Windows Server machine? Developers would use the remote desktop for the initial development, and all work together to test and debug console.

  I believe that the license computerized described here: http://www.ni.com/license/licensing_options.htm this would help, but I don't know if there is a problem to have multiple instances running at the same time.

  Did anyone tried something like? How at - it go?

  Hi Clendon,

  The license agreement states that the software can be used by a single person on several machines (with only on running instance) or by multiple users on a single machine (which would only allow a single instance of execution). I think that what you are proposing (several people using it at the same time) would violate the license agreement: http://www.ni.com/legal/license/

  If you have any other questions about how many licenses you would need to buy, I would recommend he discuss with a member of our sales team. They'll be able to talk about what you need for your particular situation.

  I think you would at least be able to get away with only 2 for three people, as the development of models and development of drivers will not access VeriStand. You really need only for testing.

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

• VeriStand custom controls

  I'm just starting to use the evaluation copy Veristand to see if it can do what I need it to do.  It seems very customizable, and I tried to create controls in the workspace personalized with Labview.  I would like to make things like radio buttons, lists and menus in the workspace to control my drop-down model.  I have tried everything just by taking one of the digital controls and its replacement by one of the controls mentioned previously, but it gave me an error message saying they were not supported.  It seems that I'd be able to do this using the free label template, but I'm not sure how to do this.  I was able to find an example of a custom indicator (min/max one), but could not find everything related to custom controls.  Are there examples or tutorials, that I could look at?  How could I go for some of these controls of Labview in things that I could use the Veristand workspace?

  -Eric

  Hello Junior, I have some answers for your problem.

  1. I have attached a zip file that contains your renamed control and build a project in it. You should be able to unpack, check the construction features and make sure that the output destination is C:\Documents and Settings\All Users\Documents\National Instruments\VeriStand\Display models. Trigger a build on that and you should get EricHettlerSample - Radio.vi and EricHettlerSampleControlSupport.llb in there. Once you have this launch a workspace, you will be able to drop the EricHettlerSample - Radio in the control list control.

  2. for the explanation. I think that when you perform a save as on the example of the min - max you download the Web of LabVIEW cross link on the screws that the llb with that of the vi.lib. Do a save as will not work. What works, it is that you create a project and setup a source distribution to generate the custom control. Here are the steps that I have take based on your attached file:

  1. Rename in windows Explorer, the attached digital indicator - radio.vi to EricHettlerSample - radio.vi
  2. Open LabVIEW convert the .llb you connected to a directory.
  3. Create a new project file.
  4. Radio.vi open EricHettlerSample - under my computer, when LabVIEW invites me to some VI I search in the directory to convert llb. Note that LabVIEW search more files under vi.lib because these are the files that NI VeriStand install labview directory.
  5. Once I added some of the screws, I mass compile the project.
  6. Create a source distribution. Add the EricHettlerSample - radio.vi. Go to setting source file main vi for the folder models and all otherwise go to a folder of llb.
  7. Trigger the build, LabVIEW will do a better job in creating an isolated component which is properly connected.

  In General, you always want to create a project to create a custom, control given that Save As not always worked with the LabVIEW VI link in NI VeriStand.

  To create a completely custom control project base what you do is:

  1. Copy C:\Documents and Settings\All Users\Documents\National Instruments\VeriStand\Display Templates\Decoration - free Label.vi in Explorer windows in a directory of your choice.
  2. Make a change of name on VI in Windows Explorer.
  3. Open LabVIEW to create new project add the renamed VI in my computer. This will create an empty project to customize the custom controls.

  I hope this helps, let me know if it still does not for you.

  Also if you still embarrassed by the error messages appears so you will want to clean directory C:\Documents and Settings\All Users\Documents\National Instruments\VeriStand\Screens this directory being where NEITHER VeriStand puts all the controls that you drop into the workspace cache. So if you have a control that cannot be loaded remove all screws in this directory should remove the wrong screws.

• VeriStand 2015 will not deploy with Labview created model: error-307703

  I try to use a model of labview to resume a few calculated channels that are currently in one of my projects veristand. Without the LV model, it works fine. But after you import the model and connection of all inputs and outputs, he used to "deploy. Gives the error-307703 during the deployment. More information in the log below.

  I use Veristand 2015 and LabView 2015 also. I put the inputs and outputs correctly in the connector pane, and when you import the model into Veristand, the inputs and outputs appear correctly. "" When I use the "Tools" NI VeriStand "generate NI VeriStand model of VI ' there is no errors and it creates a LVmodel that I can import into veristand.

  Are there steps that I missed? Or troubleshooting tips for tweaking my design to accept a LVmodel?

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

  Details:
  307703 error occurred at Window.lvlib projectWindow.vi project > Project Window.lvlib:Command Loop.vi > NI_VS Workspace ExecutionAPI.lvlib: NI VeriStand - connect to System.vi

  Possible reasons:

  NEITHER VeriStand: The specified model is not compatible with NI VeriStand. If you try to deploy the model to an RT target, launch the Console Viewer tool to view the output of the console of the target, which includes information about the source of the error.
  =========================
  NEITHER VeriStand: .vi Wrapper (RT) of the NI VeriStand Engine.lvlib:VeriStand engine > Engine.vi Engine.lvlib:VeriStand NI VeriStand > NI VeriStand Engine.lvlib:VeriStand state motor Machine.vi > model model Execution.lvlib:Initialize loop Data.vi > SIT model API.lvlib:Initialize Model.vi
  =========================
  NEITHER VeriStand: Initialization error Code 1

  
  

• Configurable custom control of reference for NI VeriStand

  I'm working on an application of VeriStand where I'm modeling more than 100 pieces of similar material, each demanding a set of controls and indicators on the VeriStand workspace. Because I have a few hundreds of orders and total indicators to configure VeriStand workspace, it was recommended to me that I should look at using reference varied Custom Control (http://zone.ni.com/devzone/cda/tut/p/id/11123), which is much more efficient to configure.

  The main problem I have with varied Custom Control reference is that when it is configured on the workspace, the full channel path appears in the legend next to the indicator/control form. As I have a simulation model complex faily using several levels of submodules, the complete track path is very long (for example. ("Controller/Simulation models/models/CCH_v1_0_bad/Inports/Islington 220kV Bus EAD/CB668/host_close") and tend to clutter the workspace and also make the workspace very ugly looking (more space is used to display the text of the legend that occupied by buttons/lights).

  Is there an easy way to remove traces of full path display, while allowing the user to verify the path full path required by say, right click on the object? Or at least it is possible to display one or two levels of the path of the canal, rather than the full path?

  Thank you for your attention.

  What do you think makes a lot of sense.  To do this, you will need to modify the source code of LabVIEW and recompile (build) the proposed model to screen with the right mouse button.  You need LabVIEW 2009 for this.

  The text of the legend is set to 2 different places in the right-click main-model VI: Init control legends VI and VI of data update.  They are presented below:

  

  You need to change both of these screws to do some string manipulation to cut parts of the path that you don't want until it is written in the Caption.Text property node.

  I recommend creating a Subvi, which makes the string manipulation, in this way you can insert it just in the two screws you need to change.  Use a while loop that traverses the chain from the end forward, find the 11th ' / ' end, then only retains the final part and coming out of the slot - VI.

  These two images highlight the places where you should put the Subvi said:

  

  

  You will need to add your Subvi in the folder Source Code/sup screws, and then recompile the project (run the specification building called "Right-click"). Then put the Library.llb to control newly updated with the right button in the model display VeriStand folder, as you did initially. If you want instructions on how to proceed, see the video embedded in this page:

  NEITHER VeriStand module-control custom Configurable reference

  If you still want to help get started on this, let us know.

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

• 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

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

• 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