Notice: The information and software provided on this site is no longer maintained or developed by Omron, or Omron Adept MobileRobots. It is provided as an archive only. This site may be discontinued at any time and without warning.

Variants or forks of some Open Source projects might now be maintained by individual developers and customers for their own use; they may have published them in popular online source code repositories or other web sites. These versions are not endorsed or supported by Omron, but by their individual users and developers. Contact the maintainers or developers of those forks only for support and questions. All copyrights and other license terms continue to apply.

Wireless Network Problems

From MobileRobots Research and Academic Customer Support

Jump to: navigation, search
  • The robot's wireless interface must be on the right wireless network. MobileRobots initially sets the

ESSID to "Wireless Network" (or "WaveLAN Network" on older robots) during installation, but your network may use a different ESSID. See Wireless Network Configuration for details on setting the ESSID. For questions about what security features need to be used, consult your IT department or network administrator.

  • Make sure your laptop or other computer is on the same wireless network as the robot or is connected to the access point via ethernet network.
  • Seekur and Seekur Jr. robots have their own WRAP wireless access point. Join this network ("Seekur" or "SeekurJr") with your laptop. (You can also reconfigure the WRAP to join an existing wireless network instead if desired.)
  • Some wireless access points include a "wireless client isolation" feature that prevents two wireless clients from communicating. Disable this in the access point configuration to allow your laptop to communicate directly with the robot if both are using wireless networking.
  • One possible cause of poor performance is a mismatch between the 802.11 wireless networking modes (a, b, g) of the robot's card and the access point. While theoretically, the modes are downward-compatible, the interaction/negotiation between the client and the access point can interrupt the network or cause poor or intermittent performance. Try changing the mode of the access point to match that of the robot's card, or vice versa.

More Information

Personal tools