# Touch Screen Problem **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [July 27, 2020, 9:46pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136 "2020-07-27T21:46:16Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Elijah.Morgan](https://avatars.discourse-cdn.com/v4/letter/e/ee7513/32.png) [@Elijah.Morgan](https://forum.inductiveautomation.com/u/Elijah.Morgan)\ **Post date:** [July 27, 2020, 9:46pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/1 "2020-07-27T21:46:16Z")
Hello, We are currently working on an HMI solution for an automation cell we have created. The screen we are using is an Industrial All in One Beckhoff PC and we are encountering a single issue with it as of now. We have multiple momentary buttons on this HMI for manual control functions and have ran into an issue of needing to double tap in order for the mousePressed event to trigger. I’m not sure if it’s a problem that can be solved through Ignition or would it be better to try to reach a solution with Beckhoff instead? We’ve noticed that when we tap on the buttons they don’t register that they are pressed until the user has moved their finger as well. Thanks for the help! ---
**Author:** ![m.sanders](https://avatars.discourse-cdn.com/v4/letter/m/df705f/32.png) [@m.sanders](https://forum.inductiveautomation.com/u/m.sanders)\ **Post date:** [July 27, 2020, 10:40pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/2 "2020-07-27T22:40:56Z")
The mousePressed Event can behave strangely sometimes. Have you tried using the actionPerformed event instead? This should trigger reliably every time the button is pressed. ---
**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\ **Post date:** [July 27, 2020, 10:44pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/3 "2020-07-27T22:44:28Z")
Take a look at settings in the touch driver. You may find something there helps it behave as expected. Also note momentary control via HMI with non-deterministic communication has issues. Search this forum for “momentary button” and you’ll find some good discussions of the issue and potential workarounds. ---
**Author:** ![jonathan.taylor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jonathan.taylor/32/4048_2.png) [@jonathan.taylor](https://forum.inductiveautomation.com/u/jonathan.taylor)\ **Post date:** [July 28, 2020, 10:17am UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/4 "2020-07-28T10:17:08Z")
I would also ask yourself, does this even need to be a momentary press? If you have access to the PLC, why not just make the PLC reset the command, rather than relying on the SCADA to do that? ---
**Author:** ![Elijah.Morgan](https://avatars.discourse-cdn.com/v4/letter/e/ee7513/32.png) [@Elijah.Morgan](https://forum.inductiveautomation.com/u/Elijah.Morgan)\ **Post date:** [July 28, 2020, 12:44pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/5 "2020-07-28T12:44:54Z")
It unfortunately needs to be a momentary press, it’s used to control a VFD jog signal and the user needs to be able to let go of the button and have the VFD stop the motor. If we could handle it in the PLC we definitely would have. ---
**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\ **Post date:** [July 28, 2020, 12:57pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/6 "2020-07-28T12:57:21Z")
I have the same problem with touch screen devices. I try to setup a simple timer on my button. define a timer on custom property of button. bind it to now(1000) add transform script. In script increment timer and check if value pass your Limit, if so use system.tag.write to reset your tag. return the new timer value. In button click event script reset self.custom.timer each time. in script check the value timer if it is ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 28, 2020, 1:14pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/7 "2020-07-28T13:14:05Z")
You absolutely need PLC code to handle lost releases for any momentary button. If you are using Perspective, I don't think there is a solid solution yet. If you are using Vision, you probably should start here: > [@Momentary Pushbutton latching ON](http://forum.inductiveautomation.com/t/momentary-pushbutton-latching-on/5373/41): > > Interesting. The failure to write when not checking is far more common that even I thought. You are still vulnerable to any of these, and to gateway-plc comms failure at the OPC level. For a more detailed (and heated) discussion, this old thread might be helpful: > [@Very Concerning Read/Write Issues. Important information for all users](http://forum.inductiveautomation.com/t/very-concerning-read-write-issues-important-information-for-all-users/18583): > > Hello Ignition Members, Disclaimer - All of our senior designers/programmers are qualified for their jobs where I work. These problems are described as I see them, they may not be exactly what happened. Therefor they are to be used for troubleshooting the issue only. Thank you. We are in contact with some ignition developers and are desperately trying to fix this problem. This is a GLOBAL problem therefore it won’t be affecting just us. It may be affecting anyone who is using ignition well. Ti… ---
**Author:** ![ashok.naphde](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ashok.naphde/32/16865_2.png) [@ashok.naphde](https://forum.inductiveautomation.com/u/ashok.naphde)\ **Post date:** [July 28, 2020, 1:24pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/8 "2020-07-28T13:24:31Z")
Hi Nader, Please share that script or little bit more information about how to develop timer script. i am also facing the same problem Thank you ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [July 28, 2020, 1:33pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/9 "2020-07-28T13:33:37Z")
> [@Elijah.Morgan](#): > > We have multiple momentary buttons on this HMI for manual control functions and have ran into an issue of needing to double tap in order for the mousePressed event to trigger. Why use the mousePressed event? Bind to control value. Your issue and "stuck bits" to me are not the same issue. Yes, you need to have something on the PLC side as a watchdog so you don't have commands stuck on. But, needing to touch the button twice is something else. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [July 28, 2020, 1:43pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/10 "2020-07-28T13:43:35Z")
Yay, Microsoft. Sarcasm implied. > [@Windows 10 touchscreen issue](http://forum.inductiveautomation.com/t/windows-10-touchscreen-issue/21399): > > I have a motor I want to jog. The motor will stay running while the touchscreen button is being pressed. It works fine with a mouse but on a Windows 10 touchscreen it does not recognize a touch until your finger is released. I have tried it on 2 different Windows 10 touchscreens. One is a Getac RX10 tablet and the other is an HP laptop. I got it to work more or less correctly in Windows 7 by disabling the “hold to right click” but that same option in Windows 10 has no effect. Has anyone else exp… ---
**Author:** ![Elijah.Morgan](https://avatars.discourse-cdn.com/v4/letter/e/ee7513/32.png) [@Elijah.Morgan](https://forum.inductiveautomation.com/u/Elijah.Morgan)\ **Post date:** [July 28, 2020, 1:43pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/11 "2020-07-28T13:43:36Z")
We are binding to control value. Momentary buttons trigger on mousePressed and turn off on mouseReleased. Our bits don’t get stuck, they straight up don’t trigger on for a long enough period for the manual controls to work. This is a problem that people have been having with Windows 10 OS for touchscreens so we’re trying to see if maybe Beckhoff has a solution to offer, I’ll post an update if I hear anything back. ---
**Author:** ![Elijah.Morgan](https://avatars.discourse-cdn.com/v4/letter/e/ee7513/32.png) [@Elijah.Morgan](https://forum.inductiveautomation.com/u/Elijah.Morgan)\ **Post date:** [July 28, 2020, 1:51pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/12 "2020-07-28T13:51:20Z")
Yeah if we were using literally any other OS this wouldn’t be a problem for us to try to solve for ourselves. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [July 28, 2020, 1:54pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/13 "2020-07-28T13:54:32Z")
You can try some of the registry edits in the thread I posted. No warranty. 😉 ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [July 28, 2020, 1:56pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/14 "2020-07-28T13:56:31Z")
I understand, that was my point, some of the comments in this thread are not on point. I have used several win 10 touch panels and they all worked great, with mom. PBs. As stated, try a different driver. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [July 28, 2020, 2:00pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/15 "2020-07-28T14:00:18Z")
Can I ask whose panels you have used? ---
**Author:** ![Elijah.Morgan](https://avatars.discourse-cdn.com/v4/letter/e/ee7513/32.png) [@Elijah.Morgan](https://forum.inductiveautomation.com/u/Elijah.Morgan)\ **Post date:** [July 28, 2020, 2:01pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/16 "2020-07-28T14:01:56Z")
We’re using Beckhoff’s panels right now, it’s the plant standard for us so it’s the only ones we’ll bring into the plant. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [July 28, 2020, 2:02pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/17 "2020-07-28T14:02:48Z")
Sorry, that was supposed to have been to @jlandwerlen. ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [July 28, 2020, 2:11pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/18 "2020-07-28T14:11:10Z")
advantech and teguar ---
**Author:** ![Elijah.Morgan](https://avatars.discourse-cdn.com/v4/letter/e/ee7513/32.png) [@Elijah.Morgan](https://forum.inductiveautomation.com/u/Elijah.Morgan)\ **Post date:** [July 28, 2020, 2:52pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/19 "2020-07-28T14:52:29Z")
We have come up with a weird solution for the problem that I am not a huge fan of but it works. We installed a single-touch driver from Elo Touch and set the visibility of the cursor to 0 when in the program. It’s a strange solution but it worked for us. Make sure click lock is disabled when using this solution. If anyone can think of a less strange way to get this done, please feel free to post your thoughts. ---
**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\ **Post date:** [July 28, 2020, 3:18pm UTC](https://forum.inductiveautomation.com/t/touch-screen-problem/37136/20 "2020-07-28T15:18:14Z")
Yeah, I don’t remember all the details, but we are using Elo Touch drivers and had to tweak some settings to get things working as desired as well (Beckhoff Windows 10 Embedded PC with Hope Industrial panels). Elo Touch driver version mattered. [Next page](https://forum.inductiveautomation.com/t/touch-screen-problem/37136.md?page=2)