LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI server application runs under debug mode but not other wise

I have an application which uses VI server to call vi's on my targets hard drive. When I run this using the highlight execution( or debug ) this works OK, however when I run without this I get error 66, connection closed by peer. When I look at my target using a direct monitor connection I get various messages relating to memory errors. I have run virtually the same code calling a simpler application and this seems to work fine, however when I simply target the RT engine with the same code ( using the RT comms wizard construction) I don't get a problem. This should, I think, be using the same amount of memory. What is the best was of assessing the memory available against the memory required? Do anyone have a
ny ideas as to why the VI should run with execution highlighted and not without. I have tried adding delays so simulate this but it doesn't seem to work.
0 Kudos
Message 1 of 2
(2,756 Views)
Check out this KnowledgeBase article. It describes how to enable a memory monitoring tool that might help solve your problem.
0 Kudos
Message 2 of 2
(2,756 Views)