pxi7852r with labview 2011

Similar Questions

• Executable VI with Labview 2011

  Hello everyone, I'm doing an executable on LabVIEW 2011 SP1. I've never done before, but in my project, I go to tools-> Build Application (EXE) from VI... I check to make sure that all the Sub VI are in the Dependencies tab and I put the way I want the EXE to go, then I build it. Building compiles and I have good Run-Time Engine installed, but when I go to open the EXE file, I get a lot of mistakes because void VI could not be loaded. I checked these Sub VI that were not loaded and they are locked and password protected. Probably comes with LabVIEW, so they don't want to play us with anything. How can I get these included in the EXE and not return an error?

  Thank you.

  I deleted the Run-Time Engine and downloaded again, and I think it worked. Strange, but I accept it

• Problem with the configuration to use Silver Style with labview 2011 (32-bit)

  Hi my friends.

  I installed labview 2011 32 bits. I select money style my default control style. but when I create the new VI, labview creates no controls in the silver model

  the controls are created in modern style.

  can someone help me solve this problem?

  with all my thanks: Saeid

  If you're down by controls via the palette, then it will drop any type palette you are in.  You are most likely in the range of modern control.  The setting that you are talking about is when you create a command or the indicator by right-clicking on a primitive terminal.

• Labview 2011 project with sbRIO cannot build app with Lv 2014 RT: error 1003

  Hello

  I have a project developed with labview 2011. It contains a PC application and a SbRIO-RT-FPGA app.

  I made a simple change in a RT VI. then I tryied to build the new application for my SbRIO.

  the problem is when I click on 'Build', an error dialog box appears saying that there is a VI with broken arrow. but my VI are OK.

  Can you help me please!

  Best regards

  

  
  

• Deal with failure when using LabVIEW 2011 and DSC MODBUS communication

  I'm currently reading from operating records a PLC with MODBUS/TCP. I confirmed that the PLC will update the values and in response to a MODBUS communication correctly by using a third-party program called Modbus Poll. However, when I try to query the PLC using the LabVIEW shared variable engine, I am unable to read the values of the same addresses that I consult with Modbus Poll.

  My installation is simply to a PC directly connected to the controller via Ethernet without a router between the two. I'm using LabVIEW 2011 SP1 with the DSC module.

  I opened the Manager of distributed systems OR to display the State of all variables in the Modbus Library that I created, and I noticed that the ILO CommFail permanently the value 'true '. All other variables with a 'read' access mode signal "failure of process". I tried to restart the process and stop and start the local variable engine without success. I also restarted my computer several times to see if any services did not exist, but this does not appear to have solved the problem.

  Finally, I resorted to listening to communications on the network card I have the PLC connected via Ethernet using Wireshark and found that while Modbus Poll communicates with PLC, number of MODBUS and TCP packet is sent and received. However, when using only LabVIEW or the DSM OR communicate with the controller, there don't seem to be any communication on the network card.

  Something that may be interesting to note is that I could communicate with the PLC and to read values with the DSM just once, when I understood everything first what address I should be reading of. All of this has stopped working shortly after. Prior to this, 'CommFail' was not generally set to 'true' with my current setup. Thinking it was my firewall, I have since disabled my firewall, but this seems to have had no effect on the problem either.

  Any help on this would be appreciated.

  So, I thought about it. It turns out that the IP address of the server i/o MODBUS must be set to the address of the MODBUS slave, not the local computer. The address of the i/o MODBUS server is defined by the navigation in the Explorer window projects, expanding the variable engine shared library for MODBUS and right click on the server MODBUS (for example Modbus1) item and select Properties.

  In addition, the addresses seem to be shifted by + 1.

  Thanks for the tip so.

• Install the engine 6.1 enforcement (or compatible) labview with the labview 2011

  I installed a Labveiw 2011 trial version in order to check for potential problems to upgrade, I get if I decide to spend labveiw 6.1. Well, needless to say, there has been a lot. This is as expected because I have not updated labview for many years. I'm still not under any pressure to update; However, I want to in order to get help and make sure that I have no problem of compatibility with new equipment purchases. I was able to solve most of my problems of compatibility with code simple and other corrections. However, twice now I ran into an error at the launch of labview executeables compiled by two different manufacturers. The equipment I use is not yet old... maybe a year or two. When I run labview executables for the device on a PC that has the trial period 2011 installed labview under control, I get an error message saying something like "this requires a motor enforcement 6.1 (or compatible) of Labview. I tried to download and install the labivew engine 6.1 but I can't install this engine on a PC that has labview installed 2011. Can someone explain how I run these executables under labview 2011. I can't imagine that these executables were developed using 6.1 as this equipment is not yet a year old now.

  You should be able to have a number any time installed and 2011. I have several versions back to 7.0. I asked what exactly happens when you try to install it.

  Have you tried 2011 withdrawal, execution 6.1 installation and then installation of 2011?

