FIRST Tech Challenge Tech Tips

Started in the 2023-2024 season, Tech Tips are a weekly segment released in the FIRST Tech Challenge Team E-mail Blast. Sometimes the Tech Tips are included in whole in the email blast, but sometimes there is more content than is reasonable in the email blast so partial content is included in the blast with the rest of the content here. Blasts are ordered on this page chronologically, with the newest content at the top of the page.

Just click to expand the Tech Tip you’d like to read.

Week of 06/24/2024 “Calculating Motor and Servo Power”

In this Tech Tip of the Week we’ll be exploring mechanical and electrical power, why some types of power are calculated differently, and how to use this calculated power to compare servos. This Tech Tip was written and fact-checked with the help of Google Gemini 1.5 Flash using Google AI Studio.

The fundamental concept we need to understand is power. We are generally concerned with two similar but different kinds of power, so let’s look at the two most common types. In a motor, electrical power is the energy supplied by the electrical current flowing through the motor’s windings. This electrical energy is transformed into mechanical power, which is the rate at which the motor performs work by rotating a shaft. Both kinds of power are measuring different aspects of the motor; electrical power deals with the movement of electrical charges, and mechanical power deals with the movement of objects due to forces. Both of these measurements are expressed in the same unit, Watts (W), because power, in general, is defined as the rate of energy transfer or work done. No matter the form of energy (electrical, mechanical, thermal, etc.) the fundamental concept of power remains the same. Even though these two power measurements carry the same unit, they are calculated differently and cannot be used interchangeably (or together!).

Motors and servos are constructed similarly - both are electromechanical devices that convert electrical energy into mechanical energy - but there are big differences in how they’re used. Motors are often used in applications requiring continuous power, such as pumps, fans, and conveyor systems. Motors are typically rated for continuous power output, meaning they can sustain that power level indefinitely without overheating. Servos are commonly used in robotics and precision positioning systems, where controlled movement and precise positioning are essential. Servos are designed for intermittent operation - typically cycling through on/off periods to control movement - and are often rated for their stall torque and no-load speed reflecting their ability to hold a position against a force and how fast they move when unloaded. While electrical power is calculated generally the same for both types of devices, these design and use differences have an impact on how mechanical power is determined.

Both motors and servos calculate electrical power the same, using the standard electrical power formula:

Electrical Power(W) = volts(V) x amps(A)

For example, a typical REV Smart Servo is supplied with 6V when used with a REV Servo Power Module (SPM) or 5V when used with a Control or Expansion Hub. Per the servo’s specs, at 6V the servo will pull at most 2A at stall (when the servo cannot physically move to the position it’s being commanded to). This means the maximum electrical power the servo will consume is 12Watts of power when plugged into the REV SPM and being commanded to a position it cannot reach. The REV SPM supplies 90W of maximum electrical power, so the maximum number of fully-stalled REV Smart Servos the SPM can supply full power to is 7 (90W divided by 12W, ignoring the remainder).

Motors and servos also generally calculate mechanical power similarly.

Mechanical Power(W) = torque (N-m) x angular speed (rad/s)

Mechanical Power for a DC motor generally follows a very specific curve, based on its efficiency, stall current, stall torque, speed, and a bunch of other factors. The general performance curve of a DC motor can be seen in Figure 1.

DC Motor Performance Curves — Figure 1: General DC Motor Performance Curve

From this we can see that the Peak Power is found at the intersection of 1/2 Stall Torque and 1/2 Speed. Even though a servo is used different than a generic motor, this approximation is still good for calculating the maximum mechanical power of a servo. Simplified, we can use this formula:

Servo Max Mechanical Power(W) = 0.25 x stall torque(N-m) x no-load speed(rad/s)

Using this approximation the REV Smart Servo, when being provided 6V, produces a maximum Stall Torque of 13.5kg-cm (1.33N-m) and a time of 0.14s per 60 degrees of travel (7.48rad/s) yielding an approximate max servo mechanical power of 2.48W.

Tip

It’s important to point out that a high speed motor or servo that is loaded past its maximum power point will actually do worse than a slower motor or servo with the same load. It’s all about getting the maximum mechanical power by operating the motor at the max power point.

One of the most difficult parts of calculating Servo Mechanical Power is working with unit conversions, especially since servo manufacturers use lots of different units. In order to calculate servo mechanical power correctly the speed unit MUST be converted to radians-per-second and the max stall torque unit MUST be converted to Newton-meters. Below is a handy calculator that you can use to automatically perform the necessary conversions and calculate Servo Mechanical Power (Thank you to Orion DeYoe for providing this tool).

Speed

Time per 60°

Angular Velocity

Stall Torque

Power

Tip

For Speed, use the radio button to choose the unit type that the manufacturer has provided - for most servos this will be listed in a period of time per 60 degrees (such as with the REV Smart Servo example) or perhaps the manufacturer may provide an angular velocity, such as rotations-per-minute (RPM). Enter the no-load speed value and unit as the manufacturer has provided.
For stall torque, provide the value and select the unit as specified by the manufacturer. If the manufacturer merely provides kg, assume kg*cm.

The calculator automatically recalculates on any changes, there is no button to press in order to trigger a calculation.

Here is a handy table of some common servo mechanical power values:

