We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Many of AS's drivers allow the use of kvaser_interface for CAN communications but this currently requires either:
kvaser_interface
kvaser_can_bridge
To achieve both flexibility and efficiency, kvaser_can_bridge should be re-written as a nodelet.
The text was updated successfully, but these errors were encountered:
JWhitleyWork
No branches or pull requests
Many of AS's drivers allow the use of
kvaser_interface
for CAN communications but this currently requires either:kvaser_interface
as a library which must be a design-time decision or;kvaser_can_bridge
as a stand-alone node, which is memory-inefficient because each message must be published to a network socket.To achieve both flexibility and efficiency,
kvaser_can_bridge
should be re-written as a nodelet.The text was updated successfully, but these errors were encountered: