Issue
The Ethernet communications can be confusing to program using Unity, since they vary from PAC family to family. This is one of a series of example applications that presents each function block in a working version for the user to build on.
Product Line
Quantum, M580, Control Expert, Unity Pro
Environment
Windows 7, Windows 10
Resolution
The attached application mbpmstrf2.zef will read ten registers from another device (using MBP_MSTR function 2). The application consists of three sections. The first is an ST section in which variables are initialized. The second section, which is the example proper, is a LD section which uses an MBP_MSTR function block to read 10 registers from another device, the server. The IP address of the server is 192.168.1.30. This should be changed to suit your own addressing scheme. There is also code in that section to time the response. The MBP_MSTR block does not contain a timeout. It is good practice to program your own application timeout. The timer can be set to an appropriate value. If the timer expires the application issues a reset of the connections to the server. This can be seen in section 3. The application is annotated and should provide a start for the user of the MBP_MSTR block. It is up to the user to change the PAC type and IP addresses to meet their own requirements. There is both a .zef and .xef version in the zip file.
The Ethernet communications can be confusing to program using Unity, since they vary from PAC family to family. This is one of a series of example applications that presents each function block in a working version for the user to build on.
Product Line
Quantum, M580, Control Expert, Unity Pro
Environment
Windows 7, Windows 10
Resolution
The attached application mbpmstrf2.zef will read ten registers from another device (using MBP_MSTR function 2). The application consists of three sections. The first is an ST section in which variables are initialized. The second section, which is the example proper, is a LD section which uses an MBP_MSTR function block to read 10 registers from another device, the server. The IP address of the server is 192.168.1.30. This should be changed to suit your own addressing scheme. There is also code in that section to time the response. The MBP_MSTR block does not contain a timeout. It is good practice to program your own application timeout. The timer can be set to an appropriate value. If the timer expires the application issues a reset of the connections to the server. This can be seen in section 3. The application is annotated and should provide a start for the user of the MBP_MSTR block. It is up to the user to change the PAC type and IP addresses to meet their own requirements. There is both a .zef and .xef version in the zip file.
Publié pour: Schneider Electric Belgium
