03-13-2018 08:02 AM
Hi, we have got an issue with our data-logging program. It has been programmed in LV 2016 and LV2017 and have been running fine on several win7 machines, logging data from an enet-9163 with ni 9205 input module. This have not caused any problems so far (over a year).
But after upgrading to win10 we got some problems with full memory buffer in the enet unit and the working memory of the pc. This are resolving in a slugish pc that crashes after 1,5 to 2 weeks. (logging 16 single ended channels at 1 hz).
We made a change to flush the memory buffer in the enet unit every 5 min and write logged data to file.
The problem now is that the working memory of the pc that acts the same way with the same result.
Is there a way to fix this problem with the working memory? How to flush or release this?
Anyone seen the same behavior? Is this related to some new way of doing things in win10 or differences between win7 and win10?
sjeggefjes
Solved! Go to Solution.
03-14-2018
10:03 AM
- last edited on
04-27-2025
11:00 PM
by
Content Cleaner
Hello,
It sounds like a memory leak.
How do you monitor the memory on your PC/enet?
I found some articles which may give you a better idea of how to find the cause of the issue:
The enet-9163 stopped being produced in 2011 and supported on 2013. That is why not a lot of info can be found.
Looking forward to your answer.
Regards,
Razvan
11-22-2018 04:20 AM
The issue her is that the enet 9163 is no longer possible to use with win10 and the versions of labview/ max that we are using. We changed them with cdaq 9181 and cdaq 9185 and the problem disappeared.