Common Servo Mechanical Power Values ( @6V )
Description	Speed	Torque	Stall Current	Max Power	Cost ($USD)
Tetrix MAX Standard (HiTec HS-485HB)	0.18 s/60°	6 kg-cm	1.2 A	0.86 W	$29.50
REV Smart Servo	0.14 s/60°	13.5 kg-cm	2.0 A	2.48 W	$30.00
goBILDA 2000 Series Speed Servo	0.09 s/60°	9.3 kg-cm	2.5 A	2.65 W	$33.99
Axon Robotics Micro+	0.075 s/60°	7.8 kg-cm	2.2 A	2.67 W	$63.79
goBILDA 2000 Series Torque Servo	0.20 s/60°	300 oz-in	2.5 A	2.77 W	$33.99
Studica Multi-Mode Smart Servo 200	0.046 s/60°	5 kg-cm	2.7 A	2.79 W	$24.99
goBILDA 2000 Series Super Speed Servo	0.043 s/60°	4.7 kg-cm	2.5 A	2.81 W	$33.99
AndyMark am-4954 High Torque Servos	0.20 s/60°	22 kg-cm	1.7 A	2.82 W	$34.00
Studica Multi-Mode Smart Servo	62 RPM	20 kg-cm	??	3.18 W	$23.99
AndyMark am-4955 High Speed Servos	0.05 s/60°	7 kg-cm	2.7 A	3.59 W	$30.00
FeeTech FT5335M-FB	0.20 s/60°	35 kg-cm	4.0 A	4.49 W	$52.95
HiTec HS-805BB	0.14 s/60°	24.7 kg-cm	6.0 A	4.53 W	$49.99
HiTec HSR-M9382TH	0.17 s/60°	34 kg-cm	2.7 A	5.13 W	$199.99
Power HD GTS3	0.083 s/60°	20 kg-cm	4.0 A	6.19 W	$120.00
Axon Robotics MINI+	0.09 s/60°	25 kg-cm	3.8 A	7.13 W	$79.99
Axon Robotics MAX+	0.115 s/60°	34 kg-cm	4.0 A	7.59 W	$79.99

Week of 06/10/2024 “Updating the SDK Manifest”

This week’s Tech Tip of the Week comes to us from an amalgamation of emailed questions asking about allowed ways to update an FtcRobotController SDK project. An approximate summary of the emailed questions along this topic is as follows:

“Is merely editing the Android Manifest file in the TeamCode directory of the FtcRobotController SDK project an acceptable way of easily updating the SDK? And would this violate RS08 in Game Manual Part 1?”

Manually editing the Android Manifest file in the TeamCode Directory of the FtcRobotController SDK software is not a violation of RS08, merely because RS08(b) only protects the binary .AAR files. The manifest file is not part of the .AAR binary, and thus it’s not protected.

Even though it’s not forbidden, that doesn’t mean you should do it – like putting pineapple on pizza (sorry, the door was open, I couldn’t stop myself). Seriously, though, 4 times out of 5 you can likely get away with updating the SDK through editing the Android Manifest to point to the latest version of the SDK libraries. However, that assumes that all the Tech Team does is update the SDK libraries, which is never ever the case. In addition to also updating programming samples, often enough the Tech Team must also update tooling, dependencies, and other build items in addition to the SDK libraries, and simply updating the Android Manifest is going to get you into real trouble (things will appear to work, until they don’t, and you won’t know why). As a corollary, you can choose to simply only put gas in your car and ignore all the other fluids, but eventually you’re going to wish you hadn’t.

The proper way of updating your SDK is to use Git/GitHub to update your robot source each time the SDK software updates. The Tech Team always updates the FtcRobotController in-place (meaning the same repo is always updated each version), so if you’re using Git you can easily pull the changes made upstream and accept the changes within your code. You should never be manually updating files, like the Android Manifest file, because Git can tell you all of the files you need to update and can do that for you. If you use Git or GitHub, we highly recommend reading our guide on ftc-docs for managing your Android Studio project repositories.

For example, check out these changelists. The FtcRobotController v9.0 commit/change is everything that needs to be changed to upgrade from version 8.2 to 9.0 – there are 75 changed files there, which include samples, a core interface module change, gradle dependencies, and in that changelist the Tech Team also rearchitected the asset structure. However, the FtcRobotController v9.0.1 and FtcRobotController v9.1 pull requests only changed a handful of files (mostly samples), and the core changes are in the AndroidManifest.xml and build.dependencies.gradle files. In general our major version releases (where we increase the first number in the version string) are the big ones, and then the dot-releases are almost always fairly small targeted releases. The Tech Team tries very hard not to make big-scale changes to build systems or major dependencies during the season.

In summary, teams should never simply change the Android Manifest, they should be updating the software appropriately – as Voltaire warned, with great “Android Studio” power comes great “GitHub” responsibility.

Week of 05/20/2024 “Wi-Fi Bands, Part 3”

Welcome back to the Tech Tip of the Week, this is Part 3 of a 3-part series talking about Wi-Fi bands and why you might be shooting yourself in the foot by not selecting (and designing your robots for) the right Wi-Fi band. In Part 1 we discussed the physical characteristics and properties of frequencies in each of the 2.4GHz and 5GHz bands. In part 2 we talked about the history of the bands, described sources of interference (e.g. other devices!) on each band, and how Wi-Fi improvements have made 5GHz more efficient to use.

Robot design - and more aptly “Control Hub placement” - is THE critical factor in influencing the Wi-Fi frequency/band you should be using. Remember Wi-Fi is a line-of-sight technology, that means Wi-Fi does best when there’s a straight unobstructed path from the antenna on the Control Hub to the antenna on the Driver Hub. Where is the antenna in a Control Hub? It’s right under the plastic on the “face” of the hub on the logo side. If the Control Hub can be mounted so that its antenna is generally not covered/surrounded/blocked by metal, 5GHz should be your target band. However, if your Control Hub is buried deep inside the robot and surrounded by metal, the 2.4GHz band may be your only option (remember, the lower frequencies of 2.4GHz might be able to “bend around” metal obstacles slightly better). Unfortunately exposing the “back side” of the Control Hub instead of the “front side” of the hub is not going to yield similar results, as there is a PCB with metal traces between the antenna and the “back side” of the Hub that will block/reflect/absorb signals.

