Labview program halts after 124 iterations

I have developed a VI which takes data from a hardware through serial port.I have employed stop and wait technique so in one iteration the VI transfers 2 bytes serially to the hardware and recieves 8 bytes.After around 124 iterations the program stops for 3 to 4 seconds and then starts again taking the data.I have tried alot to identify the problem but its there.I am using labview 8.5 professional version and windows Xp.
Thanks

Hello,
could send epurated code of your vi,
it will be easier for us to help you
@+
Tinnitus
CLAD / Labview 2011, Win Xp
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail
Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte

Similar Messages

LabVIEW program crashes after running for few hours

Hello,
I am doing some experiments at the moment which are supposed to last for 18 hours.
Basically, I use a LabVIEW program to control a power supply through a LabJack U6 DAQ. I am currently using LabVIEW 8.5 on Windows 7.
In order to do that, I use a laptop where everything has been disabled such as power management settings, network access is off, windows updates are also off...
As far as I know, the computer can't turn into sleep mode or just shut down (I'm a 100% sure of that actually).
But last night, I started an 18 hours experiment at 5 pm, and when I came in this morning, the program shutted down by itself. Fortunately, the power supply is still providing the voltage I want, but I can't figure out why the program crashes.
When I start the experiment, it also automatically starting saving data in a spreadsheet file (I guess the size of the file should be 36 MB), so it might be a problem of memory access or something.
I really don't know what could have cause this crash, does someone have an idea?
I saw some other threads similar to my problem but I am not running an executable, I am running the front panel directly from the editing mode.

Hi,
thank all of you for your quick answers!
@Josborne : I do not have an error handling in my program. Actually you can look at my program in the attachment file. This is my first LabVIEW program so I've never dealt with error in and error out function... Moreover, what is a log file exactly?
@Johnsold : Yes, I am building an array continously growing over time. Actually, my program stops saving data when you hit the "STOP" button, it doesn't write into a spreadsheet file through a period of time, that is something I eventually need to correct.
@LabJackSupport : I can try to reduce my time step, so far it's 100 ms. I have a problem with disconnecting the USB cable from the computer though : for no reason, if I just unplug the connection between the LabJack U6 and the computer, my power supply will just go providing 157 Volts! And for my experiment, this is something we don't want to have so we just leave it as it is now. Disabling some part of the program is a good idea, I can try it
Thank you for your answers
Attachments:
Control Software.vi ‏511 KB

Labview program stops running correctly after computer is switched on one hour

