LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error -301711

I am having a problem involving "configuration references property nodes". Using Labview 8.0, Windows 2000 and using an NI 8451 USB to I2C device.  I run a test routine many times but on the ~30th time I get an Error #  -301711 that says "There are no more resources available to create a new configuration reference. Reuse an existing configuration reference or close an unused configuration reference."  I've tried opening and closing the configuration reference property node both in the test loop and outside it using 'tunnels'. It seems like Labview is 'counting' the number of times I loop on this routine and counts each NI 8451 I2C 'open' or its 'configuration reference property node' and has a limit on the number of times I can use this property node. Has anyone else experienced this problem? Thanks.
0 Kudos
Message 1 of 21
(4,846 Views)
lec,

It sounds like you are not closing your references through each iteration, but you are opening a new reference.  Would you be able to post your VI so I can take a closer look at exactly what is happening?
Regards,

Jared Boothe
Staff Hardware Engineer
National Instruments
Message 2 of 21
(4,813 Views)

Jason,

Thanks for getting back to me. It does look like its not being closed. But I've been careful to always close the routine. Is it possible the canned Labview 'close' routine isn't working correctly for the NI3856  USB to I2C adapter? Have you ever heard of this Error #  -301711?

Thanks.

Larry

0 Kudos
Message 3 of 21
(4,801 Views)
I'm sorry the NI 8451 USB to I2C adapter.
0 Kudos
Message 4 of 21
(4,799 Views)

Can you post your code? 

RayR

Message 5 of 21
(4,797 Views)
Hi Larry,

Not sure what you mean with "the canned Labview 'close' routine". Some LabVIEW APIs (NI-DAQmx?) allow you to omit closing references and handles. Whenever the VI is closed (unloaded from memory) LabVIEW automatically closes those references. This is not the case for the NI-845x API. If you leave enough references/handles open, you will run into this type of problem.

Please go ahead and post your code, maybe there's something else wrong that causes this error.

-B2k
Message 6 of 21
(4,786 Views)

B2k, Jason,

As always, thanks for your continued support.

Here's the latest: I wrote a vi that simply opened an NI 845x USB to I2C reference, wrote to it and closed the reference. I loop on this using the 'continuous loop' button on the top toolbar near the 'start' and 'stop' buttons and it goes well. No failure or Error message #  -301711. I then expand the loop inside a Case structure that does some actions (unrelated to NI845x) and then this same "open, write, close" reference vi above. The loop consists of using 'next state' constants that point back to the previous Case but not using the 'continous loop' button. Looping on this expanded routine and it fails after 40-50 loops with the -301711 error code that it is "out of resourses". It seems that when using an expanded loop where the program goes in and out of a Case structure it checks and counts when resources are used and I run into a limit. But it doesn't count resourses when just using the 'continuous loop' button.  Any ideas?

0 Kudos
Message 7 of 21
(4,726 Views)
showme,

Again if you could post your code it would make things more clear.  I am assuming you do not have a while loop to keep your program going, and this is why you are using the "continuously run" method.  Would you be able to attach your VI for me to take a look at?
Regards,

Jared Boothe
Staff Hardware Engineer
National Instruments
Message 8 of 21
(4,711 Views)
Jared,
 
Attached is the code. As I said if I put it in a loop using the 'continous loop' button it does not fail. But when I loop it inside a Case structure using the 'next case' pointers it runs ~ 40-50 times and fails with the Error -301711.  I'd say the NI 845x Close routine is not working but it seems OK with the 'continous loop button. Any ideas?
Thanks again for your help.
 
Larry
0 Kudos
Message 9 of 21
(4,698 Views)
Larry,

Would you be able to provide the file that fails with the error?  The file with the case structure (for example) would be good.  It don't see anything wrong at a glance with this code, and was also able to run it without any failures over several iterations (60+). 

I am not exactly sure how you modified the code when it wasn't working.  If you could provide that file that'd be best.
Regards,

Jared Boothe
Staff Hardware Engineer
National Instruments
Message 10 of 21
(4,682 Views)