Does that mean your Control Hub needs to be mounted unprotected on the outside of the robot in order to get good signal reception? Not necessarily, fortunately not all materials are the same. Plastics are generally the most “invisible” to Wi-Fi frequencies, or at least their absorption/blocking/reflection (also known as attenuation) is generally minimal enough to not sufficiently matter. Wood, especially thin birch commonly used in many robot designs, is slightly more attenuating but definitely still a great option. Metals, however, will greatly attenuate Wi-Fi frequencies and are the worst materials for Wi-Fi transmission. Yes, I’m looking at YOU teams who use hook-and-loop to mount your robot battery to the top of the Control Hub - stop doing that! And for those looking for inspiration in this upcoming season, water is also an incredibly poor medium for transmission of Wi-Fi frequencies.

But how do you know for sure how well your robot’s Wi-Fi is performing? You can monitor the Wi-Fi signal’s strength through the Driver Station App. Check out the 2024/02/15 Team Blast Tech Tip for info on how to view and understand Wi-Fi Signal Strength. If your signal is strong when using 5GHz at maximum field range (from the Driver Hub) and in all robot orientations, you should be good to go on 5GHz! Feel free to compare the performance on 5GHz and 2.4GHz, and if they’re comparable you should stick with 5GHz for better interference reduction.

In summary, the vast majority of robots should be using 5GHz as this is the optimal channel in terms of interference reduction, device crowding, and channel utilization by the Wi-Fi standards. Robot design - specifically Control Hub placement - might necessitate the use of 2.4GHz if the line-of-sight path to the Control Hub antenna in the robot is too greatly obstructed by metal, especially motors. By monitoring the robot’s Wi-Fi signal strength, you can determine which frequency band yields the best Wi-Fi signal performance for your robot.

Week of 05/06/2024 “Wi-Fi Bands, Part 2”

Welcome back to the Tech Tip of the Week, this is Part 2 of a 3-part series talking about Wi-Fi bands and why you might be shooting yourself in the foot by not selecting (and designing your robots for) the right Wi-Fi band. In Part 1 we discussed the physical characteristics and properties of frequencies in each of the 2.4GHz and 5GHz bands. In this part we’ll talk about sources of interference.

You might have realized this, but wireless devices are all the rage. The FCC (in the USA) doesn’t just let any device broadcast on any frequency they want. Instead, there are licensed and unlicensed radio frequency bands. Some frequencies are uniquely licensed to private operators, for example radio stations pay a lot of money to the FCC for the exclusive rights to broadcast on specific frequencies. HAM radio operators undergo special training to be allowed to broadcast on a range of licensed frequencies (some reserved only for HAM radio, some not). The FCC also sets aside frequencies that are unlicensed, meaning the operators themselves (like you, your neighbor, or the kid down the street) don’t need training or licensing to operate devices that broadcast on those frequencies. The devices themselves must adhere to specific regulations, but those requirements are generally easy to meet.

Wi-Fi uses portions of the radio frequency spectrum designated as unlicensed - remember that these frequencies are available to the general public to use - so anyone can broadcast signals over it. And boy howdy do they. The 2.4GHz frequency band was opened to the public in 1985, and devices began using that frequency for use. Wi-Fi emerged in the late 1990’s. The 2.4GHz frequency band became extremely crowded, and by devices using different protocols - think about trying to have a conversation with a friend in a crowded room, but some people are talking “normally”, some are using air horns, and others are mimicking nails on a chalkboard. The resource was very narrow, but at least interference was just a matter of distance - though not everyone lives in the deserts of Arizona where they can carry out their conversations in relative peace.

By the turn of the 20th century, the 5GHz space was opened up for unlicensed use. This required different hardware, as the 2.4GHz devices couldn’t simply just start using 5GHz. The 5GHz band was much larger, and it took longer for it to become crowded as more devices came onto the market that could use it. 5GHz already had a bunch of legacy systems that used portions of it, and so the FCC grandfathered those systems and made special regulations for using those frequencies (most manufacturers designed their devices to only use the portions of the 5GHz band with the least rules and regulations). Some uses of 2.4GHz could not move to 5GHz because of the frequency wave propagation behaviors (that we talked about previously, e.g. reflections and wave bending), but many systems like Wi-Fi found the greatest use in 5GHz. The number of channels and the frequency space was much larger in 5GHz, and 5GHz Wi-Fi technologies learned to use the 5GHz space more efficiently and robustly.

When you consider which frequency you should use, you have to consider many factors. How obstructed is the path from the radio to the receiver? How crowded might the frequency space be that you’re trying to use? Has the event organizer worked with the venue to clear specific channels for robots to use? What advanced technologies might the device you’re using be capable of utilizing on specific frequency bands?

In Part 3 of this series we’ll talk about how robot design can influence the Wi-Fi frequency you should be using, how to design for the best possible outcome, and how to characterize your optimal band.

Week of 04/29/2024 “Wi-Fi Bands, Part 1”

Welcome to the Tech Tip of the Week, where this week hopefully “Bandwidth of Robots” will be your new favorite way to refer to groups of wireless robots. Today we’ll be starting a three-part series talking about Wi-Fi bands and why you might be shooting yourself in the foot by not selecting (and designing your robots for) the right Wi-Fi band. And at the end of the day how do you truly know which band you should be using?

