Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Didou
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by Didou

    • Didou

      NRF5 Hardware module crash after while
      My Project • • Didou  

      16
      1
      Votes
      16
      Posts
      131
      Views

      waspie

      @ncollins Are you currently working with any NRF5x? Do you have a working motion/contact sketch for the NRF52?
    • Didou

      Using Sensebender gateway MYSX_D3_INT Interrupts
      Troubleshooting • • Didou  

      14
      0
      Votes
      14
      Posts
      664
      Views

      Didou

      @didou Tryed it today with no luck. The behavior is globally simillar loop() { unsigned long currentMillis = millis(); // Check Sensors global timer if (currentMillis - previousMillis >= intervalMillis) { previousMillis = currentMillis; readSensors(); } // Check Triggers if (myIsrTriggerVar1) { #ifdef MY_DEBUG Serial.println("Motion Interrupt"); #endif send(MotionMsg.set("1")); // reset flag myIsrTriggerVar1 = false; } } I got the interrupt then mysensor message -> 13:13:07.719 -> 0;255;3;0;5;1 (Motion/V_trigger -> 1) Then I have to wait for 120 seconds before being able to do an other interrup Not before I have this message 13:15:07.621 -> 0;255;3;0;5;0 (Motion/V_trigger -> 0) which is not in my own code How often i do read the sensors do ot have any impact within the 120 seconds or outside of them. I have roufly checked the mysensor code and haven't seen any such define behavior for Motion/V_trigger)