VeriSTAND deployment stage bottleneck...

Similar Questions

• Problem with VeriStand deployment on cRIO-9074

  Hi all

  I'm playing with VeriStand 2010 and my cRIO-9074. I'm just trying to deploy a very simple application of VeriStand on the cRIO, but I can't get VeriStand to connect properly to the cRIO. I get error 63. Would it be a problem that the cRIO is configured using LabVIEW 2009 and I use VeriStand 2010? Glancing at the MAX software on the cRIO contained NOR-RIO 3.4.0 (minimal) that contains time LabVIEW Real 9.0.1.

  Any other ideas?

  Concerning

  Martin

  In the Add/Remove programs for your cRIO in MAX dialog, you will also need to select custom Setup to see the installation component VeriStand engine.

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

• NOR-XNET CAN custom interface code in VeriStand

  Hello

  I work with NI Labview/VeriStand 2011 and I recently received a Council XNET/XS 8513 with my controller PXI - 8106 RT.

  I noticed a great NOR - XNET.dll (about 10 MB) download in the file system on the system deployment definition PXI. Therefore, there is a greater load on the processors during execution compared to the case when I used the jury CAN 84681. I think that the reason is the extension name to FlexRay and Lin (?) protocols.

  I'm trying to reduce the load, so I create a custom model of labview for the CAN communication only, XNET with message transmission. I tested it directly with LabView on PXI, without a VeriStand deployment; The result is a correct message, reading of the CAN bus.

  Then I try to do a project veristand, deactivation of the NOR-XNET interface on the system definition file and loading the labview simulation model (builds from /Tools/NI VeriStand/generate NI Veristand) model vi; but I can't read/write in real time any new value, despite a successful deployment.

  Is there some VeriStand dependencies that I forgot? How can I use the old source NI - XNET Device Custom code for this?

  Thank you

  Giulio

  OK, I solved the problem: inport VeriStand cannot be a digital control of LabView inside a while loop time.

  Now the application is running well.

• 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

  
  

• Deployment of VeriStand model to cRIO-9024

  Hello

  I am trying to deploy a dll of Veristand simulink to my target RT VxWorks cRIO model 9024 but I get error compatibility while deploying, saying:...

  Specified model is not supported in the current execution target!

  I created the DLL file and output using RT workshop and placed them in the same folder.

  Can someone help me please?

  Check the XML in your .fpgaconfig and make sure that the values returned by your module HAVE matches the configuration fixed-point.  Looks like your values are currently set to scale by a factor of 16, what could happen if your whole word length is off by 4.  Also make sure you have all the scale applied for channels to HAVE it.

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

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

• VeriStand directory after deployment structure

  Hey everybody,

  I have a custom device that once built includes text files that will reference it in the folder data when built and I do not know where the target RT the text will be responsible to when VeriStand is deployed with this custom device.  Is there a resource that speaks of the directory on a remote RT target structure using VeriStand?  If this is not the case, no one knows where these files will be or how the directory structure is organized?

  Thanks in advance for the help.

  Your custom device can have complete control over which files deployed to the target and where these files deployed on file system target RT. I would take a peek at this custom device function to add a dependent file. You specify the location of the file on the host and the location on the target of RT where you want the file to get installed in.

• 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));
  //

  
  

• Error during deploy Homeless using veristand 2010 API

  Hello

  I developed a few screws to connect and download "in4" and it worked fine with VS 2009.

  Now I am migrating to VS 2010 and I got error-307658 when I try to connect for the second time.

  If I cancel the deployment by using the Project Explorer, I still had no error.

  I tried to undeploy using logout of the system, but I still get the same error.

  With VS 2009 it has been possible to deploy the Homeless several times without error, but it seems that the same is not allowed with VS 2010, is this good?

  I forgot something?

  I enclose the screws and the Homeless.

  See you soon,.

  Claudio H.

  If the status is active, this means that the connection between the gateway
  (host) and the target is already active. These calls will result:

  1. Connect with deploy the false value - it will be 307658 with error saying that the system is currently running (already connected), and you can reconnect.
  
  
  2. Connect to deploy true value - it will be 307658 with error saying that the system is running and you cannot deploy.
  
  
  3. Disconnect with put false - undeploy it will cut the target (host) bridge but let the defintion of running system.
  
  
  4. Disconnect with undeploy true set - this cancel the deployment of the current definition of system and disconnect the gateway of the target.

  So for a robust application, you probably should handle error

