MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    IR Frame doesn't rotate

    Scheduled Pinned Locked Moved Troubleshooting
    24 Posts 7 Posters 18.4k Views 8 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • SnilleS Offline
      Snille Module Developer @strawberry 3.141
      last edited by

      @strawberry-3.141 Yes, I read that to, but it may also mean like vertical like a monitor (normal landscape) and horizontal like a table (but still in landscape). :)

      If you cant find it, make it and share it!
      Modules: MMM-homeassistant-sensors, MMM-Modulebar, MMM-Profilepicture, MMM-Videoplayer

      AlessandroRaA 1 Reply Last reply Reply Quote 0
      • AlessandroRaA Offline
        AlessandroRa @Snille
        last edited by

        @Snille Sorry, but I hade a few problems in these weeks, so I didn’t had the chance to fix it…
        I asked the manufacturer (thank you @cowboysdude!) and they did send me a driver, but they’ve sent it with 3 extensions: .pkg, .exe, .apk and I’ve no idea how to open them… I have Debian 8 Jessie, by the way.
        Any suggestions? :anguished:

        yawnsY SnilleS 2 Replies Last reply Reply Quote 0
        • yawnsY Offline
          yawns Moderator @AlessandroRa
          last edited by

          @AlessandroRa
          Hm, these are drivers for Mac (pkg), Android (apk), Windows (exe)

          Maybe you can extract the pkg file and gather the driver files?

          AlessandroRaA 1 Reply Last reply Reply Quote 0
          • SnilleS Offline
            Snille Module Developer @AlessandroRa
            last edited by Snille

            @AlessandroRa Hi! Unfortunately the manufacturer do not have any drivers for ARM.
            I ended up with using it as a normal “HID” device. I have to rotate the frame manually with this command in SSH: DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
            But I cant get it to stick after reboot. So, I have to do it after every boot when everything has started.
            I did not get the xinnput_calibration values to stick either. I’m in Rasbian Jessie Lite.

            If you cant find it, make it and share it!
            Modules: MMM-homeassistant-sensors, MMM-Modulebar, MMM-Profilepicture, MMM-Videoplayer

            cowboysdudeC 1 Reply Last reply Reply Quote 0
            • cowboysdudeC Offline
              cowboysdude Module Developer @Snille
              last edited by

              @Snille said in IR Frame doesn’t rotate:

              @AlessandroRa Hi! Unfortunately the manufacturer do not have any drivers for ARM.
              I ended up with using it as a normal “HID” device. I have to rotate the frame manually with this command in SSH: DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
              But I cant get it to stick after reboot. So, I have to do it after every boot when everything has started.
              I did not get the xinnput_calibration values to stick either. I’m in Rasbian Jessie Lite.

              Write it in an .sh file and have it run everytime you boot up ;)

              1 Reply Last reply Reply Quote 0
              • AlessandroRaA Offline
                AlessandroRa @yawns
                last edited by

                @yawns I tried, there’s no way to open it…

                @Snille I’ve installed xinput_calibrator and I’ve just tried to start the mirror with the command you wrote, but it still doesn’t recognise the xinput command… How did you do it?

                @cowboysdude smart move!

                SnilleS 1 Reply Last reply Reply Quote 1
                • SnilleS Offline
                  Snille Module Developer @AlessandroRa
                  last edited by

                  @AlessandroRa Just install xinput sudo apt-get install xinput
                  Then you are good to go. :)
                  @cowboysdude I have to know when to start the actual xinput command, I have tried in the “startup” for LXDE, with CRON and in “openbox”:es “statup”. For some reason I cant get it to “take”. I have not made a .sh file, true. But where / when to execute it? :)

                  If you cant find it, make it and share it!
                  Modules: MMM-homeassistant-sensors, MMM-Modulebar, MMM-Profilepicture, MMM-Videoplayer

                  cowboysdudeC 1 Reply Last reply Reply Quote 0
                  • cowboysdudeC Offline
                    cowboysdude Module Developer @Snille
                    last edited by

                    @Snille

                    Edit the file:

                    sudo crontab -e
                    Add line to file (here a python script):

                    @reboot python3 /home/pi/Desktop/example.py &

                    SnilleS peemoellerP 2 Replies Last reply Reply Quote 0
                    • SnilleS Offline
                      Snille Module Developer @cowboysdude
                      last edited by

                      @cowboysdude It worked when added to a sh script! Good call! :) Before I just tested with the xinput command directly in the autostart file, but that did not work. So now instead I just created a script called xin.sh.
                      nano ~/xin.sh
                      Then added
                      DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
                      There should actually be 3 spaces between “Multi touch” and “Multi touch overlay device”. For some reason the board removes the extra spaces here.

                      You can actually find the “name” of the device with this command DISPLAY=:0.0 xinput list
                      Shows something like this:

                      ⎡ Virtual core pointer id=2 [master pointer (3)]
                      ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
                      ⎜ ↳ Multi touch Multi touch overlay device id=6 [slave pointer (2)]
                      ⎣ Virtual core keyboard id=3 [master keyboard (2)]
                      ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]

                      Depending on what you have connected to your RPi. :)

                      So, after creating the xin.sh I added that to the autostart file for LXDE:
                      Like this:
                      nano ~/.config/lxsession/LXDE/autostart
                      Added at the end of the file.
                      @/home/pi/xin.sh
                      Restarted and it works. :)

                      If you cant find it, make it and share it!
                      Modules: MMM-homeassistant-sensors, MMM-Modulebar, MMM-Profilepicture, MMM-Videoplayer

                      cowboysdudeC 1 Reply Last reply Reply Quote 2
                      • cowboysdudeC Offline
                        cowboysdude Module Developer @Snille
                        last edited by cowboysdude

                        @Snille Oddly enough you may have accidently solved my problem too! :) I’m getting a 32" IR touch frame… this may work for me as well!! So Thank you! :)

                        What kind of IR touch frame do you have and where did you get it?

                        Thanks!

                        SnilleS 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 1 / 3
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy