Most RF projects do not fail because the radio link is impossible. They fail because the quotation starts from a transmitter photo and a target distance while the electrical load, control logic and installation conditions are still undefined.
A good RF specification does not need to be long. It needs to remove the few ambiguities that cause the wrong receiver, undersized relay contacts, unreliable range or unnecessary redesign. The following is the checklist I use before approving a first sample.
1. Start with the equipment being controlled
Do not begin with button count or enclosure style. Begin at the receiver terminals.
Supply: AC or DC, nominal voltage and the real operating range.
Load: motor, lamp, solenoid, contactor, controller input or another device.
Current: normal running current and, where relevant, startup, inrush or stall current.
Output interface: dry contact, switched voltage, logic-level signal or serial interface.
A receiver rated for a 10 A resistive load is not automatically suitable for a 10 A motor. Motors, solenoids and some LED drivers can produce a much higher transient current than their steady-state value. If the load data is uncertain, use the receiver to drive a correctly selected contactor or driver stage instead of asking a small PCB relay to carry the full stress.
2. Define what must happen when each button is pressed
“Two channels” is not a complete control description. Two outputs may represent two independent loads, forward and reverse, open and close, or one load with two operating modes. Those cases require different logic.
For each button, specify one of the following:
Momentary: the output remains active only while the button is held.
Toggle: one press turns the output on and the next press turns it off.
Latched set/reset: separate commands turn an output on and off.
Interlocked: activating one direction forces the opposite direction off.
Interlocking is essential for many reversible motors and actuators. It should be implemented in the receiver logic, and often backed up electrically, rather than left to the operator’s timing. Also state what the system must do after a power interruption: remain off, restore the previous state or return to a defined safe position.
3. Count functions, not buttons
Button count and channel count are related, but they are not the same thing. A four-button transmitter may control two reversible motors, four independent relays, or a single device with several commands. Write down the required functions first, then map them to transmitter buttons and receiver outputs.
If future expansion is likely, reserve the channel in the protocol and PCB design early. Adding one unused command during the first design is usually inexpensive; changing the transmitter, decoder and enclosure after tooling is not.
4. Treat range as a system requirement
Open-field range is useful for comparing systems under controlled conditions, but it is not a guarantee inside a machine room, warehouse or reinforced-concrete building. Real range is affected by:
antenna type, length, orientation and ground reference;
metal enclosures and the position of the receiver inside the product;
walls, vehicles, machinery and people in the path;
local interference and receiver selectivity;
transmitter battery voltage and the way the operator holds the remote.
Describe the real site and the required worst-case operating point. For a metal control cabinet, plan an external antenna or an RF-transparent antenna area. For a long-range application, ask for link margin and test the final antenna arrangement—not only the bare receiver on a laboratory bench.
5. Choose frequency and coding for the market and risk
Frequency should be selected after the destination market, antenna constraints, interference environment and certification path are known. Common sub-GHz options include 315, 433.92, 868 and 915 MHz, but availability does not mean every band or power level is permitted in every country. Confirm the final configuration against the regulations and certification requirements of the sales region.
Do not choose a frequency only because a higher open-field distance appears in a catalogue. Antenna efficiency, receiver performance, permitted transmit power and the installation often matter more than the number printed on the label.
Coding deserves the same attention. Simple learning-code systems are practical for lighting, demonstrations and many low-risk industrial commands. Access control, security-sensitive equipment or applications exposed to deliberate replay may require a rolling-code or otherwise authenticated design. State the risk level early; changing the coding architecture late can affect both hardware and firmware.
6. Include power and standby requirements
For a mains-powered receiver, standby consumption may be a secondary concern. For a battery product, it can define the entire architecture. Provide:
battery chemistry and nominal capacity;
target standby time;
expected commands per day;
wake-up time and acceptable response delay;
low-voltage cutoff or battery indication requirements.
A low-power receiver may sleep between listening windows, which reduces current but can add response delay. There is no universal best setting. The right balance depends on battery life, required reaction time and how frequently commands are sent.
7. Set the mechanical and environmental boundaries
The electrical design is only half of the product. Specify transmitter size, button labels, key life, mounting method, cable exit, connector type and enclosure color. For the receiver, include the available PCB space, fastening points and connector orientation.
Temperature, humidity, dust, water exposure, vibration and impact requirements should be stated in measurable terms where possible. “Outdoor” is not a test condition. If the remote will be used with gloves, in rain or around oil, that changes the keypad, enclosure seal and label construction.
8. Approve a sample against a written test plan
A sample should answer engineering questions, not merely prove that the relay clicks. Before testing, agree on the following:
functional sequence for every button and output;
range test location, antenna position and pass/fail point;
operation at minimum and maximum supply voltage;
load switching, including startup and repeated cycling;
power-loss recovery and fail-safe behavior;
pairing, memory capacity and replacement-transmitter procedure;
basic environmental and mechanical checks relevant to the application.
Record the receiver revision, transmitter revision, frequency, code format and antenna used for the approved sample. Without that record, a later production sample can look identical while behaving differently.
The minimum information to send with an RF control inquiry
Destination country or region
Controlled equipment and load type
Supply voltage and operating range
Running, inrush or stall current where applicable
Required functions and control mode
Number of transmitters and receivers that must work together
Required range and a short description of the installation
Preferred frequency or certification constraints, if already fixed
Enclosure, connector, logo and packaging requirements
Expected annual quantity and sample timing
If two or three items are still unknown, that is normal. Send the known boundaries first. A competent supplier should identify the missing decisions and explain their effect on cost, range, safety and schedule before recommending hardware.
Engineering judgment matters more than a long specification
The purpose of this checklist is not to make the inquiry complicated. It is to prevent a simple purchasing shortcut from becoming a field failure. Once the load, control logic, environment and market are clear, the transmitter style and receiver platform are usually straightforward choices.
ANRIVERS can review an existing specification or help convert a short application description into a sample-ready RF control requirement.