You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your code and documents are awesome! Thank you for your sharing.
In SOES_CIA402_AX58100, you set watchdogcnt in check_dc_handler(). The comments and the variable names indicate that you consider each count of watchdogcnt as a nanosecond.
Yet, the DIG_process(DIG_PROCESS_WD_FLAG) in each while(), which subtracts the watchdog value between the duration, which is the processing time of while() (dozens of micorsenconds in my case). So the watchdog value is almost never below zero.
I am wondering there's any misunderstanding of the program about watchdog in your code?
The text was updated successfully, but these errors were encountered:
qiayuanl
changed the title
Watchdog is not working.
Watchdog is not working
Dec 6, 2022
Well, in normal operation watchdog value is expected not to reach zero.
To be honest, I have not done final parameter tweaking. This value is from bringup stage, when I was mostly concerned with making it large enough, so that ESC would not reset itself in loop. This surely can be done better
Your code and documents are awesome! Thank you for your sharing.
In SOES_CIA402_AX58100, you set
watchdogcnt
incheck_dc_handler()
. The comments and the variable names indicate that you consider each count ofwatchdogcnt
as a nanosecond.Yet, the
DIG_process(DIG_PROCESS_WD_FLAG)
in eachwhile()
, which subtracts the watchdog value between the duration, which is the processing time ofwhile()
(dozens of micorsenconds in my case). So the watchdog value is almost never below zero.I am wondering there's any misunderstanding of the program about watchdog in your code?
The text was updated successfully, but these errors were encountered: