at2oo1
Posts: 28
Joined: Sun Jul 13, 2014 1:10 pm
Contact:

Send & Receive 433MHz Signals For Home Automation

Postby at2oo1 » Sat Jul 26, 2014 9:45 am

Hi,

i´ve decided to work on some home automation project with raspberry pi, i want to controll all kind of 433MHz Devices like power plugs.

I´ve got no expirience in working with 433MHz senders or receivers and RPi cabling so i decided to do a simple test setup before i start with the real project. I´ll document the test setup here and later the real automation project.

Test Setup
Simple 433MHz send and receive with the RPi

Hardware:
- RPi Rev. B
- 433MHz Modules FS1000A XY-FST XY-MK-5V
- GPIO Breakout Kit, Breadboard and cables

Wiring:

RPi GPIO PINS (Revision 2):
Image
GPIO and PIN descriptions here

Breadboard setup
Image
Please note that my breakout P0 is PIN 11 on Raspberry and P1 is PIN12

Connect sender Module FS1000A:
ADATA: Pin 11 which is BCM GPIO 17 and WiringPi Pin 0
VCC: +3,3V on my breakout (without Breakout use Pin 1 on RPi)
GND: GND on my breakout (without Breakout use Pin 6 on RPi)

Connect receiver Module XY-MK-5V:
DATA: Pin 12 which is BCM GPIO 18 and WiringPi Pin 1 (Dosnt matter which of the both data pins you use)
VCC: +3,3V on my breakout (without Breakout use Pin 1 on RPi)
GND: GND on my breakout (without Breakout use Pin 6 on RPi)


Software Setup & Test:

0. Logon your rpi with ssh or open terminal
1. First we need "wiringPi" from gordon (needed by the pilight),m run following commands to install

Code: Select all

sudo apt-get install git-core
git clone git://git.drogon.net/wiringPi
cd wiringPi
./build

2. Get "pilight" and dependencies, run following commands to install

Code: Select all

sudo apt-get install build-essential dialog cmake git
git clone --depth 5 -b master https://github.com/pilight/pilight.git
cd pilight
chmod +x setup.sh
sudo ./setup.sh

3. After running setup.sh a dialog appears, for my test setup i´ve installed all protocols by just hit enter on "save and install" (this takes a while)
4. After the installation is completed there is a configuration file that configures GPIOs which pilight uses. If you dont used my wiring on wiringPi PIN0 & PIN1 just update this file with your WiringPI PINs

Code: Select all

sudo nano /etc/pilight/hardware.json

5. Start the "pilight" deamon with

Code: Select all

sudo pilight-daemon

6. Start the 433Mhz Receiver programm with and let it run

Code: Select all

sudo pilight-receive

7. Open a second terminal or ssh session and send a 433MHz

Code: Select all

sudo pilight-send -p kaku_switch -i 123456 -u 0 -t

8. If you see following output on your receive window you successfully setup 433MHz sender / receiver

Code: Select all

pi@raspberrypi ~/pilight $ sudo pilight-receive
{
        "origin": "sender",
        "protocol": "arctech_switches",
        "code": {
                "id": 123456,
                "unit": 0,
                "state": "on"
        },
        "repeat": 1,
        "uuid": "0000-00-00-8f-2748a1"
}

Further Informations:
- pilight wiki and documentation
- wiringPi pin documentation
- The receiver normaly needs 5V to operate over a wide range, for the test setup i used 3,3V because we cant use 5V directly on the GPIOs

Next Steps:
- Control this 433MHz power plugs
- Create a tool that controls the plugs from my 19'' touch screen on my RPi (for details of the touchsee my other post)

Have Fun!
Meine Projekte auf http://raspberry.tips/
at2oo1
Posts: 28
Joined: Sun Jul 13, 2014 1:10 pm
Contact:

Re: Send & Receive 433MHz Signals For Home Automation

Postby at2oo1 » Sat Jul 26, 2014 9:55 am

placeholder part 2
Meine Projekte auf http://raspberry.tips/
HeroS_NL
Posts: 17
Joined: Mon Nov 04, 2013 10:07 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby HeroS_NL » Sat Aug 02, 2014 2:37 pm

