i just tested here again, and cant fault the connection to a pixracer via wifi.
do you have wireshark or similar installed to see whats going on?
No but I will get it and use it to capture network information.
Will report back.
also, how old is your esp8266 firmware?
@Michael_Oborne there is another issue related to Pixracer and ESP8266 here: I2C Maxbotix range finder on Pixracer
same question as above. what does that url show? is data making it to the esp8266?
I’ll have to check,
On this particular issue, there is no rangefinder values shown on display when PixRacer is connected through UDP with the ESP8266 but when connecting using USB or Telemetry, it shows values.
Apologies for not replying sooner but I was at work.
I’ve managed to fix the WiFi module and now it connects to MissionPlanner 1.3.49 almost everytime.
Using 192.168.4.1/getstatus, my board responds:
Comm Status
Packets Received from GCS 0
Packets Sent to GCS 2720
GCS Packets Lost 0
Packets Received from Vehicle 2720
Packets Sent to Vehicle 54
Vehicle Packets Lost 0
Radio Messages 0
System Status
Flash Memory Left 487424
RAM Left 12960
Parameters CRC C97A639A
I remembered that on April 2017, I’ve flashed both my AUAV PixRacer and clone PixRacer ESP8266 boards using the latest MAVLinkESP firmware v1.1.1 and by also using 192.168.4.1/getparameters I get the following
Name Value
SW_VER 16842752
DEBUG_ENABLED 0
WIFI_MODE 0
WIFI_CHANNEL 11
WIFI_UDP_HPORT 14550
WIFI_UDP_CPORT 14555
WIFI_IPADDRESS 17082560
WIFI_SSID1 1383622992
WIFI_SSID2 1919247201
WIFI_SSID3 0
WIFI_SSID4 0
WIFI_PASSWORD1 1920493936
WIFI_PASSWORD2 1919247201
WIFI_PASSWORD3 0
WIFI_PASSWORD4 0
WIFI_SSIDSTA1 1383622992
WIFI_SSIDSTA2 1919247201
WIFI_SSIDSTA3 0
WIFI_SSIDSTA4 0
WIFI_PWDSTA1 1920493936
WIFI_PWDSTA2 1919247201
WIFI_PWDSTA3 0
WIFI_PWDSTA4 0
WIFI_IPSTA 0
WIFI_GATEWAYSTA 1
WIFI_SUBNET_STA 1
UART_BAUDRATE 921600
I remember that all I did was to flash the boards with the MAVLink firmware using my FTDI adapter, as both boards came with older firmware version than 1.0.4 and the 192.168.4.1/update page always returned FAIL. No other parameters were changed. Today, I’ve performed another flash of one of my two boards using the same firmware (I kept the firmware file back then and it is exactly the same as the current one on the homepage) and issued the same getparameters just to check that they are the same default ones.
Using Fing on Android, I’ve checked the network connection between my tablet (Chuwi Hi8, Intel Z3736F, Android 4.4.4 / Windows 8.1 x86) and the PixRacer and noticed that the network link used as gateway the 192.168.4.1 address. Rebooting the tablet to Windows and connecting again to PixRacer, the network information shows a null default gateway address.
Re-checking the default MAVLinkESP v1.1.1 parameters, I’ve noticed that both WIFI_GATEWAYSTA and WIFI_SUBNETSTA had values of 1 (this applies to both boards). Changing both of these to 0 solved the problem and now MP always connects to the PixRacer via the ESP8266. I do not know if this problem (the wrong configuration) applies only to my boards or it is a case of wrong default configuration (I assume that flashing the board with the firmware erases everything, including the saved configuration, then replaces it with default values).
Now, when I remove my 3DR Telemetry module, I can connect to the PixRacer WiFi (previously this was not possible even with the 3DR Telemetry module removed). Some times MP fails to connect responding “Only 1 heartbeat packet received” but rebooting the WiFi card fixes this and connects which is an improvement. The parameter changes above do not have any effect on Tower Beta Android app, this application can connect every single time to the PixRacer, whether the 3DR telemetry is connected or not.
Hope this can help.
Again, many thanks to everyone for the time taken to help me fix this.
Interesting, when we look here: https://github.com/dogmaphobic/mavesp8266/blob/master/PARAMETERS.md
WIFI_IPSTA MAV_PARAM_TYPE_UINT32 Wifi STA Static IP Address (4)
WIFI_GATEWAYSTA MAV_PARAM_TYPE_UINT32 Wifi STA Gateway Address (4)
WIFI_SUBNETSTA MAV_PARAM_TYPE_UINT32 Wifi STA Subnet Address (4)
(4) Defaults to 0 for an unset address. If either the STA IP, Gateway, or Subnet are set, then all three need to be set for it to work properly.
your issue will be mavlink routing related. and not a MP issue as such. MP can only display what it is sent.
the settings I’m using are
Parameters
Name
Value
SW_VER
16842752
DEBUG_ENABLED
0
WIFI_MODE
0
WIFI_CHANNEL
11
WIFI_UDP_HPORT
14550
WIFI_UDP_CPORT
14555
WIFI_IPADDRESS
17082560
WIFI_SSID1
1383622992
WIFI_SSID2
1919247201
WIFI_SSID3
0
WIFI_SSID4
0
WIFI_PASSWORD1
1920493936
WIFI_PASSWORD2
1919247201
WIFI_PASSWORD3
0
WIFI_PASSWORD4
0
WIFI_SSIDSTA1
1383622992
WIFI_SSIDSTA2
1919247201
WIFI_SSIDSTA3
0
WIFI_SSIDSTA4
0
WIFI_PWDSTA1
1920493936
WIFI_PWDSTA2
1919247201
WIFI_PWDSTA3
0
WIFI_PWDSTA4
0
WIFI_IPSTA
0
WIFI_GATEWAYSTA
0
WIFI_SUBNET_STA
0
UART_BAUDRATE
921600
which are the defaults
ive just added some more options to the MP esp8266 config page. this means that you need comms working in the first place however.
Updating the ESP firmware resolved the issue 
thanks for reporting back the fix!!
In my case, disabling the firewall did the trick. I wish it was easier to find which port exactly I need to exclude.
I think it is UDP port 14550.
the ports /\ you need to allow
1 Like
Thanks for the clarification!
Hello, I have NodeMcu v3 chip and tried 3 of the most famous firmware, but had no success. I flashed MaVESP 1.1.1, MAVESP 2 and ESP-LINK. My GCS is unable to connect to the vehicle through UDP or TCP. Is there any solution to this? I tried @Frontier 's solution but it didn’t worked.
Board: Apm 2.6