If you’re anything like the average team, Wi-Fi bands are something nebulous that you don’t really understand or even give a second thought to. At least, until “bad things” start happening and you’re grasping at straws trying to resolve them. So let’s start this discussion by talking about radio frequency bands and then the two Wi-Fi bands we have access to, 2.4GHz and 5GHz.

What are the important properties of Wi-Fi frequencies we should know? To explain Wi-Fi frequencies, let’s look at something most of us might already be more familiar with - AM and FM radio frequency bands (which share similar behaviors, ignoring modulation differences).

AM radio stations are assigned carrier radio frequencies between 540kHz-1600kHz. For example WGHM 900 AM out of Nashua, NH, is licensed to broadcast at 900kHz. AM radio station signals travel very far very easily mostly because the frequencies in AM radio have very large wavelengths - 900kHz, for example, has a full wavelength of 333m (just over one fifth of a mile) - and because of this they can bend around obstacles very easily (buildings, mountains, curvature of the earth, etc). However, long wavelength AM radio is more susceptible to interference and static than shorter wavelength transmissions, like FM.

FM radio stations are assigned frequencies between 88.1MHz-108.1MHz. For example, WEVS 88.3 FM also in Nashua, NH broadcasts at 88.3MHz. FM radio frequencies are higher frequency, and have a shorter wavelength - 88.3MHz is about 3.4m (about 11 feet) in wavelength - and cannot bend around obstacles as easily. Shorter wavelength frequencies also tend to be absorbed/reflected (comparatively) much easier by obstacles as well.

Hence when driving through the mountains and forests of NH I am more apt to be able to cleanly listen to the AM station uninterrupted but not the FM station, even though they’re broadcasting at roughly the same power and from very similar locations.

Frequency bands used for Wi-Fi share very similar characteristics, but because the frequencies for Wi-Fi are much higher some characteristics are more exaggerated. As an analogy, for the purposes of this discussion, we can say that 2.4GHz is to 5GHz as AM is to FM. 2.4GHz frequencies have a longer wavelength (starting at ~0.125m or ~5 inches) than 5GHz frequencies (starting at ~0.05m or ~2 inches), and because of that 2.4GHz radio waves can bend around objects better than 5GHz ones but are much more susceptible to interference than 5GHz. Similarly 5GHz frequencies will also tend to be reflected/absorbed much easier by solid objects, and so 5GHz tends to perform better with an unobstructed line of sight between antennas.

In Part 2 of this series we’ll talk more about the challenges Wi-Fi faces because unlike AM and FM radio, Wi-Fi doesn’t have dedicated frequency space. This can cause legitimate issues due to the number of existing devices and services that already use frequencies that Wi-Fi has to share.

In Part 3 of this series we’ll talk about how robot design can influence the Wi-Fi frequency you should be using, how to design for the best possible outcome, and how to characterize your optimal band.

Week of 04/08/2024 “What makes Battery Voltage Sag? Part 3”

This Tech Tip of the Week is Part 3 in a 3-part series surrounding a question that we get asked at events all the time - “What makes battery voltage sag?”. As a battery is heavily used, teams will notice that the voltage of the battery temporarily decreases from its starting voltage during periods of heavy use, and then generally raises back up once the heavy use has subsided. So what causes this?

There are LOTS of reasons why battery voltage will sag during use. In Part 1 we talked about battery chemistry to give an idea how a battery works, and we talked about how motor torque is inversely proportional to the power consumption (given a constant load). Part 2 covered cell health and battery temperature, both of which can affect a battery’s performance and longevity. This week, we’ll cover another major factor which is Internal Resistance (IR).

Understanding IR requires talking about the discharge rate of a battery. The discharge rate is a measure of how quickly the battery can deliver its stored energy. Most NiMH batteries used in FIRST Tech Challenge are rated at a nominal 12V and a maximum discharge rate of 30A, though that rate is limited by the 20A fuse. A battery’s IR refers to any opposition to that flow of electric current within the battery itself. Resistance can come from a number of sources, such as resistance within the battery’s chemistry (such as a breakdown of the conductive electrolyte within the battery), changes to the resistance of the electrodes (such as a buildup of crystals around the electrodes), resistance added due to connectors and wiring, and others. Rising IR affects the battery performance primarily in decreasing the Voltage and Current that the battery can provide, and causes the battery to generate excess heat when used. The starting IR of a battery can vary among different manufacturing processes and batches, so much that batteries should have their IR measured (using a CTR Battery Beak, West Mountain Radio CBA, or similarly capable battery tester - YOU CANNOT MEASURE INTERNAL RESISTANCE DIRECTLY WITH A MULTIMETER, ATTEMPTING TO DO SO WILL BLOW YOUR FUSE AND MAY DAMAGE THE MULTIMETER!) at “birth” (when “new” at time of purchase) and the IR then should be tracked over time. Once the battery’s IR increases by 50% from when it was “born”, the battery is universally considered ready for replacement.

Danger

You cannot measure the internal resistance of a battery directly with a multimeter. Please do not even try. Doing so will certainly blow your multimeter’s fuse, and may even damage the multimeter. Please do not attempt. Internal resistance can only be measured indirectly using a load-measuring device like a CTR Battery Beak.

What can teams do to slow the increase in a battery’s IR? Naturally the battery’s IR will change as the battery ages, increasing due to chemical changes and wear and tear. The temperature of the battery can also have a negative effect on IR, higher temperatures cause higher resistance (so keep your batteries cool!). It’s also important to note that the state of charge of a battery can change the IR, battery IR should always be measured fully charged. But the most important ways to keep your battery healthy are to avoid deep discharges (avoid letting your batteries drain below 10V steady-state, definitely never below 9V!), use a high-quality charger that prevents batteries from overcharging, follow the battery manufacturer’s recommended charging procedures, and use low-resistance connections (thick wires and clean connectors!).

