Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

I'm wondering if anyone else has seen problems like this.
I've been tearing my hair out over debugging some code. I have a ftont panel, I'm using some LEDs to send messages through the NI RS232 cable I bought, and have connected with a connector in a loopback fashion.
I've been trying to read the incoming messages from loopback...and based on those, changing indicators and controls on the front panel.
I could not figure why values were changing at strange times....like T's were turning to F's (I'm working with the serial data as boolean arrays).
Well, I was simplifying code, and mostly running right...but every once in awhile, it appeared that my front panel indictors, especially the values I'm changing based on the loopback serial messages would *BLINK*.
I happened to be looking at the Probe Watch window...and I saw where my probes were correctly showing on a couple spots (a left and right indicator) TTTTTTTF and TTTTTTTF......these appear at times to change T's to F's and vice versa.
I then started clicking around...and found this is almost always caused, when I click the mouse on the top of the window...the part that you usually click and drag to move a window around the Windows desktop!!!!!!!!!!!!
I can see this happen when I click on ANY window on the Windows OS desktop!!!!!!
It appears that the OS is messing with me..............?
I'm using Labview 2011, 32-bit on Win7....I believe the OS is 64 bit.
Has anyone seen behavior like this before?
Thanks in advance,
cayenne

Matthew Kelton wrote:
When you are probing, are you looking at the actual spot where you are getting your serial data, or are you looking at it after you've done some processing? I would look at the actual raw data and use a serial port capture utility (there are several free ones on the internet) which will confirm your data is coming in correctly.
What is your CPU running at? If it is pegged at 100%, something has to give.
Is your entire VI running in the UI execution system? If you post your test code, it sounds like it would be easy enough for someone to do a loopback test of their own to confirm similar behavior.
Thanks for the reply. No, CPU isn't being hardly used at all...this is a new lenovo laptop.....high end Dell U2711 monitor...
Task Mgr while Front Panel running:
I'm looking after I've done some processing....
I'm new to working with serial port stuff....I don't have a serial port capture device...?
Thing is...when I run this in debug with breakpoints and stepping through...I don't see this happening. But when running at full speed, and especially when I click on any of the open windows on my desktop, along the top margin where you would click and drag a window around...I can see the serial data in the probe jump...and all data going through the serial port and being displayed on the front panel changing values...
On my VI, I'm actually constructing the byte string...sending it through the serial loopback, and receiving it and acting on it. I can see the data going in is the same as is coming out...it just seems to quickly corrupt and then come back again...like maybe it is getting interrupted by the Win7 OS....?
I can't really post the whole code here...proprietary stuff...that's why in the past, I was posting a separate, simpler vi with only the parts I was having problems with....
I think I have full support with NI...I wonder if I could send them the code to look at, with more confidentiality...?
But again, I can make the problems happen, when it and the probe window is open, in real time...by clicking on windows.
Also, this tends to explain problems I saw earlier...when running slow, all was well , when debugging with break points and stepping through. But at full speed, unexplained...things would start resetting without explanation...and without regularity.
C
I"m not sure what you are asking with "Is your entire VI running in the UI execution system?"....I have the one vi running, and only that vi is running.....

Similar Messages

Adobe Acrobat V9 Professional crashes or causes PDFs to be corrupted when using Dragon software

Adobe Acrobat V9 Professional crashes or causes PDFs to be corrupted when using Dragon software. I use Nuance Dragon NaturallySpeaking 11.5 to assist me when I add comments to a PDF. I also use it when making additions or changes to text. When I use the two software programs together, Acrobat constantly crashes. If it doesn't crash, an error occurs trying to save the file. I entered 988 comments into a 158-pg PDF, only to find the file was corrupted and couldn't be printed. I also could not see the list of comments (click Show Comments).
These problems do not occur if I don't use both products simultaneously.

Never overwrite a clip that is used in Pr. Give the
modified/corrected/updated clip a new name and import that into your Pr
project. Then Alt+Drag the new clip on top of the old clip in the
timeline to replace the clip instance.
If import-then-drag isn't your style, then right-clicking the original
clip in the Project panel and selecting Replace Footage will accomplish
the same thing.
This important rule applies in Encore as well.
-Jeff

Can't install itunes on a new Win7 machine. Get a message "There is a problem with this Windows installer package. A program required for this install to complete could not be run"

Can't install itunes on a new Win7 machine. Get a message "There is a problem with this Windows installer package. A program required for this install to complete could not be run"

Have you completed all windows update including service Pack1? If not, please complete all the windows update then follow steps below to re-install all over.
1. Go to Microsoft website to fix install and Unistall problems. Click "Run now" from Fix it to remove all iTunes & related installer files:
http://support.microsoft.com/mats/Program_Install_and_Uninstall
Be aware that Windows Installer CleanUp Utility will not remove the actual program from your computer. However, it will remove the installation files so that you can start the installation, upgrade, or uninstall over.
2. You should remove all instances of iTunes and the rest of the components listed below:
it may be necessary to remove all traces of iTunes, QuickTime, and related software components from your computer before reinstalling iTunes.
Use the Control Panel to uninstall iTunes and related software components in the following order:
iTunes
QuickTime
Apple Software Update
Apple Mobile Device Support
Bonjour
Apple Application Support
Follow the instructions from Apple article listed here: http://support.apple.com/kb/HT1923 to remove all components
3. Reboot your computer. Next, download iTunes from here:http://www.apple.com/itunes/download/ and install from scratch

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

I'm hoping someone can kindly help with me with an error message that is causing PDF file generation failure when using InDesign CS6 for Windows and Acrobat Distiller 8.0

<PDFX ISO="15930-1:2001" COMPLIANT="true">
PDF/X Compliance Report
1. Summary
   Warnings: The total found in this document was 0.
   Violations: The total found in this document was 0.
   No problems were found in the document.
   This document passes PDF/X-1a:2001 compliance checks.
</PDFX>

@Jack – this is no error message, just a log, that all was running ok.
See detailed answer here:
Re: I am getting some errors while distilling the post script file.
Uwe

Serious Bugs in LabVIEW 2011

Dear Sir or Madam,
I have been working with LabVIEW for 10 years.
recently I have istalled the last version (LabVIEW 2011) and encountered some fundamental Bugs as bellow:
1-when I want to close LabVIEW 2011 Platform,it taks about 3 sec time to be closed ! while this was not in earlier version such as LabVIEW 9 sp1.
2-In a typical Front Panel,when I press Ctrl+M to chenge to Run mode,it went but after pressing Ctrl+M again,it will not exit from run mode(THIS BUG HAPPEN SOME TIMES NOT ALWAYS) or when I do right-click to view Function pallet or Control pallet,nothing happen!(THIS BUG HAPPEN SOME TIMES NOT ALWAYS).
I will be happy if you tell me what is the reasons and can I trust on LabVIEW 2011 for big projects or It is better for me to used LabVIEW 2009 as the past.
thank you for your kind attention.
Regards,
Ata Rahai,
Specialist Engineer.

Hi
I believe that 2011 is a very stable version (I was beta testing) and in my system the CtrlM works both ways, always.
Taking a few seconds to close is normal since version 8.0, depending on how many services are running. LV does clean up the system.
greetings from the Netherlands

Labview 2011 always disconnecting over wireless Ethernet bridge!

Hello, we recently upgraded from labview 2009 to labview 2011. We use a Labview cRio-9014 and FPGA backplane 9114. For connecting the cRio to our laptop we use Digi XPress Ethernet Bridge: Multipoint 900MHz industrial wireless part# XEB09. This program worked over our wireless link running labview 2009 with the old cRio software.
After upgrading the desktop, upgrading the cRio's software and recompiling the FPGA code we tested our setup via a wired ethernet connection and ran it all day with no problems. However once we switched to using our wireless ethernet bridges the cRio disconnects always 2-3 minutes after starting. It also does not allow us to reconnect without powercycling the cRio. The radio modems show a solid connect and no problems the whole time. Now I've searched through known issues and all over the forums without finding anyone having a similar issue so I hope someone can chime in and let me know if something else in LV2011 changed or what.
My current hypothesis is that labview 2011 uses UDP packets for status/keep-alive and our radio modems are not guaranteed to recieve all UDP packets. Please correct me since this is only a guess and I don't know what's going on under the hood on the cRio side.
P.S. I've captured the packet data using WireShark on the laptops side from deployment until disconnection but can't find any obvious problems. It's a fairly large file so let me know if it's needed and I'll try to find a way to upload it.
Hopefully someone can help.
Best Regards,
Sam Bingham
Great Lakes WATER Institute

Our host OS is WIn7-64Bit, and XP-32bit but they all display the same behavior.
cRIO hardware: cRio-9014 and FPGA backplane 9114
Our system is has 4 modules installed NI-9205, NI-9401, NI-9401, NI-9870, although we are only using the serial ports on NI-9870.
I looked for the NI TimeSync to remove but it isn't listed in our installation
Contents of current installation:
CompactRIO Support 4.0.0
DataSocket for LabVIEW Real-Time 4.9.0
HTTP Client 1.2.0
HTTP Client with SSL Support 1.2.0
I/O Variable Remote Configuration Web Service 1.0
LabVIEW 2011 Adaptive Filter Toolkit 11.0.0
LabVIEW PID and Fuzzy Logic Toolkit 11.0.0
LabVIEW Real-Time 11.0
Language Support for LabVIEW RT 1.0.0.4
NI Application Web Server 2.0
NI System Configuration 5.0.0
NI System Configuration Network Support 5.0.0
NI Web-based Configuration and Monitoring 2.0.0
NI-RIO 4.0.0
NI-Serial RT 3.8.0
NI-VISA 5.1
NI-VISA ENET Passport 5.1
NI-VISA ENET-ASRL Passport 5.1
NI-VISA Remote Passport 5.1
NI-VISA Server 5.1
NI-VISA USB Passport 5.1
Network Streams 1.1
Network Variable Engine 1.8.0
Remote Panel Server for LabVIEW RT 4.0.0
Run-Time Engine for Web Services 4.0.0
SSL Support for LabVIEW RT 4.0.0
System State Publisher 2.0.0
Variable Client Support for LabVIEW RT 1.8.0

Getting "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine

I am getting a "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine. I already tried running setup.exe as an administrator with the same results. I have Microsoft .NET Framework 4.5.1 installed on the affected machine. Could this be the cause of this issue? Or does someone know the root cause of such error?
Solved!
Go to Solution.

Hi - are you getting it at the start of installation, during or after 100% progress has finished?
Is it just LabVIEW you're installing, or is it drivers too, in which case, what was the last large package that was installing at the time?
This could be caused by the NVIDIA chipset driver :
https://decibel.ni.com/content/message/46299?tstart=-130
Thanks
Sacha
// it takes almost no time to rate an answer

Labview 2011 32-bit, Tescom ER3000, Windows 7 64-bit

I currently have Labview 2011 32-bit installed on a Windows 7- 64-bit machine. I am trying to run the VIs found in the attachment below, but I get the error that function called in the DLL has failed and that TESCOM.DLL may be in use. Any thoughts as to why this is happening? I've already checked to make sure the path referenced in the VIs' function call nodes is correct... any and all help is appreciated!!
~Avi
Solved!
Go to Solution.
Attachments:
ER3000.llb ‏139 KB

Greetings;
I have been reading up a bit on the company and the DLL itself, and are we sure it is supposed to work well with Win7? Would it be possible to try booting up LabVIEW in compatibility mode (XP) to try it out?
http://www.documentation.emersonprocess.com/groups/public/documents/data_sheets/der301767x012.pdf
Only mentions up to XP, hence the question.
National Instruments
Applications Engineer

Labview 2011 file layout in executable

I am working on upgrading my projects from v8.6 to 2011. one thing i noticed was that the file layout in the built executable has been changed to treat the executable itself as the root directory of the code sources.
To better address my problem, i would like to present an example as below:
I have two projects, A and B, where B is built on top of A. Their paths are:
C:\Workspace\ProjectA\source\Always_Included1.vi ...
C:\Workspace\ProjectB\source\Always_Included2.vi ...
in the built executable(ie. Application.exe) i found that all VIs were located under such as:
Application.exe\Workspace\ProjectA\source\Always_Included1.vi ...
Application.exe\Workspace\ProjectB\source\Always_Included2.vi ...
Since the "Workspace" is just a variable name for one of my workspaces, I am wondering if it's possible to make the built executable to start with one level deeper, such as:
Application.exe\ProjectA\source\Always_Included1.vi ...
Application.exe\ProjectB\source\Always_Included2.vi...
*notice that the "Workspace" has been omitted.
Thank you.
LabVIEW 2011 newbie >.<
Certified LabVIEW Developer

I don't think there's a way to really control this, as this is something which is done automatically by the application builder.
A couple of options I can think of:
Place the top level VI in a level above ProjectA and Project B. This might cause the EXE to consider that as the main folder and start from there.
Check the 8.x check box in the Advanced page of the build settings. This will cause the build to be flat instead of a hierarchy, but I wouldn't recommend that, as that's basically a flag for backward compatibility.
The real question is what's your actual problem? Most people don't care about the actual location of the files inside the executable. If you do need access to a specific file, using relative paths is generally enough, as they stay the same inside the EXE. Another option which people use to control this is to direct some VIs to be saved outside the EXE (the build spec allows you to do that), but that's usually for specific use cases, such as calling plugins.
Try to take over the world!

LabVIEW 2011 Development System fails to install

I have just tried several times to install my new copy of LabVIEW 2011 Dev Suite, but get an unknown exception (with no details - see attached picture) right at the start of installing the development system (English 32-bit). I have rebooted and closed all applications including virus scanning but still the same. I am using WinXP Pro SP3, and already have LV 8.6, 2009, and 2010 installed. I'm completely baffled as this type of problem has never occurred before and there is no information about the cause of the exception.
Mike
Solved!
Go to Solution.
Attachments:
LV2011 Unknown Exception.JPG ‏10 KB

Hi John,
After clicking on Details, the words "No information" or similar are displayed. I have tried again today but with the same result. I have attached a new screenshot showing the installer initialisation progress window. I have checked the DVD and it looks undamaged, and there is plenty of free disk space.
Attachments:
LV2011 Unknown Exception.JPG ‏64 KB

Error in invoking the build rule editor, LabView 2011

Hi all. I'm having a problem in Project Explorer. When I right-click on 'Build Specifications' and select New:Application (EXE), I get the following error dialog:
"There was an error in invoking the build rule editor. Please check the corresponding provider directory to see if any VIs are broken."
After this appears, no build specification is created.
I built this application in LabView 2010 on WinXP and was able to compile and run it sucessfully many times over the last few weeks.
The problem started yesterday when I had a problem with a Ring control. I right-clicked it and selected "Edit items" or "Properties" the cursor blinked for a moment but the dialog box did not appear. I removed the Ring control and replaced it with a String control, then when I tried to build the application, I got this error message. At that time, I also noticed that I could not get a Properties dialog box to appear for any controls or indicators.
Yesterday, I installed NI Developer Suite 2011 Version DS2. This seems to have fixed the problem with the dialog boxes and I was able to use the Ring control. However, I still have the problem with the build rule editor.
To determine if there was a problem in my program, I built a new 'Hello World' .vi with just a string control and string indicator. This program has the same problem when trying to build to an .exe.
Currently, I am trying to remove all previous versions of LabView. When that is done, I will reboot and try to build again. If that doesn't work, I will remove ALL National Instruments software and re-install NI Developer Suite 2011 DS2.
I'm hoping someone can provide a solution before it comes to that.
Two other facts which might be relevant: I don't have Administrator on this machine, although I could probably get it if I could make a strong case. Also, I can't be sure, but I think the problem may have started when I undocked my laptop from the docking station to go to a meeting.
I appreciate your help. Thanks in advance.

If you need additional assistance, I encourage you to create a new thread. It is more likely to be answered by other users as a fresh post.
The most likely cause is a corrupted file (or files) in the builder directory.
I would recommend renaming/moving the following folders and performing a repair install of LabVIEW:
\National Instruments\LabVIEW 2011\vi.lib\AppBuilder
\National Instruments\LabVIEW 2011\resource
Regards,
AnjelicaW.
Regards,
Anjelica W.
National Instruments
Applications Engineer

Statistics Express Kurtosis inconistency Labview 2011 (Bug 215683)

Hi All,
I am currently working with a data collection program from which I need to output the skew and kurtosis values for an array of 30 data points. As I was already using the Statistics Express VI to calculate mean, s.d. etc. I just added the skew and kurtosis outputs to that VI. I then set up a basic VI to generate a 1D array of random numbers to let me compare the Express VI to the skew and kurtosis VI on the mathematics > probability and stats. palette.
The skew and kurtosis values are inconsistent between the two VIs. If I calculate the skew and kurtosis by hand I can see that the non-express VI appears to be giving the correct answer. I did some digging and found that this has been labelled as bug no. 215683 and is described as having been fixed as part of Labview 2011. I am running Labview 2011 with SP1 so I'm not quite sure why the two VIs are still inconsistent.
I realise that I can simply use the VI which is giving the correct answer but I am curious as to why a bug which should be fixed still appears to be active in my version of Labview.
Any thoughts/ input would be greatly appreciated.
Many thanks in advance

Hi cat,
why don't you get rid of that buggy (as it seems) ExpressVI?
The remaining data (StDev, variance) are provided by just another function from math->statistics palette…
You can also opne the ExpressVI to see, how it calculates those data and why it does produce different results!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

LabVIEW 2011 to 2010

Hi all,
Need help to convert VIs attached below (LabVIEW 2011) to LabVIEW 2010.
Thank you very much
Solved!
Go to Solution.
Attachments:
Arduino mod for apc220-43.zip ‏4908 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
NET Basic Serial Write and Read (1).vi ‏17 KB

Labview 2011 64-bit install problem

I'm trying to install the 64 bit version of LabView onto a win7 64 laptop. The install seems to go ok. When I try to run it, it crashes with this exception 0xC06D007E$r. I've tried uninstall/reinstall and I still get the same error. I have the 32 bit version of LabView 2011 installed on this machine and it runs fine. What else should I be looking at?
Thanks
dp
Attachments:
lvlog.txt ‏2 KB

To address the point made by smercurio_fc, the Program Files (x86) folder is generally reserved for 32 bit applications. As I understand, Windows uses the distinction purely for organization. Having done more reseach, I will concede that we should look for a different workaround.
By your responses, it seems you may not need LabVIEW 32 bit. This article discusses the pros and cons of each version. This Q&A may be particularly useful in deciding whether or not you can continue on 64 bit alone.
Q. Which LabVIEW modules and toolkits are available for LabVIEW 64-bit?
A. Currently, the NI Vision Module, Application Builder, and Measurement Suite for Fixed WiMAX are available for use in LabVIEW 64-bit. Any other modules and toolkits must be run using LabVIEW 32-bit. See this Developer Zone Tutorial for more information.
Depending on your applicaion, this could be our solution If you are able to install LabVIEW 64 bit after uninstalling the 32 bit version.
KyleP
Applications Engineer
National Instruments

Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

Similar Messages

Maybe you are looking for