Replies

  • Ryan, did you figure out the issue?

    Ryan Henderson said:

    Old thread here I know but...

    The current version of UGCS seems to connect just fine to the Solo. The only thing I can't seem to get working is uploading a mission to the aircraft. I receive the error message of All attempts to write parameters failed. Has anyone been successful in uploading a flight plan to a Solo? 

    UgCS with 3DR Solo?
    Anyone out there have any success using UgCS with the 3DR Solo? I can't figure out how to connect the two. Thanks in advance.
  • Old thread here I know but...

    The current version of UGCS seems to connect just fine to the Solo. The only thing I can't seem to get working is uploading a mission to the aircraft. I receive the error message of All attempts to write parameters failed. Has anyone been successful in uploading a flight plan to a Solo? 

  • One note on this, prior to starting netmon and uGCS, edit the vsm-ardupilot.conf file, ensure the udp connections you have been attempting to use are added and they are uncommented (remove the # symbol). then do the above, without that uGCS wont be looking for the udp on 10.1.1.1 and netmon wont produce any results.

  • I having it working, to do this you need to use NetMon or Wirshark or…, connect to solo’s wifi, start uGCS. Run netmon, filter on wifi card, start a capture, wait 5 secs. Stop capture, view udp connections.

    3702389164?profile=original

    In my case the src is 14550, which it should always be. Destination is 35486 ( this port changes, so the next time you connect, the port number may or may not be the same ).

    Open the vsm-ardupilot.conf file and ensure the lines below are correct)

    # 1. UDP port which will listen for incoming mavlink messages.

    vehicle.ardupilot.udp.1.udp_local_port = 14550

     # 2. IP address of the vehicle to connect to.

    vehicle.ardupilot.udp.1.udp_address = 10.1.1.1

     # 3. UDP port of the vehicle to connect to.

    vehicle.ardupilot.udp.1.udp_port = 35486

    For #3, the udp port will change as stated above, so when you connect to Solo's Wifi, open NetMon or Wireshark or whatever, filter on the wifi card, run uGCS and look at the UDP port, the new dest udp needs to added to line 3.

    save the file (vsm-ardupilot.conf).

    Restart uGCS and you should see the Solo.

    you can verify in the uGCS log file that you see the below.

    2017-07-22 14:06:44.652 - <INF> 5 [mavlink_vehicle_manager.cpp:468] New connection [10.1.1.1:35486->0.0.0.0:14550:0].

    2017-07-22 14:06:44.668 - <INF> 5 [mavlink_vehicle_manager.cpp:218] Creating vehicle: [ArduPilot:1] Mavlink id 1

    2017-07-22 14:06:44.668 - <DBG> 2 [cucs_processor.cpp:334] Vehicle id=128 registered

    2017-07-22 14:06:44.901 - <DBG> 6 [ardupilot_vehicle.cpp:121] Ardupilot version=3.5.0, type=255

    2017-07-22 14:06:44.905 - <DBG> 6 [mavlink_vehicle.cpp:844] [ArduCopter:1] 1 waypoints received.

    and so on,  Hope this helps.

    netmon.png

    https://storage.ning.com/topology/rest/1.0/file/get/3702389247?profile=original
  • Hey Jonathan

    I think for you the better as they are so open source its crazy, They are such a reliable tool with many adaptions of software than can be used with them.

    Have you seen the solex app a guy has developed, its only available on android but is always being updated.

    I also believe that from a teaching perspective if using the Solo then mission planner is so much easier to learn and implement. You can be flying a mission in minutes, I have actually used this to draw words with my drone. 

    Now I want to advance my sky writing I really need to use the UGCS as this makes making flight path in 3d so much easier, well it will be as soon as I get my solo to connect to it.

    UGCS is far superior to Mission planner but a way steeper learning curve.

    From what ive found is Controller's WiFi network and access Solo and the Controller using their dedicated IP addresses (10.1.1.1 and 10.1.1.10)

    10.1.1.1 5502   possibly 5502 is the port

    vehicle.ardupilot.udp.1.udp_local_port = 14550
    vehicle.ardupilot.udp.1.udp_address = 10.1.1.1  or 10.1.1.10
    vehicle.ardupilot.udp.1.udp_port = 5502

    possibly

    Ive not tried the above combo yet.

  • I will second this.  My University invested into the 3DR Solo concept and for better or worse we are stuck with them.  I would like to use UGCS in conjunction with the Solo's for classroom instruction because I think students will find UGCS easier to learn than Mission Planner.  

  • I never was able to figure out the correct UDP port, so never got UgCS to connect.  But still interested if someone can figure it out and share the info.

    Tom

  • Hello Simon,

    The connection suggestion was more theoretical, but since we see interest in Solo support in UgCS we will re-consider supporting the drone.

    I may only suggest to try to get correct udp localport and IP values on Solo section of this forum.

    Good luck!

  • hi im wondering if any one managed to get this going with the solo. I would love to be able to connect.

    Does adding the above comments to the script enable this, is it testing and working. 

    Where would I find the Ip and port for 3dr solo when hooked into its wifi.

    Thanks

    This would be the most awesome thing in ages if I can get it to work.

  • How do I find the vehicle.ardupilot.udp.1.udp_port = <udp port on Solo> ?

    It appears that the IP address =10.1.1.1

    and the local port should be = 14550

    But I can't figure out  the correct <udp port on the solo> value. Google searches have come up empty or incorrect.   And I can't find this listed in Mission Planner or its docs.

    Any suggestions?

    As you can probably tell I'm not a programmer, just trying to get this to work.

    Thanks again.

    Tom

This reply was deleted.