Finally, the IR of NiMH batteries can also sometimes be decreased through a process known as “battery conditioning” (also referred to as “charge cycling”). If IR within a battery is raised due to crystal formations inside the battery, this process of conditioning can help break down those crystal formations and improve Voltage and the flow of current in a battery. Some chargers have automatic conditioning modes, but always refer to your manufacturer’s recommended procedure for charge cycling your NiMH batteries.

Week of 04/01/2024 “What makes Battery Voltage Sag? Part 2”

This Tech Tip of the Week is Part 2 in a 3-part series surrounding a question that we get asked at events all the time - “What makes battery voltage sag?”. As a battery is heavily used, teams will notice that the voltage of the battery temporarily decreases from its starting voltage during periods of heavy use, and then generally raises back up once the heavy use has subsided. So what causes this?

There are LOTS of reasons why battery voltage will sag during use. In last week’s Tech Tip we talked about battery chemistry to give an idea how a battery works, and we talked about how motor torque is inversely proportional to the power consumption (given a constant load). In this week’s Tech Tip we’ll cover two more common reasons - cell health and battery temperature. In subsequent Tech Tips we’ll cover other reasons, such as the internal resistance of the battery.

Battery cell health is an important factor in the overall health of a battery. An NiMH battery used in FIRST Tech Challenge is a multi-cell battery, meaning it’s composed of individual smaller batteries connected together. Each cell contributes to the overall power output of the battery. As a battery ages, individual cells in the battery may age at different rates - this aging can lead to degradation of cell material, electrolyte breakdown, and creation of dendrites that can eventually puncture the cell wall from inside the cell among others. Most often this cell breakdown is accelerated due to improper storage, overcharging, deep discharging, excessive temperatures, or physical damage (especially due to dropping). When a cell fails, it can lead to a reduced capacity of the battery pack, and the battery will not last as long on a single charge nor will it be able to provide the peak power output that it previously could. Failed cells can cause other cells to fail prematurely, primarily due to overcharging and imbalanced voltage due to the fact that NiMH batteries and chargers for NiMH batteries do not contain a load-balancing management system for individual cells. In some cases, failed cells can cause short circuits, overheating, and increased risk of fire/explosion! If you’re suspicious of a battery, get it tested before using it again.

Battery temperature is also an important consideration. When a battery is being charged, it will likely become warm and even slightly hot to the touch - this is expected and natural due to the process of recharging a battery. NiMH batteries deliver their best performance at moderate temperatures. When a battery is hot from charging, its internal resistance increases (we’ll cover internal resistance in a future segment) which can lead to reduced power output. Allowing the battery to cool down before use helps to ensure optimal performance. This process of allowing the battery to cool down before use can also prolong the life of the battery. This advice should also be tempered with the knowledge that most modern NiMH batteries are generally designed to handle some degree of heat; if you need to use the battery immediately after charging, it’s usually safe to do so as long as the battery is not excessively hot to the touch. However, understand that it may not provide the maximum level of power output as it would have if it had cooled first.

Week of 03/25/2024 “What makes Battery Voltage Sag? Part 1”

This Tech Tip of the Week is a short one, Part 1 in a 3-part series surrounding a question that we get asked at events all the time - “What makes battery voltage sag?”. As a battery is heavily used, teams will notice that the voltage of the battery temporarily decreases from its starting voltage during periods of heavy use, and then generally raises back up once the heavy use has subsided. So what causes this?

There are LOTS of reasons why battery voltage will sag during use. In this week’s Tech Tip we’ll cover the most common two reasons - battery chemistry and heavy use. In subsequent Tech Tips, we’ll cover other reasons, such as battery cell health, battery temperature, internal resistance, and other factors to be aware of!

The first thing to remember is that a battery is a chemical reaction factory, and does not exactly work the same as the typical “gas tank” analogy makes it seem. The chemical reactions at the electrodes create a potential difference (voltage) between them. This voltage drives the flow of electrons generated by hydrogen and hydroxide ion creation and transfer. In NiMH batteries this reaction is reversible but it takes time and energy. What’s important to understand is that the chemical reaction can happen only at a specific rate (the rate is based on a number of factors which we’ll discuss later); if the demand exceeds the rate of reaction for the battery, the voltage and current will drop until the reactions can replenish the battery output (this temporary drop is known as “sag”). As the materials at the electrodes are gradually consumed, the overall battery charge will deplete and can no longer sustain the flow of electrons, and the battery will need to be recharged or replaced.

So what is the biggest reason why batteries will sag? On a FIRST Tech Challenge robot, this reason is actuator (motor and servo) current draw. Motors and Servos can pull a considerable amount of current when they’re being used, especially when they’re being used in low-torque configurations. Motors that are geared closer to 1:1 gear ratio can spin faster - they can propel your robot’s drivetrain across the field much faster - but have less torque because of the lower gear ratio. Motor configurations that have less torque consume significantly more current to operate (when driving the same load) than motor configurations with more torque. Systems being driven by actuators that have more friction or less torque will cause the motors to consume larger amounts of current, and this can cause even healthy batteries to have their voltages “sag” during periods of high use. Teams must consider their power consumption very carefully when optimizing their battery and motor utilization during a match, even though that’s often an afterthought for most teams.

Week of 03/18/2024 “Battery Fuses”

Welcome to the Tech Tip of the Week, where hopefully after reading you don’t blow a fuse. Yup, you guessed it, we’re talking today about fuses - more specifically, we’re talking about the fuses on your Main Robot Battery.

