Troubleshooting

XCTU requires Administrator permissions. Check that you have Administrator access on the machine where you are installing XCTU. You may need to request permission to install or run applications as administrator from your network manager.

On Windows systems, a User Account Control dialog may appear when you install XCTU or try to run the XCTU program. You must answer yes when prompted to allow the program to make changes to your computer, or XCTU will not work properly.

Try the following troubleshooting methods:

• Check cables: Double check all cables. Make sure the USB cable is firmly and fully attached to both the computer and the XBee Grove Development Board. When attached properly, the association LED on the adapter is lit.

• Check that the XBee is fully seated in the XBee Grove Development Board: When the XBee module is properly installed, it should be pushed fully into the board and no air or metal should be visible between the plastic of the adapter socket and the XBee headers. Also, double check that all ten pins on each side of the XBee module made it into a matching hole in the socket.

• Check the XBee orientation: The angled "nose" of the XBee should match the lines on the silk screening of the board and point away from the USB socket on the XBee Grove Development Board.
• Check driver installation: Drivers are installed the first time the XBee Grove Development Board is plugged in. If this process is not complete or has failed, try the following steps:

  • Remove and re-insert the board into your computer. This may cause driver installation to re-occur.

  • Remove and re-insert the board into another USB port.

  • (Windows) Open Computer management, find the failing device in the Device Manager section and remove it.

  • You can download drivers for all major operating systems from FTDI for manual installation.

• Check whether the modules are sleeping: The On/Sleep LED of the XBee Grove Development Board indicates if the module is awake (LED on) or asleep (LED off). When a module is sleeping, it cannot be discovered in XCTU. Press the Commissioning button to wake a module for 30 seconds.

This is a known issue with XCTU version 6.1.2 and earlier. When the Invalid settings dialog appears, it is safe to continue writing settings.

• AES Encryption Key (KY) is a setting that must be set by the user when encryption is in use and does not apply with factory settings.
• Device Type Identifier (DD) is a diagnostic parameter which is not used in the operation of the radio and can safely be set to any value.

Check the Associate LED of ROUTER and END_DEVICE. If it is not blinking, it means that the module is not joined to the network yet. Wait a few seconds and try again.

If the module that is not found is END_DEVICE, it may be asleep. Press the Commissioning button of the board where it is plugged in to wake it up and try again.

END_DEVICE is configured to cyclically sleep for five seconds and be awake for five seconds. It may have been asleep when you typed in its console, so press the Commissioning button of the XBee Grove Development Board where it is plugged in to wake it up and try again.

To identify the END_DEVICE module, look for the board where the On/Sleep LED is ON for five seconds and OFF for another five seconds.

This usually occurs when the end device is asleep. Press the Commissioning button of the board where it is attached to wake it up and launch the application again.

To identify the END_DEVICE module, look for the board where the On/Sleep LED is ON for 5 seconds and OFF for another 5 seconds.

If you see the "Error parsing the text..." error when sending a message, this indicates that you typed the message incorrectly. Remember to follow this pattern when sending a message:

• Unicast: NODE_IDENTIFIER: message

  For example, to send the message "Hi XBee" to XBEE_C:

  XBEE_C: Hi XBee

• Broadcast: ALL: message

  For example, to send the message "Hi XBees" to all nodes in the network:

  ALL: Hi XBees

This message indicates that the module attached to your computer could not send the message to the device whose node identifier is <XXXX>.

Ensure that you typed the node identifier correctly and that it is in the list of devices found by the application. If it is not there, launch the application again.

This happens when the end device is asleep. Wait until it wakes up or press the Commissioning button and send the message again.

To identify the END_DEVICE module, look for the board where the On/Sleep LED is ON for 5 seconds and OFF for another 5 seconds.

When the end device is asleep, it cannot receive any message. Its parent stores the message until it wakes up.

Ensure that the module is joined to the network. To verify this, check that the Associate LED of ED_PIN is blinking when the DTR button is activated. If not, reset the module and wait a few seconds.

If you launch an application and see the message "WARNING: RXTX version mismatch", this indicates that the versions of the JAR file and the native library are not the same. You can safely ignore this message.

If you launch an application and you see the "com.digi.xbee.api.exceptions.InvalidOperatingMode" exception, review the following solutions.

• Could not determine operating mode:

com.digi.xbee.api.exceptions.InvalidOperatingModeException: Could not determine operating mode.
	at com.digi.xbee.api.XBeeDevice.open(XBeeDevice.java:211)
	at com.digi.xbee.sendreceivedatasample,MainApp.main(MainApp.java:43)

In this case, the library cannot access the module. Check that the PORT constant is correct.

• Unsupported operating mode:

