Benchtop Measurement and Test
Distributed Measurement and Control
Systems Engineering Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
If you get memory problems, you had to tune your reports options, result collecting, load / unload modules ....
These tasks are very long, you have to point all memory consumers first ... It pollutes your test sequence only for memory purposes !
When you try to modify the result reccording, you will also have problems for your report generation ...
It should be nice to add a new feature allowing an automatic result list removing, after onTheFly reporting, ontheFly database writing have treted them ...
A kind of "OnTheFly and remove unused results"
When ontheFly reporting, and The OnTheFly database writing are over, the treated resultList should be put in a garbage structure !
Older test results could be removed if memory is needed ...
I know this could be not simple ... but this could help very much, for big sequences creation.
Thanks a lot.
Manu.net (TestStand memory dustman !)
The "Discard Results or Disable Results when Not Required by Model" setting in model options sounds like what you are looking for. Have you tried using this setting?
You may also want to look at this document for info on conserving memory when logging:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you need our team of experts to assist you with?
We'll be in touch soon!