## Integrating third-party data into a WebCTRL® system You can integrate third-party devices into a WebCTRL® system if the following are true: The third-party devices are physically connected on the WebCTRL® system’s network. You have an Automated Logic® controller that supports third-party integration. You have the correct Automated Logic® driver for the third-party protocol. You have enabled a port for a third-party protocol on the Automated Logic® controller’s driver page. To read from or write to a third-party device, you need the following information from the third-party vendor: Protocol Third-party device’s network address Memory location of the object in the device you want to read from or write to If you are integrating with BACnet devices, you can use the WebCTRL® BACnet Discovery feature to gather this information. See To discover BACnet networks, devices, and objects. Before you begin a third-party integration, study the Automated Logic® controller’s Technical Instructions and the third-party protocol’s Integration Guide. Both are available at http://accounts.automatedlogic.com/download. NOTES While BACnet third-party points are not restricted by hardware, we recommend that you do not exceed 2000 third-party integration points in a router's applications. You also should consider baud rate, number of nodes, number of network points, and trending frequency as these factors generally lower this recommendation. The point allowance of a controller that provides third-party points applies to only itself. For example, if you purchase an LGR1000 and download control programs that use 500 third-party Network I/O points, you cannot apply the unused 500 points to a different controller. Third-party points count towards the point limitation of a WebCTRL® system.
Click for details below To determine the number of non-BACnet third-party points used in a system To determine the number of third-party points used in a controller To discover BACnet networks, devices, and objects
### To determine the number of non-BACnet third-party points used in a system In SiteBuilder, right-click the system level on the Geographic tree, then select Run Global Point Count. TIP Select Run Local Point Count below the system level to count third-party points at and below the selected item. SiteBuilder displays the addresses that require licensing, but does not show the location of the point.
### To determine the number of third-party points used in a controller In the SiteBuilder application Right-click the controller on the Network tree, then select Run Point Count. In the WebCTRL® application On the Network tree, click to the left of the controller. Click on Driver, then scroll to the bottom of the page. Number of integration points requested and Number of integration points active show how many non-BACnet third-party Network I/O microblocks the controller is using. These two counts will differ if you exceed the product's integration point limits. For example, if your controller provides 25 points and its control program includes 27 Modbus points, your Integration points requested will be 27 and your Integration points active will be 25.
### To discover BACnet networks, devices, and objects The WebCTRL® BACnet Discovery feature locates all accessible BACnet networks, BACnet devices, and BACnet objects (including devices in your WebCTRL® system) on a BACnet network. The information gathered in this process is typically used to integrate third-party BACnet devices and their BACnet objects into the WebCTRL® system. To use BACnet Discovery: On the WebCTRL® System Configuration tree, select Connections. On the Configure tab, disconnect the BACnet/IP connection. While the connection is stopped, enter or verify the server's IP Address and Subnet Mask for the BACnet/IP connection. Restart the connection. On the Network tree, select the system level. Click Devices. On the Advanced tab, click Start to discover BACnet sites for the system. An item called Discovered Networks appears in the tree. To discover BACnet networks, select Discovered Networks, then click Go. A list of all BACnet networks appears on the Network tree. After all networks are found, close the status dialog box. TIP Run a commstat manual command to determine which device routes to each network. The BACnet Bind Show Network section of the Commstat window shows the IP address of the router to each network. To discover BACnet devices on a network, select a network on the Network tree, then click Go. After all devices are found, close the status dialog box. Click the plus sign beside an item to expand the list of devices. To discover BACnet objects on a device, select the device on the Network tree, then click Go. After all objects are found, close the status dialog box. A list of all BACnet objects in this device appears on the Network tree. TIP Make sure you are discovering objects in the correct device. It may take some time to discover objects in devices with more than 100 objects. Optional: Do the following to export the BACnet information so that it can be used in the Third-Party BACnet Utility or in the EIKON® application: On the Network tree, select a discovered network with devices or a single device. Click Export. Name and save the .discovery file in any folder. NOTES Some third-party BACnet devices may not be discovered because they do not support the BACnet methods required for auto discovery. If the discovery process returns ambiguous information, such as multiple points with similar names, contact the third-party manufacturer's representative for clarification. Device configuration or network load can prevent the WebCTRL® interface from showing all BACnet devices. If you do not see a BACnet device that you expect to see, check the system's BBMD configurations. If the configurations are correct, try the discovery process again.