请问媒体和航线的oss用的是同一个么
如题,还有,我配置了oss,但是媒体上传会失败,在java的日志中会看到频繁的调用 /media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/fast-upload接口。
rtmp推流的地址是每次都会变么,我如果停止推流,再重新推流,/live 路径后面的地址会变掉,看样子像是个时间戳,需要重启app端才行。rtmp地址拼接的代码是放在了DJI Pilot 2中么,我在java代码中未发现该功能。
我的oss用的是minio,最后一个参数 object-dir-prefix 不太明白该怎么填
Agent comment from sean in Zendesk ticket #73902:
推流地址拼接的时间戳是在前端的代码中,可以删除。
minio Pilot 目前还不支持,支持的是机场端的minio,object-dir-prefix 代表的是文件在存储桶中存放的目录位置。
°°°
修改飞机的推流和页面拉流的代码我已经修改完成了。
请问: 1、 minio Pilot 上传到minio 什么时候可以更新 2、因为上传问题,我想办法获取Pilot运行时日志,但是根据教程,发现并没有那个目录/Android/data/com.dji.industry.pilot/files/LOG/Logs/。有的是 /Android/data/com.dji.industry.pilot/files/LOG/CSDK/Logs,还有您们文档上说有jar库可以查看log日志,请问相应的jar库和使用教程在哪儿( ps : pilot 日志导出页面的“通过 JSBridge 获取日志。”超链接,指向的还是当前页面,不知道这个超链接的意义是啥) 3、使用上云api,规划航线的功能是在哪儿做,记得之前看过司空的页面,上面是可以直接在页面上规划航线的,现在的demo中似乎没有在线规划航线的能力,需要要遥控器上规划好,然后会自动同步到航线库么 4、还是希望您们能尽快搞好Pilot对minio的支持 谢谢!!
Agent comment from sean in Zendesk ticket #73902:
1、当前还无法告知具体的时间。
2、https://developer.dji.com/doc/cloud-api-tutorial/cn/feature-set/pilot-feature-set/pull-pilot-log.html,文档后续会进行修改,这个是准确的页面。
3、demo 没有做在线规划航线的功能,你可以通过司空2 或者遥控器规划航线,而且遥控器上规划的航线并不会自动同步,需要手动选择航线上传到第三方云。
4、感谢反馈,我们会尽快支持。
°°°
现在有个问题一直困扰着我。 我在阿里购买了oss并按照教程获取到了参数并写入到了java的application.yml中。 遥控器中的DJI Pilot 2(更新到最新版本了)。DJI Pilot 2中的”第三方云“也已经连上了。但是在DJI Pilot 2的"航线库“中去上传航线,总是提示 ”网络请求异常,请稍后重试“,我想通过遥控器编辑好航线后,上传到oss,然后在web端下发该条航线给飞机执行,现在这个流程就是跑步起来,请您协助帮忙解决
Agent comment from sean in Zendesk ticket #73902:
https://developer.dji.com/doc/cloud-api-tutorial/cn/feature-set/pilot-feature-set/pull-pilot-log.html
根据获取日志路径查找日志,找到该目录下MissionUpload 文件夹中的日志,其中会记录上传失败的原因。
°°°
上传航线和图片的错误日志如下:
====== Device Info ====== manufacture:DJI product:pm430 model:pm430 version:V03.00.01.76 release-keys android version:7.1.2 ======== App Info ======== app version:V5.1.1.7
[d][14:32:15.591]: --> GET http://139.196.42.69:6789/map/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/element-groups?is_distributed=true [d][14:32:15.591]: X-Request-ID: fa2364fb-c4e8-4c35-a011-a8432743e956 [d][14:32:15.591]: X-Client-OS: Android [d][14:32:15.595]: X-App-ID: pilot [d][14:32:15.595]: X-Client-Version: V5.1.1.7 [d][14:32:15.595]: X-Firmware-Version: 05.01.0100 [d][14:32:15.595]: X-Device-ID: 0-60-0 [d][14:32:15.595]: --> END GET [d][14:32:15.596]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][14:32:15.623]: --> GET http://139.196.42.69:6789/manage/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/devices/topologies [d][14:32:15.624]: X-Request-ID: 1284663c-0635-41e8-8268-05d2402d4c25 [d][14:32:15.624]: X-Client-OS: Android [d][14:32:15.625]: X-App-ID: pilot [d][14:32:15.626]: X-Client-Version: V5.1.1.7 [d][14:32:15.626]: X-Firmware-Version: 05.01.0100 [d][14:32:15.626]: X-Device-ID: 0-60-0 [d][14:32:15.626]: --> END GET [d][14:32:15.628]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][14:32:15.647]: --> POST http://139.196.42.69:6789/storage/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/sts [d][14:32:15.648]: Content-Length: 0 [d][14:32:15.648]: X-Request-ID: 3ad67705-402f-478f-87d8-de14bcc93abf [d][14:32:15.649]: X-Client-OS: Android [d][14:32:15.649]: X-App-ID: pilot [d][14:32:15.649]: X-Client-Version: V5.1.1.7 [d][14:32:15.649]: X-Firmware-Version: 05.01.0100 [d][14:32:15.650]: X-Device-ID: 0-60-0 [d][14:32:15.650]: --> END POST [d][14:32:15.652]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client
[d][15:06:50.583]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines?file_type=5&key=&favorited=false&order_by=update_time%20desc&page_size=9&page=1 [d][15:06:50.583]: X-Request-ID: c3bd8d0f-38c4-40d5-930b-a7b995c59e66 [d][15:06:50.583]: X-Client-OS: Android [d][15:06:50.583]: X-App-ID: pilot [d][15:06:50.583]: X-Client-Version: V5.1.1.7 [d][15:06:50.583]: X-Firmware-Version: 05.01.0100 [d][15:06:50.583]: X-Device-ID: 0-60-0 [d][15:06:50.583]: --> END GET [d][15:06:50.585]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:06:50.687]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines?file_type=5&key=&favorited=false&order_by=update_time%20desc&page_size=9&page=1 [d][15:06:50.687]: X-Request-ID: 23020b0a-476d-4ab8-ad1a-e923749e6177 [d][15:06:50.687]: X-Client-OS: Android [d][15:06:50.687]: X-App-ID: pilot [d][15:06:50.687]: X-Client-Version: V5.1.1.7 [d][15:06:50.687]: X-Firmware-Version: 05.01.0100 [d][15:06:50.687]: X-Device-ID: 0-60-0 [d][15:06:50.687]: --> END GET [d][15:06:50.688]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:06:56.119]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines/duplicate-names?name=zc [d][15:06:56.119]: X-Request-ID: 6f28da2b-3beb-4c3b-aada-8756e0892ab9 [d][15:06:56.119]: X-Client-OS: Android [d][15:06:56.119]: X-App-ID: pilot [d][15:06:56.119]: X-Client-Version: V5.1.1.7 [d][15:06:56.119]: X-Firmware-Version: 05.01.0100 [d][15:06:56.119]: X-Device-ID: 0-60-0 [d][15:06:56.119]: --> END GET [d][15:06:56.120]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:06:58.317]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines/duplicate-names?name=zc [d][15:06:58.317]: X-Request-ID: 6297b3d0-97c9-40ac-a952-b9c898066a86 [d][15:06:58.317]: X-Client-OS: Android [d][15:06:58.317]: X-App-ID: pilot [d][15:06:58.317]: X-Client-Version: V5.1.1.7 [d][15:06:58.317]: X-Firmware-Version: 05.01.0100 [d][15:06:58.317]: X-Device-ID: 0-60-0 [d][15:06:58.318]: --> END GET [d][15:06:58.320]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:06:59.240]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines?file_type=5&key=&favorited=false&order_by=update_time%20desc&page_size=9&page=1 [d][15:06:59.240]: X-Request-ID: 09b7cf39-1df3-44c9-8867-e396bcbc270a [d][15:06:59.240]: X-Client-OS: Android [d][15:06:59.240]: X-App-ID: pilot [d][15:06:59.240]: X-Client-Version: V5.1.1.7 [d][15:06:59.241]: X-Firmware-Version: 05.01.0100 [d][15:06:59.241]: X-Device-ID: 0-60-0 [d][15:06:59.241]: --> END GET [d][15:06:59.242]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:07:27.189]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:07:27.189]: Content-Type: application/json; charset=UTF-8 [d][15:07:27.189]: Content-Length: 243 [d][15:07:27.189]: X-Request-ID: 447604ff-6e1e-45e7-b916-88bf15e32f47 [d][15:07:27.189]: X-Client-OS: Android [d][15:07:27.189]: X-App-ID: pilot [d][15:07:27.190]: X-Client-Version: V5.1.1.7 [d][15:07:27.190]: X-Firmware-Version: 05.01.0100 [d][15:07:27.190]: X-Device-ID: 0-60-0 [d][15:07:27.190]: --> END POST [d][15:07:27.193]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:07:31.963]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:07:31.963]: Content-Type: application/json; charset=UTF-8 [d][15:07:31.963]: Content-Length: 78 [d][15:07:31.965]: X-Request-ID: d296fa1e-10bd-4c04-ac0e-6654a0e342cf [d][15:07:31.965]: X-Client-OS: Android [d][15:07:31.966]: X-App-ID: pilot [d][15:07:31.966]: X-Client-Version: V5.1.1.7 [d][15:07:31.966]: X-Firmware-Version: 05.01.0100 [d][15:07:31.966]: X-Device-ID: 0-60-0 [d][15:07:31.966]: --> END POST [d][15:07:31.969]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:07:31.969]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:07:31.977]: Content-Type: application/json; charset=UTF-8 [d][15:07:31.977]: Content-Length: 78 [d][15:07:31.977]: X-Request-ID: 29a15edb-9bca-4636-b26a-6fe888bb42c2 [d][15:07:31.977]: X-Client-OS: Android [d][15:07:31.978]: X-App-ID: pilot [d][15:07:31.978]: X-Client-Version: V5.1.1.7 [d][15:07:31.978]: X-Firmware-Version: 05.01.0100 [d][15:07:31.978]: X-Device-ID: 0-60-0 [d][15:07:31.978]: --> END POST [d][15:07:31.984]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:07:32.428]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:07:32.430]: Content-Type: application/json; charset=UTF-8 [d][15:07:32.430]: Content-Length: 297 [d][15:07:32.430]: X-Request-ID: 2acca360-cc40-4da4-8559-1e668abb4b0c [d][15:07:32.432]: X-Client-OS: Android [d][15:07:32.432]: X-App-ID: pilot [d][15:07:32.432]: X-Client-Version: V5.1.1.7 [d][15:07:32.432]: X-Firmware-Version: 05.01.0100 [d][15:07:32.432]: X-Device-ID: 0-60-0 [d][15:07:32.432]: --> END POST [d][15:07:32.437]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:07:46.211]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:07:46.212]: Content-Type: application/json; charset=UTF-8 [d][15:07:46.212]: Content-Length: 517 [d][15:07:46.212]: X-Request-ID: ef67c351-2007-4160-8b9b-4f51e55dc7cc [d][15:07:46.212]: X-Client-OS: Android [d][15:07:46.212]: X-App-ID: pilot [d][15:07:46.212]: X-Client-Version: V5.1.1.7 [d][15:07:46.212]: X-Firmware-Version: 05.01.0100 [d][15:07:46.212]: X-Device-ID: 0-60-0 [d][15:07:46.212]: --> END POST [d][15:07:46.213]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:11:42.445]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:11:42.445]: Content-Type: application/json; charset=UTF-8 [d][15:11:42.445]: Content-Length: 78 [d][15:11:42.445]: X-Request-ID: bc131fbd-715b-47b4-b94e-c5573e81ba61 [d][15:11:42.445]: X-Client-OS: Android [d][15:11:42.445]: X-App-ID: pilot [d][15:11:42.445]: X-Client-Version: V5.1.1.7 [d][15:11:42.445]: X-Firmware-Version: 05.01.0100 [d][15:11:42.445]: X-Device-ID: 0-60-0 [d][15:11:42.445]: --> END POST [d][15:11:42.447]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:11:42.454]: --> POST http://139.196.42.69:6789/media/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/files/tiny-fingerprints [d][15:11:42.454]: Content-Type: application/json; charset=UTF-8 [d][15:11:42.454]: Content-Length: 78 [d][15:11:42.454]: X-Request-ID: 1e247884-1f44-4d39-a8cc-49af347f00aa [d][15:11:42.454]: X-Client-OS: Android [d][15:11:42.454]: X-App-ID: pilot [d][15:11:42.454]: X-Client-Version: V5.1.1.7 [d][15:11:42.454]: X-Firmware-Version: 05.01.0100 [d][15:11:42.454]: X-Device-ID: 0-60-0 [d][15:11:42.454]: --> END POST [d][15:11:42.456]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:11:54.606]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines?file_type=5&key=&favorited=false&order_by=update_time%20desc&page_size=9&page=1 [d][15:11:54.606]: X-Request-ID: fa780be5-7aef-4e62-ab42-aca2f21dba3a [d][15:11:54.606]: X-Client-OS: Android [d][15:11:54.606]: X-App-ID: pilot [d][15:11:54.606]: X-Client-Version: V5.1.1.7 [d][15:11:54.606]: X-Firmware-Version: 05.01.0100 [d][15:11:54.606]: X-Device-ID: 0-60-0 [d][15:11:54.606]: --> END GET [d][15:11:54.608]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client [d][15:11:54.690]: --> GET http://139.196.42.69:6789/wayline/api/v1/workspaces/e3dea0f5-37f2-4d79-ae58-490af3228069/waylines?file_type=5&key=&favorited=false&order_by=update_time%20desc&page_size=9&page=1 [d][15:11:54.690]: X-Request-ID: a369e56b-5419-4b42-9f37-ce2bcfe1c5fa [d][15:11:54.690]: X-Client-OS: Android [d][15:11:54.690]: X-App-ID: pilot [d][15:11:54.690]: X-Client-Version: V5.1.1.7 [d][15:11:54.690]: X-Firmware-Version: 05.01.0100 [d][15:11:54.690]: X-Device-ID: 0-60-0 [d][15:11:54.691]: --> END GET [d][15:11:54.692]: <-- HTTP FAILED: java.net.UnknownServiceException: CLEARTEXT communication not enabled for client
Agent comment from sean in Zendesk ticket #73902:
V5.1.1.7 不支持使用http,请将服务配置成https,目前只支持GoDaddy的证书。或者将Pilot2 降级成V4的版本,才能继续使用http。
°°°
感谢回答上面的问题。下面又有问题了,哈哈
如上两张图片,在上云api的后端/waylines/file/upload接口中,会对上传的kmz文件中的waylines.wpml进行校验,
是不是我通过代码生成kmz时,可以忽略掉template.kml这个文件,只需要将waylines.wpml打包在kmz中,飞机就可以执行这个航线了
我购买了 ali oss 资源,并将参数写在了 application.yml 中,通过航线页面的上传按钮,可以成功上传kmz文件。

