I can connect to an APM2 using a 3DR on COM4. Mission Planner works fine and will successfully upload a route. UgCS connects also and receives messages. Everything appears to work fine but UgCS is unable to upload a route and terminates with an error.
Looking through the Ardupilot log it seems that UgCS is confused about the ports in use. It finds COM4 and messages arriving on it. It then finds COM3, which has no hardware attached, and subsequently uses that when trying to upload the route. Of course it fails.
This appears to be strange behaviour. So it receives messages on COM4 which is sucessful, but tries to send on COM3 which fails.
Any ideas????
Replies
Ok I fixed it. This should help your developers because it should not be this way.
After studying the logs it appeared the upload failure was related to sending the rangefinder minimum. Since I built APM2 without the rangefinder and none of the new aeroplane builds have the rangefinder enabled anyway due to code space constraints, I cleared the entry in the profile definition.
After this the route upload worked.
This is a very time consuming gotcha and I wonder if there are any more in hiding. For my research project I will be using a Pixhawk and will be building the code myself because I have special requirements. I would expect that if something is not supported by the FCU then UgCS would be able to find this out, or at least ignore it.
Is this possible?
Recall I am evaluating this product. I will give it a fair go because I like its 3D capability. The research will involve NOE flight profiles and UgCS seems very suited to planning such flights. GPR surveys will require following a terrain profile so I will persist with UgCS for now.
That didn't work. Do you want the logs and if so which log?
Sergey Zuev said:
Please set port name manually in the config file (C:\Program Files (x86)\UgCS\bin\vsm-ardupilot.conf).
In your case it will be:
vehicle.ardupilot.serial_port.1.name = com4
Best regards, Sergey Zuev