• Report Generation Toolkit compatibility with Microsoft Office 2013 and LabVIEW 2011

  Hello

  I design the 2011 Version of LabView to test solid state device and need to create test data after this unit tested.

  When I save the test data in the configuration of Excel after you run the Laview program, it created an error like "error - 41007 is is produced in NI_report.lvclass:New Report.v->... OR reports; Musr you have the LabVIEW Report Generation Toolkit for Microsoft Office installed to create this type of report. The musr toolkit also have an activated license or be in trial mode. »

  Questions: Do I need to install LabView Report Generation Toolkit for Microsoft Office on my computer? If Yes, what is the LabView Report Generation Toolkit for Microsoft Office Version. Where can I find this software?. I use Labview 2011, Windows 7, MS 2013 in the computer.

  Thank you

  Jonathan Tran

  You can try this: http://download.ni.com/evaluation/labview/ekit/other/downloader/2011RGT.exe

  From this link: http://download.ni.com/evaluation/labview/ekit/other/downloader/

• FieldPoint for Labview 2011 W7 - 64 bit

  Hello

  I'm currently having problems running FieldPoint Labview 2011 on running on Windows 7 64 bit system. I installed the latest (6.0.9) FieldPoint driver which is compatible with 64-bit systems. However, when I try to make a simple program (see photo A). I met two main problems.

  (1) I'm not allowed to add a control, or a constant to the FieldPoint i/o Point in terminal (see illustration B). The option is grayed out.

  2) there is an error with the FPLVMgr.dll file that is used by virtually every necessary .vi for FieldPoint (see picture C)

  I'd appreciate any help. If you need to know the application, I have a Thermocouple cFP-RTD-122. I'm trying to implement a simple program to read out temperature (see picture D). E PIC shows my MAX.

  Thank you!

  Juan

  Hey Juan,.

  I see you are using 64-bit Windows, but you use a LabVIEW 2011 64 bit as well?  FieldPoint runs on a 64 bit OS, but does not work in the 64-bit LabVIEW environment.  I would recommend installation of environment 32-bit LabVIEW and go from there.

• Software FPGA with LabVIEW 2013

  I have a system with a rotating computer "development" under Windows 7 and an NI PXI-1036 chassis with a PXI-8101 controller as well as a card FPGA PXI-7853R. Recently, I upgraded to LabVIEW 2011-2013 of LabVIEW. I kept LabVIEW 2011 installed just to make sure everything is still working on the new LabVIEW.

  Now, when I open my project in LabVIEW 2013 Project Explorer, my FPGA comes with a warning triangle yellow next to him (see attached photo). The warning says:

  "Software support for this target FPGA is not installed on the computer. You can view and copy elements into the project, but you can not compile any screw under the FPGA target, until you install support for the target. Refer to the documentation of specific material for more information on the proper drivers and for more information about the installation and configuration of the target FPGA ".

  Regarding the installed software, I have LabVIEW SP1 of 2013, 2013 of LabVIEW FPGA Module SP1, SP1 of Module 2013 LabVIEW Real-time, and Xilinx Compilation tools 14.4. On the chassis of the TARGET (with the PXI-8101 controller), I have attached a list of installed software.

  Interestingly, when I open the project in LabView 2011, no errors or warnings are present with the FPGA card. It is only under LabVIEW 2013 I see the warning. Did anyone see a glaring omission of software that could be the cause of LabVIEW raise this error? Thank you for your help.

  

  

  Best guess is that're missing you the driver for your FPGA device. Try to install the latest version of NOR-RIO (or at least the version supplied on your 2013 SP1 install disks). Have you installed device drivers at the time that you have installed SP1 2013 LabVIEW?

