deploy Labview on Solaris

Similar Questions

• LabVIEW code 2013-> Solaris?

  Is it possible to make Windows code developed in Labview 2013 executable on Solaris?

  Thank you

  N ° at the same time, NEITHER had a version of LabVIEW for Solaris, but it is no longer available.

• labview deployment project has conflicts

  I'm having a problem with a deployment of teststand (2013 Teststand, LabVIEW 2013)

  I have a deployment that deploys my project LabVIEW that contains all of the drivers (classes and lvlibs) for use in my sequences.

  During deployment (LabVIEW options), I uncheck "exclude vi.lib", "exclude user.lib" and "exclude instr.lib" because the deployment should also work on a PC that has only some runtimes and an operator interface.

  The build is complete without errors, but I can't open the deployed project...

  --> not on a development PC because it detects conflicts (XNodeSupport and some in vi.lib picture.llb of the vi)

  --> not on lifetime PC (file not found)

  Else you have noticed the same behavior?

  He works with LabVIEW and TestStand 2010.

  Thanks in advance for your help, advice and tips :-)

  (Cross post, also on Lavag.org: here )

  NEITHER of the spirit together, we have identified the problem.

  The GDS (suite Goop development) causes conflicts.

  The problem is identified, the solution is underway.

  See you soon,.

  Wim

• TestStand deployment is not parsed the labview rtm path corectly

  Hi all

  I need help to solve a problem when deploying Labview run menu to teststand.  For example, when select the path to install as below:

  -Default Installation Base Directiry = Volume of window (for example, C:\)

  -Directory of the default Installation of Sub = TEST

  After building the vi seems you are looking for the file menu TEST:\Labview\close.rtm execution.  It is an invalid path.

  The file must look at C:\TEST\Labview\close.rtm

  This vi is call from a call sequence in menu area tool teststand and have a front during the race

  Pleae let me know if there is a solution for this problem.

  Thank you

  Tphan

  Tphan,

  I was testing the VI in the directory of the image which worked well.  Move the vi (and gtr) from the directory of the image to the c:\test folder reproduces the problem.

  Could you use LV 8.6.1? I tested LV 8.6.1 with the same test file and it works even after moving the files to another directory.

  -Rick Francis

• deployment issues

  Hi all

  I'm new to Teststand and tried to deploy my Teststand applicatino on computer target for the last 2 days and have some questions about the deployment process.

  1. I developed my TestStand application on the D drive on my development computer. My computer has only the C drive. In this case, (note: TestExec.ini is also being rolled out) I would still need to:

  (a) change target the path search on the computer configuration after deployment, for example, adding/changing of all relevant paths in the configuration of the research to start with drive c. or

  (b) I can also do a few tricks, by setting configuration C: research in computer development, just for the sake of deployment. In this way, the deployment on the target computer will be the right search path (and the files output because directory report I specify a directory output fix reports). Then I have to change the configuration of the search on drive D for the continuation of the focus on the computer of deveopment.

  The question is: if I choose one) as deployment strategy, in order to add/change the configuration of the computer search target, I need a teststand development license. If I download a teststand development (evaluation) on the target computer, after the add/change the configuration of the search on the target computer, I disable the Teststand development and move the license to the license of deployment on the computer base target, this will do, right?

  2. shared variable deployment published network is not so straightforward. My target computer will communicate with a compactRIO with shared variables. The compactRIO controller is AES. I added a "deploy Labview Utility LIbrary step" in a sequence step and deploy this sequence on the target computer. I ran this sequence in order to deploy the variable shared on the target computer. However, I got an error saying that the shared variable library can not be deployed and to ensure that it has only shared variables in the library. I checked and you can see that there are only shared in the lilbrary variables. What could be the possible reasons? Can someone give me advice on this problem? Y at - it a tool that can scan the library and tell me if there is a 'hidden' in this library vi because I see nothing wrong with the library even with my big glasses.

  I think other shared, for example variable deployment options: a) maybe I need to download a system assessment deveopment LabView on the target and the copy on the Labview project and deploy the variable shared across the labview project. or (b) I can create a vi that uses the variable shared and using labview generation process for deploying the vi as exe. Check the option "deploy the shared variable" appropriate in the build process, run the exe on the target computer. This way I can deploy the shared variable. After deployment, disable the deveopment LabView evaluation license so there is only LVRTE on the target computer.

  (Not the one above) and b) sensible options such as shared variable deployment strategies?

  At this point, I realize that the TestStand deployment is a skill. There is no systematic deployment for TestStand approach. The experts out there agree? I just need a few entries so that I'm not on the wrong track. Thanks in advance for your comments.

  Yours,

  chati

  Hello chati,.

  version of the software you use?

  There is a known issue with the variables related to a shared library in old versions of LabVIEW.

