Re: Rotating IR-Frame

In previous OS for Raspberry Pi (Bullseye) I have used a script with a Bash file to rotate the IR-frame. However, I had difficulties to get this to work in Debian 12 (Bookworm).

However, using the procedure, outlined in the link below, it now works in Debian 12 also.

The screen itself is rotated inside Debian in “Preferenses” => “Screen Configuration” – to the left (you have to be quick and work directly on the raspberry itself.
The name of the touch frame in the machine is provided with “xinput -list” in a terminal.

The code -matrix for rotation is the same as in Bullseye:
270° = Option “TransformationMatrix” “0 -1 1 1 0 0 0 0 1”

Hope this can help other people also!

@Snille

Thank you! :beaming_face_with_smiling_eyes:
Now, after your precise suggestions, I did read up on the autostart for Raspberry:
https://forums.raspberrypi.com/viewtopic.php?t=313191
https://forums.raspberrypi.com/viewtopic.php?f=66&t=294014

and using:
“sudo nano /etc/xdg/lxsession/LXDE-pi/autostart”

I pasted my line at the end of the the autostart:
@/home/pi/xin.sh
and then saved the file

In the xin.sh file, I have:
line1: #!/bin/bash
line 2: DISPLAY=:0.0 xinput --set-prop “Multi touch Multi touch overlay device” “Coordinate Transformation Matrix” 0 -1 1 1 0 0 0 0 1

So, just two lines and "line1or2: " is not part of the file :smirking_face: (and - as you said - I do have a bit different coordinate compared to you)

AND now it WORKS! Thank you !

@BJK
and you were logged on as user pi, right?
Well, instead of user pi, I am user Bo. So my home directory is like home/Bo/MagicMirror/modules…
But any idea about the xin.sh error? Would it help to let pm2 just run the xin.sh once?
Best

@BJK

Regarding: “we’re you running as root ( or using sudo ) when u did the pm2 start xin.sh?”

I just wrote “pm2 start xin.sh”,and then “pm2 start mm.sh” and then at last “pm2 save”

Should I have used “sudo pm2 start xin.sh” ?

@sdetweil

@sdetweil

Well, I start the xin.sh with PM2 and it works with calibrating the IR-frame:

xin.sh:
#!/bin/bash
DISPLAY=:0.0 xinput --set-prop “Multi touch Multi touch overlay device” “Coordinate Transformation Matrix” 0 -1 1 1 0 0 0 0 1

However, after the mm.sh (the MagicMirror) has started, then when I go back to Raspberry disktop the the Calibration is off again. If I then run the xin.sh with “pm2 start xin.sh” in a terminal window then the calibration is okay again.

This is the error that I get from pm2 log file:

Bo@MMpi:~ $ pm2 list
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ xin │ fork │ 15 │ errored │ 0% │ 0b │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
[PM2][WARN] Current process list is not synchronized with saved list. App led mm differs. Type ‘pm2 save’ to synchronize.
Bo@MMpi:~ $ pm2 log
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/Bo/.pm2/pm2.log last 15 lines:
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: Script /home/Bo/xin.sh had too many unstable restarts (16). Stopped. “errored”

/home/Bo/.pm2/logs/xin-out.log last 15 lines:
/home/Bo/.pm2/logs/xin-error.log last 15 lines:
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Unable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Unable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Unable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server

Should I do something else with pm2 or run the xin.sh in an other way?

It would be so nice to have i done automatically 😁

the mm.sh file:
cd ~/MagicMirror
DISPLAY=:0 npm start

Best Bo

@sdetweil

Well, I start the xin.sh with PM2 and it works with calibrating the IR-frame:

xin.sh:
#!/bin/bash
DISPLAY=:0.0 xinput --set-prop “Multi touch Multi touch overlay device” “Coordinate Transformation Matrix” 0 -1 1 1 0 0 0 0 1

However, after the mm.sh (the MagicMirror) has started, then when I go back to Raspberry disktop the the Calibration is off again. If I then run the xin.sh with “pm2 start xin.sh” in a terminal window then the calibration is okay again.

This is the error that I get from pm2 log file:

Bo@MMpi:~ $ pm2 list
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ xin │ fork │ 15 │ errored │ 0% │ 0b │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
[PM2][WARN] Current process list is not synchronized with saved list. App led mm differs. Type ‘pm2 save’ to synchronize.
Bo@MMpi:~ $ pm2 log
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/Bo/.pm2/pm2.log last 15 lines:
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] starting in -fork mode-
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] online
PM2 | 2022-03-31T20:11:38: PM2 log: App [xin:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-03-31T20:11:38: PM2 log: Script /home/Bo/xin.sh had too many unstable restarts (16). Stopped. “errored”

/home/Bo/.pm2/logs/xin-out.log last 15 lines:
/home/Bo/.pm2/logs/xin-error.log last 15 lines:
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Unable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Unable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Unable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server
0|xin | Invalid MIT-MAGIC-COOKIE-1 keyUnable to connect to X server

Should I do something else with pm2 or run the xin.sh in an other way?

It would be so nice to have i done automatically :beaming_face_with_smiling_eyes:

Best Bo

@Snille Hi Snille
I have had greate use of xin.sh file to run at start. It contained the:
“DISPLAY=:0.0 xinput --set-prop “Multi touch Multi touch overlay device” “Coordinate Transformation Matrix” 0 1 0 -1 0 1 0 0 1”
However, now using the pm2 start xin.sh for automatic start, I get an error in the pm2 log
What do you use to correct the ir-frame ?
Best
Bo