[curlymo]

The second. Please open a new thread about those unknown devices with all information requested.

[Rschnauzer]

Thanks
I reported and documented two devices in earlier posts:
http://forum.pilight.org/Thread-mumbi-AB440R
http://forum.pilight.org/Thread-SLG-RS200TR
and got the advice to install the filter to suppress the noise.
I bought the filter parts from you and installed it.
After some problems with the cabling (different numbering schemes in documentations) I at least installed and initialised the filter.
Now I receive nothing and don't know whether I have still a cabling problem with the receiver or the sender.

How may I check if the receiver and the sender works correct?

Best regards:
Herwig

[curlymo]

We can only tell with data from pilight-debug without filter.

[webdandy]

Hi Herwig,

Hallo,

it seems that I now have the correct cabling.

Code:

pi@raspberrypi ~ $ sudo pilight-flash -f /etc/pilight/pilight_firmware_t45_v3.hex
[Oct 17 15:53:09:467651] pilight-flash: INFO: **** START UPD. FW ****
[Oct 17 15:53:09:468904] pilight-flash: INFO: Indentifying microprocessor
[Oct 17 15:53:09:482633] pilight-flash: INFO: Checking for an ATMega328P @115200
[Oct 17 15:53:09:485749] pilight-flash: DEBUG: running on a raspberrypi
[Oct 17 15:53:09:647988] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:09:659778] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:09:661887] pilight-flash: INFO: Not an ATMega328P
[Oct 17 15:53:09:675142] pilight-flash: INFO: Checking for an ATMega328P @57600
[Oct 17 15:53:09:836894] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:09:848483] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:09:850788] pilight-flash: INFO: Not an ATMega328P
[Oct 17 15:53:09:872145] pilight-flash: INFO: Checking for an ATTiny25 @57600
[ Oct 17 15:53:10:42811] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[ Oct 17 15:53:10:54603] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[ Oct 17 15:53:10:56724] pilight-flash: INFO: Not an ATTiny45
[ Oct 17 15:53:10:78208] pilight-flash: INFO: Checking for an ATTiny45 @57600
[Oct 17 15:53:10:244689] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:256282] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:10:260999] pilight-flash: INFO: Not an ATTiny85
[Oct 17 15:53:10:272355] pilight-flash: INFO: Checking for an ATTiny85 @57600
[Oct 17 15:53:10:444653] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:456273] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:10:463938] pilight-flash: INFO: Firmware running on an ATTiny85
[Oct 17 15:53:10:694176] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:695540] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:10:696533] pilight-flash: INFO: AVR lfuse reads as E1
[Oct 17 15:53:10:697498] pilight-flash: INFO: AVR hfuse reads as E1
[Oct 17 15:53:10:697574] pilight-flash: INFO: AVR FLASH memory has been specified, an erase cycle will be performed
[Oct 17 15:53:10:697650] pilight-flash: INFO: AVR chip being erased
[Oct 17 15:53:10:859699] pilight-flash: INFO: reading input file "0xe1"
[Oct 17 15:53:10:859977] pilight-flash: INFO: writing lfuse (1 bytes)
Writing | ################################################## | 100% 0.00s
[Oct 17 15:53:10:860564] pilight-flash: INFO: 1 bytes of lfuse written
[Oct 17 15:53:10:909113] pilight-flash: INFO: verifying lfuse memory against 0xe1:
[Oct 17 15:53:10:909385] pilight-flash: INFO: load data lfuse data from input file 0xe1:
[Oct 17 15:53:10:909568] pilight-flash: INFO: input file 0xe1 contains 1 bytes
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:910359] pilight-flash: INFO: verifying ...
[Oct 17 15:53:10:910510] pilight-flash: INFO: 1 bytes of lfuse verified
[Oct 17 15:53:10:912610] pilight-flash: INFO: reading input file "0xe1"
[Oct 17 15:53:10:912865] pilight-flash: INFO: writing lfuse (1 bytes)
Writing | ################################################## | 100% 0.00s
[Oct 17 15:53:10:923747] pilight-flash: INFO: 1 bytes of lfuse written
[Oct 17 15:53:10:960820] pilight-flash: INFO: verifying lfuse memory against 0xe1:
[Oct 17 15:53:10:961095] pilight-flash: INFO: load data lfuse data from input file 0xe1:
[Oct 17 15:53:10:961278] pilight-flash: INFO: input file 0xe1 contains 1 bytes
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:962075] pilight-flash: INFO: verifying ...
[Oct 17 15:53:10:962224] pilight-flash: INFO: 1 bytes of lfuse verified
[Oct 17 15:53:10:964567] pilight-flash: INFO: reading input file "/etc/pilight/pilight_firmware_t45_v3.hex"
[Oct 17 15:53:10:969016] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex auto detected as Intel Hex
[Oct 17 15:53:10:970895] pilight-flash: INFO: writing flash (1146 bytes)
Writing | ################################################## | 100% 0.80s
[Oct 17 15:53:11:772157] pilight-flash: INFO: 1146 bytes of flash written
[Oct 17 15:53:11:815442] pilight-flash: INFO: verifying flash memory against /etc/pilight/pilight_firmware_t45_v3.hex:
[Oct 17 15:53:11:818296] pilight-flash: INFO: load data flash data from input file /etc/pilight/pilight_firmware_t45_v3.hex:
[Oct 17 15:53:11:818979] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex auto detected as Intel Hex
[Oct 17 15:53:11:820727] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex contains 1146 bytes
Reading | ################################################## | 100% 0.69s
[Oct 17 15:53:12:515097] pilight-flash: INFO: verifying ...
[Oct 17 15:53:12:515344] pilight-flash: INFO: 1146 bytes of flash verified
[Oct 17 15:53:12:518345] pilight-flash: INFO: AVR lfuse reads as E1
[Oct 17 15:53:12:520299] pilight-flash: INFO: AVR hfuse reads as E1
[Oct 17 15:53:12:520872] pilight-flash: INFO: AVR fuses OK
[Oct 17 15:53:12:531723] pilight-flash: INFO: Finished updating firmware
[Oct 17 15:53:12:531999] pilight-flash: INFO: **** DONE UPD. FW ****
pi@raspberrypi ~ $

[/code]
But it seems to filter all my unknown Mumbi and SLG devices completely.
I get no entries with receive or debug.

For cross check I defined some sample devices for pilight webgui. If I switch those in the Android App this is reported with receive.
Does this proof, that my receiver and my sender works correct?
Or will receive report internally when a send request is processed?

Does someone has an idea how to debug my devices?

Best Regards:
Herwig

I have same problems with the cabeling.
Can you please tell me, which cabeling is working for you now?

I'm trying with the following and it is not working:

ATTiny:
Pin 1 = PIN 24
Pin 2 = Configured PIN for receiving (config.json="receiver": 3) = The receiver was working fine
Pin 3 = DATA PIN on receiver
Pin 4 = GND
Pin 5 = PIN 19
Pin 6 = PIN 21
Pin 7 = PIN 23
Pin 8 = 5V



Thanks
Fabian

[Rschnauzer]

I hope the image will help you