Skip to content
New issue

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

VESC error #26

Open
Chenyuhancc opened this issue Oct 28, 2022 · 1 comment
Open

VESC error #26

Chenyuhancc opened this issue Oct 28, 2022 · 1 comment

Comments

@Chenyuhancc
Copy link

I'm working on the reinforcement learning by using F1/10 car. The VESC had died every time after 5 episode. Thank you!!

this is the log:
process[vesc/high_level/ackermann_cmd_mux_nodelet_manager-8]: started with pid [9311]
process[vesc/high_level/ackermann_cmd_mux-9]: started with pid [9317]
process[vesc/low_level/ackermann_cmd_mux_nodelet_manager-10]: started with pid [9324]
process[vesc/low_level/ackermann_cmd_mux-11]: started with pid [9329]
process[vesc/ackermann_to_vesc-12]: started with pid [9337]
process[vesc/vesc_driver-13]: started with pid [9347]
process[vesc/vesc_to_odom-14]: started with pid [9367]
process[vesc/throttle_interpolator-15]: started with pid [9383]
process[base_link_to_imu-16]: started with pid [9391]
process[base_link_to_laser-17]: started with pid [9400]
process[base_link_to_base_footprint-18]: started with pid [9407]
terminate called after throwing an instance of 'serial::IOException'
what(): IO Exception (5): Input/output error, file /home/user/catkin_ws/src/f1tenth_system/serial/src/impl/unix.cc, line 488.
terminate called recursively
[vesc/vesc_driver-13] process has died [pid 9347, exit code -6, cmd /home/user/catkin_ws/devel/lib/vesc_driver/vesc_driver_node __name:=vesc_driver __log:=/home/user/.ros/log/a8a2a986-56a8-11ed-bca4-00044bf24fbb/vesc-vesc_driver-13.log].
log file: /home/user/.ros/log/a8a2a986-56a8-11ed-bca4-00044bf24fbb/vesc-vesc_driver-13*.log

@hzheng40
Copy link
Member

This is not enough information to diagnose the problem. Can you only launch teleop without your own nodes?
I/O errors usually mean USB connection issues, udev rule setup issues, vesc firmware issues, etc.
Are you using a working USB port? And is the vesc detected by checking lsusb?
Did you set up the udev rules for the vesc correctly? Check if ls /dev/sensors show anything.
What is the vesc hardware that you're using? What is the firmware version that you're using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants