4

My goal is to use a 433Mhz receiver to capture the KlikAanKlikUit (Kaku/CoCo) ID.

I have it wired to 5V and GPIO4. When reading up on the subject there are a few tools to capture data and even capture the KaKu ID directly. None of these seem to work, they just do nothing.

The receiver is named XD-RF-5V. Please see some pictures of the set-up at the end of the questions.

When I use the excellent piscope I can see that 'something' is happening, also when I press some buttons on the remote. See a video of it here: http://recordit.co/8kpG42adjl

I have used https://github.com/ninjablocks/433Utils 's RFSniffer with no results but I can also see that tool is hardcoded to use pin 2. I've changed my set-up to GPIO0/1/2 to try but also no results. To be honest i'm also completely confused by all the pin standards, some use wiringPI, some use BCM, some use real numbers...

When I use pilight, which installs fine, and use their pilight-raw command with these settings:

{
        "devices": {},
        "rules": {},
        "gui": {},
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/",
                "webserver-http-port": 5001,
                "webserver-cache": 1
        },
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 4
                }
        },
        "registry": {
                "pilight": {
                        "version": {
                                "current": "7.0"
                        }
                }
        }
}

Nothing happens, except for the first line. According to the docs it should just keep outputting data.

enter image description here

http://imgur.com/xGbz9hr enter image description here

  • 1
    Since you have got piscope installed you might as well try abyz.co.uk/rpi/pigpio/examples.html#pdif2__433D or abyz.co.uk/rpi/pigpio/examples.html#Python__433_py. The first one is more recent and I suggest you try that first. Does the piscope trace look like a Manchester encoded signal? Do you get much noise? – joan Jul 22 '16 at 7:51
  • 1
    @joan yeah I believe it's Manchester encoded, see the video I made. Not sure how to differentiate with noise or background signals. I'll have a look at those code samples. thanks – tomvo Jul 22 '16 at 8:20
  • 1
    I had a look at the video and it appears to be Manchester encoding but there does appear to be some noise. You'd expect pulses of two different lengths. Every now and then there is a short pulse which shouldn't be there. Both the linked software examples will filter out the noise which will make the likelihood of decoding the signal higher. – joan Jul 22 '16 at 8:32
  • 1
    pigpio only uses Broadcom GPIO numbering, see abyz.co.uk/rpi/pigpio/index.html#Type_3 – joan Jul 22 '16 at 8:33
  • 1
    @joan thanks a lot! I hope to find some time this weekend to try it out, i'll report back! – tomvo Jul 22 '16 at 8:57
1

I got the same sensor you are using STX882/SRX882.

To solve the problem:

  1. if you are using wiringPi you could call gpio mode tri (to disable internal resistance of RPI), than your sensor will start to work, otherwise it will be in SLEEP mode
  2. Connect it to 3.3V (not to 5V) GPIOs cannot support more than 3.3V (otherwise u will burn the GPIO Pin)

See the sensor Specification to see more info

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.