Creative Commons images are CC BY-NC-SA 3.0

4.95

added to your
shopping cart

quantity
In stock 1,065 in stock
4.95 1+ units
4.46 10+ units
3.96 100+ units

Description: These wireless receivers work with our 434MHz transmitters. They can easily fit into a breadboard and work well with microcontrollers to create a very simple wireless data link. Since these are only receivers, they will only work communicating data one-way, you would need two pairs (of different frequencies) to act as a transmitter/receiver pair.

Note: These modules are indiscriminate and will receive a fair amount of noise.  Both the transmitter and receiver work at common frequencies and don't have IDs. Therefore, a method of filtering this noise and pairing transmitter and receiver will be necessary. The example code below shows such an example for basic operation. Please refer to the example code and links below for ways to accomplish a robust wireless data link.

Features:

  • 434 MHz
  • 500ft range (given perfect conditions)
  • 4800bps data rate
  • 5V supply voltage

Documents:

Comments 65 comments

  • I have successfully used this with two Arduinos. I was stuck at first, so these points might be of help to others:

    1) Using the VirtualWire library linked above is a really good idea. Then you don’t have to worry about noise or how the signal is actually transmitted. Simply call a function to send an array of bytes on the transmitter (currently max 27), and call another function to wait for incoming bytes on the receiver. Copy-paste the example code for setup(). It’s super easy!

    2) The VirtualWire library has a function to set the TX and RX-pin. But do not use pin 10! Pin 10 is assigned as default for something else (PTT, push to talk? I don’t know, but probably don’t need to know either). You might make it work on pin 10 by assigning PTT to another pin, but I haven’t tested that. I just know that it does not work if you select pin 10 for the receiver.

    3) There are three GND-pins, and two VDD-pins. My device works fine if I only connect one of the GND-pins and one of the VDD-pins (either is fine).

    4) A comment below mentions the need to connect the linear output pin to ground via a resistor to improve signal quality. Perhaps this is true, but I was able to get communication working without the resistor, so don’t worry about it to begin with.

  • Can one receiver get data from multiple transmitters (WRL-10534) if some sort of an address byte is assigned to a transmitted piece of data?

  • Would I be able to use many of these to wireless transfer information between sensor nodes and a main processor? Would I be able to use the same frequency to communicate in the reverse direction, assuming that I created a “syntax” of communication?

  • So I want to create a magic sword, like sting, that lights up in the presence of certain things. could this be used in conjunction with the transmitter to trigger EL wire?

  • Can you have one transmitter and about ten receivers?

  • Are you not suppose to obey FCC rules with this device which mandates only short transmission times with this device? SEE: https://www.linxtechnologies.com/resources/documents/fcc_resource_document.pdf ALSO: https://www.linxtechnologies.com/resources/documents/an-00125.pdf If you want to achieve proper reception with this device you should use an encoding scheme such as Manchester encoding as well as send some throw away data first such as 0xAA s to sync up the receiver to the transmitter. SEE: https://www.linxtechnologies.com/resources/documents/an-00160.pdf

  • What’s the recommended decoupling cap value to use with these (or is that completely dependent upon the application)? Also, I’d like to use these with a 9N1 UART scheme - am I barking up the wrong tree, or will that work?

  • Is there a difference between the 315MHz and 434MHz versions of this? (Not in the physical product, but in the range, quality, etc.)

  • Is it safe to supply 4.5 volts, or 6 volts to this receiver?

  • I think this is the receiver with the worst performance I ever bought.

  • FWIW, I wrote a node library that interfaces with the RF link receiver and the accompanying WRL-10534 transmitter. It’s not much, but if it helps anyone, great! http://kenhirakawa.com/one-way-rf-communication-with-arduino-and-node/

  • What are the power requirements for this? I built a project with one of these a Pro Micro - 5V/16MHz and ONE LED. I am powering it with a bank of 4 AA batteries.

    The LED goes on when I am on the phone so the LED is on about 30 minutes a day.

    The batteries lasted one week. Is this normal?

    • I haven’t measured this part specifically, but you can get a good idea just from the numbers you gave.

      A week is 168 hours. AA batteries are in the 2500mAh range. Dividing gives us an average current draw of 14.8mA.

      I would expect the Pro Micro to be in the 10mA range, so the RX and LED raising it to 15mA sounds about right.

    • Hi, I also have a Pro Micro and a TX&RX433. I try to use the virtualwire librairie but I am unsuccessful. Did you used it ? Did you do some adaptation ? thanks

  • Does anyone know of a trick to grab a RSSI from this component? Thanks!

    • I’m unimpressed with the datasheet. Tinkering wiht this module, it appears that pin 1 is power ground, and pins 6 & 7 are RF ground. Something to keep in mind if you’re trying to build a clean circuit…

    • Actually, looking the datasheet over I’m wondering if the “Linear Output” would work if I brought it to a ADC pin. Has anyone tried this?

  • Is this receiver unidirectional or omnidirectional?

  • Is it legal to use this frequency in Canada?

  • Can you read signal strength with this? If so I would like to try using a pair to get a bearing on the transmitter.

  • Anybody know if this is compatible with the universal RF remote (i.e. garage doors etc)? I’m tempted to build a project if it is, as my new car has three universal remote channels I can program… and I don’t have a garage.

  • I discovered that these units work better without the antennae than with them, at least at a distance of 4 meters or so. I also discovered that I needed to tie the “Linear Output” pin to ground via a resistor, 200K or so, otherwise the reception was horrifically unstable.

  • Just got one of these to debug a wireless project I’m working on. I bought a set of wireless outlet switches on Amazon (has a remote and 5 boxes that plug into the wall, each with a relay to switch an outlet on or off). I took the remote apart and it had a 433MHz radio. I scoped the protocol and it uses an equal-spaced long/short encoding. I figured this 434MHz would be close enough and it is. The thing outputs random noise until I press the remote button, then I see the signal perfectly. I also bought the 434MHz transmitter which I will use to mimic the remote to control the outlets. A lot of commercial stuff uses the 433/434MHz band so that is another possible source of noise, but most are not steady connections, only momentary.

  • What part number is this in the Sparkfun Eagle library?

  • What is the maximum amount of current that this thing draws when it is under maximum load? I’m trying to figure out if I can run a circuit off of the supply voltage given from the FTDI breakout board.

  • Has anyone got this to work at 4000bps? My design works perfectly with a slightly older model, so I thought this part would be a drop in replacement (yes, I verified it is the same pinout and the same operating frequency). I measured the output with a logic analyzer, and found that all the falling edges seem to be lagging – almost as if an RC time constant is too high in the rectifier circuit… It is enough to cause bit errors and dropped packets. It is frustrating because these parts are supposed to work up to 4800bps.

  • You should have the “Arduino Library” point to Mike McCauley’s site so that you can download the latest version rather than pointing to the old VirtualWire 1.5 version (which doesn’t compile out-of-the-box on Arduino 1.0).

    At the time of this comment, the lib is up to 1.9 and compiles on Arduino 1.0 out-of-the-box.

    Another good link is this one for a wireless RF temperature sensor project using two Arduinos. He doesn’t use VirtualWire though it is informative.

  • guys pls check out the example code with ur arduino and pls tell me wen u pres the button on ur transmitter does the led on receiver light up constant or does it flicker or blink?? pls guys tell me this is the most imp the im gonna make with this!!

  • Is this capable of receiving signals from weather stations that use the 433 MHz band or is the modulation (or some other aspect) incompatible?

  • Hi, I built a break out board that holds 2 receivers, 315 and 433 MHz. I added an extremely simple support circuit, and voila! Perfect data, every time. There isnt a and RF remote in my house I cant read perfectly.

    Its a beatiful board, 4 basic extra components. If Sparkfun is willing to make the board (and share the Loot), Ill gladly share the circuit. However, I think i might be willing to do it if you put my name on the silk screen!

    I wish there was a way to post pictures…

  • Would anyone care to see the output of theese on an oscilloscope?

    i can send some binary data and do some graphing on both the Linear out, and the digital out pins.

    Sorry though no Spectrum Analyzer yet :/

  • http://mbed.org/users/4180_1/notebook/ir-and-rf-remote-controls/ has a code example for mbed sending characters from the matching transmitter to this receiver.

  • Could I send a one-bit (on/off) signal without encoding, virtualWire? Basically, without a uC. I just want an LED to turn on connected to the receiver when a button is pressed on the transmitter. Is this possible?

    • Testing here, it seems that the receiver outputs a high (lit LED) by default, goes low when the transmitter sends low, and then drifts back up to high after a second or two. No chips, only buttons/resistors/LED. I read somewhere that this receiver adjusts input gain until it gets something, which might explain the drifting high.

    • Use an HT12E (encoder) and HT12D (decoder) or similar ICs no need for uC.

  • Anyone has the Eagle library for this?

    Also, I see a lot of people having trouble with the transmission. I used these in a project and I’m planning to use them again in another, and that’s because of the HT12-E HT12-D pair of Enconder and Decoders (that also appear in these devices Datasheet).With the IC pair they worked perfectly, the only drawback is that if you are really worried about hardware, you’ll have to use a 18 pin IC.

  • I have been using these to build a remote robot. The transmitter and reciver are controlled with two Arduino UNOs. I have a test where it reads a message transmitted from the transmitter(WRL-10534
    ) and prints it on the screen. I have that part working somewhat perfectly. When a motor is attached(anywhere, even on 5V and gnd pins) the data gets completly messed up, no usable information. Does anyone know how I could fix this?

    • One of two things could be happening. Either A) when the motor kicks on, its generating a lot of noise on the DC supply to the RF module, which causes the module to do all kinds of freaky things. B) The RF module is too close to the motor and is picking up the electromagnetic field generated in the motor’s coils. Connect an oscilloscope to the power supply for the RF module, monitor the signal when the motor kicks on. If you see a huge spike or even noise, add a simple filter between 5V+ and RF V+. A filter could be a simple 1+ Ohm resistor feeding a 1000uf and a 0.1uf capacitor, with the RF module being powered by the caps. Increase the resistance of the resistor until the noise goes down enough to prevent the problem, while still feeding the caps with enough power to keep the module on. Then test the data pin. If the noise is only on the data pin, then you need to move the RF module further from the motor and possibly try to shield it from EMI. Also make sure you are decoupling everything, and if you have ferrite beads, use them on the motor’s wires.

  • I bought a couple of these, and both seem to have a constant stream of output coming from both. With no input to the transmitter (even with it not powered) I still get a steady stream of bit flips out of each one on the receivers. I’ve double checked the wiring to each (all Vcc and Gnd present) and still cannot find where the issue is. Has anyone else seen the same issue?…

    • These are extremely basic transmitters and receivers, and thus you cannot just put digital or serial data in one end and have it come out the other. The signal you put in (and get out) must be modulated; that is, it needs to change state (low to high, or high to low) at least every 30ms, or the receiver will not be able lock onto the signal. When there is no valid TX data, the RX will output noise, so the TX modulation must be constant, even when there’s no actual data being passed. (And ideally the modulation should be balanced (equal time high and low), see line code for more information, Manchester encoding is a popular choice.)
      See the links above for examples on how to work with these parts; they’re an inexpensive and effective solution if you’re willing to do the work that more expensive parts do for you.

      • Mike, thanks for the quick response!…and that’s super great information to have about how the transmitter receiver pair operates. Unfortunately, knowing that now complicates my project a bit, but not a brick wall. Now, is that info also somewhere in the documents linked above for the receiver that I was completely blind to?…well, I suppose if not, it’s here now. Thanks again!

        • All of the linked examples use modulation to some extent, but you’re right that this requirement is buried in radio theory to the point of obscurity (sorry about that!)
          One way to get these working is to constantly send a character across (0xAA is a good choice since in binary it is “10101010” and thus has lots of transitions), and ignore that character at the receiving end. Then you can slip in other characters that are your “real” data as you have it. (You could even check for the 0xAA and use it to prove that a link is actually established). Hope this helps, good luck!

    • I guess I have the approximately opposite problem from n0mad. I see no activity on my receiver’s data pin – ever. The transmitter and receiver are wired correctly and I am using only example code at this point. It appears that the transmitter (as far as I can tell) is spitting out data right beside the receiver. In desperation, I tried “tuning” the receiver but there was no change. Very frustrating. Does anyone have any ideas how I can debug this? Is there any way to find out if the transmitter is actually transmitting (when one does not see anything on the receiver)?

      • Double-check your power and data lines (right voltage, right pins), and if that doesn’t help, contact us at techsupport@sparkfun.com and we’ll be happy to help you out.

    • Yes I have the exact same issue as you sadly :(

  • It would be nice if Sparkfun had Datasheets for the product they actually ship. The one they sent me does not match the link above. It doesn’t even match the picture.

  • You get what you pay for holds true for this little gem. Thinking that an xbee would be overkill to transmit a 4 byte message, I decided to try this product. I purchased one of each flavor. Both 315 and 433 Mhz radios produce nothing more than a continous stream of noise that no amount of software, checksums and programming can reliably filter out. I am lucky to get 1 good 4 byte message out of 20 transmits.

    • I have this. At first it was unusable. After I figured out some tricks, I got it to work pretty well.

  • if its used in railway track fault identification applicable possibilities is there?

  • Think this will work with the TI Chronos?

    • No, the TI Chronos uses a different wireless protocol.

      • Protocol, Frequency and Modulation- 3 diferent things.

        If the Chronos is transmitting at 433 MHz, this reciever will pick it up.

        If the Chronos is FSK instead of ASK, it wont work.

        Understanding the data format (the protocol) is a different story.

        … just for clarity sake.

      • ah good thing the deal ran out. I tend to see more cons to buying a product when I can’t have it :P

  • Dunno if this is on purpose or not, but the example code is missing the closing */ on “TRANSMITTER CODE” and “RECEIVER CODE” which effectively comments the entire thing out so you don’t get any syntax highlighting/etc.

  • So glad this is back.


Related Products