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
I am trying to use a XBEE3 dongle loaded with Zigbee 3.0 firmware with xbee-android library and xbee-manager sample application. I am always getting receive timeout exception from the dongle while opening the connection. The USB serial interface connection using Android USB manager seems to be fine and there is no error while writing the packet. However, it seems I am not getting the response back in the expected format.
For example, while trying to determine the operating mode, it tries to get the value of "AP" parameter, the response for that is never received. The same thing happens with other parameters in readDeviceInfo().
I tried changing the operating mode using XCTU app on desktop as well. No success.
I also checked that my dongle FT232R is included in the list of supported devices.
I am not sure what is it I am missing here. Could anybody help?
The text was updated successfully, but these errors were encountered:
Hi,
I am trying to use a XBEE3 dongle loaded with Zigbee 3.0 firmware with xbee-android library and xbee-manager sample application. I am always getting receive timeout exception from the dongle while opening the connection. The USB serial interface connection using Android USB manager seems to be fine and there is no error while writing the packet. However, it seems I am not getting the response back in the expected format.
For example, while trying to determine the operating mode, it tries to get the value of "AP" parameter, the response for that is never received. The same thing happens with other parameters in readDeviceInfo().
I tried changing the operating mode using XCTU app on desktop as well. No success.
I also checked that my dongle FT232R is included in the list of supported devices.
I am not sure what is it I am missing here. Could anybody help?
The text was updated successfully, but these errors were encountered: