Name | Modified | Size | Downloads / Week |
---|---|---|---|
MACS | 2014-12-21 | ||
PLSE | 2014-11-28 | ||
Power line chirp | 2014-11-23 | ||
pseudo code | 2014-11-14 | ||
README.txt | 2014-12-21 | 1.9 kB | |
Totals: 5 Items | 1.9 kB | 1 |
CEBus is an old protocol developed for power line, RF, IR, twisted pair and coax mediums. See http://en.wikipedia.org/wiki/CEBus This is a hobby project I use for testing/experimenting with my other project: protocoltool. The CEBus implementation is not complete and may never be. Disclaimer ========== Personal use only ----------------- I hereby certify that the content of this project in Sourceforge is my own (except where mentioned) and this is my own implementation of the CEBus protocol from specifications that I've got from the web. For documentation purpose, comments in the source code were extracted from the CEBus specifications. Commercial use discouraged -------------------------- CEBus is an outdated protocol and may not be compliant to regulations worldwide. In Europe, the powerline chirp conflits with CENELEC standards. There are some patents and IP attached to it. The CEBus protocol uses intellectual properties from Intellon (now sold to Atheros). CEBus attempted to implement a communication standards for many medias, but with time, other protocols took over before CEBus. I worked before for Domosys Corporation, which developped a chip using the CEBus protocol. This chip used a proprietary hardware PLSE with a crystal of 14.318MHz. The CEBus chirp in this chip has 358 samples instead of 360 (standard). After some litigation with Intellon, Domosys eventually ditched their CEBus product line and switched to their own PowerBus protocol. Finally, Domosys sold their IP to Analog Devices and ceased operations. There are other companies using the name Domosys but they're not related. Due to potential legal problems, it would be preferable to not use these files for a commercial application; if so, be sure to have proper legal advices before using these files. I would not be responsible for any copyright infringement or any lawsuit following any implementation using these files.