01-18-2016 03:58 AM - edited 01-18-2016 04:18 AM
Dear colleagues,
If it happens "white screen" on long-running LV's application - what is to be done to avoid it in future?
Note that after "white screen" (approx after 1 week from start application) - no happens any events or log in Windows 7.
It is interesting that in the LV2009 this behavior was not registered.
To isolate the problem I need to do to program your own log file and write in it all the actions in my program or may be rollback to LV2009 ?
Program is designed for 24/7 operation (well at least a month of continuous operation).
My system is Windows 7 SP1 on Advantix ER-7000 (Intel, 4 GB RAM), LV2014f1, PXI-1033 with 3 cards NI-6511, NI-6515 and Pixie4 (third-party manufacturer). Program consists form one top-level VI and 100 vi (in project tree) and 5 lvlib with local variables. Also are "calls library function" for simple read/write from Pixie4 and also are simple actions read/write with NI-6511, NI-6515 cards. Note that I don't used different threads (Preferred Execution System) now all works in one "same as caller".
Please any help is appreciated. I know about full code optimization and now I'm thinking about it.
01-18-2016 04:49 AM
01-18-2016 07:47 AM
I am also curious about what a "white screen" is. In addition to the questions that BLOKK asked, what is the CPU usage doing? I have seen a few cases where a program used so much CPU that it wasn't left with enough time to update the GUI properly.
Yes, we need to see the code.
Mike...
01-18-2016 10:00 PM
2.You could try to remove all unrelated parts step by step, and see if a minimalized code can reproduce the bug?
No, I am very far away in space from the system.
3. What do you mean about "white screen"? Win7 frozen? Do you need to hard reset PC, or you can kill the LV task from task manager (ctrl+alt+del)?
Win7 - lives on, but LV task is terminated from task manager (ctrl+alt+del).
4. After a few days, do you see increasing RAM usage?
No - RAM growth is absent, but I checked it only when my project work under LV2009.
01-18-2016 11:57 PM - edited 01-19-2016 12:00 AM
It is useful to have your MAIN VI at the top level of the project tree. I have only found a configuration vi (Pixie4SetUserPar.vi) there, can you tell us which VI do you run for days?
edit:
"4. After a few days, do you see increasing RAM usage?
No - RAM growth is absent, but I checked it only when my project work under LV2009."
Maybe then it would make sense to check your RAM when you run your project under LV2014? 🙂
(it is unlikely, but there might be difference between LV2009 and 2014 in reference and memory handling?)
01-19-2016 12:28 AM
I have only found a configuration vi (Pixie4SetUserPar.vi) there, can you tell us which VI do you run for days?
May be I did not quite understand your question, but this VI is intended only for hardware setup for Pixie4 and no use for buld exe file.
I discovered that may application do 25% CPU loading. Oh! Very interesting!
01-19-2016 12:53 AM - edited 01-19-2016 01:11 AM
No, you did not understand my question 🙂 So what is your main VI? I cannot check it in your build spec, since I am at home, and the LabVIEW Home edition does not have this feature.
Did you code this project yourself?
edit: I have found a VI called "Form_Main.vi". Is this the top level VI? I had a look at the block diagram. Massive use of flat sequence structures, global variables and a spagetti code. Sorry, this is beyond my skills to debug.
01-19-2016 02:04 AM
No, you did not understand my question So what is your main VI? I cannot check it in your build spec, since I am at home, and the LabVIEW Home edition does not have this feature. Did you code this project yourself?
edit: I have found a VI called "Form_Main.vi". Is this the top level VI? I had a look at the block diagram. Massive use of flat sequence structures, global variables and a spagetti code. Sorry, this is beyond my skills to debug.
"main VI" it is "Form_Main.vi" (it is the "Top-level VI" at the same time). Thank you. I wrote it all by myself as best I could. I agree with you that code needs to be improved. I'm working
01-19-2016 07:11 AM
01-19-2016 07:13 AM
the code was attached in a previous post:
http://forums.ni.com/ni/attachments/ni/170/943364/1/AR31_Oper.zip