• 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
zeros in pilight-debug => noise?
#1
I have a garage door opener from Came and I am trying to understand its signal. I am using pilight on a RPi3 (Raspbian 4.4.37-v7+) and pilight v7.0. Receiver is superheterodyn with a lpf as wired in the wiki: ATTiny85, flashed with
Code:
sudo pilight-flash -f /etc/pilight/pilight_firmware_t85_v3.hex

Looking at pilight-raw -L gives me a flood of signals, even I do nothing. So this cannot be helpful for finding the signal. If I press the button I know that my receiver is picking up something because I "saw" a signal in Piscope. That is why I switched to pilight-debug. There, the outcome (only if I pressed the button) was, for example:
Code:
hardware:    433gpio
pulse:        9
rawlen:        39
pulselen:    280

Raw code:
280 840 280 840 280 840 280 0 0 280 280 0 280 560 280 840 280 840 280 280 280 280 0 560 280 0 840 280 280 280 0 0 280 840 280 0 28560 2520 9520
These numbers changed a lot, I did four of five tests - always with different results.

Now my question is: What about these zeros above? In another post it was mentioned that zeros seem to correspond to noise. Is the same happening here? Or can I simply assume that, for example, the signal
Code:
280 0 0 280
is the same as
Code:
280 280
and the signal, for example
Code:
280 0 280 560
corresponds to
Code:
280 840(=280+560)
For me, a 0 timeframe between HIGH-LOW or LOW-HIGH does not make sense unless it is eliminated as I just did.
 
Reply
#2
pilight-debug, pilight-receive, .... are applying certain assumption on the received data.

pilight-raw is the only module that does not apply any filter on incoming data and prints each pulse on a new line.

Using the parameter -L instructs pilight-raw to count the number of incoming pulses and add a linefeed not after each pulse but only after pulses with a duration > 5100 and to print the number of pulses before the LineFeed.
 
Reply
#3
(12-11-2016, 03:06 PM)wo_rasp Wrote: pilight-debug, pilight-receive, .... are applying certain assumption on the received data.
Thanks! What are the assumptions so that a zero shows up in pilight-debug?
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight bugs Ascenion 1 204 03-23-2020, 06:29 PM
Last Post: curlymo
  [Solved] pilight service crashing on first webserver access after reboot VrahoK 20 1,678 12-21-2019, 09:46 AM
Last Post: curlymo
  pilight-control modify values coolinx 16 1,465 11-13-2019, 08:02 PM
Last Post: curlymo
  Bug: double free or corruption in pilight-send blackzombie 12 1,330 10-07-2019, 08:15 PM
Last Post: blackzombie
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 520 08-13-2019, 05:43 PM
Last Post: curlymo
  pilight Nano USB interface curlymo 228 117,315 07-10-2019, 06:14 PM
Last Post: curlymo
  problems compiling pilight on Odroid C2 WitchDoctor 101 17,102 03-14-2019, 09:01 PM
Last Post: curlymo
  pilight 8 what chages for custom protocols? polo 11 4,424 02-15-2019, 06:22 PM
Last Post: polo
  pilight-debug shows nothing minhdomanh 3 986 10-18-2018, 07:01 AM
Last Post: felfert
  pilight-send and pilight-daemon DieterK 0 889 06-20-2018, 12:44 AM
Last Post: DieterK

Forum Jump:


Browsing: 1 Guest(s)