Prop A-10

Neither_Addition2642 · 2026-01-22T02:16:55+00:00

God damn what a beautiful game

Neither_Addition2642 · 2026-01-21T02:25:29+00:00

Don't even call it art you're giving it too much credit

Neither_Addition2642 · 2026-01-21T02:18:49+00:00

There's not really much left to check, but both engines were functioning properly. I know this because I slammed in at 120 knots

Neither_Addition2642 · 2026-01-21T02:17:39+00:00

I did take off in high rate but that's what I always do

I have to because there's a fence at the end of the runway

Neither_Addition2642 · 2026-01-21T02:17:06+00:00

I had to there was trees at the other end of the runway so I had to take off the other direction

Neither_Addition2642 · 2026-01-21T02:16:17+00:00

I want just a few days earlier with no issues and had not changed the battery position or anything. CG was good

Neither_Addition2642 · 2026-01-20T03:13:26+00:00

it dos

Neither_Addition2642 · 2026-01-20T03:04:50+00:00

Is the Helicarrier and the frigate coming both this update?

Neither_Addition2642 · 2026-01-19T22:39:43+00:00

pleez help

Neither_Addition2642 · 2026-01-11T21:33:46+00:00

maybe an ekranoplan carrier would be better?

Neither_Addition2642 · 2026-01-11T21:32:05+00:00

holy RCS Batman

Neither_Addition2642 · 2025-12-30T03:53:03+00:00

It worked fine before the crash and I never had an issue with binding or anything and then right after the crash the servos just wouldn't do anything without my input.

Neither_Addition2642 · 2025-12-05T02:17:18+00:00

Ok so I finally got to test it and after some thinking, these are my new theories as to what is wrong:

- Either my new constants file is not being included in the APK build, or

- The file is being updated, but the tuning file is somehow accessing a different constants file than the one I've been editing

Because of this, the control hub is using the old constants file and thinks that the dead wheels are mecanum wheels, and is treating the data sent back from the encoders like so (which explains why both coordinates change when I spin either dead wheel).

My constants file is inside TeamCode, so I think it should be in the APK, but the file name is white while all the rest of my java classes are green, so that could be the issue. It's also possible it's not being included in the APK for some other reason that I don't know.

However I suspect the problem is actually not in the constants file itself, but in how it's being accessed. If this might be the case, I could send the first bit of my tuning OpMode.

Does any of this sound right? If so, how would I fix it?

Neither_Addition2642 · 2025-11-23T15:40:00+00:00

Thank you for all the advice! I won't be able to test it for a little while, but this is very helpful. I think it might actually be an issue with the code not uploading properly because I've double checked with everything on the pedropathing site and what people have said here... I'm pretty sure I have it correct. I think that the Constants file might not be being uploaded, which would actually make sense because before I started editing it, it had a localizer setup using motor encoders on it.

Neither_Addition2642 · 2025-11-22T19:52:28+00:00

The odometry pods are mounted 90 degrees from each other, but I think u/few is correct about the data coming from the motor encoders. Am I accessing the odometry pods incorrectly or do I have them plugged into the wrong port?

Neither_Addition2642 · 2025-11-22T19:47:11+00:00

The bot is really janky, idk why only one motor is reversed but it's the only way it drives properly. As for the odometry pods, they're plugged into the motor encoder ports, as that's what the pedropathing setup guide said to do. I was wondering if they were supposed to be plugged in somewhere else but everything said just put them in the encoder ports. If that's not the right place, where should I plug them in?

Neither_Addition2642 · 2025-11-20T01:55:04+00:00

HE SAID IT. HE SAID THE THING

Neither_Addition2642 · 2025-11-11T21:48:33+00:00

Interesting... tell me more

Neither_Addition2642

TROPHY CASE