I have a UDP link set up to my APM::Rover, which normally works fine, with the exception of one issue.
If the Pixhawk is sending UDP packets, and I start the APM planner, it will immediately begin receiving packets and showing telemetry data, however it cannot send commands to the Pixhawk, only listen. In order to allow it to send commands, I have to go into the settings for the UDP connection and click “Add IP”. After entering the proper IP and port, it suddenly works.
IF I restart the APM Planner after this, I cannot write to the Pixhawk until I repeat the same procedure.
Thanks Bill. I’m pretty sure I am running the beta, but I will recheck and post an issue if I am not.
I have a demo coming up where I have to make this work, and if it’s not fixed, I’m wondering about compiling the source myself and just including a couple of lines to automatically add the connection every time the program is started. I actually see a few lines that do exactly this in the source. I’m hoping I don’t have to do this though. It looks like the Windows APM Planner build guide hasn’t been updated in some time.
I’ve jus verified and this is not an issue. It works overtime for me as expected with 2.0.16-rc3 and SITL using UDP.
You could try deleting the settings file at ~/.config/com.diydrones/
I’m not sure what OS you are using, but the above is the location on Linux/OSX for windows I can’t remember the exact location but some like $HOME/.config would make sense
Interesting, my log has the same issue, but I can control SITL using UDP no problem. I haven’t had time to look at the details. sorry. And I think this is potentially a windows only issue. I’m using OS X 10.10