LCC is an accessory bus that operates beside, and in conjunction with, your layout’s traction control. Similarly to DCC, it allows users to buy compatible products from multiple sources. It is a set of protocol standards and tecnical notes directed at manufacturers (an DIYers).
OpenLCB is the open group of people, the ideas, and the technology powering LCC. Since LCC is extensible, the OpenLCB group continue to discussion and develop new aspects and protocols which can/will be merged into future LCC editions. It is an open group, and if you are interested in imagining, influencing or developing the future, please join us.
Below is a summary of LCC design points. However, I wanted to respond to some of the previous posts. LCC is the common infrastructure on which manufacturers can develop innovative products. That infrastructure allows additional features such allowing mutlitple LCC bus segments, integration with legacy buses, and self-descripton and discovery of nodes. It is superficially similar to CMRI, Loconet and CBUS, but with much expanded capabilities. Because of these, it will require more computing resources to reach its full potential – however, since computing power per chip is increasing very rapidly without increased cost, we do not think this is an issue. For example, present 32-bit ARM processors have more speed, power, and memory than similarly priced to 8-bit processors, further consider the capabilities of the $5 Raspberry Pi. LCC is designed to use many transports, including Ethernet, Wifi, RF, and other local buses. CAN was chosen as a local transport since it is well-known and robust wi