{"id":1662,"date":"2024-01-04T22:12:40","date_gmt":"2024-01-04T14:12:40","guid":{"rendered":"http:\/\/www.autouav.net.cn\/?p=1662"},"modified":"2024-01-04T22:15:16","modified_gmt":"2024-01-04T14:15:16","slug":"how-to-setup-remoteid-for-ardupilot","status":"publish","type":"post","link":"https:\/\/www.autouav.net.cn\/?p=1662","title":{"rendered":"How to setup RemoteID for ardupilot"},"content":{"rendered":"<p><a href=\"https:\/\/ardupilot.org\/dev\/docs\/opendroneid.html#opendroneid\">OpenDroneID \u2014 Dev documentation (ardupilot.org)<\/a><\/p>\n<ul class=\"simple\">\n<li>Make sure the autopilot serial port that the module is attached is setup for 57.6K and MAVLink2 if using serial interconnect. If using DroneCAN, then make sure the CAN parameters are enabled appropriately.<\/li>\n<li>Run the \u2018script remoteid.scr\u2019 command to load the script\u2026you should see it announce that it has loaded the OpenDroneID module and other commands in the console<\/li>\n<li>Set the following params:\n<ul>\n<li><a class=\"reference external\" title=\"(in Rover)\" href=\"https:\/\/ardupilot.org\/rover\/docs\/parameters.html#did-enable\"><span class=\"xref std std-ref\">DID_ENABLE<\/span><\/a>\u00a01<\/li>\n<li>then reboot pixhawk.<\/li>\n<li><\/li>\n<li><a class=\"reference external\" title=\"(in Rover)\" href=\"https:\/\/ardupilot.org\/rover\/docs\/parameters.html#did-options\"><span class=\"xref std std-ref\">DID_OPTIONS<\/span><\/a>\u00a01<\/li>\n<li><a class=\"reference external\" title=\"(in Rover)\" href=\"https:\/\/ardupilot.org\/rover\/docs\/parameters.html#did-mavport\"><span class=\"xref std std-ref\">DID_MAVPORT<\/span><\/a>\u00a0X where x is the serial port attached to OpenDroneID module<\/li>\n<li><a class=\"reference external\" title=\"(in Rover)\" href=\"https:\/\/ardupilot.org\/rover\/docs\/parameters.html#did-candriver\"><span class=\"xref std std-ref\">DID_CANDRIVER<\/span><\/a>\u00a00<\/li>\n<li><a class=\"reference internal\" href=\"https:\/\/ardupilot.org\/dev\/docs\/AP_Periph-Parameters.html#ahrs-ekf-type\"><span class=\"std std-ref\">AHRS_EKF_TYPE<\/span><\/a>\u00a03<\/li>\n<li><a class=\"reference internal\" href=\"https:\/\/ardupilot.org\/dev\/docs\/AP_Periph-Parameters.html#gps-type\"><span class=\"std std-ref\">GPS_TYPE<\/span><\/a>\u00a01<\/li>\n<li><a class=\"reference internal\" href=\"https:\/\/ardupilot.org\/dev\/docs\/AP_Periph-Parameters.html#gps-type2\"><span class=\"std std-ref\">GPS_TYPE2<\/span><\/a>\u00a00<\/li>\n<\/ul>\n<\/li>\n<li>If its a CAN module these parameters should be substituted:\n<ul>\n<li><a class=\"reference external\" title=\"(in Rover)\" href=\"https:\/\/ardupilot.org\/rover\/docs\/parameters.html#did-mavport\"><span class=\"xref std std-ref\">DID_MAVPORT<\/span><\/a>\u00a0-1<\/li>\n<li><a class=\"reference external\" title=\"(in Rover)\" href=\"https:\/\/ardupilot.org\/rover\/docs\/parameters.html#did-candriver\"><span class=\"xref std std-ref\">DID_CANDRIVER<\/span><\/a>\u00a01<\/li>\n<\/ul>\n<\/li>\n<li>Any OpenDroneID pre-arms should disappear and the vehicle appear on your android phone with this app:\u00a0<a class=\"reference external\" href=\"https:\/\/play.google.com\/store\/apps\/details?id=org.opendroneid.android_osm\">https:\/\/play.google.com\/store\/apps\/details?id=org.opendroneid.android_osm<\/a><img decoding=\"async\" src=\"https:\/\/www.autouav.net.cn\/wp-content\/uploads\/2024\/01\/opendroneid-android-app.jpg\" alt=\"..\/_images\/opendroneid-android-app.jpg\" \/><\/li>\n<li>\n<h2>Using Mission Planner as the GCS<\/h2>\n<p>Mission Planner has a special Drone ID tab in its DATA view for use with OpenDroneID modules attached to the autopilot which allows monitoring status, attaching the required GPS for operator location of the GCS, and UAS and Operator ID string setup. See\u00a0<a class=\"reference external\" title=\"(in Mission Planner)\" href=\"https:\/\/ardupilot.org\/planner\/docs\/opendroneid.html#opendroneid\">OpenDroneID Panel<\/a>.<\/li>\n<li><a href=\"https:\/\/ardupilot.org\/planner\/docs\/opendroneid.html#opendroneid\">OpenDroneID Panel \u2014 Mission Planner documentation (ardupilot.org)<\/a><\/li>\n<li>\n<div class=\"document\" role=\"main\">\n<div>\n<section id=\"opendroneid-panel\">\n<h1>OpenDroneID Panel<\/h1>\n<p>Mission Planner has a special Drone ID tab in its DATA view for use with OpenDroneID modules attached to the autopilot which allows monitoring status, attaching the required GPS for operator location of the GCS, and UAS and Operator ID string setup.<\/p>\n<div class=\"admonition note\">\n<p class=\"admonition-title\">Note<\/p>\n<p>This feature is rapidly evolving and is available only on the latest Beta Mission Planner updates. Updates will be made frequently so check for the latest version, frequently.<\/p>\n<\/div>\n<p><a class=\"reference external image-reference\" href=\"https:\/\/www.autouav.net.cn\/wp-content\/uploads\/2024\/01\/mp_remoteid.png\"><img decoding=\"async\" src=\"https:\/\/www.autouav.net.cn\/wp-content\/uploads\/2024\/01\/mp_remoteid.png\" alt=\"..\/_images\/mp_remoteid.png\" \/><\/a>This control manages the exchange of GCS\/Operator information with the RID module, via the AutoPilot connection.<\/p>\n<section id=\"gps\">\n<h2>GPS<\/h2>\n<p>Mission Planner must have a source of GPS information about its location. The GPS must provide valid NMEA GPGGA or GNGGA sentences.<\/p>\n<p>This can be accomplished by either attaching a GPS to the PC\u2019s COM or USB port (some GPS may require an FTDI adapter) or by using an app like\u00a0<a class=\"reference external\" href=\"https:\/\/play.google.com\/store\/apps\/details?id=com.cajax.gps2bt2&amp;hl=en_US&amp;gl=US\">GPS to Bluetooth<\/a>\u00a0on your phone to feed GPS data via a Bluetooth serial COM port to Mission Planner.<\/p>\n<p><a class=\"reference external image-reference\" href=\"https:\/\/www.autouav.net.cn\/wp-content\/uploads\/2024\/01\/gps2bt.png\"><img decoding=\"async\" src=\"https:\/\/www.autouav.net.cn\/wp-content\/uploads\/2024\/01\/gps2bt.png\" alt=\"..\/_images\/gps2bt.png\" \/><\/a>The COM port and baud rate (normally 9600) are entered in the\u00a0<code class=\"docutils literal notranslate\"><span class=\"pre\">GCS<\/span>\u00a0<span class=\"pre\">GPS<\/span><\/code>\u00a0dialogs and then Connect to Base GPS pushed. If successful, location data will immediately appear below those dialog boxes.<\/p>\n<p>GPS raw output can be viewed in real time by double clicking the GPS status string under the COM Port dropdown.<\/p>\n<\/section>\n<section id=\"remote-id-status-box\">\n<h2>Remote ID Status Box<\/h2>\n<ul class=\"simple\">\n<li>GCS GPS: Red &#8211; Lost Connection to GPS, Orange &#8211; Connected, no Fix, Yellow &#8211; Fix, no DGPS and Green &#8211; DGPS Fix.<\/li>\n<li>RID Comms: Green &#8211; Healthy Connection, Red &#8211; Timeout (Currently 5 seconds)<\/li>\n<li>ARM Status: Green when Armed, Otherwise Red with Reason in RID Armed Status Reason in Status tab.<\/li>\n<li>UAS ID: Red when the UAS ID tab is not fully populated. Typically, this information will be provided by the RID module when using Standard ID, and may be populated by the user in future implementation of after-market or add-on RemoteID Broadcast Modules.<\/li>\n<\/ul>\n<\/section>\n<section id=\"string-setup-tabs\">\n<h2>String Setup Tabs<\/h2>\n<p>Two tabs are provided for input of UAS and Operator information in these initial test and development version of the interface. Some of these may become read-only and obtained from the RemoteID module in the future, depending on jurisdiction and implementation. They are provided for experimentation and testing initially.<\/p>\n<\/section>\n<section id=\"master-status-indicator\">\n<h2>Master Status Indicator<\/h2>\n<p>Located in the left middle side of the panel. The master status will indicate RED if any conditions for proper operation are not valid.<\/p>\n<p>Local regulations may require such a master indicator. In Mission Planner, this will be present in this tab as well as on the map (pending).<\/p>\n<\/section>\n<\/section>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>OpenDroneID \u2014 Dev documentation (ardupilot.org) Make sure the autopilot serial port that the module &#8230; <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"class_list":["post-1662","post","type-post","status-publish","format-standard","hentry","category-25"],"_links":{"self":[{"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=\/wp\/v2\/posts\/1662","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1662"}],"version-history":[{"count":3,"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=\/wp\/v2\/posts\/1662\/revisions"}],"predecessor-version":[{"id":1668,"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=\/wp\/v2\/posts\/1662\/revisions\/1668"}],"wp:attachment":[{"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1662"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1662"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.autouav.net.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1662"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}