All Projects → astuff → kvaser_interface

astuff / kvaser_interface

Licence: MIT license
A Kvaser CAN interface ROS abstraction layer.

Programming Languages

C++
36643 projects - #6 most used programming language
CMake
9771 projects

Projects that are alternatives of or similar to kvaser interface

rclshark
Tool for ROS 2 IP Discovery + System Monitoring
Stars: ✭ 32 (-55.56%)
Mutual labels:  ros2
Awesome Robotic Tooling
Tooling for professional robotic development in C++ and Python with a touch of ROS, autonomous driving and aerospace.
Stars: ✭ 1,876 (+2505.56%)
Mutual labels:  ros2
dockerfiles
Dockerfiles I use for development
Stars: ✭ 64 (-11.11%)
Mutual labels:  ros2
ros2-ORB SLAM2
ROS2 node wrapping the ORB_SLAM2 library
Stars: ✭ 41 (-43.06%)
Mutual labels:  ros2
raspimouse ros2 examples
ROS 2 examples for Raspberry Pi Mouse
Stars: ✭ 29 (-59.72%)
Mutual labels:  ros2
dynamixel control
ros2_control packages for ROBOTIS Dynamixel
Stars: ✭ 69 (-4.17%)
Mutual labels:  ros2
raspimouse2
ROS 2 node for Raspberry Pi Mouse
Stars: ✭ 23 (-68.06%)
Mutual labels:  ros2
Nindamani-the-weed-removal-robot
Nindamani, the AI based mechanically weed removal robot
Stars: ✭ 73 (+1.39%)
Mutual labels:  ros2
awesome-webots
Awesome Webots
Stars: ✭ 46 (-36.11%)
Mutual labels:  ros2
vscode ros2 workspace
A template for using VSCode as an IDE for ROS2 development.
Stars: ✭ 527 (+631.94%)
Mutual labels:  ros2
isaac ros visual odometry
Visual odometry package based on hardware-accelerated NVIDIA Elbrus library with world class quality and performance.
Stars: ✭ 101 (+40.28%)
Mutual labels:  ros2
rmw ecal
ROS2 middleware based on eCAL
Stars: ✭ 30 (-58.33%)
Mutual labels:  ros2
DDS-Router
The DDS Router is an application developed by eProsima that allows, using Fast DDS, to communicate by DDS protocol different networks.
Stars: ✭ 34 (-52.78%)
Mutual labels:  ros2
ROS
ROS机器人操作系统 学习(写于2020年夏)
Stars: ✭ 102 (+41.67%)
Mutual labels:  ros2
isaac ros dnn inference
Hardware-accelerated DNN model inference ROS2 packages using NVIDIA Triton/TensorRT for both Jetson and x86_64 with CUDA-capable GPU
Stars: ✭ 67 (-6.94%)
Mutual labels:  ros2
trac ik
ROS 2 port of `trac_ik`, an alternative Inverse Kinematics solver to the popular inverse Jacobian methods in KDL.
Stars: ✭ 14 (-80.56%)
Mutual labels:  ros2
li slam ros2
ROS2 package of tightly-coupled lidar inertial ndt/gicp slam
Stars: ✭ 160 (+122.22%)
Mutual labels:  ros2
ros-docker-gui
ROS Docker Containers with X11 (GUI) support [Linux]
Stars: ✭ 137 (+90.28%)
Mutual labels:  ros2
ros msft camera
This ROS node uses Windows Media Foundation's frame server to efficiently process camera frames.
Stars: ✭ 17 (-76.39%)
Mutual labels:  ros2
iknet
Inverse kinematics estimation of ROBOTIS Open Manipulator X with neural networks
Stars: ✭ 27 (-62.5%)
Mutual labels:  ros2

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 <kvaser_interface/kvaser_interface.h> and linking against libros_linuxcan.so or the stand-alone node kvaser_can_bridge can communicate with a CAN device independently.

Installation

The kvaser_interface package depends on the Kvaser CANLIB API. You can install the Kvaser CANLIB from source directly from Kvaser, however the easiest way to install is using our ppa which distributes them as deb packages:

sudo apt-add-repository ppa:astuff/kvaser-linux
sudo apt update
sudo apt install kvaser-canlib-dev kvaser-drivers-dkms

Now that the dependencies are installed, we can install kvaser_interface:

sudo apt install apt-transport-https
sudo sh -c 'echo "deb [trusted=yes] https://s3.amazonaws.com/autonomoustuff-repo/ $(lsb_release -sc) main" > /etc/apt/sources.list.d/autonomoustuff-public.list'
sudo apt update
sudo apt install ros-$ROS_DISTRO-kvaser-interface

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

TOOLS

list_channels

A simple tool with no ROS dependencies which returns a list of all Kvaser devices and channels available on those devices.

canmonitor

A simple tool with no ROS depedencies to output the CAN messages received on a given channel index (-i - default: 0) and bitrate (-b - default: 500000) to the terminal.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].