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. Troubleshooting
  3. pulsemeter reset itself

pulsemeter reset itself

Scheduled Pinned Locked Moved Troubleshooting
3 Posts 2 Posters 1.3k 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.
  • SweebeeS Offline
    SweebeeS Offline
    Sweebee
    wrote on last edited by
    #1

    Today my pulsemeter reset itself today (pulse count):

    10:36:45.054 <- I_LOG_MESSAGE  0;0;3;0;9;read: 8-8-0 s=1,c=1,t=24,pt=5,l=4:115944
    10:37:25.039 <- I_LOG_MESSAGE  0;0;3;0;9;read: 8-8-0 s=1,c=1,t=24,pt=5,l=4:4
    

    How can this happen? The controller didn't send a 0. I created a little sketch that sended the old value back and now it works again. But i don't want this to happen again.

    B 1 Reply Last reply
    0
    • SweebeeS Sweebee

      Today my pulsemeter reset itself today (pulse count):

      10:36:45.054 <- I_LOG_MESSAGE  0;0;3;0;9;read: 8-8-0 s=1,c=1,t=24,pt=5,l=4:115944
      10:37:25.039 <- I_LOG_MESSAGE  0;0;3;0;9;read: 8-8-0 s=1,c=1,t=24,pt=5,l=4:4
      

      How can this happen? The controller didn't send a 0. I created a little sketch that sended the old value back and now it works again. But i don't want this to happen again.

      B Offline
      B Offline
      BulldogLowell
      Contest Winner
      wrote on last edited by
      #2

      @Sweebee said:

      How can this happen?

      did you have a power loss or maybe a little power fluctuation during a write?

      you could store the past few (50 or so) readings into a circular EEPROM buffer (for wear leveling) and always check to see that the number is being incremented properly by constantly reviewing the stored data versus your active variable.

      1 Reply Last reply
      0
      • SweebeeS Offline
        SweebeeS Offline
        Sweebee
        wrote on last edited by
        #3

        Well i could save it every 10th pulse and check if its higher than the 10 pulses before that? if not, current pulse is the pulse that was saved 10 pulses before?

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        16

        Online

        12.0k

        Users

        11.2k

        Topics

        113.4k

        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