This is my first support request for Mission Planner on this forum, apologies if this has been asked before but I could not find something that could work.
I have an AUAV.co PixRacer running ArduCopter 3.4.5. The PixRacer has an ESP8266 WiFi board which is running MavLink ESP8266 firmware v1.1.0. I am using Mission Planner 1.3.44 on two machines (one notebook and one Intel tablet), both running Windows 10 Pro x64 and using Intel PROwireless driver (the latest version from Intel). I can connect without issues to the "PixRacer" AP via Mission Planner 1.3.44. The connection settings are UDP at 921k baud, using the standard connection ports.
Upon upgrading to Mission Planner 1.3.45 (tried both in-place upgrade and uninstalling/re-installing the software), I've noticed a change to the connection behaviour; Mission Planner upon finishing loading tries immediately to connect via UDP to the PixRacer, even if the board is not initialized. Subsequent efforts to connect to the board (after powering it up) fail and it is no longer possible to connect to the PixRacer via WiFi. Connecting via USB or 3DR MavLink telemetry works as expected, only the UDP WiFi connection is no longer possible. Shutting down Mission Planner, rebooting the machine, rebooting the PixRacer, connecting the PC to the PixRacer AP and then starting up Mission Planner does not change anything; I cannot connect to the PixRacer via WiFi.
I have reverted back to MP v1.3.44 where everything works fine but I would like to know if it is possible to mimic the v1.3.44 connection behaviour on MP v1.3.45 in order to be able to connect via WiFi to the PixRacer.
Thank you very much in advance for your help.