Introduction: RF 433 MHZ (Raspberry Pi)
Basic tutorial of how to setup a generic 433 MHZ transmitter/reciever with the Raspberry Pi.
Step 1: Parts
PARTS:
RPI 3 - https://amzn.to/2VA9pQY
4 Amp Power Adapter - https://amzn.to/2CTptWu
16GB micro SD - https://amzn.to/2SFMwd3
120 pcs jumper cable: https://ebay.to/2VAb9cY
433 MHZ TX/RX kit: https://amzn.to/2M9saGC
RF Outlet Set: https://amzn.to/2M91DJu
Step 2: Setup
rpi-rf: https://pypi.python.org/pypi/rpi-rf
SSH into Raspberry Pi
1. "sudo apt-get install python3-pip"
2. "sudo pip3 install rpi-rf"
Step 3: Code
*Note use python3
1. Run recieve.py and note code, pulselength, protocol
2. Run send.py with code, pulselength, and protocol arguments
Attachments
Step 4: Additional Info
Online Guide: https://www.piddlerintheroot.com/rf-433-mhz/
4 Comments
11 months ago
What receiver models work successfully? I bought the HiLetGo from
Amazon and I can’t get them to work successfully. All are bad in the
same way. They are very noisy on the RPi 5V line. I can use another 5 V
supply and they work pretty good if I don’t connect the data line. If I
connect the data line to the RPi there is a little noise but I should
be able to pick out the signal I am looking for.
But I don’t want to continuously have another 5V supply.
I soldered filter caps across +5 and GND on the receiver board.but that doesn’t help.
So,, what make (manufacturer) have worked for you folks?
Question 1 year ago on Step 3
I've gotten through steps 1 and 2. What do I do with the receive.py and send.py code - do I create files for each with those names? Where do I place the files? Could you modify your video to show how the script import is done? Thanks.
5 years ago
Hi Guys
I'm wondering if you could give me a hand with the following issue:
After running Receive, there is a strange flow of unexpected data, what could it be?:
2018-07-24 13:18:29 - [INFO] receive: 4 [pulselength 1032, protocol 2]
2018-07-24 13:18:29 - [INFO] receive: 513 [pulselength 1383, protocol 4]
2018-07-24 13:18:29 - [INFO] receive: 24 [pulselength 1331, protocol 4]
2018-07-24 13:18:29 - [INFO] receive: 6152 [pulselength 2024, protocol 4]
2018-07-24 13:18:29 - [INFO] receive: 128 [pulselength 1363, protocol 2]
2018-07-24 13:18:30 - [INFO] receive: 512 [pulselength 1234, protocol 2]
2018-07-24 13:18:30 - [INFO] receive: 128 [pulselength 1754, protocol 4]
2018-07-24 13:18:30 - [INFO] receive: 32 [pulselength 1216, protocol 4]
2018-07-24 13:18:30 - [INFO] receive: 8 [pulselength 854, protocol 4]
2018-07-24 13:18:30 - [INFO] receive: 64 [pulselength 1303, protocol 4]
2018-07-24 13:18:31 - [INFO] receive: 1184 [pulselength 875, protocol 4]
2018-07-24 13:18:31 - [INFO] receive: 128 [pulselength 1384, protocol 2]
2018-07-24 13:18:31 - [INFO] receive: 4104 [pulselength 1417, protocol 2]
2018-07-24 13:18:31 - [INFO] receive: 80 [pulselength 1172, protocol 4]
2018-07-24 13:18:32 - [INFO] receive: 8 [pulselength 1491, protocol 4]
2018-07-24 13:18:32 - [INFO] receive: 516 [pulselength 1416, protocol 4]
5 years ago on Step 4
I have a problem:
`$ python3 rpi-rf_send -g 17 -t 3 -p 101 15194300` so:
`2018-04-01 14:31:47 - [INFO] rpi-rf_send: 15194300 [protocol: 3, pulselength: 101]` is the code I'm sending, BUT, this is what I receive:
`2018-04-01 14:31:47 - [INFO] rpi-rf_receive: 15063220 [pulselength 521, protocol 5]`
Playing around with pulselength I realised that any `pulselength < 140` with basically make me receive close-to-random stuff. If I use `pulselength > 140` things are fine............but I need to send `pulselength == 101`......do you have any hints on what could be wrong here?