LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-845x I2C Create Configuration Reference.vi and NI-845x Close Reference.vi

When the NI-845x I2C Create Configuration Reference vi is connected to a NI-845x Close Reference vi. and the application is placed into the continuous run mode the application continues to use system memory.    The SPI create config reference and close reference do the same thing.  Why doesn't the Close Reference vi release the system memory that the create configuration allocated.  If this application is allowed to run it will consume all of the system memory and the system will crash.  How can I get this issue resolved.  Since each of these is used in a sub vi that is called repeatedly from the main vi I cannot seperate the Create coinfigure vi and only place it in the main vi so that it is only called once when the main vi  executes.  The vi that I am trying to run continuously is attached.  Run the vi continuously and watch the system memory being used by watching the memory usage with windows task manager.  The system memory usage will continually increase as the vi runs.  I am using other read and write I2C functions but I have isolated the problem to the I2C Create Configuration Reference ans SPI Create Configuration VIs.

0 Kudos
Message 1 of 3
(3,208 Views)
Howdy Stan,

Please excuse the relatively slow reply. I2C/SPI issues usually post to the CAN & DeviceNet forum, which is why it stayed in limbo a bit.

I just wanted to let you know that I confirmed, using the machine here near my desk, the same behavior you experience/describe. I've subsequently filed Corrective Action Request ID# 110899 to further investigate the issue.

We thank you for this excellent feedback and apologize for any inconvenience this has caused.
Warm regards,

pBerg
0 Kudos
Message 2 of 3
(3,168 Views)

Hi Stan,

Thanks for letting us know about this problem. We fixed it already and the fix is included in the new release for NI-845x 1.1.2 scheduled for July 2008.

If you need a patch before the release date, please reply to this E-Mail: canpse@ni.com .

Please provide your name, company name, so I can track the patch distribution.

DirkW

0 Kudos
Message 3 of 3
(3,155 Views)