-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Odroid XU4 +ROS + Matrice 100_Error 449 #122
Comments
Did you add your user to the |
@rohitsantdji, I have checked the groups rights. Some more photos for troubleshooting. To verify the wiring of Odroid GPIO I noticed for the new firmware of the Remote Controller, we do not have the option to turn off the IOC. The settings only have the multiple flight modes. I have also tried toggling the F mode around, and leaving it on F mode before =| |
The odroid xu4 GPIO use 1.8V level, while most of the other external uses 3.3V. So you need a level shift converter to connect them. |
Close this issue now. If you still have more issues related to DJI SDK, please help to fill in this form: |
… to develop * commit 'f932a37bd46b7f7831893eb699f6d442041967dd': fix:fix wp2.0 cmake issues
Hey guys, need the community advice on this matter. Been cracking my skull over this.
Trying to link my Odroid XU4 (Ubuntu 14.04 + Onboard SDK ROS 3.2) with my Matrice 100. Received the following message:
![inkedcapture1_li](https://cloud.githubusercontent.com/assets/28199120/25572526/c75c0ade-2df0-11e7-84db-f75f05448623.jpg)
I have read through issues #77, #104 and config my setup according:
Latest firmware for DJI Go app, Remote control, Matrice 100, Onboard-SDJ-ROS 3.2
All connections are made;
DJI GO app connected to Remote Controller
Matrice 100 connected to Odroid GPIO with careful emphasis on Tx and Rx matching
Matrice 100 connected to Laptop via USB
Running DJI Assistant 2, with API checked
Running SSH connection to my Odroid (with internet connection)
Configured the sdk_manifold.launch file:
Updated App ID and Key
Serial set to
ttySAC0
Baud rate unchanged at 230400
Toggled the F mode around, kept it and ran it in F mode
My initial thought is that I got the serial_name wrong. So I experimented with all the available ttySAC* available from
dmseg | grep tty*
Any recommendations or suggestions?
The text was updated successfully, but these errors were encountered: