User Tools

Site Tools


rsl366

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rsl366 [2014/08/14 12:02]
ricardo
rsl366 [2015/11/27 21:09] (current)
Line 9: Line 9:
 Please give us feedback about this protocol so it can be added by default! Please give us feedback about this protocol so it can be added by default!
  
 +==== Development progress / known errors ====
 +20140815 (ricardo): works allright with pilight-send. Fit for //main// i.m.h.o.
 +==== Feature Support====
 ^Feature^Support^ ^Feature^Support^
 |Sending|{{http://​wiki.pilight.org/​lib/​images/​supported.gif}}| |Sending|{{http://​wiki.pilight.org/​lib/​images/​supported.gif}}|
Line 17: Line 20:
 ^Brand^Protocol^ ^Brand^Protocol^
 |Rising Sun RSL366|rsl366| |Rising Sun RSL366|rsl366|
-|PROmax (marketed in The Netherlands by //Praxis//)|rsl366|+|PROmax (marketed in The Netherlands by //Kwantum//)|rsl366|
  
 ==== Sender Arguments ==== ==== Sender Arguments ====
Line 152: Line 155:
 1000 0010 000 1 1000 0010 000 1
 </​code>​ </​code>​
-==== Development progress / known errors ==== +
-==Observations by ricardo== +
-20140814: it doesn'​t work here. I've checked the analysis of the pulse-train with the output from '​send.cpp'​ from '​rcswitch-pi',​ and it seems to be OK. When I try to catch the pulses from this protocol with pilight, I do not get sensible data. Maybe it is a timing problem. I could not find the source file ''​rsl366.c'',​ so I was not able to check it, or play around with it. +
  
  
rsl366.1408017747.txt.gz · Last modified: 2015/11/27 21:08 (external edit)