com.digi.xbee.api.exceptions.InvalidOperatingModeException: Unsupported operating mode: AT mode
	at com.digi.xbee.api.XBeeDevice.open(XBeeDevice.java:214)
	at com.digi.xbee.sendreceivedatasample.MainApp.main(MainApp.java:43)

This indicates the module is in transparent mode. Change the AP parameter through XCTU to be API enabled [1].

If you experience the "java.lang.UnsatisfiedLinkError" exception, there are several possibilities.

• "no rxtxSerial in java.library.path thrown while loading gnu.io.RXTXCommDriver":

java.lang.UnsatisfiedLinkError: no rxtxSerial in java.library.path thrown while loading gnu.io.RXTXCommDriver
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1878)
	at java.lang.Runtime.loadLibrary0(Runtime.java:849)
	at java.lang.System.loadLibrary(System.java:1087)
	at gnu.io.CommPortIdentifier.<clinit>(CommPortIdentifier.java:123)
	at com.digi.xbee.api.connection.serial.SerialPortRxTx.open(SerialPortRxTx.java:161)
	at com.digi.xbee.api.XBeeDevice.open(XBeeDevice.java:189)
	at com.digi.xbee.sendreceivedatasample.MainApp.main(MainApp.java:43) 

This exception indicates that the RXTX native library is not linked to the rxtx-2.2.jar file. See the second step of the Link the libraries to the project section.

• "Can't load AMD 64-bit .dll on a IA 32-bit platform thrown while loading gnu.io.RXTXCommDriver" (or similar message):

java.lang.UnsatisfiedLinkError: C:\Users\user\workspace\SendReceiveDataSample\libs\native\Windows\win64\rxtxSerial.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform thrown while loading gnu.io.RXTXCommDriver
	Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Users\user\workspace\SendReceiveDataSample\libs\native\Windows\win64\rxtxSerial.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1957)	
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1882)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1872)
	at java.lang.Runtime.loadLibrary0(Runtime.java:849)
	at java.lang.System.loadLibrary(System.java:1087)
	at gnu.io.CommPortIdentifier.<clinit>(CommPortIdentifier.java:123)
	at com.digi.xbee.api.connection.serial.SerialPortRxTx.open(SerialPortRxTx.java:161)
	at com.digi.xbee.api.XBeeDevice.open(XBeeDevice.java:189)
	at com.digi.xbee.sendreceivedatasample.MainApp.main(MainApp.java:43)

This exception indicates that the RXTX native library you have linked is not the correct one. Check to be sure you are not using a 32-bit JVM linked the 64-bit library, or vice versa.

If you experience the "com.digi.xbee.api.exceptions.InterfaceInUseException" exception, it indicates that the port you are trying to open is already in use. Ensure that you do not have any applications running and that the XCTU console of that port is not connected.

com.digi.xbee.api.exceptions.InterfaceInUseException: Port COM5 is already in use by other application(s)
	at com.digi.xbee.api.connection.serial.SerialPortRxTx.open(SerialPortRxTx.java:189)
	at com.digi.xbee.api.XBeeDevice.open(XBeeDevice.java:189)
	at com.digi.xbee.sendreceivedatasample.MainApp.main(MainApp.java:43)
Caused by: gnu.io.PortInUseException: Unknown Application
	at at gnu.io.CommPortIdentifier.open(CommPortIdentifier.java:467)
	at at com.digi.xbee.api.connection.serial.SerialPortRxTx.open(SerialPortRxTx.java:167)
	... 2 more
Error 0x5 at ..\src\termios.c(892): Access is denied.

If you experience the "java.lang.NoClassDefFoundError" exception, it indicates that the logger library (slf4j-api-1.7.7.jar) is not linked to the project. See the Link the libraries to the project section to know which libraries you have to link.

Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
	at com.digi.xbee.api.connection.serial.AbstractSerialPort.<init>(AbstractSerialPort.java:170)
	at com.digi.xbee.api.connection.serial.AbstractSerialPort.<init>(AbstractSerialPort.java:136)
	at com.digi.xbee.api.connection.serial.SerialPortRxTx.<init>(SerialPortRxTx.java:149)
	at com.digi.xbee.api.connection.serial.SerialPortRxTx.<init>(SerialPortRxTx.java:124)
	at com.digi.xbee.api.XBee.createConnectiontionInterface(XBee.java:38)
	at com.digi.xbee.api.AbstractXBeeDevice.<init>(AbstractXBeeDevice.java:164)
	at com.digi.xbee.api.XBeeDevice.<init>(XBeeDevice.java:90)
	at com.digi.xbee.sendreceivedatasample.MainApp.main(MainApp.java:40)

