Okay we are using the Surface Pro as HMI's (Human Machine Interfaces) in industrial manufacturing environments, nicely mounted in the door of a rugged electrical enclosure with fan and filter package and some other electronics. The software we run is Win32, and is not one of the Microsoft Universal Apps, so we can not used assigned access. We want to prevent the operators from going anywhere but our application, which we can easily do because they do not have a mouse or keyboard, and our system hides the task bar. I found in the Surface Pro app where to disable the Windows button, so they cannot press it. The only way to put the system into kiosk mode in our case is to run the Classic Shell and write our own script, which I do not want to do. We are running a couple of different software packages like our SCADA software, SQL Express 2012, etc.
ALL WE NEED IS SOME EASY WAY TO TURN OFF SWIPE IN WINDOWS 10. If we can get that done we are good to go. I had an IT friend of mine look just about everywhere tonight and we cannot find it. Microsoft would it not make sense to have a little button on the Surface Pro app that said Swipe Enabled/Disabled? We understand the idea of it being a mobile touchscreen, but in our case its a true kiosk, it never moves and it has a dedicated gigabit ethernet connection talking to a plant wide PLC (programmable automation controller).
Not only is it a kiosk, we have a 2nd monitor connected via the mini display to HDMI port and have the two independent of one another. Meaning we use the Surface Pro 3 as an HMI and a high definition scoreboard displaying real time metrics in manufacturing. For our clients its a two for one, typically we would need a pc behind each HDTV. With some custom VB scripting in our SCADA software we can show the HMI on monitor 1 (Surface Pro 3) and different screens and metrics on monitor 2 (HDTV). We love it and so do our clients, now we just need to turn off swipe! Help....any ideas? Usually I can find what I am looking for by searching the net, but this one has me puzzled. Really trying to avoid custom scripting, as we have many of these to setup for machines over time. Any help or insight would be greatly appreciated.
Mike
Sr. Automation Engineer
GMG Corporation
Pittsburgh, PA