• 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

pilight 8.0 / wiringx / receive ATTINY-TX
I'm using pilight 8.0 on RPi3 with low-pass-filter. I'm sending a signal (INTERTECHNO protocol) genrated by an ATTINY85 / 433MHz-transmitter to the RPi. pilight does'nt detect / decode the signal apart from a few exceptions, while RCSwitch-RFSniffer / wirless sockets do not have any problems. When I do the same with an Arduino Nano all works pretty fine.
Are there minimum requirements for signal strength / waveform different from RCSwitch/wiringpi  based in wiringx?
Please do the following:
1. Start pilight-debug with and without filter, and if that doesn't work well enough, use pilight-raw.
2. Send codes with each program you said you tried and post the raw output with and without filter for each of them.
Here are the debugs. I'm sorry that I cannot add debugs without low-pass-filter since the receiver is soldered and unfortunatly I don't have a second one. But as far as I think, it will make no difference, because RFSniffer is getting the RX via the same low-pass-filter.
Some additional informations:
- TX-pulselength is 300 (RCSniffer is detecting ~ 300)
- RCSnffer is calculating pulselength by dividing the long part of the received syncword through the estimated pulselength. There are difficulties with the ATTINY in correct detection too, at half times another protocol is detecteed but curiously with  the correct result in system-code, unit-code, state. 
- I have tried to create a new pilight-protocol.in 433.92 and traced it. With ATTINY-TX there are only rare calls parse code. May be it stops processing earlier.

Attached Files
.txt   outDebugLPF_ATTINY.TXT (Size: 8.02 KB / Downloads: 8)
.txt   outDebugLPF_NANO.TXT (Size: 3.09 KB / Downloads: 0)
What receiver are you using?
(01-03-2018, 06:39 PM)curlymo Wrote: What receiver are you using?

It is a RXB6.
It is a little peculiarly: if I run pilight-daemon and RFSiffer at the same time therre are more detections by pilight compared to running pilight alone. And decoding within pilight is then more precise.
I suppose the interrupt detection within RPi makes the difference. Enlarge receive-tolerance may be a solution. I will try to figure it out this weekend.
solved     set  MIN_PULSE_LENGTH    200      \      MAX_PULSE_LENGTH    360

Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight nano usb over Wifi for routers without USB port frenchie71 15 14,682 01-04-2022, 01:02 PM
Last Post: MyCreditDom
  pilight DIY PCB Kits curlymo 63 74,753 10-22-2019, 02:09 AM
Last Post: pusky
  pilight, Raspberry Pi and sensors for sale kid2000 0 2,741 04-07-2017, 05:04 PM
Last Post: kid2000
  parts for pilight rikeshe 4 4,956 12-10-2016, 09:02 PM
Last Post: rikeshe
  No pilight-[debug/raw/learn] signals received bassabaws 8 10,851 04-14-2016, 11:35 PM
Last Post: wo_rasp
  Experiences with the pilight DIY PCB Kits troccolo 112 72,970 03-05-2016, 11:21 AM
Last Post: curlymo
  Use existing wall switch with correct status in pilight? kylex 0 2,427 01-13-2016, 01:27 AM
Last Post: kylex
  For Sale own-made pilight shield. Luppie 3 5,123 10-31-2015, 11:23 AM
Last Post: Luppie
  sk6812wwa the code for the attiny alanwangwang 0 2,208 08-18-2015, 03:02 AM
Last Post: alanwangwang
  control sockets with pilight (broken remote) mistera 16 18,791 05-15-2015, 07:16 PM
Last Post: Seebueb

Forum Jump:

Browsing: 1 Guest(s)