• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Watchdog settings via EVOK

    Official EVOK API
    3
    3
    53
    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.
    • S
      smontosa last edited by

      Hi.
      On Debian Buster, at version:

      dpkg -l evok
      Desired=Unknown/Install/Remove/Purge/Hold
      | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
      |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
      ||/ Name           Version      Architecture Description
      +++-==============-============-============-========================================
      ii  evok           2.4.8        armhf        UniPi API based on the Tornado webserver
      
      

      evok is not able to change board watchdog state.
      Please, ¿is there some way (Evok or whatever) to set on board watchdog?

      Thanks.

      Martin Kudláček 1 Reply Last reply Reply Quote 0
      • Martin Kudláček
        Martin Kudláček administrators @smontosa last edited by

        Hi @smontosa,
        you are correct. There is indeed some problem with setting the watchdog via Evok. I reported this to our developers and make sure this will be fixed in 2.4.10.

        As a workaround, you can set the watchdog via ModbusTCP. You can use mbpoll (not preinstalled, can be installed via apt update && apt install -y mbpoll):

        # enable the MWD
        mbpoll 127.0.0.1 -a 1 -0 -1 -r 6 1
        # set timeout to 3333ms
        mbpoll 127.0.0.1 -a 1 -0 -r 1008 3333
        # write this settings to the NVRAM
        mbpoll 127.0.0.1 -a 1 -0 -1 -t 0 -r 1003 1
        

        Best regards,
        Martin

        1 Reply Last reply Reply Quote 0
        • M
          martin_triska administrators last edited by martin_triska

          Hello @smontosa,

          please try to download the current version 2.4.10. The issue should be fixed. Please note that watchdog settings (same as other parameters) are stored in RAM memory by default. To burn it into non-volatile memory (FLASH), use the appropriate coil 1003 or call the separate REST request on the same endpoint with parameter nv_save=1.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post