05-09-2014 08:25 AM
I have written a VI to acquire analogue data from Measurement Computing USB_1616HS using their Universal Library ULx VIs.
The main VI (attached) has:
I usually get a message "Not enough memory to complete this operation" quite soon after starting the data acquisition. The array sizes are all quite small eg 1000*3 - I don't think it is an array allocation problem. Windows Task manager shows Labview using 200 Mb (Windows 8, 64 bit, 16 Gb memory).
My guess is that it is something to do with the property nodes and the number of controls on the VI but without pinning it down, it's hard to know how to fix it. Any advice?
Thanks
Roger
05-09-2014 08:45 AM
It could be some function (e.g. the USB) throwing error 2, which LV thinks is out of memory. This is a perfect case for Highlight execution mode and Retain values; Light the two light bulbs on the toolbar and see what happens. I cant look at the code right now, but i assume you have connected stuff with the error wires?
/Y
05-09-2014 12:11 PM
Thanks for the suggestion.
I've tried putting a simple error handler immediately after the ULx Read VI but it shows no error.
The Error message that pops up does not pause execution, so one cannot tell from where it comes!
Roger
05-13-2014 07:46 AM
Hi Roger,
Following what Yamaeda said, you could still possibly find the point where the error occurs using highlight execution.
Even though the error doesnt stop your execution, highlight execution should slow down your application to the point your should be able to tell what part of the code is executing when the error pops up.
If you could post back letting us know the result of this investigation, that would much appreciated.
Kind regards,
05-13-2014 11:33 AM
Hi Matt,
It seems to give the message when it sets the plot names for the waveform chart - see attached screenshots. Hope this helps!
Thanks
Roger
05-13-2014 11:48 AM
See if this message thread could apply to you.
05-15-2014 07:16 AM
Hi Matt & RavensFan
Yes, it seems a similar problem. I would like to think though (since it was a "known problem" in September 2011) that it has now been fixed - the thread does not say if it has or not.
I wondered whether it was in any way due to the actual data acquisition VI library so I wrote dummy versions of the ULx VIs that just generate random numbers. The message still occurs.
I have tried to attach a zip file but I get a message "The contents of the attachment do not match its file type" so instead I have shared the file in my LabView folder on dropbox - the link is:
https://www.dropbox.com/sh/9oqfoqsrcdgpp3l/AADFpNSfRMZEbcEO2TDJybqHa
Unzip "RWM code for debugging.zip" and run RWM_LAB front panel dummy DAQ.vi
(you don't need the data acquisition hardware since the code now generates random numbers instead). Click on a few of the channel ON buttons, then "Start capture".
I'm still very much a novice at LabView so if my code seems truly, deeply horrible - by all means say so!
Thanks
Roger
05-16-2014 09:03 AM
Hi Matt,
I've put code to demonstrate the error on dropbox:
https://www.dropbox.com/sh/9oqfoqsrcdgpp3l/AADFpNSfRMZEbcEO2TDJybqHa
(see following post). Unzip "RWM code for debugging.zip" and run RWM_LAB front panel dummy DAQ.vi - hope it works for you!
Kind regards
Roger
05-19-2014 04:25 AM
Hi Roger,
I don't seem to be immedietly able to recreate that error. Upon running the program, I enable to first 5 channels, and start a capture. I leave this going for about 10 seconds. stop the capture, and start it up again. If I leave that running, I don't appear to get any error. - Am I doing this right for recreation?
Could you also clarify what version of LabVIEW you are using, and whether or not you are able to try this on another machine?
Kind regards,
05-19-2014 05:40 AM
Is there a limitation to what characters can be used in a plot name?
/Y