What is the plug is on the Plugable MXChip AZ3166 IoT DevKit? - hardware

I'm looking at prototyping a couple of solutions using the MXChip AZ3166 that require a number of external devices like GPS, Display and Comms hardware.
Does anyone know what connectors can be used with the "Pluggable" MXChip AZ3166 IOT Devkit, or if there are any breakout boards available for it?

In Mxchip AZ3166, there is a edge connector on the board that is compatible with BBC Micro:bit accessories. So you could easily extend it with external devices.
More information of Micro:Bit could be find here: https://www.kitronik.co.uk/microbit/bbc-micro-bit-accessories.html
And you could check this example https://github.com/jimbobbennett/InternetConnectedFan on how to use Micro:Bit to connect to external devices.

Related

Cannot access all Azure Kinect Cameras

I'm trying to use the feed from all Azure Kinect cameras in other apps (e.g. iMotions, OBS).
Unfortunately, there is only one camera available on the device manager, under "Camera > Azure Kinect 4K Camera" while the other cameras appear under "Universal Serial Bus devices".
I would expect to see them all under "Camera". Can you please provide further details on how to solve this problem.
Also, note that:
I can see all the cameras in the Azure Kinect Viewer but cannot use the feed in other apps.
The firmware is the latest one.
I'm using a usb 3.0 port
Thanks in advance

How to use a custom USB device (WinUSB) on Microsoft HoloLens 2?

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.

Using Roku's USB for ECP 'query' commands?

I added an ESP8266 nodeMCU for TV and SoundBar IR commands. It also provides a LAN server delivering an HTML/javascript based remote controller to my devices - computer, tablets and mobile phones.
I use this same remote setup for both a Roku4 w/ an old Dynex (dumb) TV as well as a newer TCL Roku Smart TV w/ soundbar.
Question is, can I access Roku data as used to be provided by ECP queries like '/query/apps' and '/query/active-app' via the Roku's USB port? ...if not, what is required to accomplish this end?
The definitive answer from the Roku folks is no. It's use is for data storage devices.

How do I access a GPS from Windows IoT on Rasperry Pi?

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)

Logitech Unifying Receiver Protocol?

Is there a place where I can find documentation or an SDK about the Logitech Unifying Receiver?
I recently obtained a wireless mouse, which came with a Logitech Unifying Receiver (a small USB dongle that plugs into the computer and communicates with the mouse/other compatible devices (such as keyboards)).
I wanted to try writing an app for my smartphone that pretends to be a mouse and sends data to the receiver.
I was able to monitor the data from the USB bus by using usbmon, and could probably use that to hack something out, but wanted to know if I could find the info I need somewhere on the internet without having to derive it on my own.
I'm going to try using SL4A on Android, if that helps any.
I have discovered some Logitech documents on a shared folder in Google Docs via this Chromium bug report. For convenience, I converted all doc(x) files to PDFs and put those on https://lekensteyn.nl/files/logitech/.
You will find Logitech HID++ 1.0 Specification for Unifying Receivers (pdf) very interesting, it describes the USB traffic (instead of the 2.4GHz wireless traffic as noted by Avery). My article Logitech Unifying for Linux: Reverse Engineering and unpairing tool documents a way to capture the traffic with usbmon and QEMU. It also includes tools to make the usbmon output prettier to read (for this protocol).
This is Avery, aka Tequals0. The USB dongle is a USB HID mouse/keyboard device, so all that traffic that you are seeing is basically generic HID traffic- if you want to pair your phone to your dongle, you will have to emulate the wireless traffic, not the USB traffic-that is generated by the dongle.
There is some info at Tequals0 blog, and AveryLouie also got some python tool operating with unifying