A customer once put two 433 MHz products on my bench and asked a reasonable question: “They use the same frequency, so why will they not pair?” One unit used ASK. The other used FSK. The frequency printed on the label described where they transmitted, but not how they carried the data.
This distinction matters more than many datasheets suggest. ASK and FSK are not merely two names for long-range and short-range radio. They are different ways of placing digital information onto an RF carrier. The choice affects the receiver, occupied bandwidth, immunity to certain kinds of noise, current consumption, cost, and—most importantly—compatibility.
Frequency tells you where; modulation tells you how
Think of 433.92 MHz as the address of a lane on the radio spectrum. Modulation describes how the transmitter moves within that lane to represent ones and zeros.
With amplitude-shift keying, the transmitter changes the strength of the carrier. The common low-cost form is on-off keying, or OOK: carrier on for one state, carrier off for the other. Many key-fob remotes, door sensors, simple relay controls, and alarm transmitters use this method.
With frequency-shift keying, the transmitter keeps a more nearly constant amplitude and moves between two nearby frequencies. One frequency represents one binary state and the other represents the opposite state. The distance between them is the frequency deviation.
Both systems may be described as “433 MHz.” That does not make them interchangeable. A receiver designed and configured for ASK normally cannot decode an FSK transmission, and the reverse is also true.
Why ASK remains common
ASK is popular for good reasons. The transmitter circuit can be simple, the bill of materials can be low, and a battery transmitter can remain asleep almost all the time. When a button is pressed, it sends a short coded burst and returns to sleep.
In a quiet environment and over a sensible distance, a well-designed ASK link is entirely dependable. I have seen simple ASK controls run for years in gates, lamps, doors, pumps, and small machinery. There is no engineering value in replacing a proven ASK link only because FSK sounds more sophisticated.
The weakness is contained in the name: information is carried in amplitude. Electrical interference also changes the amplitude seen by the receiver. A switching power supply, relay contact, brushed motor, ignition system, or nearby transmitter can raise and lower the received energy. The receiver has to decide whether that energy is a valid bit or noise.
Good receivers manage this with filtering, automatic gain control, timing checks, packet validation, and repeated frames. Very cheap wideband receivers manage it poorly. Two products can both use ASK at 433.92 MHz and have completely different field performance.
What FSK improves—and what it does not
FSK carries the data in frequency rather than amplitude. That gives the receiver a useful advantage when the main disturbance is amplitude noise. Short noise spikes may make the signal stronger or weaker, but they do not necessarily move it to the expected mark or space frequency.
FSK also works well with receiver architectures that limit amplitude variations before demodulation. In industrial environments with contactors, motors, long cables, and switching supplies, this can produce a noticeably cleaner link.
However, FSK is not immune to interference. An in-band carrier, another FSK transmitter, a wideband noise source, or a badly placed antenna can still block it. Poor frequency accuracy can shift the transmitter outside the receiver’s useful bandwidth. Excessive deviation can spread the signal; insufficient deviation makes the two states harder to separate.
I would never approve an FSK system based only on the letters “FSK.” I still want to know the receiver sensitivity, test conditions, data rate, deviation, selectivity, blocking performance, antenna arrangement, packet retries, and failure behavior.
The receiver often matters more than the modulation label
Older low-cost remote controls sometimes use super-regenerative receivers. They are simple and sensitive enough for basic work, but they tend to have wide bandwidth, limited selectivity, and inconsistent behavior near strong signals.
A superheterodyne receiver generally provides a narrower, better-controlled channel and better rejection of signals outside that channel. Modern integrated RF receivers can support ASK, FSK, or both with programmable bandwidth and data slicing.
This is why a comparison such as “ASK reaches 100 metres, FSK reaches 500 metres” is not a fundamental rule. It compares complete products, not modulation alone. A carefully designed ASK superheterodyne link can outperform a badly designed FSK link. Receiver architecture, antenna efficiency, transmit power, noise floor, and protocol margin all contribute.
Do not compare sensitivity numbers without the test conditions
A receiver sensitivity of −110 dBm looks better than −105 dBm, but the difference is meaningful only when both numbers use comparable conditions.
Check at least these items:
Data rate: lower rates generally allow narrower bandwidth and better sensitivity.
Error criterion: the figure may be measured at a stated bit-error rate or packet-error rate.
Modulation settings: FSK deviation and shaping affect the result.
Receiver bandwidth: wider bandwidth admits more noise but may tolerate more frequency error.
Coding and packet length: a long packet has more opportunities for an error than a short one.
Measurement point: conducted sensitivity at an RF connector is not the same as complete product range with a small internal antenna.
When these conditions are missing, I treat the sensitivity figure as a clue, not a guarantee.
Protocol quality is separate from modulation
ASK and FSK describe the physical radio signal. They do not tell you whether the system uses a fixed code, learning code, rolling code, address filtering, acknowledgement, encryption, or command repetition.
A robust packet normally includes enough preamble for the receiver to settle, a synchronization pattern, an address, command data, and an error check. Critical controls may repeat the packet or require an acknowledgement. Safety-related motion must also have a defined response to a lost or invalid link.
Changing from ASK to FSK does not automatically add security. It does not prevent an unauthorized transmitter from sending a correctly formatted command. Security and authorization must be designed at the protocol and receiver logic layers.
Battery life and response time depend on the whole system
Simple OOK transmitters can be extremely economical because the RF carrier is off during one of the symbol states and the device transmits only in short bursts. That suits key fobs and sensors that may run for years from a small battery.
FSK transmitters normally maintain the carrier while shifting frequency during a packet. Modern transceivers are efficient, but their synthesizer start-up, packet duration, transmit current, and sleep current still need to be counted.
Do not judge battery life from modulation alone. A poorly written device that wakes too often will waste more energy than the difference between ASK and FSK. For a handheld remote, measure current during a real button press and check the quiescent current between presses.
Response time also comes from packet length, data rate, repetitions, receiver polling, and confirmation logic. A fast modulation setting can still feel slow if the protocol waits through several retries.
Compatibility requires more than matching 433 MHz
Before mixing a transmitter and receiver, confirm the complete radio definition:
Nominal frequency and regional version.
Modulation: ASK/OOK, 2-FSK, GFSK, or another format.
Data rate and symbol timing.
FSK deviation, when applicable.
Receiver bandwidth and frequency tolerance.
Bit polarity and encoding, such as pulse-width, Manchester, or NRZ.
Packet structure, address format, command definitions, and checksum.
Pairing or learning procedure.
If one of these is unknown, “same frequency” is not enough. I prefer a matched transmitter-receiver set or a verified protocol specification over trial-and-error pairing.
When I choose ASK and when I choose FSK
I normally choose ASK when the application is simple, the operating distance is moderate, the RF environment is reasonably clean, battery life and cost are important, and there is already a proven matched product.
I lean toward FSK when the installation has frequent electrical noise, needs longer or more consistent range, operates near other sub-GHz devices, requires narrower channel behavior, or uses a bidirectional radio with acknowledgements and diagnostics.
There are exceptions. A noisy site can sometimes be fixed by moving the antenna, separating the receiver supply, adding suppression at the load, or replacing a wideband receiver with a better ASK superheterodyne model. Changing modulation is not the first repair for poor installation.
A practical bench test before installation
For either system, I test the complete transmitter and receiver as they will be used:
Use the production antenna, enclosure, supply voltage, and cable length.
Repeat the test with motors, relays, chargers, and switching power supplies operating.
Test with the control cabinet closed; an open metal door can make a bad antenna location look good.
Walk through the real operating area and approach from different orientations.
Check command latency and missed packets, not only the maximum point where one command occasionally works.
Repeat with a low transmitter battery and at the expected temperature limits.
The useful range is the distance where every normal command works with margin. The last spot where one packet gets through is a demonstration, not a design value.
The engineering answer
ASK is simple, efficient, and perfectly suitable for many remote-control jobs. FSK usually gives the receiver a better basis for rejecting amplitude noise and is often the stronger choice in demanding RF environments. Neither one guarantees range or reliability by itself.
Treat modulation as one part of a complete link. Match the transmitter, receiver, antenna, bandwidth, data rate, protocol, power supply, and installation. Once those pieces are correct, the ASK-versus-FSK decision becomes practical rather than promotional—and the system behaves much more predictably in the field.