X hits on this document





16 / 21


In network 5 (the network with the STRTSERV function), right click on SRV4_EX and then View Servo Setup. Do a File | Save As to SRV4_NEW.


Make any necessary changes to the servo setup and then do a Compile | Make Function. When prompted for the library name for the servo function, change the name to ZNEWAPPL.


Close servo setup.


Replace the SRV4_EX function with the new servo setup function you just created by clicking on Ladder |Functions | ZNEWAPPL | SRV4_NEW.


Close the NEW_APPL ladder window and save the changes when prompted.


Go to back to the project window and delete MMC4_EX from the MAIN .LDO and add NEW_APPL.ldo.


Do a File | Update Project Tree to update the project.


Close the project. When prompted to compress the application select No. You do not need to compress the project until you are ready to store it on the flash disk.


Using Windows Explorer delete the MMC4_*.* files, the SRV4*.* files and ZSRVMMC.LIB file from the new project folder: C:\Program Files\Giddings & Lewis\Applications V13.0.1\New_Appl

Note that if the application is using SERCOS-controlled servos, the above procedure is followed starting with MMC4_SOI with additional steps to replace the example SERCOS setup file.


The following is a description of the functionality provided with each standalone MMC example.

The purpose of each example is to provide a foundation for a customer's own application. As mentioned above, each provides all the basic features of most applications:

Loading the servo configuration

Closing the servo position loops

Handling emergency stop and control stop conditions

Jogging the axes

Referencing (or homing) the axes

Typically, the ladder logic required for a specific application can be added to the end of an example.

Which example is the best starting point depends on the specific application: how many servo axes are required and will an operator interface device be used?

Basic Application Examples

The following is a description of the two examples that lack an operator interface. They are MMC2_EX for a 2 axis MMC and MMC4_EX for a 4 axis MMC.

The initial network with the STRTSERV function loads the servo setup configuration. Each example ladder includes a servo setup example (such as SRV2_EX for a 2 axis MMC or SRV4_EX for a 4 axis MMC). Each application must have its own servo setup configuration. Typically, this configuration is unique for every application as each could have different ratios of programming units (i.e., inches, millimeters, degrees, etc.) to the servo feedback units, different travel limits, different servo PID gains, etc.

The M_CHK1 and M_CHK49 function blocks check which axes are configured within the loaded servo setup. These blocks make it easier to write sections of ladder code that support different numbers of axes; by checking the Booleans set here, the appropriate actions can be taken based on the axes that are configured.

The M_CLOS1 function blocks will close the position loops for the configured servo axes. This action also includes resetting any internal e-stop or c-stop servo conditions (a servo e-stop will open the position loop).

The M_STATUS and M_ERROR function blocks provide all the significant data for the servos in one place within the ladder. If the application is using the digitizing axis available with the MMC, there is a network that checks that axis for an e-stop condition (that can result from a 'loss of feedback' hardware error).

The STATUSSV functions provide the ladder with information regarding the state of the respective servo fast inputs. Each axis has a DC input provided with a 'fast input' capability - so that (when enabled) the axis can latch the axis position at the instant the DC input occurs, based solely on the input condition rather than on the ladder scan time.

The network with the ESTOPACT coil monitors for an emergency stop (or e-stop) condition. The purpose for this network is to ensure that if an e-stop condition is detected, all the servo axes will be e-stopped immediately.

The network with the CSTOPACT coil monitors for a controlled stop (or c-stop) condition. The purpose for this network is to ensure that if a c-stop condition is detected, all the servo axes will be c-stopped immediately.

MMC-Cimrex Quick Start.doc


Document info
Document views34
Page views41
Page last viewedSun Aug 28 02:04:38 UTC 2016