Thread Content
The company mainly uses ABB AC800F, as well as one Hilscher K series 6.52 unit, and some Siemens S7-200, S7-300, S7-400 units, and Zhejiang University Zhongkong ECS-100 units. These non-ABB data are to be exchanged with ABB and then uploaded to the main control room together. Seeking help on how to communicate ABB with other data sources. ABB with Profibus-DP
I think a communication scheme like yours might cause an excessive communication load on the AC800F. It is recommended to use the OPC interface of other systems to communicate with the scheduling system. If the 200/300/400 host computer is WINCC, its OPC interface is enabled by default. The ATP OPC software system of ECS-100 requires authorization to be enabled. The K series from Hollyland also requires authorization.
This post was last edited by humker on 2017-12-8 at 18:47. This type of gameplay has been tried before. First: you need to determine exactly how much money you are willing to spend on this task. Hehe. Is the number of licenses for the ABB AC800F sufficient? Are there the necessary function licenses available (such as Modbus, etc.)? We can then discuss the remaining points one by one. 1. Modbus can be used: This is certain, provided that ABB has Modbus communication cards. From what I’ve seen, almost all of the models listed support Modbus communication, and they can generally function either as Modbus masters or slaves. The problem lies in the use of Modbus for handling such large volumes of data; the costs associated with this – primarily the number of licenses required, as well as the cost of Modbus functionality licenses and communication modules – are the main factors that need to be taken into consideration. If DP communication is used, the 800F can only act as a DP master, not as a slave. In the aforementioned systems, some of them (such as HaliTech’s systems) do not support DP master-slave functionality; therefore, it is necessary to use a DP coupler for master-slave conversion. Another issue that arises is related to expanding the number of authorized points. Both of these approaches present a significant challenge in terms of programming effort, and I personally do not recommend using them. If a Siemens system has an operator station that allows data to be transmitted via OPC, then given that the other systems also have OPC servers, it is highly recommended to use OPC communication for all measurement points. In principle, Zhejiang University’s OPC server requires separate authorization, while HaliTech’s OPC server can be obtained free of charge, but it still needs to be licensed in order to be used on a long-term basis. The greatest advantage of this is that although the amount of work involved is significant, there is a batch-based approach, so it takes little time; basically, no changes are needed to the control station section. Given my engineering experience, I recommend the following approach: For the Allen-Bradley and control system components, use OPC communication; both the control system and Allen-Bradley devices should act as OPC servers (make sure there is an authorization for using the OPC server function). The ABB AC800F device will serve as the OPC client (no authorization is required for this). As for the Siemens components, if there is a corresponding HMI software, use that software’s OPC server function to transfer the data; if not (which is quite likely, as on-site systems usually consist of just touch screens or similar), use the Modbus communication protocol to send the data to the ABB AC800F. A FI813 card is required in the AC800F unit. Personally, I do not recommend using DP, as it involves significant changes to ABB’s DCS system itself, and there is also a strong mutual influence among the various systems. Moreover, it increases the technical requirements for maintenance personnel