Can you think of a likely reason that it seems like my V5 brains are not correctly measuring distances? If I have a student do a quick test for a dragster, that starts via a bump switch, at like 20inches it drives and stops like it should within its forever and if then loops… but if I want them to …

What programing software are you using and share your code (one of the only ways we can help) Another issue I see is you aren’t using sensors outside the motor, as motors are not 100% accurate at measuring distance, but this shouldn’t cause a too dramatic change in distance

@DodgeDoodle_41442A I am having my class use VEXcode V5. In this case the the drive-train is a 2-motor with 4in wheels, 11.75in track width, 7in wheel base, 1:7 ratio, with green gear cartridge. The robot will drive and stop with the code on the left, like its supposed to. But the one on the rig…

Can you try the same thing but with an else part underneath? The if-then-else hat. [image] with all the other code around it

Your making it drive forward for 50ft, not 5ft Change the varible to 60in and see is you have the same issue

@dodgedoodle Yeah that was a typo in my reply. I do want them driving 50ft at 600in. I’m sorry, thanks for trying to help me. Just so we’re on the same page again because of the typo. I want them to go 600", but they are driving nonstop for like five minutes when I put 600 inches and they are d…

@robomaster Just tried it. Same thing. It basically forever when I want them to put any amount of inches over like 100. It stops when I have them put like 20" while holding up the drive-wheels when they are making sure they are going the correct direction though.

This sounds like a bug By chance do you have any bumper sensors? You could have it run forever, and when it hits the wall and the bumper is pressed, it could shut off the program. A picture of the dragster also might help (the motor-gear-gear connection)

It sounds like we have an overflow error somewhere. I’ll look into it and let you know, can you post a screen shot of the drivetrain configuration so I can exactly reproduce your project.

Assuming 4 inch wheels, 600 inches is ~24 rotations. At 2048 ticks-per-rotation, that would be 49,152 which would overflow a 16-bit signed integer (32,768). However, the V5 motor specs seem to indicate that the green gears are 900-ticks per revolution, which would put this at 21,600 encoder ticks. …

[image] DC2: I am having my class use VEXcode V5. In this case the the drive-train is a 2-motor with 4in wheels, 11.75in track width, 7in wheel base, 1:7 ratio yea, I don’t see any errors, I’m just wondering of you (or we I guess) have external gear ratio reversed

Help: "Drive For Distance" Blocks & Measuring

VEX V5 Technical Support

VexTeamZ December 8, 2021, 11:27pm 12