• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.

MMM-Navigate, Navigation inside MagicMirror with Rotary Encoder

Scheduled Pinned Locked Moved System
45 Posts 6 Posters 16.8k Views 5 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.
  • A Offline
    AxLed Module Developer
    last edited by Jan 9, 2021, 10:59 AM

    @keineAhnung123,

    thanks for feedback.
    first:
    Idea A:

    • maybe the pin 19 is the problem, because it is not only a GPIO pin rather it has SPI features. Can you change to BCM16 (and change it in config.js as well) and try it?

    Idea B:

    • Do you use capacitors for debouncing? If not, you can change debouncing value of following line: https://github.com/Ax-LED/MMM-Navigate/blob/master/node_helper.js#L37

    second:

    • Which module should start hidden? MMM-Navigate?

    third:
    I tried to reproduce on my pi 3 and get no error, so i checked the code.
    You can add following line as new line 19 in node_helper.js
    var lastdir = '';

    AxLED

    1 Reply Last reply Reply Quote 0
    • K Offline
      keineAhnung123
      last edited by Jan 9, 2021, 11:13 AM

      @AxLed
      I will try that later. Thanks
      And yes, i want to start MMM-Navigate hidden. Is that possible?

      1 Reply Last reply Reply Quote 0
      • A Offline
        AxLed Module Developer
        last edited by Jan 9, 2021, 7:41 PM

        @keineAhnung123 ,

        informations to your second issue:
        Your request is not provided by MMM-Navigate, maybe it is possible with one of the following modules (untested):

        • MMM-ModuleScheduler
        • MMM-ModuleToggle

        AxLED

        1 Reply Last reply Reply Quote 0
        • K Offline
          keineAhnung123
          last edited by Jan 10, 2021, 10:36 AM

          Hello @AxLed

          first

          • Idea A: didnt solve the problem. Still no click
          • Idea B: I tried capacitors and software debouncing. Still no click

          I will use this python script to get the click working:

          import RPi.GPIO as GPIO
          GPIO.setmode(GPIO.BCM)
          BUTTON_PIN = 16
          GPIO.setup(BUTTON_PIN, GPIO.IN, pull_up_down = GPIO.PUD_UP)
          

          and start it within node_helper.js:

          var child_process = require('child_process');
          
          module.exports = NodeHelper.create({
          	// Subclass start method.
            start: function() {
          		var self = this;
          		this.loaded = false;
          		this.createRoutes();
          		child_process.execFile('python', ['/home/pi/MagicMirror/modules/MMM-Navigate/ky-040-initialisieren.py']);
          	},
          

          Now it works.

          Btw: In intializeRotary-function (node_helper.js) there ist a CLK and DT.read and also a CLK and DT.watch instruction. For the SW there is only a SW.watch but not a read instruction. Is that right? Just wanted to mention. Im not an expert in programming.

          third
          Yes, the error is gone :)

          1 Reply Last reply Reply Quote 0
          • A Offline
            AxLed Module Developer
            last edited by Jan 10, 2021, 1:34 PM

            @keineAhnung123 ,

            thanks for your patience.
            to first:
            it seems to be something with the pullup / pulldown resistors, see also https://github.com/fivdi/onoff#configuring-pullup-and-pulldown-resistors
            See also the new “gpio” config command (https://www.raspberrypi.org/forums/viewtopic.php?f=117&t=208748)
            So here is another idea, can you try (based on informations mentione above):

            • (i suppose your SW pin is 16)
            • add following line in /boot/config.txt
              gpio=16=ip,pu
              Meaning: sets your GPIO 16 as input (ip) and pull up (pu)
            • if this doesnt work try:
              gpio=16=ip,pd
              Meaning: sets your GPIO 16 as input (ip) and pull down (pd)

            Maybe this way MMM-Navigate works without the python script.

            To SW.watch you mentioned, this is ok, as i dont need to know the initial state of SW.

            to third:

            • i added the line in node_helper.js in the github repo.

            Regards

            AxLED

            1 Reply Last reply Reply Quote 0
            • K Offline
              keineAhnung123
              last edited by Jan 10, 2021, 2:46 PM

              @AxLed Now it works with gpio=16=ip,pu
              Do the changes in boot.txt affect the Raspberry Pi in any way i have to know?

              Thanks a lot so far :)

              1 Reply Last reply Reply Quote 0
              • A Offline
                AxLed Module Developer
                last edited by AxLed Jan 10, 2021, 4:21 PM Jan 10, 2021, 4:20 PM

                @keineAhnung123,

                great to hear it works, i will update the readme at github.
                The line in config.txt only tells the pi at boottime, that GPIO16 is set to input and the internal resistor is set to pullup. So there is nothing else to know unless you change your GPIO Pins for something else.
                @Eisblume maybe this is a solution for your issue.

                AxLED

                R 1 Reply Last reply Nov 12, 2022, 11:07 PM Reply Quote 0
                • R Offline
                  robiv8 @AxLed
                  last edited by Nov 12, 2022, 11:07 PM

                  @AxLed
                  also a great modul from you :-)

                  I have tested and works fine. Two questions.

                  When I press any selection, the module disappears.
                  It fades out and the module below it jumps up. Why?

                  Is it possible to control the MMM-Dreambox module with it? That would be great, of course.

                  Thanks in advance

                  1 Reply Last reply Reply Quote 0
                  • A Offline
                    AxLed Module Developer
                    last edited by Nov 15, 2022, 7:32 PM

                    @robiv8

                    the modul MMM-Navigate disappears by design. If it is faded out and you use rotary or button it comes back on (fades in).

                    Yes MMM-Dreambox can be controlled bei MMM-Navigate, see https://github.com/Ax-LED/MMM-Dreambox#further-options

                    AxLED

                    R 1 Reply Last reply Nov 30, 2022, 8:24 PM Reply Quote 0
                    • R Offline
                      robiv8 @AxLed
                      last edited by robiv8 Nov 30, 2022, 8:34 PM Nov 30, 2022, 8:24 PM

                      @AxLed
                      Hallo,
                      is there a way to deaktivate this Fade out? i want it olways on.
                      Thanks Robi

                      OK Sorry, i found it by my self :-)
                      in MMM-Navigate.js
                      // this.hide(10000);

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 3
                      • 4
                      • 5
                      • 4 / 5
                      • 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