• Error e/s of generic file during deployment

  Hello

  I have a LabVIEW RT application I'm developing on a RT PXI system. The code works well on the target of RT. However, when I try to build an application and deployment, deployment generates this error:

  Deployment VDW_1V (impossible to deploy)
  LabVIEW: File generic i/o error.

  Strangely enough, it is:

  -Can I run the code very well (as source code)

  -The code consists of a hand VI using 8 Parallels Subvi. Only, I get the error when activated the application with all the Parallels of the Subvi of construction. When I disable some VI (with structure diagram to disable), there is no error. However, I can't identify

  1 bad VI: there is no error when you use only the 4 first Subvi. But there is also no error when using only the other 4 VI.

  It seems that there is only an error when all SIX are enabled.

  -J' have enabled debugging and checked/unchecked all the compilation options available.

  Is there a way I can get more information about the deployment error?

  HW:

  -Chassis SMU-1078

  -Controller SMU-8135

  -CAnbus PXI-8512 map

  -Card CANOpen PXI-8531

  -Map digital e/s PXI-6514

  -2 x card SMU-8234 GigE Vision

  Software:

  -LabVIEW 2013 SP1

  -LabVIEW RT 2013.0.0

  -Vision RT 15.0.0

  -IMAQdx 14.5.0

  -DAQmx 14.0.0

  Solved the problem by opting for LabVIEW 2015 AND uncheck 'allow debugging' in build RT specification.

• Segfault LabVIEW 8.2 on Ubuntu Linux 8.10 64-bit

  Hi, I just upgraded my Ubuntu 8.10 Linux box. And then, I found that LabVIEW 8.2 cannot work on this, but it worked fine on Ubuntu 8.04. Does anyone have the same problem? Are there solutions?

  See you soon,.

  Forrest

  OK, now it works very well. I guess the problem is that I deployed LabVIEW on Ubuntu 8.10 Release Candidate. The stable version has no problem.

  Ldd labview Forrest@Xem:/usr/local/natinst/LabVIEW-8.2$
  Linux - gate.so.1-online (0xf7f6a000)
  libOSMesa.so.4-online /usr/local/natinst/LabVIEW-8.2/linux/libOSMesa.so.4 (0xf7dff000)
  libGL.so.1-online /usr/local/natinst/LabVIEW-8.2/patchlib/libGL.so.1 (0xf7dbb000)
  libX11.so.6-online /usr/lib32/libX11.so.6 (0xf7cb8000)
  -Online /usr/lib32/libXext.so.6 (0xf7ca9000) libXext.so.6
  libdl.so.2-online /lib32/libdl.so.2 (0xf7ca5000)
  -Online /lib32/libpthread.so.0 (0xf7c8c000) libpthread.so.0
  libstdc ++. so.5-online /usr/local/natinst/LabVIEW-8.2/linux/libstdc++.so.5 (0xf7bd5000)
  libm.so.6-online /lib32/libm.so.6 (0xf7baf000)
  libgcc_s.so.1-online /usr/lib32/libgcc_s.so.1 (0xf7ba0000)
  -Online /lib32/libc.so.6 (0xf7a42000) libc.so.6
  libxcb - xlib.so.0-online /usr/lib32/libxcb-xlib.so.0 (0xf7a3f000)
  libxcb.so.1-online /usr/lib32/libxcb.so.1 (0xf7a25000)
  libXau.so.6-online /usr/lib32/libXau.so.6 (0xf7a22000)
  /lib/ld-linux.so.2 (0xf7f6b000)
  libXdmcp.so.6-online /usr/lib32/libXdmcp.so.6 (0xf7a1d000)

