My solution was to use a low drop out voltage high ripple rejection ratio voltage regulator 3V0 to power the PIR. That special voltage regulator is fed from the booster 3V3, that keeps the voltage to the PIR rock solid. The booster is noisy especially when the arduino goes from sleep to wake and back.
Sorry, just getting around to try to get MYSController setup and I can't seem to get it sorted out to connect to my serial GW that is attached to my VeraLite.
Here is what I have done to try to get connected:
ser2net -C 5003:raw:0:/dev/ttyACM0:115200
I also tried
ser2net -C 5003:raw:0:/dev/ttyUSB0:115200
Next I launch MYSController on my PC and in the config window under TCP/IP tab set the IP to the IP of Vera and port to 5003.
Hit connect and I get the following....
2/17/2016 13:04:54 INFO Connected to 192.168.0.108:5003
2/17/2016 13:04:54 INFO Unknown message, Msg=
Port already in use by another process, dc=1
2/17/2016 13:04:54 RX
Port already in use by another process
For those of you have have done this before...any suggestion?
A couple of questions.
@darazs Good to know. I think the output of the booster is very dependent on the current draw and, of course, every booster is a little different.
@mrlynx
Downside to using 3xAA would be size.
@Andreas-Maurer
I would prefer to use the 3 pin header and not have wires coming from multiple places, but you are correct.
This post outlines how to run a PIR sensor with 2xAA batteries and use interrupts to sleep a 3V3 8 MHz Arduino between both tripped and not-tripped states. This seems pretty straight forward, however there are a couple subtleties.
Here, I will describe how I overcame this problem by modifying the PIR to work at 3V0.
Steps:
PIR PCB modification
The board should look like the photo shown below
Prepare the power source for the PIR
Figure 1. Comparison of the output of the 3V3 booster and the LDO 3V0 regulator while the Arduino is sleeping. AC coupled scope termination. Note: the LDO is multiplied by 100 and offset for clarity.
Figure 2. Motion at around 1100 ms causes the PIR output to go high and the Arduino to wake up. Note the output from the booster quiets down and the output from the LDO is smooth. PIR and LDO outputs are offset for clarity.
Figure 3. Entering sleep once the PIR goes from tripped to non-tripped state. Once the Arduino starts to sleep, the output from the booster becomes noisy, while the LDO is smooth. PIR and LDO outputs are offset for clarity.
Here is my example code (nothing fancy and much of it is borrowed from various places).
//This program will test the PIR using interrupts
#include <avr/sleep.h>
#include <avr/interrupt.h>
void setup()
{
Serial.begin(115200);
pinMode(3,INPUT);
digitalWrite(3, LOW);
pinMode(4,OUTPUT);
//Signal PIR startup by flashing an LED
digitalWrite(4,HIGH);
delay(5000);
digitalWrite(4,LOW);
delay(200);
}
void loop()
{
//Come out of sleep and read state of PIR pin
bool flag = digitalRead(3);
if (flag == true)
{
Serial.println("tripped");
digitalWrite(4,HIGH);
}
else
{
Serial.println("not tripped");
digitalWrite(4,LOW);
}
delay(100);
sleepNow();
}
void sleepNow()
{
Serial.println("Entering Sleep");
// Set pin 3 as interrupt and attach handler:
attachInterrupt(1, wakeUp, CHANGE);
delay(100);
// Choose our preferred sleep mode:
set_sleep_mode(SLEEP_MODE_PWR_DOWN);
// Set sleep enable (SE) bit:
sleep_enable();
// Put the device to sleep:
sleep_mode();
// Upon waking up, sketch continues from this point.
sleep_disable();
}
void wakeUp(void)
{
detachInterrupt(1);
}
One last thing, it is necessary to attach a pull-down resistor on the PIR output pin in order to help the signal line go low when transitioning to the non-tripped state.
@hek okay, I guess I was being stupid....
With this msg constructor...
MyMessage msgVolt(CHILD_ID_VOLT, V_VAR1);
With this type def...
float batteryV = sensorValue * 0.003363075;
I had the following thinking that I had turned on auto ack...
gw.send(msgVolt.set(batteryV, 1));
but that sets the decimal places to "1". So, if I want to set the decimal places to "2" and enable auto ack it would look like this...?
gw.send(msgVolt.set(batteryV, 2),1);
Thanks again.
Hey guys,
Just wondering if someone would be so kind as to help me figure out how to use setters to send a payload with more decimal places than the standard custom variable.
I saw that perhaps I could construct the msg "on the fly", but I don't know the proper syntax to get that accomplished. Even easier, I would simply like to send a custom variable with two decimal places (or however many one should like). Right now the default is a single decimal place as I gather from the data that is being sent currently.
In the plainest terms, I would like to send the battery voltage in a format X.XX using a custom variable, but using the standard custom variable constructor the payload is X.X.
Thanks for your help.
Awesome, when I order new boards I will include this feature. One question, does your implementation require the use of both SDA and SCL pins or just SDA? I think I prefer the larger SOT-23 package that only has SDA pin. I guess simply, one-wire or I2C?
Thanks.
Thank you for this excellent work. I look forward to using it in my network. I just have a couple questions regarding setting up the GUI. I've read through this thread several times, but still have a couple of gaps in my understanding.
Is the gateway that interfaces with the GUI an additional gateway which listens to, and sends node messages and updates? That is, additional to one that is interfaced with the controller (in my case a serial gateway connected to a Vera controller)?
If my the answer to my first question is, yes, it is an additional gateway, is the code defining the operation different such that is does not interfere with the 'true' gateway? Or is the code the same (standard serial gateway sketch) but simply does not interfere?
Do the nodes require the MYSBootloader in order to show up in the 'messages' tab, or will 'messages' tab show all node traffic regardless of bootloader? Of course for over the air (OTA) sketch updates it needs the MYSBootloader.
Are these the correct steps to setup operation:
a) download and extract the files.
'b) place the bootloader folder into /arduino/hardware path such that the MYSBootloader and the associated boards show up in the 'tools->boards' menu.
c) connect an Arduino with the gateway sketch to a computer using a USB cable (for the serial connection).
d) run MYSController.exe (on windows) and select the COM port of the serial gateway in the configuration.
e) hit connect and node traffic will show up in the 'messages' tab.
If this is correct (and now that I write it down) it seems pretty straightforward, but I didn't see it explicitly described elsewhere. Sorry to be such a beginner, and thanks for straightening me out if I'm incorrect in any step.