Every legal Main Robot Battery in FIRST Tech Challenge is required to have an in-line replaceable fuse on the battery, you’ll find the fuse housing on the red (positive) cable on your battery between the battery and the connector (the top lifts off, exposing the fuse). This fuse helps protect your battery and your electronics from prolonged or excessive over-current. The fuse used with all legal batteries is a 20A Automotive-Mini (ATM) blade-style fuse, and can be found in virtually every auto parts store. It has a yellow-colored housing which easily identifies it as a 20A fuse. If you find that your battery’s voltage suddenly drops to zero (when tested using a battery tester or multimeter) it’s probably because you’ve blown your battery’s in-line fuse.

A fuse is a short span of specially-designed electrical wire intended to carry electrical loads up to a very specific amount of current. When the current loads exceed the rating, the wire within the fuse begins heating up - the more the load exceeds the rating, the hotter the wire will get. Eventually the wire will heat up so much it self-destructs and melts or burns up, breaking the circuit. This fuse-melting condition is often called “Blowing a Fuse”; the fuse is thus destroyed and is no longer usable, but it protected the electronics in the circuit as its last selfless act.

How does a fuse battery get blown? These are two of the most common reasons why a fuse can be blown:

Overcurrent Conditions - The Robot has components (generally actuators, like servos and motors) that can pull a combined current that is more than the robot’s electrical circuit can safely carry. The main electrical power wires on a robot are required to be a minimum 18AWG, which can easily continuously carry up to 16A of current. When components pull a combined current far exceeding this limit, generating unsafe heat in excess of what the wires can tolerate (risking melting the wire insulation which could lead to short circuits and fire), the fuse blows to protect the circuit. The wire size and fuse limit has been carefully selected for the safety of the robot’s electrical system. Short Circuits - Usually this happens if unshielded wires of opposite polarity touch each other in the robot’s electrical system, like when performing electrical maintenance on switches or wires (ALWAYS unplug the battery before performing any maintenance on a robot!). Other causes can be failed electronics and damaged components. This causes an extremely high current load to travel through the battery, near-instantly causing the fuse to blow. When replacing the connector on a battery, ALWAYS remove the fuse prior to performing any work - this protects the person doing the maintenance AND protects the fuse!

Always make sure your main battery fuse is replaced with the proper fuse (20A for FIRST Tech Challenge) and make sure you’re always following all safety guidelines when working with your robot’s electrical system!

Week of 03/11/2024 “Signal Filtering with Ferrite Cores”

For those about to use sensors, we salute you - with our Tech Tip of the Week! This week’s Tech Tip focuses on signal noise and how to eliminate it with ferrite cores.

When deciding to use a sensor on a robot, we’re normally worried about how accurate the sensor’s detection is, how much the sensor costs, or how the sensor’s protocol will interface with the control system. It isn’t until the device is being mounted to the robot before we consider how outside electrical noise already present on the robot might significantly impact the performance of the sensor. This electrical noise almost exclusively comes from the electric motors and other sources of electric fields on a robot, such as power wires, power supplies, some sensors (especially ultrasonic sensors and cameras), radio frequency generators (like the Wi-Fi on the robot), and other places. This electrical noise can generate unwanted currents through electromagnetic induction in nearby wires, especially sensor wires, and these unwanted currents can wreak havoc (create “noise”) within the signals from your sensors. The amount of current induced in the wire depends on several factors including the strength of the magnetic field, the rate of change of the field, and the orientation of the wire.

Some buses and wiring are more sensitive to electrical noise than others. On a FIRST Tech Challenge robot, long signal-carrying wires (such as Servo wires or I2C sensor wires) are most susceptible to induced noise. So how can we eliminate this noise? The easiest way to remove noise is through the use of a Ferrite Core. Ferrite Cores, also known as Ferrite Beads, are made of a ceramic material called ferrite that has incredibly useful magnetic properties. When a Ferrite Core is clipped around a signal-carrying wire, the induced “noisy” alternating currents in the wire generate electrical fields in the ferrite that act to oppose those currents - this has the effect of canceling out or removing the high-frequency noise. It’s not typically required to “loop” the cable around the ferrite core, but doing so could increase the efficiency of the noise filtering in cases where excessive noise is being generated. You can find ferrite cores already installed in cables meant for high-noise environments or highly sensitive devices such as USB webcam cables and monitor cables. It’s best to place ferrite cores on the wire closest to the connector leading into the Control/Expansion Hub port.

Week of 02/19/2024 “Robot Wi-Fi Link Speed”

In last week’s Tech Tip of the Week we talked about Wi-Fi Signal Strength. This week’s Tech Tip rounds out the Wi-Fi reporting features and introduces Link Speed and the Signal Bar Graph, both found on the FTC Driver Station App.

Link Speed is the speed (in Mbps) at which a Wi-Fi connection can communicate, and it generally ranges from a snail-like 1Mbps through about 100Mbps, which is the maximum practical rate for an 802.11ac/b/g/n/w Wi-Fi network (when using a Control Hub and Driver Hub). It’s important to understand the difference between Signal Strength and Link Speed. Signal Strength is often used to describe how “loud” a connection is, and Link Speed is used to describe how “fast” a connection can communicate. Link Speed can also be a secondary indicator of how much “noise” or “interference” a communication channel has; the “louder” the signal and “clearer” the communication channel, the “faster” the devices can generally communicate. Wi-Fi link speeds are automatically renegotiated periodically and they’re most often affected by noise, channel congestion (too much happening at once), and distance.

