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.
Related
I am using the Kinect 2 with the newest available SDK version 2.0. Everything works except IR, tested it with both SDK infrared demo example and Kinect Studio, both result in a black screen. I also looked at the code and capturing Kinect IR frames does not result in any errors, it just consists of all minimum values.
This is quite weird, as I thought IR was used to calculate depth and I can successfully read depth information. Also, I checked (with my cellphone camera) that the IR emitter is turned on and off correctly, just data is not received correctly for some reason.
After encountering the problem I made a fresh install on another computer, as I suspected I had broken my system somehow. I got exactly the same results after installing Kinect SDK. Everything except infrared works.
Has anyone seen this kind of behaviour before?
check this out
https://social.msdn.microsoft.com/Forums/en-US/70dcceb7-8d2f-485f-b3e9-f2d4b399fbe7/kinect-v2-infrared-not-working?forum=kinectv2sdk
try updating graphics card drivers
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 used until yesterday afternoon a Kinect for XBOX 360 on my computer, a MacBook Pro 15" Late 2011, whose specifications are available here. I use Windows 7 (natively installed, without using virtual machines). The version of the SDK I had installed was 1.0.
All of a sudden, from today the Kinect no longer worked. Initially I thought it was some error in my code, but I noticed that the program remained stuck at the beginning, when I called the method KinectSensor.Start().
I started looking for information on the internet. I read about a solution obtained by reinstalling the drivers. It did not work, and then I tried to install version 1.6 of the SDK. Unfortunately, even that did not work.
I've seen at this stage, there might be compatibility issues with certain USB host controllers, such as the Intel 5 Series/3400 Series Chipset USB host controller. In my case, however, there should be no problems (because there were not ever been up to yesterday):
To check if the problem was really due to the sensor, and not to my application, I run one of the test applications provided with the SDK, called Kinect Explorer. However, I encountered the same problem with this test application. After waiting about one minute, when the Kinect Explorer starts I cannot see neither the color stream, nor the depth stream, nor information about skeleton. The only thing I can do is move the Kinect up and down, changing the angle of the neck. Even the microphone array seems to work properly.
I read two interesting posts about this kind of problem: this and this, which have not been answered.
In the first of these two links, the user who reports the problem says that the hardware has been compromised. I thought the same thing myself until I started again Kinect Explore, initially with the sensor unplugged. Once started this program, I plug-in the cable, and I noticed that Kinect Explorer has marked the Kinect sensor as Connected. After a short initialization phase, I again see the color stream, while the depth stream showed an image of uniform color (green-gray):
This situation lasted a few seconds, after which the image is locked and the question came up. Also, sometimes the FPS value drops from 30 to 29.
I am able to reproduce this latter situation only after keeping the Kinect unplugged for a while (10 minutes are sufficient).
How can I solve this strange and terrible problem? Is it possible to restore the Kinect sensor, and make it works again? Or do I have to conclude that the sensor is irretrievably broken?
I tried using "Kinect for Windows" on my Mac. Environment set-up seems to have gone well, but something seems being wrong. When I start some samples such as
OpenNI-Bin-Dev-MacOSX-v1.5.4.0/Samples/Bin/x64-Release/Sample-NiSimpleViewer
or others, the sample application start and seems working quite well at the beginning but after a few seconds (10 to 20 seconds), the move seen in screen of the application halts and never work again. It seems that the application get to be unable to fetch data from Kinect from certain point where some seconds passed.
I don't know whether the libraries or their dependency, or Kinect's hardware itself is going wrong (as for hardware, invisibly broken or something), and I really want to know how to detect which is it.
Could anybody tell me how can I fix the issue please?
My environment is shown below:
Mac OS X v10.7.4 (MacBook Air, core i5 1.6Ghz, 4GB of memory)
Xcode 4.4.1
Kinect for Windows
OpenNI-Bin-Dev-MacOSX-v1.5.4.0
Sensor-Bin-MacOSX-v5.1.2.1
I followed instruction here about libusb: http://openkinect.org/wiki/Getting_Started#Homebrew
and when I try using libfreenect(I know it's separate from OpenNI+SensorKinect), its sample applications say "Number of devices found: 0", which makes no sense to me since I certainly connected my Kinect to MBA...)
Unless you're booting to Windows forget about Kinect for Windows.
Regarding libfreenect and OpenNI in most cases you'll use one or the other, so think of what functionalities you need.
If it's basic RGB+Depth image (and possibly motor and accelerometer ) access libfreenect is your choice.
If you need RGB+Depth image and skeleton tracking and (hand) gestures (but no motor, accelerometer access) use OpenNI. Note that if you use the unstable(dev) versions, you should use Avin's SensorKinect Driver.
Easiest thing to do a nice clean install of OpenNI.
Also, if it helps, you can a creative coding framework like Processing or OpenFrameworks.
For Processing I recommend SimpleOpenNI
For OpenFrameworks you can use ofxKinect which ties to libfreenect or ofxOpenNI. Download the OpenFrameworks packaged on the FutureTheatre Kinect Workshop wiki as it includes both addons and some really nice examples.
When you are connecting the Kinect device to the machine, have you provided external power to it? The device will appear connected to a computer by USB only power but will not be able to tranfer data as it needs the external power supply.
Also what Kinect sensor are you using? If it is a new Kinect device (designed for Windows) they may have a different device signature which may cause the OpenNI drivers to play-up. I'm not a 100% on this one, but I've only ever tried OpenNI with an XBox 360 sensor.
I'm trying to get the latitude and longitude information from a Windows Phone through the GeoCoordinate Class. When I'm outdoor or under the sky directly, I'm able to get the values instantly but when I'm indoor or inside a room, I'm getting completely wrong values. Is there a way to get my exact location when I am indoor?
N.B. Even when switching my Wi-Fi on, I am getting wrong coordinates
This totally depends on the GPS hardware primarily and secondly on the Service provider's ability to track your device based on towers. So I doubt if you can do anything. To confirm this you can check the default Maps application. If that works then there is some problem in your application. I had seen similar problems on bada OS devices but it was a GPS hardware problem.