LabVIEW 2009 shared Variable Crash

Similar Questions

• LabView 2009 Web server crash

  Hi all!

  Here's a simple VI containing any control, functions or library in LabView 2009 f3.

  

  Web server settings are default. After the tools-> operation of another PC Web publishing tool we are connecting to this Panel (IE6 for example) and put a finger to the F5 not lifting.

  Web page with the VI is very refreshing.

  There are 3 results.

  1. in DevEnv: LabView die.

  2. in DevEnv: need to restart LabView for charging Web server and restore connection.

  3. in App.exe: die

  4. in App.exe: LabView interpreter loose some time-cycles in the cases where they exist, but connection stored.

  5. in App.exe: but lost connection application work.

  Is this normal? Are there settings in Web server to avoid this situation.

  
  

• Sharing of Variable crashing LabVIEW

  It's just one of those projects that has a wall of brick in each round so far. Two computers running LV2009. Computer A hosted data write sharing Variable. Computer B shared reading Variable data hosts. Reading data is linked to write data. Everything worked fine, and then yesterday afternoon, I don't think I changed anything on the shared variable, I start my VI on the computer B and LV crashes. The VI begins to run before the first performance for reading data, and then poof, everything open in LV disappears. Since then the problem is reproducible 100 percent.

  Here's what I know:

  1. an error indicator hooked to reading data watch-1950679034 (shared Variable has no value) for about a second before the accident. Everything stops execution as soon as the warning.

  2. writing of data is a single editor, but it is also sometimes read in VI it is written in. It is not read when the accident occurred. I can however perform playback on computer A without incident.

  3. don't know if this is related, but if I open the VI on computer B and then open the project, I am not able to drag data reading of the project on the block diagram. I also cannot perform operations on the shared Variable (as right-clicking, ignore the timestamp). I have to close the VI and reopen the project. In retrospect, this problem might have started when I opened the VI without opening the project.

  I'm torn between abandoning the shared Variables and try to understand it. I would definetely prefer to use the Variable shared, mainly because I need a buffering. I guess I can put other things buffer. Don't know if I can remote access to a queue, or...?

  I was able to reproduce the crash that you see with extreme simplicity VI in LabVIEW 2009.  This looks like a bug in LabVIEW, so I'll check if there is any of this behavior already.

• LabVIEW 2009 Crash when record for previous

  I'm having a problem when you try to save a VI in LabVIEW 2009 to a previous version of LabVIEW, in this case 8.2, but itseems crashing no matter which version I chose.  I've narrowed the problem down to this:

  If the vi contains a structure of event I get the following error: unrecoverable internal error: 'MemoryManager.cpp', line 547

  If I remove the structure of the event, she records very well.  I even go the error if I create a vacuum vi and drop an empty event on the diagram structure.  No control, no other code.

  Is this a known issue?  Is this a problem with my copy of LV?  Is there a solution?  Removal of the structure of the event in the present application is not an option.

  Thank you

  Rob

  So the solution is to save to LV 8.6, then open in 8.6 and save here to earlier versions.  It works, I have not tried to save 8.6 initially.

  Rob

• LabVIEW 2009 linux crashes when editing a control, or a constant of resources VISA

  Linux crashes when I click on a constant resources VISA (block diagram) or control (front).  This happens on LabVIEW 2009 SP1 32-bit for Linux on CentOS (similar to RedHat 6.3) 6.3.  I have updated drivers VISA 5.1.2 and that did not help.  Thanks in advance for any ideas of five Linux guys out there.

  Hello Jason,

  My problem has been resolved with LabVIEW 2012.  To answer your question, LabVIEW would crash only trying to select another device in the list.  Thanks for your help.

  Kind regards

  Marvin

