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.

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

PCM Device Health Check #25

Open
AraknosDe opened this issue Apr 10, 2017 · 3 comments
Open

PCM Device Health Check #25

AraknosDe opened this issue Apr 10, 2017 · 3 comments
Assignees

Comments

@AraknosDe
Copy link

Check PCM health so that if it fails the correct driving constants are restored. Find the time it takes to do a health check, and time the checking loop accordingly so we don't use too many resources.

@AraknosDe AraknosDe modified the milestone: Ready For Championships Apr 11, 2017
@rothvann
Copy link
Contributor

As of right now I have no idea how to communicate over CAN to check the PCM or any CAN devices for that matter.

@AraknosDe
Copy link
Author

Please contact Thad in the next few days to ask him about it. If he cannot answer the question, ask on Chief Delphi.

@ThadHouse
Copy link

ThadHouse commented Apr 12, 2017

What exactly do you want to do?
https://www.chiefdelphi.com/forums/showpost.php?p=1529415&postcount=10
This will work, but it won't exactly be fast (as realistically CAN has a lot of unnecessary lag), so don't call this exactly at runtime. You should be able to fairly easily modify this code to only check the PCM you are looking for however, and that should speed it up enough to be called in the normal teleop loop safely.

@rothvann rothvann removed the wontfix label Jul 12, 2017
@rothvann rothvann removed this from the Ready For Championships milestone Jul 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants