|
kvaser_interface package from pacifica_dbw_ros repodbc dbw_pacifica_can dbw_pacifica_joystick_demo dbw_pacifica_joystick_speed_demo dbw_pacifica_msgs kvaser_interface pacifica_dbw pdu pdu_msgs |
Package Summary
| Tags | No category tags. |
| Version | 2.0.2 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/NewEagleRaptor/pacifica-dbw-ros.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2019-04-30 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
Package Description
Additional Links
Maintainers
- AutonomouStuff Software Development Team
Authors
- Joshua Whitley
- Daniel Stanek
Kvaser ROS Interface API
This package was developed as a standardized way to access Kvaser CAN devices from ROS. It can either be used as a development API
by including the header libros_linuxcan.so or the stand-alone node
kvaser_can_bridge can communicate with a CAN device independently.
The following are required prerequisites:
-
The Kvaser CANLIB API (https://www.kvaser.com/downloads/)
-
Can be downloaded directly or installed through PPA:
sudo apt-add-repository ppa:jwhitleyastuff/linuxcan-dkmssudo apt update && sudo apt install -y linuxcan-dkms For Linux kernel 4.13 or higher, version 5.21 or higher of CANLIB is required
-
can_msgs
The kvaser_can_bridge Node
TOPICS
can_tx [can_msgs::Frame]
This topic is published by the node. It expects to have other nodes subscribe to it to receive data which are sent by the CAN device.
can_rx [can_msgs::Frame]
This topic is subscribed to by the node. It expects to have data published to it which are intended to be received by the CAN device.
PARAMETERS
~can_hardware_id
This is the Kvaser Hardware ID (serial number) of the connected device.
~can_circuit_id
This is the 0-based index of the channel number on the specific hardware device designated by the ~can_hardware_id.
~can_bit_rate
This is the communication rate to be used on the CAN channel in bits per second (default: 500000).
Could not convert RST to MD: No such file or directory - pandoc
Wiki Tutorials
Source Tutorials
Launch files
- launch/kvaser_can_bridge.launch
-
- can_hardware_id [default: 10051]
- can_circuit_id [default: 0]
- can_bit_rate [default: 500000]
Messages
Services
Plugins
Recent questions tagged kvaser_interface at answers.ros.org
|
kvaser_interface package from pacifica_dbw_ros repodbc dbw_pacifica_can dbw_pacifica_joystick_demo dbw_pacifica_joystick_speed_demo dbw_pacifica_msgs kvaser_interface pacifica_dbw pdu pdu_msgs |
Package Summary
| Tags | No category tags. |
| Version | 2.0.2 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/NewEagleRaptor/pacifica-dbw-ros.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2019-04-30 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
Package Description
Additional Links
Maintainers
- AutonomouStuff Software Development Team
Authors
- Joshua Whitley
- Daniel Stanek
Kvaser ROS Interface API
This package was developed as a standardized way to access Kvaser CAN devices from ROS. It can either be used as a development API
by including the header libros_linuxcan.so or the stand-alone node
kvaser_can_bridge can communicate with a CAN device independently.
The following are required prerequisites:
-
The Kvaser CANLIB API (https://www.kvaser.com/downloads/)
-
Can be downloaded directly or installed through PPA:
sudo apt-add-repository ppa:jwhitleyastuff/linuxcan-dkmssudo apt update && sudo apt install -y linuxcan-dkms For Linux kernel 4.13 or higher, version 5.21 or higher of CANLIB is required
-
can_msgs
The kvaser_can_bridge Node
TOPICS
can_tx [can_msgs::Frame]
This topic is published by the node. It expects to have other nodes subscribe to it to receive data which are sent by the CAN device.
can_rx [can_msgs::Frame]
This topic is subscribed to by the node. It expects to have data published to it which are intended to be received by the CAN device.
PARAMETERS
~can_hardware_id
This is the Kvaser Hardware ID (serial number) of the connected device.
~can_circuit_id
This is the 0-based index of the channel number on the specific hardware device designated by the ~can_hardware_id.
~can_bit_rate
This is the communication rate to be used on the CAN channel in bits per second (default: 500000).
Could not convert RST to MD: No such file or directory - pandoc
Wiki Tutorials
Source Tutorials
Launch files
- launch/kvaser_can_bridge.launch
-
- can_hardware_id [default: 10051]
- can_circuit_id [default: 0]
- can_bit_rate [default: 500000]