Section C: Integrating the core “flying saw” functions

Program environment and interfaces

Flying Saw with SIMOTION

A4027118-A0414

6.2Call environment

The function block FB_BGD_TEMPLATE_FlyingSaw() of the “flying saw” core function must be cyclically called in the user program. This is the reason that the call can only be made from a program that is incorporated in the background task.

Fig. 6-1 Call environment of the FB_BGD_TEMPLATE_FlyingSaw()

All rights reserved

Saw V1.4.doc

Copyright Siemens AG 2008

Manual SIMOTION Flying

B a c k g r o u n d

T a s k

U s e r s

P r o g r a m

SIMOTION

TO specific commands

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Unit „FS_Var“

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

„FB_BGD_

 

 

TO

specific

 

 

 

 

 

 

TEMPLATE_

 

 

commands

 

 

 

 

FlyingSaw()“

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Central Function Flying Saw

 

 

 

 

 

 

 

 

 

 

 

 

 

TO

other Axes

in mode (4) Manual only

TO

Flying Saw Axis

The technology object “FlyingSawAxis”, influenced by the function block FB_BGD_TEMPLATE_FlyingSaw(), may only be addressed by the user program if, beforehand, the user switched the core “flying saw” function into Mode 4 “Manual”. In all of the other modes, it is not permissible that the user program influences the technology object “FlyingSawAxis”.

6.3Interfaces

6.3.1Classifying the interfaces

The function block FB_BGD_TEMPLATE_FlyingSaw() can be influenced using several parameters and interfaces that are classified/sub-divided into the following areas:

V 1.4

Release 06/06/08

65/107

Page 65
Image 65
Siemens A4027118-A0414 user manual Call environment, Interfaces, Classifying the interfaces