LabView is crashing

[oxsanj1]

Hello!

I am running Labview 2020 SP1

• I have made a data acquisition VI which reads voltage input from 2 load cells, 2 displacement transducers, and 8 pressure bridge sensors.
• I use cRIO-9045 with 9223, 9263, 2 nos. 9237, and 2 nos. 9234.  Currently the load cells and disp transducers connect to 9223, and the 8 pressure sensors to 9237 modules. 
• I want continuous and simultaneous measurements of all these sensors.
• My PC is Windows 10 64-bit based.  
• Tell us about your LabVIEW 2020 SP1 32 bit version 20.0.1
• My code is part of a "LabVIEW Project".  The code for the load cells and disp transducers worked fine until I expanded it by inserting an available vi for bridge sensors and editing it to have the same timing; the Labview crashes began.  
• I have sent the crash report/log and code to Ni each time but their website does not accept the code for some reason.
• I am attaching the latest crash report and the vi for your expert guidance please.

[Bob_Schor]

Your Block Diagram is 7 "screens" tall and 3 "screens" wide.  In order to look at (and begin to comprehend) this single VI without the Developer walking us through it is to have 21 monitors mounted in three "stacks" of 7 monitors (which would put quite a crimp in our necks.  Totally impractical.

Please refactor your code.  Look for "chunks" of Block Diagram that do "a function", make it a sub-VI (32 x 32 pixels in size), give it a clear Icon (if you don't want to use Graphics, use three lines of (short) text, like "Set up Fribble Input", put the Error Line on the lower corners, and try to use only 1-2 inputs and outputs.  Use Clusters, make every Cluster a TypeDef, hire a Developer to work with you and to help you design better LabVIEW code.

I was fortunate to get introduced to LabVIEW around the time Peter Blume published "The LabVIEW Style Book".  I already was pretty good at Text-based languages, but was unused to Graphical Programming, and certainly had no idea how crucial "Style" can be in LabVIEW programming, particularly with more complex programs.  I (very) rarely have a VI or sub-VI that doesn't fit on a single LabVIEW screen (an early "Style Guideline" from Peter's book.

Bob Schor

[oxsanj1]

Hi Bob

Thank you for your comments. Helpful indeed.  Were you able to look at the error log which I had attached. That might be more useful in determining why Labview is crashing.

Kind regards

[LVIEWPQ]

The easiest way to debug errors is through the VI.

Your VI is too large for anyone to want to spend the time looking at it to help you. 

If you clean up the VI in the way suggested, you will find more people are able to/willing to, help you determine where the crash is occurring. 

Until you bother cleaning up your VI, it is unlikely that anyone will be able to tell you what is causing the crash, even less so from the error log. 

[oxsanj1]

Thanks for the advice. Will attempt to make the vi more efficient.