LabVIEW 2012 and DDE

Similar Questions

• Communication problems with third-party modules using Labview 2012 and cRIO-9024.

  Hi all

  I recently bought the module moviemed 1501 AF but I am unfortunately not able to communicate properly with him. I followed all the instructions in the Manual, but nothing helps. I downloaded the drivers and software recommended, but whenever I try to add the AF 1501 in special edition module C-series (in the menu drop-down), Labview does not see it.

  When I installed the driver for the module he asked for what version of Labview, I was running (2009 or 2010, no option to 2012), I chose 2010. Could be the problem?

  Thank you!

  Hi Mswn,

  I would just like to ask if you can see other modules of the series-C on your chassis - other modules appear correctly?

  I also see that MoviMed is no indication that they offer LabVIEW 2011 and 2012 of pilots to the AF 1501 hereproduct page. Here are the drivers you are using?

  Andy C.

  Technical sales engineer

  National Instruments

• LabVIEW 2012 Patch f1 crashes

  I just installed LabVIEW 2012 and unfortunately I've met a few worries.

  I got one "Installer has stopped working" when I installed device drivers.  But the installation seems fine.  LabVIEW began and MAX would open up.  I wasn't looking to connect to any material yet.

  When you try to install the fix for the f1, LabVIEW crashed again.  Net subsequent attempts the same thing.

  Has anyone else had this problem with the patch?

  It's on a Win7 with 8.6 and previously installed 2011 LV machine.

  

  Even if accidents are reported, all seems to be installed correctly.  It just seems like Windows is confused when the installation program stops.

  This seems to be a problem with Windows on my machine and not a problem with LabVIEW.

• Why LabVIEW 2012 does not support USB-6009?

  Hi all

  I recently installed LabVIEW 2012 and DAQmx 9.6 (and also tried with latest version) in my PC with Windows 7. I have the version of Explorer 5.4 measure and automation. I'm working with hardware DAQ USB 6009. Everything seems compatible, but when I try to post data acquisition, it fails. However, I used to use this device (since I bought it last year) with the other PC that has the Windows XP operating system and the older version of LabVIEW 8.5.

  What can I do with LabVIEW 2012 is a message "a 88302 error has occurred." and "This could be an internal error."

  If someone has an idea to solve the problem, please let me know.

  devkotaj

  Hi devkotaj,

  The USB-6009 device should work perfectly on Windows 7 with the software you have listed. This looks like a problem of configuraiton of material for me.

  What are you trying to do when you receive the error 88302? This error usually indicates a corrupt DAQmx driver, which may result from the installation of several DAQmx versions on the same machine. Have you tried repairing your installation DAQmx? I could uninstall DAQmx from the Control Panel before installing the latest driver. You can see our procedure to reinstall or uninstall recommenedd here.

  I hope this helps!

  Andy C.

  Engineering applications

  National Instruments

• Using an FPGA as a stand-alone system to run labview 2012

  Hello

  I have a request for my main project which is built using Labview 2012 and I want to transfer to a FPGA as it becomes a stand-alone system with no attached PC. I saw that labview for this but I do not know what card FPGA and the labview libraries are able to do this, and what is the mechanism to do this.

  Software details: LabVIEW Professional Development System version 2012
  Operating system: Windows 10

  T2dei wrote:

  What about Xillinx Zedboard? Y at - it approach to transfer of LabVIEW code directly without the conversion, in the zedboard?

  N ° Code LabVIEW FPGA only works on FPGA boards OR.  If you give us a better idea of what your project and what you want, we could probably give you a better recommendation.

  Furthermore, since this is for reasons of the student, give your representative OR a call and maybe they can cut you a deal on a Board sbRIO.

• I can't MJD (date and time) in LabVIEW 2012 SP1?

  I need some time my data of stamps before sending it to the file.  I did this with the standard calendar date and time but MJD is that we prefer to use.  How can I get a timestamp MJD in LabVIEW 2012 SP1?

  Check the JD MJD conversion formula
  http://www.IERS.org/nn_10828/IERS/en/service/glossary/MJD.html

  The modified Julian day (MJD) is defined as MJD = JD - 2400000.5, where JD is the Julian Day

