How LEO Satellites Are Changing Motion Control in SATCOM Systems
Low Earth Orbit (LEO) satellites are changing the motion control requirements of SATCOM systems, and with them, the demands placed on motors.
Download our Technical Guide to Motors for SATCOM Systems to learn more about the motor technologies used in SATCOM systems and what to consider when choosing a motor.Â
Satellite communication has developed in stages. At first, a dish was pointed at a geosynchronous satellite and, because that satellite moved with the Earth, only small adjustments were needed. Mobile platforms such as ships and aircraft came next. When aircraft began using satellite connections for onboard Wi-Fi, they needed a gimbal that could keep the antenna pointed at a single satellite as the aircraft moved.Â
With today’s LEO constellations, the motion control required is far more complex than tracking a single geosynchronous satellite from a moving ship, because the satellites are moving, many terminals are moving and, in many constellations, the satellites also communicate with each other.Â
Direct Drive and Geared Systems in SATCOMÂ Â
Larger systems generally use geared solutions, while smaller systems generally use direct drive. Large ground station dishes, for example, have traditionally used motors with gearing because of their size. In LEO systems, the trend is toward direct drive motors integrated into the gimbal. In these applications, direct drive removes the need to manage how gears and their lubrication behave across temperature differences, and can offer greater reliability and better control.Â
Speed also matters. A ground system tracking LEO satellites follows one satellite across the sky, then needs to move back quickly to pick up the next one coming into view. Accuracy remains essential too, because the greater the distance, the larger the error caused by a small change in angle. Precision and accuracy continue to drive decisions in SATCOM motion systems.Â
Thermal Challenges for Motors in LEO Satellites Â
In the past, much of the engineering effort for space hardware went into surviving the vibration and temperature of launch. Once in orbit, the environment was relatively well understood. LEO satellites, however, remain subject to a great deal of variability that needs to be engineered for.Â
In space there is no convection, so there is no surrounding air to carry heat away as there would be on the ground. Instead, heat has to be removed largely through conduction, out through the motors and moving parts. As a LEO satellite’s position relative to the sun changes, its components can also cycle from very cold to very hot multiple times a day. This challenges the selection of bearings, epoxies and traditional assembly methods, as materials expand and contract. The same system must work in hot conditions on the ground, or in a rocket before launch.Â
Temperature cycling is one of the most overlooked factors. Datasheets often do not state how many temperature cycles a motor can withstand before it degrades, as many motors are used in factory settings, where they run for years.Â
A high motor constant, which describes how much torque a motor can produce for the amount of heat it generates, allows a motor to deliver its performance with less heat and, generally, less weight. However, performance can also depend on the application. In the eyes of the customer, a motor that runs too hot may be seen as a low-performance motor.Â
Why Analysis Matters in SATCOM Motor SelectionÂ
With information so easy to find online, it can be tempting to select a component and test it without carrying out the analysis first. In SATCOM, this is rarely an option, as it costs a great deal to put a component into space and then find out it does not perform. Today’s tools make analysis much faster, but it still needs to be done, so that engineers understand why a design works, not simply that it works.Â
Get in touch to speak with a Solutions Engineer about the right motor for your LEO or SATCOM application, or download our Technical Guide to Motors for SATCOM Systems.Â