Model

The model of one module represents the uncontrolled behavior of the machine. That means all properties of the real hardware part have to be mapped to the model (software). In the model all actuators and sensors have to be included. To describe special behavior one must use algorithms either in Structure Text or in Java.  Actuators are inputs, because the model itself receives data from the controller and reacts in a special way. Sensors are outputs for the model block, because they provide information about the state of the model and this information is supposed to be sent to the controller and the view FBs. The algorithms analyze and calculate the data from the inputs (actuators) and create states in which the model is situated. Note, that the algorithms of the model only describe the behavior of the real object. That means these algorithms represent the reaction of the model, e.g. when an actuator is changing its state. All other actions are performed by the controller of the module and the model has to react.

View

The visualization is realized by connecting the passive adapter of a module with its special graphical FB, which represents the visualization and has algorithms inside. Those algorithms are adverted to a java file named testpic.java and its compiled class testpic.class. This class evokes pictures in bitmap-format. After clicking RUN/LAUNCH on the toolbar and then RESET and START on the PANEL, the modeled plant begins to run. Which visualization refers to the FBs, one can see on the green frame.

Control

The controller of one module is supposed to control the model. That means actuators are set, so that the model functions in the proper way. The controller consists of inputs, outputs and algorithms. The inputs are represented by the sensors of the model, because the controller has to know the state of the model. The outputs are represented by the actuators of the model, because with them the model is controlled. In the algorithms the data of the sensors is analyzed and with this information the data for the outputs (actuators) is created. The algorithms for the controller have the purpose to control the model (and the real object), which means the aim of the module has to be realized in these code lines.

 

to view complete Function blocks please refer to the System configurations...

 

« back to content