• Why the continuous measurement and Logging in LabVIEW 2012 Project uses strings instead of Enums and orders from the queue?

  Hello!

  I noticed that the continuous measurement and a project in LabVIEW 2012 Logging using chains instead of enums and orders from the queue. I wonder if there is a good reason for it?

  Kind regards

  Anguel

  First, string vs enum debate is probably the version of LabVIEW vim vs emacs. There are good arguments on both sides, and I doubt that there is always a "winner".

  A brief summary of our reasoning for the current state of the project examples:

  1. We used enums for the state machine because it is self-contained. A state machine will never tell himself to enter a State, he does not know. Knowing (as the programmer) all possible States with the help of an enum allows you to enlist the compiler in order to help us avoid mistakes to change the time (because you can't quite out an enum and LabVIEW can be said if you are not covering all cases to a structure of the case, etc..).

     Enums provide greater protection and rigidity by ensuring all withdrew at the time of publishing. This is often the 'default' recommendation that we do.

  2. We used strings for messages in queue manager because the producer of message and the message handler could be independent processes that are reused or traded. Channels avoid the need for the compiler to be able to connect the orders and push this responsibility to the programmer. This allows you to develop some sub-components independently as long as you agree to a series of channel commands that you can manage - you need not to share a file 'messages.ctl' or 'states.ctl '. It is conceivable a loop of message management a message it does not, how you can decide to either silently ignore it or will trigger an error (as we do in the model). The strings make it also easier if you want to swap the queues of LabVIEW outside by a TCP implementation for network vacilitate or intra-Processuse communication where the other end may or may not be written in LabVIEW.

     Channels to provide more flexibility (that is, you can add new commands to an existing via plugins system, you can pass parameters as part of the string, etc.) at the expense of pushing her potential errors at run time and to put more responsibility on the programmer.

  3. The actor's gifts frame a 3rd option - using classes such as messages. For me, it combines many of the advantages of these two enumerations (strictly typed, change errors) and strings (flexible and scalable), but with the disadvantage of being somewhat less transparent (you understand OO, be comfortable to navigate through a multitude of screws, legacy of understanding, etc.).

  I don't know there are other reasons, others to the breast OR had or seen as we validated models and examples of projects in-house, but here are my reasons. We know that we can not design for each situation there - our goal is to get useful models against new users to make them aware of what well thought LabVIEW programs are similar to experienced users know their applications better and I hope they do not hesitate to change what we provide or create their own designs, when they feel it's necessary. (On a side note, please share what you come up with - a community of experts sharing models would be really useful to us all LabVIEW users).

  Best regards

  Simon

• Impossible to install LabView 2012 SP1 (64-bit)

  I've got license for LabView edition student of 2012 and I cannot download mentioned MS. Update says I need membership in the Standard Service program.

  Is what it means that I can't download it at all or there is problem somewhere else?

  I'm running on Windows 8 Pro x 64

  Other updates installed without any problems.

  Thanks for the reply

  Hello.

  I guess not. But you can always write your SN [email protected] license and ask them what products including versions are activated with your SN.

  Ondrej

  NIEE AE

• Cannot find FP write in LabVIEW 2012

  System: Win7 64 bit

  LabVIEW: LabVIEW 2012 (64-bit)

  I can't find FP read/write etc in LabVIEW 2012.

  I installed FieldPoint 6.11 and disk driver OR. Nothing happened... And I can't find "fieldpoint" folder in "vi.lib".

  I noticed that my Win7 "Program files" and "Program files (x 86)". The labveiw program was in "Program files", I think. But there is also a "National Instrument" folder in "program feels (x 86). I just used by default to install the labivew.

  Do not know why. Can anyone help?

  Hi Yang,

  FieldPoint is not supported with 64-bit LabVIEW.  I propose to install LabVIEW 32 bit and then see if you can see these FieldPoint VI.

  Kind regards

• Error-63101 when executing the FPGA Interface C API Generator in LabVIEW 2012

  I'm using LabWindows CVI 2012 and 2012 LabVIEW FPGA module.  I try to use the FPGA Interface C API generator and I get the following error from a freshly generated .lvbitx bitfile.  I use the local server compiles on my PC.

  Error-63101

  NOR-RIO: A valid .lvbitx bitfile is required. If you are using a valid .lvbitx bitfile, the bitfile maybe isn't compatible with the software you use. Determine which version of LabVIEW was used to make the bitfile, upgrade your software to this version or later, and then try again.

  The problem occurs when executing CVI or LabVIEW.  I was able to do this earlier when I was compiling the FPGA in LabVIEW with the API generator 2011 downloaded from the Web site.

  A bit of weirdness in my setup, it's that I charged it off downloads from the website (latest files after 2012 NIWeek) rather than the normal distribution DVD.  I installed LabVIEW, so NI RIO, then the Xilinx tools compatible with 2012.  It works very well when you talk to the FPGA to a LabVIEW vi running on my Windows PC to the host.

  Any suggestions?

  Problem solved.  I had to download FPGA Interface C API generator 12.0.  It works now.

  I would have thought that if a product was called on the menu in LabVIEW 2012, it would be prompted to upgrade to a compatible version, when I installed LabVIEW.  The old version is not compatible with version 3.0 bitfiles, as identified on the following lines at the top of the .lvbitx file:

  
  
   3.0

• Load a file EDS into LabView 2012

  Through research I found that DeviceNet Configurator is no longer available. I'm under LabView 2012 with IndComm/Devicenet 2.2 pilot. What replaces the DeviceNet Configurator? How to load the EDS files?

  Thank you

  Tennessee Paul

  My post here on a different topic, I thought that I would wear it to conclude this thread.

  Load an EDS file to the slave device

  1. Right-click on the slave device
  
  
  2. Select "Sheet"... »
  
  
  3. Click on add files...
  
  
  4. Navigate to the location of the EDS file.
  
  
  5. Select the file.
  
  
  6. Click OK.
  
  
  7. In the left pane, expand the data sheet newly added up to reach the node displays the version.
  
  
  8. Select the version.
  
  
  9. Click OK.

  Check the device and file EDS

  1. Right-click on the slave device
  
  
  1. Select utilities
  
  
  2. Select the Panel of Test online
  
  
  2. Select the option 'Device status' in the field of category on the left.
  
  
  3. On the right, select the slave device, you want to check.
  
  
  4. Click on "check the device".
  
  
  5. Read the errors/warnings or lack thereof.

  Edit the file EDS

  To change the EDS file, I used EZ-EDS , which is a specific devicenet EDS of ODVA freeware Editor.

  I did my corrections and saved my file EDS. (After having saved my original, of course).

  Remove the installed Labview EDS file

  1. Navigate to the following location: C:\ProgramData\National Instruments\NI-IndComm for DeviceNet\Datasheet
  
  
  2. Remove the sheet (Note: there is more that one datasheet added manually.) Additional EDS files come with the IndComm driver. Find the EDS file for the specific device that you want to replace and delete).

