error -301711

[lec]

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.

[Jared_B]

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?

[showme]

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

[biker2000]

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

[showme]

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?

[Jared_B]

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?

[showme]

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


I2C Write data to ASIC 062408.vi:
http://forums.ni.com/attachments/ni/170/335011/1/I2C Write data to ASIC 062408.vi

[Jared_B]

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.

[lec]

Jared, Sorry about the slow response. Been pulled onto other projects. Can we attack this thing from another direction? Is there a list of error codes? What is Error Code -301711? It must be defined somewhere. This definition could be a big clue. Also, it could be related to the NI 8451 USB to I2C device. The USB architecture may be counting some number of times it is opened / closed, etc...The bottom line is that it looks like the I2C open / write / close is not closing... but the same code works is a small loop. The code only gives an error when it goes out into another case structure and back into the I2C open / write / close case. Some 'resource' is being counted by the 'higher' level LabView software. If we can find out what Error Code -301711 is it might give us a clue.Again, thanks for your support.

[JoeLabView]

Error Code -301711:
There are no more resources available to create a new configuration reference. Reuse an existing configuration reference or close an unused configuration reference.
 
Above is the definition that I found.
R

[lec]

Thank you, R. Yes, that is the phrase I get when the error occurs. What I'm looking for is the reason this error is flagged. Somewhere in the LabView software its counting a 'resource' and its hitting some 'limit. If I can find out what the 'resource' is and what the 'limit' is, maybe I could reset the count or increase the limit. When I restart the program, its reseting the count because I then loop 30-50 times before I get the fail again with the phrase you posted. Any ideas?Thanks again for the support.LEC

[showme]

Jared, Ray R, B2K,
Does anyone know about this problem? Are there any paths / ideas I can try to solve this problem? Please, this is a very important problem I need to solve / work around.
Thank you.
LEC

[JoeLabView]

It is a generic error message.  To find out what causes (might cause?) the error message within a certain code, we would have to see the code.
Can you post your code?  Simply attach it to your reply.
 
R

[showme]

R,
Thanks for responding.
I had already posted the code awhile ago. I'm not sure about a 'generic' error though. Error -301711 sounds pretty specific to me.
I'm pretty sure the problem / solution is in the LabView software specifically in the I2C open / write / close VIs. I see it as one of 2 things:
1) The LabView software is keeping track of a 'resource' (Probably how many times I 'open' the I2C vi) and even though I 'close' the I2C vi it doesn't actually close it. or
2) If we can adjust the number of times this 'resource' is used so I won't hit the 'limit'
Do you know anyone who knows the higher level LabView software that could find where this 'resource' counter is or where the 'limit' number is located?
Thanks again for your support.
LEC

[showme]

I'm sorry the NI 8451 USB to I2C adapter.

[JoeLabView]

Can you post your code? 
RayR