You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2019. It is now read-only.
I'm using the 900MHz XBee digimesh radio and sometimes I'm seeing issues where either right at startup of my application or sometimes after heavy usage of the radio it becomes unresponsive.
When I get to xbee_setup(...) the libxbee3 library prints out flock(): Resource temporarily unavailable and returns error code -19 which prints with xbee_errorToStr(...): A the item requested is currently in use.
I have no other instances of applications on the system running and in some cases everything is fine until after a few minutes of heavy radio usage, then it seems to loose its session with the radio and when it tries to reconfigure, gets these errors. Other times these errors happen right at startup of the application.
Has anyone else experienced this type of issue and know what the resolution is?
The only thing I've found that works is to restart my application and wait. However, this is not a good solution as I run this on remote mobile sensor nodes and I can't manually restart the application if my only communication link to the node has gone down.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using the 900MHz XBee digimesh radio and sometimes I'm seeing issues where either right at startup of my application or sometimes after heavy usage of the radio it becomes unresponsive.
When I get to
xbee_setup(...)
the libxbee3 library prints outflock(): Resource temporarily unavailable
and returns error code-19
which prints withxbee_errorToStr(...)
:A the item requested is currently in use
.I have no other instances of applications on the system running and in some cases everything is fine until after a few minutes of heavy radio usage, then it seems to loose its session with the radio and when it tries to reconfigure, gets these errors. Other times these errors happen right at startup of the application.
Has anyone else experienced this type of issue and know what the resolution is?
The only thing I've found that works is to restart my application and wait. However, this is not a good solution as I run this on remote mobile sensor nodes and I can't manually restart the application if my only communication link to the node has gone down.
The text was updated successfully, but these errors were encountered: