![]() ![]() ![]() In both of the examples above, changes would be made to the application using WindowMaker on what is typically referred to as an engineering workstation. Below is a diagram that depicts this scenario. Essentially this allows for continuous communication to the PLC's in the event of hardware or some other issue with the DA Server. This setting is configured within the access name(s) in the InTouch application. To add resiliency to the implementation it is a good practice to add a primary and backup DA server. In the scenario above, there is a single path for IO communication with the PLC's. ![]() Below represents a small architecture depicting this scenario: In general a small system could be a certain number of clients that connect to a DA Server and the DA Server communicates with the PLC or other field device. These requirements should include items such as the number of clients the implementation will require, the number of IO (data points from PLC's) that will be required, physically where will these clients be located and do these locations have the necessary network connections to other systems. When developing an architecture for a system one should review specific application requirements. These can range from the number of users / operators that will use the application to the manufacturing process / environment that the application is deployed within. ![]() InTouch interacts directly with DA Server reading / writing data to the PLC.Īrchitectures for Wonderware InTouch typically are driven by multiple factors. Usually it is either the PLC Brand or communication protocol used for PLC communication that determines what DA Server is used. These DA Servers are independent software applications of InTouch and are typically hardware specific. Device integration is achieved through Data Acquisition Servers (DA Servers). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |