This repository has been archived by the owner on Dec 7, 2024. It is now read-only.
Revisions to LabVIEW velocity closed loop. -- NOT TESTED #20
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.
I attempted to make revisions to the LabVIEW closed loop example to use the VI that are in the palette.
Also moved visual and user interaction to Robot Main to allow this to run easier on the robot interactively.
Also added what I think would be get distance.
I wasn't certain if this is the most efficient way to get the information. (Is there a single call that can retrieve
all the information? Should the VI be put in parallel rather than serial?)
** I've not used the Spark Max so I don't have experience **
** with this or any way to test. Strongly suggest review **
** and testing before accepting.... **