error -301711

[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.

[Ray.R]

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

[Ray.R]

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

[lec]

Jared,

Do you know any solution that I can try to fix the I2C open / write / close problem I'm experiencing? Should I call my local NI Rep? It seems that the Discussion Forum is the best shot but I can't seem to find any other solutions.

Thanks.

Larry 

[Ray.R]

Are you able to post your code?

R

[Jared_B]

Could you post the code in which the VI works properly as well as the option that it doesn't.  It seems like you have the subVI but not the calling VI posted previously.

[R_J]

Hi All,

Sorry to post my question in between. I was not able to post my query.

I am using NI USB 8451 SPI card. Sometimes i am getting errors with error code

-301709

-301706

-301708.

I am not getting these errors always. i am only getting these errors when i am executing the code in a loop.

Kindly tell me how to solve these error issues.

Regards,

J