View and control your Windows 10 IoT Core UWP applications remotely, from a Windows 10 desktop PC, tablet, or phone
The remote display experience is a technology used to remotely control UWP applications running on a Windows 10 IoT Core device. Remote control can be established from any Windows 10 desktop PC, tablet, or phone, putting a display on every displayless device.
To see an example of the technology in action, check out this YouTube video. In the second half, the demonstrator uses a tablet to remotely control the Windows 10 IoT Core device, using both touch and accelerometer to control the system.
Users connect to their Windows 10 IoT Core devices through a Microsoft Store application installed on their Windows 10 companion device of choice. The UI generated by the UWP application running on the Windows 10 IoT Core device is remoted to the display of the companion device, while input and sensor data are sent in the opposite direction. The functionality is easy-to-use, and is included out-of-box on the latest Insider build of Windows 10 IoT Core. Learn how to use it below.
To get started, you’ll need to set up a Windows 10 IoT Core device with the latest build of Windows 10 (Creators Update) - visit the Get Started page to set up your board.
Setup is quick and easy - follow the three steps below to use the remote display technology.
Turn on the remote display functionality on your Windows 10 IoT Core device.
Connect your device to the Internet and connect to Windows Device Portal. For detailed instructions on how to get connected, see the Get Started page.
Choose the page “Remote” from the options on the left, and mark the check box labeled “Enable Window IoT Remote Server”. Your device is now enabled for remote display experience.
Install the Windows IoT Remote Client on your companion Windows 10 device.
To enable a Windows 10 device to connect to your Windows 10 IoT Core device, you need to install our Store application. The Windows IoT Remote Client app is currently available by link only and can be found here.
Connect to your Windows 10 IoT Core device through the installed application.
Run the Windows IoT Remote Client application on your Windows 10 companion device. At the Connect screen, enter the IP address of your device. The two devices should connect, remoting the UI experience of the Windows 10 IoT Core device to the companion device.
You’re now connected! From this point forward, touch and click input on the companion Windows 10 device can be used to control the Windows 10 IoT Core UWP application. In addition, you can use accelerometer data from your connected companion device.
While the remote display experience is a powerful tool to put a display on any displayless device, it also offers the ability to use remote sensors in an Windows 10 IoT Core application. If you followed the setup above with a Windows 10 tablet or phone as your companion device, you can use the accelerometer in the connected device as a sensor in your IoT Core project.
To see the remote sensors in action, once again check out this YouTube video. In the second half, the demonstrator uses a tablet to remotely control the Windows 10 IoT Core device, using both touch and accelerometer to control the system.
The code to use a remote sensor is simple - in fact, it’s the exact same code used to implement local sensors.
In a UWP application on a Windows 10 IoT Core device, the GetDefault() function of the Accelerometer class will search for remote accelerometers on connected companion devices. View this Hackster.io post for a closer look at this demo using remote sensors. Refer to the implementation of an accelerometer on this GitHub code page to integrate remote sensors in your own projects.
The remote display experience currently works on Raspberry Pi 2 and 3, Minnowboard Max, and Dragonboard. These boards must be running the latest build of Windows 10 IoT Core (Creators Update). The remote display and sensor capability is an “alpha” or “Insider” technology. It is still in an early state, but it serves as a useful tool for putting a display on any displayless device.
Using the remote display technology is quick and easy, but there are still some issues that users may experience. Make sure to follow the Setup instructions above closely - if problems persist, check below.
Failed connections can be caused by a number of issues, but we’ve run into a couple more common problems:
The Raspberry Pi 2 does not have GPU support on Windows 10 IoT Core, thus the framerate of the remote display experience is lower than on other boards. Enhanced CPU on the Raspberry Pi 3, as well as graphics capabilities on the MBM and Dragonboard, allow for a more stable experience. Lowering the resolution to 800x600 will increase performance.