On-Off-Keying (OOK)

Transmit Data Using Simple OOK Protocol, Or Mimick More Sophisticated Encoding Formats Like EV1527

The most fundamental digital ASK encoding scheme is On-Off keying (OOK).

Transmits Any Data

You can use it to transmit any type of data, for example sensor readings or even text messages.

EV1527 For Remote Controls

One specific use case is the EV1527 encoding commonly used in commercial remote controls such as garage door openers or home automation plugs:

Any generic OOK device can be programmed to understand the EV1527 encoding and act as a remote control or remotely controlled device.

OOK vs. EV1527-Ready

There is a wealth of breakout boards available that can transmit and receive radio signals in the Short Range Device frequency bands.

The fundamental difference - and important choice for you - is whether you want a breakout board that uses generic OOK, or whether you choose a dedicated EV1527 device/board.

  • OOK: Generic OOK devices can send or receive raw OOK bits. Such boards typically require a microcontroller that makes sense of these bits. Your software then has the freedom to implement whatever encoding scheme you want: you can then send arbitrary EV1527 codes to control as many remote devices as you want, clone codes, or encode completely different data in your very own format, such as sensor readings.
  • EV1527-ready: EV1527-ready senders come with a dedicated EV1527 encoder chip and send out one or more EV1527-compliant codes. Such devices do not need any external components and no microcontroller or programming. EV1527-ready receivers typically implement some form of learning mode: when enabled, they pick up the control code emitted from a sender and store it. The learning mode basically pairs the remote control and the remotely controlled device.


Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.

Here is how your comments are stored

Whenever you leave a comment, a new github issue is created on your behalf.

  • All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.

  • There is no third-party provider, no disrupting ads, and everything remains transparent inside github.

Github Users Yes, Spammers No

To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant utteranc.es the permission to submit issues on your behalf.

If you don’t have a github account yet, go get yourself one - it’s free and simple.

If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.


For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.

  Show on Github    Submit Issue

(content created Apr 15, 2024)