The LonWorks community will tell you "stay away from gateways". We happen to agree. That's why our gateways are really object servers.

What's the difference between a Gateway and an Object Server?

A traditional gateway will perform literal packet by packet translation from one protocol to another. This can degrade performance of the primary network. In the case of LonWorks, it also leads to behavior that is inconsistent with LonMark functional profiles and standard LonWorks network behavior.

An object server, as implemented in Control Solutions' Babel Buster series of devices, will create true objects having all of the characteristics of a native device. Our LonMark Certified "gateways" implement sensor and actuator profiles having all of the typical LonMark characteristics.

Does Babel Buster adversely affect my LonWorks network traffic?

No. These devices behave exactly the same as any other sensor or actuator on the LonWorks network. You bind their network variables, set the "send on delta", minimum and maximum send times, etc. You are in full control of the traffic just as you are with any other properly designed LonWorks device.

Can Modbus response slow down my LonWorks network?

No. Modbus and LonWorks communications are independent autonomous processes inside the Babel Buster. The LonWorks network variables respond just as they are meant to in a properly designed LonWorks device.

Is end to end response time an issue?

That depends on your application. We recommend avoiding any network for applications such as motion control. Building automation is typically less critical. Most LonWorks devices default to minimum send times on the order of seconds. End to end response by a Modbus device would not be noticed in this case. When operating as a slave, Modbus response will be immediate. When operating as a master, Modbus poll rate is programmable as a configuration property accessible from LonMaker.