No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.

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

Kvaser CAN interface for ROS device drivers.

Additional Links

Maintainers

  • AutonomouStuff Software Development Team

Authors

  • Joshua Whitley
  • Daniel Stanek

Kvaser ROS Interface API

CircleCI

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 and linking against 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-dkms

      sudo 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).

CHANGELOG

Could not convert RST to MD: No such file or directory - pandoc

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged kvaser_interface at answers.ros.org

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

Kvaser CAN interface for ROS device drivers.

Additional Links

Maintainers

  • AutonomouStuff Software Development Team

Authors

  • Joshua Whitley
  • Daniel Stanek

Kvaser ROS Interface API

CircleCI

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 and linking against 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-dkms

      sudo 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).

CHANGELOG

Could not convert RST to MD: No such file or directory - pandoc

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged kvaser_interface at answers.ros.org

No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.