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 part hangs on creation #1160

Open
mgagvani opened this issue Feb 9, 2024 · 3 comments
Open

VESC part hangs on creation #1160

mgagvani opened this issue Feb 9, 2024 · 3 comments

Comments

@mgagvani
Copy link
Contributor

mgagvani commented Feb 9, 2024

Hello,

I am trying to use the VESC part with a VESC 6 and Traxxas brushless motor. The VESC is brand-new and has 6.02 firmware. I have tested it to work while connected to my personal computer by running the PyVESC example code: https://github.com/LiamBindle/PyVESC/blob/master/pyvesc/examples/motor_example.py

However, when connected to the Nvidia Jetson Orin Nano on my car, it gets stuck in a spinlock trying to read the firmware version:
IMG_8105

Any ideas why this is happening? The permissions have been set, and I've followed the instructions on the F1-Tenth website to create the udev rules, so if there is anything else I need to do to get it working with DonkeyCar on top of that it would be great to include that in the DonkeyCar docs.

Pinging @sisaha9 as the creator of this, hopefully you can provide some insight.

@sisaha9
Copy link
Contributor

sisaha9 commented Feb 9, 2024

I don't have access to a physical VESC anymore to test post graduation. I can ask some folks to test out. But regarding the error itself it looks like it's getting stuck here in the VESC library and not in any Donkeycar code itself

https://github.com/LiamBindle/PyVESC/blob/master/pyvesc/VESC/VESC.py#L89

If you are able to make the example work I would double check the parameters you are inputting in both

@mgagvani
Copy link
Contributor Author

mgagvani commented Feb 9, 2024

That's the weird thing: the example works on my own laptop, but not on the Jetson. So there is some underlying difference in how serial works on x86 laptops and the Jetson which is causing this error. Thanks for your help.

@sisaha9
Copy link
Contributor

sisaha9 commented Feb 10, 2024

I guess one thing to make sure is if you are in the dialout group. Otherwise you may need to use sudo to read that port

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