• Ask for a link for Labview 2011 SP1

  I ask for the link to download the Labview 2011 SP1.

  I have a bug that corrects SP1 (damaged Panel before, cannot open vi, see the discussion http://forums.ni.com/t5/LabVIEW/LabVIEW-load-error-code-3-Could-not-load-front-panel/td-p/1895379/pa...), but the download link disappeared.

  Please, if anyone knows tell me the link to download (32 bit).

  I found it here

  http://download.NI.com/support/softlib/LabVIEW/labview_development_system/2011%20SP1/

  Anyway, there are a few problems with the link that you gave to me. I thank you all the same because what is happening is somethink wronk with national instruments site, which is not the same for all countries (web designers should check and fix the bug).

• LabVIEW 2011 compiled the application crash

  I'm writing an application DAQ simple enough to use in a freshman Engineering Lab is written to the USB-6211. Since it will be used at more than one campus, I try to make a compiled application. Demand, such as built in LabVIEW 2011, works very well. The problem is that the compiled executable hangs in the same places without fail. I've included the source VI unmodified and a version with the acquisition of data code disabled and some dialogue inserted to track the progress of the request. Executables for both are also included.

  I use a architecture of producer/consumer-events to manage the three tasks of data acquisition. Consumers loop will fail after one of the three DAQ events are executed. Consumers loop works very well for the exit event. I also returned to LabVIEW 2010 and recompiled, the same failures.

  Any help is greatly appreciated!

  Stuart

  I think that if you close the front panel to start the VI, it will leave the built application.

  Replace the properies "FP.open" with "FP." State"and toggle between 'Hidden' and 'Normal'. That seems to work in my limited testing.

• LabVIEW labview 2011 2003

  I am completely new to labview and I want to do a compression test with frame of MTS

  I got a code that is written in labview 3 but it does not work (I think it's a problem compabality) in labview 2011 (the version I have access too and my acquisition of data works with)

  I have to fix as soon as possible because I do my research and I did not have enough time to understand the code. I use PCI-MIO-16-4 and I need to 3 channels for moving loadcell, extensometer and Phillips.

  I appreciated if anyone can give me a direction for this

  Thank you

  Roozi

  Your topic says 2003 but your message says version 3 - a huge difference. If you are able to load, it is not the version 3. See if you get an error message that the code is old to convert, then post to Conversion of Version map you linked to at the top of the page.

• Wiring of connectors in LabVIEW 2011 problems

  I've just been 'bitten again"by a wiring problem with a connector for a VI in LabVIEW 2011 (I've not seen this behavior in any previous version of LabVIEW to 7.0).

  The question is this.  I (or one of my colleagues, who also noted it), run LabVIEW 2011 (August 2011 release), 32 - bit, Windows 7, 64-bit systems.  I have create a VI using the usual 4-2-2-4 connector of mires and connect the appropriate connector.  I save the VI, then drop it on a block diagram to use.

  In another variation of this problem, the VI has fallen don't watch any connector or, if used to 'replace' an existing wired in VI with the same model of connector, "break" all the sons (because it has no connector when dropped on the diagram).  Reopen and reconsider the VI show that, indeed, the connectors are wired, but when I use the VI, the connector wiring is absent (the VI dropped watch without connectors).

  In the second variant, all right, the connectors appear as expected.  But I then decide to move a connector.  I have open the VI to edit, make a cut of this Terminal and rewire to its new location.  The connector pane presents the new model.  But when I drop the VI on a block diagram, the connector is in its original location.

  Restart LabVIEW, indeed restart the PC, does not change.  The only way to 'fix' this is to disconnect all terminals and a reconnect them.  A nuisance, to say the least, but also an obvious bug.

  Has anyone else seen elsewhere?  I sent to OR, but it would be useful to know 'is it just me?' or not.  In my defense, I've seen this problem on several computers, all win 7/LabVIEW 2011.  I've also seen this with several LabVIEW projects.

  I've attached a file with such a VI "buggy".  When you open it, you will see that the 'Length' indicator is wired to the top of the connector set page.  When I drop this VI on a new VI, however, the connector indicates coming out from the bottom!

  BS

  I was told by an engineer NOR that this problem (a) is real and (b) has been fixed in SP1 release (spring) 2011 LabVIEW.  I have not had a chance to check this point, but (the trusting soul that I am), I consider that this problem has been a "Bug in LabVIEW 2011 that has been fixed in the SP1 Release"and therefore, I am prepared to mark this "resolved".

• LabVIEW 2011 executable does not close

  Hello

  I created a very simple piece of demo code to try to discover Labviews Plugin architecture (please see attached).

  For some reason when I create my demo code in an executable file and click the button stop the façade that closes, but the program continues to run in the taskbar.

  I built, run and compiled my code in Labview 2011 SP1.

  My final actions for the main vi are to close the front panel and then call the function "Quit Labview".

  Failure to close occurs intermittently (it will close with success after 3 out of 4).

  I have attached my code.  Does anyone have an idea why it doesn't work?

  Thank you!

  
  

• How is it you can't use more than 126 GB of a 1.5 TB with LabVIEW Real-time hard drive?

  How is it you can't use more than 126 GB of a 1.5 TB with LabVIEW Real-time hard drive?
   
  It's only 8.3% of disk space!

  http://digital.NI.com/public.nsf/allkb/E7E2F5657B6026358625750B007201A6?OpenDocument

  The national Instrument is reformat that you drive less than 126 GB or replace the drive with a less than this size.

  Please OR tell me you go fix your LabVIEW Real Time soon, and that we will not have to wait for LabVIEW RT 9.2.1 in 2011 for this one to fix.

  http://upload.wikimedia.org/Wikipedia/Commons/9/90/Hard_drive_capacity_over_time.svg

  Readers as high as 126 GB or more have been around since mid-2002.  It's about 7 years now and LabVIEW Real-time STILL cannot use greater than 126 GB drives!  Please OR.  Do something.

  We deserve the patches for older versions of LabVIEW RT.  What about updates to LabVIEW RT.  As 7.0.2 7.1.2 7.6.2, 8.0.2, 8.2.2, 8.6.2.

  We don't need new features or versions of LabVIEW RT as 9.0 until we have some of the bugs fixed in existing versions.

  Kevin.