Description

I do not see available COM ports!

If you are using the a virtual environment to run the softwares on your USB card, make sure, that all of the COM-ports associated with the evaluation boards are transferred to the virtual PC.

The neighbor list under "developer tab" is empty!

This error can happen due to several reasons:

• Distance between boards:
  The boards should be placed at least a meter apart in order to properly function. An alternate solution to this problem can be to decrease the transmission power for the modules using the "config app".
• Dissimilar network keys:
  All the boards which should belong to the same network has to share the same network key. THe network key settings can be accessed using the "Config app".
• Jumper placements:
  Make sure that all tue jumpers are in the proper position for operation. More information on the jumpers can be found here. Pay special attention to the position of the "Main Jumper" and the "supply reg. select jumper".
• Antenna:
  Make sure that the antenna and the antenna jumper wire is connected correctly.
• Trace messages:
  It can happen, that the network is working fine, but the "Trace Output" setting is not enabled. You can make sure that the trace output is enabled by looking at the timestamp in the upper left corner of the "developer tab" in "config app". In the case when the trace is disabled, the board will not send updates of the neighbor list to the "config app". You can enable trace mode in the configuration settings. More information can be found here.
• Node ID:
  Make sure the the NodeID of your module is not "0xFFFF". You can choose the modules NodeID using the "config app". More about his can be found here.
• Firmware version:
  Only nodes with the same firmware version can be neighbors. If you are unsure which version your moduls have, you can either check it using the command line tool, or you can reinstall the firmware on the modules using the "config app". For the second option, see the Firmware update tutorial here.

I have pressed the "Start" button, and nothing happened!

• Trace messages:
  It can happen, that the "Trace Output" setting is not enabled. When the trace output is disabled, the board will not send updates of the neighbor list to the "config app". You can enable trace mode in the configuration settings. More information can be found here.
• Standalone mode:
  FTDI?

The messages get no acknowledge!

• Neighbor:
  Make sure the nodes are listed as each-other's neighbors. You can check this on the "developer tab" of the "config app".
• Message queue:
  If a message is stuck in the message queue, then the intended recipient node can not send an acknowledge back. Make sure the message is in "written" status in the "demo app" in the "Tx Status" column.
• Message arrived:
  You can also check if the message is arrived at the intended recipient node in the "demo app" instance connected to the recipient evaluation board.

My messages get stuck in "Enqueued" state!

• Config tool logout:
  You have to log out from the "config app" in order to send messages through the "demo app". If you are still logged in to the configuration settings, it can cause the issue.
• DIP switch positions: Please make sure that the DIP switch next to the USB port on your evaluation board is set to the correct position (All switches are in the "ON" position).

During firmware update the "Bringing device into bootloader mode" window times out!

• Reset:
  Try to push the reset button on the evaluation board then immediatley after initialize the firmware update.
• Power cycle:
  Try to unplug your evaluation board from the computer and remove the battery. After a couple of seconds, reconnect it and try the firmware update again.

During firmware update, I get an error message!

• Faulty firmware file:
  Acquire a new version of the firmware from the NeoCortec website or contact us.

I am unable to log in on the modules with the provided password!

• Case sensitivity:
  The passwords for the modules are case-sensitive.
• Hex checkbox:
  Please make sure that the "as hex" checkbox on the left of the password text field is set appropriately to the password format that you have typed in.
• Password changed:
  Please make sure no-one changed the password, and it is still the factory-original. If the password was changed and the new password was forgotten, please contact us.
• Firmware update:
  A firmware update will override all of the previous settings, including passwords, resetting them to factory default.

My module does not seem to detect WES networks!

• Client conflict:
  The WES server can only handle one client at a time. Please make sure that only one node is in WES client mode.
• WES key:
  Please make sure that the WES key is correctly set amongst the nodes. All nodes connecting to the same WES network should have the same WES key.
• Distance between boards:
  The boards should be placed at least a meter apart in order to properly function. An alternate solution to this problem can be to decrease the transmission power for the modules using the "config app".

My module does not start the WES server after the "Start Server" button is pressed!

• Message status:
  Please check if the message is in "written" status. You can see a message's status in the "demo app" in the "Tx Status" column.

My module does not update it's Node ID through the WES network!

• Client conflict:
  The WES server can only handle one client at a time. Please make sure that only one node is in WES client mode.
• Distance between boards:
  The boards should be placed at least a meter apart in order to properly function. An alternate solution to this problem can be to decrease the transmission power for the modules using the "config app".
• Setup request message:
  Please make sure that your WES server node did get the "setup request" message from the WES client node. IMAGE PLACEHOLDER!!!!

My nodes do not hibernate when commanded so!

• Message status:
  Please check if the "hibernate" message is in "written" status. You can see a message's status in the "demo app" in the "Tx Status" column.
• Recipient NodeID:
  Please make sure that the hibernate command was sent to the correct NodeID.

My hibernated nodes do not wake up when commanded so!

• Wakeup parameter: Please make sure that the wakeup parameter what you are using is set correctly, both on the hibernated node and the waking nodes.
• Message status:
  Please check if the "wake up" message is in "written" status. You can see a message's status in the "demo app" in the "Tx Status" column.
• NodeID:
  Please keep in mind, that the waking of a node should be initialized by a separate node, which is not in hibernation. For this reason, the wakeup command is not issued to the hibernating node, but to a different one which we intend to use for the waking. The waking and the hibernating node should be separated by no more than one "hop" from each other within the network.

My nodes do not send messages when in Generic Application - GPIO mode is set!

• Operation mode:
  Please check if your devices operate in the same mode as you have set the generic application up for.
• Receiver node not on network:
  Please check, that your receiver node is in the same network as the sender, and that the package has a route from source to origin.