bee-mar / mmm-simple-swiper Goto Github PK

I performed all steps in correct order without any error but I was only able to swipe once and then the pages were not changing. Sensors are kept 1.5cm apart, and I tried swiping fast and slow but nothing working

I think maybe it is due to improper connection of sensors ? you showed to connect 1k ohm resistor to echo pin but i don't think that's safe for gpio pins, see this tutorial ModmyPi

Please keep me updated if you find any solution (Thanks in Advance)

hi,
when i was trying to install the module an error get out. When i run "make build-depends" , nodeJS Dependencies install well but Wiring Pi not. In the screen I see this:

==========================
Getting WiringPi Dependency
===========================

Cloning to 'wiringPi' ...
fatal: unable to connect to git.drogon.net:
git.drogon.net [0: 188.246.205.22]: errno = Connection refused
git.drogon.net [1: 2a03: 9800: 10: 7b :: 2]: errno = The network is unattainable

/ bin / sh: 6: cd: can not cd to wiringPi

What i can do to solution this?
Thanks

Hi Bee-Mar,

the last two days I have played around with your module but have not been able to get it to work properly. When the module is freshly loaded through a MM restart, it sometimes works for several swipes. I first thought that my sensors might be faulty, but this does not seem to be the case as I constantly get measurements when using the swiper executable fom CLI.
As you have written in your manual you also faced this behavior when configuring delays smaller than 1000. Unfortunately my system is not stable even with much higher values.
I therefore have changed the code of the swiper application a little to only send data to stdout when the difference of the measurements of the LEFT and RIGHT sensor has a defined value ( in my case 20). With this change I have made sure, that the node_helper will not be overwhelmed by to much data. This change, however, did not completely resolve the issue.
As the next step I got rid of the sudo workaround by adding the pi user to the gpio group ( sudo usermod -a -G gpio pi ) and changing the child_process in node_helper.js:

// creating demon spawn
const { spawn } = require('child_process');
const child = spawn( __dirname + '/swiper', [ JSON.stringify(payload), ], { detached: true, stdio: [ 'ignore' ] });
child.unref();

With this in place MM can now be properly shut down.

I have recognized, that when the measurements stop to propagate from the swiper application to the modules node_helper the sensors have to be power-cycled to use them again. It seems to me as if the trigger lines somehow stop to work.
This does not happen when using swiper from the command line.

Did you find out what could be the cause of the issue and how it could be fixed ?

Thank you for your kind help.
Andreas

I have a problem, already when connecting the sensors something does not seem to work. I have tested all cables and all power connections by using different sensors. It seems to be due to the GPIOs, only the combination of trigger in 25 and echo in 26 seems to work. So I manage to get on one sensor, but the second one doesn't work. I have no idea where the problem could be. I thank you in advance for any help.

joyful greetings Daniel

Hi, I have installed this module as per the instructions, but there's an error when I enter the command" make build_depends && make". it shows that "make: No rule to make target 'Build_depends'. Stop."
The Ultrasonic sensors are not detecting any movements, and hence there is no change in the pages.
Kindly reply

Jumps around from page to page as though something is moving in front of it. Sprinkled holy water and preformed an exorcism, so good on the ghost. Replaced the sensors with two new ones and the issue remains. Just jumps from page to page.

I followed the instructions and worked perfectly until I ran the Magic Mirror and found that my Calander is missing and my pages are toggling on their own. Please help :/

excludes is actually a byproduct of how MMM-pages hides modules:

MM.getModules()
  .exceptWithClass(this.config.excludes)
  .exceptWithClass(this.config.modules[this.curPage])
  .enumerate(module => module.hide(
    self.config.animationTime / 2,
    { lockString: self.identifier }
  ));

Since exceptWithClass basically acts like a filter, I was thinking of the config option as an exclusion filter, ergo excludes. You're right though, the name leaks implementation detail, and it doesn't make much sense for end users. I've changed it to fixed (while still supporting excludes) to hopefully help people with this. No real action is required by you, unless you want to use fixed instead—this issue was just an FYI.

I followed all the instructions as in the readme but when i ran the mirror there is no response and in the terminal i was popped up with an error called no main js file. Hence i had to rename the main js file and the error disappeared but still nothings working.
Thanks for replying!

Are you sure about the wiring ? On the GPIO pinout diagram, 23 then 24 and on your wiring picture, you notice 24 then 23.