If you receive the "SLF4J: Class path contains multiple SLF4J bindings" message, it indicates that you linked several logger libraries. Ensure that only the following four libraries are added to your project:

• xbee-java-library-X.Y.Z.jar

• rxtx-2.2.jar

• slf4j-api-x.y.z.jar

• slf4j-nop-x.y.z.jar

The XBee Java Library only supports API and API escaped operating modes. You cannot use it with modules in transparent mode.

Check the following in XBee A (receiver):

1. The value of ID is 2015 (the same as the ID value of XBee B and XBee C).

2. The value of CE is Enabled[1]. The module is a coordinator.

Check the following in XBee B and XBee C (senders):

1. The value of ID is 2015 (the same as the ID value of XBee A).
2. Channel Verification (JV) is enabled.
3. The value of DH is 0.
4. The value of DL is 0.
5. The value of D4 is Digital Input [3].
6. The value of IC is 10 to changes in DIO4 pin (00010000 binary = 10 hexadecimal).

Note To learn how to configure IC parameter to monitor the pins, see How to obtain data from a sensor.

7. If the data is not received yet, restore the default settings of both XBees and reconfigure them.

Check the following in the Java code:

• The LINE constant that appears on the Java source code is IOLine.DIO4_AD4.

Check the following in XBee A (receiver):

1. The value of ID is 2015 (the same as the ID value of XBee B and XBee C).

2. The value of CE is Enabled[1] (the module is a coordinator).

Check the following in XBee B and XBee C (senders):

1. The value of ID is 2015 (the same as the ID value of XBee A).

2. Channel Verification (JV) is enabled

3. The value of DH is 0.
4. The value of DL is 0.
5. The value of D3 is ADC [2] if the XBee module is through-hole (THT). If the module is surface-mount (SMT), configure D2 as ADC [2] instead.
6. The value of IR is 1388 (5 seconds).

7. If the data is not received yet, restore the default settings of both XBee modules and reconfigure them.

Check the following in the Java code:

• The LINES constant that appears on the Java source code contains IOLine.DIO2_AD2 and IOLine.DIO3_AD3.

This message indicates that the module attached to your computer could not establish the connection with the device whose node identifier is the value REMOTE_NODE_ID constant. Check the following:

1. Both modules are in the same network.
2. The Node Identifier (NI) of the XBee B (receiver) is ROUTER.

In addition, the value of the REMOTE_NODE_ID constant that appears in the Java source code should be ROUTER.

Check the following:

1. In the XBee B (RECEIVER), the value of the D4 setting is Digital Out, High [5].
2. The LINE constant that appears on the Java source code is IOLine.DIO4_AD4.

The local device you have selected has no remote devices. Click the Discover remote devices button and XCTU discovers devices on the local device's network.

If there are no remote XBee modules to select in the Radio Range Test dialog, try one of the following resolutions.

Check cables

The USB cables should be firmly and fully attached to both the computer and the XBee development board. When attached correctly, the association LED on the adapter is lit.

Check that the XBee module is fully seated in the XBee Grove Development Board

When the XBee module is properly installed, it is pushed fully into the board and no air or metal is visible between the plastic of the adapter socket and the XBee module headers. Also, check that all ten pins on each side of the XBee module are in a matching hole in the socket.

Check the XBee module orientation

The angled "nose" of the XBee module should match the lines on the silk screening of the board and point away from the USB socket on the XBee Grove Development board.

Check that the XBee modules are in the same network

Check that the Network ID (ID), Preamble ID (HP), and Channel Mask (CM) settings have the same value for both XBee modules.

Restore default settings

If the XBee modules are properly connected and in the same network, restore default settings and configure them again.

Check cables

The USB cables should be firmly and fully attached to both the computer and the XBee development board. When attached properly, the association LED on the adapter is lit.

Check that the XBee module is fully seated in the XBee Grove Development Board

When the XBee module is properly installed, it is pushed fully into the board and no air or metal is visible between the plastic of the adapter socket and the XBee module headers. Also, check that all ten pins on each side of the XBee module are in a matching hole in the socket.

Check the XBee module orientation

The angled "nose" of the XBee module should match the lines on the silk screening of the board and point away from the USB socket on the XBee Grove Development board.

The local device (the one attached to your computer) can be configured to use API or transparent mode. The remote device RSSI value can only be read when the local XBee is working in API mode.

To display the remote RSSI value, reconfigure the local module to work in API mode.

This message indicates that no devices were found in the network. Ensure you have properly configured all your devices as it is described in the Configure the XBees step.

This message indicates that the module attached to your computer could not send the message to the device whose node identifier is <XXXX>.

Ensure that you typed the node identifier correctly and that it is in the list of devices found by the application. If it is not there, launch the application again.