Didn't you have to use a 5V to get it working? I'm trying to send and receive signals but with no success.. (Didn't follow your tutorial, was just using my own project)
Massi
Posts: 1567
Joined: Fri May 02, 2014 1:52 pm
Location: Italy

Re: Send & Receive 433MHz Signals For Home Automation

Postby Massi » Sun Aug 03, 2014 8:36 pm

HeroS_NL wrote:Didn't you have to use a 5V to get it working? I'm trying to send and receive signals but with no success.. (Didn't follow your tutorial, was just using my own project)


yes, you have to give 5V to the transmitter AND to the receiver.
Transmitter data pin can be moved by gpio at 3,3V
Receiver data pin (pins, ok) have to be lowered to be read by gpio (they exit at 5V), so take some resistance and make a partitor..
olihd
Posts: 3
Joined: Tue Aug 05, 2014 8:03 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby olihd » Tue Aug 05, 2014 8:33 pm

Did you had a look at busware.de (here -> http://shop.busware.de/product_info.php ... ucts_id/44 )? It's a usb device which can be controlled from the command line or any programming language - no need to build something special. Firmware is available here -> culfw.de . Very well documented and available as source free. The device can transmit and receive, but receive is a little bit tricky - still working on it :-( Easy to control intertechno or similar devices.
equathza
Posts: 1
Joined: Tue Aug 12, 2014 5:58 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby equathza » Tue Aug 12, 2014 6:27 pm

Thank you for the tutorial. I've successfully controlled several kaku switches and dimmers using a prototype setup. The receiver has only limited range because it operates at 3.3v. (still works though...)

Do you also plans on controlling them through a web interface?
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Fri Aug 15, 2014 12:50 am

Does the fact the receiver needs 5V to work properly means it's sending 5V to its data pin?
User avatar
joan
Posts: 12702
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: Send & Receive 433MHz Signals For Home Automation

Postby joan » Fri Aug 15, 2014 6:30 am

Bianco wrote:Does the fact the receiver needs 5V to work properly means it's sending 5V to its data pin?

That's the case for the modules I've seen. You should use a voltage divider to convert the data out pin from 5V to 3.3V.
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Fri Aug 15, 2014 10:07 am

The cheap chinese one?

I guess my multimeter would be useless to check it, I'd need an oscilloscope or a logic analyser?
User avatar
joan
Posts: 12702
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: Send & Receive 433MHz Signals For Home Automation

Postby joan » Fri Aug 15, 2014 10:51 am

Bianco wrote:The cheap chinese one?

I guess my multimeter would be useless to check it, I'd need an oscilloscope or a logic analyser?

Cheap tends to invoke the wrong connotations, I prefer inexpensive.

Yes, those sorts of modules.

At a pinch any pair of resistors with equal value would do as a voltage divider. The voltage would be around 2.5 but would still be seen as a high. Failing that a single large resistor in series might reduce the damage to a manageable level.
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Mon Sep 01, 2014 12:06 pm

joan wrote:
Bianco wrote:The cheap chinese one?

I guess my multimeter would be useless to check it, I'd need an oscilloscope or a logic analyser?

Cheap tends to invoke the wrong connotations, I prefer inexpensive.

Yes, those sorts of modules.

These really are cheap, especially the receiver. I just replace them for these: the range I gained is phenomenal!
User avatar
joan
Posts: 12702
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: Send & Receive 433MHz Signals For Home Automation

Postby joan » Mon Sep 01, 2014 12:16 pm

Thanks for the tip.

I'll look into buying some.
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Mon Sep 01, 2014 1:12 pm

A good rule of thumb seems to be:
  • The receiver has a resonator (regardless of its looks: round, rectangular, ...): it's going to have a decent range
  • The receiver doesn't have one: it's a piece of ***
Massi
Posts: 1567
Joined: Fri May 02, 2014 1:52 pm
Location: Italy

Re: Send & Receive 433MHz Signals For Home Automation

Postby Massi » Mon Sep 01, 2014 1:16 pm

Bianco wrote:A good rule of thumb seems to be:
  • The receiver has a resonator (regardless of its looks: round, rectangular, ...): it's going to have a decent range
  • The receiver doesn't have one: it's a piece of ***


so you gained range RECEIVING signals?
what's the range of the chinese receiver? and of your new one?
since i've no idea of how to code a program receiving signals :) i don't think i'm going to use it, but just for curiosity..
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Mon Sep 01, 2014 2:27 pm

Between the cheap emitter (Arduino) and the cheap receiver (R-Pi), I had around 8 meters of range (using RCSwitch or VirtualWire).
With the new one, I can't measure it without leaving my house. It has to be several dozens of meters.

Night and day, really.


Using a receiver on the Pi, you could have it automatically order a pizza when you press a button of your 433 MHz remote for instance :lol:
Massi
Posts: 1567
Joined: Fri May 02, 2014 1:52 pm
Location: Italy

Re: Send & Receive 433MHz Signals For Home Automation

Postby Massi » Mon Sep 01, 2014 2:35 pm

Bianco wrote:Between the cheap emitter (Arduino) and the cheap receiver (R-Pi), I had around 8 meters of range (using RCSwitch or VirtualWire).
With the new one, I can't measure it without leaving my house. It has to be several dozens of meters.

Night and day, really.


while i assume that emitter is quite the same range, isn't it?

Using a receiver on the Pi, you could have it automatically order a pizza when you press a button of your 433 MHz remote for instance :lol:


Sure, but it's hard for me to think to the software managing this..
Not the pizza ordering, the listening for EVERYTHING to sense the correct message..
How can this be something not cpu intensive? i think it should go on listening trying to sense a "known" wave form, but this means always listen and always try to match the signal with the known waveform..

More than this, the chinese cheap (an as you say, sh** :D) receiver senses A LOT of noise. I assume that the cheap, but better, receiver senses MUCH MORE noise, isn't it?
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Mon Sep 01, 2014 3:25 pm

pattagghiu wrote:
Bianco wrote:Between the cheap emitter (Arduino) and the cheap receiver (R-Pi), I had around 8 meters of range (using RCSwitch or VirtualWire).
With the new one, I can't measure it without leaving my house. It has to be several dozens of meters.

Night and day, really.

while i assume that emitter is quite the same range, isn't it?

My test weren't that thorough so I can't really say but I did test the "old" emitter with the new receiver and the range was better than with both old modules.

Using a receiver on the Pi, you could have it automatically order a pizza when you press a button of your 433 MHz remote for instance :lol:


Sure, but it's hard for me to think to the software managing this..
Not the pizza ordering, the listening for EVERYTHING to sense the correct message..
How can this be something not cpu intensive? i think it should go on listening trying to sense a "known" wave form, but this means always listen and always try to match the signal with the known waveform..

Using software decoding, that's gonna be CPU intensive. I guess you could decode with a microcontroller though but that's not a solution I've tried.

More than this, the chinese cheap (an as you say, sh** :D) receiver senses A LOT of noise. I assume that the cheap, but better, receiver senses MUCH MORE noise, isn't it?

It's quite possible the resonator enables it to filter a bit that noise?
I didn't check on piscope: the libraries are handling the noise for me.

Alternatively, you can also buy/build a low pass filter (again, not a solution I've tried).
Massi
Posts: 1567
Joined: Fri May 02, 2014 1:52 pm
Location: Italy

Re: Send & Receive 433MHz Signals For Home Automation

Postby Massi » Mon Sep 01, 2014 3:29 pm

Bianco wrote:Alternatively, you can also buy/build a low pass filter (again, not a solution I've tried).


mmm not sure about that.
From another topic where we were talking about receivers, it seems that the receiver has a sort of "gain" (lol, speaking as a true noob, take care of this) so that noise you sense when there are no "true" signals is not sensed between close signals (that's why when you send multiple signal between them the line in the oscilloscope is nice and plain..)
Bianco
Posts: 41
Joined: Sun Jul 13, 2014 9:41 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby Bianco » Mon Sep 01, 2014 5:01 pm

Not a low pass filter but a band pass filter, according to the experts at pilight.org:
https://github.com/pilight/pilight_firmware
User avatar
iinnovations
Posts: 621
Joined: Thu Jun 06, 2013 5:17 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby iinnovations » Tue Sep 02, 2014 4:41 am

This:

http://lowpowerlab.com/moteino/#antennas

These things are rad. Fully functional Uno/Nano clone + RFM, great library and support. $20-25. No-brainer.

C
CuPID Controls :: Open Source browser-based sensor and device control
interfaceinnovations.org/cupidcontrols.html
cupidcontrols.com
kdusilvestre
Posts: 1
Joined: Sat Feb 21, 2015 3:43 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby kdusilvestre » Sat Feb 21, 2015 3:47 pm

Hi olihd,

I'm also trying to read 433MHz signals using CUL v1.61 and CULFW + Pi, did you by any chance solved how to manage it? I'm struggling and I'm starting to think I'll have to write code to make it happen.

Thanks.
sneeu
Posts: 1
Joined: Sun Jul 19, 2015 11:15 am

Re: Send & Receive 433MHz Signals For Home Automation

Postby sneeu » Sun Jul 19, 2015 11:30 am

Steps 7 and 8 are not really reliabe to test whether the modules are working.
sending pilight-send -p kaku_switch -i 123456 -u 0 -t generate the same output to pilight-receive even if no(!) modules (neither receiver nor sender) are conneted to the pi at all
lexaberlin
Posts: 5
Joined: Sun Jun 07, 2015 8:37 am

Re: Send & Receive 433MHz Signals For Home Automation

Postby lexaberlin » Thu Aug 20, 2015 11:21 pm

Hello. I am trying this code and at one point when i do:

sudo ./setup.sh

i got this error:

CMake Error at CMakeLists.txt:245 (message):
Looking for libunwind - not found

-- Configuring incomplete, errors occurred!
make: *** No rule to make target 'install'. Stop.

Any idea? Thanks!
centos90
Posts: 25
Joined: Fri Jul 31, 2015 4:18 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby centos90 » Thu May 19, 2016 6:08 pm

sudo ./setup.sh

I get this error

-- Configuring incomplete, errors occurred!
See also "/home/pi/pilight/build/CMakeFiles/CMakeOutput.log".
make: *** No rule to make target 'install'. Stop.
pi@raspberrypi:~/pilight $


output.log

Code: Select all


pi@raspberrypi:~/pilight $ cat /home/pi/pilight/build/CMakeFiles/CMakeOutput.log
The system is: Linux - 4.4.9-v7+ - armv7l
Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
Compiler: /usr/bin/cc
Build flags:
Id flags:

The output was:
0


Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "a.out"

The C compiler identification is GNU, found in "/home/pi/pilight/build/CMakeFiles/3.0.2/CompilerIdC/a.out"

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded.
Compiler: /usr/bin/c++
Build flags:
Id flags:

The output was:
0


Compilation of the CXX compiler identification source "CMakeCXXCompilerId.cpp" produced "a.out"

The CXX compiler identification is GNU, found in "/home/pi/pilight/build/CMakeFiles/3.0.2/CompilerIdCXX/a.out"

Determining if the C compiler works passed with the following output:
Change Dir: /home/pi/pilight/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec1703416546/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec1703416546.dir/build.make CMakeFiles/cmTryCompileExec1703416546.dir/build
make[1]: Entering directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/pi/pilight/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building C object CMakeFiles/cmTryCompileExec1703416546.dir/testCCompiler.c.o
/usr/bin/cc    -o CMakeFiles/cmTryCompileExec1703416546.dir/testCCompiler.c.o   -c /home/pi/pilight/build/CMakeFiles/CMakeTmp/testCCompiler.c
Linking C executable cmTryCompileExec1703416546
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec1703416546.dir/link.txt --verbose=1
/usr/bin/cc       CMakeFiles/cmTryCompileExec1703416546.dir/testCCompiler.c.o  -o cmTryCompileExec1703416546 -rdynamic
make[1]: Leaving directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'


Detecting C compiler ABI info compiled with the following output:
Change Dir: /home/pi/pilight/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec4163429875/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec4163429875.dir/build.make CMakeFiles/cmTryCompileExec4163429875.dir/build
make[1]: Entering directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/pi/pilight/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building C object CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o
/usr/bin/cc    -o CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o   -c /usr/share/cmake-3.0/Modules/CMakeCCompilerABI.c
Linking C executable cmTryCompileExec4163429875
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec4163429875.dir/link.txt --verbose=1
/usr/bin/cc     -v CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o  -o cmTryCompileExec4163429875 -rdynamic
Using built-in specs.
COLLECT_GCC=/usr/bin/cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Raspbian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv6 --with-fpu=vfp --with-float=hard --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 4.9.2 (Raspbian 4.9.2-10)
COMPILER_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/
LIBRARY_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../:/lib/arm-linux-gnueabihf/:/lib/:/usr/lib/arm-linux-gnueabihf/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-o' 'cmTryCompileExec4163429875' '-rdynamic' '-march=armv6' '-mfloat-abi=hard' '-mfpu=vfp' '-mtls-dialect=gnu'
 /usr/lib/gcc/arm-linux-gnueabihf/4.9/collect2 -plugin /usr/lib/gcc/arm-linux-gnueabihf/4.9/liblto_plugin.so -plugin-opt=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper -plugin-opt=-fresolution=/tmp/cc4HWqQn.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --sysroot=/ --build-id --eh-frame-hdr -export-dynamic -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu -m armelf_linux_eabi -o cmTryCompileExec4163429875 /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crt1.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtbegin.o -L/usr/lib/gcc/arm-linux-gnueabihf/4.9 -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../.. -L/lib/arm-linux-gnueabihf -L/usr/lib/arm-linux-gnueabihf CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtend.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crtn.o
make[1]: Leaving directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'


Parsed C implicit link information from above output:
  link line regex: [^( *|.*[/\])(ld|([^/\]+-)?ld|collect2)[^/\]*( |$)]
  ignore line: [Change Dir: /home/pi/pilight/build/CMakeFiles/CMakeTmp]
  ignore line: []
  ignore line: [Run Build Command:"/usr/bin/make" "cmTryCompileExec4163429875/fast"]
  ignore line: [/usr/bin/make -f CMakeFiles/cmTryCompileExec4163429875.dir/build.make CMakeFiles/cmTryCompileExec4163429875.dir/build]
  ignore line: [make[1]: Entering directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp']
  ignore line: [/usr/bin/cmake -E cmake_progress_report /home/pi/pilight/build/CMakeFiles/CMakeTmp/CMakeFiles 1]
  ignore line: [Building C object CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o]
  ignore line: [/usr/bin/cc    -o CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o   -c /usr/share/cmake-3.0/Modules/CMakeCCompilerABI.c]
  ignore line: [Linking C executable cmTryCompileExec4163429875]
  ignore line: [/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec4163429875.dir/link.txt --verbose=1]
  ignore line: [/usr/bin/cc     -v CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o  -o cmTryCompileExec4163429875 -rdynamic  ]
  ignore line: [Using built-in specs.]
  ignore line: [COLLECT_GCC=/usr/bin/cc]
  ignore line: [COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper]
  ignore line: [Target: arm-linux-gnueabihf]
  ignore line: [Configured with: ../src/configure -v --with-pkgversion='Raspbian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv6 --with-fpu=vfp --with-float=hard --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf]
  ignore line: [Thread model: posix]
  ignore line: [gcc version 4.9.2 (Raspbian 4.9.2-10) ]
  ignore line: [COMPILER_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/]
  ignore line: [LIBRARY_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../:/lib/arm-linux-gnueabihf/:/lib/:/usr/lib/arm-linux-gnueabihf/:/usr/lib/]
  ignore line: [COLLECT_GCC_OPTIONS='-v' '-o' 'cmTryCompileExec4163429875' '-rdynamic' '-march=armv6' '-mfloat-abi=hard' '-mfpu=vfp' '-mtls-dialect=gnu']
  link line: [ /usr/lib/gcc/arm-linux-gnueabihf/4.9/collect2 -plugin /usr/lib/gcc/arm-linux-gnueabihf/4.9/liblto_plugin.so -plugin-opt=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper -plugin-opt=-fresolution=/tmp/cc4HWqQn.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --sysroot=/ --build-id --eh-frame-hdr -export-dynamic -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu -m armelf_linux_eabi -o cmTryCompileExec4163429875 /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crt1.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtbegin.o -L/usr/lib/gcc/arm-linux-gnueabihf/4.9 -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../.. -L/lib/arm-linux-gnueabihf -L/usr/lib/arm-linux-gnueabihf CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtend.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crtn.o]
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/collect2] ==> ignore
    arg [-plugin] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/liblto_plugin.so] ==> ignore
    arg [-plugin-opt=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper] ==> ignore
    arg [-plugin-opt=-fresolution=/tmp/cc4HWqQn.res] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc_s] ==> ignore
    arg [-plugin-opt=-pass-through=-lc] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc_s] ==> ignore
    arg [--sysroot=/] ==> ignore
    arg [--build-id] ==> ignore
    arg [--eh-frame-hdr] ==> ignore
    arg [-export-dynamic] ==> ignore
    arg [-dynamic-linker] ==> ignore
    arg [/lib/ld-linux-armhf.so.3] ==> ignore
    arg [-X] ==> ignore
    arg [--hash-style=gnu] ==> ignore
    arg [-m] ==> ignore
    arg [armelf_linux_eabi] ==> ignore
    arg [-o] ==> ignore
    arg [cmTryCompileExec4163429875] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crt1.o] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crti.o] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/crtbegin.o] ==> ignore
    arg [-L/usr/lib/gcc/arm-linux-gnueabihf/4.9] ==> dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9]
    arg [-L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf] ==> dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf]
    arg [-L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../..] ==> dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../..]
    arg [-L/lib/arm-linux-gnueabihf] ==> dir [/lib/arm-linux-gnueabihf]
    arg [-L/usr/lib/arm-linux-gnueabihf] ==> dir [/usr/lib/arm-linux-gnueabihf]
    arg [CMakeFiles/cmTryCompileExec4163429875.dir/CMakeCCompilerABI.c.o] ==> ignore
    arg [-lgcc] ==> lib [gcc]
    arg [--as-needed] ==> ignore
    arg [-lgcc_s] ==> lib [gcc_s]
    arg [--no-as-needed] ==> ignore
    arg [-lc] ==> lib [c]
    arg [-lgcc] ==> lib [gcc]
    arg [--as-needed] ==> ignore
    arg [-lgcc_s] ==> lib [gcc_s]
    arg [--no-as-needed] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/crtend.o] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crtn.o] ==> ignore
  remove lib [gcc]
  remove lib [gcc_s]
  remove lib [gcc]
  remove lib [gcc_s]
  collapse library dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9] ==> [/usr/lib/gcc/arm-linux-gnueabihf/4.9]
  collapse library dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf] ==> [/usr/lib/arm-linux-gnueabihf]
  collapse library dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../..] ==> [/usr/lib]
  collapse library dir [/lib/arm-linux-gnueabihf] ==> [/lib/arm-linux-gnueabihf]
  collapse library dir [/usr/lib/arm-linux-gnueabihf] ==> [/usr/lib/arm-linux-gnueabihf]
  implicit libs: [c]
  implicit dirs: [/usr/lib/gcc/arm-linux-gnueabihf/4.9;/usr/lib/arm-linux-gnueabihf;/usr/lib;/lib/arm-linux-gnueabihf]
  implicit fwks: []


