i am working on an app which requires finding out distance between ios devices using BT 4.0 LE and then pass a message to paired devices if they are in range. Is there any feasible solution for it??? Please help me out on this
You cous use RSSI as an indication of distance (more accurately Quality of the current RF condition with that device) and come up with your own mechanism to compuet the distance.
Related
I am in search of a method to get one meter accuracy between mobile devices, with no luck so far. I was looking at gps and location based geo-fencing as an option, but i don't think I am going to get a one meter accuracy. The other option is with Bluetooth, but not sure about that as well.
Can I build a react-native app that can see whether two mobile devices with the app installed to get an accuracy as little as one meter using gps or any other device specific sensors?
I am not sure about your requirement. But to answer your questions, yes you should be able to get 1-meter displacement measurement between 2 geo-location.
Maybe you can check how to achieve 1-meter accuracy in Android
There is other way, where you don't need 2 devices but you can find the distance of any object. That would require a phone with 2 cameras. If that fits the requirement of yours you can explore that area also.
I've been starting to read about the above and on BLE devices in general and trying to find the differences between those 2 frameworks. Is there something that the iBeacon API offers beside the option to use startMonitoringForRegion with CLBeaconRegion (which will basically "wake up" or notify the app that you're in range)?
To my understanding on iPhone 4S and up I can get a list of BLE devices and check their signal strength on iOS 6 sure, i't will not be as simple as the API for ranging but still, am I missing something?
Thanks
Yes, the CoreLocation APIs allow you to see iBeacon devices where CoreBluetooth does not. See my in depth discussion of this here: http://developer.radiusnetworks.com/2013/10/21/corebluetooth-doesnt-let-you-see-ibeacons.html
This may not matter if you want to roll your own Bluetooth LE devices that are fully visible by CoreBluetooth. But such devices are somewhat more complex and more power-hungry. iBeacons by contrast are transmit only and send a minimal amount of data.
The bottom line is that if you want your app to see standard iBeacons, CoreBluetooth simply will not do the job.
Has anyone found a good example of how to discover, connect, and disconnect BLE devices on Windows 8 using C/C++?
I'm not sure how to get a device handle to use with the "Bluetooth Low Energy Functions" API http://msdn.microsoft.com/en-us/library/windows/hardware/hh450825(v=vs.85).aspx
The Windows 8 Bluetooth GATT apis requires that the device be paired using the built-in UI and does not allow application to connect to an arbitrary Bluetooth LE device.
Source: MSDN Forum
MSDN has code samples(Windows 8+) on interfacing different BLE devices using either one the predefined Bluetooth SIG profiles (blood pressure, heart rate, thermometer) or the Texas Instruments CC2540 Mini development kit).
I don't know whether it is good or not but it looks quite comprehensive:
http://code.msdn.microsoft.com/windowsdesktop/Bluetooth-Generic-4f4ea968
I am trying to build this device which takes analogue input from the earth , converts them into electrical impulses which I wish to input into a android smartphone for data analysis. I initially thought about using the 3.5mm jack of the android device. Apparently Android does not support input through the 3.5mm jack. So I decided to use the USB cord as the input.
Now my question is will my android phone or tablet directly able to read the USB data, or has it to be fed through some microcontroller??
I'm not sure I'm understanding your question correctly, are trying to measure soil conductivity and find out if your plants need water? which is easy. Or are you trying to build a heart monitor? which is a bit more complex.
Anyway if you are interested in conductivity measurement with Android, you may want to have a look at this device, it is driver free and works on Android.
http://www.yoctopuce.com/EN/products/usb-sensors/yocto-knob
I believe V-Alarm is using them as well
http://www.valarm.net/blog/use-valarm-sensor-for-flood-warning-and-water-detection
I have a Samsung 700T ATIV Smart PC Pro tablet and I tried to access the different sensors using a basic Windows Store app template to test a few things out.
I used the samples from here: http://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh465294.aspx
So far I was able to get data from the Accelerometer and the Gyrometer.
The Inclinometer and the Compass however are not giving me any data. I can instantiate them just fine (they are not null) using Compass.GetDefault(); and Inclinometer.GetDefault();. The "reading" event handlers are not getting invoked though.
I tried the Inclinometer and Compass samples from the SDK as well. Same result, no readings.
The tablet should be up-to-date according to the Samsung Updater tool.
Is there any other way how I can check whether these sensors are enabled and working?
Any help is greatly appreciated.
Update 1:
Using the Sensor Diagnostic Tool from the Windows Driver Kit (Link) I was able to get some more information (it's located in prog.files\Windows Kits\8.0\Tools\).
I get readings for the X, Y and Z values from the compass sensor but "Magnetic North Degrees" is always VT_NULL. Since the Runtime API is only giving me HeadingMagneticNorth and HeadingTrueNorth instead of the raw values, this may be the root of the problem. Screenshot
Now since there seems to be a working compass, I wonder what the issue might be. Driver related?
For the inclinator, I am not getting any readings at all using the Sensor Diagnostic Tool. X, Y and Z values are VT_NULL. Screenshot
Any other Samsung Win8 tablet owners out there willing to test this out?
Both sensors work now and are providing the expected values.
The solution was to move to a different place in the house and rotate the tablet on each axis several times. This led to a re-calibration of the sensors.
It's possible that the sensor was being distracted by strong magnetic interference which prevented it from calibrating properly.
You might need to set the reporting interval property too.