thanks LoneStar. I've had a little more time to look over the HomePlug initiative and it seems clear to me that this has to do with data networks and a way of accessing them (as opposed to wireless, cable modem etc) in contrast to control networks which is Elons domain. I re-read my previous post and in the rush to get my post out I was not entirely clear in this respect.
From what I understand there will be a number of networks converging in the home: the 'Computer' network (PC's, printers, scanners, fax etc), the 'Entertainment' network (TV, VCR, Stereo, DVD etc) and the 'Control' network (electric meters, light switches, electrical outlets, motion sensors, thermostats, security alarms, refrigerators, washing machines, etc). Computer and Entertainment networks are Data networks and are complementary to and can be managed by ELON's technology. There are many stds in Data networking of which HomePlug appears to be the latest variation. (Upnp, HomeRF, HomePNA, Havi, etc) and Elon is clearly taking an active role in ensuring that all these data network interface stds remain compatible with LonWorks.
I am still comfortable with my initial assessment that "this has Elon written all over it", but understand how this could easily be misinterpreted. Let me try and clarify this a bit.
Comprehensive, all encompassing home networking will require the co-operation of many players, no single company can make it happen by themselves. What is required a) smart devices (Upnp, HomeRF, HomePNA, Havi, HomePlug etc)... b) a gateway to connect the home network to the net (Open Systems Gateway Initiative - OSGi)...and c) a platform and architecture to support services (LonWorks Technology). The key to true home networking lies in the seamless integration between the Computer, the Entertainment and the Control network and this can only be achieved if there is a Universal Software Platform /Architecture. Enter the LonWorks family of products which is capable of not only executing on the 'control' network, but can also manage the other networks in the system. In this sense LonWorks is the infrastructure std that sits atop the the other (data) network infrastructures.
Echelons greatest asset at this point seems to be the acceptance of LonWorks as the de facto std for open interoperable control networks, and the HomePlug info states clearly that their chosen (data network) std will have to be compatible with LonWorks. This new stds committee will serve to strengthen the home network market which can only be good for Echelon.
This is how I understand it, but as I've said before I am not a techie....please correct me / comment if you see things differently. |
