-
Notifications
You must be signed in to change notification settings - Fork 18
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
Motion replay/performance capture/recording #34
Conversation
This is a port of https://github.com/Spartronics4915/2017-Demo-ActionReplay to the real codebase. One addition is that the program is stored and loaded from SmartDashboard in two double[]s named Drivetrain_Replay_Forward and Drivetrain_Replay_Rotation. These need to be completely empty strings to save a recording, otherwise it won't overwrite it and your recording will be erased when the code restarts.
This uses the "Drivetrain_Replay_Folder" key in SmartDashboard. It's essential that this points at a folder with read and write access on the robot. It must be an absolute path, trailing slashes shouldn't matter however. The path defaults to /home/lvuser, which isn't _too_ awful but it will get overwritten by the next recording. Example: - Log in as admin@roboRIO-4915-FRC.local - su lvuser - mktemp -d - Copy that path. This commit also fixes the issue only allowing a recording to be played once per boot of the roboRIO.
minor integration issue wrt to declan's recent change. |
Just updated your merge commit, think I fixed it. |
This is purely for recording/archiving purposes? |
The idea is we'll record |
So there is no visual recording being done quite yet (?) When you say 'track' do you mean, some form of location system that keeps track of motor and servo movement? |
Joystick inputs are what we record and replay here. The Talon SRX motor controllers we use have a "true" motion capture system built in where we can run each motor individually at a certain speed for a certain duration, but as the official usage guide includes, among other things, an excel macro to output the actual motor profiles, it's not worth it. There's no vision system this year. |
Ok, fantastic. Reason I was interested was that I was tasked by Declan to start building a RoboRIO comparable vision system for next year, and was wondering if you guys were currently doing anything with visuals. Thanks. |
No description provided.