• LabVIEW 2009 SP1 crashes when moving large selection with the arrow key

  If I select a lot (10 or 15) diagram components and try to move some distance with the arrow button, I'm often a program crash.  Because a reduced number of components seems to hang after a longer distance traveled, it looks like some sort of buffer overflow error.  I don't see this problem when you use the mouse to move selections.

  I checked to make sure I have the latest version of the video driver for my NVIDIA Quatro FX570.  I also tried to work with no hardware acceleration and no handset, written.  What happens on Windows XP SP3 with all current updates.

  It became so bad that I have to do a save as every fifteen minutes to avoid losing data.

  Why not use my mouse for all movements?  Because it is not as specific and not so easy to limit to only one dimension of the movement.   My hand is not as stable as it once was.

  I'm hoping someone will have a suggestion that will clear up this problem.

  As I have indicated, I had the same problem with 8.5 and just DID a new install of Labview 2009.

  Since it is possible that my three monitors configuration, which of course requires more memory video, may be at the origin of the problem, I am satisfied with workaround by dragging the objects closer to their final destination and then using the arrow keys.

  Three monitors are ideal for the front, block and help/Internet/probe damaged.  When I got to work in the field with a single monitor, I felt severely handicapped.

  You can consider the issue closed.

  Thank you for trying to reproduce the failure.

• Cannot bind to the shared object created with LabVIEW 2009

  I have problems referring to a shared library built from a LabVIEW VI under RHEL 5 with LabVIEW 2009.

  To illustrate the problem, I created a VI with a digital input and output that corresponds to a certain number. Then, I created a draft specification of build to create a shared library with a feature that makes use of this VI square. The shared object is created successfully (square.so).

  When I try to compile a test application written in C, that connects to this library, I get errors in the following link:

  cc  -I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintools build/square.so  test.c   -o test/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'collect2: ld returned 1 exit statusmake: *** [test] Error 1
  

  Running ldd reveals that liblvrtdark.so.9.0 is used for the execution of labview.

  In order to investigate on what could be the cause of the problem, I have compiled the nidaqmx basic examples, and I don't have an error. Current running ldd as reveals that he uses liblvrtdark.so.8.2 for the view of laboratory, time of execution.

  My suspicion is that some components of labview are being compiled with gcc 3.4 while others are being compiled with gcc 4.1 (which is the default compiler in RHEL 5).

  Any ideas how I could fix the build errors?

  Thanks in advance for your suggestions.

  PS.

  I enclose a tar file with the source files and here are the details of the ldd:

  ldd build/square.so         linux-gate.so.1 =>  (0x008de000)        liblvrtdark.so.9.0 => /usr/local/lib/liblvrtdark.so.9.0 (0x00b9c000)        libc.so.6 => /lib/libc.so.6 (0x00110000)        libstdc++.so.6 => /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 (0x009a7000)        libm.so.6 => /lib/libm.so.6 (0x00756000)        libdl.so.2 => /lib/libdl.so.2 (0x00256000)        libpthread.so.0 => /lib/libpthread.so.0 (0x0025a000)        /lib/ld-linux.so.2 (0x00b80000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00272000)
  
  ldd /usr/local/natinst/nidaqmxbase/lib/libnidaqmxbase.so.3.3.0         linux-gate.so.1 =>  (0x00e50000)        libnidaqmxbaselv.so => /usr/local/lib/libnidaqmxbaselv.so (0x00248000)        libc.so.6 => /lib/libc.so.6 (0x00689000)        /lib/ld-linux.so.2 (0x00b80000)        liblvrtdark.so.8.2 => /usr/local/lib/liblvrtdark.so.8.2 (0x00e51000)        libdl.so.2 => /lib/libdl.so.2 (0x00813000)        libpthread.so.0 => /lib/libpthread.so.0 (0x001b0000)        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x009c7000)        libm.so.6 => /lib/libm.so.6 (0x00b0a000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0050c000)
  

  Hi mimi,

  I'm happy to report that I managed to get the code to work. I have included some of the steps I experienced the problem in case it might help improve the documentation or future generations.

  In response to your question about the "error 1" reported by do, it's just an indication that detected a compiler error (it probably resembles the return code of the compiler).

  The errors ' undefined reference... @GLIBCXX_3.4.9 "have been narrowed down. The generated labview shared library, the square.so, links to /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 which is a symlink to usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6.0.9. I decided to compare this version of libstdc ++ that included with RHEL:

  strings /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_3.4.9GLIBCXX_FORCE_NEW
  

  strings /usr/lib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_FORCE_NEW
  

  So libstdc ++ RedHat does not include a string for GLIBCXX_3.4.9.

  With this in mind, I was able to get my test application to compile using the version of LabVIEW libstdc ++ using the following makefile:

  .PHONY: all cleanCPPFLAGS=-I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintoolsLDFLAGS=build/square.so \        /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 \        -Wl,--rpath -Wl,/usr/local/lib/LabVIEW-2009/patchlib/
  
  all: test
  
  clean:        rm -f test *.o
  

  When you try to run the application, I got the following error:

  ./test: error while loading shared libraries: /usr/local/lib/liblvrtdark.so.9.0: cannot restore segment prot after reloc: Permission denied
  

  But apparently, it's because of SELinux prohibiting the use of libraries shared with moving text.
  This can be disabled by running /usr/sbin/setenforce 0 as root.

  The test application now works!

  See you soon,.

  RW

