Hey guys, just had a couple of doubts on how to use Jerry.IO properly.
So when I boot it up and start a path, how do I make a path that allows for the robot to travel backwards with the same orientation? For example, if the bot moves forward 3 inches, how do I make it move backward 3 inches while maintaining its pose?
I am using a 6M, 8W drivetrain, and I want to make a path that effectively gets the AWP every time. What format should I use (LemLib Odom, Rigid Code Gen, etc) ?
A path is generally based upon what library you use.
If you are new, I would suggest looking up the LemLib docs to get started on configuring your robot to get it working, however you can tinker with Jerry.IO to make a path beforehand and then use the path when you configure your project for LemLib. Note that LemLib uses PROS, which nowadays is identical to VEXCode.
Uninstall VEXCode extension in VSCode and install PROS Extension. Then I would install clangd extension and disable the intellisense.
Super sorry for the late reply, but thanks! One quick question, is Jerry.IO solely made for LemLib? Like my team currently uses EZ-Template and liftshifting is going to take some time.
The EZ template does not have any pathing generation as far as I am aware of, so it won’t be compatible for Jerry IO. As far as I know it, Jerry IO simply generates code for a robot to transverse a path. Any library can work if it has the back-end for such code, however the EZ template doesn’t.
Oh? Is it reliable, like has it been thoroughly tested? If not, that’s fine too.
And does it read the path files from Jerry.IO or does it have something else?