• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[solved] No signal with raw data
#1
I installed pilight on arduino using Windows (I first tried Mac OS X but failed in my first try, see https://forum.pilight.org/Thread-Mac-OS-...8#pid19648). I am using a "433Mhz Superheterodyne Wireless Receiver RXB8 3.3V-5.5V Steady for Arduino/AVR" that gave me raw data when I installed it on a raspberry pi. So the hardware seems to be working. But because I had too much noise there (see https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=164177&start=25) I switched to arduino as a low pass filter, sort of.


The problem is: I do not receive any signal. I installed pilight on two different Windows computers (one laptop with 32 bit Windows 7, another 64 bit Windows 7) and do not even see a raw signal even when pressing the garage opener that opens and closed the garage all day long, see attached screenshot. Does anyone has an idea where I can look further?


.png   screenshot.png (Size: 44.47 KB / Downloads: 16)
 
Reply
#2
Did you try pilight-raw?
 
Reply
#3
(11-30-2016, 09:48 PM)curlymo Wrote: Did you try pilight-raw?
Yes, I did (no signal). I installed a low-pass filter in order to solve my problem. I used ATTiny85 and flashed the firmware using the following code
Code:
sudo pilight-flash -f /etc/pilight/pilight_firmware_t45_v3.hex
[Dec 04 20:42:58:823517] pilight-flash: INFO: **** START UPD. FW ****
[Dec 04 20:42:58:824023] pilight-flash: INFO: Indentifying microprocessor
[Dec 04 20:42:58:836277] pilight-flash: DEBUG: running on a raspberrypi
[Dec 04 20:42:58:997381] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:58:998555] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Dec 04 20:42:58:999515] pilight-flash: INFO: Not an ATMega328P
[Dec 04 20:42:59:177867] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:59:179816] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Dec 04 20:42:59:181575] pilight-flash: INFO: Not an ATTiny45
[Dec 04 20:42:59:351385] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:59:352516] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Dec 04 20:42:59:353424] pilight-flash: INFO: Not an ATTiny85
[Dec 04 20:42:59:523239] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:59:525445] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Dec 04 20:42:59:527206] pilight-flash: INFO: Firmware running on an ATTiny85
[Dec 04 20:42:59:711427] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:59:713584] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Dec 04 20:42:59:714302] pilight-flash: INFO: AVR lfuse reads as E1
[Dec 04 20:42:59:714927] pilight-flash: INFO: AVR hfuse reads as E1
[Dec 04 20:42:59:715089] pilight-flash: INFO: AVR FLASH memory has been specified, an erase cycle will be performed
[Dec 04 20:42:59:715403] pilight-flash: INFO: AVR chip being erased
[Dec 04 20:42:59:876332] pilight-flash: INFO: reading input file "0xe1"
[Dec 04 20:42:59:876754] pilight-flash: INFO: writing lfuse (1 bytes)
Writing | ################################################## | 100% 0.00s
[Dec 04 20:42:59:877259] pilight-flash: INFO: 1 bytes of lfuse written
[Dec 04 20:42:59:890601] pilight-flash: INFO: verifying lfuse memory against 0xe1:
[Dec 04 20:42:59:891167] pilight-flash: INFO: load data lfuse data from input file 0xe1:
[Dec 04 20:42:59:891419] pilight-flash: INFO: input file 0xe1 contains 1 bytes
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:59:892118] pilight-flash: INFO: verifying ...
[Dec 04 20:42:59:892245] pilight-flash: INFO: 1 bytes of lfuse verified
[Dec 04 20:42:59:893195] pilight-flash: INFO: reading input file "0xe1"
[Dec 04 20:42:59:893354] pilight-flash: INFO: writing lfuse (1 bytes)
Writing | ################################################## | 100% 0.00s
[Dec 04 20:42:59:894228] pilight-flash: INFO: 1 bytes of lfuse written
[Dec 04 20:42:59:909357] pilight-flash: INFO: verifying lfuse memory against 0xe1:
[Dec 04 20:42:59:909887] pilight-flash: INFO: load data lfuse data from input file 0xe1:
[Dec 04 20:42:59:910166] pilight-flash: INFO: input file 0xe1 contains 1 bytes
Reading | ################################################## | 100% 0.00s
[Dec 04 20:42:59:910925] pilight-flash: INFO: verifying ...
[Dec 04 20:42:59:911054] pilight-flash: INFO: 1 bytes of lfuse verified
[Dec 04 20:42:59:912045] pilight-flash: INFO: reading input file "/etc/pilight/pilight_firmware_t45_v3.hex"
[Dec 04 20:42:59:912562] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex auto detected as Intel Hex
[Dec 04 20:42:59:913239] pilight-flash: INFO: writing flash (1146 bytes)
Writing | ################################################## | 100% 0.31s
[Dec 04 20:43:00:220391] pilight-flash: INFO: 1146 bytes of flash written
[Dec 04 20:43:00:236053] pilight-flash: INFO: verifying flash memory against /etc/pilight/pilight_firmware_t45_v3.hex:
[Dec 04 20:43:00:236567] pilight-flash: INFO: load data flash data from input file /etc/pilight/pilight_firmware_t45_v3.hex:
[Dec 04 20:43:00:237094] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex auto detected as Intel Hex
[Dec 04 20:43:00:237818] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex contains 1146 bytes
Reading | ################################################## | 100% 0.22s
[Dec 04 20:43:00:458744] pilight-flash: INFO: verifying ...
[Dec 04 20:43:00:459680] pilight-flash: INFO: 1146 bytes of flash verified
[Dec 04 20:43:00:461661] pilight-flash: INFO: AVR lfuse reads as E1
[Dec 04 20:43:00:462851] pilight-flash: INFO: AVR hfuse reads as E1
[Dec 04 20:43:00:462910] pilight-flash: INFO: AVR fuses OK
[Dec 04 20:43:00:464831] pilight-flash: INFO: Finished updating firmware
[Dec 04 20:43:00:464874] pilight-flash: INFO: **** DONE UPD. FW ****
It seems that everything went ok, I double-checked the wiring. Using:
Code:
sudo service pilight restart
pi@Zimmer:~ $ pilight-receive
^Cpi@Zimmer:~ $ (after 1 minute)
does not give me anything. But pilight-raw now gives a signal:
Code:
pi@Zimmer:~ $ sudo pilight-raw
433gpio: 1404650915
433gpio: 94
433gpio: 172
433gpio: 227
433gpio: 137
433gpio: 106

