Difference between revisions of "Project Example: Flip Flop (Structure Text)"
(Created page with "FF ST creation") |
|||
| (10 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | FF ST | + | {{Languages|Project_Example:_Flip_Flop_(Structure_Text)}} |
| + | The task's purpose is to set and reset an output. <br/> | ||
| + | The main program initializes a startup process in the softMC. <br/> | ||
| + | After the startup process is done, a global variable is set and programs 'Axis1' and 'Axis2' are called. <br/> | ||
| + | The application uses two drives and their outputs. <br/> | ||
| + | <br/> | ||
| + | |||
| + | After installation of device description file (created by the Configurator) to Device Repository, the drive's address will be declared in the Axis Pool: | ||
| + | |||
| + | [[File:FF A1.PNG|border|600px]] [[File:FF A2.PNG|border|600px]] | ||
| + | <br/> | ||
| + | <br/> | ||
| + | |||
| + | In the EtherCAT Slaves section, we can find the I/O mapping for each device.<br/> | ||
| + | In the picture below Input1, Input2, Output1, Output5 are declared as new variables (can also be mapped as existing variables): | ||
| + | |||
| + | [[File:FF CDHD I_O.PNG|border|600px]] | ||
| + | <br/> | ||
| + | <br/> | ||
| + | |||
| + | The main program uses 'softMC_Startup' FB ('mc_st' Instance) to initialize a startup process in the softMC. <br/> | ||
| + | When the process is done, a global variable will be set TRUE. After that, programs 'Axis1' and 'Axis2' are called. | ||
| + | |||
| + | [[File:FF main program ST.PNG|border|850px]] | ||
| + | <br/> | ||
| + | <br/> | ||
| + | |||
| + | When programs 'Axis1' and 'Axis2' are called, output5 is turned on.<br/> | ||
| + | After that, 'SR' FB is enabled with output1 as 'Q1' ('SR_0' Instance). <br/> | ||
| + | Input1 will trigger the 'set' function and input2 will trigger the 'reset' function.<br/> | ||
| + | Programs 'Axis1' and 'Axis2' are similar:<br/> | ||
| + | |||
| + | [[File:FF Axis1 ST.PNG|border|750px]] [[File:FF Axis2 ST.PNG|border|590px]] | ||
| + | <br/> | ||
| + | <br/> | ||
| + | |||
| + | ==Visualization== | ||
| + | |||
| + | The program is controlled by a graphic interface: | ||
| + | <br/> | ||
| + | |||
| + | [[File:FF Visualization.PNG|border|600px]] | ||
| + | <br/> | ||
| + | <br/> | ||
| + | When the startup process of softMC is done, the blue lamp is turned on.<br/> | ||
| + | The user can set and reset the outputs of the two drives with special buttons for each function. In addition, the result of the 'SR' FB is shown by the green lamps. | ||
Latest revision as of 02:31, 16 July 2017
| Language: | English • 中文（简体） |
|---|
The task's purpose is to set and reset an output.
The main program initializes a startup process in the softMC.
After the startup process is done, a global variable is set and programs 'Axis1' and 'Axis2' are called.
The application uses two drives and their outputs.
After installation of device description file (created by the Configurator) to Device Repository, the drive's address will be declared in the Axis Pool:
In the EtherCAT Slaves section, we can find the I/O mapping for each device.
In the picture below Input1, Input2, Output1, Output5 are declared as new variables (can also be mapped as existing variables):
The main program uses 'softMC_Startup' FB ('mc_st' Instance) to initialize a startup process in the softMC.
When the process is done, a global variable will be set TRUE. After that, programs 'Axis1' and 'Axis2' are called.
When programs 'Axis1' and 'Axis2' are called, output5 is turned on.
After that, 'SR' FB is enabled with output1 as 'Q1' ('SR_0' Instance).
Input1 will trigger the 'set' function and input2 will trigger the 'reset' function.
Programs 'Axis1' and 'Axis2' are similar:
Visualization
The program is controlled by a graphic interface:
When the startup process of softMC is done, the blue lamp is turned on.
The user can set and reset the outputs of the two drives with special buttons for each function. In addition, the result of the 'SR' FB is shown by the green lamps.