I am trying to connect my drone M210 RTK to DJI assistant 2, but when i connect my drone to the computer, nothing happen.
I have switched on the drone and put the button on the good configuration to connect to a computer by USB cable. I have also made both RTK and M210 firmware update using the remote controller and the DJI GO 4 App.
So here is my problem : How to do to make the M210 RTK available in Dji assistant 2 so i can enable the API.
A few more things to check for you:
Are you using the USB cable that came with the Aircraft?
Are you using DJI Assistant 2 v1.1.8+?
Is the switch on the back to the aircraft to the computer sign? (switch all the way to the left) page 41 in the manual
Did you try to reboot your computer. Assistant works with a background binary which establishes the communication with the aircraft, on rare occasions it freezes, you can kill the process but rebooting is easier.
Did you try re-pluging the USB cable after power on and switch to computer mode?
Can you access the RTK from assistant (usb switch on RTK)?
Related
I developed an application using DJI Windows SDK to control a Mavic 2 Pro. I manged to get all the data from the drone but when I tried to send commands to the drone through the VirtualRemoteController nothing happens
The set up is the following. I first send the command to auto-take off from my Windows app, which does it without out problems. Then, I give a position to move on my app. All the calculations are done as I expected but the drone continues hovering despite the values that I am sending are different of 0 and are on the range [-1,1].
I am getting an instance of the virtual remote controller as it follows:
VirtualRemoteController virtualController = DJISDKManager.Instance.VirtualRemoteController;
Then, I use the following command to send the movement that I want to execute:
virtualController.UpdateJoystickValue(throttle,roll,pitch,yaw);
throttle, roll, pitch and yaw are values between [-1,1]
This API is only supported for DJI aircraft that have a "WIFI-only" capability.
It is available for the Mavic Air for the Windows SDK.
The Mavic Pro supports Wifi but the Windows SDK does not support the Mavic Pro.
None of the Mavic 2 models support wifi.
I implemented Google assistant on Raspberry PI using Google Assistant Library.
And, I would like to connect my Raspberry PI to Google Home.
(Want to detect Raspberry PI on Google Home App)
1)
On google assistant, I could find Raspberry PI on device lists.
But it is not detectable on Google home app, even I had registered raspberry Pi in my google account.
2)
Google Assistant -> more settings -> Home control in Services tab.
When I clicked above path, I could see raspberry Pi with No room assigned status. So, I tried to change Nickname and Room for pi.
But the error message occured(Couldn't update the setting.Check your connection.)
Do I have to do something else for these things?
Is there any possible way for these?
Thanks
The integration between the Google Home and devices with the Google Assistant library is not very deep, such that the Google Home will not recognize any Raspberry Pis on the network.
Both devices are connected to your Google account, such that personal queries will return the same response on both devices.
Google Assistant SDK devices currently don't get a room assignment. There isn't any reason to put it in the HomeGraph as things like room control and remote execution are currently not supported.
I am trying to connect my sony xperia sp running on android 7.1 ( Lineage OS ) to my arduino uno using an OTG cable and the droidScript app. It worked perfectly the first time, it asked permission to open droidScript : I clicked on "OK" and checked "Use by default for this USB device".
But now I can't get it to work. When I reconnect my phone to the Uno nothing happen on my phone, droidScrip does not seem to recognize the device either and now when I try to connect my phone to my computer it does not work either ( but it's charging ).
I have tested all my cables and connected the arduino the same way using a different phone several times and it worked ( but didn't allow "Use by default for this USB device" as I suspect it comes from here ). Manually enable MTP through dev options does not work.
How can I remove that "Use by default for this USB device" option, and get the asking permission box back when I connect to my Uno ?
Try unistalling DroidScript and any other apps that might have talked to that USB device and then re-install DroidScript but don't start it up.
Plugin the OTG cable to the device (make sure you get it the right way round so that the OTG cable goes into the phone end) and then you should see the popup box for permissions.
I have recently started to have a deeper look into Wi-Fi Direct under Windows 10 (desktop version) and had a look into the API descriptions
from Microsoft => https://msdn.microsoft.com/en-us/library/windows/desktop/dn457945(v=vs.85).aspx
One of the described methods there (WFDStartOpenSession) states that a previous pairing through the "Windows Pairing experience" (WPS ?) is required.
So i started to play a little bit with the pairing stuff by using a Windows 10 (Build 1607, Desktop) together with an Android-based smartphone (version 6.0.1) and
made the following observations:
When i initiate the connection from my PC to the phone, it "basically" works i.e. the pairing dialog shows up on the phone's display and i can connect to it.
Although it works, it's not really stable in my opinion - on my side it works 1 out of 3 times.
After ~ 30 seconds, Windows disconnects from the phone (in the "Devices and printers" view) while the phone itself stays connected a little longer (then it also disconnects).
When i initiate the connection from my phone to the Windows PC, nothing happens - no message box, no pop-up window :-(
Has anybody else seen this or similiar behavior ?
I tried it with 2 different USB adapters, one with a RTL8723BU chipset from Realtek and the other one with a RT5572 chipset from Mediatek Ralink - both show
exactly the same behavior.
In addition, i noticed that the "Realtek Wireless Lan Utility" to control and configure the USB adapter is not working anymore in Windows 10 (1607) when switching
from client to Access Point mode. I think it's somehow related to ICS, missing hosted network support ... don't know yet.
However, actually you don't need the tool from Realtek as you can for example use the mobile hotspot feature of Windows 10 to share your internet connection with your devices.
But without the Realtek tool i have not found any possibility to switch WiFi channels - does anybody have the same problem ? is there are solution available for that ?
Thanks
I enabled debugging over bluetooth on my Moto 360
and enabled Android Wear app on my Nexus4.
Status displays target : disconnected
Forwarding the port from my computer shows the status host will be changed to connected, but the target status remains disconnected.
I toggled debug via the bluetooth switch which had no effect.
My phone is a Nexus 4. Is there a problem with my phone or the Moto 360?
I eventually managed to get it working. The issue seems to be related to having paired your device with an emulator first. Take a look at this post to see how I fixed it: http://melix.github.io/blog/2014/10/android-moto360.html
open the applications settings, search for the Android Wear application, then force stop it
clear its data and cache
Search for Google Play Services
Click on Manage space. Delete all data.
reboot your phone
reset your Moto 360
Pair watch with phone
Following the instructions from android.com https://developer.android.com/training/wearables/apps/bt-debugging.html to setup debugging and it should work now.
Done.
I tried it on a Sony z1.
It succeeded without any problems.
So, maybe it's not supported perfectly in Nexus 4.
If you have the same problem, I suggest using another device.
I fixed without factory reset with these steps
-Force stop android wear application and clear cache
-Disconnect emulator on android wear app
-Forget emulator on android wear app
-Connect your real device via bluetooth
-Open debugging over bluetooth
Make sure that debugging options are also active in android wear device
Run this commands in command window:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444