Determining if the CXX compiler works passed with the following output:
Change Dir: /home/pi/pilight/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec2597813641/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec2597813641.dir/build.make CMakeFiles/cmTryCompileExec2597813641.dir/build
make[1]: Entering directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/pi/pilight/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building CXX object CMakeFiles/cmTryCompileExec2597813641.dir/testCXXCompiler.cxx.o
/usr/bin/c++     -o CMakeFiles/cmTryCompileExec2597813641.dir/testCXXCompiler.cxx.o -c /home/pi/pilight/build/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
Linking CXX executable cmTryCompileExec2597813641
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec2597813641.dir/link.txt --verbose=1
/usr/bin/c++        CMakeFiles/cmTryCompileExec2597813641.dir/testCXXCompiler.cxx.o  -o cmTryCompileExec2597813641 -rdynamic
make[1]: Leaving directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'


Detecting CXX compiler ABI info compiled with the following output:
Change Dir: /home/pi/pilight/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec3190290574/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec3190290574.dir/build.make CMakeFiles/cmTryCompileExec3190290574.dir/build
make[1]: Entering directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/pi/pilight/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building CXX object CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o
/usr/bin/c++     -o CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o -c /usr/share/cmake-3.0/Modules/CMakeCXXCompilerABI.cpp
Linking CXX executable cmTryCompileExec3190290574
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec3190290574.dir/link.txt --verbose=1
/usr/bin/c++      -v CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o  -o cmTryCompileExec3190290574 -rdynamic
Using built-in specs.
COLLECT_GCC=/usr/bin/c++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Raspbian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv6 --with-fpu=vfp --with-float=hard --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 4.9.2 (Raspbian 4.9.2-10)
COMPILER_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/
LIBRARY_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../:/lib/arm-linux-gnueabihf/:/lib/:/usr/lib/arm-linux-gnueabihf/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-o' 'cmTryCompileExec3190290574' '-rdynamic' '-shared-libgcc' '-march=armv6' '-mfloat-abi=hard' '-mfpu=vfp' '-mtls-dialect=gnu'
 /usr/lib/gcc/arm-linux-gnueabihf/4.9/collect2 -plugin /usr/lib/gcc/arm-linux-gnueabihf/4.9/liblto_plugin.so -plugin-opt=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper -plugin-opt=-fresolution=/tmp/cceJSvXk.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/ --build-id --eh-frame-hdr -export-dynamic -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu -m armelf_linux_eabi -o cmTryCompileExec3190290574 /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crt1.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtbegin.o -L/usr/lib/gcc/arm-linux-gnueabihf/4.9 -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../.. -L/lib/arm-linux-gnueabihf -L/usr/lib/arm-linux-gnueabihf CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtend.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crtn.o