Hope to get help on this strange problem.
I have a Labview program (executable using a run time version) running on a
portable computer (Dell Inspiron 4000 with Windows ME) which collects
measurement data and stores these to a file over a long time period. When I
start up the portable and then start my Labview program, the program fails
to work correctly exactly one hour after the portable has been started (in
fact, the program remains active but stops collecting and writing data).
However, if I start this Labview program just after that the portable has
already been active for one hour, the program is not interrupted and
continues to run for hours without any problems.
Obvi
ously, I have switched off all power management, screen savers, virus
scanners etc. to avoid interference of these, but without success. I have
run the same Labview program without any problems on a different Windows ME
system. Also on Win98 or 95 systems I have observed no problems. Does anyone
have a tip to which program or process could be activated in Windows ME
exactly one hour after the computer has started up and which might interfere
with Labview applications (when I look at all tasks running under Windows ME
I don't have an idea where to look at first).
Thanks in advance,
Martien

Did you shut off power management in the BIOS setup also?
Sounds like something is scheduled to go to sleep at 1 hour,
either the serial port or hard drive?
"Martien Janssen" wrote in message
news:wfyf7.445764$[email protected]..
> Hope to get help on this strange problem.
>
> I have a Labview program (executable using a run time version) running on a
> portable computer (Dell Inspiron 4000 with Windows ME) which collects
> measurement data and stores these to a file over a long time period. When I
> start up the portable and then start my Labview program, the program fails
> to work correctly exactly one hour after the portable has been started (in
> fact, the program remains active but stops collecting and writing data).
>
However, if I start this Labview program just after that the portable has
> already been active for one hour, the program is not interrupted and
> continues to run for hours without any problems.
>
> Obviously, I have switched off all power management, screen savers, virus
> scanners etc. to avoid interference of these, but without success. I have
> run the same Labview program without any problems on a different Windows ME
> system. Also on Win98 or 95 systems I have observed no problems. Does anyone
> have a tip to which program or process could be activated in Windows ME
> exactly one hour after the computer has started up and which might interfere
> with Labview applications (when I look at all tasks running under Windows ME
> I don't have an idea where to look at first).
>
> Thanks in advance,
>
> Martien
>
>
>
>
>

System halt after my program run

infoI make a program by LabVIEW 6i. The program function is that firstly it get data from OPC server by network, secondly to send command by RS-232. But the program do not run correctly. some information as follows:
1. computer: advantech industrial PC, CPU: P3-800(intel), memory:128M, HD:20G, display memory:4M(ATI), net crad: 3Com(3c905,10-100M)
2. system: windows NT4.0 workstation with SP4 (chinese), LabVIEW 6i
3. OPC: server: citect.opc (citect is automation & industrial software),
client: labVIEW.opc
4. some phenomena: when the program run after 4-5 hours or 10-12 hours, system halt and show that visual memory is shortage(visual memory of system is 160M).
I do not know why it is, need you help.
thanks
in advance.
Liu Weixing
2001/10/23
Attachments:
Opc.exe ‏608 KB

Two suggestion you might try:
1. Update your video monitor to the latest version.
2. Put a small delay (around 10 to 100 ms) in all your For and While Loops (including sub VIs). To create a delay, use the the 'Wait' sub VI in the Time & Dialog sub palette. This will force LabVIEW to pause momentarily and let Windows do other stuff....
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program

Hello!
We have the following problem:
LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program
We freshly installed LabView 8.2 (2006) and NI-DAQ 7.4.4 on a PC running Windows XP (Service Pack 3). We built a larger vi that remotely controls a traditional NI-DAQ card (AT-AO-10) on a second PC via NI-VISA 5.0.3. We were successfully running this program until a power failure caused the first computer to crash. After this crash we were unable to start the program again: LabView freezes while loading the vi. LabView itself can be started but freezes when adding I/O operations from the NI-DAQ palette to a block diagram.
We have tried to re-install NI-DAQ 7.4.4, but it did not help. We then re-installed all NI software, but still no improvement. In the end we decided to reinstall ALL software, first Windows XP, then LabView and finally NI-DAQ 7.4.4. This worked. However, after a few days of running the program we had to abort LabView via Windows Task manager and afterward we again experienced the same problem as before: LabView freezes when loading the program.
Obviously, we cannot afford to reinstall Windows every time. Are there any known Windows XP / NI-DAQ issues that might cause the freezing of LabView? We would be very grateful for any idea.
Best regards,
Matthias

Hello Sprice,
Browse the shipping examples according to “Directory Structure” and then select
DAQ to find the Traditional DAQ examples.
There a lot of examples that are written for counters (Counter >>
daq-stc.llb >> Count Edges (DAQ-STC).vi).
What kind of signals are your photons creating? Are they TTL compatible at a certain
frequency? You don’t care about overwriting
your buffer?
Respectfully,
Rob F
Test Engineer
Condition Measurements
National Instruments

Labview Program always crashs after a few hour' work

My Labview Program always crashs after a few hour' work. The error report is:
#Date: 2014年7月30日 4:27:27
#OSName: Windows 7 Ultimate
#OSVers: 6.1
#OSBuild: 7600
#AppName:
#Version: 12.0 32-bit
#AppKind: AppLib
#AppModDate: 07/29/2014 20:13 GMT
#LabVIEW Base Address: 0x30000000
<DEBUG_OUTPUT>
2014/7/30 8:34:11.006
DAbort 0xF50EFD7B:
c:\builds\penguin\labview\components\mgcore\trunk\12.0\source\MemoryManager.cpp(1104) : DAbort 0xF50EFD7B:
minidump id: 6ebe0400-78d2-41e3-b2fd-858c21e3567b
$Id: //labview/components/mgcore/trunk/12.0/source/MemoryManager.cpp#13 $
</DEBUG_OUTPUT>
0x30076B23 - lvrt <unknown> + 0
0x307D1F90 - lvrt <unknown> + 0
0x30605C66 - lvrt <unknown> + 0
0x6C42A045 - nivissvc <unknown> + 0
0x075A1F00 - nivision <unknown> + 0
0x03B0577A - <unknown> <unknown> + 0
0xE5BA0800 - <unknown> <unknown> + 0
Who knows what had happened? Thank you for your help.

Thank you for your reply.
I don't build array continuously. I just build a few queues. I am sorry the program is too large to show it to you. I have read the dump file. It seems like memory overflow. Do you think so? But it seems like there is no chance for memory overflow in Labview. The dump file is as below:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\LabVIEW Data\LVInternalReports\1.0.0.1\51437f73-aab6-4097-b7e1-3fee8a74e4dd\6ebe0400-78d2-41e3-b2fd-858c21e3567b.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Program Files (x86)\Symbols
Symbol search path is: C:\Program Files (x86)\Symbols
Executable search path is:
Windows 7 Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed Jul 30 08:34:10.000 2014 (UTC + 8:00)
System Uptime: not available
Process Uptime: 0 days 4:06:44.000
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(dfc.4b8): Unknown exception - code 00000002 (first/second chance not available)
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
*** WARNING: Unable to verify timestamp for kernel32.dll
*** ERROR: Module load completed but symbols could not be loaded for kernel32.dll
eax=13dbec20 ebx=13dbe550 ecx=00000008 edx=00000008 esi=00000003 edi=13dbe570
eip=77b564f4 esp=13dbe500 ebp=13dbe59c iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
ntdll+0x464f4:
77b564f4 c3 ret

HP4275A can not pass self test after running the labview program

I am using Labview to control HP4275A LCR meter. The Labview program is just the instrument driver for the HP4275A, and it works great. Before running the program, the instrument can pass both Open and Short test perfectly. But after running the program, it can not pass self test, neither Open nor Short. I don't know why?? Is it relative to my Labview program??
Thanks

Thank you so much for your help. Yes, the instrument is in Local after running the instrument driver. In normal Open self test, just choose Capactiance as the Display A, and leave the four output terminals open then press the Self Test button. The Open self test will start and "OP" will be shown in the DIsplay A window, after 2 seconds, the open test will be finished. If something abnormal, the number of the abnormal step is displayed in Display A. Similar with the Short test.
The problem I had was: before running the instrument driver, the self tests pass; but after running the instrument driver, the Open and Short test show abnormal, Open test is abnormal at step 17, and Short test is abnormal at step 24.
And the instrument driver is only write commands into the instrument and then read back measuring values from it. Nothing else. So I am not sure if the problem is my instrument driver.
The weird thing is the problems happened several times and then if I do the Open and Short self test again after running the instrument driver, both pass. I am not sure whether the problem will come back or not.
Ia there any help??
Big thanks

Error when running the LabVIEW program

hello...........
I'm newbie in LabVIEW....I have a problem when i'm running the LabVIEW program...i want to analyse data using the LabVIEW through the real experiment....
My problem is, there is an Error when i try to start the program...This Error forced me to restart the program several times until it can run.......By the way, i'm using Picoscopes 3206 to connect the LabVIEW program in PC with the real experiment.....
Here, I'm attached the picture that I snap when the Error occur....
Attachments:
error.JPG ‏222 KB

You have to try to isolate the problem...
Use 'Diagram disable' or 'Case' structure to run special part of code or try write a specific code to access and manage your equipment.
Several questions could help:
- Are you up to date with your hardware driver?
- Do you call external ressources (ex: dll)? perhaps with instability
- Do you properly close connection with your equipment after using?
- With your offline mode, do you load all the code, including hardware driver or do you use a special method without no loading the specific code?
- When you are able to run after many tries, is the program stable? Can you re-start it without exiting LabVIEW?

Modification of Global channels In NIMax while Labview Program running, not updating in Labview

Hello,
Okay, here is my issue. I have a program that reads data from a device using global channels in MAX.
Step 1: I open MAX with the systemExecute.vi with the parameters to wait till program finishes.
Step 2: I Modify a channel in Max, for example change the assigned daqMX Scale, or Min Max values.
Step 3: Save channel in Max.
Step 4: Exit MAX with the file exit.
Step 5: The Labview program continues, and I re-read the available global channels and global scales in the Labview vi but the properties have not changed to match what I change in MAX.
If I stop the VI then start it again and read the global channels then the properties get updated. How can I get the channel properties to update in Labview after changes are made in Max without stopping the labview vi and starting it again?

Many properties of the channel can only be modified when the task is not running. Have you tried stopping the task in LV before modifying the parameters, and then re-starting the task?
Dan

How do I make a labVIEW program for a linear CCD camera?

Hi, I'm pretty new at LabVIEW and I'm having a hard time figuring out how to connect my linear CCD image sensor (Toshiba TCD1304AP) with my computer. I know I need a DAQ device, what would work best for this particular CCD? After I got that connected, I need to create a LabVIEW program that displays the light detected by my CCD. Does anyone have a similar program or template I can use as a model? Any help would be appreciated. Thanks.

Hello,
I'm not sure the type of signal that is generated as an input to a DAQ device. This could either be an analog or digital input. The signal type will determine how you make your program in LabVIEW. You will also need to correlate the signal level to the light detected. That will be determined by your sensor. I don't have any programs or templates for this, but if you look at the basic analog or digital input examples, you might get a good starting point for DAQ device programming.
-Zach
Certified LabVIEW Developer

How to create a labview program and use it as a compiled prgram

I am a mechanical engineer, and I have some formulas and equations that I used to obtain maximum thickness of pipelines and also in the design of steel structures, what I need now is to use Labview to put these huge number of formulas in one program. I can do that, but the problem after I make the program I want it to be used by anybody on any PC which is not installed Labview on it, and that is the problem, I don't know if I can make an excel sheet or something to be the interface that can be used by the user, and if I can, I hope that I can have the details of who to execute that.

LabVIEW interacts with Microsoft Excel using its Active X hooks. Anything Microsoft has exposed in the Active X API, LabVIEW can do. This includes opening Excel, reading values, writing values, etc. Doing this can be tricky for a novice programmer and NI has created the Report Generation Toolkit for Microsoft Office that plugs into LabVIEW for a more streamlined experience.
The Developer Zone is a good place to start a search looking for Active X Excel examples: http://zone.ni.com/devzone/fn/p/sn/n16:en/sb/navsRel?q=microsoft+excel+labview&x=0&y=0
As well as the Forum: http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=2391
Reading and writing to an open Excel file could become quite cumbersome however. If the Excel file is open and the user is interacting with it, writing to that same file will return an error saying that the file is currently open. It would have to end up like this: User opens file, modifies some fields, saves file and closes excel. LabVIEW program opens file, reads fields and writes a result, then opens Excel to display to the user the result.
Is there any specific reason you want to use Excel as your user interface? You can use the front panel of a LabVIEW application to enter the data and display the results, all while writing this data to an Excel file for logging/reference in the future.
Message Edited by Stephen B on 11-17-2008 01:26 PM
Stephen B

Labview program to unistall and install new/updated software programatically

Hi,
I want to create a labview program to install and uninstall teststand deployment programatically.
Query : I have teststand deployment made and ready,wanted to deploy in 5 test PC's and for very first time it did work good. Now when I made updates in the modules, i made a new deployment with version increment. Now this time, i first uninstalled the previous deployment and reinstalled a new one. This time it took time to uninstall and install all 5 test PC's.
I wanted to automate this process through labview. I wanted to create a labview exe or installer which continusouly running on the client PC's looking for a perticular folder for new/updated deployment. If it finds, uninstall the older version if present and install a newer version of deployment.
I wanted to know what things i need to consider while making this type of labview program which uninstalls the older version and installs a newer one? I think i need to even reboot after uninstallation, before installing newer deployment. How make the program running even after reboot and continue the process?

I have the MS-6968 device and i want to use driver 1.4.x or 3.0.x. I found the driver 1.4.2.10 but i cannot find any WIDCOMMSecurity code.
So, can anyone give me a link for BTWPatcher.exe???
It cannot be found here (Jon's Bluetooth ) anymore.
Thanks

Labview Program will hang between 33% and 50% of the time.

I have a problem with a Labview program I made. I have two programs that do the same thing. One is in flat sequence form and the other is in state machine form.
As explained in the link below, I would like to make use of a microcontroller to make wiring connections for automating a measurement process. A separate current source and volt meter will be used.
https://forums.ni.com/t5/LabVIEW/Sequence-a-good-idea/td-p/2601333
I have since made some simple test programs which I have attached. The problem is when executing, the labview program will hang, but not every time the program is execute.
For example: Hall 1.2.vi will work properly twice with the third time it is executed it will hang. If you abort and try again, it will again run twice with no problems with the third hanging. This one is in flat sequence format (was in a flat sequence, but merged the windows because I thought that was the cause). From what I can tell, the program will hang when calling Keithley 6517 Single Read.vi. Both connected Keithley devices are connected to the computer via GPIB at 16 and 27. The way I verified if it was this vi causing it or contributing to it was that I removed it and the program never hung. I find it very strange that it will hang exactly on the third attempt every time.
Hall 1.3 simple.vi will work the first time and hang the second time. So it works 50% of the time. This one is in State Machine format. This one will hang at the case titled "Measure 1" which contains the Keithley 6517 Single Read.vi.
I've used the highlight execution button and watched the program run. Oddly, it doesn't hang when using this button. So I tried adding delays/wait in different places to no avail.
What could be causing this? As a side note, I say the program hangs for two reason. The main one is the program doesn't finish running so the run arrow is still black. The second thing is that if you notice at the end of the labview program, I have a block there that turns the current source off which doesn't happen when it hangs. I have to manually turn it off and then hit the abort program button to stop labview.
Solved!
Go to Solution.
Attachments:
Hall 1.2.vi ‏42 KB
Hall 1.3 simple.vi ‏81 KB

altenbach wrote:
SaintsFan wrote:
Also, I've tried placing wait/delays at various places with no improvement of the problem. My next thought is to just remove all the vi calls and have everything in one program.
How did you place the waits?
Why would placing everything in one program fix the problem. That makes no sense! What is your reasoning?
In the case of hall1.3, I placed a wait in the Measurement cases and CS On cases and there was no affect. In the hall 1.2 when the blocks were broken up similar to the state machine cases where each sequence window was identical to the cases, I placed a wait or delay in each window with no effect on the hanging.
My reasoning for placing everything in one program is the same as my reasoning for figuring delays would help, since the time of execution would be altered. If the execution time is faster and if the timing is the problem then I figured that the problem would happen more frequently or even every time.
Somehow I get the feeling this is not the case. The reason being the interval in which it succeeds or hangs is constant. I believe somewhere, a value is getting set. The 6517 Read vi runs fine if I run this vi by itself no matter how many or how fast I run it. Also, the same goes for both 1.2 and 1.3 if I remove the 6517 read vi they run fine no matter how fast or how many times I run them.
Somehow after the current source is set to operate and triggers labview will hang on a set interval when calling 6517 read vi.
Separately they work, together there is a problem. I tried placing a delay between these two by connecting the error out of the trigger vi to the error in of the delay block and the error out of the delay block to the error in terminal of the 6517 config block. I've also tried delays between other blocks connected the same way. From what I understand, a called vi can't execute until all inputs are present. Is this the correct way to wire the delays?

LabVIEW Program not running if i lock my PC (using an EXE made from LabVIEW)

Hi everyone
I observed some odd behavior when I was running my program on a PC. I prepared an EXE for a LabVIEW program, this am running on another PC. Purpose of the program is to read a text file and follow the command given in that text document, we are accessing parallel port, calling third party EXEs in this. It is not running when I minimize the window or lock the PC. Do we have any property in VI properties for this?
Please help me in this.
Thanks
Anil

Hi Anil,
Minimizing the application or locking Windows should not stop the executable from running. Can you reproduce this behavior on the development PC? Also try to create an executable with a simple VI that counts the number of iteration and check for this behavior ?
Tunde.

Labview program halts after 124 iterations

Similar Messages

Maybe you are looking for