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.
Related
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?
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.
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 anyone tell me whether or not Qt supports the windows Bluetooth API?
If so could you please share some information on how to use it?
The answer to this question has changed a bit since the last response was given. Qt version 5.2 implemented a Bluetooth API for Linux/BlueZ and BlackBerry devices. Qt 5.3 includes Bluetooth support for Android. Linux devices can connect with RFCOMM or L2CAP protocols. Android and Blackberry only have RFCOMM.
Bluetooth on Windows is still not supported, but that fact is hard to find. Currently, if you create a QBluetoothSocket on Windows and tell it to connect to an address, it fails silently even though there is a built-in error-reporting mechanism. If you use the QBluetoothLocalDevice interface to retrieve devices, you get back an empty list. Although the class documentations don't mention the fact, the Bluetooth Overview clarifies that
Currently the API is supported on Android, BlackBerry 10 and Linux (Bluez 4.x).
Starting from Qt 5.11, Qt documentation says:
Despite there not being a Win32 port yet, the WinRT backend is
automatically used if the win32 target platform supports the required
WinRT APIs. Minimal requirement is Windows 10 version 1507 with
slightly improved service discovery since Windows 10 version 1607.
Therefore Windows 7 and 8.x targets are excluded.
Bluetooth Chat Example tested successfully using following setup:
Qt 5.11.1Win10 Qt Kit MSVC2017 64 bit.
As January 2020 documentation, Qt 5.14 officially supports "Classic Bluetooth" for win32 builds.
However, it doesn't seem complete, here mentions a restriction about finding devices:
...it is only possible to find devices that have been previously paired through Windows Settings
Has anyone try to debug their app to wp7 device througn vs2010pro?
The phone is registered.. I already reinstall my vs2010pro and windows developer tool, but still the error persists. Windows 7 Ent 64bit.
Here are some points to check (to summarize):
Device should be dev-unlocked
Device should have the screen unlocked at the time of debugging
Device should not have apps installed over the limit (applied to VS-installed apps)
Zune should be in full-sync relationship with the device (not guest)
If Zune is not running, you need to run the WP Connect Tool
If the problem persists, try restarting the device and connecting it again.
Also, is the phone officially registered?
Are you able to deploy your project to the device? (assuming only live debugging is failing)
I have faced this problem at work, and when I de-register the device, and register again, it usually works for me.
Double check that the device is definelty reported as unlocked in the app hub.
Check that the device is on, connected, Zune is running and you hav unlocked the device since connecting to Zune.