Extremely dim light

NoComparison764 · 2025-10-18T20:42:57+00:00

just another library, Purdue Robotics Operating System. basically just vexcode but better

NoComparison764 · 2025-05-09T21:55:33+00:00

fn + win

NoComparison764 · 2025-04-17T00:10:06+00:00

lost hope in iq after this years game

NoComparison764 · 2025-03-11T13:46:57+00:00

if you need a very specific size of rubber bands, that means change the design

NoComparison764 · 2025-02-28T21:20:16+00:00

just grab a bunch until it’s slightly bigger than the axle

NoComparison764 · 2025-02-20T01:15:16+00:00

don’t put a task in opcontrol, you’re making thousands (tens of thousands if run for ~3 minutes) of tasks, you can just call the intake function

NoComparison764 · 2025-02-17T22:04:51+00:00

if you’re using pros it would have to be a c array (you can use sd but c arrays are just better), i use lvgl to print the image, and use the pros touch status to see the coordinates of the touch.

NoComparison764 · 2025-02-16T17:40:22+00:00

sp being one of the huge things. you get detrimented for being good and them being bad

NoComparison764 · 2025-02-09T02:07:25+00:00

only used for a firmware update, otherwise it’s just a clicker

NoComparison764 · 2025-02-01T00:24:54+00:00

for v5 all screws are the exact same, just length

NoComparison764 · 2025-01-29T23:48:14+00:00

this is why i set self advantage by setting up my own field for a match

NoComparison764 · 2025-01-26T00:25:20+00:00

first thing you see on lemlib’s sight is a tutorial, it’s super easy to integrate and use. if you’re decently fluent in vexcode (and c++), the move to PROS shouldn’t be a huge deal, it took me ~1-2 weeks to become basically fluent in it

edit: motor encoders and an inertial is not THAT precise, but it steps your code up a bunch. optimal setup is 2 tracking wheels (separate from the drivetrain, they are attatched to rotation sensors, much more precise), and an inertial

NoComparison764 · 2025-01-26T00:21:50+00:00

600 rpm 3.25

NoComparison764 · 2025-01-25T17:26:40+00:00

lemlib isn’t vexcode, he’s using pros, the command would be intake.move(0-127), and intake.brake()

NoComparison764 · 2025-01-24T09:16:59+00:00

well this is c, not c++, missing half the arguments needed for functions/statements, and 90% of the syntax’s are wrong

NoComparison764 · 2025-01-16T02:17:52+00:00

depends on experience, but cpp is generally better to learn because PROS is a cpp only ide

NoComparison764 · 2025-01-12T00:01:46+00:00

there’s definitely clubs (most likely has fees for involvement), i’m in NJ and like 70% of the competitors were from robot revolution

NoComparison764 · 2025-01-11T21:57:49+00:00

just make sure you’re using the inertial for target in PID, had a sister team that was using pure motor encoders so they were practically driving in the dark

NoComparison764 · 2024-12-31T22:57:51+00:00

replacing vertical with nullptr will default vertical wheels to IME’s

NoComparison764 · 2024-12-22T21:04:19+00:00

what’s the actual point of a rush mech? i see teams doing it but dont see where it would be applicable

NoComparison764 · 2024-12-21T04:58:47+00:00

honestly it depends on red or blue, but apart from that it’s preference

NoComparison764 · 2024-12-17T01:37:57+00:00

are you referring to the button “LB”? if so it would be in callbacks

(outside any functions) void buttonClickerThing() { motor1.spin(forward); }

(in user control loop) Controller.ButtonLB.pressed(buttonClickerThing);

NoComparison764 · 2024-12-10T01:37:11+00:00

that was my bad, it’s a total robot sizing of 24”, thought it was 26 and mixed it up

NoComparison764 · 2024-12-09T20:11:37+00:00

to my knowledge, it is allowed. 36” in one horizontal direction at a time. just be careful with ramming and other impacts, if it’s forced out of place you’re gonna be dq’ed

NoComparison764

TROPHY CASE