Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : Gorilla and King Portfolio Candidates -- Ignore unavailable to you. Want to Upgrade?

To: 100cfm who wrote (18647)	2/24/2000 5:37:00 PM
From: konabound	Respond to of 54805

The BACnet and Lonworks would not be on the same system simultaneously, but would rather be two different options for a system. Many manufacturers have had their own proprietary protocols for years and have had to adapt to the newer protocols, sometimes by redeveloping their own system, sometimes through the use of gateways that will translate from one protocol to another. As an example, Carrier uses their own proprietary protocol but have two different internally developed gateway cards. One allows them to provide BACnet output, another provides Modbus output. I believe that they are now also coming out with a gateway to provide Lonworks output. Trane has for years used their proprietary control protocol between chillers and controllers but has used BACnet as the protocol from their controllers to the rest of the world. The Lonworks protocol they are coming out with is for unit level communication, such as from chiller to controller, not for system level communication. Thus, as has been found by other Building Automation firms, BACnet is best for system level interoperability and Lonworks is best for unit level interoperability. An ID node is the address for the specific Lonworks device, just like an IP address in Ethernet. Also, I forgot to mention in my previous post, BACnet is also an ANSI standard!