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

Can you clatify the can bus connections for this setup? #3

Open
console-beaver opened this issue Dec 16, 2019 · 11 comments
Open

Can you clatify the can bus connections for this setup? #3

console-beaver opened this issue Dec 16, 2019 · 11 comments

Comments

@console-beaver
Copy link

We are trying to use this code, but it doesn't work in our setup. We still can control gimbal/blaster via Robomaster app and can capture the canbus packets from the "intelligent" controller, but we cannot control motors ("motion" controller) via both joystick and Robomaster app.

Can you please clarify how to you connect Can Bus'es in your setup?

@Radziula7
Copy link

Hi @console-beaver . I have the same problem. I can't controll motors (gimbal is working). I use 2 CAN-BUS and I use the oldest code version. Can you tell how did you solve a problem? It's really important for me. Thanks 👍

@console-beaver
Copy link
Author

console-beaver commented Nov 16, 2020

Generally speaking, the old code with two CAN Bus connections where the controller was sandwiched between CAN Busses as a pass-thru, had alot of issues. I'm now using the newer code which got rid of "Intelligent controller" and it works for me.

Also make sure you keep holding L2 button on your controller, otherwise it wont send any messages.

@krvcz
Copy link

krvcz commented Nov 17, 2020

Generally speaking, the old code with two CAN Bus connections where the controller was sandwiched between CAN Busses as a pass-thru, had alot of issues. I'm now using the newer code which got rid of "Intelligent controller" and it works for me.

Also make sure you keep holding L2 button on your controller, otherwise it wont send any messages.

I had the same problem, but when i change code on the newest (one CAN) robot didn't respond.

@Radziula7
Copy link

Radziula7 commented Nov 17, 2020

125486964_2860655454218088_3963727592021439660_n
@console-beaver look at this photo. Did you have the same problem when you used code "Intelligent controller"? I use this code and robot dosen't respond. Thanks for anwser 👍

@console-beaver
Copy link
Author

Where you are getting these messages from? ds4drv? Make sure you start ds4drv with elevated privileges, i.e. via sudo.

@krvcz
Copy link

krvcz commented Nov 17, 2020

Where you are getting these messages from? ds4drv? Make sure you start ds4drv with elevated privileges, i.e. via sudo.

The same problem . Roscore is working and when i want roslaunch then i see the same error. I think ROS is working, but it's something wrong in robomaster ros code

EDIT: sudo ds4drv work fine

@Radziula7
Copy link

@console-beaver , I had problem when i tried start "roslaunch ros_robomaster_s1_bridge robomaster_s1_bridge_joy.launch". Drives ds4drv work good. I don't know what is a problem. What do you think, what is not ok ? Thanks :)

@console-beaver
Copy link
Author

@krvcz, @Radziula7 make sure that you are using the older version of robomaster_s1_bridge_joy ROS code. The old version uses udp protocol to communicate with the bridge controller, the newer version uses USB.

@Radziula7
Copy link

@console-beaver. I also uploaded the newest code version and I connected the wires correctly (robomaster led is blue). I uploaded program in ros and I tried testing ros program, robomaster didn't move :(

@console-beaver
Copy link
Author

console-beaver commented Nov 18, 2020

Try to troubleshoot the joystick controls, to make sure it's working under linux.

  1. Make sure your remote controller type is correctly set in robomaster_s1_bridge_joy.launch, i.e. ps3/ps4/xbox/etc

  2. Make sure that /dev/input/js0 and /dev/hidraw0 devices are being created with correct permissions, so your user can read them, i.e.:

root@nx-tegra194:~# ls -la /dev/input/js0
crw-rw-r--+ 1 root input 13, 0 Aug 31 16:53 /dev/input/js0

root@nx-tegra194:~# ls -la /dev/hidraw0
crw------- 1 root root 509, 0 Aug 31 16:35 /dev/hidraw0

  1. Test the remote control with jstes, i.e.:

sudo jstest /dev/input/js0

@Radziula7
Copy link

@console-beaver thanks for your advice. Can I ask you when i have a problem ? :)

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

3 participants