• Deploy on top of running Veristand system definition

  I managed to deploy a definition of a RT PXI system.  I then closed the workspace but not a not cancel the deployment.  The definition of system continued to run on the PXI system.  I have changed since my definition of the system and would like to deploy this new file.  However, I can't figure out how to stop the currently running system definition file to enable this.

  Thank you

  Marty

  You have a few easy options to do so:

  Run the project: you can run a project in the window started to get or by clicking on the run button in the toolbar when you configure the project. Run first will try to connect to targets in the system definition without deploying. If the targets are already running with the same version of system definition, then the project will connect everything simply. However, if the objectives not running a system definition, run a different system definition or run a different version of the system definition, then the project stop targets and force deploy its version before connecting. In your case, because you updated the definition of system on the host computer, the project will stop the target and deploy this version on the top automatically for you.

  Deploy the project: you can deploy a project by clicking on configure to open it and then clicking the button deploy in the toolbar. This will force deploy the project on the overall objectives of the RT in the system definition, which makes them first establish some definition of the system they were running before.

  In summary, virtually the only option you don't want to try is to Connect, which, unlike an option the deploy, don't try to connect to a target executes the same system definition and never deploy or stop this project.

• WebCenter 12 c: is it allowed to do TDSB on the implementation stage and delivery while deployment servers or only on the staging and publishing to delivery?

  Hi guys,.

  I am currently working on Webcenter 12 c. Building models, definitions, etc., for deployment in the previous version (7.6 Fatwire), allowing us to make TDSB on staging and then to publish models, definitions, etc., to the delivery server. In this way the templates and meta-data were published story and when content authors used to publish content it would not ask to include metadata as well.

  Now we continue doing in the same direction or can we TDSB on intermediate servers and delivery while deployment? We will have problems of constraint violation unique assetid if we do it this way especially when that merges several branches and deployment?

  Kind regards

  Murali

  Yes, you can even export/import through TDSB (the link gives some basic information about it), but the question is whether it is advisable - usually there will be other changes in the environment of the staging, which are not related to the TDSB, then you want rather to publish all changes in the scene at a time.

• HP T610 more: HPDM deployment for t610 image more crashes during the installation of the new initial start of the image

  We are working on the update of our thin clients HP T610 more.  Update us the thin clients in the last image of the OS WES7P and also update to IE11 and Citrix receiver 4.4.

  We use HPDM 4.6.4

  We have successfully several T610s and update the image of the OS and related software with no problems.  We are then able to use the 4.6.4 to successfully shoot HPDM and image of these thin clients updated in the master repository.

  We then create a task to deploy the new image to several thin clients.  We configure the task to use the imagery being cached, and then run the task.  HPDM then successfully deploys the image for thin clients.

  Customers accept the image cache and once the image is fully downloaded they restart to deploy the image.   After the restart, the image unfolds and decompresses correctly, then the thin client, start the original installation of Windows.

  But for 90% or more of these newly imaged thin clients that they get hung up during the installation of Windows (usually during the message that windows is written to the Registry).  Once the thin clients get hung at this stage they are inaccessible and unrecoverable by HPDM and must be copied via USB.

  We believe that the issue is somehow related monitors are connected to thin clients.  If isolate us completely thin clients monitors, then deploy an image the new image is OK.  HPDM reports that the image has been deployed successfully.  If we then go back to thin clients and reconnect the monitors of the thin client is updated and the screen seems to be in standard vga mode low resolution.  A restart of the thin client then recognizes and sets the appropriate screen resolution, and the thin client is good to go.

  What is normal sound monitors must be separated to deploy a new image?

  Thanks for any idea or thougts.

  From the point of view HPDM, disconnect monitor is not required when you deploy the image. Personal thought is that there is a compatibility problem between the display driver, graphics card and the system. Installing Windows intend to write a default registry value based on connected monitor (maybe display settings), for some reason, he was stuck. I'm not the driver or the operating system that you are an expert, I would say that you submit a ticket to HP for additional troubleshooting.

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