|
|
Click any link below for a summary of gateways that use this protocol as the primary network:
|
|
|
|
About choosing a gateway:
Simply listing two protocols does not fully define a gateway. For example, putting a Modbus device on a BACnet network is one process. Putting a BACnet device on a Modbus network is quite a different process. In one instance, you want Modbus to be a master, and in the other instance you need it to be a slave. The same role reversal requirement applies on the BACnet side.
Virtually none of our gateways are a simple protocol translator, simply because there is no totally transparent, direct translation between Modbus registers and BACnet objects (for example). This becomes even more true with LonWorks and its 200 different variable types. Our gateways consist of a pairing up of clients and servers.
|
|
|
|
|
Not sure which gateway to use?
Follow the product tree by answering two simple questions...
(1) what protocol is on the network?
(2) what protocol is in the device?
Follow the product tree below, and if you can't get there, we don't make that version of a gateway. |
  |
|
|
|
|
Notes:
1) All gateways require configuration. We make the configuration process as easy as possible, but you cannot simply skip this step. If you do not ask for data, you will not get any. We suggest doing this before field installation.
2) Echelon LonMaker is required where indicated. The notation usually includes "or equivalent". If you have a tool capable of binding network variables, you already know that. If you do not have such a tool, you need to contact Echelon Corporation. Control Solutions does not sell LonMaker or any "equivalent".
|
|
|
