LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Front Panel VI now crashes Immediately: Development Environment

Solved!
Go to solution

I have been working on this project on and off for a customer for 2 years. Yesterday, I was changing the analog signal from to a 9207 card from voltage to current. The change was successful, and I built a new executable for the customer. 

 

I then realized that calibrating the loadcell (modifying offset and gain) programmatically had to also be changed. I changed the code around reading and writing from network variables, and ran the VI. I then toggled a GV I had to show a calibration mode on the front panel (basically turning on/off visibility property nodes.) It didn't do what I wanted, so I went back to trying more code. 

 

Next time I tested, the Front Panel VI crashed immediately when ran. It will also stop the program running on the RT Target. This is the first time I have experienced any crashing with this project, executable or development mode. The executable I made before I attempted to change the calibration runs fine. But in development mode, the Front panel will crash immediately.

 

Here is what I've tried: 

Clean compile of the project 

Commenting out all of the network communication

Turning on the watch lightbulb to see what part of code is crashing (appears to not even do initialization routine.) 

Commenting out property nodes activated by calibration variable. 

 

I've looked on the forums about crashing, and it appears most people get more information from LabVIEW when their projects crash. Mine gives me: 

Exception: Unknown (0x00000000) at EIP=0x0263943B 

 

Hardware: a CompactRIO

Software: LabVIEW 2017 Robotics (32 bit) runs on a Windows 10, 64 bit machine. 

 

Thank you for the help!

0 Kudos
Message 1 of 4
(1,427 Views)
Solution
Accepted by topic author ace.bot

Could just be a corrupt VI.  Happens from time to time.

 

When that happens, one thing that can be an easy fix is to just create a new VI and copy-paste all of the code from your old VI to your new one.

 

Or if you have backups or other forms of source control, load up the last known good version and add in all the changes again manually and see if it develops the same issue again.

Message 2 of 4
(1,416 Views)

I've tried to copy paste to no avail. I do have backups, but not that recent. Hopefully I didn't alter too much since then.  Lesson learned on being more diligent with source control. 

0 Kudos
Message 3 of 4
(1,411 Views)

Ended up saving as a new project, deleting some of the variables, I had created in the last revision. Had it back and running in 30 minutes. Thanks for the help.  

Message 4 of 4
(1,324 Views)