How can we get the Windows version installed on the device through IotHub Device Twin or Direct Method or Any other means?
IoTHub SDKs can not get the version of the windows system installed on the device,they have no related API.AnalyticsVersionInfo Class provides version information about the device family. Please see this topic of Windows 10 get DeviceFamilyVersion.
Related
I got a Kinect from Xbox 360 and I bought an adaptor to plug it to my laptop. The problem is, I already installed 1.8 SDK and developer tools but when I run Kinect Explorer it says 'kinect sensor required'. So I look the device manager I couldn't find Microsoft Kinect, there's only Generic USB Hub. I tried to use the older version, 1.7, but it makes no different. What should I do to get this Kinect works?
I had the same problem when connected Kinect through an external USB hub. When I plugged it directly into the PC USB port everything was OK.
I made a custom USB sensor device that runs on a Windows 8.1 / 10 desktop computer using the WinUSB driver (I implemented Microsoft extended USB descriptors in device firmware to automatically install the driver when the device connected).
Can I use a WinUSB device on HoloLens2? Or, if there is no WinUSB support on HoloLens2, how can I use my USB device with a “custom USB device class”?
At the moment, I do not have a hololens2, but I need to understand how the USB works on it.
Edit: I found this link: https://learn.microsoft.com/en-us/hololens/hololens-connect-devices#hololens-2-connect-usb-c-devices
It says that hololens2 supports the following device classes:
Mass storage devices (such as thumb drives)
Ethernet adapters (including ethernet plus charging)
USB-C-to-3.5mm digital audio adapters
USB-C digital audio headsets (including headset adapters plus charging)
Wired mouse
Wired keyboard
Combination PD hubs (USB A plus PD charging)
My device does not implement any of these classes (custom class). Is there a chance to make it work on hololens2?
I finally tested my code and USB device on real Hololens 2. The USB device works great there because Hololens2 supports WinUSB! The WinUSB driver was installed automatically (my device has WinUSB descriptors).
According to the documentation you referred, all classes HoloLens2 supports have been listed, and unlisted classes are not supported.
Could you provide more information about your business request and submit a feature request via feedback hub on new feature request to be considered in future releases of HoloLens OS and devices?
If it’s a hot impacted feature, it will be possible to be given priority to jump in the development schedule. Actually, the existing classed on HoloLens 2 are also based on user’s feedback in such way.
For how to post feedback request, you can follow this doc: Send feedback to Microsoft with the Feedback Hub app.
I'm using an Ubuntu 16.04 guest on Windows 10.
I have this strange problem: all USB devices are not attached even the ones that were working fine with a filter.
The devices are captured but not attached. If I try to click on a device under "Devices->USB->" I receive a message saying that the device is busy.
Have a look at UpperFilters key at this path Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{36fc9e60-c465-11cf-8056-444553540000} in the Windows registry.
Remove the UpperFilters.
For example Wireshark setup the UpperFilters and stopped all devices from being attached to VirtualBox.
Download and install the extension pack from here: https://www.virtualbox.org/wiki/Downloads
Be sure that you are not already using that pendrive in your host or guest.
And check in "Devices->USB" if your are choosing right type (usb 1.0, 2.0, or 3.0)
I have done this when running Debian using gpsd. But when running Windows IoT preview...what is a way to get the NMEA sentences off an attached GPS (on the USB port). Is that kind of support around yet?
Currently this support is not yet available but it is being actively developed. Furthermore the Geolocator API is broken. Unfortunately I don't have an ETA for this but its coming.
Mark Radbourne (MSFT)
Quite a while I am struggling with a problem regarding the installation of certain USB device driver in Windows CE 6.0.
The device is some kind of Digital and Analog IO device that connects to the USB port.
It is the LabJack U3.
I followed all instruction and put the driver (labjackusb.dll) and coresponding registry entries into the Windows CE image but the device is not detected correctly.
On every boot up a small Message box came up with the Title "Unidentified USB Device"
and the message "Enter the name of the driver for this USB device:"
Whatever name I put into it want work. I tried the name of the dll. Some title in from the registry and so on but never succedes.
The driver does not work nor the device.
The customer support can not help me so I am asking here somebody to help me at least
with a steps to follow to try to find a solution.
Why the OS does not matches the USB device with the corresponding driver?
I checked everything one million times and everything is in place.
There are a load of reasons this might fail. First:
Is the driver definitely a Windows CE driver?
Is it built for CE 6.0 (not 5.0 or something else)?
Is it built for the same processor architecture you have?
The way to really debug this is to hook up KITL, put in a debug version of device.exe and see what the device managet is actually doing when you plug in the device. A way better and way more reliable mechanism than just trying to guess.