We are pleased to present below all posts tagged with 'IOT'. If you still can't find what you are looking for, try using the search box.
In my previous blog Windows 10 (including IoT) USB HID device identification was covered in detail. This included an app that takes the relevant IDs for an HID device and checks whether it is present on the system. Two of the IDs could be looked up via a menu as they come an HID Usage table. The menu data was loaded from a JSON (text) file and translated using Linq to a list that is the Xaml data source binding for the menu. This blog demonstrates the mechanism for loading JSON data from a text file into an Xaml ComboBox.
Human Interface Devices (HID) are supported in the “headful/headed” (viz. headless) version of Windows 10 IoT. Anything that takes users input for an app is an HID device, and can include devices such as screens that provide feedback to the user. Traditional HID devices are the mouse and keyboard, whereas gaming devices such as joystick, XBox controller and steering wheel are also HID devices. A barcode scanner or credit scanner are also be HID devices, A system with just a few push buttons to control it has those pushbuttons as a trivial HID. Technically the HID protocol was developed as a protocol for the USB-HID class such that devices that conform to that class do not need a specific driver.
Whilst the Raspberry Pi 2 has extensibility through GPIO, I2C, SPI and Single wire, the main interface for adding off-the-shelf peripherals is via USB. Unlike the desktop, there is though only a limited set of USB peripherals that can be used on the RPI2 running Windows 10 IoT in the first release. This series of articles looks at what is available and what the overarching issues are. The first Article is “Connected Devices”
Peripheral devices can be connected to the Raspberry PI 2 via the four USB host ports. The connected devices can be examined in a number of ways. This blog examines these methods.
The following is an identification of the changed project files for an RC version of a Universal App with the RTM version of the project.
The following is the comparison of the project files contents (.csproj) for a RC version of a Universal App with the RTM version of the project
The Visual State Manager can be configured to change the properties of UI controls when aspects of the UI are triggered. This blog completes the SQLite UA app by resizing the command buttons when the app runs on a small screen such as a Windows 10 phone.
The previous blog created the UA project, inserted the required SQLite bits and set up the XAML user interface. This part covers the functional code.
A truly Universal App will run on all Windows 10 targets, with only a targeted CPU change and rebuild required. This second part of this blog series sets up a UAP/UWP project to make use of the file base SQLite database engine. This part creates the project, gathers the required bits and sets up the user interface. Parts three covers the functional code.
With no version of SQL Server and SQL Compact available for Windows 10 IoT and Windows 10 Phone, the suggested alternative is SQLite. Whilst early evaluations indicate it isn’t available for Win10 IoT Background and Console apps, it’s not too hard to use SQLite with a Windows 10 UWP (Universal) app. The app can be rebuilt without modification and using the exact same project content for the desktop, phone and IoT Windows 10 targets.