I know that windows phone 7 has 5 sensors: A-GPS, Accelerometer, Compass, Light, Proximity and microphone, WiFi, Bluetooth, Camera, etc.
I can access GPS, Accelerometer, Microphone and Camera. But I cannot find APIs for accessing the raw data of compass, light, proximity, WiFi and Bluetooth.
What I am in need now is to scan the WiFi frequently and get the nearly-by access points IDs. Is that possible?
Thanks.
You haven't found the API for these functions because they aren't exposed in the SDK at the moment.
Compass was pulled before CTP for being just slightly below quality expectations, light and proximity aren't exposed at the moment, neither is bluetooth via the 3rd Party SDK.
Data is accessible via Wifi and Wifi contributes to the Location service. However you can't access low level wifi network data at the moment.
Related
In the context of a research project I'm planning to develop a desktop application to operate with my DJI Mavic Pro 2 (or similar drones).
So, my question is: Is there anyway I can control the DJI drone from a desktop application without using the controller? For example, I would like to get the video stream in realtime on desktop app as well as automatically planning the mission for the drone.
Unfortunately, the Windows SDK only provides few APIs compared to the Mobile SDK.
For most of the other heavy/potential killing drones, e.g mavic 2 pro or above. it need remote on so that you can fly.
If you really need to do so, How about tello? it is a small DJI drone that can allows you to control it. Moreover, it allows you to get video and imu feed from its API. There is plenty of open-source code for it.
The controller is required.
Some of the older drones had a wifi option but the newer ones user controllers at the connection.
I am trying to develop basic applications on my moto 360 (synchronizing messages and notifications, sending sensors data..) connected with a mobile phone. My problem is that I wish not to install android wear application on the mobile phone and I would like to know if there is a way not to do so.
Thank you for your help !
It's probably possible, but it's actively discouraged. From the Wear communication API docs:
Warning: Because these APIs are designed for communication between handhelds and wearables, these are the only APIs you should use to set up communication between these devices. For instance, don't try to open low-level sockets to create a communication channel.
Given that a Wear device runs (nearly) full Android, I expect it's possible to roll your own communications layer using low-level Bluetooth, Wifi, or some such. But the correct answer is "Don't".
I will try to be as specific as possible here :
You mentioned that you don't want to install the Android Wear application on you mobile. If this is the case, then your watch still needs to be paired with some phone if its running AW < 2 [which Moto 360 is, for now]. Without this, you will not be able to get the watch out of factory mode (unless you flash it with an already paired watch' data). Even then, it will not communicate with the phone since it's not paired with it.
If instead, your question was about opening up a low-level bluetooth socket with a mobile phone, or any bluetooth enabled device in general (atleast those that implement RFCOMM functionality), then yes, this is still possible, as long as you can sideload apps to your watch. In order to do this, you have to implement a BluetoothServerSocket or a BluetoothSocket, depending if you want your watch to be a client or a server. In either case, you can open a two-way communication socket, with throughput upto 50KBps, in real world scenarios.
As far as I understand eddybeacon (just released by Google) is effectively a new 'operating system' for Bluetooth 4.0 Low energy devices (iBeacons). I have been experimenting with iBeacons for sometime now and want to try out a few things with eddybeacon. Has anyone had a go with it yet? I've read a few sites and they say it can be installed to some devices... Can anyone share how to do this?
If you want to start out by playing with Eddystone, you have a couple of options:
You can use a software transmitter. Just download my free Locate App in the Google Play store which will both act as an Eddystone transmitter and decode other Eddystone-compatible beacons in the vicinity. Google also has posted an Android app that can transmit the Eddystone-UID frame here, but you have to compile it yourself.
You can get a few hardware beacons for testing with a Developer Kit from Radius Networks (my company) here.
Once you have a transmitter, you can try writing some software to work with it. Here's a tutorial I wrote on how to build a basic Eddystone-capable Android app.
One other thing that might be useful is an Eddystone detector tool. You can use the free Android Locate app to detect and decode all of the frames transmitted by Eddystone.
So:
Eddystone is a specification for Bluetooth Smart (usually just called BLE) devices to behave like beacons — it defines the Bluetooth frames and content they need to broadcast to be seen as beacons.
iBeacon is not a generic term. iBeacon is actually Apple's specification for Bluetooth beacons. Eddystone and iBeacon are both examples of beacon specifications for BLE devices.
There are a few ways to get started with Eddystone beacons.
a. A number of hardware manufacturers sell developer kits that will let you get started with Eddystone beacons right away, and there is plenty of example software out, either from those vendors, or from the google pages on GitHub — github.com/google/eddystone and github.com/google/beacon-platform.
b. Some people have had good luck with Arduinos and Raspberry Pis. You can see an Arduino example here (Note: I have no idea how well that project works, I've just seen it used a few times.)
Can I use Serial Port Profile (SPP) to communicate with iOS devices over Bluetooth Low Energy (v4.0) without the need for MFi Chip?
If you're designing something from scratch (rather than trying to interface to an existing SPP-enabled device), there is a possible solution.
Laird Technologies make a Bluetooth Low Energy Module (BL600), which can be loaded with a virtual serial port application. This creates a service which is similar to the SPP; at the remote end it can just be treated as a plain serial port (albeit rather low speed). You could roll your own service to do something similar on other devices.
It's not the most elegant solution, but seems to work okay, and far easier than trying to get MFi certification.
If you cannot control the peripheral's protocol choice:
The Serial Port Profile (SPP) is still supported by Bluetooth 4.0. However, Bluetooth 4.0 Low Energy uses different pysical and link layer protocols that are not backwards compatible with older Bluetooth standards. Current iOS and Android devices use "dual mode" interfaces that support the backward compatible part of BT 4.0 and the Low Energy standard.
Bluetooth 4.0 Low Energy does not support SPP whereas regular Bluetooth 4.0 does!
I found a Cordova/Phonegap Plugin on GitHub that might serve as a source of inspiration for you. They advertise to support SPP on iOS and Android alike.
If you are in control of the peripheral, i.e. you implement the peripheral's software:
Bluetooth 4.0 Low Energy communication makes use of the Generic ATTribute Protocol. Based on GATT there exist a number of profiles but no serial port profile.
The good news is that implementing your own proprietary serial port profile on iOS, Android and your device is fairly simple. The API instructions for your BTLE module/SoC should provide some examples for existing profiles.
As soon as you see how simple implementing your own profile is, you will probably choose to go for a more use case specific profile which will save you lots of power on your (battery powered?) peripheral.
Just to clear up John Parsons comment from Feb 16th - the BL600 is definitely not discontinued whatsoever.
vSP works well for a low level, low throughput data connectivity using BLE for iOS devices, as well as Android. Video showing the solution working to an iPad are at this link and full source code is available for the iOS application as well http://www.lairdtech.com/Support-Center/Technical-Library/Videos/VSP-Bridge-Command/#.UwYvzGJ_s1w
There are no MFi requirements for BLE connectivity on iOS.
MFi is only relevant to Classic Bluetooth data connections to / from iOS devices, where you need to use Apple's iAP protocol, be a MFi licensee, use an external Apple Authentication IC and pay a royalty to Apple.
NO,you can't. BLE not support SPP.
No, you can't. In general, it's important to remember that any Bluetooth Classic profile isn't necessarily applicable for Bluetooth Low Energy. With BLE however, you can easily create your own custom service/profile, specially tailored towards your particular application. As far as I know, all BLE communication with iOS is currently allowed without participating in the MFi. You can also take a look at this page for further information on SPP and BLE.
I'm searching for SPP for iOS myself and found a German supplier, lintech.de, that has products for "Bluetooth meets Apple" claiming to support/emulate SSP, apparently using their own embedded software layer combined with iAP. "BlueMFI software communicate with APPLE devices using the iAP (iPod Accessory Protocol) and manage the data communication with the Apple authentication chip...BlueMFI software is designed to run on a variety of hardware platforms (Bluetooth modules), and interested users can obtain the relevant evaluation kits. LinTech’s Bluetooth modules with BlueMFI software not only support the APPLE iAP protocol via Bluetooth, but they are also able to communicate with standard Bluetooth devices." Haven't tried this yet, just exploring and sharing.
I won't say SPP is directly supported under iOS 7, Apple says no. Won't argue :)
But...
I use connectblue modules OBS421 and OBS425 on a data collection project.
BLE modules have SPP profile enabled and I transmit data from my sensors to the iOS devices using BTLE module in SPP mode.
Works pretty fine under iOS 6 and 7
That said, I was having trouble with MFi bluetooth devices under iPhone 5S, that's why I moved to BTLE.
Drawback with BTLE, it's limited to 20 bytes at a time.
I had to adjust hardware and software, but was easy.
You have programmable chips such as Bluegiga BL112 that are doing the job. It is the cable replacement code.
I'm integrating it actually for both iOS and Android 4.3. It works at least on the demo board.
I am new to WP7 development and working on a project (wp7 app) where I need to get ONLY gravity force using accleration API (I think I can do some thing using Motion Api) but It requires window phone to support Compass and Gyroscope as well.So Is there any way to separate gravity from accleration or only get gravity forces on X, Y and Z axis using only accelration (as I want my app to run on wp devices where there is no Compass and Gyroscope).
Also in android there are some methods likes
Linear Acceleration
Low pass / high pass filters etc
Do we have such kind of support in Wp7?
Thanks
The phone itself doesn't know what force is caused by acceleration and what by gravity. You would need information from other sensors to be able to do the math to separate the values. That's what Motion API is for.
So, your only chance is to use Motion API. It will fall gracefully if the device doesn't have the necessary sensors, but will work if there are:
The Motion API used by this sample requires all of the supported
Windows Phone sensors, and therefore these sample applications will
fail gracefully but will not work properly on devices without the
necessary sensors or on the device emulator.
There was a post on the Windows Phone Team blog about implementing a High pass / low pass filter on the accelerometer data. I've used this with fairly good results.