Turret Logic | Turret/Drive Interaction
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- embedded-iot, robotics
Research direction
No files, tests, or entry points are named. Start by reviewing the turret and swerve-system implementation to understand their limits and coordination, then define and validate a safe strategy for target alignment and turret wraparound behavior.
Written by the indexing model from the issue text.
Description
One idea that Andrew and I have been thinking about is how the swerve system could be used in combination with the turret to line up shots more quickly. If, for example, the turret has 270-degree limits on either side (which is ambitious, but we can hope), but the target is at 300 degrees, it would be much quicker to rotate the swerve system by >30 degrees and line up instead of whipping the turret around 360 degrees. We have to think about how we could potentially implement this logic, any potential dangers or better solutions, etc.
Another idea: If the turret is supposed to be ready to shoot at any moment (always lined up with the target), is it better to whip the turret around when, say, at +240 degrees to give more freedom near that orientation? Instead of having 30 degrees of freedom clockwise, and 510 degrees of freedom counterclockwise, you'd have 390 degrees clockwise and 150 degrees counterclockwise (I think). How do we determine when to spin around?
- Dominant language
- LabVIEW
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MARSProgramming/M15
-
better method/nice to have
Difficulty 4/5 3-5 days Newbie friendliness 30/100
MARSProgramming/M15#17 ·
-
vital
Difficulty 3/5 1-2 days Newbie friendliness 42/100
MARSProgramming/M15#16 ·
-
vital
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MARSProgramming/M15#15 ·
-
vital
Difficulty 3/5 1-2 days Newbie friendliness 25/100
MARSProgramming/M15#14 ·
-
vital
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MARSProgramming/M15#13 ·
All issues in MARSProgramming/M15
Similar issues
-
approved checks-failed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
zwave-js/firmware-updates#390 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
espressif/esp-aws-iot#261 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#120011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
CVA6 cache increase Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100