Advertisement
Guest User

NEXA LYC Protocoll

a guest
Apr 25th, 2012
564
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.50 KB | None | 0 0
  1. Yeah, after reading and cewding something that dosen:t work. I read som kewd in the "Tellstick" project.
  2. After that, i came up with this facts:
  3.  
  4. The signal is computed as "Manchester", like:
  5. a "1", is actually represented by a "10", and
  6. a "0", is actually represented by a "01".
  7.  
  8. Whith that clear, we going to show the structure of the package sent(Without the manchester):
  9. b0 b1
  10. +----------+
  11. | Startbit | --- This is quite special, we digg in to this later. OBS: Read the timing for this
  12. +----------+
  13.  
  14. b1 b27
  15. +-----------+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+---------------+
  16. | Device ID | This is a 26bit long transmitter ID, uniq to all Transmitters | End Device ID |
  17. +-----------+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+---------------+
  18.  
  19. b27 b28
  20. +---------------------------+
  21. | Group action, Default "1" | --- Like, apply on all recivers in the group, to not do that, set it "1".
  22. +---------------------------+
  23.  
  24. b28 b29
  25. +----------------------------------------+
  26. | Method, On("10"), Off("01"), Dim("00") |
  27. +----------------------------------------+
  28.  
  29. b29 b31 b33
  30. +-------------------+-----------+
  31. | Channel/Group ID | Button ID |
  32. +-------------------+-----------+
  33.  
  34. b32 b35
  35. +---------------------------------------+
  36. | This is the 4bit (16levels) dim value |
  37. +---------------------------------------+
  38.  
  39. b36 b36
  40. +-----------------------------------------+
  41. | This is just an manchester "0", End bit |
  42. +-----------------------------------------+
  43.  
  44. After computing, this 33bit:s is computed to 66 manchester bit:s.
  45. After that, the signal is ready for the antenna.
  46. Here is the timings:
  47. NOTE this is the timings AFTER the manchester computing, so atually a unprocessed(before manchester)
  48. 1 or 0 is represented by two of the following timings:
  49.  
  50. '0' bit:
  51. _______
  52. | |
  53. | |
  54. | |_______
  55.  
  56. |<----->|<----->|
  57. 240µs 240µs
  58.  
  59. '1' bit:
  60. _______
  61. | |
  62. | |
  63. | |__________________________________________
  64.  
  65. |<----->|<---------------------------------------->|
  66. 240µs 1270µs
  67.  
  68.  
  69. NOTE
  70.  
  71. Startbit(b0-1):
  72.  
  73. This is the start bit, like a wakeup bit, just to show that "Hello, i am transmitting".
  74. The special about this, is that the timing is quite special:
  75. REMEMBER: 240µs up, 2550µs down
  76.  
  77. Device ID(b1-27):
  78.  
  79. This is a 26bit long ID that is diffrent to all remote:s. The reason why you have this, is the abillty
  80. to use several buttons on diffrent transmitters. Adding this later on
  81.  
  82. Group action(b27-28):
  83.  
  84. Default is just a "1". Not sure, but i thik that if you use a "0", the method is applyed on all the
  85. recivers programmed in the specified group.
  86.  
  87. Method(b28-29):
  88. NOTE: This is actually ONE bit, the specified numbers is in manchester.
  89. 01 - OFF
  90. 10 - ON
  91. 00 - DIM
  92.  
  93. 00: This may see werry strange, and this is the reason why a chose to represent this in manchester.
  94. This is two manchester zero:s.
  95.  
  96. Group ID(b29-31):
  97.  
  98. 00 = 1
  99. 01 = 2
  100. 10 = 3
  101. 11 = 4
  102.  
  103. Button ID(b31-33):
  104.  
  105. 00 = 1
  106. 01 = 2
  107. 10 = 3
  108. 11 = 4
  109.  
  110. Dim value(b32-35):
  111.  
  112. This is just an normal binary number, 1-16 on wich dim level to chose.
  113. NOTE: if you use a method like, ON, OFF, exclude this from the package
  114.  
  115. End bit(b36):
  116. This is just an manchester "0". End bit.
  117. NOTE: Not an ordinary "0", a manchester "0".
  118.  
  119. ----
  120.  
  121. In my code, this package is sent 4 time:s, whith 10ms delay.
  122.  
  123. Written by me, oskvadd, 120422.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement