05-12-2025 07:55 AM
Hi All,
I'm hoping that one of you kind experts could spare a little time to take a look at a simple FlexLogger plugin that I created (based on one of the templates).
The issue I'm having is that when FlexLogger is running with this plugin, the memory usage (of the FlexLogger process) slowly increases over a few days. It was once left for about a week and the PC crashed.
Context:
- The FlexLogger plugin reads a channel of 'Revolutions' and increments a 'Cycle Count' when the Revolutions reaches a target value and then goes back near zero. (Each cycle takes about a minute, so we're not looking at counting large numbers here).
- We record in FlexLogger at 250Hz, and the test (ideally) runs continuously for a few months (with FlexLogger configured to split tdms files in 512Mb chunks).
- I'm a beginner at LabView, so I wouldn't be surprised if I'm doing something like appending values to a variable every time Process.vi is run.
Would really appreciate any help you can provide. Let me know if you'd like any more details.
09-25-2025 08:09 AM
I was wondering if you managed to fix this issue. I am using Flexlogger to monitor 16 channels as 10Hz and 2 channels at 1Hz and I am now finding that 3 days into the test the Flexlogger is not responding and has grabbed 98% of the memory. I have no Idea why.
10-06-2025 05:06 AM
Hi Hansolo, unfortunately not. NI support didn't provide much help either.
We're planning on updating our FlexLogger & plugin dev kit versions, and hoping that will fix this. Good luck with yours!