- Sun Aug 05, 2018 8:05 am
#77589
I am tying to connect an Ardupilot flight controller to an application on my Android phone via ESP8226. Its a well established option and many are successful with it. I have followed the wiki on it exactly. The system connects the ESP8226 via the UART on the flight controller..the ESP8226 runs firmware which packetizes the flight controller communications and sends out via UDP.....there are PC based and Android based applications which allows communication via WIFI to the ESP8226 and its connected flight controller...
the issue is that the PC apps all "connect" and work well with my setup.....but the Android based apps normally do not "connect"....do not see the UDP packets....the phone IS able to connect to the ESP8226 firmware's built-in setup web page for this bridge(TCP)....the weird thing is that if I connect to the ESP8226 server and utilize it via the PC, THEN , SOMETIMES, my Android apps can connect to it...but sporadically....
I have checked to be sure that the UDP sockets used are not blocked somehow by the phone....and others have no trouble connecting to either the PC apps or the Android phone apps using the exact same firmware and setup steps....
any ideas?
the issue is that the PC apps all "connect" and work well with my setup.....but the Android based apps normally do not "connect"....do not see the UDP packets....the phone IS able to connect to the ESP8226 firmware's built-in setup web page for this bridge(TCP)....the weird thing is that if I connect to the ESP8226 server and utilize it via the PC, THEN , SOMETIMES, my Android apps can connect to it...but sporadically....
I have checked to be sure that the UDP sockets used are not blocked somehow by the phone....and others have no trouble connecting to either the PC apps or the Android phone apps using the exact same firmware and setup steps....
any ideas?
