Profibus DP Driver for JMobile This Technical Note contains the information needed to connect the HMI to control devices using the Profibus DP protocol. Exor International S.p.A. ptn0422 Ver. 1.01
Copyright 2013 Exor International S.p.A. Verona, Italy Subject to change without notice The information contained in this document is provided for informational purposes only. While efforts were made to verify the accuracy of the information contained in this documentation, it is provided as is without warranty of any kind. Third-party brands and names are the property of their respective owners. www.uniop.com Profibus DP Driver for JMobile 2
Contents Profibus DP Driver... 4 Protocol Editor Settings... 4 Configuring the HMI as a Slave Node... 4 Special Data Types... 5 Tag Definition for Profibus DP... 5 Communication Status... 6 Profibus DP Driver for JMobile 3
Profibus DP Driver The Profibus DP communication driver has been designed to connect HMI products to a Profibus DP network as slave nodes. With the Profibus DP driver, the HMI simply exchanges Input and Output data with the Master. It is up to the Master to make sense of this data. Connection to Profibus DP network requires the optional Profibus DP communication module. Verify the suitable version for your HMI model. Please note that changes in the controller protocol or hardware, which may interfere with the functionality of this driver, may have occurred since this documentation was created. Therefore, always test and verify the functionality of the application. To accommodate developments in the controller protocol and hardware, drivers are continuously updated. Please ensure that the latest driver is used in the application. Document code ptn0422 Version 1.01 Protocol Editor Settings Add (+) a driver in the Protocol editor and select the protocol called Profibus DP from the list of available protocols. The driver configuration dialog is shown in figure. Figure 1 Panel Node ID The Profibus node ID assigned to the HMI Configuring the HMI as a Slave Node The Profibus DP master must be configured to communicate with the slaves devices present in the network. To configure the Master System you will generally need a software package available from the manufacturer of the Master System. Before the master configuration software can recognize the the HMI device as slave, it must be included in the catalog of devices. For this purpose it is available a device description file in the standard GSD format. The device description file is EX9649AX.GSD. It must be installed following the instructions of the network configuration software you are using. One of the fundamental steps of the configuration of a slave station in a Profibus DP system is the mapping of the slave s I/O buffers in the memory of the master. Profibus DP Driver for JMobile 4
The HMI panels support Input / Output buffer sizes of 8, 16 or 32 bytes and they expect that both the Input and the Output areas are configured to the same size, i.e. both 8 bytes, either 16 bytes or both 32 bytes. The HMI panels will automatically detect the buffer size used by the master. The feature generally referred to as Response Monitoring should always be disabled in the master for the HMI panel slaves. Special Data Types The Profibus DP communication driver provides one special data type called "Node Override". The Node Override ID allows changing at run time the value of Panel Node ID. This memory type is an unsigned byte. The Node Override ID is initialized to the value defined as Panel Node ID in the project at programming time. The communication with the master is described in the table. Node Override ID value Behavior 0 The communication with the master is stopped 1 to 255 If Node Override ID has a value different from 0, it is interpreted as the new node ID for the slave device. Note: the Node Override values assigned at run-time are retained through power cycles Tag Definition for Profibus DP Figure 2 1) Studio allows you to access the HMI panel Output Buffer, the area containing data sent from the PLC, as well as the HMI panel Input Buffer, the area containing data to be sent to the PLC. The data in the Output Buffer is read only, while the data in the Input Buffer is read write. The Address Offset range (in bytes) for these 2 types is from 0-31. It should be borne in mind, however, that that Input / Output buffer range configured in the PLC for the panel can be either in the range 0-7, 0-15 or 0-31. 2) In addition to the Input Buffer and the Output Buffer Designer also allows you to access the Internal Work Buffer data type. This buffer is purely an internal buffer in the panel. The panel Profibus DP Driver for JMobile 5
sets aside 256 bytes for this buffer. The data in this buffer is neither read from nor written to the PLC. It is purely a work area. Communication Status The current communication status can be displayed using the dedicated system variables. Please refer to the User Manual for further information about available system variables and their use. The codes supported for this communication driver are: Error NAK Timeout Invalid response General error Notes Controller replies with a not acknowledge. Request is not replied within the specified timeout period; ensure the controller is connected and properly configured for network access The panel did receive from the controller a response, but its format or its contents or its length is not as expected; ensure the data programmed in the project are consistent with the controller resources. Error cannot be identified; should never be reported; contact technical support Profibus DP Driver for JMobile 6