10-01-2007 02:29 AM
10-01-2007 11:36 PM
10-02-2007 07:24 AM
10-03-2007 02:56 PM
10-04-2007 01:15 AM
10-04-2007 02:25 AM
10-04-2007 08:50 AM
In addition to the note above we have avoided this issue because of the nature of our applications.
Since our apps don't know the targets we will interact with, we avoid using the Shared Variables and rely on traditional methods (TCP/IP, Datasockets, etc.) to share data. I have not seen slow edits in app's that don't use the Shared Variables. This is just my personal observation.
Trying to help,
Ben
10-05-2007 04:38 AM
10-06-2007 04:13 PM
You've hijacked the thread by posting a question into a thread that has nothing to do with what you are asking. Please repost you questions in a new message thread.
@120341 wrote:
HiWhere can I get the lab view program for IQS 12004B lab view program?
11-21-2007 11:01 AM
In my experience with main vi's > 700kb in LabVIEW 8.2 and 8.5 on a 1.3 GHz Pentium 4 with 2 Gb RAM, editing speed is reasonable - about a second to add/delete objects and wires. Then I recently experienced a sudden, severe slowdown with one such vi. The same edit operations that used to take one second now consistently took 15 seconds. The aforementioned suggestions in this thread for correcting the problem were ineffective or irrelevant for my situation with one exception. I believe my problem is similar to one where a developer fixed his problem by replacing a particular control (an enum in his case). I was able to trace my problem to (defective?) property nodes for two graph controls using this troubleshooting procedure:
1. Delete front panel controls one-at-a-time until editing speed is restored on the block diagram. Note which control you deleted just before speed was restored.
2. Reload the vi and delete just the troublesome control. Check editing speed.
3. If editing is still slow, continue deleting controls one-at-a-time from the set of controls deleted originally until editing speed is restored and the second problematic control has been identified.
4. Proceed in a similar manner to identify additional problematic controls if necessary.
In my case, I next reloaded the vi, and deleted just the property nodes of the two troublesome controls. Speed was restored once the last property node was deleted. The problem returned once I began recreating property nodes (once the 2nd node was created), however, so the final solution was to recreate the controls AND the property nodes.
Larry