Windows 10 Swift Pair (BLE) - windows

At the moment, I am developing an Android-based BLE peripheral and I'm hoping to integrate Windows 10 Swift Pair, following this documentation: Microsoft Swift Pair
I have ensured that my Windows version is above 1803 and have ensured that the "Show notifications to connect using Swift Pair" box is checked.
I followed the payload structure defined in the documentation.
I double confirmed the BLE advertise data by using an Android Test App and a Windows Test App (On the same PC I'm getting this to work). I'm sure that I'm advertising the correct payload.
Unfortunately, the notification of swift pairing did not pop up and I'm at loss at what I'm missing. It will be great if anyone could tell me what's wrong!
Updates 17 Dec 2020
The notifications are showing now. The only change I made was to increase the txpower of the Advertisement.
Currently, I'm facing another issue. Pairing doesn't work on all PC. I tested with 2 PC (that's every PC in my inventory). 1 work and 1 doesn't.
Working PC: BLE 5.0 (LMP 9.256) |
Not Working PC: BLE 5.1 (LMP 10.256)
Any idea why this is happening?

Related

DJI Windows sample code - USB connection - cannot view FPV

Using VS 2019 and Windows SDK 0.3.1 I cloned and executed the SDK sample code correctly. Trying to connect to the smart controller of Mavic 2 doesn't work.
FPV page says 'turn work mode green first'. I guess there is no outgoing serial communication from the sample code towards controller.
Connection with Assistant 2 Mavic does work normal.
Device manager shows under Com and LPT: CDC Serial (Interface 1) COM4 and under USB devices: ADB interface.
Component handler doesn't communicate either with the controller.
I am clearly missing something in setting up correctly the USB connection between the sample code and controller.
Thx
I think I had a similar issue recently Martin. I was trying to follow the DJI/Windows SDK tutorials and got the DJISdkManager to register but could not invoke the FPV on my Mavic 2 Pro.
I ended up following the guidelines here
Turns out I think I had the wrong version of DJI Assistant 2 installed (legacy from having a Mavic 1) I updated and used the Zadig program to install a WinUSB driver for the remote controller. After that, I got the FPV working handily enough.
This might help.
Edit: Link to the correct version of the software I had to install.
Just got the reply from DJI dev.
Windows SDK is not compatible with the smart controller, only with regular controller.

DJI Windows SDK Sample Code: Cannot view FPV mode on Mavic 2 Pro

I am using the example code provided by DJI for Windows SDK to connect with a Mavic 2 Pro. I can receive the name of the drone, subscribe to update on velocities and see them. However, I cannot get any video when I click on the FPV nor use the playback, where workmode turns on green but then there is a time out when I click on reload:
LaunchFileDataTask get files:REQUEST_TIMEOUT: Switch Mode or try again
I am using:
Visual Studio Professional 2017 Version 15.9.5
Latest version of the drone and radio controller.
Latest version of Windows SDK
Windows Enterprise Version 1803
I have installed all the drivers and done the Guidance to Connect with Mavic 2 Pro. I have checked on Device Manager when the controller is connected and I see the following devices:
Vision (Interface 3)
DJI USB Virtual COM
Also, I have uninstall and install all DJI's program, and drivers.
Solution
So, after several attempts and different approaches I solved the problem. I figure out that all the drivers provided on DJI Assist 2 for Mavic and DJI Simulator do not comply with the requirements to get the images from the Mavic. So the solution was to use zadig. Once on the program and the controller on and plug to the computer, select Options->List all devices. Now, it should be visible the driver libusb, selected and then click on replace driver.
Lol I was doing beta test for DJI WSDK. didn`t encounter this. The only problem is the limited selection of drone.
Here is a checklist, cross them out 1 by 1 to rule out the issue.
USB Authority Configuration in UWP
Connection sequence
Make sure that before connecting using your cable, your P4P V2.0 remote controller is off.
Connect the remote controller to your computer using Micro-USB cable.
Turn on your remote controller.
Make sure you have not open the DJI software like DJI Assistant 2.
DJI Windows SDK Applications are not able to communicate with the aircrafts at the same time.
3 Make sure that you have installed DJI Assistant 2 and have enabled all the driver intallation while installing DJI Assistant 2.
4 WinUSB Driver
Your error seems is a connection issue. But once you pass that there are a few more thing you have to check
make sure you have FFMpeg dlls in the directory
I`ll add more if I remember more. Currently, this is all I can think of

Is scanning BLE devices in Windows 10 under Cordova possible?

I wrote an app with cordova (8.1.2) to communicate with a BLE (blutooth low energy) device. I got it running on Android, and I managed to build a Windows 10 version too.
But under Windows 10 no device will be found.
If the evothings.ble.startScan function is called, no error callback function is called, but unfortunately the onDeviceFound callback is never called too.
If I try to connect to my device via the Windows 10 Control Center the device is found and I also managed to connect to it.
The answerable question is: Is scanning for BLE devices supported by the evothings cordova plugin under Windows 10? If so, what do I have to do to get it running?
Plugin source: https://github.com/evothings/cordova-ble
In the evothings website (https://evothings.com/evothings-studio-2-2-0-released/) there is a broken link to a forum, so I cannot ask this question there.

Parse SDK Windows 8.1 : Device not getting registered on Parse.com portal

I followed the documentation(https://parse.com/docs/dotnet/guide#push-notifications-setting-up-push) by Parse for sending Push to Windows 8.1 device. But, I am not able to get through the first step ie. "Installation". As per the documentation I followed , the channel should get registered instantly. I have enabled "Toast capable" within the Package.appxmanifest file in my Windows 8.1 Universal App(C#).
I have also authenticated the App by adding the Package Security Identifier and the Client Secret to the Parse.com Windows Push Credentials settings. But still no success. Can anyone tell me if I am missing anything or if Parse SDK is supported for Universal Windows 8.1 C# App.
I previously had Parse working for WP8 as per instructions here. So this is to say it is definitely doable, follow those steps there to see if you missed any steps.
Caveat
We are using Cordova, but I had to end up doing this part natively. It was working in December 2015 but mysteriously this year we had issues with Parse on all 3 device platforms (iOS, Android, WP8). I'm still spending time trying to figure out why WP8 just doesn't work now, can't even get the device to register to a channel anymore...

Can deploy to Windows phone on one machine but not another?

I have been developing a Windows phone app on my lunch breaks at work and spare time at home. The project is stored in my Dropbox so it's the same on both pcs. At work when I debug/deploy to the device everything is fine and dandy. At home however I get the following.
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Now in both cases I'm using the same version of the SDK and of VS on the same Microsoft account on the same phone on the same project. But it doesn't work.
I have reinstall the SDK twice now to no avail.
When I run the device registration I get the following message.
Unable to connect to a phone. Make sure the Windows Phone IP over USB transport service is running
I'm not sure what I'm doing wrong here, has anyone run into this before? Any ideas of a fix for the issue?
Update:
I have uninstalled 2013 r4 and installed 2015. I have done a hard reset on my phone. I have run Windows Update and I'm up to date. I have tried making brand new projects as some of the posts suggest, to no avail. Same issue occurs, except now my emulators get:
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '184901A8-DC44-4CED-869E-DC7733D048D6'
I'm guessing the next step is reinstalling Windows, I think I'll just wait till Windows 10 comes out.
Possible Fixes:
1.Try reconnecting your phone.
2. try re registering your phone as developer device
3. try this fix
https://dev.windowsphone.com/en-US/OEM/docs/Phone_Testing/Configuring_IP_over_USB
Testing apps on windows phones can be frustrating. One common problem I get is the need to reinstall drivers for the phone. I think this may be your problem.
The other problem similar to this I've encountered, was when registering for windows phone not using the correct version on that pc for 8.0 or 8.1.
Aside from this, there is a list with links provided that may help you. Let us know how you get on.
This link Problems and fixes when registering a Windows Phone 8 device to deploy/debug applications covers the major issues, some mentioned by Akash.
The following is a summary of the points discussed in the above link:
Windows Phone IP Over USB Transport(IpOverUsbSvc) service is running
Phone name is already in use by this account
Too many phones have already been registered with your account
Device lockscreen has to be unlocked (and it is unlocked)
Can’t find any devices
Point 5 is also addressed in this answer https://stackoverflow.com/a/30303946/3956566.
Update after comment
The other thing that you may need to do is:
1. make sure you have all your updates in Windows.
2. Make sure you have all VS updates.
3. reinstall VS.
4. Reinstall any .net framework packages for VS.
The first two are the most likely things.
If worse comes to worse, to reinstall windows.
I have needed to do all of the above at one time or another to fix various issues. Painful, yes.
And don't forget to reboot your machine.
Let me know if this works. There MUST be a solution.
I know what you mean about the phone appearing in explorer, update anyway, won't hurt to reinstall them.

Resources