• Shared variable between 2 LabVIEW executables via the network

  Hello, I need to create a number of network shared variables by two (built with LabVIEW 8.6) executables running on two different computers on a local network. The library to invoke node returns an error when you use a different IP than localhost. even more, it is not clear to me what exactly I have to do (what executable deploys the library, on which targets, activate the link or not, so on...). Thanks for any help, if you have already managed to make this communication works properly...

  Thanks for the replies. I've found the last two documents, but the first one is the most interesting: if I can't put the sources of two applications in a single project, I will move to another solution (data as suggested by Mike sockets or TCP). The two original projects are larger, and their merger would lead to such a huge thing!

• My compiled program crashes after the first run (LabVIEW 2009)

  I have a compiled program created with LabVIEW 2009 which, in the first round, once the computer is restarted, works fine but after discontinuation of the program, it will not work properly.

  The program uses a compiled Launcher to dynamically activate a set of VI containing the expectation driven by State Machines (QDSM).  Begins subsequent program launcher module appears fine, and his progress bar shows that she starts each of the VI.  Once the Launcher is complete it removes memory launched Dynamics VI and caressed.  The spear that do not reach the main UI that VI is barely long enough for the observer to see (if there is one) then stops.  The program then went from memory I can say.  There is no process in memory or anything.

  Also, when I try to run the installed version of the exe file on a computer with installed 2009 development environment I get this behavior consistently successful launch once again.

  In both case, my program does raise all errors (that are connected), or runtime generates everything I can see.  Also, when I run my program in the development environment the program does that way.  He has no problem at all.

  I have used this style of architecture front of LV8.6 with all the problems.  Can anyone suggest some possible solutions or even a few debugging tips?  I've never had a problem that I could not duplicate in the development environment, so I'm not sure how to start to attack my question.

  Thanks for any help.

  Jason

  

  I solved the problem I think that (at least with regard to the tests on this point revealed).   After that I added the possibility to connect the past States to of the QDSM, I was able to determine that the program was 'plant' after that I dynamically closed the Panel front of the Launcher.  My program is designed to close the Panel before the pitcher, then pop up the façade of the main user interface.   My EXE is inspired to hold the Launcher with my other files QDSM kept outdoors in specific directories.  What seemed to be happening is that when Launcher closed its façade and before UI opening upward the runtime engine decide since it is y no Windows Open he was closing down.  It's my guess on what might happen any way.  I modified my code to change the Launcher window to hidden and delay for 1/2 second to give a chance to fully start running to the main user interface.  This will correct the problem, or at least worked around her.  If someone out there can explain me exactly what is happening that I sure would appreciate it.

  Thanks for all the help that those of you who responded.  Your advice has been very beneficial and certainly led me to a faster resolution.

  Jason