BTW I thought that the ATTiny can reduce noise. But I do see too much noise. This is a recording of a few seconds of pilight-raw - still too much to see although nothing really happens (I did not push any button; x-axis is time and y-axis is signal I got):

.png   Bildschirmfoto 2016-12-04 um 21.57.54.png (Size: 410.88 KB / Downloads: 10)

UUPS.

I found something. I ran pilight-debug this time with the filter (without I never ever did get anything) and this time the output was:
Code:
pi@Zimmer:~/pilight $ sudo pilight-debug
Press and hold one of the buttons on your remote or wait until
another device such as a weather station has send new codes
The debugger will automatically reset itself after one second of
failed leads. It will keep running until you explicitly stop it.
This is done by pressing both the [CTRL] and C buttons on your keyboard.
--[RESULTS]--

time:        Sun Dec  4 22:39:56 2016
hardware:    433gpio
pulse:        6
rawlen:        131
pulselen:    5320

Raw code:
0 0 0 0 0 21280 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 31920 180880
This should mean that noise could be eliminated! Am I correct? And how can I interpret the signal? In any case: There is progress!
 
Reply
#4
Quote:BTW I thought that the ATTiny can reduce noise. But I do see too much noise. This is a recording of a few seconds of pilight-raw - still too much to see although nothing really happens ....
Purpose of the filter is the reduction of interrupts and CPU load.
433 MHz transmission is based on OOK (ON-OFF-Keying) of a 433 MHz RF carrier, the result is a square signal with sharp rising/falling edges.
You can not apply any kind filter to this kind of signals, you can only suppress rising/falling edges based on the knowledge that the minimum distance between rising/falling edges is appr. 100µS and simply ignore transitions with shorter durations.
Thus it is no suprise that you still have plenty of pulses.
 
Reply
#5
(12-04-2016, 11:04 PM)wo_rasp Wrote: Thus it is no suprise that you still have plenty of pulses.
Thank you, I did not know this (but should have since I know something about wave signals).

I found out something else and was expecting signals where no signal was found. But I had issues if two different daemons were running. Therefore, before applying pilight-deamon always
Code:
sudo service pilight stop
sudo service pigpiod stop
 
Reply
#6
Unfortunately, I have to ask again. My ultimate purpose is reading the signal from a Came garage opener but I am still struggling getting any signal at all. I have tried a ATTiny85 but now I am getting only noise, so my guess is that this chip is broken - and it will tae a few days until I get the new one. Therefore, I switched again to arduino. I had some problem flashing the arduino firmware using windows but in the end I used my raspberry and everything went fine. I also wired it according to the description in the wiki and connected it to a RXB2. I am using jessie on RPi3 with the newest apt-get update and upgrade, also the newest kernel (depmod 4.4.37-v7+).

My config.json reads
Code:
"hardware": {
                "433nano": {
            "comport": "/dev/ttyACM0"
        }    },
Still, I do not get any signal:
Code:
pi@Zimmer:/etc/pilight $ sudo pilight-raw -L
^Cpi@Zimmer:/etc/pilight $ sudo nano config.json
I changed the RXB2 - same result. Does anyone know what I can try? Sender and receiver are about 1cm apart.
 
Reply
#7
Issue is solved: see thread.

Lessons learned: If you start with an unknown device do not use pilight-debug or other functions, use pilight-raw and analyze by hand. Also, get the newest sender version possible, older senders might produce much more noise then newer ones.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [Solved] No ssdp connection found Hexcode 145 141,610 12-23-2017, 02:10 PM
Last Post: HuberDe
  [solved] Webgui 404-Error PT-Biker 2 853 11-11-2017, 09:49 AM
Last Post: PT-Biker
  [solved] Hardware not compatible ccc.ggg73 1 1,363 06-10-2017, 09:10 AM
Last Post: curlymo
  [Solved] pilight ssdp celle 6 7,840 02-23-2017, 03:22 PM
Last Post: gneandr
Question [SOLVED]pilight-daemon: ERROR: config is not in a valid json format herrmeier 4 7,026 11-28-2015, 11:28 PM
Last Post: herrmeier
  [Solved] pilight IR volle 2 2,858 11-03-2015, 10:24 PM
Last Post: volle
  Use pilight to send data between RPis Korrupt 3 2,364 06-01-2015, 10:40 PM
Last Post: curlymo
  pilight - emulating api?, custom daemon as a data input sirkubax 2 2,841 01-25-2015, 08:24 PM
Last Post: curlymo
  [solved]error while loading shared libraries: libpilight.so IcedEarth 27 17,290 12-30-2014, 09:21 PM
Last Post: BenPi
  SOLVED - Config file does not work after upgrade to 5.0 Jeroenk 6 4,466 10-12-2014, 08:49 PM
Last Post: Jeroenk

Forum Jump:


Browsing: 1 Guest(s)