NodeManager: plugin for a rapid development of battery-powered sensors
-
THEN MY NODE WILL BE CONNECTED TO A BATTERY 3.6 VOLT AA 2600 MAH, SO I DO NOT RIGHT CONNECTIONS? BUT I HAVE TO CHANGE OTHER PARAMETERS TO BEING 3.6?
TANKS@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
THEN MY NODE WILL BE CONNECTED TO A BATTERY 3.6 VOLT AA 2600 MAH, SO I DO NOT RIGHT CONNECTIONS? BUT I HAVE TO CHANGE OTHER PARAMETERS TO BEING 3.6?
TANKSIf directly connected to the battery you don't need any other connection. To set minimum and maximum voltage to have an accurate battery percentage level calculated you need to use e.g.:
nodeManager.setBatteryMin(2.7); nodeManager.setBatteryMax(3.6);So the percentage will be calculated between the two values.
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
THEN MY NODE WILL BE CONNECTED TO A BATTERY 3.6 VOLT AA 2600 MAH, SO I DO NOT RIGHT CONNECTIONS? BUT I HAVE TO CHANGE OTHER PARAMETERS TO BEING 3.6?
TANKSIf directly connected to the battery you don't need any other connection. To set minimum and maximum voltage to have an accurate battery percentage level calculated you need to use e.g.:
nodeManager.setBatteryMin(2.7); nodeManager.setBatteryMax(3.6);So the percentage will be calculated between the two values.
-
@mar.conte ok, this looks better, the node is presenting correctly and I see the sensor triggering continuously. You still have a lot of radio failures while sending but this is another story and it is not related to the issue but keep in mind you are losing a few messages.
Now, if I look at the digital read of the pin waking up the board (V=):SWITCH I=1 P=3 V=1This is HIGH so the board correctly wakes up. Since the signal apparently stays high, the board goes in and out of sleep so looks like an expected behavior. The are a couple of functions available to prevent this (setTriggerTime() and setDebounce()) but before giving direction I'd ask you to measure the voltage at pin 3 with a multimeter because it looks like the motion sensor goes HIGH and stay HIGH for a long time. If we know this timeframe, we can adjust the settings accordingly. Btw you should have the same behavior with the example sketch at https://www.mysensors.org/build/motion.
Thanks@user2684
Solved
I solved it by putting settriggertime (5000) setdebounce (50); also solved the supply problems because if power is ftdi with the sensor was always high, with batteries the pir is stable and works well
thanks for the support
This is my reprap printed house for my project
-
@user2684
Solved
I solved it by putting settriggertime (5000) setdebounce (50); also solved the supply problems because if power is ftdi with the sensor was always high, with batteries the pir is stable and works well
thanks for the supportThis is my reprap printed house for my project
@mar.conte great to hear it is working now! For anybody else interested in these parameters, setDebounce() will set a debounce interval, e.g. the value of the input is checked after the interval from the wakeup so to avoid false positives, while seTriggerTime() ignore any input after the pir has triggered to avoid the sensor to trigger continuously. Btw, very nice and clean packaging!
-
-
Can I suggest updated sourceforge to say that the code has been moved to github, and leaving little else there? That way it's easier to update everything in the same place. I was browsing on sourceforge for a while and wondering "Why isn't this on github instead?" It wasn't even until I came back and started skimming this thread that I realized it was moved to github.
-
I have a problem, my node is in sleep for 60 minutes and hourly reads the battery voltage but when you wake the pir is high and in addition to the high volts sends me even then the controller sends me a pir pir movement false; how can I avoid it?
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
I have a problem, my node is in sleep for 60 minutes and hourly reads the battery voltage but when you wake the pir is high and in addition to the high volts sends me even then the controller sends me a pir pir movement false; how can I avoid it?
So you are saying when the node wakes up not from the pir interrupt at the end of the sleeping cycle to report battery level, is it also reporting a V_TRIPPED with payload 0? Thanks
-
Can I suggest updated sourceforge to say that the code has been moved to github, and leaving little else there? That way it's easier to update everything in the same place. I was browsing on sourceforge for a while and wondering "Why isn't this on github instead?" It wasn't even until I came back and started skimming this thread that I realized it was moved to github.
@JonnyDev13 said in NodeManager: plugin for a rapid development of battery-powered sensors:
Can I suggest updated sourceforge to say that the code has been moved to github
Good advice thanks! I've changed the website link on Sourceforge as well as added a note in the description and redirected the "Support" link.
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
I have a problem, my node is in sleep for 60 minutes and hourly reads the battery voltage but when you wake the pir is high and in addition to the high volts sends me even then the controller sends me a pir pir movement false; how can I avoid it?
So you are saying when the node wakes up not from the pir interrupt at the end of the sleeping cycle to report battery level, is it also reporting a V_TRIPPED with payload 0? Thanks
-
@JonnyDev13 said in NodeManager: plugin for a rapid development of battery-powered sensors:
Can I suggest updated sourceforge to say that the code has been moved to github
Good advice thanks! I've changed the website link on Sourceforge as well as added a note in the description and redirected the "Support" link.
@user2684 Looks great!
-
if it reports "no motion" it is not a false alarm. The important thing is it must report when there is "motion"
@gohan said in NodeManager: plugin for a rapid development of battery-powered sensors:
if it reports "no motion" it is not a false alarm. The important thing is it must report when there is "motion"
Agree with what @gohan says. But I'll look into this anyway @mar-conte, reporting no motion when waking up should not happen even if it is a minor issue (https://github.com/mysensors/NodeManager/issues/71). What should not happen at all is reporting motion (payload 1) but as far as I've understood this is the case.
Thanks -
@gohan said in NodeManager: plugin for a rapid development of battery-powered sensors:
if it reports "no motion" it is not a false alarm. The important thing is it must report when there is "motion"
Agree with what @gohan says. But I'll look into this anyway @mar-conte, reporting no motion when waking up should not happen even if it is a minor issue (https://github.com/mysensors/NodeManager/issues/71). What should not happen at all is reporting motion (payload 1) but as far as I've understood this is the case.
Thanks -
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
So with version 1.5 do I solve my problem too?
I'll look into it by then. Feel free to follow the github issue to see how it will evolve. Thanks!
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
I noticed that the battery report if set to one hour does not happen every hour ...
More details please :-) Does not happen at all, it is not regular, happens every other hour, etc. what is the case?
Thanks!