A Wi-Fi channel is like a room where only one person/device is ever allowed to talk at a time. If each person/device can talk in short, fast bursts (fast link speed) then everyone has an opportunity to speak within a short duration of when they want to speak. However, if one or more devices are speaking slowly (slow link speed) then all devices have to wait for them to finish before they can talk REGARDLESS of their own link speeds - this invariably introduces communications lag. This example highlights the fact that even though it’s important for a given device to have a strong signal and a fast link speed, it’s important for ALL devices communicating on a channel to have a strong signal and fast link speed. As the idiom goes, it only takes one rotten apple to spoil the whole bunch.

Finally the Signal “Bar” Graph attempts to combine the Signal Strength and Link Speed into an easy to understand graphical meter. The more bars, the stronger and clearer the signal and the faster the communications.

NOTE: The Driver Hub has a known bug where the Link Speed indicator only shows the initially negotiated link speed, and the link speed indicated does not change when the Wi-Fi device renegotiates different link speeds. This means the Link Speed indicator and the Bar graph are not represented accurately on Driver Hubs, but are represented accurately on all legal phones.

Week of 01/29/2024 “REV Driver Hub Tips”

Welcome to the Tech Tip of the Week! This week is a long one, filled with great REV Driver Hub tips. Most everything here can be found in REV’s Driver Hub Troubleshooting tips page, we’ve just annotated a few of these for the most common scenarios you’ll potentially experience with the REV Driver Hub. Understand that this Tip of the Week is not meant to disparage the REV Driver Hub in any way - no device is perfect, but the REV Driver Hub can provide you trouble-free performance if you can understand its nuances and take a few additional steps to keep it running optimally.

Make sure your REV Driver Hub time/date is set correctly! This is the cause of a number of inspection nightmares and Robot Controller log file confusion, the first step should always be to check to make sure the Date/Time on the Driver Hub is set correctly. This is set through the normal Android System Settings by pulling down the Android Quick Settings pull-down twice, tapping the Gear Icon, selecting System, and then selecting “Date & Time”.
USB wall chargers are all the same, right? Wrong. A/C-to-USB wall chargers can range drastically in power (measured in Watts) - the REV Driver Hub comes with an A/C-to-USB wall charger, and that is the recommended wall charger to use to charge the REV Driver Hub. Can you use another device to charge the REV Driver Hub? Maybe, but it’s best to stick to either the one that ships with the REV Driver Hub or a fully-charged USB Battery Pack like the Anker 10,000mA Power Bank which can keep a Driver Hub fully charged all day without ever needing to put the Driver Hub to sleep.
Rechargeable Lithium batteries don’t necessarily work the same way that other batteries work, they all have a slightly different usable Voltage range. The REV Driver Hub needs to calibrate to the Voltage range of the internal lithium battery plugged into it, and to do that there’s a full calibration process that has to be followed for any new battery, along with a verification step. DO NOT simply “replace” a drained battery with a new charged one when it gets low, the new battery is NOT guaranteed to have the same calibration as the first and it is not guaranteed to perform optimally. If you’re having problems keeping the REV Driver Hub internal battery charged, consider a USB Battery Pack like the Anker 10,000mA Power Bank.
Battery safety in any Lithium Battery system is paramount, and the REV Driver Hub has battery safety features that most teams will likely run into at least once. The most commonly experienced safety feature is the Battery Lockout system. If a REV Battery depletes to a level below its recommended safe level, or the battery is overcharged, the REV Driver Hub will enter lockout mode to protect the battery. In this mode, the REV Driver Hub will not power on when the battery button is held down. The process for recovering from Battery Lockout can take several minutes, but it’s better than the alternative. It’s not recommended to leave a REV Driver Hub on charge unattended for more than 8-10 hours, and definitely NOT for multiple days.
When a user puts the REV Driver Hub to sleep, or if it goes to sleep on its own because the Driver Station App main screen is not actively running in the foreground, it goes to sleep pretty easily. However, when the REV Driver Hub returns from a sleep state, sometimes the Wi-Fi and the gamepads will not reload correctly or automatically; this requires you to unplug and replug the gamepads from the REV Driver Hub before you can use them again, or perform a hard reboot in order to bring Wi-Fi connectivity back. Many veteran teams use a fully-charged USB Battery Pack, like the Anker 10,000mA Power Bank, and leave the Driver Station App main screen running all day without putting the device to sleep.
Keep the REV Driver Hub safe by using 3M Dual-Lock or hook-and-loop fasteners (like those sold by Velcro Brand) to mount the Driver Hub to a Driver Station Carrier. This prevents your REV Driver Hub from being placed on the floor (where team members may step on it) and prevents you from accidentally dropping the Driver Hub on the floor - dropping the Driver Hub is the #1 cause of all Driver Hub damage! Some teams have designed their own custom Driver Station Carriers, be creative and have fun!
When the REV Driver Hub is not in use (not at competitions, not in use during practices) it should be turned OFF and have all sources of power disconnected. Do not put the Driver Hub to sleep, but actually turn it off - press the power button for 1-2 seconds and then use the drop-down menu to turn off the device. The Driver Hub uses power even in sleep mode, and that can lead to a dead battery and you may have to perform Battery Lockout Recovery before you can turn it back on.
Sometimes teams may experience “random power loss” on the REV Driver Hub. This is usually due to a battery fitment issue within the battery box on the device (the battery momentarily stops making a connection with the power pins on the device), and can be mitigated using techniques from the REV Troubleshooting tips. Some teams have been known to operate their REV Driver Hubs without a battery inserted at all, and simply run the Driver Hub using a fully-charged USB Battery Pack, like the Anker 10,000mA Power Bank. The jury is still out on whether that’s a good idea, but worth considering if you’re having problems that you’re desperate to solve and REV Support is unable to help you resolve (because of time pressures) before your big event.
Ensure your REV Driver Hub is fully updated. Firmware 1.2.0 solves a host of REV Driver Hub issues, and it makes sense to use the on-board updater (once connected to Wi-Fi) to perform all updates on the Driver Hub.
This isn’t specifically a REV Driver Hub tip, but it’s a question we get asked all the time. Did you know that the Robot Wi-Fi network name (Robot Controller Name) and the Wi-Fi passwords can be managed straight from within the Driver Station app? With the Driver Station App connected via Wi-Fi to the Robot Controller, click on the three dots menu on the upper-right and select “Program and Manage”, then use the hamburger menu on the upper-left and select “Manage”. On this page you’ll find all of the same settings as you’d find on the webpage by logging in to the controller on a laptop!