• How to interface a simple way using LabVIEW 2009 simulink model and SIT?

  Hello

  I finally found a way to use a template simulink with LabVIEW and the Toolbox to SIT, but I'm not satisfied.

  If you have any suggestions, the link of resource that I missed, please do not hesitate to answer

  Note that I do not know much about simulink, so that is my question seems stupid, let me know what

  Software configuration

  OS: Windows (not an RT target)

  LabVIEW 2009

  SIT 2009

  question 1: interfacing the model DLL (mapping considerations) with a driver VI

  We have created a model of DLL by using the 'Workshop in real time' tab in simulink.

  In LabVIEW, launch us the tool 'SIT connection manager' and try to use the DLL with a driver VI by mapping the e/s model for screw/lights orders.

  The fact is that I fail to connect to my controls/indicators VI/o model because they do not appear in the mapping dialog box.

  The simulink single objects that I managed to map are "constant" and "test points" while I need to edit the template simulink itself (example below)

  

  Are in e/s model, not considered as part of the parameters of the model? (this could make sense because the mapping says in fact that it operates on "model parameters")

  Is it possible to link the IO model VI commands/lights?

  Note:

  -the "configure HW i/o mapping" dialog box allows me to map model e/s with e/s HW...

  -The examples also use these "constant" and "test points".

  2nd question: use of direct screw SIT

  I tried to use the DLL directly with the screws SIT (code example below)

  This kind of code works well on another project (target of 8.0/RT LV) but not on the current project (LV 2009/Windows)

  The second stage of the model never ends:

  -0-index of the loop works as expected (model doing its job).

  -index of the loop 1 starts normally, but execution is stuck in the 'SIT scheduler.vi.

  Then I have no choice that to kill LabVIEW ("Reset screws" windows appear if I try to stop/close them).

  

  Is there a reason that I do not see what explains this behavior?

  Thanks for reading.

  Any help appreciated.

  Kind regards

  Hello

  I spent some time analyzing the VI driver as you suggested.

  Here are my findings.

  Question 1: the SIT connection manager does not pass to the model SW controls/indicators. Only, it allows the user map HW AIs/AOs.

  The only solution I found (to have a SW - for example a shared variable - object that is mapped to an input/output model) is to customize the VI driver that is scripted by the SIT Connection Manager ("_Baserate Loop.vi" in the flat sequence structure named "read code")

  Question 2: after spending some time in the VI driver, it seems that the VI to call right is not 'SIT scheduler.vi' but 'If SIT take model no time' (which uses the other as a Subvi)

  

  My conclusions are correct? If I use the API in the wrong way, please let me know.

  Kind regards

• Support of the shared Variables in the third part XP embedded based of PTC?

  I sent a request in an embedded XP touch function (third party). The application works very well, but hosted on a RT (sbRIO Board) shared variables are not getting updated in the app on PTC

  1. the PTC is part of the project as a Windows XP Embedded Touch Panel

  2 NI TPC Service has been installed on the PTC and the application can be deployed remotely from the PC development via ethernet. (Where network connections and communications are OK)

  3. using distributed in the development computer systems manager, I can see that the shared variables are getting updates on the network

  I think that the problem can be solved if the following programs are installed on the TPC

  A. Support for variables that are shared for XPembedded

  B. shared Variable engine

  I tried to install the support of variables shared Program Files > National Instruments > Labview 8.6 > PDA > utilities > Variables > x 86 - but I get an installation error "cannot find the application for the Pocket PC applications Manager.

  Shared variable engine was installed from the ve220 folder. The program is installing. But the engine Variable is not start Control Panel > administrative tools > Services, Xpe, the service is stopped and cannot be started. When I try to start the service, I get the following error on PTC

  "Cannot start Service engine of National Instruments Variable on the local computer."

  Error 1053. Service has failed to demand launch or timely control.

  Please suggest solutions to the addresses above or another of the following:

  1. support of variables shared for XP built-in PTC

  2 Installer engine Variable shared.

  Thank you

  Krish

  Problem solved!

  Update for interested people working on XP Embedded PTC

  Just to ensure that shared Variables were indeed accessible to the TPC, I wanted to install Distributed Systems Manager 8.6 on the TPC. However given that the TPC was only 1 GB of DOM (disk on memory) and with all the software that I had tried, there remained only a few megabytes on the system. I had to add an another DOM of 2 GB.

  All products in the Installation went well, with the exception of the Logos NOR (Version 5.0). Logos OR installation has failed repeatedly.  I tried to install NI Logos separately, with the same results. Then I had this intuition that NI Logos had anything to do with the question.

  Then, I downloaded the new version of NI DSM 2009 SP1. Even if it were to settle on any fresh system without Labview, the installation would not proceed beyond the stage of configuration. I tried to install NI Logos of the folder on the download of new products separately and it worked magically!

  Once the new Logos (Ver 5.5) installed, the Shared Variable engine starts automatically and the shared Variables are finally unleashed - free stand up and shine! I thank Almighty God!

  On the lighter side, come to think of it - to run an application about 400 KB, we need NEITHER of Run Time, XP embedded, DSM, Logos...  (around 900 MB). Can make us everything simpler?  Invite your comments...

  Thank you

  Krish