• specification of the building does not start

  Hello

  I am trying to build a standalone application that would start when PSC 2210 controller is started.

  In my project, I use specification to build everything first build specification. I put it in the startup. Then I deploy the specification and some libraries which include variable necessary shared. Without errors or warnings are displayed. Then I start my PCP to see if something happens. I have a small LCD screen connected to the controller of the PSC which should show a text that the application starts. LCD screen shows no traces of event. But I still think that there is something with the controller, because I can not connect to the controller unless it is in a position NO App.

  If I then set controller on the position of the No. App and start the vi of the project under the CFP-2210, application start, LCD shows everything is OK. But there is now an error message while deploying "LabView: the startup application configured to start was absent at the start of the RT target."

  Can anyone tell what is missing and where? I know that I added vi wanted to start in the startup list screws in my real application of time when generating specification properties.

  I'm using Labview RT 8.5.1 on PC and PSC 2210.

  Mika

  I solved the problem. The problem was the path of the startup.rtexe file. RTTarget.ApplicationPath=/C/ni-rt/startup/startup.rtexe should be RTTarget.ApplicationPath=/ni-rt/startup/startup.rtexe and RTTarget.VIPath=/c/ni-rt/startup should be RTTarget.VIPath=/ni-rt/startup.

  This path should not have the / c forwards. It's a little weird for me because it is defined like this as a default value. I mean Build specification which defines as target path when opening, and all other files and folders still exist in the right places. Know not working very well, but I do not know if all the real things are saved in the right places.

• How to use the 'Get Shared Variable list' VI on a target RT?

  Hello

  I would like to browse all variables shared in a library hosted on my CompactRIO programmatically. I dropped the 'Get Shared Variable list' VI in my VI in real time, but when I tried deploying, LabVIEW says

  Deployment PRC_GetVarList.viPRC_GetVarList.vi loaded with errors on the target and was closed.
  LabVIEW: Unable to load the shared library dscProc.dll:ni_lvdsc_process_GetTagListEnd:C. ensure that the library is present on the target of RT. MAX allows you to install software from OR or FTP to transfer custom RT target libraries.
  LabVIEW: Unable to load the shared library dscProc.dll:ni_lvdsc_process_GetTagListBegin:C. ensure that the library is present on the target of RT. MAX allows you to install software from OR or FTP to transfer custom RT target libraries.

  I watched the wizard of the MAX software, but cannot find the DSC-based modules. Where should I look?

  Thank you!

  Hello

  The palette of DSC is not supported on the screws in real-time and will lead to errors when they are deployed.  Unfortunately, to have a successful build you will need to modify your application and remove the screws from the palette of DSC on your target of RT.

