Skip to content

Conversation

acharraggi
Copy link
Collaborator

With field inspection "gone", reword references to Field Inspector or Field Inspection.
Fix Inspection Checklist link.

@acharraggi acharraggi added the enhancement New feature or request label Sep 19, 2025
is available to help teams self-inspect their ROBOT before their event. Teams are strongly encouraged to self-inspect prior to their event.

There is also a `Inspection Quick Reference (PDF) <https://ftc-resources.firstinspires.org/ftc/archive/2026/event/inspection-reference>`_
with some examples of legal and illegal parts (though it is not a subsitute for the Competition Manual.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

subsitute and missing )

@WestsideRobotics
Copy link
Collaborator

Comments for consideration here:

#361 (comment)

@acharraggi
Copy link
Collaborator Author

I added the letter designator rule to each device name paragraph, we should include an example for commonly used things.

The version info might be paraphrased from your comments, I tried to organise it so it it makes sense as read from the top. I think I got all your points covered and added some stuff. Let me know if there's anything I missed, or a better way to say something.

I copied a sentence from the CM:

Teams may choose to run older versions without affecting their ROBOT inspection status.

And added a caution:

Some FTC App versions have a different robot communication protocol and are unable to connect with each other.

Here's the point mismatch line:

  • Item 14 Matches DS Version should be Yes. A No can show up here and is likely due to a point mismatch e.g. 10.0 and 10.1, mismatches are now allowed, but not recommended.

Does this work for you?

@acharraggi
Copy link
Collaborator Author

FYI - I just realized the old self-inspect page mentions "Field Inspection", so I'll make one more change for this PR.
I'll do a search as well to see if it's mentioned elsewhere.

@acharraggi
Copy link
Collaborator Author

I found the old self-inspect page and the FAQ page also mentioned Field Inspection so they've been updated.

I wasn't going to update the Tech Tip post, but on re-reading it I thought I should. A simple Field to Robot change makes the text work. But the real incentive for the change on that page was the inspection checklist link which was to a Centerstage checklist which still has Field Inspection. I updated it to point to this year's checklist.

You can see the new changes at this commit diff link: cd56b0e

texasdiaz
texasdiaz previously approved these changes Sep 29, 2025
@WestsideRobotics
Copy link
Collaborator

The text that changed after my approval seems OK, contains no typos.

As of this writing, the link-check is showing as "failed".

Speaking of links...

I updated it to point to this year's checklist.

This new link uses ftc-resources -- is that the folder being eliminated on October 1?

@acharraggi
Copy link
Collaborator Author

ftc-resources is the new location, links with resource_library are the ones we should delete or update.
The link check passed when I re-ran it.

@rachmo
Copy link
Contributor

rachmo commented Sep 29, 2025

I'm late to the comment, but if you want to always point to "this season's" resource you should use: https://ftc-resources.firstinspires.org/ftc/event/inspection-reference

If you want to specifically always point to the DECODE resources use: https://ftc-resources.firstinspires.org/ftc/archive/2026/event/inspection-reference

@acharraggi
Copy link
Collaborator Author

Thanks. It's better to have evergreen links on these pages so I updated those links.

@texasdiaz texasdiaz merged commit 6096eaf into FIRST-Tech-Challenge:main Oct 3, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants