There is an example provided for the press transfer ASFB set within the motion ASFB package. This example (MMC4_PT) is an extension of the 4 axis MMC example with an operator interface. There is a detailed 'readme' file for this example's user interface and the accompanying ladder logic; that file is MMC4_PT.TXT.

Stepper Application Example

There is an example provided for the stepper block I/O module. This example (MMC_STEP) is a simple ladder to illustrate the control logic for a stepper module.

The UDFB U_STPRC handles the overhead required for a stepper control. This UDFB handles the stepper home or zero reference, jog, move a distance, move to a position, controlled-stop, emergency stop, and a reset of a c-stop or e-stop.

Centurion DeviceNet Positioning MicroDSM Drive Application Example

There is an example provided for the Centurion DeviceNet MicroDSM drive. This example (MMC_DND) is a simple example to illustrate the logic to control the DeviceNet scanner and to control the DeviceNet drive over DeviceNet.

The ASFB M_DNJOGC handles the overhead required for the jog motion. The ASFB M_DNPOSC handles the overhead required for the motion of either a move of an incremental distance or a move to an absolute position. Note that both of these ASFBs are for the Centurion DeviceNet MicroDSM drive. Other DeviceNet drives will have their own unique DeviceNet interface (i.e., the respective boolean, byte and long-word tag name assignments in the scanner's memory map).

The ASFB M_DNSTAT extracts the details for the DeviceNet module status into individual bytes and booleans.

This example ladder is referenced in the MicroDSM with DeviceNet installation manual. It serves as the programming example for the MicroDSM with DeviceNet drive. The MMC_DND.GLC DeviceNet scanner's configuration data file is also referenced in the same drive manual to illustrate how to define the tag names for the DeviceNet drive's input and output data.

SERVO SETUP ASSISTANT

The Tools directory contains ServoSetupAssistant.xls. The ServoSetupAssistant is an Excel spreadsheet tool that makes creating your servo setup information a little bit easier. You specify machine parameters such as time base and precision in the ServoSetupAssistant spreadsheet. Based on these parameters the servo setup information for an axis is automatically calculated and can be imported into PiCPro for Windows using the new Import button that is provided under the 'Axis Data' tab. To use this spreadsheet:

1.

Do a File Save As to save this spreadsheet as a different name to maintain the original. A different .XLS file should be made for each axis in your application.

2.

Two sheets are provided for each type of axis that is allowed: Closed loop servo, Digitizing, and Closed loop SERCOS. The first sheet is used to input data, the second sheet holds the servo setup data that will be imported into PiCPro. You may delete the sheets for axes that are not being used. Double click on the tab for a sheet to change the name of the sheet to match the description of the axis.

3.

Enter the data for the axis. The setup information is being automatically calculated on the next sheet as you enter. Enter only information with pull down boxes or data that appears in blue. When you are ready to save the information for an axis select the sheet called 'PiCPro 'X' Setup Data' (where X is Servo, Digitizing or SERCOS Servo). NOTE: Before you save the file in .CSV format, you must save the entire workbook by doing a File Save to keep your edits. If you do not do this, all formulas and changes will be lost when you save the file in .CSV format.

4.

From the File menu select Save As and save the sheet under a different name, with file type .CSV (comma delimited variable). Excel will prompt you through the save process. All other sheets in the workbook and all formulas will be deleted in the .CSV file.

5.

Close the files in Excel.

6.

Start PiCPro for Windows. Import the data from the .CSV file by selecting the Import button under axis data.