Short answer: a relay remote can switch a motor on and off, select a few fixed speeds, or tell a separate controller to run faster or slower. It cannot, by itself, provide smooth proportional speed control. If the operator expects the machine to respond to how far a trigger, joystick, or knob is moved, the radio system must transmit a changing command value and the machine still needs the right motor drive, VFD, or proportional valve controller.
This distinction causes more wrong selections than it should. A customer asks for “wireless speed control,” receives a four-relay receiver, and discovers during commissioning that the outputs only provide four electrical states. Nothing is defective. The control requirement was never defined precisely enough.
“Speed control” can mean three different jobs
Before looking at frequency, range, or channel count, decide which of these the operator actually needs.
Fixed-speed selection
The machine has two or three preset speeds. A relay may select LOW, MEDIUM, or HIGH at the VFD or controller input. The speed changes in steps, but this is often perfectly adequate for fans, conveyors, pumps, and simple winches.
Increment and decrement
Two buttons tell an existing controller to increase or decrease its setpoint. The receiver still sends discrete commands. The controller stores and ramps the speed. This feels adjustable to the operator, but the relay receiver is not generating the speed reference.
True proportional control
A joystick, trigger, or rotary control produces a continuously changing command. Half travel might request half speed; releasing the control must return the request to neutral. This needs more than ON and OFF. The system must measure the operator input, encode a value, transmit it repeatedly, validate it at the receiver, and deliver it to the machine in a usable form.
Once we separate these three cases, most of the hardware decision becomes straightforward.
A relay is a decision, not a setpoint
A relay contact is excellent at answering a yes-or-no question: run, stop, forward, reverse, enable, or select preset 2. It does not naturally describe 37% speed or a joystick position of -420 counts.
There are ways to combine several relays into a coded value, but I rarely recommend that for proportional motion. It consumes outputs, creates transition states, and still gives coarse steps. More importantly, the machine must decide what to do if one contact arrives late or fails. A proper data or analogue interface is cleaner and easier to diagnose.
Operator input → encoded command value → RF link → freshness and identity checks → machine interface → drive or valve controller → actuator
The radio link is only one part of that path. Smooth motion depends on every part agreeing about value range, neutral, update rate, ramping, and fail-safe behaviour.
Match the receiver output to the machine controller
The correct receiver is usually chosen by the input the machine already accepts.
0–10 V: common on VFDs and industrial speed controllers. Check whether zero volts means stop, minimum speed, or a broken wire.
4–20 mA: useful over longer cable runs and easier to supervise for open-circuit faults. Confirm what value represents neutral or stop.
PWM: common on compact DC motor and embedded controllers. Frequency, duty-cycle range, logic level, and ground reference must match.
CAN, RS-485, Modbus, or another fieldbus: often the best choice when the machine already has a controller. The command can include value, direction, status, and fault information without extra relay wiring.
Up/down relay inputs: acceptable when the VFD or controller owns the speed setpoint and ramp. The remote is requesting adjustment, not generating an analogue reference.
Do not connect a low-level proportional output directly to a motor or hydraulic coil unless the receiver is specifically designed as the power driver. Most are not. A 0–10 V signal cannot supply motor current, and a communication output cannot replace a valve amplifier.
DC motors, VFDs, and hydraulic valves are different problems
DC motor speed
For a brushed DC motor, speed is commonly controlled by a PWM motor controller. The wireless receiver should provide the controller with an enable, direction, and speed request. The motor controller handles current, switching losses, acceleration, braking, and protection.
I would not ask a small receiver relay to chop motor current for speed regulation. Relay contacts are not designed for high-frequency PWM, and the result is short relay life rather than controlled speed.
AC motor with a VFD
The VFD should remain responsible for the motor. A relay remote can select preset frequencies or send run and direction commands. For smooth adjustment, use the VFD’s analogue input or fieldbus interface. Keep the existing emergency stop and safety chain hardwired according to the machine design; a wireless speed request is not a replacement for them.
Hydraulic proportional valve
This is where casual “wireless dimming” ideas become expensive. A proportional valve may need a controlled coil current, dither, deadband compensation, ramps, and direction logic. The receiver should send a command to the valve amplifier or machine controller. The amplifier, not the RF board, should regulate the coil.
Hydraulic systems also move differently under cold oil, changing load, and pressure variation. A clean joystick value does not guarantee a constant actuator speed. Commission the complete machine, not just the radio.
Update rate matters, but faster is not always better
A proportional command must be refreshed often enough to feel responsive and to prove that the link is still alive. For many industrial hand controls, tens of updates per second is a sensible starting range. The exact number depends on the machine dynamics, permitted radio duty cycle, protocol, and how the receiver filters the command.
Increasing the packet rate can reduce available airtime and battery life. It can also make collision behaviour worse when several transmitters share the area. I prefer a stable, measured update rate with sequence checking and a defined timeout over an impressive headline number that collapses under real site conditions.
Define neutral before defining full speed
At commissioning, everyone wants to see full travel. I start with neutral.
What value is transmitted when the control is released?
How wide is the neutral deadband?
Does a broken joystick wire look like neutral, full scale, or an invalid reading?
What happens while the transmitter starts up?
Can calibration drift create a small unwanted command?
Does the receiver output neutral immediately when packets become stale?
A machine creeping at 3% command is usually more troublesome than failing to reach 100%. Spring-return controls, input plausibility checks, and a deliberate neutral deadband are worth specifying.
Signal loss should produce a planned transition
For a light dimmer, holding the last value may be acceptable. For a winch, vehicle function, conveyor, or hydraulic motion, it often is not. The receiver needs a command-age timer. If fresh valid packets stop, the output should move to the defined safe state within a tested interval.
“Stop immediately” also needs engineering judgment. Dropping a heavy load, removing hydraulic pressure abruptly, or applying aggressive braking can create a second hazard. Sometimes the correct response is a controlled ramp to zero followed by disabling motion. That sequence belongs in the machine controller and must be tested with the actual load.
The commissioning test I use
Power the receiver before the transmitter. Confirm the speed request remains neutral.
Power the transmitter with its control off-centre. Confirm the system rejects motion until the control returns to neutral.
Move slowly through the full input travel. Check direction, deadband, linearity, minimum useful command, and full-scale limit.
Release the control from several positions. Verify the return-to-neutral time and mechanical response.
Interrupt the RF path while moving. Measure the real timeout and the machine’s stopping behaviour.
Run the motor, contactor, pump, or hydraulic power unit under load. Electrical noise often appears only after the high-current equipment starts.
Operate other nearby remotes at the same time. The command may pause briefly, but it must not jump, reverse, or remain latched.
Disconnect each command wire in turn. Confirm the controller detects or safely handles the fault.
Cycle power to the transmitter, receiver, and machine controller in different orders. No power-up sequence should create motion.
Record command value and machine response if the controller allows it. A ten-second trend of joystick input, received setpoint, and actual speed settles arguments that cannot be solved by watching the shaft.
When a relay remote is still the right answer
Do not reject relay systems just because proportional control sounds more advanced. A two-speed fan, preset conveyor speeds, a pump with fixed operating points, or a winch that only needs jog and stop may be safer and easier to maintain with discrete commands.
I choose proportional wireless control when the operator genuinely needs continuous control of motion or process output. I choose relays when the machine already knows the operating points and the remote only needs to select them.
What to tell the supplier
A useful request should state the actuator type, machine controller or drive model, accepted input interface, command range, neutral definition, required update rate, signal-loss action, maximum response time, number of transmitters, operating distance, and local frequency rules. If a joystick is involved, include its axes, spring-return behaviour, deadband, and whether simultaneous movements are allowed.
“Four channels with speed control” is not enough information. “One spring-return joystick axis, neutral at 5 V, ±10 V command to an existing valve amplifier, 100 ms maximum stale-command timeout, controlled ramp to zero” gives an engineer something that can actually be designed and tested.
Bottom line
A wireless relay can select speeds; it cannot create smooth proportional control on its own. For true variable motion, transmit a validated command value and let the correct drive, VFD, valve amplifier, or machine controller regulate the actuator. Define neutral and signal-loss behaviour first, then test the complete machine under load.