ROS with VESC motor controller

ROS Kinetic and VESC, a simple recipe on Ubuntu 16.04


- Install ROS kinetic full desktop
http://wiki.ros.org/kinetic/Installation/Ubuntu

- Install ROS serial
apt-get install ros-kinetic-serial

- Create catkin_ws
mkdir catkin_ws
cd catkin_ws
mkdir src
cd src
catkin_init_workspace

- Install VESC driver packages
git clone from:
https://github.com/mrsd16teamd/loco_car

To compile, need
loco_car/utilities/ackermann_msgs
loco_car/utilities/vesc

Compile
 . /opt/ros/kinetic/setup.sh
cd ~/catkin_ws
catkin_make

 Each terminal needs setup, unless append to .bashrc
. /opt/ros/kinetic/setup.sh
. ~/catkin_ws/devel/setup.sh

Terminal 1. Run roscore
roscore

Using VESC STM32F407 as serial port, mapped as /dev/ttyACM0
$ lsusb
..
Bus 001 Device 010: ID 0483:5740 STMicroelectronics STM32F407
$ cat /sys/class/tty/ttyACM0/device/uevent
DEVTYPE=usb_interface
DRIVER=cdc_acm
PRODUCT=483/5740/200
TYPE=2/0/0
INTERFACE=2/2/1
MODALIAS=usb:v0483p5740d0200dc02dsc00dp00ic02isc02ip01in00

Terminal 2. Run VESC node, wants port as parameter
rosrun vesc_driver vesc_driver_node _port:=/dev/ttyACM0
Output:
[ INFO] [1523385642.355806199]: Connected to VESC with firmware version 2.18

Terminal 3. Subscribe telemetry
rostopic echo /sensors/core
Sample output:
header:
  seq: 3292
  stamp:
    secs: 1523385708
    nsecs: 216151628
  frame_id: ''
state:
  voltage_input: 13.3
  temperature_pcb: 28.1
  current_motor: 0.0
  current_input: 0.0
  speed: 0.0
  duty_cycle: 0.001
  charge_drawn: 3.0
  charge_regen: 0.0
  energy_drawn: 48.0
  energy_regen: 0.0
  displacement: 11472.0
  distance_traveled: 11472.0
  fault_code: 0

Terminal 4. Manually publish messages to 2000rpm speed topic (at 20hz)
rostopic pub -r 20 /commands/motor/speed -- std_msgs/Float64 2000






Original loco_car article (highly appreciated),
https://github.com/mrsd16teamd/loco_car/wiki/VESC





Kommentit

Lähetä kommentti

Tämän blogin suosituimmat tekstit

Matrox G200eW 1920x1200 resolution on Ubuntu 16.04

Recipe for Matrox G200eW 1920x1200 resolution on Ubuntu 16.04. (Note: Needs patch for Xorg, not easy for beginners) I am using X9SCM-F with built-in VGA controller and IPMI. Only x8 PCIe slots on this motherboard. My path is laid out below, I did not retry all of this once got it working. The resolution is most likely restricted for KVM to work. I am not interested on monitor redirection on this system, I use this system as workstation. I use 16bpp bit depth on Xserver and seems to work. The patch workings are courtesy of Samir Ibradzic. Credits to other authors whose writings helped me figure this out. https://lists.x.org/archives/xorg-devel/2012-January/028523.html The patch is for this specific PCI identifier controller in driver source, pMga->is_G200WB = (pMga->Chipset == PCI_CHIP_MGAG200_WINBOND_PCI);{ PCI_CHIP_MGAG200_WINBOND_PCI,     "mgag200 eW Nuvoton" },  $ lspci -s 03:03.0 03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G2
Lue lisää

Docker CUDA Runtime

Kuva
In this post I'm documenting rough steps to use CUDA inside Docker.  Initial status is the nvidia-smi is working but Docker does not recognize the nvidia runtime. After following the instructions on  https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html root@Moebels:/home/sampsa# curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \ && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \ sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \ sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list \ && \ sudo apt-get update deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://nvidia.github.io/libnvidia-container/stable/deb/$(ARCH) / #deb [signed-by=/usr/share/keyrings/nvidia-contai
Lue lisää

VESC open source motor controller

I use VESC for controlling brushless motor. Control target is closed loop control with feedback sensing on electrical robot locomotion. Purpose of this blog entry is to keep record atleast for myself. VESC is developed by Benjamin Vedder. The design is open source and comes in different version on hardware and software. VESC supports various operation modes with feedback by back EMF, hall sensors and encoders. Documentation for modes could be improved. Per code review the hall sensor cannot be not used as primary feedback method, rather the code relies on back EMF. Due to this, the calibration of feedback is necessary to get the motor working properly. With bad calibration, the back EMF feedback is not stable. Unstable operations can be seen as oscillating control signal, which can also result power rails to become unstable due to power surging to motor. STM32F4 supports quadrature encoder A/B signals by hardware and VESC uses this functionality also. I have not tested quadrat
Lue lisää