Page index
Hardware-Interfaces
Bus-Hardware
Network
Servos
Robots
COM and LPT
 File access
DLL-Interface


Go on to...


Back to...
Home
 Overview
Soft-PLC


See also...
Data type
Program structure
Operations
 Failure system
Different modes
WAGO

To top of page

To top of page

To top of page

To top of page

To top of page

To top of page

To top of page

To top of page

To top of page

To top of page

Hardware-Interfaces

Because of the requirements of practical applications, different interfaces were implemented. They are designed in a way, in wich the programmer only has to adapt the prepared data. The preparation is already made in the interface. In most cases this is done by splitting the transferred data block into bits and bytes. So single bits, bit groups, bytes, words, etc. can easily be appointed. The classification can alternatively be done by text analysis or test synthesis.

Different Hardware-Interfaces

+

Hardware Interfaces

+

Industrial-Bus-Hardware
Profibus DP Master
Profibus DP Slave
CANopen Master
TCP/IP Modbus
Bus-Auto-Configuration
Product selection
Free definition of special products
Multiplexer

+

Network
TCP/IP Interface
TCP/IP Modbus
Computer linking
DDE
Intelligent Servos
Industrial robots
COM and LPT interfaces
File access
DLL-Interface

Industrial-Bus-Hardware
The most important interfaces for process hardware are industrial bus systems. Presently Profibus Master and Slave and CAN-open Master are realised.
Below this tree element the decentralized bus interfaces and I/O-Modules are attached. The selection is made intelligently from a list of predefined brands and types. Modules that are not available can be configured manually or by using a GSD-File. This can be saved specifically to the user. It is not neccessary to configure the bus seperately. This is done automatically by the tree structure.
Bus-Auto-Configuration
A bus configuration does no more have to be accomplished separately.
Product selection
The selection takes place intelligently steered from a list of pre-defined manufactures and types.
Definition of hardware
Interfaces, bus interface boards, bus modules and other cards are shown and configured in the MPC-Solution tree.
The diagram of the hardware allows quick and easy access to data of the hardware units being used in programs or being visualized on screens.

Current conditions can be retrieved at any time - this is important for the initial operation.
Because of the simple hardware configuration within the MPC-Solution file you can quickly adjust the basic setup of the hardware.

Free definition of special products
Not available building groups can be configured manually or over a GSD file automatically. Then they can optionally be stored user specifically.
Multiplexer 
If more data has to be transfered over an industrial bus than the process image permits, you can use the multiplexer function of MPC Solution. This is to a large extent automated and requires minimum expenditure for the programmer. Multiplexing is separately possible for all process images (input, output, diagnosis and parameter). On the process image a multiplexer variable and a multiplexer data block is defined. The latter contains different contents in dependence on the multiplexer variable. The remaining data of the process image is cyclically transmitted. Program variables are assigned to each possible contents of the multiplexer block in dependence on the multiplexer variable, so that after the parametrization in the hardware definition only variables must be accessed in the program.

Example:
With a process image of 200 bytes, 880 bytes of utilizable data must be transferred.80 byte of that are fast data, which must be transfered each cycle.
In the process image are thus accommodated:
80 bytes fast data
100 bytes multiplex block
4 bit multiplex variable
Thus still 19 bytes and 4 bits remain reserved for extensions. There are 8 different multiplex block contents of (multiplex variables content 0-7; 8-15 is reserve). Each block contains 100 byte utilizable data. Each block is considered as separate process image and gets its appropriate variables assigned.


Network
TCP/IP

 

This kind of interface makes a direct TCP/IP connection from PC to the periphery possible.

TCP/IP Modbus interface

The TCP/IP Modbus interface is an industrial bus for the coupling of decentralized periphery over Ethernet. The realization is economical, since in the computer only a normal network card is needed.
Process interface equipment products of different manufacturers can be used. Among them also the complete Ethernet palette of Wago©. The treatment of the modules takes place similarly to the Profibus or CANopen.

Computer linking

When having disistributed decentral systems it is necessary to exchange data between several computers. This is very simple via TCP/IP and Fast Ethernet. Therefore one system exports miscellaneous variables. The other systems can import these variables and copy them into their own system. This copy will be actively kept synchronious to the original.
DDE
DDE is available for all variables in the system. So data exchange with all usual aplication for Windows is granted. MPC-Solution acts as DDE-Server.

Intelligent servos
MPC-Solution supports also intelligent bus servos.

Industrial-Robots
Via a serial interface a KUKA industrial robot can be connected. This robot can be remotely controlled. The single movement commands or the access to the robots´ I/O-units are integrated in the control program. Thus synchronisation processes between PLC and robot are easier than with a seperate robot program. Thereby real time events can affect the movement of the robot. As well the programmer does not have to learn two programming languages. An important advantage is the operation made completely by one system.

COM and LPT  
The transfered data block is distributed to variables as explained above. The transmission is done automatically by time steering (without the need to program anything!) or explicitly by an operation. The typical Baud Rates can be adjusted. Additionally we offer 3964 and 3964R protocol.

File access

The communication with files on disk (binary or text) is similar to COM-interfaces. Operations for file handling are available.

DLL-Interface

 

A DLL-interface is used to call certain functions which are left behind in a DLL (library). To the DLL, parameters can be given from MPC-Solution - which are processed in the DLL - and a return value comes back. It is not of importance if the DLL is written in C or VB.