(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):
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!