ni.com is currently undergoing scheduled maintenance.
Some services may be unavailable at this time. Please contact us for help or try again later.
LabVIEW
the problem running
Is the application sluggish from the beginning, or does it get worse the longer the program runs.
If it happens right away, it could be that you are hogging all CPU, for example with a few loops that don't contain any wait statements. Also make sure to run under normal proirity. If you set the VI to time-critical, some system services might suffer, e.g. even simple mouse movements.
If it gets worse with time, it could be a memory allocation issue. Do your data arrays grow without limits (e.g. by using "build array" inside a loop with the array stored in shift registers (or even worse, local variables).
Feel free to attach your VI so we can have a critical look at it. ;).
If it happens right away, it could be that you are hogging all CPU, for example with a few loops that don't contain any wait statements. Also make sure to run under normal proirity. If you set the VI to time-critical, some system services might suffer, e.g. even simple mouse movements.
If it gets worse with time, it could be a memory allocation issue. Do your data arrays grow without limits (e.g. by using "build array" inside a loop with the array stored in shift registers (or even worse, local variables).
Feel free to attach your VI so we can have a critical look at it. ;).
I don't see any obvious problems so far. Could you also attach FCS-For.vi?
Have you tried to do some profiling?
Have you tried to do some profiling?
One thing you should definitely do is save FCS-For.VI under LabVIEW 7.1. It currently is still in LabVIEW version 6.1, while the rest of your program is 7.1. This means that this subVI gets converted every time you run your program.
It has been my experience that a freshly converted, but not yet saved(!), VI uses significantly more resources and runs slower until it is saved under the new version. You should also be more careful with data types, for example in this VI you have an array of U8 and XOR it with an I32 then display it as DBL. A better alternative is in the attached modification (LabVIEW 7.1) and keep it all as U8.
OK, now to a possible problem in the main VI: If the two case structure on the right are both false, the two refnums and error cluster are not wired through. This means that the two files opened during that loop iteration never get closed. You should definitely wire these across in every case (see arrows in picture)!
It has been my experience that a freshly converted, but not yet saved(!), VI uses significantly more resources and runs slower until it is saved under the new version. You should also be more careful with data types, for example in this VI you have an array of U8 and XOR it with an I32 then display it as DBL. A better alternative is in the attached modification (LabVIEW 7.1) and keep it all as U8.
OK, now to a possible problem in the main VI: If the two case structure on the right are both false, the two refnums and error cluster are not wired through. This means that the two files opened during that loop iteration never get closed. You should definitely wire these across in every case (see arrows in picture)!
Message Edited by altenbach on 05-25-2005 10:46 PM
