Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Watchdog Timer #24

Open
Shengw3n opened this issue Jan 19, 2025 · 1 comment
Open

Watchdog Timer #24

Shengw3n opened this issue Jan 19, 2025 · 1 comment
Assignees
@JeffreyYJackson

Comments

@Shengw3n
Copy link
Collaborator

Add a watchdog timer to avoid code lock up
@Shengw3n Shengw3n moved this to Todo in Thrust Vectoring II Jan 19, 2025
@JeffreyYJackson JeffreyYJackson moved this from Todo to In Progress in Thrust Vectoring II Jan 26, 2025
@JeffreyYJackson JeffreyYJackson self-assigned this Jan 26, 2025
@JeffreyYJackson JeffreyYJackson moved this from In Progress to Currently Under Review in Thrust Vectoring II Jan 26, 2025
@Shengw3n Shengw3n moved this from Currently Under Review to Done in Thrust Vectoring II Jan 26, 2025
@Shengw3n Shengw3n closed this as completed by moving to Done in Thrust Vectoring II Jan 26, 2025
@Shengw3n Shengw3n moved this from Done to Currently Under Review in Thrust Vectoring II Jan 26, 2025
@Shengw3n
Copy link
Collaborator Author

@JeffreyYJackson Can you test the watchdog timer by intentionally breaking the I2C protocol and see if it detects? (maybe remove the IMU while running, and see if watchdog detects)

@JeffreyYJackson JeffreyYJackson moved this from Currently Under Review to In Progress in Thrust Vectoring II Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffreyYJackson JeffreyYJackson

Labels
None yet
Projects
Thrust Vectoring II
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JeffreyYJackson @Shengw3n