• Need help with the presentation of the trace file

  Hello
  
  I need to understand
  
  -the large number of fetch for the query
  -SQL * Net message to client and SQL * Net message from the clientbeing even
  -locking: cache buffers chains
  
  The question I have is a delay of 6 x for some reason.
  
  Can someone help me?
  
  Thank you
  D
  
  -----
  
  SQL
  
  SELECT R_RO.*
  Of
  (SELECT b.ID, b.ANSWERS, b.C_CLASSID, b.C_ID, b.FCI, b.FROM_ID, b.TCI, b.TO_ID, b.FFU, b.TFU, b.NOU, b.ISN, b.SC_NAME,
  b.DN_NAME, b.DN_ITEM_NUMBER, b.ISC, priority of THE VVP. B RELATIONSHIP WHERE b.ID NOT IN (SELECT / * + HASH_AJ * / SDE_DELETES_ROW_ID OF VVP.) D94 WHERE DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages WHERE l.lineage_name = l: source_lineage_name AND l.lineage_id < =: source_state_id) AND SDE_STATE_ID
  =: 'SYS_B_0') UNION ALL SELECT a.ID, a.ANSWERS, a.C_CLASSID, a.C_ID, a.FCI, a.FROM_ID, a.TCI, a.TO_ID, a.FFU, a.TFU, a.NOU, a.ISN, a.SC_NAME, a.DN_NAME, a.DN_ITEM_NUMBER, a.ISC, a.PRIORITY IN THE PSV. A94 has, SL SDE.state_lineages WHERE (a.ID, a.SDE_STATE_ID) NOT IN (SELECT / * + HASH_AJ * / SDE_DELETES_ROW_ID, SDE_STATE_ID OF VVP.) D94 WHERE DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages WHERE l.lineage_name = l: source_lineage_name AND l.lineage_id < =: source_state_id) AND SDE_STATE_ID >: 'SYS_B_1') AND a.SDE_STATE_ID = SL.lineage_id AND SL.lineage_name =: source_lineage_name AND SL.lineage_id < =: source_state_id) R_RO WHERE (ID =: "SYS_B_2")
  
  -----
  
  call the query of disc elapsed to cpu count current lines
  -----
  Parse 3911 2.30 2.14 0 0 0 0
  Run 3911 2.47 2.43 0 0 0 0
  Search 3911 268.96 270,60 28 15696558 0 3911
  
  Total 11733 273.73 275,18 28 15696558 0 3911
  
  Chess in the library during parsing cache: 1
  Optimizer mode: FIRST_ROWS
  The analysis of the user id: 1031
  
  Rows Row Source operation
  -----
  1 VIEW (cr = 3966 pr = 0 pw = time 0 = 84973 US)
  1 UNION ALL (cr = 3966 pr = 0 pw = time 0 = 84968 US)
  1 ANTI-HASH JOIN (cr = 3963 pr = 0 pw = time 0 = 84707 US)
  1 TABLE ACCESS BY INDEX ROWID CONNECTION (cr = 4 pr = 0 pw = time 0 = 123 en)
  1 INDEX SCAN SINGLE R94_SDE_ROWID_UK (cr = 3 pr = 0 pw = time 0 = 88)(object id 7404) US
  VW_NSO_2 VIEW 8586 (cr = 3959 pr = 0 pw = time 0 = 112274 en)
  8586 NESTED LOOPS (cr = 3959 pr = 0 pw = time 0 = 103686 US)
  3661 INDEX RANGE SCAN LINEAGES_PK (cr = 7 pr = 0 pw = time 0 = 67)(object id 307740) US
  8586 D94_PK1 INDEX RANGE SCAN (cr = 3952 pr = 0 pw = time = 0 70624 US)(object id 1637355)
  0 ANTI-HASH JOIN (cr = 3 pr = 0 pw = time 0 = 248-en)
  0 NESTED LOOPS (cr = 3 pr = 0 pw = time 0 = 71 US)
  0 TABLE ACCESS BY INDEX ROWID A94 (cr = 3 pr = 0 pw = time 0 = 68 fr)
  0 A94_ROWID_IX1 INDEX RANGE SCAN (cr = 3 pr = 0 pw = time 0 = 65 US)(object id 129281)
  0 INDEX UNIQUE SCAN LINEAGES_PK (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 307740)
  0 REVIEWS VW_NSO_1 (cr = 0 pr = 0 pw = time 0 = 0 US)
  0 NESTED LOOPS (pr = 0 pw = time cr = 0 0 = 0 US)
  0 D94_PK1 INDEX RANGE SCAN (pr = 0 pw = time cr = 0 0 = 0 US)(object id 1637355)
  0 INDEX UNIQUE SCAN LINEAGES_PK (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 307740)
  
  
  Elapsed time are waiting on the following events:
  Event waited on times max wait for the Total WHEREAS
  
  SQL * Net message to client 3911 0.00 0.00
  SQL * Net client message 3911 72,42 0.49
  latch: cache buffers chains 1434 0.07 0.00
  latch: shared pool 1 0.00 0.00
  DB file sequential read 28 0.31 0.14
  free latch 15 0.04 0.02
  latch: cache line items 1 0.00 0.00
  Journal of end of file switch 4 0.98 1.64

  ssddgreg wrote:
  Hi Julie,.

  Thank you for your excellent performance! I have the DBMS Oracle 10.2.0.3 Ent edition deployed on Sun Solaris (64-bit), FIRST_ROWS and CURSOR_SHARING = SIMILAR.

  I also checked the D94 table. SDE_DELETES_ROW_ID on the index, there are 3 indexes on the same column:

  D94_IX1, NON-UNIQUE
  D94_IX2, UNIQUE
  D94_PK1, UNIQUE

  This table is a system of another application of intermediate layer, and all the DXX tables are set up like that.

  Is it a seller third-party application that you have no control over the schema? Because your description of the indices look like a potential case of massive too indexing, increasing the workload required to keep all this index. Most likely some of these indices are redundant and could be covered by a less index number.

  Not to mention that my comment about the execution plan was probably not clear enough - I mean, it's the HASH_AJ trick prevents the optimizer to do clever things with predicates that I described.

  So basically, the question is: what execution plan that you get if you omit the HASH_AJ advice? And how much compliance requires this new plan at run time? You may need to add a NL_AJ key instead to get what I have just described, but it would be interesting to see, in the first place, what execution plan is generated without any evidence.

  A few other comments:

  First_rows optimizer mode: this application allows you to use the optimizer mode FIRST_ROWS requires? Because in principle, if you have an application that actually retrieves most of the time only the first rows of a result like set, then you should use (n) FIRST_ROWS optimizer mode instead. FIRST_ROWS optimizer mode is obsolete since Oracle 9i, if I remember correctly, and has strange side effects on implementation plans, especially if the SQL contains an ORDER BY clause.

  If your application usually treats all rows in a particular result set, default optimizer mode ALL_ROWS is more appropriate - using FIRST_ROWS as a band-aid because with ALL_ROWS things are slower only shows that there is something wrong that must be treated in a different way (by investigating why the ALL_ROWS mode can't seem to appropriate as the first activity execution plan).

  CURSOR_SHARING = SIMILAR: CURSOR_SHARING = SIMILAR Note has some other effects secondary (and bugs). Oracle recently announced on My Oracle Support (see document 1169017.1) CURSOR_SHARING = SIMILAR will be deprecated (no longer supported) in Oracle 12. See this note for a description why this setting can be problematic.

  Of course, if you have no control over a provider application and it works very well and has been optimized for these parameters (FIRST_ROWS CURSOR_SHARING = SIMILAR) then there not much you can do (or do) on this subject.

  Kind regards
  Randolf

  Oracle related blog stuff:
  http://Oracle-Randolf.blogspot.com/

  Co-author of the book "OakTable Expert Oracle practices":
  http://www.Apress.com/Book/view/1430226684
  http://www.Amazon.com/Expert-Oracle-practices-database-administration/DP/1430226684

• deployment error: unable to locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.

  Hello world

  I want to deploy my project Teststand and got a strange error when creating the image.

  For many additional files with the suffix as .tso, alias, lvlpb, exe, dll... deployment tool launches the error message "unable to locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.» (see also the attached picture).

  If I exclude the files of my distribution or set them to "include without treatment or dependencies of elements of" the generation works fine.

  After the error, I checked the Temp folder. The temporary project LV is not yet created.

  I used the deplyoment-installation in the same way within a fromer project and had no problems like that...

  I use Win7 / LV2013 SP1 & Teststand 2013 f1 (5.1.240).

  Could someone help or support? Thank you!

  Finally, I tried the construction with LV2015 & TS2014 - no problems... Everything works fine...

• 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

  
  

• Problems with labview on TestStand deployment system (usually run without a license of labview)

  I'm trying to deploy a system using testStand for a machine of deployment for the 1st time. I built my Installer and image etc files The files of the installation on the target however machine when I try to run my program in mode operator TestStand I get errors relating to Labview. The only way I can work around this error is to activate a Labview license on the deployment computer, is not viable.

  The error I see when I turn off my Labview license simply indicates that an error has occurred accessing the Labview ActiveX automation server.

  I have included engines of execution etc. in my Installer. As this is my first build is there something obvious I've missed here?

  Thanks for any input.

  Vinny

  Vinny,

  My first guess is that the setting of the LV adapter on the deployment computer is always set to "LabVIEW development environment". You must change this to "runtime".

  hope this helps,

  Norbert

• How to include LabView Instr.llb in a deployment of TestStand?

  I want to deploy my sequenze of testbed. When I install the deployment and you want to let it run it shows that it can t find all the sub whitch screws I used directly from LabView. For example: .vi VISA set up a Serial Port (Instr) or by check if file or folder Exists.vi. How to include this VI s to the installer?

  He s solved. This screw is located in the folder: Support screw whitch is createt automatically by the installation.  Thank you

• Deploy file. DLL for CompactRIO with LabView

  Hello

  I have compiled a DLL-file of SimulationX, and I want to deploy this file on a CompactRIO with LabView. How do I do that?

  Thanks in advance

  A correction, the x 900 cRIO and 908 x seem to use an x 86 CPU and execution Pharlap ETS. PharLap ETS allows you to run SOME Windows but by far not all DLLs, because it supports only a subset of the Windows API available on Windows 2000. So, if you have a controller of 908 x cRIO (900 x are very old and unlikely to be used these days) you MAY be able to deploy the DLLS on your cRIO system. To make sure that you check the DLL API not supported importation by the auditor of the DLL which can be downloaded for your version of LabVIEW specific here.