I am trying to run a sample application for the Matrice 100 by using ROS on a raspberry Pi 2.I have the Pi connected to the drone via USB-TTL cable to the UART port on the drone. I have my laptop connected to the drone running DJI Assistant 2, and the controller and my iPhone connected wirelessly to the drone as well through the DJI Go App(v3.1.54). All are connected to the internet and logged into my respective developer account for DJI. However, when I run "roslaunch dji_sdk sdk.launch" I am returned an error saying the drone is not activated.
I have enable API access from DJI Assistant 2, I've made sure the the TX and RX pins are connected correctly, and I have changed my sdk.launch file to have the correct App ID and Key. Ive noticed in other posts that they say to edit the UserConfig.txt file for App ID, Key, and BaudRate; however, I could not locate this file on my Pi(it doesn't exist). Just the sdk.launch file which I correctly changed these settings to fit my application and drone.
STATUS/1 # init, L55: attempting to open device /dev/ttyUSB0 with baudrate 230400...
STATUS/1 # init, L65: ...serial started successfully.
STATUS/1 # parseDroneVersionInfo, L727: device Serial No. = 041DF31901
STATUS/1 # parseDroneVersionInfo, L729: Hardware = M100
STATUS/1 # parseDroneVersionInfo, L730: Firmware = 3.1.10.0
STATUS/1 # parseDroneVersionInfo, L733: Version CRC = 0xA6453AAC
STATUS/1 # initSubscriber, L778: Telemetry subscription mechanism is not supported on this platform!
STATUS/1 # initMFIO, L981: MFIO is not supported on this platform!
STATUS/1 # initHardSync, L1077: Hardware sync is not supported on this platform!
STATUS/1 # activate, L1313: version 0x3010A00
STATUS/1 # getErrorCodeMessage, L656: activate
STATUS/1 # getCMDSetActivationMSG, L705: NEW_DEVICE_ERROR
ERRORLOG/1 # activate, L1339: Failed to activate please retry SET 0x0 ID 0x1 code 0x3
ERRORLOG/1 # activate, L1346: Solutions for NEW_DEVICE_ERROR
*Double check your app_id and app_key in UserConfig.txt. Does is match with your DJI developer account?
*If this is a new device, you need to activate it through the App or DJI assistant 2 with internet
For different aircraft, the App and the version of DJI Assistant 2 might be different,
For A3, N3, M600/Pro and M100, please use DJI Go App
For DJI Assistant 2, it's available on the download tab of the product page
*If this device is previously activated with another app_id and app_key, you will need to reactivate it again
*A new device needs to be activated twice to fix the NEW_DEVICE_ERROR, so please try it twice.
[ERROR] [1560967071.851508645]: drone activation error
[ERROR] [1560967071.851845364]: Vehicle initialization failed
I checked the app_id and app_key in the sdk.launch file and they are the same as on my app on DJI website. Still unable to find file "UserConfig.txt". I don't see where to activate a device on the DJI Go App after it is already connected to the vehicle via the controller. For DJI Assistant 2, I cannot find the download tab or where/how to activate the drone for OSDK via my laptop as well. I don't believe it was activated with another app_id and key considering it is very new. So this is where Im stuck, and would like to run a sample app on the drone. Any ideas on how to fix this issue?
Welcome to the hell of DJI SDK world. The world of shitty API documentation and bug land.
Based on your error, the link is ok -> as you can see firmware version.
The error is new device error which means you either did not open remote. Or the remote is not connected to Go App or Go App not authorize the API .
Connect everything and power on everything accordinly.
turn on the drone and remote. connect the phone and on Go App.
Make sure that you can see drone position in map.
Once you saw the drone in map in Go App, run sdk.launch.
Once you do that, the Go App will pop up a MESSAGE saying api sth sth xxxxxxxxx , you have to press OK or Confirm. This is to solve the new device error
Then ctrl-C for the terminal and run sdk.laucnch again.
Also make sure that the sdk.lunch app id is the same account that are login in to the Go App
If first time not working, power cycle again and repeat this 2 step.
The sdk.launch needs to be run at least twice. I know its stupid but it is DJI and it is common.
Also do remember to set up udev rules for your /dev/serial/by-id/usbXXXX , then set the low latency mode for the serial. Those are all common error you are going to expect as well.
I had the same problem a few days ago and literally went through like 10-20 posts on Stack Overflow, DJI forums, etc. I contacted dev#dji.com and their suggested approach worked for me. Below is the email.
Bruce Cheung (DJI) 6 Sep, 11:22 CST
Dear Chris,
Thank you for contacting DJI.
If have the same error log as before, it doesn't matter the new device
is activated. Suggest that you can delete the catkin_ws folder, then
git clone DJI OSDK-ROS source code, modify dji_sdk_node.cpp, and do
catkin_make. You can provide a new log document if there is any
problem again. Good luck with your project.
Thank you for your understanding and support, hope you have a nice
day.
Best Regards, DJI SDK Support Team
My reply after it worked:
Thank you, I took your advice and it worked.
I deleted the folders, did catkin_make. This time I made a 2nd Onboard
SDK project at developer.dji.com and used that one instead. My first
one had been activated on the same computer but through the Linux (not
ROS sdk). Not sure if that makes a difference. It works now.
Chris
I'm really not sure why removing and then uninstalling worked, as I had literally just added a new install the day or two before. But guess it worked. I also made a 2nd API key but according to DJI that wasn't the reason why it worked.
I'm working on a WPF/C# application who are exposing commands to be called called by magnet link.
Our application create registry key when msi in installed but, when we use the magnet link, we have a security message each time, even if we check allow access.
Does someone know how we can do to not have this message or at least, just the first time?
We can have dev solution, registry entry, gpo, ...
thanks by advance for any help.
Regards
I recently installed apricity-os and when trying to use pacman, I was prompted with an error message saying that I didn't have the apricity-core database .I wished to know of one of you could help me find it .
Apricity OS support is ended, as reported here https://apricity-os.github.io/.
I have setup bugzilla 3.6.4 on my centOs 5 based on the instruction provided http://www.bugzilla.org/docs/3.6/en/html/installation.html . I chose mod_perl approach to execute it. I see my bugzilla running , when I go to create a new account , i get token url through mail. But once I fill the form and submit , 500 error occurs and same happens with forgot password .
No clue why it is happening .
Help is really really appreciated .
Thanks a ton in advance
-DD
If you get an 500 error, check out your web servers log. It usually contains a more detailed error message compared to the plain message that the browser displays. If I remember it correctly CentOS puts logs into /var/log/httpd but you might have defined another path inside your httpd.conf or your virtual server files.
For some reason on my installations using Ubuntu Server, Bugzilla 3.6.4 never worked well for me.
I so recomend the Bugzilla 4.0 upgrade. Installation Guide
I created an installer for it, installed .NET Framework 4 on target machine. However, my application didn't work. I've got a message, that is has stopped working and offered to send a report.
Windows log:
The name of the offending module: KERNELBASE.dll, version: 6.1.7600.16385
Exception Code: 0xe0434352
Offset error: 0x00009617
This could be many things. Ensure the correct .net runtimes are installed. Insure permissions are correct on all files. Did you forget to deploy some dependencies? Check the fusion log. Check the system log.
Do you have logging in your application? How far does the app get before crashing? We need LOTs of info before we can even start to help.
Insufficient information to give a meaningful answer.
Check your Windows event log log (administrative tools | event viewer | windows logs | application) and find the real error.