• Error Code HDL with CRio RFP generation after update for LabView 2012

  Hello everyone,

  I use a CRio DP Comsoft master/slave module for my communication with a PLC system. The application worked perfectly under LabView 2011. After the update to LabView2012, I got an error message that the HDL Code generation failed. After that I've updated also the Software NI Profibus CRio in Version 1.3, but this n ' t´t solve the problem. The next step was to use the example of project code "CS_cRIO-PB_DP-MasterExample" which was delivered with the new NI CRio Profibus software. Even with this code example, the problem still exists. For detailed information on the configuration and the error message please refer to the screenshot. Any help or idea would be appreciated.

  Jürgen

  Hi Jürgen,

  I looked inside and could reproduce this error. Somehow the compiler with LV 2012 has problems with the coded 8.5.1 Subvi LV. Please use the attached VI and copy it to the following location. (\\Program Files\National Instruments\LabVIEW 2012\vi.lib\addons\Comsoft.lib\cRIO PB)

  Before do you it please close your LabVIEW.

  Then try to compile again.

  Let me know if it still does not. We are currently working on a new installer that will correct this problem.

  DirkW

• Legend bug XYGraph slider blocks instantly LabView 2012

  Hello!

  I'm just facing a very annoying bug.

  Please find my attached VI example, I would like to know the weather, you can confirm the bug? Run the VI if you want to see a curve (in fact the bug appears even if you put all the data on the chart, if you do, all the same) and after that try to click the cursor vertical scroll bar legend to scroll upwards or downwards to see the cursor names.

  It instantly blocks my full version of LabVIEW 2012 Edition: 12.0.1f2 (32 bit). This XYGraph is still blocking LabView... I can't continue with my project, now I will just try to work around the error, I'll try to remove the sliders and then add them again...

  In any case, a very strange and very annoying behavior...

  Anyone could repeat the same bug?

  Thanks for the support!

  The reason for the accident seems to be duplication of the cursor "Gas_inject." There are four times. Using the property node 'CursorList' to remove these duplicates made the VI DO NOT crash when you move the vertical scroll bar of the legend of cursor.

  To simplify:

  Read the CursorList first, remove any duplicated the table manually in the indicator (right-click on the element > data operations > Delete Element). The change to a control, change the property node to write and run the VI once.

  Norbert

• 2013 LabVIEW allows the user to return to the LabVIEW 2012 or 2011?

  Hi all

  I have LabVIEW 2013. I noticed that in LabVIEW measurement and Automation Explorer (MAX) under the LabVIEW Run-Time 2012 SP1 f2 software is listed. This somehow means I can return or switch between LabVIEW 2013 and 2012 without having to install/reinstall?

  The reason why I ask, is that I have several instrument drivers written for LabVIEW 2012 sp1 I want to use.

  This is probably a silly question, I know.

  On a related note, is it possible to tell if a driver written for an older version of LabVIEW will work in a new version of LabVIEW? Or you just have to play with the software?

  Thank you

  Oh, John

  Hi John,.

  More explicitly answer your main question - you can install multiple versions of LabVIEW in parallel (at the same time, on the same PC), however that one version of patch of each major version (for example, 2011, 2012, 2013) can be installed - you can not install 2012 and 2012 SP1 at the same time.

  The runtime that you noticed has probably been installed with another component that was built in this environment.

  As Dennis said, the big thing to keep in mind is that your screws will have to be upconvertis/resized when moving between versions.

  If your instrument driver is written in 2012 LabVIEW using the serial at low altitude of LabVIEW drivers, it will certainly work in 2013.  If you open the screw driver in 2013 and that you do not see workload issues, you should be good to go.  If pilots request DLL or another have external dependencies can be involved more work.

  Kind regards

• exe created with labview, 2012 will not be run using LVRTE2013

  I created an exe using Labview 2012.  I had the user to install the latest rte (lvrte2013).  The exe wouldn't and told the user to TENS of 2012.  Should users have the same rte for each exe?

  Yes.  But different rural enterprises can co-exist on the same PC.