Week of 11/06/2023 “Driver Hub or Smartphone?”

This week’s Tech Tip of the Week briefly discusses the pros and cons of Smartphones versus the Driver Hub. Which one should you use? Are there hidden benefits or perils for using one over the other?

The REV Driver Hub is the standard FIRST Tech Challenge Driver Station hardware device. It boasts three USB-A ports for plugging in gamepads, a USB-C port used for communication and charging, a large touch screen, and an unused Ethernet port (for future-proofing). This device runs the Android operating system, maintained by REV Robotics, and uses Wi-Fi to communicate with the REV Control Hub.

Driver Hub Pros

Driver Hub and Control Hub combo use 802.11w for communications. No approved Smartphone supports 802.11w communications.

802.11w offers encryption of control packets, which prevents many Wi-Fi attacks by remote routers/devices.

Driver Hub is a “standard” FIRST Tech Challenge Driver Station device, which provides long-term support for FIRST Tech Challenge. The average SmartPhone is deprecated within 2 years after being released, but the Driver Hub is supported as long as it’s legal to use in FIRST Tech Challenge.

Driver Hub has a USB-C port, which allows for charging while it’s being used.

USB-C port allows use of external battery packs, which are necessary for sustained use of PS4 and PS5 gamepads which leech power from the Driver Station to charge their own internal batteries.

A single 10,000mAh External battery pack allows Control Hub to be used non-stop over the course of an entire day.

Driver Hub has 3 USB-A ports, so no external USB hubs and additional cables are required for using multiple USB gamepads. This makes the Driver Hub very compact and easy to manage.

Driver Hub Cons

Driver Hub still has Power Management issues

Driver Hub needs battery compartment tweak to ensure internal battery makes good connection. Foam insert in battery compartment helps, but doesn’t always perfectly fix the problem.

Driver Hub cannot boot if the internal battery is too low, even if plugged into external battery. If battery dies, troubleshooting requires removal of battery to power device.

Power Management bugs can drain battery while charging.

Driver Hub USB ports are fragile

Teams carrying their Driver Hubs around without a Driver Station tray (NOT RECOMMENDED) have dropped their Driver Hubs with gamepads plugged in, and impact can damage USB-A ports.

Display screen ribbon cable comes loose

If the screen stops working, opening the back of the device and re-seating the screen ribbon cable can sometimes fix screen issues.

Turning off the display unloads gamepad drivers, but turning the display back on does not reload them. USB devices must be re-plugged in order to trigger USB driver loading.

USB-C to USB-C cables do not work with Driver Hub. USB-A to USB-C cables are required in order to use the USB-C port.

On the other hand, several off-the-shelf SmartPhones are supported, including the Motorola Moto E4 and Moto E5 phones. These devices, like the REV Driver Hub, run the Android mobile operating system and use Wi-Fi to talk to the REV Control Hub (therefore no SIM card or cell plan is required). SmartPhones use USB-OTG to interface with gamepads and external USB hubs necessary for operating multiple gamepads.

SmartPhone Pros

SmartPhones are typically cheaper than Driver Hubs, and generally survive being dropped better.

SmartPhones don’t have the same power management issues that Driver Hubs are known to have.

Some teams report having better Wi-Fi consistency with SmartPhones than Driver Hubs, though that has not been verified or debunked in any way.

SmartPhone Cons

There are only a small number of approved Android Smartphones, none of which are still supported by the manufacturers of the phones.

SmartPhones are deprecated typically within 2 years after being released. Security updates and OS updates are not guaranteed.

The number of approved SmartPhones are dwindling, and SmartPhones are becoming increasingly difficult to obtain. New SmartPhones are not being approved to replace older ones.

Android is not a consistent platform in the Mobile Phone industry. Each manufacturer, and sometimes even within product families, will produce their own “flavor” of Android which has different software requirements and behaviors. Supporting the different manufacturers in the changing Android landscape is near impossible.

There is very little consistency between smartphones of the same model sold in different countries - each will have their own firmware with their own quirks, often impossible to debug or avoid.

FIRST Tech Challenge is not enough of a volume consumer to be able to set requirements or have partnerships with SmartPhone manufacturers.

SmartPhones cannot use 802.11w for encryption of Wi-Fi control packets, which makes the connection between devices vulnerable. Rogue Access Point Detection and Quarantine features within venue network security systems (like within schools and other venues) can interrupt these communications seemingly randomly, making connections difficult to maintain.

SmartPhones cannot be used at the same time they’re being charged, so teams frequently run down the internal batteries on the phones during the course of an event. Careful battery management is required.

PS4 and PS5 gamepads with internal batteries will further drain the SmartPhone batteries, as they leech power from the Driver Station in order to maintain a full charge level for their own batteries.

SmartPhones require USB-OTG cables and external USB Hubs are also required in order to use multiple gamepads, and each cable/connection and device is a potential source of failure. Extreme care must be taken to ensure the connections remain solid.