Skip to content

Conversation

@nightwolf3140
Copy link
Member

@nightwolf3140 nightwolf3140 commented Oct 3, 2025

Summary:

Upgraded EZ to PROS 4.2.1 and upgraded to okapi 5.1

Motivation:

Allows for the use of AI sensors.

References (optional):

purduesigbots/pros-vsc#262 (comment)

Test Plan:

  • test on robot

Download the template for this pull request:

Note

This is auto generated from Add Template to Pull Request

curl -o EZ-Template@4.0.0+35f4ed.zip https://nightly.link/EZ-Robotics/EZ-Template/actions/artifacts/4243219033.zip;
pros c fetch EZ-Template@4.0.0+35f4ed.zip;
pros c apply EZ-Template@4.0.0+35f4ed;
rm EZ-Template@4.0.0+35f4ed.zip;

@nightwolf3140 nightwolf3140 self-assigned this Oct 3, 2025
@nightwolf3140 nightwolf3140 changed the title Upgraded EZ to PROS 4.2.1 and to okapi 5.1.0, regenerated template files Upgraded EZ to PROS 4.2.1 and to okapi 5.1.0 Oct 3, 2025
@nightwolf3140 nightwolf3140 added enhancement New feature or request restructuring labels Oct 3, 2025
@nightwolf3140 nightwolf3140 requested review from ssejrog and removed request for WillXuCodes October 9, 2025 02:50
@nightwolf3140 nightwolf3140 removed the request for review from ssejrog October 25, 2025 03:02
@nightwolf3140 nightwolf3140 moved this to In review in Getting Ready for 4.0 Oct 25, 2025
@nightwolf3140
Copy link
Member Author

In testing it seems to work well so far no issues to report yet.

@nightwolf3140
Copy link
Member Author

Tested on robot and it appears completely broken at the moment

@jemminiz
Copy link
Contributor

What does "completely broken" mean? What's not working? The entire robot isn't functioning? New features aren't working?

@GamerVerse722
Copy link

I have the 4.2.1 version of Ez-Template currently installed on my team robot and had experience the same issue of the robot not functioning with black screen no action being ran. Just a frozen state. The way I made it be able to run was manually copying over all the header and implementation files over to my project.

@@ -1,30 +1,11 @@
# Dependencies
/node_modules
Copy link
Contributor

Choose a reason for hiding this comment

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

keep node_modules in gitignore, can mess with binaries

__undef_stack = .;
} > COLD_MEMORY

/* There are no sections for the stack. This is intentional, since VEXOs sets up a stack before
Copy link
Contributor

Choose a reason for hiding this comment

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

unlikely that this caused the error you're seeing if this is true, but still something to point out.

*
* \param active
* sets piston to true
* \param active
Copy link
Contributor

Choose a reason for hiding this comment

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

I keep seeing these, who messed up the params 😭

#include <unistd.h>
#endif /* __cplusplus */

#define PROS_VERSION_MAJOR 4
Copy link
Contributor

Choose a reason for hiding this comment

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

are these necessary? that might also be an issue, depending on if/how pros handles these

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request help wanted Extra attention is needed restructuring

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

🐛[BUG] - ez namespace is forced on users ✨[FEATURE] - Allow custom tracking Multiple IMU Support Motor temperatures on screen

4 participants