From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-26-2017 01:44 PM
Hi Everyone!
Am a newbie to LabView.
I have developed a recursive program that keeps running until its stopped. I have connected the test setup to my PC where I do other stuffs as well.
So what I do is, click RUN in the LabView window, program starts running and I keep doing other works. I check whether the program is running without any errors once in a while. But sometimes I forget to check and it happens to show pop-ups explaining some error has occurred and can it STOP or CONTINUE.
Since the whole program is on the background, am not able to track when the error actually occurred.
Is there a way to show pop-up if any errors have occurred in the background LabView program that is running while doing other stuffs in the PC?
Thanks!
Solved! Go to Solution.
10-26-2017 02:15 PM
10-26-2017 03:04 PM
Hi GerdW,
Thanks for your reply.
Yes I know that I should do some error handling but its not a consistent error. Am doing lots of I2C reads and file write each second but most of the time everything looks good.
how do I know if the VI is running or halted without visiting it?
Thanks!
10-26-2017 10:54 PM
You could try using the Debugging Window. Call it using this:
Any string you input will write to the debugging window which pops-up on first call. It looks like this:
Chief LabVIEW Architect, Testeract | Owner, Q Software Innovations, LLC (QSI)
Director, GCentral | Admin, LabVIEW Wiki | Creator, The QControl Toolkit
Certified LabVIEW Architect | LabVIEW Champion | NI Alliance Partner
10-27-2017 01:48 AM - edited 10-27-2017 01:50 AM
Hi TSBSR,
but its not a consistent error. … but most of the time everything looks good.
So because the error is not popping up with each iteration of your loop you can dismiss any error handling? Fail!
Especially when such errors only occur once in a while you want to know the (possible) reasons with some additional information!
how do I know if the VI is running or halted without visiting it?
Implement some error handling so your VI will never "halt"…
Btw. Q's debug window function only works in the IDE, in an executable the debug window will not open… (Atleast it did so when I tested it with LV2011.)
11-02-2017 06:00 PM
Thanks GerdW for your inputs!
I did code review and found 2 bugs. Solved it and now my setup is alive for 2 days in a stretch.
11-02-2017 06:01 PM
Thanks Q for your inputs but I wasnt able to try it out