Robotis Openmanipulatorx icon Robotis Openmanipulatorx — Inverse kinematics for Robotis OpenManipulatorX: compute joint angles and MoveTo 3D (cm) positions, supports camera-to-CM mapping for pick-and-place. Try it →
Asked

EZ-B V4/2 Too Slow In Wifi Client Mode

Hello,

I've successfully connected to my EZ-B in Ad Hoc WiFi mode and configured it to connect to my home WiFi network.  It boots up and tells me it's connected and has a green flashing light.  In the ARC app, I can scan and see it's address (192.168.1.63 in my case).  When I try to connect to it, in ARC, the connection fails due to the operation timing out.  If I do a port scan, nothing shows as open on the EZ-B.  If I type 192.168.1.63 into my browser, I get the web page for the EZ-B - but it takes a very long time to load.  This is the WiFi version: WiFi 3165 v2017.01.05.00

I've rebooted the EZ-B and the same thing happens.  My WiFi router is in the same room and is an AirPort Extreme.  Nothing else is this slow on my network. 

Any ideas what could be going on?

Thanks!



Related Hardware (view all EZB hardware)
EZ-B V4 by EZ-Robot
EZ-B v4 with Synthiam ARCx controls servos, sensors, camera and audio over Wi-Fi or USB serial, no firmware needed.
Wi-Fi / USB
Servos 24
Camera
Audio
UART 3
I2C
ADC 8
Digital 24

ARC Pro

Upgrade to ARC Pro

Subscribe to ARC Pro, and your robot will become a canvas for your imagination, limited only by your creativity.

Author Avatar
PRO
USA
#1  

Hi 

try when you connect to the EZ -B V4

press the reset  and it will connect - in router then set the ip

#2  

Make sure your antivirus program is turned off.

#3  

No joy resetting the WiFi and putting the EZ-B back into client mode.  Same issue.

I’m not running an antivirus on the Mac or Raspberry Pi.

I plan on using a nano router in the robot anyway, so I put the EZ-B into client Wi-Fi mode on that, instead of my home router, and all is well again.

Author Avatar
PRO
Synthiam
LinkedIn Thingiverse Twitter YouTube GitHub
#4  

If you identify the cause, let us know. Some application or router compatibility is causing the symptom. However, it's never risen before.