How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?











up vote
0
down vote

favorite












I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7.
The problem consists of a number of factors, please find the details below:




  • The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format.

  • The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen.

  • The employees using this solution is not supposed to see nor have access to anything but the POS application.

  • Our sales organization demands that touch is an available feature when going live with the new POS environment.


Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen:




  • We've simply changed the resolution in CentOS7 from 1920x1080 16:9 to 1024:768, we get the expected result with black boarders on the short edges of the touch-screen.

  • We then started the POS application and quickly notice that the touch-screen doesn't work as expected, it hits other menus and buttons compared to where we actually touched the screen.

  • We found similar posts regarding this issue but none where it is desired to achieve what we're trying to; running a 16:9 touch-screen with a 4:3 resolution.

  • In similar posts we've found tools (xinput, xinput_calibrator, xrandr) that we tried using to resolve this but so far we haven't been able to and now we're not sure how to really approach this issue.


For instance, when we run xinput_calibrator we can see the application starting but it stretches beyond our screen resolution and we're unable to complete the calibration due to this.
Our beliefs are that; when we change the monitor resolution, the touch-screen doesn't consider this change and also has its "fixed size"... but all in all we're just guessing.



When running xinput we can see the touch-screen being listed as two different devices, but all in all they seem to have the same property values:



u239c   u21b3 ILITEK ILITEK-TP                            id=14   [slave  pointer  (2)]

u239c u21b3 ILITEK ILITEK-TP id=15 [slave pointer (2)]


Looking closer on one of the devices (xinput list-props 14) we can see the following information and this is an example where it gets more difficult for us.. we're simply not sure what properties, in any, we need to focus on:



Device 'ILITEK ILITEK-TP':

Device Enabled (137): 1

Coordinate Transformation Matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

Device Accel Profile (265): 0

Device Accel Constant Deceleration (266): 1.000000

Device Accel Adaptive Deceleration (267): 1.000000

Device Accel Velocity Scaling (268): 10.000000

Device Product ID (259): 8746, 323

Device Node (260): "/dev/input/event5"

Evdev Axis Inversion (269): 0, 0

Evdev Axis Calibration (270): 0, 16384, 0, 9600

Evdev Axes Swap (271): 0

Axis Labels (272): "Abs MT Position X" (296), "Abs MT Position Y" (297), "None" (0), "None" (0)

Button Labels (273): "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Wheel Up" (143), "Button Wheel Down" (144)

Evdev Scrolling Distance (274): 0, 0, 0

Evdev Middle Button Emulation (275): 0

Evdev Middle Button Timeout (276): 50

Evdev Middle Button Button (277): 2

Evdev Third Button Emulation (278): 0

Evdev Third Button Emulation Timeout (279): 1000

Evdev Third Button Emulation Button (280): 3

Evdev Third Button Emulation Threshold (281): 20

Evdev Wheel Emulation (282): 0

Evdev Wheel Emulation Axes (283): 0, 0, 4, 5

Evdev Wheel Emulation Inertia (284): 10

Evdev Wheel Emulation Timeout (285): 200

Evdev Wheel Emulation Button (286): 4

Evdev Drag Lock Buttons (287): 0


When running xrandr we can see that the resolution settings are what we expect, but we're not sure how to "tell" the touch-screen what the monitor resolution/format actually is.



Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
eDP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1920x1080 60.05 + 40.03
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.04* 60.00
960x720 60.00
928x696 60.05
896x672 60.01
800x600 60.00 60.32 56.25
700x525 59.98
640x512 60.02
640x480 60.00 59.94
512x384 60.00
400x300 60.32 56.34
320x240 60.05
DP-1 disconnected (normal left inverted right x axis y axis)


I'm sorry if the information provided is hard to understand, we're not all familiar with Linux but can perform the most basic tasks.
If we've missed any necessary information in this post please excuse us and do let us know what we should add to it in order for us to go further.



Many thanks in advance.



Best Regards
Danny










share|improve this question







