M300 osdk 口 通讯问题
Completed你好,
我使用树莓派的UART 接口, 通过usb breakout板链接M300上方的osdk接口,总共使用了三根线,RX,TX和GND。改写适当的参数后,在尝试跑sample code:
sudo ./dji_sdk_demo_linux
在成功获取了飞机的基本信息后,出现了下面的警告信息,并且卡在“”Updating dji sdk policy file...“”这一步无限循环,请问可能是什么原因呢?(序列号我人工打码了)
[0.001][core]-[Info]-[DjiCore_Init:92) Payload SDK Version : V3.1.0-beta.0-build.1509
[1.233][utils]-[Info]-[DjiSdkVersionAck_Parse:183) Identify aircraft serial number = xxxxxxxx, Firmware = 3.4.19.2
[1.260][adapter]-[Info]-[DjiAccessAdapter_Init:154) Identify aircraft series is Matrice 300 Series
[1.260][adapter]-[Info]-[DjiAccessAdapter_Init:171) Identify mount position type is Extension Port Type
[1.284][adapter]-[Info]-[DjiAccessAdapter_Init:242) Now auto reconfigure baudrate from 230400 to 921600
[2.810][adapter]-[Info]-[DjiAccessAdapter_Init:154) Identify aircraft series is Matrice 300 Series
[2.810][adapter]-[Info]-[DjiAccessAdapter_Init:171) Identify mount position type is Extension Port Type
[3.993][core]-[Info]-[DjiIdentityVerify_UpdatePolicy:415) Updating dji sdk policy file...
[4.993][core]-[Info]-[DjiIdentityVerify_UpdatePolicy:415) Updating dji sdk policy file...
[4.994][linker]-[Warn]-[DjiCommand_SendAsyncHandle:860) Command async send retry: index = 0, retryTimes = 65535, cmdSet = 60, cmdId = 64
[5.994][core]-[Info]-[DjiIdentityVerify_UpdatePolicy:415) Updating dji sdk policy file...
[5.995][linker]-[Warn]-[DjiCommand_SendAsyncHandle:860) Command async send retry: index = 0, retryTimes = 65534, cmdSet = 60, cmdId = 64
[6.994][core]-[Info]-[DjiIdentityVerify_UpdatePolicy:415) Updating dji sdk policy file...
[6.997][linker]-[Warn]-[DjiCommand_SendAsyncHandle:860) Command async send retry: index = 0, retryTimes = 65533, cmdSet = 60, cmdId = 64
[7.994][core]-[Info]-[DjiIdentityVerify_UpdatePolicy:415) Updating dji sdk policy file...
-
这个报错是USB通信异常,M300 OSDK端口分为串口通信和USB通信,具体可以参考文档: PSDK 3.0版本OSDK(OSDK 5.0)部分相关介绍与指引 https://sdk-forum.dji.net/hc/zh-cn/articles/4408437830041 -
文章中有关于M300只使用串口的方式和说明,可以参考: ![](https://djisdksupport.zendesk.com/attachments/token/3UdjWAubNBZ7oqcHQE6lbm7RJ/?name=image.png)
Please sign in to leave a comment.
Comments
4 comments