After downloading the toolchain and replacing my current toolchain folder with that toolchain folder im still getting the memory permission error. Does this mean that there is something wrong in the way I am declaring my motion profile controller?
I declare my Chassis as below outside of the autonomous
sorry my english is poor.
I don’t use okapilib either.
I’ve seen this question in the forum before. I suggest asking the author.
Is okapilib Built-in route planning? A* algorithm?
All good. Yea the motion profile is used for the robot to follow a path given by xy coordinates and an angle. I was actually able to get it to work thanks for the help!
Thanks everyone for the help! I was actually able to get it to work.
I moved my chassisControllerFactory and AsyncControllerFactory to be created in a functions file and then in that functions file I made a function in which I generated the path and set the target.
In my autonomous file I just call the function that generates the path and sets the target.
That made the motion profile work and got rid of the memory permission error. I’m not 100% sure why but it worked. If anyone knows why it worked I would love to deepen my understanding.
I wrote odometers for students
I don’t know how to adjust the sensor accurately. It often leads to errors in odometer.
Students are reluctant to use it.
The vex path is relatively simple. There’s no need for astar.
If astar is used, it seems that a special controller has to be written for astar.
Traditional controllers can cause stutters .
I’ve only written 2 paths but I assume there is no limitation on the number of paths. I think shorter paths have slower speeds but most paths are the same speed.