为什么PIR传感器在nodeMCU / ESP8266板上保持高电平?

时间:2016-03-09 22:20:37

标签: arduino esp8266 ifttt

我有一个PIR传感器连接到Amica nodeMCU板,从VIN路由5v并通过USB端口连接进行测试。当动作被发现时,它会连接到互联网并将数据发送到IFTTT,我会在手机上收到通知。

当我打开电源时,PIR会暂停校准,然后立即变为高电平并触发我在手机上收到的检测到动作的电话。然而,从那时起,它永远不会变为低电平,但即使没有动作,每5-8分钟也会发出另一个HIGH电话。

测试

  • 尝试使用单独的5v供应给PIR发生同样的事情
  • 我尝试了两种重新触发模式(H& L)并且经历了相同的结果
  • Adafruit featherwing huzzah板也是如此。
  • 我在没有微控制器的情况下对PIR进行了测试,并且可以确认正常运行 指示灯
  • 我使用相同代码的Arduino Nano测试,正常运行 - 点亮led

我的代码 Arduino Playground PIR Project

的修改版本
//Sends IFTTT every 5 minutes it detects motion

#include <ESP8266WiFi.h>
//WiFi Settings

// Set up macros for wifi and connection.
#define SSID "my-network"    // SSID
#define PASS "mypassphrase"      // Network Password
#define HOST "maker.ifttt.com"  // Webhost
//-------------------------------
const char* streamId   = "test";
const char* privateKey = "mysecretkey";

//PIR Settings
//the time we give the sensor to calibrate (10-60 secs according to the datasheet)
int calibrationTime = 10;        

//the time when the sensor outputs a low impulse
long unsigned int lowIn;         

//the amount of milliseconds the sensor has to be low 
//before we assume all motion has stopped
long unsigned int pause = 5000;  


int  interval = 1000; // Wait between dumps
boolean lockLow = true;
boolean takeLowTime;  
int ledPin = 1;
int pirPin = 2;    //the digital pin connected to the PIR sensor's output
int nPIR_detect;
int motion = 2;

int minSecsBetweenUpdates = 300; // 5 minutes
long lastSend = -minSecsBetweenUpdates * 1000l;
//-------------------------------

// Begin Setup
void setup(){
  Serial.begin(115200);
  pinMode(pirPin, INPUT);
  digitalWrite(pirPin, LOW);

  //give the sensor some time to calibrate
  Serial.print("calibrating sensor ");
  for(int i = 0; i < calibrationTime; i++){
    Serial.print(".");
    delay(1000);
    }
  Serial.println(" done");
  Serial.println("SENSOR ACTIVE");
  delay(50);
   nPIR_detect = 0;  

  // Test ESP8266 module.
  Serial.println("AT");
  delay(5000);
  if(Serial.find("OK")){
    connectWiFi();
  }
}

void loop(){
 if(digitalRead(pirPin) == HIGH){
       digitalWrite(BUILTIN_LED, HIGH);   //the led visualizes the sensors output pin state
       if(lockLow){  
         //makes sure we wait for a transition to LOW before any further output is made:
         lockLow = false;            
         Serial.println("---");
         Serial.print("motion detected at ");
         Serial.print(millis()/1000);
         Serial.println(" sec"); 
         sendData(String(motion));
         delay(50);
         }         
         takeLowTime = true;
       }

     if(digitalRead(pirPin) == LOW){       
       digitalWrite(BUILTIN_LED, LOW);  //the led visualizes the sensors output pin state

       if(takeLowTime){
        lowIn = millis();          //save the time of the transition from high to LOW
        takeLowTime = false;       //make sure this is only done at the start of a LOW phase
        }
       //if the sensor is low for more than the given pause, 
       //we assume that no more motion is going to happen
       if(!lockLow && millis() - lowIn > pause){  
           //makes sure this block of code is only executed again after 
           //a new motion sequence has been detected
           lockLow = true;                        
           Serial.print("motion ended at ");      //output
           Serial.print((millis() - pause)/1000);
           Serial.println(" sec");
           delay(50);
           }
       }
}

void sendData(String motion){

  //Send the motion to IFTTT value1
  Serial.print("connecting to ");
  Serial.println(HOST);

  // Use WiFiClient class to create TCP connections
  WiFiClient client;
  const int httpPort = 80;
  if (!client.connect(HOST, httpPort)) {
    Serial.println("connection failed");
    return;
  }

  // We now create a URI for the request
  String url = "/trigger/";
  url += streamId;
  url += "/with/key/";
  url += privateKey;
  url += "?value1=";
  url += "motion";

  Serial.print("Requesting URL: ");
  Serial.println(url);

  // This will send the request to the server
  client.print(String("GET ") + url + " HTTP/1.1\r\n" +
               "Host: " + HOST + "\r\n" + 
               "Connection: close\r\n\r\n");
  delay(10);

  // Read all the lines of the reply from server and print them to Serial
  while(client.available()){
    String line = client.readStringUntil('\r');
    Serial.print(line);
  }

  Serial.println();
  Serial.println("closing connection");

}

boolean connectWiFi(){
  Serial.println("AT+CWMODE=1");
  delay(2000);
  String cmd="AT+CWJAP=\"";
  cmd+=SSID;
  cmd+="\",\"";
  cmd+=PASS;
  cmd+="\"";
  Serial.println(cmd);
  delay(5000);
  if(Serial.find("OK")){
    Serial.println("Connection");
    return true;
  }
  else{
    Serial.println("No Connection");
    return false;
  }
}

为什么PIR传感器在nodeMCU / ESP8266板上保持高电平?

从本质上讲,我从来没有看到串行消息&#34;动作结束于......&#34;

2 个答案:

答案 0 :(得分:4)

几个月之后,但希望能帮助其他人解决同样的问题。几个星期我感到很沮丧并尝试了几个具有相同(令人沮丧)结果的PIR模块,我发现问题是由于我在nodeMCU开发板中闪存固件的方式造成的。

我有ESP-12E并使用以下命令上传固件:

esptool.py --port /dev/cu.SLAB_USBtoUART --baud 115200 write_flash -fm dio -fs 32m 0x00000 /Users/dev/nodemcu-firmware.bin

问题是 -fm dio (双闪存I / O模式)参数。一些ESP8266模块,包括某些(并非所有)NodeMCU板上的ESP-12E模块,都是双I / O,固件只有在用 - flash_mode dio -fm闪存时才会启动dio 但在我的情况下是我所有头痛的根源。一旦我在没有这个选项的情况下刷新固件,一切都开始像魅力一样。

答案 1 :(得分:2)

能够通过用V_cc的PIR插入Node MCU的V_in来解决问题。似乎PIR需要~5V且只有V_in才能提供这种电压。早些时候,我每隔x秒就获得一系列HIGH,当插入3.3v时。