I am currently following the steps on your web page for the Torizon calibration but I am getting a weston-touch-calibrator error : “:0” was not found.
I have already the -e HEAD=HDMI-A-1 command but it didn’t change anything.
Thank you for your help,
Muzzy Weston-touch-calibrator error : “:0” was not found issue
As you can see the script actually used the variable DISPLAY not HEAD in the script. With TorizonCore 6.X we started using Debian bookworm containers and change the script to use HEAD. That’s probably where you got this confusion from.
I have changed the variable and I still have the error : weston-touch-calibrator error : “HDMI-A-1” was not found …
I am just getting started understanding the way to use the calibration so I may do some errors.
It seems for some reason the touch calibration tool can’t derive what your touch input is based on the display.
Let’s try this. If you pass nothing to the DISPLAY variable then the touch calibration tool will instead list possible touch inputs and their corresponding display. You should see something like this:
So in my case the display device is DPI-1 while the corresponding touch input is /sys/devices/platform/bus@5a000000/5a810000.i2c/i2c-17/17-004a/input/input1/event1. I can then set DISPLAY to this touch input file-path and that seems to satisfy the touch calibration tool as well.
Thank you fo your answer.
I can finallynow display the crosses on my touchscreen but the touch isn’t active.
I cannot touch the crosses to finish the calibration.
It seems that there is a problem with my touch screen.
I have tried to test the touch with the “evtest” tools. And the touch isnt active on the input identified as my touchscreen from the weston-touch calibrator container. However it is active on another input identified as Mouse from the container.
The event9 is identified as my touchscreen but the touch isn’t active but it’s active on the event6.
I have already tried to change the event6 into a touchscreen and the event9 into mouse or something else but it is not working.
However it is active on another input identified as Mouse from the container.
That makes sense. I’ve seen others have issues with this before particularly with USB touch. Sometimes USB touch will appears as a mouse interface instead of a proper touch interface to the system. This causes issues with the touch calibration tool since it specifically looks for touch interfaces only.
I can finallynow display the crosses on my touchscreen but the touch isn’t active.
I cannot touch the crosses to finish the calibration.
Wait did your touch work before this point?
I guess im near from successfully calibrate it but I definitely miss something.
I have change the touchscreen.rules files
So you’re trying to use a udev rule to get your mouse interface to come across as a touch interface? Can’t say I’ve tried this and not sure if it will work quite right. Though for reference here’s what the udev of a touchscreen would look like: Touch Screen Calibration (Torizon) | Toradex Developer Center
Worst, case scenario you could try manually creating the calibration info. All the calibration tool does is create a udev rule with some calibration values. Though these values would be difficult to determine manually.
My touchscreen isn’t Linux native so I have tried to manually change some settings to make it functional.
What do you mean by this? Do you mean your display isn’t mean to be used on Linux?
It’s difficult for me to suggest something specific since I don’t have a touchscreen display that demonstrates the same behavior.
You can see how the values in this matrix get interpreted. It’s a bit complex and I’m not even sure if it’s possible/practical to deduce these values by hand without a tool.
