RF Data FormatThe RF data to control this device is arranged as follows: |
Preamble:
Bit Timing:
|
Circuit Diagram |
![]() |
Construction TipsYou don’t strictly need the exact regulator parts shown—substitute with any 5 V regulator:
|
![]() |
Use ~32 cm single‑core wire for the RF receiver aerial, wound into a spiral. Testing LEDs:
|
Operation Overview
LED indicator feedback:
|
First‑Build Photos |
![]() ![]() ![]() |
Future Enhancements
Current PIC16F88 is common but wastes many I/O pins. |
Why No Full RGB Control?Setting 64 levels per channel via IR takes 20–30 s per color—impractical. Use built‑in presets and recall via PC software. |
Reverse enginerring the RGB LED Striplight infra red transmission and encoding |
This is documentation written previously to the information above.. |
This information is based on these unigs below, but may also be compatable with others.
|
![]() |
First of all, this has already been covered here: If you have already read my other page covering X10, the protocol for this lighting is almost identical. See image that was taken directly from the infrared remote IR LED |
![]() |
Timings Confirm timings used The first 8 bits are the address, Bit 8 is sent first The final bit is a stop bit with the same timing as 0 The whole block of data is only sent once, although it looks like the remote then sends some sort of blanks which I suspect cause the button to repeat the command. After a lot of hours testing and failing, I worked out a couple of things: 1, the other website (linked above) has the address wrong. They suggest the address is always 0xFF (all 1’s) but in actual fact its 0x00 (all zeros). 2, the other issue which had me scratching my head was that the infra red transmission must be modulated on a 38 Khz carrier. After half building a 555 timer circuit to do this, I realised that the microcontroller could achieve this instead saving on additional parts. |
|