New contributor




Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
























    up vote
    0
    down vote

    favorite












    I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7.
    The problem consists of a number of factors, please find the details below:




    • The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format.

    • The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen.

    • The employees using this solution is not supposed to see nor have access to anything but the POS application.

    • Our sales organization demands that touch is an available feature when going live with the new POS environment.


    Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen:




    • We've simply changed the resolution in CentOS7 from 1920x1080 16:9 to 1024:768, we get the expected result with black boarders on the short edges of the touch-screen.

    • We then started the POS application and quickly notice that the touch-screen doesn't work as expected, it hits other menus and buttons compared to where we actually touched the screen.

    • We found similar posts regarding this issue but none where it is desired to achieve what we're trying to; running a 16:9 touch-screen with a 4:3 resolution.

    • In similar posts we've found tools (xinput, xinput_calibrator, xrandr) that we tried using to resolve this but so far we haven't been able to and now we're not sure how to really approach this issue.


    For instance, when we run xinput_calibrator we can see the application starting but it stretches beyond our screen resolution and we're unable to complete the calibration due to this.
    Our beliefs are that; when we change the monitor resolution, the touch-screen doesn't consider this change and also has its "fixed size"... but all in all we're just guessing.



    When running xinput we can see the touch-screen being listed as two different devices, but all in all they seem to have the same property values:



    u239c   u21b3 ILITEK ILITEK-TP                            id=14   [slave  pointer  (2)]

    u239c u21b3 ILITEK ILITEK-TP id=15 [slave pointer (2)]


    Looking closer on one of the devices (xinput list-props 14) we can see the following information and this is an example where it gets more difficult for us.. we're simply not sure what properties, in any, we need to focus on:



    Device 'ILITEK ILITEK-TP':

    Device Enabled (137): 1

    Coordinate Transformation Matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

    Device Accel Profile (265): 0

    Device Accel Constant Deceleration (266): 1.000000

    Device Accel Adaptive Deceleration (267): 1.000000

    Device Accel Velocity Scaling (268): 10.000000

    Device Product ID (259): 8746, 323

    Device Node (260): "/dev/input/event5"

    Evdev Axis Inversion (269): 0, 0

    Evdev Axis Calibration (270): 0, 16384, 0, 9600

    Evdev Axes Swap (271): 0

    Axis Labels (272): "Abs MT Position X" (296), "Abs MT Position Y" (297), "None" (0), "None" (0)

    Button Labels (273): "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Wheel Up" (143), "Button Wheel Down" (144)

    Evdev Scrolling Distance (274): 0, 0, 0

    Evdev Middle Button Emulation (275): 0

    Evdev Middle Button Timeout (276): 50

    Evdev Middle Button Button (277): 2

    Evdev Third Button Emulation (278): 0

    Evdev Third Button Emulation Timeout (279): 1000

    Evdev Third Button Emulation Button (280): 3

    Evdev Third Button Emulation Threshold (281): 20

    Evdev Wheel Emulation (282): 0

    Evdev Wheel Emulation Axes (283): 0, 0, 4, 5

    Evdev Wheel Emulation Inertia (284): 10

    Evdev Wheel Emulation Timeout (285): 200

    Evdev Wheel Emulation Button (286): 4

    Evdev Drag Lock Buttons (287): 0


    When running xrandr we can see that the resolution settings are what we expect, but we're not sure how to "tell" the touch-screen what the monitor resolution/format actually is.



    Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
    eDP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
    1920x1080 60.05 + 40.03
    1400x1050 59.98
    1280x1024 60.02
    1280x960 60.00
    1024x768 60.04* 60.00
    960x720 60.00
    928x696 60.05
    896x672 60.01
    800x600 60.00 60.32 56.25
    700x525 59.98
    640x512 60.02
    640x480 60.00 59.94
    512x384 60.00
    400x300 60.32 56.34
    320x240 60.05
    DP-1 disconnected (normal left inverted right x axis y axis)


    I'm sorry if the information provided is hard to understand, we're not all familiar with Linux but can perform the most basic tasks.
    If we've missed any necessary information in this post please excuse us and do let us know what we should add to it in order for us to go further.



    Many thanks in advance.



    Best Regards
    Danny










    share|improve this question







    New contributor




    Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7.
      The problem consists of a number of factors, please find the details below:




      • The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format.

      • The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen.

      • The employees using this solution is not supposed to see nor have access to anything but the POS application.

      • Our sales organization demands that touch is an available feature when going live with the new POS environment.


      Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen:




      • We've simply changed the resolution in CentOS7 from 1920x1080 16:9 to 1024:768, we get the expected result with black boarders on the short edges of the touch-screen.

      • We then started the POS application and quickly notice that the touch-screen doesn't work as expected, it hits other menus and buttons compared to where we actually touched the screen.

      • We found similar posts regarding this issue but none where it is desired to achieve what we're trying to; running a 16:9 touch-screen with a 4:3 resolution.

      • In similar posts we've found tools (xinput, xinput_calibrator, xrandr) that we tried using to resolve this but so far we haven't been able to and now we're not sure how to really approach this issue.


      For instance, when we run xinput_calibrator we can see the application starting but it stretches beyond our screen resolution and we're unable to complete the calibration due to this.
      Our beliefs are that; when we change the monitor resolution, the touch-screen doesn't consider this change and also has its "fixed size"... but all in all we're just guessing.



      When running xinput we can see the touch-screen being listed as two different devices, but all in all they seem to have the same property values:



      u239c   u21b3 ILITEK ILITEK-TP                            id=14   [slave  pointer  (2)]

      u239c u21b3 ILITEK ILITEK-TP id=15 [slave pointer (2)]


      Looking closer on one of the devices (xinput list-props 14) we can see the following information and this is an example where it gets more difficult for us.. we're simply not sure what properties, in any, we need to focus on:



      Device 'ILITEK ILITEK-TP':

      Device Enabled (137): 1

      Coordinate Transformation Matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

      Device Accel Profile (265): 0

      Device Accel Constant Deceleration (266): 1.000000

      Device Accel Adaptive Deceleration (267): 1.000000

      Device Accel Velocity Scaling (268): 10.000000

      Device Product ID (259): 8746, 323

      Device Node (260): "/dev/input/event5"

      Evdev Axis Inversion (269): 0, 0

      Evdev Axis Calibration (270): 0, 16384, 0, 9600

      Evdev Axes Swap (271): 0

      Axis Labels (272): "Abs MT Position X" (296), "Abs MT Position Y" (297), "None" (0), "None" (0)

      Button Labels (273): "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Wheel Up" (143), "Button Wheel Down" (144)

      Evdev Scrolling Distance (274): 0, 0, 0

      Evdev Middle Button Emulation (275): 0

      Evdev Middle Button Timeout (276): 50

      Evdev Middle Button Button (277): 2

      Evdev Third Button Emulation (278): 0

      Evdev Third Button Emulation Timeout (279): 1000

      Evdev Third Button Emulation Button (280): 3

      Evdev Third Button Emulation Threshold (281): 20

      Evdev Wheel Emulation (282): 0

      Evdev Wheel Emulation Axes (283): 0, 0, 4, 5

      Evdev Wheel Emulation Inertia (284): 10

      Evdev Wheel Emulation Timeout (285): 200

      Evdev Wheel Emulation Button (286): 4

      Evdev Drag Lock Buttons (287): 0


      When running xrandr we can see that the resolution settings are what we expect, but we're not sure how to "tell" the touch-screen what the monitor resolution/format actually is.



      Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
      eDP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
      1920x1080 60.05 + 40.03
      1400x1050 59.98
      1280x1024 60.02
      1280x960 60.00
      1024x768 60.04* 60.00
      960x720 60.00
      928x696 60.05
      896x672 60.01
      800x600 60.00 60.32 56.25
      700x525 59.98
      640x512 60.02
      640x480 60.00 59.94
      512x384 60.00
      400x300 60.32 56.34
      320x240 60.05
      DP-1 disconnected (normal left inverted right x axis y axis)


      I'm sorry if the information provided is hard to understand, we're not all familiar with Linux but can perform the most basic tasks.
      If we've missed any necessary information in this post please excuse us and do let us know what we should add to it in order for us to go further.



      Many thanks in advance.



      Best Regards
      Danny










      share|improve this question







      New contributor




      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7.
      The problem consists of a number of factors, please find the details below:




      • The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format.

      • The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen.

      • The employees using this solution is not supposed to see nor have access to anything but the POS application.

      • Our sales organization demands that touch is an available feature when going live with the new POS environment.


      Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen:




      • We've simply changed the resolution in CentOS7 from 1920x1080 16:9 to 1024:768, we get the expected result with black boarders on the short edges of the touch-screen.

      • We then started the POS application and quickly notice that the touch-screen doesn't work as expected, it hits other menus and buttons compared to where we actually touched the screen.

      • We found similar posts regarding this issue but none where it is desired to achieve what we're trying to; running a 16:9 touch-screen with a 4:3 resolution.

      • In similar posts we've found tools (xinput, xinput_calibrator, xrandr) that we tried using to resolve this but so far we haven't been able to and now we're not sure how to really approach this issue.


      For instance, when we run xinput_calibrator we can see the application starting but it stretches beyond our screen resolution and we're unable to complete the calibration due to this.
      Our beliefs are that; when we change the monitor resolution, the touch-screen doesn't consider this change and also has its "fixed size"... but all in all we're just guessing.



      When running xinput we can see the touch-screen being listed as two different devices, but all in all they seem to have the same property values:



      u239c   u21b3 ILITEK ILITEK-TP                            id=14   [slave  pointer  (2)]

      u239c u21b3 ILITEK ILITEK-TP id=15 [slave pointer (2)]


      Looking closer on one of the devices (xinput list-props 14) we can see the following information and this is an example where it gets more difficult for us.. we're simply not sure what properties, in any, we need to focus on:



      Device 'ILITEK ILITEK-TP':

      Device Enabled (137): 1

      Coordinate Transformation Matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

      Device Accel Profile (265): 0

      Device Accel Constant Deceleration (266): 1.000000

      Device Accel Adaptive Deceleration (267): 1.000000

      Device Accel Velocity Scaling (268): 10.000000

      Device Product ID (259): 8746, 323

      Device Node (260): "/dev/input/event5"

      Evdev Axis Inversion (269): 0, 0

      Evdev Axis Calibration (270): 0, 16384, 0, 9600

      Evdev Axes Swap (271): 0

      Axis Labels (272): "Abs MT Position X" (296), "Abs MT Position Y" (297), "None" (0), "None" (0)

      Button Labels (273): "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Wheel Up" (143), "Button Wheel Down" (144)

      Evdev Scrolling Distance (274): 0, 0, 0

      Evdev Middle Button Emulation (275): 0

      Evdev Middle Button Timeout (276): 50

      Evdev Middle Button Button (277): 2

      Evdev Third Button Emulation (278): 0

      Evdev Third Button Emulation Timeout (279): 1000

      Evdev Third Button Emulation Button (280): 3

      Evdev Third Button Emulation Threshold (281): 20

      Evdev Wheel Emulation (282): 0

      Evdev Wheel Emulation Axes (283): 0, 0, 4, 5

      Evdev Wheel Emulation Inertia (284): 10

      Evdev Wheel Emulation Timeout (285): 200

      Evdev Wheel Emulation Button (286): 4

      Evdev Drag Lock Buttons (287): 0


      When running xrandr we can see that the resolution settings are what we expect, but we're not sure how to "tell" the touch-screen what the monitor resolution/format actually is.



      Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
      eDP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
      1920x1080 60.05 + 40.03
      1400x1050 59.98
      1280x1024 60.02
      1280x960 60.00
      1024x768 60.04* 60.00
      960x720 60.00
      928x696 60.05
      896x672 60.01
      800x600 60.00 60.32 56.25
      700x525 59.98
      640x512 60.02
      640x480 60.00 59.94
      512x384 60.00
      400x300 60.32 56.34
      320x240 60.05
      DP-1 disconnected (normal left inverted right x axis y axis)


      I'm sorry if the information provided is hard to understand, we're not all familiar with Linux but can perform the most basic tasks.
      If we've missed any necessary information in this post please excuse us and do let us know what we should add to it in order for us to go further.



      Many thanks in advance.



      Best Regards
      Danny







      resolution centos-7 touchscreen xrandr xinput






      share|improve this question







      New contributor




      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked Nov 21 at 10:55









      Danny

      1




      1




      New contributor




      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Danny is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Danny is a new contributor. Be nice, and check out our Code of Conduct.










           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377244%2fhow-to-calibrate-169-built-in-touch-screen-to-a-43-resolution%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Danny is a new contributor. Be nice, and check out our Code of Conduct.










           

          draft saved


          draft discarded


















          Danny is a new contributor. Be nice, and check out our Code of Conduct.













          Danny is a new contributor. Be nice, and check out our Code of Conduct.












          Danny is a new contributor. Be nice, and check out our Code of Conduct.















           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377244%2fhow-to-calibrate-169-built-in-touch-screen-to-a-43-resolution%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

          Eduardo VII do Reino Unido