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

Responses to functional broadcast request may be of a much wider range of IDs #255

Open
peplin opened this issue Aug 2, 2014 · 1 comment
Assignees

Comments

@peplin
Copy link
Member

peplin commented Aug 2, 2014

See openxc/uds-c#5 - we wil need to set the CAN acceptance filter to bypass if you send a functional broadcast request and check all incoming messages for matching PID and mode.

@peplin peplin self-assigned this Aug 5, 2014
@peplin peplin added the ready label Aug 30, 2014
@peplin peplin added in progress and removed ready labels Oct 7, 2014
@peplin
Copy link
Member Author

peplin commented Oct 7, 2014

I've decided to backlog this since I don't know a good solution and I don't have any more details on the proprietary messages involved to try and understand it better. If anyone is experiencing this firsthand, please let me know if you could help. I've added more notes in openxc/uds-c#5.

@peplin peplin removed the in progress label Oct 7, 2014
peplin added a commit that referenced this issue Oct 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant