LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Help, open my vi, I can't do it anymore

Solved!
Go to solution

Hi all,

 

I'm a stupid boy....

 

I've increased the history length of my graph up to 4 10^9, and I can't now open my vi anymore (not enough memory on my computer, strange no ?... ).

 

I'm looking for someone who can open it and change the history length of my graph to 1024.

 

And no, I haven't made any backup of my vi... I know, I'm stupid.....

 

Thanks in advance !

 

David.

0 Kudos
Message 1 of 7
(3,166 Views)

Hi David,

 

"Im a stupid boy" - YES!

"I haven't made any backup of my vi... I know, I'm stupid..." - YES! YES! YES! Smiley Wink

 

Ok, a history of 4×10^9 ~= 4Giga requires atleast 4GB of RAM (for byte values, or 16GB for SGL or 32GB for DBL). I don't think someone here has a LV version capable to support such RAM allocations - I'm happy when I get 1.3GB RAM allocated on a 2GB machine.

 

So you better start to recode that vi. And do backups this time!

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 7
(3,156 Views)

It doesn't open on my machine - it just crashes LabVIEW. But I don't understand. The vi is only just over 100K?

=====================
LabVIEW 2012


0 Kudos
Message 3 of 7
(2,692 Views)

Hi Steve,

 

the history size of a chart is set to a huge number.

When you open that VI LabVIEW tries to allocate sufficient RAM for the chart history - and simply fails...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 7
(2,684 Views)

Thanks.

 

David, maybe someone in NI support who knows the internals of LabVIEW code could edit it with some kind of tool to reset the size. It is only a guess but you might want to ask.

=====================
LabVIEW 2012


0 Kudos
Message 5 of 7
(2,673 Views)

Hi Steve,

 

you see the thread is now 1.5 years old. I think he already created a new version of the VI...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 7
(2,668 Views)
Solution
Accepted by David_49

For information, I've recode my vi. I didn't find any solution, even with a powerfull computer...

0 Kudos
Message 7 of 7
(2,667 Views)