Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Hardware
  3. Sleep/Wake/TXRx Cycle

Sleep/Wake/TXRx Cycle

Scheduled Pinned Locked Moved Hardware
27 Posts 6 Posters 11.1k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • hekH Offline
    hekH Offline
    hek
    Admin
    wrote on last edited by
    #21

    @Yveaux said:

    @hek I had a quick look at the Sensor.cpp code and all sends seem to boil down to Sensor::sendWrite.
    And what's in there? "WAIT FOR ACK" which can take 50ms???

    This is the old inter-node ack mechanism used in 1.3 (long story why we had to do it like this). This should not be mixed up with full route ack messages used from source to final destination.

    This code has been replaced by the NRF build-in ack/retransmission functionality in 1.4.

    YveauxY 1 Reply Last reply
    0
    • hekH hek

      @Yveaux said:

      @hek I had a quick look at the Sensor.cpp code and all sends seem to boil down to Sensor::sendWrite.
      And what's in there? "WAIT FOR ACK" which can take 50ms???

      This is the old inter-node ack mechanism used in 1.3 (long story why we had to do it like this). This should not be mixed up with full route ack messages used from source to final destination.

      This code has been replaced by the NRF build-in ack/retransmission functionality in 1.4.

      YveauxY Offline
      YveauxY Offline
      Yveaux
      Mod
      wrote on last edited by
      #22

      @hek OK, I'll repeat with 1.4 then!

      http://yveaux.blogspot.nl

      1 Reply Last reply
      0
      • T Offline
        T Offline
        therik
        wrote on last edited by
        #23

        Hi guys,

        I checked again, with another scope (1 GHz Tektronix) and I get 1.44s total time. It must be hardware or software related, not measurement related. Any other ideas to fix? I need to run the node without a gateway, because the measurement must be made off-site from vera and the gateway.

        YveauxY 1 Reply Last reply
        0
        • Z Offline
          Z Offline
          Zeph
          Hero Member
          wrote on last edited by
          #24

          @therik said:

          No modification: current from battery: 2.24 mA, current to pro-mini: 1.63 mA
          Remove LED: current form battery: 144 µA, current to pro-mini: 104 µA
          Remove LED and regulator: current from battery: 48 µA, current to pro-mini: 23 µA

          This refers to removing a power-on LED from the APM, right? (The LED from the china booster already being removed).

          And you were feeding power to the APM's VCC (ie: output of it's onboard linear regulator) until the third measurement, where you removed the unused regulator as well from the APM?

          That's excellent low power for a cheap booster!

          Did you remove the LED and reg with a simple soldering iron?


          Only thing is, that bottom trace looks kinda choppy. No problems with powering the radio directly from the booster?

          (All this leaving aside the slow timing. I understand that 1.3's timeouts were 50ms and it probably did a bunch of them because there was nobody to respond, but why would the lower current first part - presumably doing sensor measurements - take so long?).

          1 Reply Last reply
          0
          • T therik

            Hi guys,

            I checked again, with another scope (1 GHz Tektronix) and I get 1.44s total time. It must be hardware or software related, not measurement related. Any other ideas to fix? I need to run the node without a gateway, because the measurement must be made off-site from vera and the gateway.

            YveauxY Offline
            YveauxY Offline
            Yveaux
            Mod
            wrote on last edited by
            #25

            @therik You are running at 8Mhz, right? Maybe do a quick I/o pin toggle test to toggle it a fast as possible and measure pulse on a scope. That test we can easily repeat when in doubt.

            http://yveaux.blogspot.nl

            1 Reply Last reply
            0
            • T Offline
              T Offline
              therik
              wrote on last edited by
              #26

              Okay, did the toggle test using the delayMicroseconds() method. I tested 96 µs, 1000 µs, and 10 ms and all were very close to the set delay, pins 6, 5, and 4 respectively. (@ 8 MHz the delay is a multiple of 8 µs).

              It must be the fact that I'm trying the MySensors temperature sketch 'gatewayless'. I wonder if I can modify the sketch to not wait for an ACK. Of course, when I get a scope at home the 'gatewayless' operation will not be needed.

              YveauxY 1 Reply Last reply
              0
              • T therik

                Okay, did the toggle test using the delayMicroseconds() method. I tested 96 µs, 1000 µs, and 10 ms and all were very close to the set delay, pins 6, 5, and 4 respectively. (@ 8 MHz the delay is a multiple of 8 µs).

                It must be the fact that I'm trying the MySensors temperature sketch 'gatewayless'. I wonder if I can modify the sketch to not wait for an ACK. Of course, when I get a scope at home the 'gatewayless' operation will not be needed.

                YveauxY Offline
                YveauxY Offline
                Yveaux
                Mod
                wrote on last edited by Yveaux
                #27

                @therik What about the first part of the scope chart, starting from 0 sec?
                What is the sketch doing there for more than half a second? It was reading temperatures, but for how many sensors?

                http://yveaux.blogspot.nl

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                14

                Online

                11.7k

                Users

                11.2k

                Topics

                113.1k

                Posts


                Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • MySensors
                • OpenHardware.io
                • Categories
                • Recent
                • Tags
                • Popular