但是,在遥控器上却死活上传不了,下面是MissionUploader中的日志
一直报错,You have no right to access this object because of bucket acl.,但是我在页面上是可以成功上传的,之前在后台端也是出现这个错误,百度发现是少赋值了权限,权限已经加进去了。
请帮忙排查,谢谢!
oss上传到问题,我把所有权限全关闭了,解决了,应该是我配置的问题。感谢!
下面是新的问题,调用航线接口失败

我该如何在Pilot2 上排查为何信息没有返回这个问题呢
上面出现问题的代码位置是: com/dji/sample/component/mqtt/service/impl/MessageSenderServiceImpl.java:73 应该就是给Pilot2发送了消息,但是等待回信超时了吧,具体该如何排查呢 飞机版本:05.01.0100 Pilot2 app版本:v5.1.1.7 遥控器版本:05.01.0200
你好,在Pilot2上规划好了航线,在航点动作中添加了 ”相机变焦“,值为“102.02”,然后导出了kmz文件,解压后打开wpml,发现对应的xml中的值变成了“2425.5”,请问这是如何转化的,文档中并没有详细的表明

Agent comment from sean in Zendesk ticket #73902:
关于产品问题,Pilot2 中相机变焦动作参数值和实际变焦焦距的关系,可以直接联系邮箱【[email protected]】获得帮助。
°°°
