System Networking Best Practices

This is a collection of best practices for networking Kahler Automation systems, which consist of several components including computers, scales, controllers, PLCs and sensors that work together during system operation.

Physical connections

With few specific exceptions, all networks should consist of hard runs of shielded cable on a single network. Shielded CAT 5, CAT 5e, or better cables should be used. A reasonable metric is a minimum connection link speed of no less the 100Mbps, called “Fast Ethernet” or “100 Base T”. Gigabit or better is recommended.

Where very long runs (greater than 100 meters or 330 feet) are needed, a fiber optic network connection is preferred as these offer low latency, jitter, and packet loss.

Wireless connections are not recommended or supported in most situations, as they can be affected by weather, jitter, latency, interference, and packet loss, and tend to provide an experience that cannot be relied upon. Kahler Automation systems expect stable network conditions for intercommunication and are not as forgiving as other technologies can be.

Wireless connections may be allowed for the following: Terminal Management TMX webpage access, Staged Order Viewer, 1530 Graphics, and VNC. Wireless may also be used for Container Filling 2, but it is not recommended.

Network structure

All system component devices should be on a single network segment, not requiring routing between subnets. This may be referred to as L2 switching versus L3. Routing across subnets may introduce latency that the system can be sensitive to. Ping times can be used to gauge latency and should be as low as possible, with <1ms on average expected.

For those wishing to isolate equipment on a separate network, either with physical separation or VLANs, it is required to keep all infrastructure accessible in the same segment. Loadout machines, servers and other computers should be connected to both the isolated network and the primary as required.

Static IPs are required on most equipment used, and recommended on all. Where DHCP is desired, care should be taken to make it reliable, and to designate a range separate from the static IPs in use.

Kahler Automation systems should be considered OP (Operational Technology) rather than IT (Informational Technology)

Software separation

Kahler Automation recommends that a separate, dedicated server machine (not used in normal day-to-day operations) is used to host Terminal Management TMX, interface software, the database, and other similar software. This server machine should be on premises and in accordance with all other recommendations.

Sites where Kahler Automation’s cloud-based offerings – Constellation and LOADPASS – are used should also have a persistent internet connection to the server machine. Kahler Automation cloud-based offerings do not require port forwarding or special rules in most cases, as all connections used are initiated on the site-side for improved security. A persistent internet connection is not required for licensing purposes. Specific URLs and ports that may be required for cloud offerings and licensing are listed below. This list may not be exhaustive.

Still Need Help?

Submit an online web ticket or call us at Kahler Automation 507-235-6648 Option 2.