make[1]: Leaving directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp'


Parsed CXX implicit link information from above output:
  link line regex: [^( *|.*[/\])(ld|([^/\]+-)?ld|collect2)[^/\]*( |$)]
  ignore line: [Change Dir: /home/pi/pilight/build/CMakeFiles/CMakeTmp]
  ignore line: []
  ignore line: [Run Build Command:"/usr/bin/make" "cmTryCompileExec3190290574/fast"]
  ignore line: [/usr/bin/make -f CMakeFiles/cmTryCompileExec3190290574.dir/build.make CMakeFiles/cmTryCompileExec3190290574.dir/build]
  ignore line: [make[1]: Entering directory '/home/pi/pilight/build/CMakeFiles/CMakeTmp']
  ignore line: [/usr/bin/cmake -E cmake_progress_report /home/pi/pilight/build/CMakeFiles/CMakeTmp/CMakeFiles 1]
  ignore line: [Building CXX object CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o]
  ignore line: [/usr/bin/c++     -o CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o -c /usr/share/cmake-3.0/Modules/CMakeCXXCompilerABI.cpp]
  ignore line: [Linking CXX executable cmTryCompileExec3190290574]
  ignore line: [/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec3190290574.dir/link.txt --verbose=1]
  ignore line: [/usr/bin/c++      -v CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o  -o cmTryCompileExec3190290574 -rdynamic  ]
  ignore line: [Using built-in specs.]
  ignore line: [COLLECT_GCC=/usr/bin/c++]
  ignore line: [COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper]
  ignore line: [Target: arm-linux-gnueabihf]
  ignore line: [Configured with: ../src/configure -v --with-pkgversion='Raspbian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv6 --with-fpu=vfp --with-float=hard --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf]
  ignore line: [Thread model: posix]
  ignore line: [gcc version 4.9.2 (Raspbian 4.9.2-10) ]
  ignore line: [COMPILER_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/]
  ignore line: [LIBRARY_PATH=/usr/lib/gcc/arm-linux-gnueabihf/4.9/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/:/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../:/lib/arm-linux-gnueabihf/:/lib/:/usr/lib/arm-linux-gnueabihf/:/usr/lib/]
  ignore line: [COLLECT_GCC_OPTIONS='-v' '-o' 'cmTryCompileExec3190290574' '-rdynamic' '-shared-libgcc' '-march=armv6' '-mfloat-abi=hard' '-mfpu=vfp' '-mtls-dialect=gnu']
  link line: [ /usr/lib/gcc/arm-linux-gnueabihf/4.9/collect2 -plugin /usr/lib/gcc/arm-linux-gnueabihf/4.9/liblto_plugin.so -plugin-opt=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper -plugin-opt=-fresolution=/tmp/cceJSvXk.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/ --build-id --eh-frame-hdr -export-dynamic -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu -m armelf_linux_eabi -o cmTryCompileExec3190290574 /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crt1.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtbegin.o -L/usr/lib/gcc/arm-linux-gnueabihf/4.9 -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../.. -L/lib/arm-linux-gnueabihf -L/usr/lib/arm-linux-gnueabihf CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/lib/gcc/arm-linux-gnueabihf/4.9/crtend.o /usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crtn.o]
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/collect2] ==> ignore
    arg [-plugin] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/liblto_plugin.so] ==> ignore
    arg [-plugin-opt=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper] ==> ignore
    arg [-plugin-opt=-fresolution=/tmp/cceJSvXk.res] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc_s] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc] ==> ignore
    arg [-plugin-opt=-pass-through=-lc] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc_s] ==> ignore
    arg [-plugin-opt=-pass-through=-lgcc] ==> ignore
    arg [--sysroot=/] ==> ignore
    arg [--build-id] ==> ignore
    arg [--eh-frame-hdr] ==> ignore
    arg [-export-dynamic] ==> ignore
    arg [-dynamic-linker] ==> ignore
    arg [/lib/ld-linux-armhf.so.3] ==> ignore
    arg [-X] ==> ignore
    arg [--hash-style=gnu] ==> ignore
    arg [-m] ==> ignore
    arg [armelf_linux_eabi] ==> ignore
    arg [-o] ==> ignore
    arg [cmTryCompileExec3190290574] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crt1.o] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crti.o] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/crtbegin.o] ==> ignore
    arg [-L/usr/lib/gcc/arm-linux-gnueabihf/4.9] ==> dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9]
    arg [-L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf] ==> dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf]
    arg [-L/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../..] ==> dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../..]
    arg [-L/lib/arm-linux-gnueabihf] ==> dir [/lib/arm-linux-gnueabihf]
    arg [-L/usr/lib/arm-linux-gnueabihf] ==> dir [/usr/lib/arm-linux-gnueabihf]
    arg [CMakeFiles/cmTryCompileExec3190290574.dir/CMakeCXXCompilerABI.cpp.o] ==> ignore
    arg [-lstdc++] ==> lib [stdc++]
    arg [-lm] ==> lib [m]
    arg [-lgcc_s] ==> lib [gcc_s]
    arg [-lgcc] ==> lib [gcc]
    arg [-lc] ==> lib [c]
    arg [-lgcc_s] ==> lib [gcc_s]
    arg [-lgcc] ==> lib [gcc]
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/crtend.o] ==> ignore
    arg [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf/crtn.o] ==> ignore
  remove lib [gcc_s]
  remove lib [gcc]
  remove lib [gcc_s]
  remove lib [gcc]
  collapse library dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9] ==> [/usr/lib/gcc/arm-linux-gnueabihf/4.9]
  collapse library dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../arm-linux-gnueabihf] ==> [/usr/lib/arm-linux-gnueabihf]
  collapse library dir [/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../..] ==> [/usr/lib]
  collapse library dir [/lib/arm-linux-gnueabihf] ==> [/lib/arm-linux-gnueabihf]
  collapse library dir [/usr/lib/arm-linux-gnueabihf] ==> [/usr/lib/arm-linux-gnueabihf]
  implicit libs: [stdc++;m;c]
  implicit dirs: [/usr/lib/gcc/arm-linux-gnueabihf/4.9;/usr/lib/arm-linux-gnueabihf;/usr/lib;/lib/arm-linux-gnueabihf]
  implicit fwks: []
danicymru54
Posts: 4
Joined: Fri Jan 20, 2017 12:57 pm

Re: Send & Receive 433MHz Signals For Home Automation

Postby danicymru54 » Fri Jan 20, 2017 1:10 pm

I have done some work in this area if anyone is having problems with getting receive codes back from the 433Mhz rf receiver. see https://danicymru.wordpress.com/2016/12 ... -doorbell/