When programming our robot for programming skills run, our team noticed something rather confusing. When we download the program from a laptop, the outcome is what’s desired. If we switch to another laptop and download the exact same program in the brain, the outcome is different. Angles are bigger and distances are not accurate. Have you guys got any idea on how such a thing is possible?
1 Like
Are you using block code? And are you using an inertial sensor? What works for us is downloading the code twice when that happens. As for it turning too much might be related to too much weight on a certain side.
1 Like
Exact same as in copy the file from one machine to another and download it, or exact same as in create again on a different machine?
Reason I ask is because that sounds like the gear cartridges (assuming this is V5) are different on one program to the other, or different wheel sizes are specified.
If you could share the exact file from both machines, that would help to identify the issue.
6 Likes
This likely should not happen, and for that reason I highly suspect it is purely coincidental. Make sure that the robot is aligned properly every skill run in the same location, alongside good battery life and you utilize sensors and algorithms for better turning.
1 Like
This could easily be the issue. Did you just copy and paste main.cpp between computers? Make sure that robot-config.h is also transferred to preserve the motor configuration. The easiest way would be to save the program, then copy its entire directory to the other computer with a flash drive, etc.
6 Likes
Thank you guys for your time. I appreciate it. We’ve figured out that the problem was indeed the configuration of our drivetrain. Wheel size and distance between wheels were not the same. Thanks again guys 
You are using time aren’t you? If so, that is your reason. The brain counts time differently when it is at different battery levels.
Read the OP’s last post - issue was configuration issue of robot drivetrain declaration between two.
Your statement is factually incorrect, Brain always counts time the same no matter what the battery level is. 1 millisecond is always 1 millisecond or whatever unit you use. So you need to rethink your assumption about how things work.
5 Likes
I mean… technically a charged battery will have a slightly higher gravitational pull, therefore there would be some tiny amount of time dilation that would change how the brain counts time…
I think what you meant to say was:
And this is arguable - it depends on if you want to believe VEX or if you want to trust everyone’s anecdotal evidence.
1 Like
Yes this is what I meant. Sorry. But my point still stands, motors will not go to the same position every run if you are using time time.
and you need to research causation vs correlation before trying to make points. 1) time in the context of your position in the universe is likely to be the same units in the V5 Brain, unless your V5 Brain is a passenger in a Tesla on a mission to pollute the universe. 2) timed function has many variables that are outside your control, including poor battery storage (with V5 Batteries not as much an issue compared with old 7.2V batteries …), 3) interactions with objects outside your control, such as alliance partner robots, opposing alliance, or game and field objects you never expected to encounter. Suffice to say - a lot of variables to consider before considering that relativity is to blame for time units used in V5 brain and … well, better ways to adapt to a competition than assume the universe likes your robot 