• Shared variable refuses to deploy correctly!

  My problem looks like one that has been met before, but without good answers on the documents OR or the forums. When you try to run a VI that deploys shared variables, I get an error that the shared variable engine was not found. This seems to be almost at random, because I was able to deploy perfectly shared variables. He could have when I rebooted my computer this problem started to occur.

  I tried to disable the firewall, which had no effect. LabVIEW 2009 reports the following when I try to start my VI:

  "LabVIEW: (Hex 0x8BBB0005) Impossible to locate the variable in the shared Variable engine."  Deployment of this variable may have failed.

  This error or warning occurred when writing the following shared Variable:
  \\.\fake_data\flow_sh
  \\.\fake_data\flow_sh".

  I will include all relevant files so that you can see exactly what I'm doing. The purpose of the fake_data program is just to practice using shared variables, very simple. Thanks for any idea that you can offer!

  my shared variables work once again, I just open cmd.exe and typed:

  net stop "national instruments variable motor.

  followed by

  net start "national instruments variable motor.

• RT target does not read shared variable hosted by host

  Hello

  I just started to move my LabView application to a system of RT, and I came up with a problem. When I host a shared variable network-published on the RT target, I can access through vi running on the target and the host (which is good!). However, when I have this host on the host variable (such as by simply dragging on 'My Computer' in Explorer projects or all create a new variable), the vi running on the target RT is not read.

  I wonder if there is a problem with my installation of LabView, or if there is some step I'm missing. Any suggestions would be greatly appreciated!

  My host is running Windows 7 x 64, with LabView 2009 SP1 32 - bit. The objective of the RT is a real-time OS-powered desktop PC. I have attached a very simple project to illustrate this problem: I start 'Target VI' and 'Host VI' at the same time. On 'Host VI', I change the values of the two shared variables: 'hosted host' and 'target hosted. Only the changes made to the target "hosted" appear on the 'target VI'.

  Thank you!

  Andrew

  Take a look at this link (software configuration and firewall hardware to support National Instruments products) and this link (configuration of firewalls and routers network address translating shared Variables) to see if this highlights exactly what you need to explain in your application regarding the definition of the firewall exceptions.

  David has.

• Meet an applescript event in LabView 2009 (Mac OSX) VI

  I have a LabView VI that works constantly, acquisition of data at a remote location.  I recently bought a UPS for power cuts, and I would like to be notified by LabView by e-mail that an event has occurred.  Can I have the UPS software run an executable when there is a power failure, so my question is this:

  How to run an executable file (preferably AppleScript) and have it trigger an event in LabView 2009?

  The main VI is still running, and I would like to respond to an event and send a mail/text to the appropriate personnel, so that they can respond accordingly to the power failure.  In addition, if power failure, I can then stop the experience "smoothly."

  It seems that all the pieces have to exist to do this, but I can't find a way to get there.  Thank you in advance, this will make many people happy!

  News: Mac OS X 10.5.8, LabView 2009

  Hi jumpman Jr,.

  When you say that the UPS software may run an executable file, which means that it can run an executable of LabVIEW? If so, you can write a small executable of LabVIEW to send an email to a specified address. In the measurement of the notifying the main VI that is running, you can try to communicate between the executable and the VI using the methods of normal communication of VI at VI, i.e. global variables, functional global variables, shared variable network published, or even tax filers or queues. Then you can safely leave your main VI.

  Aaron P

  National Instruments

  Technical sales engineer

  http://www.NI.com/support

• to connect to a shared variable (android)

  Hello

  I just started to learn how to use the dashboard data Labview for android.

  I made a very simple project, with a VI that generates random numbers. I also added a variable published network shared in this project, and I write the random number generated for this variable shared every second.

  I would like to read this value on my phone (Motorola Razr i, Android 4.1.2) android using the dashboard of data for an Android application.

  I have a wireless access point and both my laptop (that hosts the project, LabView, Labview 2013) and my smart phone is properly connected to the wireless router, and both gets from dynamic IP addresses.

  I start running my VI on the laptop and the variable shared within the lvlib correctly deployed and began to broadcast (I guess) its value to the network.

  I start the DD application on my Smartphone, I choose 'Connect shared variable to', I type the local IP address of my laptop, which is 192.168.0.100, and I try to connect.

  After some 'research' and waiting, I get a message "connection error".

  Do I did wrong?

  Thank you much for the help.

  Best regards