Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    WDT not available

    Scheduled Pinned Locked Moved WiPy 2&3
    wdt wipy
    11 Posts 5 Posters 2.6k Views 5 Watching
    Loading More Posts
    • 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.
    • T Offline
      Thosch42
      last edited by

      I try to use the WDT starting with

      from machine import WDT
      

      but I get the following:

      Running main.py
      Traceback (most recent call last):
        File "<stdin>", line 9, in <module>
      ImportError: cannot import name WDT
      

      I think my WiPy is up to date:

      (sysname='WiPy', nodename='WiPy', release='1.6.12.b1', version='v1.8.6-593-g8e4ed0fa on 2017-04-12', machine='WiPy with ESP32')
      

      What's wrong?

      Cheers,
      Thomas

      L 1 Reply Last reply Reply Quote 2
      • L Offline
        livius @Thosch42
        last edited by

        @Thosch42
        look here - same topic
        https://forum.pycom.io/topic/1098/lopy-wdt

        think about people first, then computers

        1 Reply Last reply Reply Quote 0
        • T Offline
          Thosch42
          last edited by

          But mine IS a WiPy, so it should be implemented, isn't it?

          Otherwise, please correct the documentation. It's so frustrating to try out things, try to find the failure, and then get told that it's simply not implemented.

          L 1 Reply Last reply Reply Quote 1
          • L Offline
            livius @Thosch42
            last edited by livius

            @Thosch42
            Please precise
            Wipy1 or Wipi2
            I assume that Wipi2 because you have software version 1.6.12.b1

            And python modules are same for all boards
            with some exception like Lora, Sigfox, LTE-M specific
            Then link is valid for you

            think about people first, then computers

            1 Reply Last reply Reply Quote 0
            • B Offline
              BetterAuto Pybytes Beta
              last edited by

              Same error, and I have a WiPy 2.0. Livius I'm not clear from your answer if you're saying this is an issue also on the WiPy 2.0, yes?

              L 1 Reply Last reply Reply Quote 1
              • L Offline
                livius @BetterAuto
                last edited by

                @BetterAuto
                Yes, if WDT is not avaiable (now) it is not avaiable on all boards, Wipy2, Lopy...

                think about people first, then computers

                1 Reply Last reply Reply Quote 0
                • B Offline
                  BetterAuto Pybytes Beta
                  last edited by

                  Then I concur with the OP and request that the docs be updated.

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    BetterAuto Pybytes Beta
                    last edited by

                    Does this mean there is no watchdog running in the background either, just not at all functional?

                    1 Reply Last reply Reply Quote 0
                    • B Offline
                      BetterAuto Pybytes Beta
                      last edited by

                      FYI I plan to work around this issue by using one of the two alarms on a DS3231 RTC. It has an alarm with a resolution of one second; So to keep the system from staying locked up I'll constantly reset the alarm to 10 (or some number) seconds in the future. If the alarm ever fires it'll hit the WiPy reset.

                      1 Reply Last reply Reply Quote 0
                      • S Offline
                        smssms
                        last edited by

                        I updated my WiPy 2.0 late last week and there still does not seem to be a WDT available.

                        My workaround was to put all the code in a 'Try/Except' and have a machine.reset() in the 'Except'.

                        J 1 Reply Last reply Reply Quote 0
                        • J Offline
                          jmarcelino @smssms
                          last edited by

                          @smssms
                          According to the log the WDT module only became available this past Friday in version 1.7.2.

                          https://forum.pycom.io/topic/1326/firmware-release-1-7-2-b1

                          1 Reply Last reply Reply Quote 1

                          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
                          • 1 / 1
                          • First post
                            Last post

                          Pycom on Twitter

                          Pycom