01-03-2018, 03:46 PM
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.
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.