forked from jandrew/SkyStone
-
Notifications
You must be signed in to change notification settings - Fork 0
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
updating to 5.3 #1
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jeds example for the club on friday
Upgrade the gradle.build but take it out of tracking Unpollute the main repo with mentor code
…s.xml each team should get their own; mine will be available as a default that can be obtained locally but not in the remote repo. add your license to the licenses.xml file as an item within the <resources> ... </resources> block: <string name="vuforiaLicense"> YOUR VERY LONG LICENSE STRING </string> see FIRST-Tech-Challenge#50 for background. NOTE: on slow phones like ZTE Speed, Vuforia initialization can time out unless you're running in the debugger. Solution to that is still TBD.
* 'master' of https://github.com/jandrew/SkyStone: Jeds example or club on friday
…low (ZTE) phones --- most teams won't need this.
* remove license key argument from init() -- always use xml resource for license * add functions to return list of visible trackables names * make position and orientation formatting functions public * update object detection functions to SkyStone objects update VuforiaNavigationTestSkyStone to get info itself rather than just relying on library to dump telemetry
…s implemented in FTC sample) TBD: figure out if orientations of the bridge images is correct.
…e tank around while it reports its position using (in this case) a mix of Vuforia updates and PositionIntegration
… sources (like Vuforia)
…osInt -- this version doesn't yet do anything different from that one. See Vuforia+PosInt branch.
…ith a given set of motor names.
…b and update usage examples (PosIntDriveTestOp and TankDrivePosInt) to use that one.
…osition either by pure PositionIntegration from wheel encoders and gyro (TankDrivePosInt) or by that plus occasional updates from Vuforia when a target is visible (TankDriveVuforia).
…tation about vehicle vertical (Z) axis in deg/sec. Which axis we return depends on orientation of RevHub, which we know.
…tes the PI position by weighting what it thinks vs. suggested position -- e.g. if we get a position from another sensor (like Vuforia) that we don't completely trust, go with a weighted mix of the two.
… tracking by implementing our own Listener to record the status and statusInfo associated with tracker update calls. Make this info available along with the id and location of the most recent visible target.
… we trust it: - check status and statusInfo must be "reasonable" - rate of vehicle rotation about vertical axis must be low (to avoid blurry image)
…) cycle so we know if we actually got some data
…rmal, Mecanum, X-Drive). delete specialized MecanumEncoderPosInt (no longer needed).
…ion -- it uses the left stick AND dpad for orientation and the right stick for movement on the field (better for RH drivers?)
* post usage instructions to operator console in init() * add code to set initial orientation of robot on field (defaults to bearing zero
…ttons on gamepad. So, if the gyro drifts, you can "steer" the bot back to correct alignment with the field by tapping those buttons -- each tap is one degree.
* 'master' of https://github.com/jandrew/SkyStone: SkyStone v5.3
…obotics were getting an error doing it the old way -- something changed in driver code??
…ribution of motors to "full speed" -- TBD: add way to limit this to less than full speed?
…ey are working on ratbot)
…um wheels (equivalent to X-Drive) (previously, reflected earlier arrangement of wheels on ratbot)
…t to track field position as we drive around to test position integration when strafing. Should help with tuning position integration for use in autonomous modes.
…bot --- other users should set things up for their bot.
…ng in smaller venues.
…ava file -- update all uses
…lue1 sample to AutoLib so it can be more widely shared. for now, leave the Vuforia-enhanced version (now called VfSqGyroPosIntGuideStep) in SkystoneAutoBlue1 sample, where it is used in that sample's local version of SqPosIntDriveToStep. reorder some classes in AutoLib to group like functionality together better.
…de now appears to work both with Vuforia updates enabled and disabled.
…or the one with the target picture, then move toward it presumably to try to pick it up.
* make "stop" option on various PosInt drive-to steps actually work by passing motors to be stopped to the termination step * make that work correctly by reordering the steps in GuidedTerminatedDriveStep to put termination step AFTER motor update steps so it will override their power setting if it's time to stop * move PosIntDriveToStep from PosIntDriveTestOp to AutoLib
…by terminator step is passed all the motor steps (you have to implement the set(...) function) rather than trying to pass motors and set them directly --- doing it this way, the terminator step has to run BEFORE the motor steps since it just tells them to set the motors to zero and they actually do it.
…ovements and waits for servos, etc.
…ing and stick scaling to improve (?) driveability (from simulator)
updated forum link.
…rive steps --- currently, Counted step doesn't work ... TBD
…qPosIntDriveToStep to reflect the fact that it uses Vuforia updates to its PositionIntegrator and remove confusion with the real one in AutoLib.
…) to test AutoLib.SqPosIntDriveToStep
Update README.md
* 'master' of https://github.com/jandrew/SkyStone: Update README.md
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before issuing a pull request, please see the contributing page.