AR Tag Detection Toggle is Not in my AI Vision Sensor Utility

AR Tag Detection Toggle is Not in my AI Vision Sensor Utility

Please help! Using VEXCode AIM Web IDE and robots are on current firmware.

Not to worry! We’ve actually simplified the process of using AprilTags with AIM! Now it just detects them automatically, so there’s nothing you need to do on your side.

But it isn’t working. My student’s code is ignoring AR Tags 1-5. The Vision Utility detects them, but conditional statements are still saying False when it sees one of the tags. There is no option to Get All Tag data in the drop down on the Get AI Vision data block anymore in VEX Code .

And now the Get All Tag data option is back in the drop down. It wasn’t there yeaterday on my student’s iPads or on the website. Sigh.

How strange! I’m glad it’s back for you.

@Sardorbek_Omonkulov / @Catherine_Kettner Wanted to make sure you saw this also. Not sure if you know what might have caused this?

Hello Chris,

Thank you for reaching out.

1. “All AprilTags” option missing from the dropdown

I just verified this on multiple platforms and devices, and the “all AprilTags” option is currently available everywhere.

It may have appeared missing because the dropdown contains many options, and “all AprilTags” is located at the very bottom so you need to scroll down to see it. That could also explain why it was difficult to find.

We’ve taken note of this and will look into improving the dropdown usability in the future.

2. Student code ignoring April Tags 1–5

You mentioned the robot firmware is up to date. We ran several tests on our end and were not able to reproduce the issue.

This may be related to the project logic rather than the VEXcode or the AIM itself. To help isolate the issue, I’ve attached a simple test project we used. This project prints all detected April Tags to the console.

You can access the project here:

Show detected april tags.aimblocks (7.9 KB)

Please try running this project and see if it behaves as expected on your end. If you have any questions about the code or continue to see unexpected behavior, feel free to let us know.

Thanks again!