Gotcha. The first image is basically a check list of capabilities for each type.

Suggested reading and video review:

First post-kickoff meeting update:

We’re meeting less frequently than in the past. In part to reduce mentor burnout (people are having kids and buying houses and stuff) and in part to take a deep breath and make sure we’re heading down the right path. We’re also doing robotics work outside of meetings, which is somewhat more relaxing.

We made some initial decisions to guide our initial prototyping and design work.

We distilled some of our archetypes down to simpler descriptions. We settled on ‘fire support.’

We also did what we have termed a DPS analysis (you gaming nerds will get it) to look at what the more efficient operations might be for scoring. Note - tailor the difficulty and difficulty rating to your teams abilities if you choose to do this.

Some subtle tweaks to our chassis model. It’s coming along nicely. We are planning on using 4xneos in 2-motor ball shifters geared at 7/15ft/s with automatic shifting again. This sort of combination has worked well for us since 2018.

The AM performance wheels are sold out, so we’ll be looking at other options.

Prototyping is coming along, but nothing worth a picture or write-up yet.

Robot, you are the chosen one, destined to bring balance to the switch!

I would strongly encourage every team to run some sort of simulation on their drivetrain every year. The ubiquitous JVN Design Calculator is a great way to start, especially if you’re using an OTS gearbox. I don’t think it has BLDC motors yet, but it’s good enough to scope out your drive options (and other mechanisms).

For the next level there are a few options. I gave @JesseK’s ILITE DTS a go this year. It provides some wonderful insights and data. It’s a simulation - so don’t take it to the bank. But it can help you make a better drivetrain gearing choice, and it supports BLDCs.

We’re dropping on the side of ‘geared a little slower than optimal’ which is a nice place to be to have some extra margin on your drivetrain. Especially if you intend to defend or anticipate being defended.

There is a 2020 version of the ILITE DTS, with improvements

For those who use the ilite simulator, can you explain sprint?

I want to know the best gear ratio to go a certain distance. Let’s say 10 feet. On the spreadsheet, if I put in 10 feet as the sprint, the results say the total distance ends up being 20. So can I assume the sprint distance is really just the acceleration distance?

Next, if I change my gear ratios, then my final distance measurement changes too. Does this mean I need to play with sprint distance number to get the correct final distance number if I want to compare times over that specific distance?

Is there a way to specify a shift point within the calculator?

For auto-shifting? Unfortunately, not yet. There have been multiple requests for it though, so I can look into that for next year.

Thanks. The info from your guys’ awesome simulator is still really useful. I think we’ll be a little faster than it predicts when we optimize our shifting point.

With low gear around 7 ft/s we will often shift at 4-6ft/s to keep the drive motors in a high-power-output state, rather than let the robot (slowly) get to 7ft/s.

You can actually calculate the optimal shift point, i.e. the speed at which the force applied by the motor in high gear becomes larger than the force in low gear.

The force applied by the motor with gear reduction G at a speed \omega can be expressed by \tau_s G \left( 1- \frac{\omega G}{\omega_f} \right). So we can solve for the shift point, \omega = \omega_s by equating the forces from both gear ratios:

\tau_s G_1 \left( 1- \frac{\omega_s G_1}{\omega_f} \right) = \tau_s G_2 \left( 1- \frac{\omega_s G_2}{\omega_f} \right)

G_1 - \frac{\omega_s G_1^2}{\omega_f} = G_2 - \frac{\omega_s G_2^2}{\omega_f}

\frac{\omega_s}{\omega_f} \left(G_2^2 - G_1^2 \right) = G_2 - G_1

\omega_s = \omega_f \frac{G_2 - G_1}{G_2^2 - G_1^2} = \frac{\omega_f}{G_1+G_2}

A few questions -

Are Gs 9.17 or 1/9.17? i.e. the reduction or ratio?

How does this equation account for the different motor torques at different RPMs?

G would be 9.17 (i.e. the ratio)

The equation for motor torque at various rotational speeds is given by \tau_m = \tau_s \left( 1 - \frac{\omega_m}{\omega_f} \right), where \tau_s is the stall torque, \omega_f is the free speed, and \omega_m is the motor’s current rotational speed. We can replace \omega_m for the wheel speed, \omega multiplied by the gear ratio, and multiple \tau_m by the gear ratio to get the torque at the wheel, \tau. So putting that all together we get \tau(\omega) = \tau_s G \left( 1 - \frac{\omega G}{\omega_f} \right), which gives the torque provided by the motor at the wheel for any possible wheel speed.

Explored this thread tonight, surely could help younger teams in need of inspiration.

Finally, a meaty update.

We got out 2012 turreted shooter working again to get a little testing in. Firstly - needs way more flywheel mass. Secondly - old and corroded brushed motors get really pissy. Was a good, quick, learning experience, but we quickly moved on.

We got into prototyping for real. We laser-cut our mk2 prototype shooter out of PETG. A nice little-known plastic with many of the properties of polycarbonate, except that it’s less expensive and laser-cuttable. It’s a great prototyping material for us.

Roughly 2in compression, 6x2 colson wheel, 25° of engagement, and 1x minicim running open-loop at ~12V. Tons of range, and shot variation was about 1 ball diameter at ~25ft range. Quite pleased for our first try.

It’s designed to do a target zone shot, so about 70 deg, and we had to tip it waaaay down to test at full power. Our first shot almost took out a light fixture…

The CAD model uses a laser-joint featurescript to make tabbed joints, which fit together really well if you massage the material thickness to make up for the laser kerf. We then pilot-drilled some spots to cinch everything together with wood screws. Worked like a charm.

Some pollen seems to have materialized out of nowhere! Very weird for this time of year in NH…

We are also wrapping up ‘gimpy bot’ which is our 2018 chassis stripped way down to just a programmers playground. This will be our test bed for control loop development, additional/advanced prototyping, and other such activities.

Our prototyping carnage thus far. The intake funnel is… not as effective as we’d have hoped. Lots of work to do there. The power cells will squeeze through very small gaps if they are over-constrained. I hope we can make good progress on that this weekend. The wooden mk1 shooter went together quickly, and exploded even more quickly.