M1301-7003 14.1 PiCPro SoftwareManual

PiCPro for Windows ™ ®
Software Manual
Version 14.1
G&L Motion Control

NOTE
Progress is an ongoing commitment at G&L Motion Control. We continually strive to offer

the most advanced products in the industry; therefore, information in this document is subject
to change without notice. The illustrations and specifications are not binding in detail. G&L
Motion Control shall not be liable for any technical or editorial omissions occurring in this
document, nor for any consequential or incidental damages resulting from the use of this
document.
DO NOT ATTEMPT to use any G&L Motion Control product until the use of such product is
completely understood. It is the responsibility of the user to make certain proper operation
practices are understood. G&L Motion Control products should be used only by qualified
personnel and for the express purpose for which said products were designed.
Should information not covered in this document be required, contact the Customer Service
Department, G&L Motion Control, 672 South Military Road, P.O. Box 1960, Fond du Lac,
WI 54936-1960. G&L Motion Control can be reached by telephone at (920) 921–7100.
Release 2004
Part Number M.1301.7003
© 1995-2004 G&L Motion Control
IBM is a registered trademark of International Business Machines Corporation.

Windows 98, NT, Microsoft, XP, and MS-DOS are registered trademarks of Microsoft Corporation.
Pentium and PentiumPro are trademarks of Intel Corporation.
ARCNET is a registered trademark of Datapoint.
PiC900, PiCPro, PiCMicroTerm, MMC are trademarks of Giddings & Lewis.
Table of Contents
PiCPro for Windows Software Manual
CHAPTER 1-Getting Started with PiCPro for Windows ....................... 1
Introduction to PiCPro for Windows .................................................................. 1

PiCPro for Windows Professional Edition ................................................... 2
PiCPro for Windows MMC-Limited edition ................................................ 2
PiCPro for Windows Monitor Edition .......................................................... 2
Customer Services .............................................................................................. 2
Principal Technical Support Services ........................................................... 2
Hands-on Training Schools .......................................................................... 3
Before Calling Technical Support ................................................................ 3
World Wide Web Site ................................................................................... 3
The Computer Workstation ................................................................................ 3
Hardware Connections ........................................................................................ 4
Infrared Communications Drivers ................................................................ 4
Installing PiCPro for Windows ........................................................................... 4
The Work Area in PiCPro for Windows ............................................................. 5
The Main Ladder Area .................................................................................. 5
Status Bar ...................................................................................................... 6
Status Bar Details .......................................................................................... 8
Window Elements ............................................................................................... 9
The Title Bar ................................................................................................. 9
The Menu Bar ............................................................................................... 9
Dialog Boxes ................................................................................................. 10
Help Files ...................................................................................................... 10
Ladder ........................................................................................................... 11
Start-up .......................................................................................................... 12
To change a color..................................................................................... 14
Moving Toolbars ........................................................................................... 16
Displaying/Hiding Toolbars ......................................................................... 16
Organizing PiCPro Files ..................................................................................... 17
PiCPro Libraries ........................................................................................... 17
Library Contents ........................................................................................... 18
Using On-line Help ............................................................................................. 19
Using What's This? Help .............................................................................. 19
Retrieving On-line Help ................................................................................ 20
Printing On-line Help .................................................................................... 20
Using Function/Function Block Help ........................................................... 20
Creating Function/Function Block Help ....................................................... 21
Starting PiCPro ................................................................................................... 22
CHAPTER 2-Working with Projects ....................................................... 23
TOC-1
Overview: Using Projects ................................................................................... 23
Menu Commands that Manage Projects ....................................................... 23
The Project Tree and Its Components ........................................................... 25
Project Tree Categories ....................................................................................... 26
Category: PROJECT NAME ........................................................................ 26
Category: MAIN.LDO .................................................................................. 28
Item: MAIN.LDO ......................................................................................... 29
Category: COMPRESSED FILE .................................................................. 29
Item: COMPRESSED FILE ......................................................................... 31
Category: PiCPro VERSION ........................................................................ 31
Item: PiCPro VERSION ............................................................................... 33
Category: PiCPro LIBRARY PATHS .......................................................... 34
Item: PiCPro LIBRARY PATHS ................................................................. 35
Source and Library File Categories .............................................................. 36
Category: Source and Library Files .............................................................. 37
Item: Source and Library Files ..................................................................... 38
Category: OTHER FILES ............................................................................. 39
Item: OTHER FILES .................................................................................... 40
Creating a New Project ....................................................................................... 40
Opening an Existing Project ............................................................................... 42
Opening a Project File (.PRJ) ....................................................................... 43
Opening a Compressed Project File (.G&L) ................................................ 44
Compressing a Project ........................................................................................ 46
Launching a Project ............................................................................................ 47
Printing a Project ................................................................................................ 48
Copying a Project (Save As) ............................................................................... 48
CHAPTER 3-Working with Ladders ........................................................ 51
A PiCPro Session ................................................................................................ 51

Creating New Files ....................................................................................... 51
Opening a New Ladder File .......................................................................... 52
Opening an Existing Ladder File .................................................................. 53
Opening a Recently Opened File .................................................................. 54
Password Protecting LDO Files .......................................................................... 55
Overview ....................................................................................................... 55
File Properties Dialog for Password Protection ............................................ 56
To Password Protect a File ........................................................................... 59
Opening a Password Protected File .............................................................. 60
To Modify an Existing Password............................................................. 62
To Remove an Existing Password ........................................................... 64
Locking a File ............................................................................................... 66
Locking a File with password protection................................................. 66
Locking a File with no password protection............................................ 66
PiCPro Tools ....................................................................................................... 67
Using the Pointer Tool .................................................................................. 67
TOC-2
Zooming In and Out ...................................................................................... 67
Using Zoom Command from View Menu ............................................... 67
Using Zoom Command from Navigator Toolbar .................................... 68
Selecting and Deselecting Items ................................................................... 68
Focus ........................................................................................................ 68
Selection................................................................................................... 69
Deselect.................................................................................................... 70
Entering Ladder Networks .................................................................................. 70
Inserting a Network ...................................................................................... 70
Inserting a ST network with focus in a ST element................................. 71
Inserting a LD network with focus in a ST element ................................ 72
Inserting a ST network with focus in a LD element ................................ 72
Overview - Cut, Copy, Delete and Paste ............................................................ 73
Delete ................................................................................................................. 73
Deleting LD or ST Networks ........................................................................ 73
Deleting LD or ST Network Elements ......................................................... 73
Deleting LD Elements or Structured Text .................................................... 74
Cut, Copy, and Paste ........................................................................................... 74
Cutting Network Elements ............................................................................ 74
Cutting LD Elements or Structured Text ...................................................... 74
Copying LD Elements or Structured Text .................................................... 75
Copy Rules............................................................................................... 75
Pasting LD Elements or Structured Text ..................................................... 75
Paste Rules ............................................................................................... 76
Paste Insert Rules..................................................................................... 77
Drag and Drop .................................................................................................... 77
Drag and Drop Copy ..................................................................................... 77
Drag and Drop Copy Rules...................................................................... 78
Drag and Drop Move .................................................................................... 78
Drag and Drop Move Rules ..................................................................... 78
Drop Rules .................................................................................................... 79
Other Notes - Drag and Drop ........................................................................ 79
Finding and Replacing ........................................................................................ 80
Finding and Replacing - Procedures ............................................................. 82
To search for an element in the ladder..................................................... 82
To search and replace an element in the ladder ....................................... 82
Filtering Find and Replace ............................................................................ 83
Finding Duplicates ........................................................................................ 84
Saving, Closing, and Exiting .............................................................................. 84
Saving Files ................................................................................................... 85
Saving Files with a Different Name ............................................................. 85
Closing Files ................................................................................................. 86
Exiting PiCPro .............................................................................................. 86
Working with a Split Screen ............................................................................... 86
Hardware Declarations ....................................................................................... 88
Hardware Declaration Restrictions ............................................................... 88
TOC-3
Entering Hardware Declarations ......................................................................... 89
To bring up the Hardware Declarations table .......................................... 89
To enter hardware declarations - master rack (all CPU types) ................ 90
Viewing Hardware Declarations ................................................................... 91
Hardware Declarations Table - PiC CPU ................................................ 91
Hardware Declarations Table - Remote I/O Expansion Rack ................. 95
Hardware Declarations Table - MMC for PC CPU ................................. 95
Hardware Declarations Table - Standalone MMC CPU.......................... 96
Hardware Declarations Table - Block I/O Module.................................. 97
Editing Hardware Declarations ..................................................................... 97
Inserting and Deleting Hardware Declarations........................................ 97
Cutting and Copying Hardware Declarations .......................................... 98
Pasting and Paste Insert in Hardware Declarations ................................. 99
Pasting to Software Declarations .................................................................. 100
Printing Hardware Declarations .................................................................... 100
Closing and Saving Hardware Declarations ................................................. 101
Software Declarations ......................................................................................... 102
Entering Software Declarations .................................................................... 102
Names and Long Names of Variables .......................................................... 103
Names ...................................................................................................... 103
Long Names ............................................................................................. 103
Reserved Keywords ................................................................................. 104
I/O Points ...................................................................................................... 105
Standalone MMC I/O Points.................................................................... 105
Fast Inputs................................................................................................ 107
MMC for PC I/O Points........................................................................... 107
ASIU I/O.................................................................................................. 107
MMC for PC Fast Inputs ......................................................................... 108
Numbering .................................................................................................... 108
PiC CPU................................................................................................... 109
Master Rack, PiC CPU ............................................................................ 109
Expansion Rack I/O ................................................................................. 109
Master Rack Standalone MMC CPU....................................................... 110
ASIU I/O for MMC for PC CPU ............................................................. 110
Block Expansion Rack I/O ...................................................................... 110
Blown Fuse Status ........................................................................................ 111
Short Circuit Detection ................................................................................. 111
Fast Inputs ..................................................................................................... 112
PiC CPU................................................................................................... 112
Standalone MMC CPU ............................................................................ 112
MMC For PC CPU .................................................................................. 112
Initial Values ................................................................................................. 112
Prefixes for initial values ......................................................................... 113
Working with Data Types in Software Declarations .......................................... 113
Bitwise .......................................................................................................... 113
Numeric ........................................................................................................ 114
TOC-4
String ............................................................................................................. 115
Time .............................................................................................................. 115
Time of Day ............................................................................................. 115
Time duration........................................................................................... 116
Groups of data - Structures and Arrays ........................................................ 116
Arrays....................................................................................................... 116
Declare an Array ...................................................................................... 117
Resize an Array........................................................................................ 119
Remove an Array ..................................................................................... 120
Referencing and accessing elements of arrays in the module ................. 120
Structures ................................................................................................. 121
Declare a Structure.................................................................................. 121
Referencing and accessing member of structure ..................................... 122
Structures with arrays .............................................................................. 123
Declare structures with arrays.................................................................. 123
Referencing and accessing data in a structure with arrays ...................... 124
Array of structures ................................................................................... 124
Declare an array of structures .................................................................. 124
Referencing and accessing data in an array of structures ........................ 126
Array of structures with arrays ................................................................ 126
Declare an array of structures with arrays ............................................... 127
Referencing and accessing the data in an array of structures with arrays 127
Attributes ...................................................................................................... 128
Retentive Attribute................................................................................... 128
Global Attribute ....................................................................................... 128
Both Global and Retentive Attribute ....................................................... 129
External Attribute .................................................................................... 129
In and Out Variable Attributes for UDFBs.............................................. 129
Editing Software Declarations ............................................................................ 129
Inserting/Deleting Software Declarations ..................................................... 130
Cutting, Copying, and Pasting Software Declarations ................................. 130
How to Select Multiple Entries................................................................ 131
Reserved Keywords when pasting ........................................................... 132
Searching in the Software Declarations Table .............................................. 134
Find by Name Only.................................................................................. 135
Find by Type ............................................................................................ 135
Find by I/O Point ..................................................................................... 135
Using the Find Next Command ............................................................... 136
Purging Unused Variables from the Software Declarations Table ............... 136
Working with Networks and Network Elements ................................................ 137
Network Size ................................................................................................. 137
LD Network Size ..................................................................................... 137
ST Network Size ...................................................................................... 138
Network Labels in Networks ........................................................................ 138
To assign or edit a label on a network, follow these steps: ..................... 139
Comments in Network Elements .................................................................. 139
TOC-5
To add comments to your ladder, follow these steps:.............................. 139
To choose the number of comment lines to display, follow these steps:. 139
Constants and Variables in Network Elements ............................................. 139
Constants.................................................................................................. 139
Variables .................................................................................................. 140
LD Elements ................................................................................................. 141
Contacts ................................................................................................... 141
Wires ........................................................................................................ 143
Functions/Function Blocks in LD Network............................................. 144
Jump in LD Network ............................................................................... 146
ST Elements and Structured Text ................................................................. 147
Expressions .............................................................................................. 147
Comments in ST Elements ...................................................................... 149
Conditional Statements ............................................................................ 151
ELSIF-THEN-ELSE ............................................................................ 153
Iteration Statements ................................................................................. 155
FOR-DO................................................................................................... 157
Other Statements in ST ............................................................................ 161
Inserting Conditional and Iteration Statements in ST.............................. 162
Rules for a Structured Text Template...................................................... 163
Functions in ST ........................................................................................ 163
Function Blocks in ST ............................................................................. 166
ST Network Considerations..................................................................... 167
Variables in ST Networks........................................................................ 168
Checking Syntax in a ST Element ........................................................... 171
Using the Right-Click Menu in a ST Element ......................................... 171
Compiling and Downloading .............................................................................. 173
Compiling ..................................................................................................... 173
Downloading............................................................................................ 173
Compiling a Bin File ..................................................................................... 173
Compile and Download ........................................................................... 174
Compile Only........................................................................................... 175
Compiling a Hex File .................................................................................... 175
To Compile a Hex File............................................................................. 176
Compiling a Task .......................................................................................... 176
To Compile a Task, follow these steps: ................................................... 176
Compiling a UDFB, follow these steps: ....................................................... 177
To Compile a UDFB, follow these steps: ................................................ 177
Settings .......................................................................................................... 178
Ignore Direct I/O...................................................................................... 179
Force Soft Bit Memory ............................................................................ 179
Generate Map File (Main Ladder Only) .................................................. 179
Operator Interface .................................................................................... 179
Extended Data Memory Feature ................................................................... 179
Tips on Working with Extended Data Memory ............................................ 180
Animating the Ladder ......................................................................................... 181
TOC-6
To Turn Animation On, follow these steps: ................................................. 181
To Turn Animation Off, do any of the following: ........................................ 182
Forcing & Viewing Variables ............................................................................. 182
Entering Variables in the Force List ............................................................. 183
Copy/Paste ............................................................................................... 184
Drag-n-Drop............................................................................................. 184
Right-Click Menu in Ladder.................................................................... 185
Manual Entry ........................................................................................... 185
Turn Forcing/Grouping On/Off .................................................................... 185
Turn Forcing/Grouping On ...................................................................... 185
Turning On Forcing/Grouping from the On-Line Menu ......................... 186
Turning On Forcing/Grouping from the Tool Bar Buttons ..................... 186
Turning Off Forcing/Grouping from the On-Line Menu......................... 186
Updating the control after Force List is edited ............................................. 187
Viewing Enabled Variables ................................................................................ 187
Copy/Paste ............................................................................................... 188
Drag-n-Drop............................................................................................. 188
Right-Click Menu in Ladder.................................................................... 188
Manual Entry ........................................................................................... 188
Turning Animation On in the View List ....................................................... 188
Controlling the Scan ........................................................................................... 189
Stopping the Scan ......................................................................................... 189
To Stop the Scan, choose one of the following: ...................................... 190
Running One Scan ........................................................................................ 190
To Run One Scan, choose one of the following: ..................................... 190
Doing a Hot Restart ...................................................................................... 190
To do a Hot Restart, choose one of the following: .................................. 190
Doing a Warm Restart .................................................................................. 190
To do a Warm Restart, choose one of the following: .............................. 190
Doing a Cold Restart ..................................................................................... 190
To do a Cold Restart, choose one of the following: ................................ 191
On-line Editing ................................................................................................... 191
To perform an on-line edit or patch, follow these steps: .............................. 192
To abort a patch ............................................................................................ 192
Printing ................................................................................................................ 193
Printing the Ladder ....................................................................................... 193
To print the ladder file, follow these steps: ............................................. 193
Selections in the Ladder Network Section of the Print Dialog ..................... 194
Include in Listing ..................................................................................... 194
Cross Reference ....................................................................................... 195
Full Comments......................................................................................... 195
Long Names ............................................................................................. 195
Page Break at Function Block ................................................................. 195
Fit Width to Page ..................................................................................... 195
Selections in the Software Declarations Section of the Print Dialog ........... 196
TOC-7
Selections in the Hardware Declarations Section of the Print Dialog .......... 196
Printing View List, Force List, or Information Window .............................. 196
To print the view list, force list, or information window, follow these steps: 196
Printout Symbols ........................................................................................... 197
Troubleshooting the Print Option ................................................................. 198
Building a Dependency List ............................................................................... 198
To build a dependency list, follow these steps: ............................................ 198
Comment Import / Export ................................................................................... 199
Importing Comments .................................................................................... 199
Exporting Comments .................................................................................... 199
Communications ................................................................................................. 200
Communications Settings ............................................................................. 200
Communication Status .................................................................................. 201
Time Read / Set ............................................................................................. 201
Downloading a Hex File ..................................................................................... 202
To Download a Hex file for a PiC or Standalone MMC .............................. 202
To Download a Hex file to a MMC for PC .................................................. 203
Configure Application / RAMDISK Size ..................................................... 203
Update CPU’s Firmware ............................................................................... 204
Update TCP/IP Module Firmware ................................................................ 204
Update SERCOS Module Firmware ............................................................. 204
Update Drive Firmware ................................................................................ 205
Download Ladder Hex File ........................................................................... 205
Clear Flash Memory ..................................................................................... 205
Clear Application Memory ........................................................................... 205
To clear application memory with any MMC CPU:................................ 206
Backing Up and Restoring User Programs ......................................................... 206
Backing Up User Programs .......................................................................... 206
Restoring User Programs .............................................................................. 206
PiC Restore ......................................................................................................... 207
CHAPTER 4-Setting Up the MMC Smart Drive ...................................... 209
Overview: MMC Smart Drive Setup .................................................................. 209

Analog Interfaced Drive Terminology ......................................................... 209
Maintenance Mode ....................................................................................... 210
Accessing Drive System Setup ........................................................................... 211
Create a New Analog Interfaced Drive System File ..................................... 211
Open an Existing Analog Interfaced Drive System File ............................... 211
ONLINE Drive List view Details ................................................................. 213
Drive Label ............................................................................................. 214
Connected?............................................................................................... 214
Enabled?................................................................................................... 214
Faults? ...................................................................................................... 215
Data - File vs. Actual ............................................................................... 215
TOC-8
ONLINE Drive List/Drive Data view Scenarios ................................................ 216
Connect to Drive in Drive List ..................................................................... 216
Drive List view ........................................................................................ 216
Drive Data view ....................................................................................... 216
Disconnect the Current Drive and Connect to a Different Drive Already
in the Drive List ............................................................................................ 216
Drive List view ........................................................................................ 216
Drive Data view ....................................................................................... 216
Connect to an Initialized Drive not in the Drive List ................................... 217
Drive List view ........................................................................................ 217
Drive Data view ....................................................................................... 217
Connect to an Uninitialized Drive not in the Drive List ............................... 218
Drive List view ........................................................................................ 219
Drive Data view ....................................................................................... 219
Drive Information Operations ............................................................................. 220
Insert/Add a New Drive to a Drive List ........................................................ 220
Delete a Drive from a Drive List ............................................................. 221
Rename a Drive in a Drive List ............................................................... 222
Edit Drive Data ............................................................................................. 223
Cut/Copy/Paste from the Drive List View .................................................... 224
How to Select Drives .................................................................................... 224
Cut a Drive............................................................................................... 225
Copy a Drive ............................................................................................ 225
Paste a Drive ........................................................................................... 226
Save and Save As..................................................................................... 226
Close ............................................................................................................. 227
ONLINE vs. OFFLINE Drive List/Drive Data views .................................. 228
Other Operations in ONLINE Drive List View ............................................ 230
Configuring / Editing / Monitoring a Drive ........................................................ 232
Access Drive Data view from Drive List view ............................................. 232
Content of Drive Data view .......................................................................... 233
Changing Drive Data views .......................................................................... 234
Navigating in the Drive Data view ............................................................... 235
Find Parameter in Drive Data ....................................................................... 237
Search Column......................................................................................... 237
Search Drive Name .................................................................................. 237
Search Parameter Name........................................................................... 237
Copy/Paste Parameters ................................................................................. 238
Copy......................................................................................................... 238
Paste ......................................................................................................... 239
How to Select........................................................................................... 239
Undo .............................................................................................................. 240
Redo .............................................................................................................. 240
Monitoring ONLINE Drive Data .................................................................. 240
Download File Data ...................................................................................... 241
Print Drive Information ................................................................................ 241
TOC-9
Restore Factory Defaults .............................................................................. 243
Output Override ............................................................................................ 243
Override Output ............................................................................................ 244
Toggle Overridden Output....................................................................... 244
Remove an Override ................................................................................ 244
Control Panel / Oscilloscope View ..................................................................... 245
Accessing Control Panel / Oscilloscope view .............................................. 246
Content of Control Panel / Oscilloscope view .............................................. 246
Changing Control Panel / Oscilloscope modes ............................................. 247
Navigating in the Control Panel / Oscilloscope view ................................... 250
Display Control Panel .............................................................................. 250
Display Parameters .................................................................................. 250
Changing the Parameters area.................................................................. 250
File Menu Features ....................................................................................... 251
Save Trace…............................................................................................ 251
Restore Trace… ....................................................................................... 252
Save Scope Template…........................................................................... 252
Recall Scope Template… ........................................................................ 252
Restore Parameters .................................................................................. 253
Print Trace…............................................................................................ 253
Close Oscilloscope................................................................................... 253
Oscilloscope Channel Configuration ............................................................ 253
Oscilloscope Channel Signal ................................................................... 253
Oscilloscope Channel Scale..................................................................... 254
Oscilloscope Channel Offset ................................................................... 254
Oscilloscope Channel Color .................................................................... 254
Oscilloscope Channel Hide...................................................................... 254
Oscilloscope Setup ........................................................................................ 255
Trigger Signal .......................................................................................... 255
Trigger Level ........................................................................................... 255
Trigger Edge ............................................................................................ 255
Trigger Mode ........................................................................................... 255
Buffer Trigger Position ............................................................................ 256
Sample Rate ............................................................................................. 256
Samples per Division ............................................................................... 256
Secondary Scale ....................................................................................... 256
Line Weight ............................................................................................. 256
Control Panel Features .................................................................................. 257
Oscilloscope Group ....................................................................................... 257
Arm Trigger ............................................................................................. 257
Run Continuous ....................................................................................... 257
Stop .......................................................................................................... 257
Trigger State Indicator ............................................................................. 257
Channel Definition ........................................................................................ 258
Drive Status ................................................................................................... 258
Enabled / Disabled ................................................................................... 258
TOC-10
Warning / Fault ........................................................................................ 258
Drive Control ................................................................................................ 258
Enable / Disable ....................................................................................... 258
Set User Fault........................................................................................... 258
Clear Faults .............................................................................................. 258
Start / Stop Motion................................................................................... 259
Alignment Mode ................................................................................................. 259
Overview ....................................................................................................... 259
Accessing Alignment Mode .......................................................................... 260
Parameters in Alignment Mode .................................................................... 261
Changing the Parameters area.................................................................. 261
File Menu Features .................................................................................. 261
Oscilloscope Channel Configuration and Setup ...................................... 261
Control Panel Features............................................................................. 261
Alignment Mode for a Motor with Incremental Encoder ............................. 261
Overview.................................................................................................. 261
Alignment Successful for Motor with an Incremental Encoder .............. 262
Alignment Unsuccessful for Motor with an Incremental Encoder .......... 263
Alignment Mode for a Motor with a Resolver ............................................. 265
Overview.................................................................................................. 265
Alignment Successful for Motor with a Resolver ................................... 265
Alignment Unsuccessful for Motor with a Resolver ............................... 266
Cases When PiCPro Cannot Perform Alignment ......................................... 267
Stegmann Encoder ................................................................................... 267
Motor with alignment mode of Move, Move Minimum, or Hall then Index 267
CHAPTER 5-Custom Motors ................................................................... 269
Overview: Custom Motors .................................................................................. 269

Accessing Custom Motor Setup ......................................................................... 269
Create a New Custom Motor File ................................................................. 269
To Open an Existing Custom Motor File ...................................................... 270
Configuring and Editing a Custom Motor File ................................................... 271
Navigating in the Custom Motor Data View ................................................ 272
How to Select Parameter Values .................................................................. 272
Editing Custom Motor Values ...................................................................... 272
Copying/Pasting Parameter Values .............................................................. 273
Copy......................................................................................................... 273
Paste ......................................................................................................... 273
Undo .............................................................................................................. 273
Redo .............................................................................................................. 274
Loading Default Data from Another Motor .................................................. 274
Restoring Factory Defaults ........................................................................... 275
Saving to a New Custom Motor File .................................................................. 275
Printing Custom Motor Information ................................................................... 276
Deleting a Custom Motor File ............................................................................ 277
TOC-11
Changing the Location of Custom Motor Files .................................................. 278
To Cancel the Location Change of Custom Motor Files ......................... 278
Information Window Messages .......................................................................... 279
CHAPTER 6-Servo Setup and Tuning .................................................... 281
Servo Setup Overview ........................................................................................ 281

Accessing Servo Setup ........................................................................................ 281
Create a New Servo Setup File ..................................................................... 281
To Open an Existing Servo Setup File .......................................................... 282
To Open file from the setup function in your ladder .................................... 283
To Open file from Windows explorer ........................................................... 284
Inserting an Axis in Servo Setup ........................................................................ 284
Servo Axis Limitations ................................................................................. 284
To insert a Servo Axis .................................................................................. 285
Input / Output Types ..................................................................................... 287
D/A Output Setup ......................................................................................... 288
Encoder Input Setup ...................................................................................... 288
Resolver Input Setup (Only for PiC CPU) .................................................... 290
Analog Input Setup (Only for PiC CPU) ...................................................... 290
TTL Input Setup (Only for PiC CPU) .......................................................... 291
SERCOS Setup ............................................................................................. 292
Stepper Setup (Only for PiC CPU) ............................................................... 294
Default axes using Auto Fill (Standalone MMC) ......................................... 295
To insert a Time Axis ................................................................................... 295
Editing a Servo Setup File .................................................................................. 296
Servo / Digitizing Axis Setup Data Categories .................................................. 297
Entering Scaling Data ................................................................................... 298
Entering Iterator Data for Servo Axis ........................................................... 301
Entering S-Curve Data for Servo Axis ......................................................... 305
Entering Iterator Data for Digitizing Axis .................................................... 307
Entering Position Loop Data for Servo Axis ................................................ 307
Time Axis Setup Data Categories ....................................................................... 309
Entering Iterator Data for Time Axis ............................................................ 310
Entering S-Curve Data for Time Axis .......................................................... 311
Importing / Exporting Axis Data ........................................................................ 313
Exporting Axis Data ..................................................................................... 313
Importing Axis Data ..................................................................................... 313
File Format for Servo Data File .................................................................... 314
Data Field Identifiers .................................................................................... 314
Copying Axis Information .................................................................................. 317
Saving a Servo Setup File ................................................................................... 319
Printing Axis Information ................................................................................... 319
Making a Servo Setup Function .......................................................................... 320
Converting a Servo Setup File CPU Type .......................................................... 321
Axis Tuning ........................................................................................................ 322
TOC-12
Axis Tuning using Forcing ........................................................................... 322
Axis Tuning using Viewing .......................................................................... 323
Axis Tuning Variables .................................................................................. 324
CHAPTER 7-PiCPro and SERCOS ......................................................... 325
SERCOS Setup Background Information .......................................................... 325

SERCOS Functions ....................................................................................... 326
Using Standard Motion Functions and Variables ......................................... 327
Using SERCOS Functions/Blocks with TASKS .......................................... 328
SERCOS Telegrams ..................................................................................... 329
IDNs .............................................................................................................. 329
Working with Procedure Command Function IDNs .................................... 330
SERCOS Phases ........................................................................................... 331
Comparing Cyclic Data and Service Channel Transfers .............................. 332
Service Channel Background Information ................................................... 333
Examples of Ladder Design to Access the Service Channel ........................ 333
SERCOS Setup Overview .................................................................................. 336
Replacing Your Analog System with SERCOS ........................................... 336
Using SERCOS Advanced Features ............................................................. 337
Axis Positioning and Referencing in SERCOS ............................................ 338
Opening SERCOS Setup .................................................................................... 339
To create a new SERCOS setup file ............................................................. 339
To open an existing SERCOS setup file ....................................................... 340
To open an existing SERCOS setup file from the setup function in a ladder 340
To open an existing SERCOS setup file from Windows explorer ............... 340
Inserting / Editing SERCOS Rings ..................................................................... 341
Inserting / Editing SERCOS Slaves .................................................................... 342
Edit Startup IDN List .......................................................................................... 344
Inserting / Editing IDNs ...................................................................................... 345
Define Cyclic Data .............................................................................................. 346
Cyclic Data Structures .................................................................................. 348
Define Operation Modes ..................................................................................... 349
Operation Mode Application Note ............................................................... 350
Copying SERCOS Data ...................................................................................... 350
Saving a SERCOS Setup File ............................................................................. 352
Printing SERCOS Setup ..................................................................................... 353
Making a SERCOS Setup Function .................................................................... 353
Upload Drive Information .................................................................................. 355
Changing IDN Data and Uploading IDNs Note ........................................... 356
Converting a SERCOS setup file’s CPU Type ................................................... 357
Copying an SRS structure to the clipboard ......................................................... 358
Battery Box ......................................................................................................... 359
Using the Battery Box ................................................................................... 359
Receive IDNs ...................................................................................................... 361
Receive Continuous IDN Data ........................................................................... 362
TOC-13
Inserting / Editing IDNs for Receive Continuous ......................................... 363
Send IDNs ........................................................................................................... 364
Inserting/Editing IDNs for Send ................................................................... 365
Execute Procedure Command ............................................................................. 366
Ring State ............................................................................................................ 367
Slave Status/Control ........................................................................................... 369
IDN Lists ............................................................................................................. 370
Options for IDN Display ............................................................................... 370
IDN Lists ....................................................................................................... 371
Finding a Specific IDN in an IDN List ......................................................... 372
Printing IDNs from an IDN list .................................................................... 372
Viewing Variable Length Data from an IDN List ........................................ 373
Specifying the SRS for Viewing the Drive IDN List ................................... 373
Troubleshooting SERCOS .................................................................................. 374
Communication Problems........................................................................ 374
Control Problems ..................................................................................... 375
CHAPTER 8-Working With Tasks and UDFBs ....................................... 377
UDFBs ................................................................................................................ 377

Creating a UDFB .......................................................................................... 377
Naming the UDFB ........................................................................................ 378
Scanning UDFB Logic .................................................................................. 378
Contents of the UDFB LDO module ............................................................ 379
Size of UDFB Libraries ................................................................................ 379
Data Handling in UDFBs .............................................................................. 380
Compiling the UDFB .................................................................................... 380
Editing a UDFB ............................................................................................ 380
Viewing a UDFB .......................................................................................... 381
UDFB Software Declarations ............................................................................. 382
Naming the Variables ................................................................................... 382
Order of UDFB Inputs and Outputs .............................................................. 382
Number of UDFB Inputs and Outputs .......................................................... 383
Marking UDFB Inputs and Outputs .............................................................. 383
Tasks ................................................................................................................... 383
Comparing UDFBs and Tasks ...................................................................... 384
Types of Tasks .............................................................................................. 384
Using the Task Template .............................................................................. 385
Errors at the ERR output of the Task ............................................................ 385
Using Functions from the I/O and Motion Libraries .................................... 386
Comparing Declaration Rules for Main and Task LDOs ............................. 387
Creating a Task ................................................................................................... 388
Naming the Task ........................................................................................... 389
Task Hierarchy .............................................................................................. 389
Interlocking Data in Tasks .................................................................................. 392
Setting up Semaphore Flags ......................................................................... 392
TOC-14
Semaphore Flag Example 1 - Data Transfer from Task LDO to Main LDO 392
Semaphore Flag Example 2 - Data Transfer from Main LDO to Task LDO 394
CHAPTER 9- DeviceNet - Ethernet - TCP/IP .......................................... 397
G&L DeviceNet Configuration Software ........................................................... 397

Overview of setting up a DeviceNet Network .............................................. 397
Procedure for using the G&L DeviceNet Configuration Software ............... 398
Ethernet - TCP/IP Configurator .......................................................................... 401
Overview of setting up an Ethernet Network ............................................... 401
Ethernet - TCP/IP Configuration Procedure ................................................. 402
CHAPTER 10- G&L Profibus Configuration Software .......................... 405
Overview of setting up a Profibus Network ................................................. 405

Procedure for using the G&L Profibus Configuration Software .................. 406
APPENDIX A - Quick Reference to In/Out Function Data ..................... 409
Function Input/Output Data Type Reference ...................................................... 409
APPENDIX B - Errors ............................................................................... 415
Function Error Codes .......................................................................................... 415

General Function Errors ................................................................................ 415
I/O Function Block Error Codes ................................................................... 415
String Function Errors .................................................................................. 419
Servo C-Stop, E-Stop, and Programming Error Codes ...................................... 421
Servo C (controlled) - stop errors ................................................................. 422
Servo E (emergency) - stop errors ................................................................ 422
Servo P (programming) - errors .................................................................... 424
Servo Timing Errors ..................................................................................... 426
SERCOS Error Codes ......................................................................................... 426
Ring Errors .................................................................................................... 426
Slave Errors ................................................................................................... 428
Compile Error Messages (Ladder) ...................................................................... 430
Dependency List Error Messages ....................................................................... 433
Library Error Messages ...................................................................................... 433
Hardware Declarations Error Messages .............................................................. 433
Ladder Error Messages ....................................................................................... 438
Fieldbus Error Messages ..................................................................................... 483
Servo Setup Error Messages ............................................................................... 485
SERCOS Error Messages ................................................................................... 497
APPENDIX C - PiCPro Reference Card - Errors/Variables ................... 501
Reference Card ................................................................................................... 501
TOC-15
APPENDIX D - Stepper Reference Card ................................................. 505
Stepper Reference Card ...................................................................................... 505
APPENDIX E - Diagnostic LED Error Codes .......................................... 507
Error Codes ......................................................................................................... 507
APPENDIX F - IBM ASCII Chart ............................................................... 509
ASCII Chart ....................................................................................................... 509
APPENDIX G - Time Axes ........................................................................ 511
Using a Time Axis .............................................................................................. 511

Referencing a Time Axis .............................................................................. 511
Controlling Time Axis Velocity ................................................................... 511
Rollover on Position with a Time Axis ........................................................ 512
Synchronizing Slave Axes with a Time Axis ............................................... 512
APPENDIX H - Stepper Axis Module Notes ............................................ 513
Introduction - Stepper Axis Module ................................................................... 513
APPENDIX I - Toolbar Buttons ................................................................ 515
Servo - Standard Toolbar and SERCOS - Standard Toolbar ............................. 516

Drive List - Standard Toolbar ............................................................................. 517
Custom Motor Toolbar ....................................................................................... 518
Standard Toolbar ................................................................................................. 519
Basic Online Operations Toolbar ..................................................................... 520
Advanced Operations Toolbar ............................................................................ 520
Ladder Toolbar ................................................................................................... 521
View Navigator Toolbar ..................................................................................... 522
Function/Function Block Toolbar ....................................................................... 522
Compiler Toolbar ................................................................................................ 522
Structured Text Tools Toolbar ............................................................................ 523
Insert New Network Toolbar .............................................................................. 524
APPENDIX J - Module Filenames ............................................................ 525
APPENDIX K - Service Pack Installation ................................................ 527
Service Pack Installation ..................................................................................... 527

Service Pack Update Installation - Manual Method ..................................... 527
Service Pack Installation - Automatic Mode ................................................ 530
TOC-16
APPENDIX M - Virtual Axis ...................................................................... 533
Virtual Axis ......................................................................................................... 533
APPENDIX N- Firmware ........................................................................... 535
Firmware ............................................................................................................. 535
APPENDIX O - Things to Consider When Converting an Application from One

CPU Type to Another ............................................................................... 537
Application Note 1 ................................................................................... 539
Reading and Writing STRINGs from a Structure ............................................... 539
TOC-17
TOC-18
CHAPTER 1 Getting Started with PiCPro for Windows
Introduction to PiCPro for Windows
PiC (Programmable Industrial Computer) and MMC (Machine and Motion Con-
trol) systems provide an integrated solution to the logic, motion, process, operator
interface and communications requirements found in today’s industrial automation
applications. PiCPro for Windows Professional Edition and PiCPro for Windows
MMC-Limited edition are the software packages that allow you to program the
PiC or MMC to run your application(s). They include the following programs:
Program Function
Ladder Diagram Allows you to program control logic
in both ladder and structured text and
save it as a .LDO file
Servo Setup Allows you to program setup informa-
tion for your servo application and
save it as a .SRV file
SERCOS Setup Allows you to program setup informa-
tion for your SERCOS application and
save it as a .SRC file
Project Allows you to manage an application
through development and production
phases and then maintain the applica-
tion
Analog Interfaced Allows you to identify, set up and
Drive System monitor the analog interfaced digital
drives used in your application.
If PiCPro is new to you, you will soon discover how easy it is to write your appli-
cation program using the interactive tools available in PiCPro. There are tutorials
on the CD you receive that may be helpful.
If you have used PiCPro in the past, you will see how the new tools and enhanced
features in this Windows version enable you to work more effectively and effi-
ciently in designing your application program(s).
Structured text as used in PiCPro provides powerful data handling such as arrays
and structures that contain different data types. It provides control structures for
the following statements: IF-THEN-ELSE, CASE, FOR, REPEAT and WHILE
loops.
Included on the PiCPro CD are the Function/Function Block Reference Guide, the
PiC900 Hardware Manual, the Standalone MMC Hardware Manual and the MMC
for PC Hardware Manual.
Getting Started with PiCPro for Windows 1

PiCPro for Windows Professional Edition
PiCPro for Windows Professional Edition is the full-featured member of the

PiCPro for Windows product line. It allows you to program PiC controls, MMC
controls and/or analog interfaced drives to run your application(s).
The title bar of the application indicates its edition.
PiCPro for Windows MMC-Limited edition
PiCPro for Windows MMC-Limited edition allows you to program the standalone
MMC control and/or analog interfaced digital drives to run your application(s).
Note: You cannot program an MMC for PC with this edition of software. You
must use the Professional Edition.
PiCPro for Windows Monitor Edition
PiCPro for Windows Monitor Edition is a subset of the PiCPro for Windows Pro-
fessional Edition software. The Monitor Edition allows you to view, print and
monitor the execution of an application program for the PiC/MMC family of con-
trols. It can also perform a PiC Restore.
Generally speaking, you cannot create new files, edit existing files or compile and
download.
However, project files and analog interfaced drive system files can be created and
edited with the Monitor Edition.
The Monitor Edition provides full functionality for the analog interfaced drive sys-
tems. You can identify, configure, setup, monitor and analyze the analog inter-
faced digital drives used in your application. You can create, edit and maintain the
drive files used to save the drive parameters. The Monitor Edition is packaged
with each analog interfaced digital drive shipped from Sheffield Automation.
Customer Services
Sheffield Automation is committed to providing customers with high-quality tech-

nical support. The following sections describe the support services available.
Principal Technical Support Services
North American customers may reach an experienced Sheffield Automation engi-
neer 24 hours a day, every day of the year, by dialing 1-800-558-4808. Over 90%
of all problems are solved via telephone within a few hours.
2 Getting Started with PiCPro for Windows

Hands-on Training Schools
Sheffield Automation offers training schools that provide training with PiC prod-
ucts. Classes are conducted at Sheffield Automation or at your location. Students
will receive thorough orientation and hands-on experience from our qualified
instructors.
Before Calling Technical Support
Before calling Sheffield Automation Technical Support, please have the following
information available. This will assist the Technical Support representative in
helping you more quickly and efficiently.
• A brief description of the problem, including the text and number of any
error messages received and the steps to recreate the problem.
• The type of computer and monitor you are using.
• The version of Microsoft Windows and PiCPro in use. Choose the About
Windows command from the Help menu in Explorer to find which version
of Windows you are running.
World Wide Web Site
The World Wide Web address for Sheffield Automation on the Internet is http://
www.sheffieldautomation.com. At this location you can search, read, print, or
download information and service packs.
The Computer Workstation
The recommended requirements for a workstation are:

For a PiC or Standalone MMC Controller:
Computer 486 or Pentium processor is required with Windows 98, NT4.0, 2000, ME,
Home Edition XP or Professional Edition XP. Windows 2000 and Win-
dows XP require a Pentium processor.
Memory Consult operating system for additional memory needs.
Video 800 x 600 or higher resolution, 16-bit or greater color.
Disk drives Typically, 100 MB of hard disk space is required.
Serial communications port RS232 port (COM1 or COM2) is required.
to controller
For an MMC for PC Controller:
Computer Minimally, 133 MHz Pentium processor with Windows NT4.0, Windows
2000, or Professional Edition XP with PCI network (an ISA network card
is not recommended).
Memory Consult operating system for additional memory needs.
Video 800 x 600 or higher resolution is required, 16-bit or greater color.
Disk drives Typically, 100 MB of hard disk space is required.
Note: Power saver option in BIOS should not be set when using an MMC for PC.
Setting this option will cause a communications error when the computer is shut
down.

Hardware Connections
A cable is supplied with the PiCPro package. One end of the cable is labeled
“PiC900” and the other “Computer”. Connect the “Computer” end to the serial
port you specify in the Online | Comm Settings dialog box and connect the
“PiC900” end to the PiCPro Port on the controller. The pin-out for the controller
serial port is given in the appropriate Hardware Manual. The pin-out for the serial
port should be in the computer’s manual.
Infrared Communications Drivers
If your system has Infrared Communications Drivers, you need to be aware that
under the Windows default settings, COM1 and COM3 use the same interrupts and
COM2 and COM4 use the same interrupts. The communications settings option in
PiCPro for Windows, when checking for valid communications ports, may initiate
execution of some Infrared Drivers. Communications problems will occur if the
Infrared Driver is using one member of the above pairs and PiCPro for Windows is
using the other. To avoid communications problems, do one of the following:
• Disable the Infrared Driver in the control panel
• Change the communications port used by the Infrared Driver so that it does
not conflict with the communications port used by PiCPro.
Installing PiCPro for Windows
PiCPro for Windows is available on CD.

To install from the CD, follow the instructions on the inside jewel case cover of the
CD.
Note: PiCPro V14.0 requires Winsock.dll version 2.2 or higher. Most newer com-
puters or operating system software (such as Windows 2000) use this file. To
determine the Winsock.dll version on the computer that PiCPro V14.0 is installed
on:
1. Right-click on the Start button and select Explore from the menu.
2. Click on the Search button.
3. Select All files and folders.
4. In the All or part of the file name: box, type in winsock.dll.
5. In the Look in: box, select Local Hard Drives (C:); then select More
advanced options and make sure Search subfolders is checked.
6. Right-click the Winsock.dll file(s) that are displayed in the left-hand window.
7. Select Properties and then click the Version tab. The file version number is
shown.
Newer Winsock.dll versions can be located on the Microsoft website.

The Work Area in PiCPro for Windows
When you open a file, its window appears in the work area. This is where you
work on developing a new file or editing an existing file. An information window
appears at the bottom of the work area. You can open multiple files and easily
move between them in the work area.
Title Bar
Menu
Bar
Toolbars
Main
Ladder
Area
Information
Window
The Main Ladder Area

The main ladder area is where you create or edit your LDO file. Usually only part
of your file can be displayed on your screen and you have to scroll up and down or
left and right to bring portions into view.

The Information Window
The information window provides a read-only area that PiCPro uses to display
data pertinent to your application. It is displayed when you open a file and any
time data has been placed in it by a process within PiCPro. The information
remains in the window until it is replaced by data from another process, the file it
pertains to is closed or PiCPro is closed. With certain data (i.e. ladder compiler
error messages), you can go to the location of the error in your file by double click-
ing on the message in the information window.
Other features of the information window include:
• You can undock the information window by dragging it away from the
PiCPro edge it is docked to.
• You can dock the information window by dragging it to any edge within
PiCPro.
• You can resize it vertically or horizontally, but not diagonally.
• You can copy the contents of the information window to the clipboard by
selecting some or all of the text, right-clicking and then selecting Copy.
• You can print the contents of the information window by putting focus in
the window and doing a File | Print from the menu.
• You can hide the information window from view in various ways:
Select View | Information Window from the menu
Press the Esc key
Right-click and select Hide
• To view a hidden information window, choose View | Information Win-
dow from the menu.
Status Bar
The status bar appears at the bottom of the PiCPro screen and provides the follow-
ing information.
1 2 3 4 5 6 7
1. A project is open and the PiCPro version/edition matches the project.

A project is open and the PiCPro version/edition doesn’t match the
project.
2. LDO CFG I/O indicates Ladder Configurable I/O option is enabled.
3. Lists the location of the focus in your ladder. In this case, Network 5, Row 3,
Column 3. A Structured Text Network would appear as STNet:5, R:3, C:3.
4. Indicates connection to control. For Ethernet-TCP/IP communications,
indicates connected; indicates NOT connected. For serial communica-
tions to your workstation, indicates connected to a control; indicates
connected to a drive; indicates disconnected.

5. For Ethernet-TCP/IP communications, this is the IP address of the control.
6. (Not shown above, a blank space) until forcing is turned on. The symbol
will appear in this location when forcing is on.
7. Dynamically updates with the scan time when connected to a control and the
scan is running.
Example 1:
In Example 1, the workstation is connected to a control, but is configured to con-

nect serially. The scan is not running (scan time is 0.00ms) and the focus in the
ladder is in LD Network #3, Row 1, Col 3.
Example 2:
In Example 2, the workstation is connected to a control, but is configured to con-

nect serially. The scan is not running (scan time is 0.00ms) and the focus in the
ladder is in ST Network #2, Row 2, Col 38 and is in Insert mode.
Note: The element can be in either Inserts (Ins) or Overstrike (OVR) mode.
In Insert mode, characters are inserted at the cursor position and ex-
isting characters past the inserted character are pushed to the right.
In Overstrike mode, inserted characters will overwrite any charac-
ters already at that position.
Example 3:
In Example 3, the workstation is connected to a control (configured for Ethernet-

TCP/IP communication), the scan is not running (scan time is 0.00ms) and the
focus in the ladder is in ST Network #1, Row 1, Col 1 and is in Insert mode.
The color of “ST Net” turns yellow as the number of lines in the ST element
reaches the limit of 500 lines.

Status Bar Details
The status bar appears at the bottom of the PiCPro screen and provides the follow-
ing information
Indicator Description
<text at far left> Concise help information relevant to the selected window component.
Indicates a project is open and the PiCPro Version and Edition configured
for the project matches the one currently running. This icon has a green
background.
Indicates a project is open and the PiCPro Version and Edition configured
for the project does NOT match the one currently running. This icon has a
red background.
LDO CFG I/O Indicates the Ladder Configurable I/O status: LDO CFG I/O is displayed
when this option is enabled.
LD Net or ST Identifies the Ladder (LD) network or Structured Text (ST) network, row
Net: , R: , C: and column in the ladder that the cursor is in.
Indicates the workstation is connected to control (configured for Ethernet-
TCP/IP communication). This icon has a green background.
Indicates the workstation is NOT connected to control (configured for

Ethernet-TCP/IP communication). This icon has a red background.
Indicates the workstation is connected to control (configured for serial

communication). This icon has a green background.
Indicates the workstation is NOT connected to control (configured for

serial communication) or drive. This icon has a red background.
Indicates the workstation is connected to an analog interfaced digital

drive (configured for serial communication). This icon has a green back-
ground.
IP: For Ethernet-TCP/IP communication, the IP address of the control.
IP: r This is the same as IP: except that the “r” indicates relay mode
This symbol appears only when forcing is on in the connected control.
0.00ms Dynamically updates with the scan time when connected to a control and
the scan is running.

Displaying/Hiding the Status Bar
You can choose to display or hide the status bar.
• Choose View | Status Bar from the menu. A check mark indicates that the
status bar will be displayed.
• Click on Status Bar again to remove the check mark and hide the status bar.
Window Elements
If you are familiar with Windows, you will recognize basic screen elements com-
mon to most Windows applications. If you are new to Windows, this section will
inform you about some of these elements.
The Title Bar
When you start PiCPro, a Title Bar extends across the top of the window. It dis-
plays the edition of PiCPro you are using, the name of the file you are working in
and indicates whether it is the active window or not. The Title Bar of the active
window is highlighted. The Title Bar of the inactive windows are dimmed.
PiCPro for Windows Title Bar
Where:
Editionname specifies the edition of PiCPro for Windows. The possible
versions are Professional, Monitor and MMC Limited.
You can drag the Title Bar to reposition the window within the work area.
Clicking on the icon on the left end of the Title Bar drops down a menu that allows
you to Restore, Move, Size, Minimize, Maximize, or Close PiCPro.
There are three buttons on the right end of the Title Bar.
Use the first to minimize the window, use the second to maximize the window to
fill the entire screen and use the third to close PiCPro.
The Menu Bar
Directly below the Title Bar is the Menu Bar. It contains the names of the menus
that group together similar commands. Clicking a menu name displays a list of
commands that can be used to access PiCPro functions.
When PiCPro is started, the Menu Bar contains the names shown below.
Once you open a ladder file, the Menu Bar is expanded to include more items
needed to program your ladder.

Dialog Boxes
Dialog boxes can appear when you choose a menu item or a command. A dialog
box presents the list of options available for the selected command and requires
you to type in information or select options that PiCPro requires to proceed.
Typically, you will see some or all of the following in a dialog box.
• OK button
• Cancel button
• Option button
• Check boxes
• Display boxes
• List boxes
• Spin boxes
• Tabs
• Edit fields
• Browse button
When using a dialog box, you can use the question mark button in the top right
corner, to display What’s This? help on a specific dialog component by doing the
following:
1. Click on the button. The cursor changes to a question mark:

2. Click on the component for which you want help.
Help Files
You can access Help files by using the Help menu. There you will have two types
of Help available.
Help Topics offer information on how PiCPro works, error messages and general
help topics.
Function/Function Block Help offers specific help on Functions/Function
Blocks, ASFBs and you can even add your own for UDFBs.
Additional details can be found later in this chapter.

Customizing PiCPro
PiCPro has several features that let you set up your PiCPro work space for the way
you want to work.
You can:
• Set preferences
• Choose animation color
• Customize the toolbars
• Display/hide the status bar
• Choose Structured Text Keyword, Comment, Number and Template colors
Options for user preferences and color can be set under View | Options from the
menu or by pressing the button from the standard toolbar.
Ladder
Under the Ladder tab, you can set the following:
• Software Declarations - Forced Declarations: Whether you want a mes-
sage to appear that tells you to enter a software declaration for the ladder
element you have just added to your ladder.
• Sound - Beep Enabled: Whether you want a beep to sound after certain
actions.
• Confirmations - Confirm Actions: Whether you want a confirmation
message to appear after certain actions.
• Hide:
Symbol Long Name: Whether you want to view long names you have
entered in your program. Note: When you choose to view the long names
all the cells in your ladder are enlarged.
Structured Text F/FB Templates: Whether you want Function/Function
block templates shown when you drop a Function/Function Block into a
Structured Text element.
• Ladder View Preferences - Initial Network Rows: and Network Com-
ment Lines: The number of network rows and the number of comment
lines you want to view in your ladder.
• Cell Width: How wide the cells in the networks appear on your screen.

Start-up
• Automatically reload documents: When you restart PiCPro, whether you
want to reopen any documents (.ldo, .srv, .src) opened using File | Open or
File | New that were still open when you exited PiCPro.
Note: Files that were opened using View | UDFB/Task…, View | Sercos
Function or View | Servo Function will not be reopened.
• Automatically Check for Updates: PiCPro can check for updates, service
packs...prior to startup. When selecting this option, the check for updates
frequency can be configured. See APPENDIX K for the various methods
of Service Pack installations.

Drive Setup
• Location: This is the location where custom motor files will be read from
when PiCPro is started. To change this location, enter a new folder or select
“...” to display the browse dialog. After entering the new location, select
Apply or OK. The custom motor files found in that folder will be read and
Motor Data Status will be reevaluated for any open drive files.
• Refresh: If custom motor files have been added to the custom motor folder
outside of PiCPro while PiCPro is running, select the Refresh button to
force PiCPro to read all files in the custom motor folder. Motor Data Status
will be reevaluated for all open drive files.

Colors
The Animation section shows the colors that will outline power flow when anima-
tion is on. The Running color is used when the control is scanning. The Stopped
color is used when the scan is stopped.
In the Structured Text section, the colors used to display Keywords, Comments,
Numbers and Templates are shown.
As changes are made to each of the ST element types, a sample of Structured Text
code is displayed to preview how the changes will look. The default colors for
Keywords is blue, for Comments green, for Numbers red and for Templates
cyan.
To change a color
1. Choose the Colors tab of the View | Options dialog box.
2. Click on the associated button.
3. Choose a solid color from the Color box that appears.
4. Click OK to save your choices.

Customizing Toolbars
The toolbars give you quick access to some of the frequently used tools. You can
enable or disable toolbars from View | Toolbars under the menu bar.
The type of toolbars available on-screen depends on the type of file opened on-
screen. For example, if an LDO (Ladder) file is open and viewable on-screen and
View | Toolbars is selected from the menu, as many as nine different toolbars are
available. If there is no file open on-screen, only the Standard and Basic Online
Operations toolbars are available. The tools available under each of the toolbars
are listed under each toolbar title in APPENDIX I.
There is a lot of flexibility in displaying and arranging toolbars to fit your needs.
Toolbars can be:
• Arranged within a toolbar region
• Docked horizontally or vertically on any or all four sides of the PiCPro
screen
• Docked inside or outside the PiCPro screen
• Resized
In working with your PiCPro application you will discover which toolbar arrange-
ment works best for you. Your final toolbar arrangement will become the default
until you change it.

Moving Toolbars
When you install PiCPro or when you choose to display a toolbar from the menu,
the toolbars appear at the top of your PiCPro screen under the menu bar in a tool-
bar region. Within this region you can move the toolbars by the drag and drop
method. The toolbars are dockable and can be positioned in a variety of ways.
Note: The toolbar region that holds the toolbars that are displayed along
any of the four sides of your PiCPro screen disappears when all the
toolbars have been docked somewhere else.
Examples of Positioning the Compile Toolbar:
Docked Horizontally Docked Vertically Undocked (Labeled)
Along the top or bottom

of your PiCPro screen Anywhere within the PiCPro
screen or on the desktop
Note: When the toolbar has a
label, it is possible to resize it and
Along the left or right edge close it.
of the PiCPro screen
Docking Tips
•Always click in the dead space around a button to move the toolbar.
• When you want to dock the toolbar vertically, be sure that the edge of the
PiCPro screen is in view. The orientation switches as you cross the edge of
the PiCPro Screen.
Displaying/Hiding Toolbars
You can choose to display or hide any of the toolbars available in PiCPro.
• Choose View | Toolbars from the menu. The Select Toolbars box appears.
Click the box in front of the toolbar name to display it. A check mark
appears in the box.
• Click the box again to remove the check mark and hide the toolbar.
• Click OK to apply the changes and close the Select Toolbars box. Apply
will apply the changes but not close the box and Cancel will close the box
without making any changes.

Organizing PiCPro Files
When you install PiCPro for Windows, the default directory structure is:
C:\Program Files\Giddings & Lewis\PiCPro for Windows Vxx.x editionname Edition
• where Vxx.x is the version number (e.g. V14.0) and editionname is the name of the Edi-
tion (e.g. Professional). Hereafter, this directory is referred to as the PiCPro program
directory.
Subdirectories under the Program Directory:

Libraries - contains the standard function and function block library files.
Firmware - contains hex files.
Personalities - contains personality files.
Organizing directories:
One method of organizing your files when working with PiCPro is to create a
directory structure similar to the following
C:\PiCApplications\project1 to hold a project, keeping it

separated from other projects
C:\PiCApplications\project1\myUDFBs to hold any User Defined
Function Blocks you may
create.
C:\PiCApplications\project1\ASFBs to hold any Application Spe-
cific Function Blocks you
may be using.
To avoid confusion when installing new versions of PiCPro or uninstalling old ver-
sions, it is recommended that you NOT create your directories under the PiCPro
program directory structure (where PiCPro is installed).
PiCPro Libraries
All PiCPro functions and function blocks are stored in libraries. There is a standard
set of libraries that is installed with the PiCPro software. There are also libraries
that can be created by the user to hold user-defined function blocks, set up func-
tions, etc. You can add and remove the paths to these libraries using the dialog box
found under File | PiCPro Libraries.
Note: To be able to compile with a function/function block, whether it’s a standard
one or a user-written one, the path to its library must be configured in the PiCPro
Libraries list of directories. You can access this list directly by selecting File |

PiCPro Libraries from the menu or, if you are using a project, by adding directo-
ries from there.
Library Contents
You may want to view a library’s contents or delete libraries. You may also remove
individual functions from within a library. Deleted libraries and removed functions
are removed from the Function list in PiCPro (Ladder | Functions).
Note: You cannot delete any of the standard PiCPro libraries or functions.
With the PiCPro Libraries dialog box displayed, choose the Contents button.
The Library Contents box appears.
1. In the Directory section, select the desired library path from the drop down
list.

2. The list of libraries in that path will appear on the left in the Libraries (*.Lib)
section. Selecting a library causes the functions included in that library to
appear on the right in the Function/Function Blocks section.
3. To delete the entire library, select the library and choose the Delete Library
button. Note: The library is not deleted until the OK button is clicked.
4. To delete one or more functions from a library, select the function and choose
the Remove Function button. Note: The function is not deleted until the OK
button is clicked.
Note: In the Function/Function Block section, the name of the function/

function block is listed followed by the type (standard, UDFB, SER-
COS, servo, or internal) and the timestamp. The Delete Library and
Remove Function buttons will be grayed if you select a function
that is either a standard or internal (hidden) type or select a library
that contains a standard or internal function.
5. If you want to print a list of all the libraries in the directory along with the
functions in each, choose the Print button. You can also choose to Print to a
File from within the print dialog box.
6. If you want to display the dependencies, if any, for each function/function
block, choose the Dependencies On button. The dependencies will be dis-
played right below the function name entry. With this button on, the dependen-
cies will be included in the print out or print file if you choose to print.
Using On-line Help
The Help documentation includes an on-line Help system, a context-sensitive

(What’s This? system) and Function/Function Block Help system. Some of the
ways you can access the Help system are by choosing it from the Help menu, by
pressing <F1>, or by clicking on the question mark.
Using What's This? Help
The What’s This? system displays context-sensitive information that is relevant to
the component that you click on. The What’s This? help appears in a popup box
with a pale yellow background.
To use What’s This? Help:
1. Click on the button in the top right corner of the dialog box.
2. The cursor changes to:

3. Click on the component that you want information on.
4. What’s This? Help is displayed. It automatically disappears as soon as you
click somewhere else.

Retrieving On-line Help
The on-line Help system enables you to retrieve information you need quickly and
return to your work within PiCPro. The Help appears in a separate window on your
screen. You can keep the Help window displayed on top of your PiCPro applica-
tion for quick access. You can also print Help topics.
Printing On-line Help
When running the on-line Help system, you can print specific topics or print entire
sections from the Contents tab.
To print a specific Help topic
• Click the Print button that appears along the bottom right-side of the Help
window.
or
• While displaying the topic, right-click and select Print Topic
To print an entire section of Help
1. Display the Contents tab of the Help system and select the section you want to
print.
2. Click the Print button that appears along the bottom right-side of the window.
Note: Printing help windows that contain graphics using Windows 98 may pro-
duce unexpected results. The problem does not occur when using Windows NT 4,
Windows 2000, or Windows XP.
Using Function/Function Block Help
This Help system provides information on standard Functions and Function
Blocks and also for ASFBs. You can access this Help for a specific Function or
Function Block in the following ways:
• Click the question mark button and then click on the desired Function/
Function Block in your ladder.
• Right-click on the desired Function/Function Block in your ladder and then
click Help on the popup menu.
You can also start the Function/Function Block Help from the menu: Help | Func-
tion/Function Block

Creating Function/Function Block Help
The Function/Function Block Help system also enables you to write help for your
own UDFBs. Just do the following:
1. Make sure your UDFB’s library is in your library path. (File | PiCPro Librar-
ies)
2. Open the Function/Function Block Help system
3. Right-click on your UDFB in either the Contents list or Index list on the left
side of the help window.
4. Select Edit. At the prompt, choose Yes to create a new file.
5. Proceed with adding any plain text descriptions for your UDFB. The diagram
of inputs and outputs is automatically generated for you based upon the inputs
and outputs you enter in the corresponding tables that are provided. The initial
information provided is based on the information in the library for this UDFB.
6. Choose OK or Cancel. In either case, if you have changed anything, you are
asked whether to save. This is to provide you one last chance at not losing any
edits.
7. When you’re finished, the help system takes your information and generates an
html file named <your library name>.htm and deposits it in the same directory
as your library. Note: If you ever move or copy your library to a new location,
you also need to move or copy its corresponding .htm file. All of the UDFBs
for a specific library are documented in that library’s one .htm file. The more
UDFBs you have in a library, the bigger the .htm file and the longer it takes to
load when you want to view or edit it.
8. Once you’ve created help for your UDFBs, you can access it exactly the same
way that you access the standard Function/Function Block Help.
Note: The help files for the standard libraries and the ASFB libraries are
not .htm files, but rather .chm files. These are compiled html files.
The same rule applies regarding their location and naming. They are
named to match their corresponding library: <library name>.chm.
Example: arith.chm goes with arith.lib. Both files must exist in the
same directory, so if you’re moving your libraries around, move
their help files with them.

Starting PiCPro
Once you start PiCPro, you’ll be able to create and develop your various applica-
tion files.
With PiCPro running, you can easily switch between PiCPro programs (Ladder
Diagram, Servo Setup, SERCOS Setup and Analog Interfaced Drive System). You
can go back and forth between programs without exiting one and launching the
other.
To begin working in PiCPro, start the PiCPro application.
To start PiCPro
1. Click the Start button in the Windows task bar.
2. Click the PiCPro for Windows entry in Programs.
3. Click the desired version and edition of PiCPro.
Or double-click the PiCPro for Windows desktop icon provided during installa-
tion.

CHAPTER 2 Working with Projects
Overview: Using Projects
A project is a tool to help you manage your applications. A project consists of a

project file (.prj) and, optionally, a compressed project file (.g&l). A project file
contains descriptions of all the files (and their paths) that you have determined
encompass your project. A compressed project file actually contains, in com-
pressed format, a copy of all of the files described by name in the project file.
PiCPro for Windows enables you to create, edit, compress, or print the project file
as required. There is only one project described in a project file.
Once the files in the project have been defined in the project file, you can work on
the development of your application using the tools found in PiCPro. A com-
pressed file (.g&l) containing all the files identified in the project file can be cre-
ated. This file can be stored on the workstation or on the FMSDISK on the control.
Note: Use the DOS 8.3 format naming convention (8 characters, period, 3 charac-
ters) for compressed project files if you will be saving those on FMSDISK.
A project can play a role in simplifying your control maintenance. You can main-
tain the control by using a workstation with only the PiC programming tools
installed. All the files required for your application can be stored in the PiC on the
FMSDISK. When you open a project from the FMSDISK, the compressed file is
loaded onto the workstation. The compressed file is expanded onto your worksta-
tion according to the options you select. You can then use the software tools to
maintain the project and then compress back to the FMSDISK (or even the work-
station).
A summary of the capabilities of project maintenance using PiCPro for Windows
is listed below:
Allows you to control the development of a project in a development, pro-
•
duction, and archive version.
• Allows you to work with multiple versions of PiCPro.
• Simplifies creating a single disk containing all the files required for an
application.
• Provides the tools needed to store a single compressed file containing all
the files required for an application on the FMSDISK in the control.
• Allows you to update the FMSDISK on the control without stopping the
scan.
Menu Commands that Manage Projects
The following is a list of commands from the menu bar that enable you to manage
your projects.
File | New – creates a new project tree. This project tree consists of various catego-
ries. To develop your project, you must add file definitions or other information to
the applicable categories. Note: A project tree and a project file represent the same
data; a project tree is the graphical representation of the project characteristics and
file definitions in the opened project file.
Working with Projects 23
File | Open – Opens an existing project. You can open a project file (.prj) or a
compressed project file (.g&l). Opening a compressed project file uncompresses
its contents to locations in your workstation according to the options you select.
Once open, you can edit, print, and compress a project file. The contents of an
open project file is presented to you graphically as a project tree.
File | Open From Control - Opens a compressed project file on the control’s
FMSDISK.
File | Print – Prints the contents of an open project file.
File | Save As – Copies existing files defined in your project file to different direc-
tories according to your specifications and creates a new project file containing
those new file definitions. After a Save As, the new saved-as project is the one that
is left open.
File | Compress – Compresses the files defined by name in your project file into a
single compressed project file (.g&l) and stores it on the control’s FMSDISK, on
the workstation’s hard disk or mapped network drive according to your specifica-
tions. Note: Use the DOS 8.3 format naming convention for compressed project
files if you will be saving those on FMSDISK.
File | Launch Project - Launches the version and edition of PiCPro for Windows
as defined in the PiCPro VERSION category in the project tree.
File | Update Project Tree - Updates the project tree file definitions based upon
the file dependencies found in the main .LDO in the project. Update removes all
items in the UDFBs/TASKs, SERVO SETUP FILES, SERCOS SETUP FILES
and PROFILE SETUP FILES categories and adds file definitions based upon the
determined dependencies AND the project’s properties. If you manually add file
definitions to any of these 4 categories, they could be lost on an update.
File | Validate Project Tree - Validates the project tree by verifying that all files
and paths defined in the tree exist. If not found, the icon next to the file or path def-
inition is altered to have a red circle with a diagonal slash through it.
Edit | Add - Enables you to add an item to a selected category such as LIBRARY
PATHS or UDFBs/TASKs. Refer to the specific category or item description for
information on the results because they depend upon which category or which item
is selected.
Edit | Delete - Enables you to delete all items of a selected category or if an actual
item is selected, enables you to delete that item from its category. Refer to the spe-
cific category or item description for information on the results because they
depend upon which category or which item is selected.
Edit | Cut - Cuts the selected item from its category and places it on the clipboard.
Refer to the specific category or item description for information on the results
because they depend upon which category or which item is selected.
Edit | Copy - Copies the selected item or category of items to the clipboard. Refer
to the specific category or item description for information on the results because
they depend upon which category or which item is selected.
24 Working with Projects

Edit | Paste - Pastes the contents of the clipboard into the selected category. Refer
to the specific category or item description for information on the results because
they depend upon which category or which item is selected.
The Project Tree and Its Components
A project tree is the graphical representation of the information configured in the
project file. The project tree is displayed when you open a project file. It consists
of several categories that are made up of items that describe different characteris-
tics of the project or describe files and file locations that belong to the project.
You can see the items in a category by expanding the category. Do this by clicking
on the symbol to the left of the category name. If the symbol is a , click on
it to collapse the category. You can also double click on the category name itself to
toggle between expanded and collapsed. If neither symbol is displayed, no items
are currently configured in that category.
Select a category or item in a category by single clicking on it. When selected, the
category name or item is selected. Once highlighted, you can use menu commands
to manipulate an item or category or right-click and use those menu items.

Project Tree Categories
Category: PROJECT NAME

The PROJECT NAME category defines the name of the project file. Its format is
<projectname>.PRJ where <projectname> is whatever name you choose for this
particular project. The path (or location) for the project file is also displayed with
the name.
If you right-click on the PROJECT NAME category, a popup menu is displayed
with the following menu selections:
Popup Menu
Description
Selection
Compress Allows you to compress the project file. This is the same as the com-
mand selected from File on the menu.
Print Allows you to print the information in the project tree. This is the same
as the command selected from File on the menu.
Launch Allows you to start up the edition/version of PiCPro configured in the
Project project if it is installed on your workstation. This is the same as the com-
mand selected from File on the menu.
Update Allows you to automatically update the entire project tree based upon
Project Tree dependency information. This is the same as the command selected from
File on the menu.
Validate Allows you to validate the contents of the tree categories. This is the
Project Tree same as the command selected from File on the menu.

Popup Menu
Description
Selection
Properties Enables you to change the properties for this project.
Update Project Tree Options:

If you want to include all of the sources (all .LIB, .LDO, .SRV, .SRC,
.PRO files) for all of the files found in the paths configured in the PiCPro
LIBRARY PATHS category, then check the top option. This is the
default option.
Otherwise choose Include only sources for functions used. This means
that when you select Update Project Tree, only those sources for the
actual functions used will be configured in the project file. This will
result in a smaller compressed project file (should you choose to com-
press your project). Be aware, however, that this could limit future devel-
opment or alteration of the project if working from the compressed
project file. For example, lets say that you only have the compressed
project file available and a problem occurs. And you want to include a
new-to-this-project ASFB in your ladder to help diagnose the problem.
The source for that ASFB won’t be in the compressed project file and
you may or may not be able to find it elsewhere.
Operator Interface Settings:
Your project automatically inherits the current Operator Interface Set-
tings. You can change these settings by pressing the Edit Operator
Interface Settings button or by using the Compile | Settings dialog.
Both methods display the same dialog.

Popup Menu
Description
Selection
Properties Compress Options
(Continued) When checked, help files associated with a project’s libraries will auto-
matically be included when the project is compressed. Help files include
files with .chm and .htm extensions.
Note: Projects created prior to V13.0 and opened in V13.0 will have this
option de-selected by default. Projects created in V13.0 and later will
have this option selected by default. Projects created in V13.0 and
opened in V11.0 will have the checkbox marked, but it will have no
effect on projects compressed in V11.0. Help files will not be included.
Category: MAIN.LDO
The MAIN .LDO category can contain one item. This is the main .LDO file (lad-
der file) for this project.
If you right-click on the MAIN .LDO category, a popup menu is displayed with the
following menu selections:
Popup Menu
Description
Selection
Add Enables you to add a main ladder file to your project. This
option is only enabled if a main ladder file is NOT already
specified.
Delete All Enables you to delete all of the items belonging to this cat-
egory. In this case, that is only one: the main ladder file.
Note: the actual file is not deleted; just the entry in the
project tree is deleted. You are prompted for a confirma-
tion first.
Cut Cuts (removes) the main ladder file item from this cate-
gory and places it on the clipboard.
Copy Copies the main ladder file item from this category to the
clipboard.
Paste Pastes the contents of the clipboard into the MAIN .LDO
category. This command is only available if there is not
already a main ladder file item entered for this category
and if the clipboard contains a main .ldo file item.
Update Not enabled for this category.
Project
Items under
this Cate-
gory
Item: MAIN.LDO
If you right-click on an item (the main ldo file) in the MAIN .LDO category, a
popup menu is displayed with the following menu selections:
Popup Menu
Description
Selection
Open Opens the main ladder file. If this ladder is already open, it
makes it the active window. You can also open this file by
double clicking on it.
Delete Removes this item, the main ladder file, from this cate-
gory. You are prompted for a confirmation first.
Edit Allows you to manually edit this item’s name and path by
typing in the new information.
Cut Removes this item, the main ladder file, from this cate-
gory.
Copy Copies this item to the clipboard.
Paste Pastes a main ladder file into this category. This is only
available if a main ladder file item is on the clipboard. This
overwrites the selected main ladder file item.
Category: COMPRESSED FILE

The COMPRESSED FILE category contains a file description for this project’s
compressed project file, if it has one. (Note: Use the DOS 8.3 format naming con-
vention for compressed project files if you will be saving those on FMSDISK.)
The compressed file contains the project’s characteristics like version and proper-
ties. It also physically contains, in a compressed format, a copy of all of the files
described by name in the project along with their supporting files if any exist:
• .REM - comment file for an .LDO file (main ladder, UDFB, etc.)
• .FRC - force list file for an .LDO file (main ladder, UDFB, etc.)
• .RTD - view list file for an .LDO file (main ladder, UDFB, etc.)
• .SVT - force/view (tuning) information for an .SRV file (servo setup file)
• .SCT - force/view (tuning) information for an .SRC file (SERCOS setup
file)
These support files do not show up in the tree, but are the “behind-the-scenes” files
that are necessary to support the usage and customization of the .LDO, .SRV, and
.SRC files that are named in your tree.
If no file is configured in the COMPRESSED FILE category, you will not be
prompted to do a compress when you do things like edit and then save and close a

project file. But if there is a compressed file specified, you will be prompted to
update the compressed file with the changes you’ve made (i.e. compress the
project again.). During your project’s development process, it may be useful for
you to postpone specifying a compressed file until closer to completion in order to
avoid all of the prompts to compress.
If you right-click on the COMPRESSED FILE category, a popup menu is dis-
played with the following menu selections:
Popup Menu
Description
Selection
Add Enables you to add a compressed project file item to your
project. This option is only enabled if a compressed project
file is NOT already specified.
egory. In this case, that is only one: the compressed project
file item. Note: the actual file is not deleted; just the entry
in the project tree is deleted. You are prompted for a con-
firmation first.
Cut Cuts (removes) the compressed project file item from this
category and places it on the clipboard.
Copy Copies the compressed project file item from this category
to the clipboard.
Paste Pastes the contents of the clipboard into the COM-
PRESSED FILE category. This command is only available
if there is not already a compressed project file item
entered for this category and if the clipboard contains a
compressed project file item.
Project
Items under
this Cate-
gory

Item: COMPRESSED FILE
If you right-click on an item (the compressed project file) in the COMPRESSED
FILE category, a popup menu is displayed with the following menu selections:
Popup Menu
Description
Selection
Open Not enabled for this category. Instead, to open a com-
pressed file, use File | Open and select a compressed
project. This will close the currently open project and
uncompress the selected compressed project according to
your specifications.
Delete Removes this item, the compressed project file, from this
category. You are prompted for a confirmation first.
Edit Enables you to edit the compressed project file item, not
the compressed project file itself. You may type in a new
path and/or compressed project file name.
Cut Removes this item, the compressed project file, from this
category.
Paste Pastes a compressed project file into this category. This is
only available if a compressed project file item is on the
clipboard. This overwrites the selected compressed project
file item.
Category: PiCPro VERSION

The PiCPro VERSION contains an item that specifies which version and edition
this project is built for. If you open a project in a version or edition other than what
is specified in its VERSION category, then you will not be able to compile and
download the main ladder or any other ladder. In addition, you will not be able to
compile servo or SERCOS functions. You must Launch the correct version to do
so (File | Launch Project). Of course, you can only launch a particular version/
edition of PiCPro if it is actually installed on your workstation.
If you right-click on the PiCPro VERSION category, a popup menu is displayed

Popup Menu
Description
Selection
Add Enables you to add a PiCPro version/edition item to your
project by displaying the PiCPro Version Selection dia-
log. This dialog allows you choose both the edition and
version of PiCPro that you want associated with this
project. This option is only enabled if a PiCPro version/
edition is NOT already specified.
In this example, the edition that is chosen is the Profes-

sional Edition and the version is 14.0.
egory. In this case, that is only one: the PiCPro version/
edition item. You are prompted for a confirmation first.
Cut Cuts (removes) the PiCPro version/edition item from this
category and places it on the clipboard.
Copy Copies the PiCPro version/edition item from this category
to the clipboard.
Paste Pastes the contents of the clipboard into the PiCPro VER-
SION category. This command is only available if there is
not already a version item entered for this category and if
the clipboard contains a PiCPro version item.
Project
Items under
this
Category

Item: PiCPro VERSION
If you right-click on an item (PiCPro version/edition) in the PiCPro VERSION
category, a popup menu is displayed with the following menu selections:
Popup Menu
Description
Selection
Open Not enabled for this category.
Delete Removes this item, the PiCPro version/edition, from this
category. You are prompted for a confirmation first.
Edit Enables you to edit the PiCPro version/edition by display-
ing the PiCPro Version Selection dialog. You can choose
the edition and the version of PiCPro that you want associ-
ated with this project.
In this example, the edition that is chosen is the Profes-

sional Edition and the version is 14.0.
Cut Cuts (removes) this item, the PiCPro version/edition, from
this category.
Paste Pastes a PiCPro version item into this category. This is
only available if a PiCPro version item is on the clipboard.
This overwrites the selected PiCPro version item.

Category: PiCPro LIBRARY PATHS
This category contains all of the paths for all of the libraries that your project uses.
You can edit this list by right clicking on the category or an actual item in the cate-
gory and selecting Modify. The PiCPro Libraries dialog is displayed. Alterna-
tively, you can select File | PiCPro Libraries while a project is open. Any changes
made to the library path list there, will be reflected in the PiCPro LIBRARIES
PATHS category of the open project.
If you right-click on the PiCPro LIBRARY PATHS category, a popup menu is dis-
Popup Menu
Description
Selection
Modify Allows you to add or remove library paths in this category.
Displays the same dialog that you get when you select
File | PiCPro Libraries.
Delete All Deletes all of the libraries paths under this category. You
are prompted for a confirmation first.
Cut Cuts (removes) all of the library paths from this category
and places them on the clipboard. A library path on the
clipboard can be pasted into the PiCPro LIBRARY PATHS
category if it does not already exist there. Note: if you do a
cut on this category, you’ll get a warning message stating
that PiCPro couldn’t find any library paths. Just click OK.
Remember, you will need to add some library paths back
in sometime.
Copy Copies all of the library paths in this category and places
them on the clipboard. A library path on the clipboard can
be pasted into the PiCPro LIBRARY PATHS category if it
does not already exist there.
Paste If the clipboard contains library paths, this pastes the con-
tents of the clipboard into this category. If a matching path
already exists there, a duplicate one is not added. This
menu selection is only available if the clipboard contains
library paths.

Item: PiCPro LIBRARY PATHS
If you right-click on an item (a library path) in the PiCPro LIBRARY PATHS cate-
gory, a popup menu is displayed with the following menu selections:
Popup Menu
Description
Selection
Edit Allows you to manually edit the library path by typing in
the new information.
Modify Allows you to add or remove libraries paths in this cate-
gory. Displays the same dialog that you get when you
select File | PiCPro Libraries.
Delete Deletes the selected library path from the list. You are
prompted for a confirmation first.
Cut Cuts (removes) the selected library path from the list and
places it on the clipboard.
Copy Copies the selected library path from the list and places it
on the clipboard.
Paste Pastes the contents of the clipboard into this category,
replacing the selected item. This menu selection is only
available if the clipboard contains library path items.

Source and Library File Categories
These categories list the source files and the libraries for your projects. These cate-
gories are updated by Update Project Tree and Update Items in this Category. If
you manually change the contents of these categories, performing an update will
potentially lose those changes. Update first removes all items from a category and
then based on dependencies and the Properties settings for the project, adds items
back in.
The following are Source and Library File Categories for your project:
Source and Library File Source File

Category Description
Category Extension
UDFBs/TASKs .ldo Typically contains entries for the library
files (.lib) for the tasks and function blocks
for this project. Also contains entries for
their corresponding source files (.ldo).
SERVO SETUP FILES .srv Typically contains entries for the library
files (.lib) for the Servo Setup functions for
this project. Also contains entries for their
corresponding source files (.srv).
SERCOS SETUP FILES .src Typically contains entries for the library
files (.lib) for the SERCOS Setup functions
their corresponding source files (.src).
PROFILE SETUP FILES .pro Typically contains entries for the library
files (.lib) for the Profile Setup functions
their corresponding source files (.pro).

Category: Source and Library Files
If you right-click on one of these categories, a popup menu is displayed with the
following menu selections:
Popup Menu
Description
Selection
Add Allows you to manually add libraries files (.lib) and source
files to the selected category. WARNING: any manual
changes to this category could be lost if you perform an
Update Project Tree or Update Project Items under this
Category. To add files where they won’t automatically be
removed on an update, add them to the OTHER FILES
category.
Delete All Deletes all of the items in the selected category. You are
prompted to confirm this first.
Cut Cuts (removes) all of the items from this category and
places them on the clipboard.
Copy Copies all of the items in this category and places them on
the clipboard.
Paste Pastes all of the items in the clipboard into the selected cat-
egory. This menu selection is only available if the sources
and/or library items on the clipboard are compatible with
the selected category.
Update Performs the Update Project Tree operation on just this
Project category of the tree, leaving all of the other categories
Items under untouched. All items in the category are removed and new
this Cate- entries are added based on the configured properties for
gory this project. The properties determines whether all sources
and libraries in your configured paths are added or only
those that are used.

Item: Source and Library Files
If you right-click on an item in one of these categories, a popup menu is displayed
Popup Menu
Description
Selection
Open Opens the selected source file in the appropriate PiCPro
editor. This menu selection is not available if a library is
selected. Note: This command is equivalent to File |
Open. It is not the same as View | UDFB/Task, View |
Servo Function or View | SERCOS Function. You will
not be able to animate the file if it is a UDFB/Task, Servo
function, or SERCOS function.
Delete Deletes the selected item from its category. The entry for
this file is removed from the project; the file itself is not
removed from disk. You are prompted for a confirmation
first.
Edit Allows you to manually edit this item’s name and path by
typing in the new information.
Cut Cuts (removes) the selected item from its category and
Copy Copies the selected item and places it on the clipboard.
Paste Pastes the contents of the clipboard into the selected item’s
category, overwriting the selected item. The types of items
on the clipboard must be compatible with this category,
otherwise this menu selection is disabled.

Category: OTHER FILES
The OTHER FILES category provides you with the opportunity to include any
type of files that you want to in your project. Perhaps you have a text file or
spreadsheet with relevant notes or data. Or maybe you have some analog inter-
faced drive system files (*.adv). Or maybe you have some alternative UDFBs you
want included but you’re not using yet. Or maybe its important to you to have the
online help files for the UDFBs or ASFBs available. Or maybe you would like to
include the Drive IDN files associated with your SERCOS functions. You can
include them all here and, unlike files entered in the UDFBs/TASKs, SERVO,
SERCOS, and PROFILE categories, the Update Project Tree command will
leave them alone.
If you right-click on the OTHER FILES category, a popup menu is displayed with
the following menu selections:
Popup Menu
Description
Item
Add Enables you to add any type of file to this category.
egory. You are prompted for a confirmation first.
Cut Cuts (removes) all of the items belonging to this category
and places them on the clipboard.
Copy Copies all of the items in this category to the clipboard.
Paste Pastes the contents of the clipboard into this category. This
command is enabled only if the clipboard contains
OTHER FILES items.
Project
Items under
this Cate-
gory

Item: OTHER FILES
If you right-click on an item in the OTHER FILES category, a popup menu is dis-
Popup Menu
Description
Item
Open If the selected file is a PiCPro source file, that file is
opened in the appropriate PiCPro editor. Otherwise, this
menu selection is not enabled.
Delete Deletes the selected item from this category. You are
prompted for a confirmation first.
Edit Enables you to manually edit the name and location of the
selected item.
Cut Cuts (removes) the selected item from this category and
Copy Copies the selected item in this category to the clipboard.
Paste Pastes the contents of the clipboard into this category,
overwriting the selected item. This command is enabled
only if the clipboard contains OTHER FILES items.
Creating a New Project
To create a new project:

1. Select File | New from the menu. The New dialog box is displayed.
Note: If you are running PiCPro for Windows Monitor Edition, you will not be
prompted with the New dialog box. Instead, if another project is open, you are
prompted to close it, and then a new project tree is immediately created and dis-
played for you.
Note: In any of the PiCPro editions, if you already have a project open, you are
prompted to close it. You can only have one project open at a time.
2. Choose Project from the list.

Note: The Target CPU choice is immaterial here and all choices are disabled. CPU
type is not a characteristic of the project file itself; it is a characteristic of the
source files configured in the project.
3. Click on OK.
4. A project tree is created and displayed for you.
5. Modify the project as desired.
6. Select File | Save to save the project file. The file name you enter becomes the
name of the project.
When a new project tree is displayed, all of the categories exist in the tree, but not
all have default values.
• PROJECT NAME - No default. Specified when you save the project (File |
Save).
• MAIN .LDO - If you have a ladder open and the ladder has focus when you
create this new project, this category defaults to the name and location of
the open ladder.
• COMPRESSED FILE - If you have a ladder open when you create this
new project, the file item in this category defaults to <open ladder name
and location>.g&l.
• PiCPro VERSION - Defaults to the edition and version of PiCPro that you
are currently running.
• PiCPro LIBRARY PATHS - defaults to the library path list that is config-
ured for the edition/version of PiCPro that you are running.
• UDFBs/TASKs - If you have a ladder open and the ladder has focus when
you create this new project, this category defaults to include all of the
dependencies for that ladder based on the project’s properties, which
default to ALL files in Library Paths, even if not used.
• SERVO SETUP FILES - If you have a ladder open when you create this
new project, this category defaults to include all of the dependencies for
that ladder based on the project’s properties, which default to ALL files in
Library Paths, even if not used.
• SERCOS SETUP FILES - If you have a ladder open when you create this
new project, this category defaults to include all of the dependencies for
that ladder based on the project’s properties, which default to ALL files in
Library Paths, even if not used.
• PROFILE SETUP FILES - No defaults.
• OTHER FILES - No defaults.
If a ladder file is not opened and/or the ladder file does not have focus, the New
Project dialog box will open with two defaults entered, the PiCPro VERSION and
the PiCPro LIBRARY PATHs. All other entry fields will be blank.
You can modify or add to these defaults as applicable. Remember that any modifi-
cations made to the UDFBs/TASKs, SERVO SETUP FILES, or SERCOS SETUP
FILES categories will be lost if you do an Update Project Tree. The OTHER

FILES category allows you to enter additional files you want to include in the
project and is not altered by an update.
Opening an Existing Project
A project is opened by using the File | Open command from the menu. There are
two types of project files that can be opened:
1. PiCPro for Windows project file (.PRJ or .prj).
2. PiCPro for Windows compressed project file (.G&L or .g&l).
You can also open any of these from the FMSDISK, if you have one, on the con-
trol.

Opening a Project File (.PRJ)
If you want to open an existing PiCPro for Windows project file:
1. Selecting File | Open from the menu. Then the Open dialog box is displayed.
2. In the Files of type edit box, select Project Files (.prj,.g&l)
3. Browse to the desired project file.
4. Select the project file that you want to open
5. Click the Open button.
6. If any other project is open, you are prompted to close it because only one
project can be open at a time.
Note: if the version and edition of PiCPro that is configured in the project is differ-
ent than the version and edition you are currently running, you will be warned of
this and can either continue opening the project or not. On the status bar, an icon
with a red background indicates that the editions/versions don’t match: . This
indicates that to have full functionality, you should launch the correct edition/ver-
sion of PiCPro for Windows (File | Launch). An icon with a green background
indicates that a project is open and that the editions/versions match:
7. The project is now open for editing and if found, the main ladder file of the
project is opened, also.
Alternatively, if the desired project has been recently open, you might find it in the
“most recently used list” located near the bottom section of the File menu. Just
select the entry that you want.

Opening a Compressed Project File (.G&L)
A PiCPro for Windows compressed project file that is stored on your workstation
or on the FMSDISK on your control can be uncompressed by opening it:
1. Select File | Open from the menu. Make sure the file type at the bottom of the
dialog is set to “Project Files (.prj,.g&l)”. Browse to the compressed project
file (.G&L) that you want to open and select it and click on Open.
2. Alternatively, if the compressed project file is on the FMSDISK on your con-
trol, select File | Open From Control instead. A list of compressed files on the
control’s FMSDISK is displayed to you. Realistically, there should only be one
there. Select the file by clicking on it and then click OK. The file is then copied
to a temporary directory on your workstation before the Uncompress Project
dialog is displayed to you.
3. If any other project is open, you are prompted to close it because only one
project can be open at a time.

4. The Uncompress Project dialog is displayed.
5. Choose the locations you want to uncompress to:

• Drives Specified in Project - this option uncompresses all of the files in
the compressed project file into the exact locations (drive and directory
paths) that were specified in the project when the compressed file was
made.
• Different Drive - this option uncompresses all of the files in the com-
pressed project file into the directory location specified in the original
project file, BUT substitutes the drive with the one you select here.
• A single directory - this option uncompresses all of the files in the com-
pressed project file into a single drive and directory location. Use the but-
ton to the right to browse to the desired location or manually type in the
desired location.
6. The project name will default to the uncompressed project file name with a
.PRJ extension instead. You can modify the name and path.
7. If you have chosen an Uncompress To: option other than Drives Specified in
Project, selecting the Modify Project File when ‘Uncompress to’ is changed
will generate the new project file with file entries whose locations match your
Uncompress To: choice. Exception: The drive and location of standard librar-
ies in the LIBRARY PATHS is not altered.
8. Click OK.
Note: if the version and edition of PiCPro that is configured in the project is differ-
ent than the version and edition you are currently running, you will be warned of
this and can either continue opening the project or not. On the status bar, an icon
with a red background indicates that the editions/versions don’t match: . This
indicates that to have full functionality, you should launch the correct edition/ver-

sion of PiCPro for Windows (File | Launch). An icon with a green background
indicates that a project is open and that the editions/versions match:
9. When done, a message saying “Uncompress project is complete” appears. All
files have then been uncompressed to the location(s) you specified and the
specified project file has been created according to your specifications and is
opened for editing.
Compressing a Project
When you create a project using PiCPro for Windows, you create a project file.
This file has entries that describe the name and location of the various source files
and library files and others that constitute your project. The actual files are not a
part of the project file. However, if you compress your project, a compressed
project file is created. This file physically contains, in compressed format, a copy
of all of the files described by name (plus their supporting files) in the project file.
You can now easily distribute your project as a single file or deposit it on an appro-
priate control’s FMSDISK.
Note: Compressed project files do not include the standard libraries.
To compress a project file:
1. Open or create a project.
2. Make sure a compressed project file name is configured in the COMPRESSED
FILE category of the project.
3. Select File | Compress or right-click on PROJECT NAME category and select
Compress
4. The project is automatically Validated. This checks that the files that are refer-
enced in the project tree actually exist in the configured location. It does not
validate the compressed project file or verify the PiCPro edition/version.
5. You are also prompted to save your project if it has changed. You must save it
to continue with the compress.
6. You are asked whether or not to Update your project. Updating checks the
dependencies for the files in your project and automatically includes source
and library files according to the properties selected for this project. Remember
that entries for files that were manually added to the UDFBs/TASKs, SERVO
SETUP FILES, and SERCOS SETUP FILES could be lost if other files are not
dependent on them.
7. The Select Compress Destination dialog is displayed. Your choices for desti-
nation are the workstation or the FMSDISK, if you have one. If you select the
workstation, the location for the compressed project file is exactly what you
had configured in the project file. However, if you select FMSDISK, the loca-
tion for the compressed project file is FMSDISK:\. (Note: you cannot edit the
destination from here, only from the COMPRESSED FILE category in the
project tree.)
8. Click OK.

Destination if FMSDISK is selected.
Note: Even if you compress to your workstation, you can copy the compressed
project file to the FMSDISK on your control by using Online | Disk Operations |
Flash. Remember that depositing any file(s) to FMSDISK completely removes
anything that was already there. You do get a prompt warning you of this, allowing
you to Cancel, if desired.
Launching a Project
At times, you may open a project that is configured with a version and edition of
PiCPro for Windows that is different than the version and edition you are currently
running. In these cases, you are warned of this and can either continue opening the
project or not. If you choose to continue the open, the status bar will display an
icon with a red background that indicates the edition/version mismatch: . If no
mismatch, this icon is displayed in green: .
If you have a red (version mismatch) icon displayed, PiCPro for Windows pro-
vides a mechanism for you to automatically reopen your project in the correct edi-
tion/version of PiCPro for Windows (provided it is installed on your workstation).
• Select File | Launch Project
OR
• Right-click on the PROJECT NAME category of the project tree and select
Launch Project.
The Launch Project feature first checks to see if the configured edition/version of
PiCPro for Windows is installed on you workstation. If it isn’t, a message is dis-
played and the launch is canceled. Otherwise, the currently running PiCPro is
closed, the configured one is opened and the project is also automatically opened.
Note: It is important to be running the same edition/version of PiCPro for Win-
dows as is configured in the project if you need to edit and download any changes
to the control. To avoid unexpected results, a particular edition/version of PiCPro
for Windows should only be used with the libraries distributed with it. For exam-
ple, if a project called for PiCPro for Windows 10.2 Standalone MMC Edition and
you are currently running PiCPro for Windows 11.0 Professional Edition a version
mismatch occurs. In fact, if your editions/versions mismatch, the Compile and
Download feature will report the mismatch to you and will then cancel.
Printing a Project
To print the contents of a project file:

1. Open the desired project file.
2. Once the project is open, select File | Print from the menu or click the
button
3. The standard Print dialog box is displayed.
4. Make appropriate changes for printer properties, etc. if needed.
5. Click OK.
Copying a Project (Save As)
The Save As command allows you to copy all of the files that make up an entire
project to new locations. Here you have total control over where each different file
type and directory combination will be copied to for the new project.

The Save As Project feature can be useful as a tool to help you move your project
from development directories to production directories.
Source PRJ
This is the name and location of the project you are making a copy of. You cannot
alter this field.
Destination PRJ
Fill in the name and location for the new project file. The name and/or location is
usually different than the Source PRJ name. You can use the button to the right of
this field to browse to the location you want and then type in the new name. In the
new project, this will be entered into the PROJECT NAME category.
Destination G&L
Fill in the name and location for the new compressed project file. The name can be
different than what is configured in the Source PRJ project file, although that is
what it defaults to. In the new project, this will be entered into the COMPRESSED
FILE category.
PiCPro Version
Enter the edition/version for the new project. Pressing the button to the right of this
field brings up the PiCPro Version Selection dialog. Choose the desired edition
and version from this box and click OK. In the new project, this will be entered
into the PiCPro VERSION category.
Project Paths
This section is made up of file types and paths that are used to build the following
categories in the new project:
• UDFBs/TASKs
• SERVO SETUP FILES
• SERCOS SETUP FILES
• PROFILE SETUP FILES
• OTHER FILES
For every different type of file (Servo Setup source, UDFB library, etc.) and path
combination that exists in the Source PRJ project file, a corresponding entry exists
in the Project Path(s): in the dialog. For the example below, if for some reason
this is how you’ve arranged your UDFB files in the Source PRJ project file...

...then this will be the information the File Types and Source directories columns
of the Save As Project dialog:
Note: If a category in the Source PRJ is empty, then the corresponding file types
will not be listed in this dialog’s Project Path(s):. For example, if the
Source PRJ has no items in the OTHER FILES category, then Other Files
will not be listed in the File Types: of this dialog. If the Source PRJ has
source files in the PROFILE SETUP FILES categories, but no library files,
then the File Types: in this dialog will have Profile Setup Source listed
but not Profile Setup Libs.
The File Types: and Source directories: columns cannot be edited from this dia-
log, but the entries in the Destination directories: column can be. Edit this field
for every file type’s destination that you want changed in the new project. By
default, the Destination directories: column is initialized with the same informa-
tion as in the Source directories: column.
To begin editing a Destination directories: field, single click at the point in the
text where you want to start typing. A blinking cursor should appear. Any charac-
ters typed will be inserted before the cursor. If any portion of a field is selected,
any character you type will replace that selected portion. If you click in the field
where there isn’t any text, the entire field will be selected.
Note:
• <Ctrl + X> cuts any selected portion to the clipboard.
• <Ctrl + C> copies any selected portion to the clipboard.
• <Ctrl + V> pastes clipboard contents over any selected portion otherwise
pastes before the blinking cursor in the field.
You can also use the browse button to the right of each Destination directories:
field to browse to the desired location.
When done click the OK button. The source PRJ file is automatically closed, the
files are copies to their new locations, and the new project file is opened in the
PiCPro for Windows that is currently running.

CHAPTER 3 Working with Ladders
A PiCPro Session
This section covers information about basic operations you need to be familiar with to use
PiCPro. A PiCPro session begins when you launch the application. Next you choose what
you want to do in the session.
• Create a new ladder file (*.ldo). Refer to Chapter 3 - Working with Ladders.
• Open an existing ladder file (*.ldo). Refer to Chapter 3 - Working with Ladders.
• Create a new servo setup file (*.srv). Refer to Chapter 5 - Servo Setup and Tun-
ing.
• Open an existing servo setup file (*.srv). Refer to Chapter 5 - Servo Setup and
Tuning.
• Create a new SERCOS setup file (*.src). Refer to Chapter 6 - PiCPro and SER-
COS.
• Open an existing SERCOS setup file (*.src). Refer to Chapter 6 - PiCPro and
SERCOS.
• Create a new analog interfaced drive system file (*.adv). Refer to Chapter 4 - Set-
ting Up MMC Smart Drive.
• Open an existing analog interfaced drive system file (*.adv). Refer to Chapter 4 -
Setting Up MMC Smart Drive.
• Create or edit a Project (*.prj). Refer to Chapter 2 - Working with Projects.
Once the file you’ve chosen is open, you can begin to add/change the file using the editing
tools. Then you save the file to a location specified by you. Finally, you can exit PiCPro
or, if completed, compile and download your file to the PiC.
Creating New Files
Once PiCPro is started, you can create a new ladder file.
1. To start a file, do one of the following:
• Click the button in the standard toolbar.

• Select File | New from the menu.
2. The New dialog appears. Choose Ladder Diagram.
51 Working with Ladders

When creating new files in PiCPro Professional Edition, you can also select the
CPU type (PiC, MMC, or MMC for PC). The default selection is the last
selection made.
Note: In the PiCPro MMC-Limited Edition, the CPU type is always MMC.
Target CPU cannot be selected in the MMC-Limited Edition.
3. Choose OK to start a new ladder file. Select Cancel or to close the dialog
without starting a new ladder file. Select Help to display information related
to starting a new ladder file.
PiCPro then displays a new ladder diagram. You can now create your ladder program
with the tools and features available in PiCPro and then save your ladder file.
Opening a New Ladder File

When you open a new ladder file, Network #1 appears and you can begin entering
your program. Additional networks can be added as you develop your program.
The location of elements for both an LD Network and a ST Network are illustrated
below.
Network
Element
LD Network
LD
Elements
Network
Element
ST Network
ST
Element
Working with Ladders 52

Opening an Existing Ladder File
The Open command opens files that have already been saved.
1. To open an existing file, do one of the following:
• Click the button in the standard toolbar

• Select File | Open from the menu
2. In the Look In: list, choose the drive where the file is located.
3. Double-click the folder where the file is located.
4. Double-click the filename of the file you want to open

An example ladder file is illustrated below.
Note: The toolbar area can be optimized by moving toolbars. See section
Moving Toolbars.
Opening a Recently Opened File

To open a recently opened file, do the following:
• Select File from the menu.
A list of the most recently opened files appears at the bottom of the menu.
• Click on the file you want to open.
Note: Opening a ladder file (*.ldo) with a PiC or MMC for PC CPU in MMC-Limited
Edition will result in a confirmation prompt. If you choose not to convert the CPU
type, the file will be opened but cannot be downloaded, compiled etc.

Password Protecting LDO Files
Overview
Each LDO file can be assigned a password (Main LDO and UDFB files). By assign-
ing a password to an LDO file a file can be locked to prevent opening or editing. A
password can be set, modified, or removed using the File | Properties dialog.
Note: PiCPro Professional and MMC-Limited Editions prior to version V14.1 and all
versions of Monitor Edition do not allow assignment of passwords to an LDO
file. Also, all versions prior to V14.1 are not compatible with a password pro-
tected LDO file (an error will display when an attempt is made to open the
file).
Two levels of password protection are available:
• Password Required to Open File - The LDO file cannot be opened without enter-
ing a password. Once the password is entered, the LDO file is opened and full
editing of the LDO file is possible.
Note: If the file is opened in Monitor Edition, a password prompt will be dis-
played before the file is opened. Once the file is open, the file cannot be
edited.
• Password Required to Edit File - The LDO file is opened without entering a
password, but the LDO file cannot be edited until the file is unlocked by entering a
password through the menu item File | Properties or by selecting the unlock tool-
bar button.
If the same password is used for all files of a ladder program (Main LDO and
UDFB's), then all files in that ladder program can be unlocked by entering the pass-
word just once. When opening additional files, a prompt will be displayed asking for
a password. The newly opened files will open in an edit lock state until unlocked by
clicking on the unlock toolbar button - but this time, no password is required. This
helps prevent accidental changes to a file that was not specifically unlocked.
Note: The main LDO is always the main level of password protection. In other
words, a UDFB nested inside another UDFB always compares its password
against that of the main LDO and not its parent UDFB.
When passwords are different between the main LDO and a UDFB, each file adheres
to its own password protection scheme with one exception: the main LDO must
always be unlocked before a UDFB can be unlocked. If the main LDO has not been
unlocked yet (or has been re-locked), a double password prompt will be displayed; one
for the main LDO password and one for the UDFB password.
Files that are not password protected can still be locked temporarily during any edit
session. This protects a file against accidental changes. A click of the unlock toolbar
button is all that is required to unlock the file - no password is needed.

File Properties Dialog for Password Protection
1. From an open LDO file, select File | Properties. The file properties will be dis-
played in the non-editable File Properties dialog as follows:

2. Click the Password Protection tab and the following will be displayed:
Descriptions of dialog components and related actions are as follows:
Enter Password In order to modify password protection, the

file’s password must be entered. Password
length is between 6 and 32 characters. The
entries can consist of alphanumeric, spaces
and punctuation characters.
Add/Modify password Click this button to activate password pro-

required to OPEN file tection required to open this LDO file. This
button will be disabled if the current pass-
word has not been entered using the Enter
Password button.
Add/Modify password to Click this button to activate password pro-

EDIT file tection required when editing this LDO file.
This button will be disabled if the current
password has not been entered using the
Enter Password button.
Remove Password Protection Click this button to remove password pro-

tection for this LDO file. This button is dis-
abled if password protection does not
already exist or if the current password has
not been entered using the Enter Password
button.

New Password: Enter the password into this field that will be
used to unlock this file.
The entry has to be between 6 and 32 char-
acters. The entry can consist of alphanu-
meric, spaces and punctuation characters.
Verify Password: Enter the same password in this field as in

the New Password field. The Verify Pass-
word field is used to verify that the two
passwords match and prevents a mistyped
password from being attached to an LDO
file.
The entry has to be between 6 and 32 char-
acters. The entry can consist of alphanu-
meric, spaces and punctuation characters.
Unlock File This is used to unlock a password protected

LDO file. Click this button to display the
Unlock File dialog. Enter the file password
in this dialog and click OK. The entered
password will be compared to the file's pass-
word. If the passwords match, the file will
be unlocked. This button is only enabled if
the file is currently locked.
Re-Lock File This is used to lock a file and prevent edit-

ing. Click this button to re-lock the file.
OK Closes this dialog and saves any changes

that were made.
Cancel Closes this dialog without saving any

changes.
Apply Click this button to apply the changes made

without closing this dialog.
Help Displays information about this tab.

To Password Protect a File
1. From an open LDO file, select File | Properties.
2. Click the Password Protection tab and the following will be displayed:
3. Select Add/Modify password required to open file to prevent the file from being
opened until a password is entered or select Add/Modify password required to
edit file to prevent editing of the file until a password is entered.
4. At New Password, enter the desired password. At Verify Password, enter the
desired password again.
5. Click OK.
Note: The file must be saved to activate the protection.

Opening a Password Protected File
When opening a main LDO file or viewing a UDFB from the main LDO file that is
password protected on open, the following prompt will be displayed:
Note: The password entry field will be titled “UDFB Password” if a UDFB is
being loaded.
1. Enter the password.
Note: If the password is not correct, the following will be displayed:
2. Click OK and the Unlock File: dialog will again be displayed, allowing the correct
password to be entered.
3. Enter the correct password.
Once the correct password has been entered, the file will open for viewing.

Unlocking a File that is Edit Protected
If the file is password protected and the option Add/Modify password
required to open file is selected, the file can be viewed without entering a
password. The title block of the file contains [Locked], indicating that the file
is password protected and cannot be edited.
To edit this file the file must be unlocked first. To unlock the file:
1. Click on the standard toolbar and the Unlock File: prompt will be dis-
played as follows:
2. Enter the correct password. The Lock/Unlock icon will change to indi-
cating that the file is unlocked and can be edited.
Note: There should not be any forcing windows active for the active LDO
being re-locked.

To Modify an Existing Password
1. From an open LDO file that is password protected, select File | Properties.
2. Click the Password Protection tab. The File Properties dialog will be dis-
played as follows:
3. Click Enter Password. The following will be displayed:
Note: The password entry field will be titled “UDFB Password” if a UDFB is
being edited.

4. Enter the correct password and click OK. The File Properties dialog will be
displayed as follows:
5. (Option) Select either Add/Modify password required to open file to apply

an “open” password or select Add/Modify password required to edit file to
apply a password that allows editing of the file.
6. To change the password, at New Password, drag and select ******** . Enter
the new password. At Verify Password, drag and select ********. Enter the
new password again.

To Remove an Existing Password
1. From an open LDO file that is password protected, select File | Properties.
2. Click the Password Protection tab. The File Properties dialog will be dis-
played as follows:
3. Click Enter Password. The following will be displayed:

4. Enter the correct password and click OK. The File Properties dialog will be
displayed as follows:
5. Click Remove password protection as shown in the following display:
6. Click OK or Apply to remove the password. Click Cancel to stop the pass-
word removal.

Locking a File
Any LDO file can be locked by clicking on the standard toolbar.

Locking a File with password protection
If the file was previously password protection, the file will be locked without fur-
ther prompting, unless the file has changes that have not been saved or if a force
list is opened for that file. If one of these cases exist, a dialog will display describ-
ing why the file cannot be locked. Once the file is locked, the file’s password will
be required to unlock the file again.
Locking a File with no password protection
If the file has no password protection a dialog will be displayed asking if you want
to add password protection.
If Yes is clicked, the File Properties password protection dialog will be displayed.
From this dialog, password protection can be added.
Note: If password protection is added to a file, the file will not be com-
patible with versions of PiCPro older than V14.1.
If No is clicked, the following dialog is displayed:
If Yes is clicked, the file will be locked against changes. No password is required
to unlock the file.
If No is clicked, the file will remain unlocked.

PiCPro Tools
The toolbars give you quick access to some of the frequently used tools. These are the
toolbars available in PiCPro (refer to APPENDIX I - Toolbar Buttons).
• Servo - Standard and SERCOS - Standard
• Drive List - Standard Tools
• Custom Motor
• Standard
• Basic Online Operations
• Advanced Operations
• Ladder
• View Navigator
• Function/Function Blocks
• Compiler
• Structured Text Tools
• Insert New Network
Using the Pointer Tool
The Pointer tool button is found on the Ladder Toolbar. It is the default selection
allowing you to point and click to select locations in the ladder. You can exit the drop
mode for any of the other Ladder toolbar buttons by selecting the Pointer tool.
Zooming In and Out

Zooming in and out allows you to view and work on your program from 5% to 400%
magnification.
Using Zoom Command from View Menu
1. Select View | Zoom from the menu. The Zoom dialog appears:
2. Choose a zoom rate by using one of the following methods:

• Click a button
• Press a hot key (i.e. 7 for 75%)

• Enter a custom rate by incrementing or decrementing the scroll box in
increments of 1%
Note: that choosing 200% will double the size. Choosing 50% will
decrease the size by one half. The default is 100%.
3. Click OK to accept the zoom rate or Cancel to ignore it.
Using Zoom Command from Navigator Toolbar
• To decrease the size of the display, click on the repeatedly until you reach
the desired magnification.
• To increase the size of the display, click on the repeatedly until you reach
the desired magnification.
Tip
When you zoom in or out, the cell in the top left-hand corner remains in that loca-
tion after zooming.
Selecting and Deselecting Items
Focus
A cell or group of cells in your ladder will always have focus. Focus is indicated
by a dashed rectangular border around the area. A cell that has focus can be cop-
ied, cut, pasted, and deleted. You can also select a cell or group of cells.
The quickest way to set focus is by using the Pointer tool to single click on a cell.
If you place focus on the power rail in your ladder, the whole row will have focus.
If you place focus on a Function/Block, the whole Function/Block will have focus.
However, if you placed focus on the power rail and there is a Function/Block in the
row, the entire Function/Block is not selected. You can also move the cell focus
from the keyboard as follows.

Keys Focus Moves:
LD (Ladder) and ST (Structured Text)
Arrow From current position to new position in the direction of the arrow
Home To first column of current row (not on the power rail)
End To the last filled cell of the current row
<Ctrl + Home> To Network #1 in your ladder if focus is already in first row, first
column of current network or else to first row, first column of cur-
rent network
<Ctrl + End> To the End of Module marker if focus is already on the last occu-
pied cell in the last row of the network or else to the last occupied
cell of the current network
<Page Down/Up> One vertical viewable page down/up
<Ctrl + Page- One horizontal viewable page left/right
Down/Up>
LD Only
Tab One element to the right of the current element
<Shift + Tab> One element to the left of the current element
Selection
Selection is indicated by highlighting the area. Selected cells can be copied, cut,
pasted, deleted, dragged and dropped.
Selection is set by first placing focus on the cell and then clicking within the cell.
The cell is highlighted.
A row is selected by placing focus on the power rail and then clicking on the
power rail within the focus row.
Multiple cells are selected by clicking on the first cell and then dragging the mouse
over the area you want to highlight.
If the power rail is not included in the selection, the selection must be contained
within a network.
If the power rail is included in the selection, the selection can contain sequential
rows from more than one network.
Note: A ST element takes up only 1 row but can contain up to 500 lines of text.

You can also select cells using the keyboard.
Keys Selects
<Shift + Arrow> All cells within the rectangular area defined by the arrow
keys (Within a network if focus is not on the power rail
and over multiple networks if focus is on the power rail.)
<Shift + Home> The focus cell and cells to the left of it
<Shift + End> The focus cell and cells to the right of it until the last
filled cell
<Shift + Ctrl + Home> The focus cell and all cells to the upper left-hand cell in
the network if focus cell is not on the power rail.
The focus cell and all cells to the first row in the module
if the focus cell is on the power rail of the first row of the
current network or else selects the focus cells and all
cells through the first row of the current network
<Shift + Ctrl + End> The focus cell and all cells to the last row in the network
if focus cell is not on the power rail.
The focus cell and all cells to the last row in the module
if the focus cell is on the power rail of the last row of the
current network or else selects the focus cell and all cells
through the last row of the current network
<Ctrl + A> All cells in the ladder if all cells in the current network
are selected. If all cells in the current network are not
selected, all cells in the current network will be selected.
Deselect
If you click on any cell, all cells will be de-selected.

If you move focus with an arrow key, all cells will be de-selected.
Entering Ladder Networks
Inserting a Network
When a network is inserted it will be inserted above the focus cell. A new network
appears above the focus cell. All the networks below the insertion are renumbered.
Right-Click Method
1. Position the focus where you want to insert a network.
2. Right-click and choose Insert | LD Network or ST Network.
Menu Pull-Down Method

• Select Ladder | Network | Insert from the menu
• Then select either LD Network or ST Network.

Hotkey Method
Press a hotkey combination:
• <Shift + Insert> for a LD Network
• <Ctrl + Insert> for a ST Network.
Toolbar Method
Select a toolbar button from the Insert New Network toolbar. Select LD for a
Ladder Network or ST for a Structured Text Network.
Inserting a ST network with focus in a ST element
If focus is in a ST element and you insert a ST network, the ST element will be

divided at the cursor position. The following prompt will appear:

Select Yes and the ST network will divide into two ST networks. The line with the
cursor will appear in the second ST network. The networks will be renumbered if
this is not the last network.
Inserting a LD network with focus in a ST element
If focus is in a ST element and you insert a LD network, the ST element will be

divided at the cursor position. The following prompt will appear:
Select Yes and the ST network will divide into two ST networks at the cursor loca-
tion and a LD network will be inserted between them. The focused element will be
the new LD element. The networks will be renumbered if this is not the last net-
work.
Inserting a ST network with focus in a LD element
If focus is in a LD element and you insert a ST network, the LD network will be

divided into two LD networks at the cursor position. A ST network will be inserted
between them. The focused element will be the new ST element. The networks
will be renumbered if this is not the last network.

Overview - Cut, Copy, Delete and Paste
The Cut, Copy, and Paste commands allow you to use the clipboard to make copies of LD
or ST Network Elements, LD Elements or Structured Text items from your ladder.
The Copy command places a copy of the selected item on the clipboard.
The Cut command removes the item from your ladder and places it on the clipboard.
Once an item is on the clipboard, you can use the Paste or Paste Insert commands to
place the item in a ladder. The item remains on the clipboard until you cut or copy another
item. Only one item can be placed on the clipboard at a time.
Note: The Delete command removes the selected item from your ladder. It does not
place it on the clipboard.
If animation is running when you begin these procedures, it will be halted.
Delete
Deleting LD or ST Networks
To delete a LD or ST network, do the following:
1. Position the focus anywhere in the network you want to delete.
2. Choose one of the following methods to delete a network:
• Select Ladder | Network | Delete from the menu
• Press <Shift + Delete>.
3. A confirmation message will appear. If you select OK, the network will be
deleted. All the networks after the deleted network are renumbered.
4. You can delete multiple networks by selecting all the rows within the networks.
Choose one of the following methods to delete a row:
• Select Ladder | Row | Delete from the menu
• Press Delete key.
Deleting LD or ST Network Elements

Deleting a LD or ST network element results in the merging of two networks. How-
ever, only like networks can be merged.
To delete a network element, do the following:
1. Position the focus on a network element.
2. Choose one of the following methods to delete a network element:
• Select Edit | Delete from the menu
• Press <Ctrl + D>
3. A confirmation message will be displayed.

Deleting LD Elements or Structured Text
The Delete command removes the selected LD Element or Structured Text. It does not
place it on the clipboard.
To use the Delete command, do the following:
1. Click on the LD element or select the Structured Text.
2. Choose one of the following methods to issue the Delete command:
• Select Edit | Delete from the menu
• Press <Ctrl + D>
3. A confirmation message will be displayed.
Cut, Copy, and Paste
Cutting Network Elements

Cutting a network element results in the merging of two networks. However, only like
networks can be merged (i.e. a LD network cannot be merged with a ST network and
vice versa).
To cut a network element, do the following:
1. Position the focus in the network element you want to cut.
2. Choose one of the following methods to issue the Cut command:
• Click the button from the standard toolbar.

• Select Edit | Cut from the menu.
• Press <Ctrl + X>.
• Right-click and select Cut.
3. A confirmation prompt will be displayed if the network element is the same
type as the previous network element. An error message will be displayed if
the network element is not the same type as the previous network element (a
LD network cannot be merged with a ST network).
Cutting LD Elements or Structured Text

When you cut a LD Element, a ST Element or a portion of a ST element, it is removed
from the file and placed on the clipboard.
1. Select what you want to cut.
2. Choose one of the following methods to issue the Cut command:
• Select Edit | Cut from the menu.
• Right-click and select Cut from the menu.
Copying LD Elements or Structured Text
When you copy LD Elements or Structured Text Elements, they remain in the file and
are placed on the clipboard.
1. Select what you want to copy.
2. Choose one of the following methods to issue the Copy command:

• Select Edit | Copy from the menu.
• Press <Ctrl + C>.
• Right-click and select Copy.
Copy Rules
• If focus is on a ST element and nothing is selected, nothing will be copied.

• If focus is on a ST network element, only the ST network element will be cop-
ied.
• If focus is on a LD element, the LD element will be copied.
• When a portion of a source ladder is copied and pasted into a different target
ladder, the software declarations that were used in the copied portion of the
source ladder are also placed on the clipboard and pasted in the target ladder.
Undeclared variables will remain undeclared. This is true for LD elements and
ST elements.
Pasting LD Elements or Structured Text

To paste LD Elements or Structured Text into a file from the clipboard, you can use
either the Paste or the Paste Insert commands.
To use the Paste command, do the following:
1. Select a location for the paste.
2. Choose one of the following methods to issue the Paste command:

• Select Edit | Paste from the menu.
• Press <Ctrl + V>.
• Right-click and select Paste.

Paste Rules
• If the data copied to the clipboard contains a power rail, it must be pasted on a
power rail.
• Rows must be pasted on rows. The only exception is if focus is on the End of
Module (EOM). If focus is on EOM, rows are inserted.
• Pasting a non-network element on a network element has the effect of merging
two like networks.
• A paste operation that does not include the power rail does a replace as fol-
lows:
If focus is on a LD network element, the following prompt will be displayed:
If you click Yes to continue, data in the network will be overwritten with the
data from the clipboard.
If focus is on a ladder element and the number of rows affected is less than or
equal to the number of rows in the network, the following prompt is displayed:
If you click Yes to continue, elements and functions in the network will be
overwritten with the data from the clipboard.
If focus is on a ladder element and the number of rows affected is more than
the number of rows remaining in the network, rows are added to the network.
If focus is on the EOM, rows are inserted.
• A paste operation that includes the power rail, does an insert above the line
with focus.
• The maximum number of cells in an LD network is 255.
• An error message will be displayed if an attempt is made to paste text into a ST
network that would cause the number of lines to exceed 500 or the number of
characters in a line to exceed 500.

• A ST element (not a ST network) or portion of a ST element that is copied can
be pasted as plain text into Microsoft WordTM , NotepadTM or WordpadTM. In
this case, software declarations are not pasted.
• Text copied from Microsoft WordTM , NotepadTM or WordpadTM can be pasted
into a ST element.
• A portion of a ladder can be copied and pasted into the view and force lists.
• Within a LD network, selecting ladder elements makes no difference when
pasting. Only ladder elements actually replaced, when the paste takes place,
will be deleted.
Paste Insert Rules
• If Edit | Paste Insert is selected while focus is on a ladder element, the follow-
ing prompt is displayed asking if rows should be shifted down or network col-
umns should be shifted right:
• If the clipboard data contains a power rail, it must be pasted on a power rail.
The only exception is End of Module (EOM). If focus is on the EOM, rows can
be pasted.
• The maximum number of cells in an LD network is 255.
• Within a ST element, a paste is always a paste insert operation. If text is high-
lighted when paste is selected, the highlighted text will be deleted when the
paste occurs.
Drag and Drop
You can drag a highlighted area by left-clicking and holding down the button, moving to
the desired area, and drop the selection by releasing the button.
If a power rail is not included in the selection, the selection must be contained within a
network.
If the power rail is included in the selection, the selection can contain sequential rows
from more than one network.
Note: A ST element takes up only 1 row but can contain up to 500 lines of text.
Drag and Drop Copy

1. Select an item.
2. Hold down the Ctrl key and hold down the left click button at the same time.

3. Drag the selection to a new location. A + character will appear by the mouse
pointer.
4. Release the left click button and the item will be copied to the new location.
Drag and Drop Copy Rules
When a portion of a ladder is Drag and Drop copied into a different ladder, the
software declarations that were used in the copied portion of the ladder are added
to software declarations. Undeclared variables will remain undeclared.
Drag and Drop Move

1. Select an item.
2. Hold down the left click button.
3. Drag the selection to a new location.
4. Release the left click button and the item will be moved to the new location.
Drag and Drop Move Rules
When a portion of a ladder is Drag and Drop moved into a different ladder, the
software declarations that were used in the moved portion of the ladder are added
to software declarations. Undeclared variables will remain undeclared.
If a LD network element is dragged and dropped, one of the following will occur
based on the location of the element to be moved.
After the move:
• If the network above the element being moved is a LD network, the
remaining rows in the network will be merged with the network above.
• If the network above is a ST network, an error message will be displayed.
• If the network is the first network and the network is empty, a prompt will
be displayed asking if the entire network should be deleted.
• If the network is the first network and the network is not empty, an error
message will be displayed along with a prompt asking if the entire network
should be deleted.
If a ST network element is dragged and dropped, one of the following will occur
based on the location of the element to be moved.
After the move:
• If the network above the element being moved is a ST network, the ST ele-
ment below the network element being moved will be merged with the ST
element above the network element being moved.
• If the network above is a LD network, an error message will be displayed.
• If the network is the first network and the network is empty, a prompt will
be displayed asking if the entire network should be deleted.

• If the network is the first network and the network is not empty, an error
message will be displayed along with a prompt asking if the entire network
should be deleted.
Drop Rules
• The maximum number of lines in a ST network is 500. The maximum number of
characters in a line in a ST network is 500.
• The maximum number of cells in a LD network is 255.
• If the data to be dropped contains a power rail, it must be dropped on a power rail
(rows must be dropped on rows). The only exception to this rule is the EOM. If
focus is on the EOM, rows can be dropped.
• Dropping a non-network element on a network element has the effect of merging
two like networks.
• A drop operation, which does not include the power rail, does a replace as follows:
• If dropping on a network element, the following prompt is displayed: Net-
work(s) will be overwritten. Continue anyway?.
• If dropping on a ladder element, and the number of rows affected is less than or
equal to the number of rows in the network, the following prompt is displayed.
Element(s) will be overwritten. Continue anyway?.
If dropping on a ladder element, and the number of rows affected is more than the
number of rows remaining in the network, rows are added to the network.
• If dropping on EOM, rows are inserted.
• A drop operation, which includes the power rail, does an insert above the line with
focus.
Other Notes - Drag and Drop

• Within a ST element, a drop is always an insert operation.
• Drag and Drop can be used to copy/move a ST element (not a ST network) or por-
tion of a ST element into Microsoft WordTM. In this case, software declarations are
not dropped.
• Text dragged from Microsoft WordTM can be dropped into a ST element.
• NotepadTM and WordpadTM do not support drag and drop.
• Drag and Drop can be used to copy or move a portion of a ladder or structured text
into the view and force lists.

Finding and Replacing
In a ladder in PiCPro, you can search for declared contacts, declared coils, declared
function blocks, declared elements, function/function block titles, network numbers,
or structured text.
The search can be refined by applying a filter that limits the search (e.g. Struc-
tured Text Only):

Control Description
Find: Enter Item to search for. An item can be chosen

from the list or typed in. Valid entries are filled in
when a filter is chosen. The drop down list con-
tains valid entries for the specified filter. If the
Structured Text Only filter is selected, the
Find: drop down list contains the most recently
searched for “Structured Text Only” strings.
Replace with: Enter the item you want to replace the Find: item
with or choose an item from the list. The drop
down list will contain items from a previous find/
replace.
Filter search by: An item can be chosen from the list to filter the
search with. The filter will describe the type of
item being searched for.
Search direction Check the appropriate box to search either for-
ward or backward from where the focus is in
your ladder. The search will proceed in the direc-
tion you specify and then auto-wrap when the
top/bottom of the ladder is reached.
Structured Text Match Whole Word Only - Enabled for Struc-
Options tured Text Only filter. When selected, finds
strings that are whole words and not part of a
larger word.
Match Case- Enabled for Structured Text Only

filter. When selected, distinguishes between
uppercase and lowercase characters and will
match only those instances where the capitaliza-
tion matches the text typed in the Find: field.
Find Next Finds the next occurrence of the entry in Find:
Replace Replaces the entry in Find: with the entry in
Replace with:
Replace All Replaces all occurrences of the entry in Find:
with the entry in Replace with:
Cancel Closes this dialog without saving any changes.
Help Accesses the Help system.
Notes:
• You must enter the complete name of the item you want to search for.

• When searching for declared contacts, coils, Function Blocks or Function
Block titles in a ST network, text may not be recognized as a declared element
if there are errors while compiling. Replace will be disabled in a ST Network
that contains compile errors.
• When searching in a ST network, Function Blocks of a specific type can only
be found if the Title is left in the function.
• Choosing the Structured Text Only filter causes a search to be done only
inside ST networks. LD networks will not be searched. Any filter selected
other than Structured Text Only causes a search to be done in both ST and LD
networks.
• You can find and replace items individually or find and replace all occurrences
of items by entering a declared variable in the Replace with: field and choos-
ing the Replace or Replace All button.
Finding and Replacing - Procedures
To search for an element in the ladder
1. Choose one of the following methods to see the Find/Replace dialog.

• Select Edit | Find/Replace from the menu
• Press <Alt + F3>
2. Enter the name of the ladder or structured text element you want to search for
in the Find: field or use the dropdown list and select the name of the ladder
element you want to search for. If the focus in your ladder is on an element that
can be searched for, it will automatically appear in the Find: field.
3. Be sure the correct filter is selected in the Filter search by: field.
4. Choose the Search direction.
5. Select the Find Next button to move either forward or backward to the next
location of the element in the ladder.
6. Continue selecting the Find Next button or press the Enter key if you want to
continue to find occurrences of the element. A message will inform you after
the ladder has been completely searched.
To search and replace an element in the ladder
1. Choose one of the following methods to see the Find/Replace dialog:

• Select Edit | Find/Replace from the menu
• Press <Alt + F3>
2. Enter the name of the ladder element you want to search for in the Find: field.
If the focus in your ladder is on an element that can be searched for, it will
automatically appear in the field.
3. Enter the name you want to replace the variable with in the Replace with: field
or use the dropdown list and select the name you want to replace the variable
with. If the replacement name has not been added to the software declarations
table, you will be prompted to do so now.

4. Be sure the correct filter is selected in the Filter search by: field.
5. Choose the Search direction.
6. First choose the Find Next button to find the element.
7. Choose either Replace to replace an occurrence of the element or Replace All
to replace all occurrences
Filtering Find and Replace

You can filter your search by the criteria listed below in the Filter search by: field
within the Find/Replace dialog. Some things to keep in mind include:
• If focus in your ladder is on a contact, coil, data input, data output, function,
function block, network label, or a jump label, the name will automatically be
entered in the Find: field.
• If the focus is on a wire or a return label, things that cannot be searched for,
you must enter a name in the Find: field and the correct filter in the Filter
search by: field.
• If you want to find a network, enter the number in the Find: field and select
Network Numbers for the Filter search by: field.
TYPE OF FILTER LADDER ELEMENTS TO FIND

Declared Contacts/Data Ins To first column of current row (not on the power rail)
Declared Coils/Data Outs Coil or data output
Declared Functio Blocks Function Block instance
All Declared Elements Contact, coil, data input, or data output
Function/Block Titles Functions
Label Names Network or jump label
Network Numbers Numbered network
Structured Text Only Structured Text
• All the filter selections except Structured Text Only, Function/Block Titles
and Network Numbers require entries into the Find: field that are defined in
software declarations and that match the current filter. If Structured Text
Only is selected, any text can be typed into the Find: field.
• If the Declared Contacts/Data Ins filter is selected, the entire ladder will be
searched for the contents of the Find: field. A match will be found in a ST net-
work anywhere the contents of the Find: field is used and not set. Note:
When this filter is selected, the Find: field must contain a valid variable name.

• If the Declared Coils/Data Outs filter is selected, the entire ladder will be
searched for the contents of the Find: field. A match will be found in a ST net-
work anywhere the contents of the Find: edit field is set and not just used.
Note: When this filter is selected, the Find: field must contain a valid variable
name.
• If the Declared Function Blocks filter is selected, the contents of the Find:
field represent a function block instance name. In a ST element, a function
block is represented in the following format: Instance:Title(…). If found in a
ST network, only Instance will be highlighted.
• If the All Declared Elements filter is selected, all declared elements will be
searched.
• If the Function/Block Titles filter is selected, the contents of the Find: field
represents a function/block title. In a ST element, a function/block title is rep-
resented in the following format: Instance:Title(…). If found in a ST net-
work, only Title will be highlighted. If ‘:Title’ is not typed in (it is optional),
the search will not relate the instance name back to the title being searched.
• If the Label Names filter or the Network Numbers filter is selected, ST ele-
ments will not be searched since these items are not relevant to a ST element.
• If the Structured Text Only filter is selected, the drop down list for the Find:
field will contain a list of the last Structured Text Only search entries.
Finding Duplicates
When debugging a ladder problem, it can be useful to identify all symbols that are
modified at multiple locations within a ladder. Find Duplicates provides this function-
ality. When Find Duplicates is selected, PiCPro searches for function blocks, data
outs, and coils that appear more than once in the ladder. When PiCPro finds duplicated
function blocks, data outs, or coils, a message is displayed in the information window.
To search for duplicated elements:
1. Select Edit | Find Duplicates from the menu.
2. PiCPro searches the ladder and puts a message in the information window
when finished either saying no duplicates were found or listing the ones that
were found.
Note: Duplicated jump labels, contacts, data ins, and functions are not included in
this search.
Saving, Closing, and Exiting
When you close your ladder, PiCPro asks if you want to keep any changes that have not
yet been saved. You have three choices:
• Yes to save the latest changes
• No to lose the changes and close the ladder
• Cancel to allow you to change your mind and continue to work on the ladder.

If you close a ladder that you have not yet assigned a name to, PiCPro asks if you want to
save changes to the ladder diagram. If you choose Yes, the Save As box appears and you
can type in the name. PiCPro assigns the name to the ladder, saves the ladder, and then
closes.
Note: A ladder saved in V13.0 is saved in a format that cannot be read by previous
versions of PiCPro if software declarations contains any mixed case variable
names, variable names longer than 8 characters, the ladder contains any ST
networks, or scan with ASIU errors has been enabled in hardware declara-
tions.
Saving Files
It is a good idea to save your file at regular intervals as you work on it.
Using the Save command, you can save the file under its existing name.
Using the Save As command, you can specify a new filename and/or a location where
you want the file stored.
To save a new file, do the following:
1. Select File | Save from the menu or the button from the standard toolbar.
2. In the Save As box, choose a drive and folder where you want to save your lad-
der file (*.ldo).
3. Enter a name in the File name: field.
4. Click Save.
To save an existing file, do the following:
• Select File | Save from the menu or the button from the standard tool-
bar.
To save all files open within PiCPro, do the following:
• Select File | Save All from the menu
If any of the open files have not been saved previously, PiCPro prompts you to choose
a location to save the file to. Type in a name in the File name: field and click Save.
Note: This command will update the Windows time stamp on all of the open files
regardless of whether changes were actually made.
Saving Files with a Different Name

You can use the Save As command to change the name and/or the location of a file. By
giving the file a different name when you save it, you create a copy of the existing file
while keeping the original intact.
To save a file under a different name, do the following:
1. Select File | Save As from the menu.
2. Select the location you want to save the file to in the Save in: field.

3. Enter the new file name in the File name: box.
4. Click Save.
Closing Files
If the file has changed but has not yet been saved, PiCPro asks if you want to save the
file before closing it. Choose Yes to save the file before closing, choose No to close the
file without saving it.
To close a file, do the following:
• Select File | Close from the menu
Exiting PiCPro
Exiting means shutting down PiCPro. It marks the last step in a PiCPro session.
To exit, do one of the following
• Select File | Exit from the menu
• Click on the corner symbol on the title bar to drop down a list. Choose
Close.
• Press <Alt + F4>.
• Click the button in the upper right corner.

PiCPro asks if you want to save any unsaved changes in any open files:
• Click Yes to save changes before exiting.
• Click No to exit without saving changes.
• Click Cancel to exit the dialog box and continue with your application.
Working with a Split Screen
You may find it helpful to use the split screen feature when you want to view sections
of a ladder at the same time. Each section will have its own scrolling capability so you
can move to any ladder location you want.
Note: Click within the quadrant you want to scroll before using the scroll bar.
The screen can be split horizontally and/or vertically.

To split the screen, do the following:
1. To split the screen horizontally, move the arrow to the top section (encircled
below) of the vertical scroll bar.
2. When the arrow head changes to the double line/double arrow, click the button
and drag the horizontal line into your ladder and release.
3. To split the screen vertically, move the arrow to the left section (encircled
below) of the horizontal scroll bar.
4. When the arrow head changes to the double line/double arrow, click the button
and drag the vertical line into your ladder and release.
To unsplit the screen, do the following:
• Double click on the vertical or horizontal split line to remove the split
screen and return to your normal view.

Hardware Declarations
Hardware declarations will differ based on whether you declare a PiC CPU, standalone
MMC CPU, or MMC for PC CPU. If you declare a CPU that differs from what is actually
installed in the control, you may not be able to download your ladder file (*.ldo) to the
control.
The hardware configuration in the hardware declarations table is compared to the I/O
points defined in the software declarations table when the ladder (*.ldo) is compiled.
PiCPro can detect an error such as an output that is defined at an input location. An error
message will be displayed when you issue the Compile Only or the Compile & Down-
load command.
In the hardware declarations table, you define what type of hardware module occupies
each slot in the master rack. Based on the type of CPU selected, you can also define the
other types of I/O in your system such as remote I/O expansion racks, block I/O, or ASIU
I/O.
If you later change the CPU type from what was originally declared, you will need to
review the I/O points defined in software declarations to ensure that your I/O points are
correctly assigned.
Hardware Declaration Restrictions

When making hardware declarations, you must first determine that the CPU supports
the I/O in your system.
PiC 90 PiC 900 Standalone MMC for

CPU CPU MMC (3) PC
Remote I/O Expansion NO YES NO NO

Rack
Block I/O Module YES YES (1) YES YES
ASIU I/O Module NO NO NO YES
Ethernet YES YES YES YES (2)
DeviceNet YES YES YES YES
(1) Not
all PiC 900 and PiC 90 CPUs support block I/O modules. Check the hard-
ware manuals for these CPUs for complete information.
(2)
MMC for PC does not require a separate Ethernet module. PiC and standalone
MMC require separate modules.
(3)
Information that applies to standalone MMC also applies to standalone MMC
PLUS.

For CPUs that accept Remote I/O Expansion racks, up to 7 racks can be added.
For CPUs that accept Block I/O modules, up to 77 modules can be added.
For CPUs that accept ASIU I/O modules, up to 8 modules can be added.
Entering Hardware Declarations
To bring up the Hardware Declarations table
Use one of the following methods:
• Click the button on the View Navigator toolbar.

• Select View | Hardware Declarations from the menu.
The following dialog is displayed:

The following describes the Hardware Declarations dialog:
Control Description
I/O Expansion Option
Master Rack Only Select this option if your hardware configuration consists
of a master rack only.
Remote I/O Select this option if your hardware configuration contains

remote I/O.
Block I/O Select this option if your hardware configuration contains

Block I/O.
I/O Config/Scan Options
None Select this radio button to disable Ladder Configurable I/O

and prevent continued scan of a ladder with I/O errors.
Reconfigurable Select this radio button to enable Ladder Configurable I/O

Block I/O and con- and allow the ladder to continue scanning with Master
tinue to scan with Rack, Remote Rack or I/O errors.
Master Rack, Note: If an ASIU error is present, the ladder will not con-
Remote Rack or tinue to scan. The function block IO_CFG must be used to
Block I/O failures allow the ladder to react to I/O errors.
Reconfigurable Select this radio button to enable Ladder Configurable I/O

Block I/O and con- and allow the ladder to continue scanning with Master
tinue to scan with Rack, Block or ASIU errors.
Master Rack, Block Note: This option is only available if an MMC for PC Ana-
or ASIU failures log Servo CPU is selected.
To enter hardware declarations - master rack (all CPU types)
1. Position the cursor on the slot you want to declare a hardware module in and
left-click. A fly-out box appears. If an arrow is at the end of the item on the
fly-out list, there are more choices.
2. Slide the mouse over each fly-out list, select the description of the module you
want to declare.
3. When you are at the final fly-out list, left-click to make your selection. Your
choice will be listed in the master rack list. Note: if you want a brief descrip-
tion of the module, press F1 key before making your selection.
4. To add remote I/O (PiC CPU only) or block I/O, click the check box. You can
then use the fly-out lists to configure the I/O.
5. To enable I/O Config/Scan Options, select the appropriate radio button.
6. To save your declarations or changes and return to your ladder, use File | Save
& Close from the menu or F10 key or Enter key. To exit without saving your
changes, use File | Close from the menu or Esc key.

You can access various editing commands (Copy, Paste, Insert, etc.) with a right-click
or from the Edit menu.
You can also use the keyboard for selecting modules by pressing the spacebar. Then
use the up and down arrow keys to scroll, and press Enter key to select a module. You
can use the keyboard to access the editing commands by pressing <Shift + F10>.
Viewing Hardware Declarations

You can change the view of the hardware declarations list using the plus (+) and minus
(-) symbols to expand and contract the branches of the tree.
Hardware Declarations Table - PiC CPU
The Hardware Declarations Table is described on the following pages.

Master Rack
Slot 1 is reserved for the Central Services Module (CSM)
Slot 2 is reserved for the CPU module as follows:.
Slots 3 through 13 define the type and location of the I/O modules.

PiC I/O -- Inputs
PiC I/O -- Outputs

PiC I/O -- Mixed I/O

Hardware Declarations Table - Remote I/O Expansion Rack
Expansion Rack
Slot 1 Reserved for Remote Services Module

Slot 2 Reserved for I/O Driver Module
Slots 3 - 13 Define the type and location of the additional I/O modules.
Hardware Declarations Table - MMC for PC CPU
Master Rack (Board mounted in workstation)
Slot 1 MMC for PC CPU (Analog or Digital Servo)

Slot 2 Reserved for the DeviceNet, Profibus or Digital Line Shaft (DLS) module
MMC for PC ASIU I/O

Analog Servo Interface Units (ASIU)
Slot 1 - 8 (Only available when an Analog Servo CPU is specified)
A left-click on an ASIU “Slot” will display the selection menu shown.

The ASIU “slot” number refers to the physical switch setting on the
hardware.

Note: If an MMC for PC Digital Servo is selected, the ASIU I/O branch will not be
shown on the hardware tree.
Hardware Declarations Table - Standalone MMC CPU
Master Rack
Slot 1 2 1/2 or 4 1/2 Axes Servo

Slot 2 MMC CPU and General I/O
Slots 3 - 4 Reserved for Ethernet-TCP/IP, DeviceNet or Profibus modules
Hardware Declarations Table - MMC PLUS CPU

Master Rack
Slot 1 2 or 4 Axis Analog Servo Module

Slot 2 MMC PLUS In/Out 24V DC Module
Slots 3 - 6 Reserved for DeviceNet, Profibus, Ethernet or MMC 4-Axis Analog
Servo module

Hardware Declarations Table - Block I/O Module
Block I/O Modules
Blocks 1 - 77 Define the type and location of the I/O modules. Select the module type
and then the correct module from the fly-out list provided
Editing Hardware Declarations

The editing commands in the hardware declarations table are insert, delete, cut, copy,
and paste.
Inserting and Deleting Hardware Declarations
After entering the first Remote I/O expansion rack, you can add additional expansion
racks by using the Insert After command.
To insert additional remote I/O expansion racks or block I/O, do the following:
1. Select the device after which you want to insert another device.
2. Choose Edit | Insert After from the menu or Insert key. The new device will
be placed directly after the one you selected. If there are any racks or blocks
after it, they will be renumbered.

Note: Block I/O will only be incremented up to the first empty block. For exam-
ple, if you have Block I/O modules in blocks 1 through 5, and 6 through 9 are
empty, and 10 through 15 contain Block I/O modules, and you Insert After at
block 2, only 3, 4, and 5 will shift becoming 4, 5, and 6. The block modules in 10
through 15 are unaffected. You will also be prompted to have the corresponding
Block I/O points adjusted in Software Declarations. For this example, all I/O
points for block 3 would be changed to block 4, etc. You cannot insert Block I/O
that would cause a block defined at block 77 to be replaced. You will be prompted
to remove that block first.
To delete a remote I/O expansion rack or a block I/O, do the following:

1. Select the object you want to delete.
2. Choose Edit | Delete from the menu or Delete key. A warning message
appears. The object will be deleted if you choose OK. With a remote I/O
expansion rack, if there are any racks after the one you deleted, they will be
renumbered.
Note: When you delete a Block I/O module, remaining modules are moved up in
the list to the first empty block. For example, if blocks 1 through 6 are filled with
Block I/O modules, 7 through 9 are empty, and 10 through 15 contain Block I/O
modules, and you delete block 4, then 5 and 6 become 4 & 5, 6 is empty, and 10
through 15 are unaffected. Any Software Declarations specifying I/O points for
block 4 will be modified to remove the I/O points. You are prompted to have the
Software Declarations automatically adjusted. For this example, all I/O points for
block 5 will be changed to block 4, etc.
Cutting and Copying Hardware Declarations
The Copy and Cut commands let you use the clipboard to create copies of some
selected objects in the declarations table. The commands are context sensitive and
will be grayed if they do not apply to where you are in the table.
The Copy command places a copy of the selected object on the clipboard.
The Cut command removes the object from the table and places it on the clip-
board.

Copy command can be used on Cut command can be used on these
these selected objects: selected objects:
Entire Hardware Declarations Table Expansion Racks

Master Rack I/O and Block I/O Modules
Expansion Rack(s) Block I/O Branch
Block I/O Branch ASIU I/O Modules
ASIU I/O Branch
CPU, I/O, Modules
Copy command cannot be used Cut command cannot be used with:

on:
Modules that cannot be changed Entire Hardware Declarations Table

Master Rack
CPU and modules that cannot be
changed
I/O in slot 1
To copy an object in the hardware declarations table:
1. Select the object.
2. Choose Edit | Copy from the menu or <Ctrl + C> to copy the selected
object to the clipboard.
To cut an object in the hardware declarations table:
1. Select the object.
2. Choose Edit | Cut from the menu or <Ctrl + X> to cut the selected object.
Things to note about cutting objects from the hardware declarations table:
• When you cut a Block I/O module, remaining modules are moved up in the
list to the first empty block. For example, if blocks 1 through 6 are filled
with Block I/O modules, 7 through 9 are empty, and 10 through 15 contain
Block I/O modules, and you delete block 4, then 5 and 6 become 4 & 5, 6 is
empty, and 10 through 15 are unaffected. Any Software Declarations spec-
ifying I/O points for block 4 will be modified to remove the I/O points. You
are prompted to have the Software Declarations automatically adjusted.
For this example, all I/O points for block 5 will be changed to block 4, etc.
• When you cut an expansion rack or a block branch, the rack or block
branch is removed. With expansion racks, any remaining racks are renum-
bered.
Pasting and Paste Insert in Hardware Declarations
Once an object is on the clipboard, you can use the Paste command or the Paste
Insert After command to place the object back into the table. The object remains
on the clipboard until you cut or copy another object onto the clipboard. Only one
object can be placed on the clipboard at a time.

Using the Paste command
1. Select the location where you want the paste to occur.
2. Choose Edit | Paste from the menu or <Ctrl + V>. The object on the clip-
board will replace the selected object.
Using the Paste Insert After command
1. Select the location where you want the paste insert after to occur.
2. Choose Edit | Paste Insert After from the menu or <Ctrl + A>. The object
on the clipboard will be inserted after the location you selected.
Things to note about pasting objects in the hardware declarations table
• With the Paste command, the object on the clipboard must match the
selected object in the table.
• With the Paste Insert After command, the object on the clipboard must be
an expansion rack or a block module. The selected object can be the master
rack, an expansion rack, the block I/O root, or an individual block module.
• With the Paste Insert After command, Block I/O will only be incremented
up to the first empty block. For example, if you have Block I/O modules in
blocks 1 through 5, and 6 through 9 are empty, and 10 through 15 contain
Block I/O modules, and you Paste Insert After at block 2, only 3, 4, and 5
will shift becoming 4, 5, and 6. The block modules in 10 through 15 are
unaffected. You will also be prompted to have the corresponding Block I/O
points adjusted in Software Declarations. For this example, all I/O points
for block 3 would be changed to block 4, etc. You cannot insert Block I/O
that would cause a block defined at block 77 to be replaced. You will be
prompted to remove that block first.
Pasting to Software Declarations

You can copy I/O information for a standalone MMC or MMC for PC to the clipboard
and paste it in Software Declarations.
Right-click on a standalone MMC module (slot 1, 2, 3, 4, 5 or 6) or an MMC for PC
ASIU module, select Copy I/O to clipboard. Declarations for all I/O points on that
module will be placed on the clipboard.
Printing Hardware Declarations

The hardware declarations table cannot be printed while the hardware declarations
dialog is open. It can be printed using the Print command from the File menu for the
application. The table will be printed in its expanded form regardless of how it was
last displayed.
To print your hardware declarations
1. Put focus on the ladder view.
2. Select File | Print from the menu or press <Ctrl + P>.
3. The Print dialog appears. Make sure the Hardware Declarations Include in
Listing box is checked. Select OK to proceed or Cancel to exit.
Closing and Saving Hardware Declarations
You can close the hardware declarations table and save any changes or close without
saving changes.
To close and save the hardware declarations table:
1. If you choose File | Save & Close from the menu or press the F10 key, your
table will close and any changes will be saved.
2. If you choose File | Close from the menu or press the Esc key, your table will
close and no changes will be saved.

Software Declarations
In the Software Declarations table, you enter the following information for your lad-
der:
• The name and data type of every variable, contact, coil, function block,
structure and array used.
• The location of every physical input or output used.
• The initial or default value of any entry if required.
• The retentive, global, external, or UDFB in or out attribute of any variable
if required.
• A descriptive long name if desired.
You can perform the following editing functions in the Software Declarations table:
• Inserting and deleting entries
• Finding declared entries
• Cutting, copying, and pasting entries
• Purging the table of entries that are not used in your ladder
Entering Software Declarations

There are several ways to access the Software Declarations table in order to declare
entries.
• Select the button from the view navigator toolbar.

• Select View | Software Declarations... from the menu.
• When you enter a new variable in your ladder and it has not been declared
yet, answer Yes to this dialog and the Software Declarations table will
appear.
Press the Insert key to add a new variable to the table.
You can add a variable to the declarations. There are six columns in the table in
which you enter information.

• The name and data type of every variable, contact, coil, function block,
structure and array used must be entered in the Name and Type columns.
• If required, the retentive, global, external, or UDFB in or out attribute of
any variable is entered in the A. (or Attribute) column.
• The location of every physical input or output used is entered in the I/O
Point column.
• The initial or default value of any entry, if required, is entered in the Initial
Value column.
• A descriptive long name, if desired, can be entered in the Long Name col-
umn.
Names and Long Names of Variables

Names
In the Name column of the Software Declarations table, type in up to 63 alphanu-

meric/underscore characters.
• The first character must be alpha (A-Z, a-z) or the underscore (_).
• The 2nd through 63rd character can be alpha, numeric (0-9), or underscore.
• Mixed case characters are allowed.
Note: No distinction is made between names having the same characters with
different case (e.g. Switch1 and SWITCH1). If there is an existing vari-
able named SWITCH1 and a new variable named Switch1 is inserted, an
error message box will be displayed indicating there is already another
variable with the same name.
If the name is changed in this column, every occurrence of the variable in your lad-
der will be changed. The only exception is a ST Network that contains syntax
errors. In this case the name may not be changed.
Long Names
Since the release of PiCPro for Windows V13.0, Long Names are no longer
required. This column is being retained for ladder files created with versions of
PiCPro prior to V13.0.
In the Long Name column, you can add a long name to any variable used in a net-
work. Long names can have up to 40 ASCII characters on four lines (10 per line).
You can view, edit or add a long name to a variable in a LD network or to the Long
Name column in the Software Declarations table. When you add or change a long
name for a variable in a network, PiCPro automatically updates the Long Name
column in the Software Declarations table and vice versa. You can choose to dis-
play or hide the long names in your LD Networks.

Reserved Keywords
The following are reserved Keywords that are not allowed as variable names:
ACTION ADD AND ANDN
ARRAY AT BOOL BY
BYTE CAL CALC CALCN
CASE CONFIGURATION CONSTANT D
DATE DATE_AND_TIME DINT DIV
DO DS DWORD ELSE
ELSIF END_ACTION END_CASE END_CONFIGURATION
END_FOR END_IF END_FUNCTION END_FUNCTION_BLOCK
END_PROGRAM END_REPEAT END_RESOURCE END_STEP
END_STRUCT END_TRANSITION END_TYPE END_VAR
END_WHILE ENO EQ EXIT
FOR FROM FUNCTION FUNCTION_BLOCK
F_EDGE GE GT IF
INITIAL_STEP INT JMP JMPC
JMPCN L LD LDN
LE LINT LREAL LWORD
LT MOD MUL N
NE NOT OF ON
OR ORN P PROGRAM
R READ_ONLY READ_WRITE REAL
REPEAT RESOURCE RET RETURN
R_EDGE S SD SINT
SL ST STEP STN
STRING STRUCT SUB TASK
THEN TIME TIME_OF_DAY TO
TRANSITION TYPE UDINT UINT
ULINT UNTIL USINT VAR
VAR_ACCESS VAR_EXTERNAL VAR_GLOBAL VAR_INPUT
VAR_IN_OUT VAR_OUTPUT WITH WHILE
WORD XOR XORN

If you attempt to enter a variable name that is a reserved keyword (e.g. ACTION),
the following message will appear:
Choose OK and enter a variable name that is not a reserved keyword.
I/O Points
In the I/O Point column, enter the location of physical inputs and outputs only.
• For hardware modules located in the master or expansion rack,
the rack and slot location of the module and the channel location of the input or
output are defined. The hardware module must be declared in the Hardware
Declarations table.
• For block I/O modules, the block number and the point number are defined.
• For ASIU I/O modules, the ASIU number and the point number are defined.
The data type in the Type column must be boolean in order to enter information in the
I/O Point column.
The format of I/O points defined in software declarations is different based on the
CPU type declared in hardware declarations. The definition of Block I/O points is
unaffected by CPU choice.
Note: I/O point information that applies to the standalone MMC CPU also applies to
the standalone MMC PLUS CPU.
Standalone MMC I/O Points
Both PiCPro Professional and the MMC-Limited Edition allow you to copy and
paste the I/O information to the Software Declarations table from the Hardware
Declarations table. This can be done for the I/O on the MMC CPU module and the
MMC analog servo module.
The information can be copied by doing the following:
• Select the CPU (Slot 2) or Analog Servo Module (any slot) in the Hard-
ware Declarations table.
• Right-click and choose Copy I/O to Clipboard.
• Close the Hardware Declarations table and view the Software Declarations
table.
• Paste the information into the Software Declarations table.
All necessary information will be entered in the Software Declarations table.

Below is a list of the I/O Point labels for the general connector on the MMC CPU
module and for the axis and auxiliary connectors on the analog module. The infor-
mation in column 2 will be pasted in the Name column and the information in col-
umn 3 will be pasted in the I/O Point column of the Software Declarations table.
In the following table, ‘#’ represents the slot number.
Discrete point Declared Name Software Declaration I/O assign- PiC I/O Point
ment
(MMC I/O Point)
16 general DC Inputs GENI1–GENI16 IGEN.1 through IGEN.16 13.1 - 13.16
16 general DC Outputs GENO –GENO16 OGEN.1 through OGEN.16 O3.1 - O3.16
2 short circuit Inputs SHORT1-SHORT2 ISGEN.1 through ISGEN.2 I3.17 - I3.18
6/12 auxiliary DC Inputs AUXI#_1-AUXI#_12 IAUX#.1 through IAUX#.12 Is.1 - Is.12
Axis 1 DC input AX1RDY# I#A1.1 (Slot #, Axis 1, Input 1) Is.13
Axis 2 DC input AX2RDY# I#A2.1 Is.14
Axis 1 DC output AX1EN# O#A1.1 (Slot #, Axis 1 Output 1) Os.1
Axis 2 DC output AX2EN# O#A2.1 Os.3
Axis 1 DC output AX1RES# O#A1.2 (Slot #, Axis 1 Output 2) Os.2
Axis 2 DC output AX2RES# O#A2.2 Os.4
In the PiC I/O Point column, s represents the slot number. Where the slot number
is 4 if the Analog Servo module was in slot 1, or slot number of the Analog Servo
Module +2 if the Analog Servo module was in slots 3 through 6.
Note: The PiC I/O Point column is what will appear in the software declarations
if you later change your CPU from standalone MMC to a PiC CPU type. Always
check the I/O points after changing CPU types to be sure the I/O mappings match
your system.
Note: If you later change the CPU type in hardware declarations, the I/O points
will automatically change in software declarations.

Fast Inputs
The following I/O points can be manually entered in software declarations.

Where # represents the slot number.
Discrete point Declared Software Declaration I/O assignment
Name (MMC I/O Point)
Axis 1 fast input AX1FIN# IFAUX#.1 (aux port, Axis 1, Fast Input)
Axis 2 fast input AX2FIN# IFAUX#.2
Axis 49 fast input DIGFIN# IFAUX#.49 (aux port, Digitize 49, Fast Input)
Expansion input (future) I3.1 – I3.x
MMC for PC I/O Points
PiCPro Professional Edition is used to program the I/O points for MMC for PC
CPU types. If an MMC for PC CPU is specified in the hardware declarations, all
I/O points in the software declarations must be MMC for PC I/O points.
I/O points can be manually entered or copied from one ladder to another. The
ASIU I/O points can be copied to the clipboard from Hardware Declarations table,
and pasted into the Software Declarations table. Note: Declarations for the Fast
Inputs available for each axis must be manually entered into Software Declarations
table. They cannot be copied to the clipboard from Hardware Declarations table.
ASIU I/O
The following table describes the MMC for PC, Analog Servo Interface Unit
(ASIU) I/O points. The information in column 2 is the default declared name
which will be pasted into the Name column if the ASIU I/O is copied to the clip-
board from Hardware Declarations table. The information in column 3 will be
pasted in the I/O point column. The ASIU number is included in both the declared

name and the I/O assignment. In the following table, “#” represents the ASIU
number.
Discrete point Declared Name Software Declaration I/O assignment PiC I/O Point
16 general DC Inputs GENI#_1 - GENI#_16 IGEN#.1 - IGEN#.16 Is.1 - Is.16
16 general DC Outputs GENO#_1 - GENO#_16 OGEN#.1 - OGEN#.16 Os.1 - Os.16
2 short circuit Inputs SHORT#_1 - SHORT#_2 ISGEN#.1 - ISGEN#.2 Is.17 - Is.18
6/12 auxiliary DC Inputs AUXI#_1 - AUXI#_12 IAUX#.1 - IAUX#.12 Is.19 - Is.30
Axis 1 DC Input AX1RDY# I#A1.1 (ASIU #, Axis 1, Input 1) Is.31
Axis 2 DC Input AX2RDY# I#A2.1 Is.32
Axis 1 DC Output AX1EN# O#A1.1 (ASIU #, Axis 1, Output 1) Os.17
Axis 2 DC Output AX2EN# O#A2.1 Os.19
Axis 1 DC Output AX1RES# O#A1.2 (ASIU #, Axis 1, Output 2) Os.18
Axis 2 DC Output AX2RES# O#A2.2 Os.20
In the PiC I/O Point column, s represents the slot number where the slot number is
the sum of the ASIU # and 5.
Note: The PiC I/O Point column contains the I/O that would be displayed if the
CPU in hardware declarations were changed from an MMC for PC CPU to a PiC
CPU.
Note: If you later change the CPU type in hardware declarations, the I/O points
will automatically change in software declarations.
MMC for PC Fast Inputs
The following I/O points can be manually entered in software declarations.

Where # represents the slot number.
Discrete point Declared Software Declaration I/O assignment
Name
Axis 1 fast input AX1FIN# IFAUX#.1 (aux port, Axis 1, Fast Input)
Axis 49 fast input DIGFIN# IFAUX#.49 (aux port, Digitize 49, Fast Input)
Numbering
The manner in which I/O points are displayed changes based on the type of CPU
selected in Hardware Declarations (PiC, standalone MMC, or MMC for PC).
PiC CPU
The master or CPU rack is #0. Expansion racks are numbered 1 - 7, where #1 is the
rack connected to the master, #2 is the rack connected to #1, etc. Slots are num-
bered left to right when facing the PiC rack. Slot 1 and slot 2 are reserved for the
CSM/CPU module. On an expansion rack, slot 2 is reserved for the I/O driver
module.
Master Rack, PiC CPU
Enter four to six characters.

1st I or O Input or Output
2nd 0-1 First digit of module slot number* (can omit if 0)
3rd 0-9 Second digit of the module slot number*
4th . (point) Used as a separator
5th 0-3 First digit of channel number** (can omit if 0)
6th 0-9 Second digit of channel number**
* Valid slot numbers are 3 - 13.
**Valid channel numbers are 1 - 64.
Example:
If the input is in the master rack at slot 4, channel 3, enter: I4.3
Expansion Rack I/O
Note: Expansion Rack I/O is only available if PiC CPU is chosen.

Expansion Rack I/O is not available for a standalone MMC or MMC
for PC CPU.
Enter six to eight characters.
2nd 1-7 Expansion rack number
3rd . (point) Used as separator
4th 0-1 First digit of module slot number* (can omit if 0)
5th 0-9 Second digit of the module slot number*
7th 0-3 First digit of channel number** (can omit if 0*)
*Valid slot numbers are 3 - 13.
Example:
If the output is from expansion rack #7 at slot 12, channel 10, enter: O7.12.10

Master Rack Standalone MMC CPU
(Three Options)
2nd AUX, FAUX Connector/Type
3rd 1-6 Slot number
5th 0-4 First digit of channel number
6th 0-6 Second digit channel number
OR
2nd GEN Connector/Type
3rd . (point) Used as a separator
5th 0-6 Second digit of channel number
OR
2nd 1-6 Slot number
3rd A1, A2, A3, A4 Connector/Type
ASIU I/O for MMC for PC CPU
(Two Options)
2nd GEN, AUX, FAUX Connector/Type
3rd 1-8 ASIU number
6th 0-6 Second digit channel number
OR
2nd 1-8 ASIU number
Block Expansion Rack I/O
Note: Block Expansion Rack I/O is only available for certain CPUs.

Enter five to seven characters.
1st B Block
2nd I or O Input or Output
3rd 0-7 First digit of module number* (can omit if 0)
4th 0-9 Second digit of the module number*
6th 0-6 First digit of point number** (can omit if 0)
7th 0-9 Second digit of point number**
*Valid block module numbers = 1 - 77.

**Valid point numbers = 1 - 64.
Example
If the input is in block I/O module 33, point 5, enter: BI33.5
Blown Fuse Status

The status of up to four fuses on an AC Output, DC Output, or a combination
I/O module can be made available to your ladder program. You declare the fuses as
inputs in the Software Declarations table.
On modules having both inputs and outputs, the points are numbered sequentially
(starting at 1 for inputs and starting at 1 for outputs) in the Software Declarations table
as shown in the two examples below.
The 24 V DC Output 16 point The 24V I/O 16/8 source module
module with four fuses with two fuses
Name Type I/O Point Name Type I/O Point
OUT1 BOOL O4.1 IN1 BOOL I5.1
. . . . . .
. . . . . .
. . . . . .
FB1 BOOL I4.1 OUT1 BOOL O5.1
FB3 BOOL I4.3 . . .
FB1 BOOL I5.17
FB2 BOOL I5.18
Short Circuit Detection

The status of the short circuit detection feature of the general DC outputs for the stan-
dalone MMC, the MMC for PC ASIU, and the block I/O output modules can be made
available to the ladder diagram. There is one circuit for each group of outputs. The
module’s hardware description defines how many output points are in a common elec-
trical group. You declare the circuit as an input in Software Declarations table.
16 point DC out Mixed (8 in/ 8 DC out)

Block I/O BI#.1 or 2 BI#.9
Standalone MMC ISGEN.1 or 2 not applicable
MMC for PC ISGEN#.1 or 2 not applicable

For example: If the short circuit input is from a 24VDC input and output block I/O,
module number 33, there is only one group of outputs, the detection input is 9, enter:
BI33.9
If the short circuit input is from the GEN outputs for a standalone MMC, there are two
groups of outputs (1 to 8 and 9 to 16), there can be two detection inputs: ISGEN.1 and
ISGEN.2. The detection input from an ASIU would also include the ASIU number.
Fast Inputs
PiC CPU
The fast inputs available on the encoder, resolver, and servo encoder hardware
modules can be declared as inputs in the Software Declarations table. The inputs
are:
For Channel 1 For Channel 2 For Channel 3 For Channel 4
X.1 X.3 X.5 X.7
Standalone MMC CPU
The fast inputs available on the standalone MMC can be declared as inputs in the
Software Declarations table. The inputs are (where # is the slot number):
IFAUX#.1 Channel 1 (AXIS 1)
MMC For PC CPU
The fast inputs available on the MMC for PC can be declared as inputs in the Soft-
ware Declarations table. The inputs are (where # is the ASIU number):
Initial Values
All variables have a default value of zero. By entering a value in the Initial Value column,
you can change the default value. Default values go into effect:
• For all variables when a cold restart is performed
• For variables that are not retentive, when a warm restart is performed
Note: An initial value cannot be set if the variable has an I/O point assigned to it.

Prefixes for initial values
The following prefixes are required for values in the formats listed.
Prefix Value Format
2# Binary
8# Octal
None Decimal
16# Hexadecimal
D# Date
TOD# TIME_OF_DAY
DT# DATE_AND_TIME
T# TIME
Working with Data Types in Software Declarations
When a variable is declared in the Software Declarations table, you assign a data
type to it in the Type column by entering in the type or selecting it from the drop-
down list. The data type categories and associated data types are listed below:
Bitwise Numeric String Time of day Time duration
BOOL SINT STRING DATE TIME
BYTE INT TIME_OF_DAY
WORD DINT DATE_AND_TIME
DWORD LINT
LWORD USINT
UINT
UDINT
ULINT
REAL
LREAL
Function/Function block Structures/Arrays

(Any Data Type) (Any Data Type)
Bitwise
Bitwise variables/constants are used to represent binary values. When manipulated,
these data types are treated as a series of binary digits.
Description Data Type # of Bits Range
A boolean value is a bit. Contacts and coils BOOL 1 0 or 1
are always represented by boolean vari- boolean
ables. 0 = off/no 1 = on/yes
Byte, word, double word, and long word values BYTE 8 eight 0s - 1s
are groups of bits that are used when logical WORD 16 sixteen 0s - 1s
and bit manipulation operations are performed. DWORD 32 thirty-two 0s - 1s
double word
LWORD 64 sixty-four 0s - 1s
long word

Bitwise values can be entered in binary, octal, decimal, or hexadecimal. The format for
entering these values is shown below for the number 23. (2#, 8#, and 16# are
required.)
Binary =2#10111 Octal =8#27 Decimal =23 Hexadecimal =16#17
Note: Bitwise constants are limited to 32 bit values. A constant can be entered for any
bitwise data type. For data types 32 bits or less, the constant value must be within the
range of the data type. For data types greater than 32 bits, the 32 bit constant value will
be extended. Zeros will be placed in the 32 most significant bits. The constant value
will be held in the least significant 32 bits.
When booleans are entered as constants, enter the following:
For: Enter:
On 1, (hex) 16#80, or (decimal) 128 can be used interchangeably.
Off 0
For boolean initial values, enter a 0 or 1.
Numeric
Numeric variables/constants are used to represent integers and real or floating point
numbers. When manipulated, these types of data are treated as numbers.
Description Data Type # of Range
Bits
Integers are whole SINT 8 -128 to +127
numbers or zero. short integer
INT 16 -32,768 to +32,767
integer
DINT 32 -2,147,483,648 to +2,147,483,647
double integer
LINT 64 -9,223,372,036,854,775,808 to
long integer +9,223,372,036,854,775,807
Unsigned integers USINT 8 0 to 255
are greater than or unsigned short integer
equal to zero. UINT 16 0 to 65,535
PiCPro will prevent unsigned integer
you from entering a UDINT 32 0 to 4,294,967,295
negative number for unsigned double integer
an unsigned integer. ULINT 64 0 to 9,223,372,036,854,775,807
unsigned long integer
Real numbers are REAL 32 significant digits 6-7
floating point num-
bers. They contain a LREAL 64 significant digits 15-16
decimal point and long real
an exponent indicat-
ing the power of ten
the number is to be
multiplied by to
obtain the value
represented.

String
String variables are used to represent a sequence of zero or more characters. The char-
acters are ASCII and /or extended ASCII.
Length in
Description Data Type bytes Range
(internal)
String type variables are used to read STRING Two plus num- 1 to 255 ASCII characters
or write messages. Every string has ber of
two extra bytes that hold information declared char-
about the string. The second byte tells acters
the actual length of the string.
Note: STRINGs cannot be entered

as constants.
String values are keyed in exactly as they are to be interpreted. A three character com-
bination of the dollar sign ($) followed by two hexadecimal digits is interpreted as the
hex representation of an eight-bit ASCII character code. A two character combination
of the dollar sign followed by a character is the ASCII interpretation given below.
Character String Interpretation
$$ dollar sign
$’ single quote
$L line feed
$N new line
$P form feed (page)
$R carriage return
$T tab
Time
Time of Day
Time of day values represent the time of day, the date, or both.
Description Data Type # of Range Examples
Bits
Date and time values are DATE 16 Jan.1, 1988 - Year/month/day
used when the date or time Dec. 31, 2051 D#1997-10-23
is to be printed, or when an TIME_OF_DAY 32 00:00:00 - Hours/minutes/ seconds
event is to be triggered at a 23:59:59 TOD#23:59:59
given moment in time. Val- DATE_AND_TIME 32 Same as the Year/month/day/hours/
ues can be assigned manu- two above, minutes/ seconds
ally or extracted from the PiC combined
clock (with functions). DT#1997-10-23-23:59:59

Time duration
A time (duration) value represents an amount of time.

Data # of
Description Type Bits Range Examples
Time duration values serve as TIME 32 0 - 49d17h2m47s295ms Days/hours/minutes/
inputs to timer functions for seconds/milliseconds
0 - 1193h2m47s295ms
counting up/down for a speci-
fied amount of time. They also 0 - 71582m47s295ms T#1d2h3m4s5ms
serve as outputs into which 0 - 4294967s295ms
elapsed time values are 0 - 4294967295ms
entered.
Values are entered as shown in the examples below where d = day, h = hour, m =
minute, s = second, ms = millisecond. T# is required and d, h, m, s, and ms are
required if the value for that increment is not zero.
T#1d3h7m16s45ms T#14d T#459871ms
Groups of data - Structures and Arrays

Variables can be grouped to create entities called arrays and structures. This ability to
group data enables you to keep various types of data together that have a common link.
Values can be read into or written from these groups with I/O functions. Also, individ-
ual variables in structures and arrays can serve as inputs to and outputs from Function/
Function Blocks.
Groups of variables can be handled by arrays, structures, structures with arrays, an
array of structures, and an array of structures with arrays.
Arrays
An array is a group of variables. Each variable in an array must be of the same data
type. Any data type is acceptable. An array can have from 2 to 999 variables.
These variables are called elements. Arrays are useful for handling large groups of
like data items.
• Only single dimensioned arrays are supported in PiCPro
• Array variables are identified with square brackets.
• Array subscripts follow the same rules in ST and LD. An array subscript
can be any variable or constant that evaluates to USINT or UINT. Array
subscripts can be nested if the variable name used in the subscript is
another array.
As an example, assume that you have a list of 200 rod part numbers. An array
could be used to store the list. Each part number is an element in the array. See the
table below:

An array of part numbers
PART NUMBER DATA TYPE
R101 STRING
R102 STRING
. .
. .
R199 STRING
R200 STRING
Declare an Array
To declare an array, follow these steps:

1. Choose one of the following methods to display the Software Declara-
tions dialog:
• Select the button from the view navigator toolbar

• Select View | Software Declarations… from the menu
• Right-click and select Software Declarations…
2. Enter the name and data type for the array you want to create.
In the example, RODS is the name and a STRING with 4 characters is the
data type.
Note: If all the elements in the array are to have the same value, enter the value in
Initial Value column now, before you create the array. That value will then appear
with each element in the array when it is declared. This will not be done for the
example, since each rod part number is different and will have to be entered indi-
vidually.
3. Choose one of the following methods to size your array:
• Select Tools | Make Array from the menu
• Press <Alt + A>
• Right-click and select Make Array

4. The Array Length dialog appears:
Enter the array length (a number between 2 and 999) in the dialog. Press
the Enter key to accept the value. For the example, 200 was entered.
5. The index numbers (0…x-1) will appear behind the data type of the vari-
able where x is the length specified.
In the example, x = 200 and the index numbers will be 0 through 199 as
shown below:
The word ..ARRAY.. will be displayed in the initial value field if the ini-
tial value for any element in the array has been entered.
6. To initialize or change the initial values of the elements in the array, move
the cursor to the Initial Value field and press the Enter key. If no initial
value was entered before the array was declared, then there will be no value
for any elements. If an initial value was entered before the array was
declared, that initial value will be duplicated for all elements in the array.

7. To enter values, either click on a field or use the up and down arrow keys
to move to the desired location and type in the value you want.
In the example, you would type in R101 at [0], R102 at [1], R103 at [2]
through R200 at [199].
8. When the values have been loaded, select OK to accept the values, select
Cancel or click on button to exit the dialog without saving the values
or select Help to display information related to initial values.
9. The word ..ARRAY.. will display in the Initial Value column for any ele-
ment that has been entered or changed.
Resize an Array
To resize an array, follow these steps:

1. Choose one of the following methods to display the Software Declarations
dialog:

2. Click anywhere on line of the variable declaration.
3. Choose one of the following methods to resize your array:
• Press <Alt + A>
4. Enter a new array length. Press the Enter key to accept the new value.
5. The index numbers displayed behind the variable in the Type column will be
updated.
6. To initialize or change the initial values of the added elements in the array,
move the cursor to the Initial Value field and press the Enter key.
Note: If the array length is increased, the added elements will have the same
value as the first element (index 0).
In the example, each added element beyond [199] would have the value of R101.

Remove an Array
To remove an array, follow these steps:

dialog.

2. Click anywhere on line of the variable declaration.
3. Choose one of the following methods to remove your array:
• Press <Alt + A>
4. Enter an array length of 1. Press the Enter key to accept the new value.
5. The index numbers previously displayed behind the data type of the variable
will be removed.
6. The initial value, if any, will be displayed in the Initial Value column instead
of the word ..ARRAY...
Referencing and accessing elements of arrays in the module
Array elements are referenced according to the position of the element within the
array. The positions are numbered 0 through x-1, where x is the number of ele-
ments. The position numbers are called index numbers and they act as pointers to
the elements. To access an element, you enter the name of the array and the index
number of the element.
One of the powerful features of arrays is that the index number can be a variable
(USINT or UINT). By using a variable and changing its value, you are able to
access every element in the array with a minimal number of commands.
IMPORTANT
Be careful to enter the correct index number for the element you want.
PiCPro does not prevent you from entering an invalid number. If an
index number is greater than “x-1,” a memory location after the array
will be accessed. The results are unpredictable.

The index number is entered in brackets after the array name. For the example
array, the name RODS followed by constants or a variable called RODNUM can
be used to index the array as shown below:
Name with constant or variable Contents of each element Data Type
RODS [0] or RODS [RODNUM] R101 string

. . .
Structures
A structure is a group of variables where the variables can be of any data type
except another structure. Each variable that comprises a structure is called a mem-
ber. A structure can have an unlimited number of members.
NOTE: When booleans are used as data types in structures, each boolean occupies
a byte of memory and more scan time is required. It is the most significant bit of
the byte that indicates the state of the boolean.
When you declare a structure you are creating a template or framework for a group
of data items.
As an example, assume that you have some information about a rod part that you
want grouped together. The data consists of a part number (PART), a description
of the part (DESC), its diameter (DIAM), the first operation on the part (OPER)
and the time it takes to perform the operation (TIM1).
You could create a structure with five members, depicted below:
Member name PART DESC DIAM OPER TIM1
Member data R101 class A rod 126 deburr 15m
Data type string string usint string time
Declare a Structure
To declare a structure, follow these steps:

dialog:

2. Enter its name.
For the example, the name will be ROUTING.
3. Move to the Type column.

4. Use the dropdown list and select STRUCT.
The screen will display the following:
The END_STRUCT type is entered automatically by PiCPro.

5. Enter the members for the structure.
For the example, there will be five members entered.
Click in the Name field on the END_STRUCT line.
6. Choose one of the following methods to activate Insert mode:
• Select Edit | Insert from the menu
• Press the Insert key
• Right-click and select Insert.
7. Enter the member name, type, etc. as you would for any variable.
Note: A dot or period will be automatically inserted before the member name
by PiCPro. All member names (and only member names) start with a period.
Members can be any data type except another structure.
Referencing and accessing member of structure
To reference a member or access the data, enter the structure and member names,
separated by a dot or period.
For the ROUTING structure with the members PART, DESC, DIAM, OPER and
TIM1, the names on the left are used in the module:
Name used to reference member Contents of the member Data type assigned
ROUTING.PART R101 string

ROUTING.DESC class A rod string
ROUTING.DIAM 126 usint
ROUTING.OPER deburr string
ROUTING.TIM1 15 time

Structures with arrays
A structure with arrays is a structure where one or more members are arrays of
data. Given the definitions and requirements of arrays and structures, it follows
that for a structure with arrays:
1. Each element in an array must be the same data type.
2. Each array can be a different data type.
3. The arrays can have different numbers of elements.
As an example, assume that for the structure shown earlier the information for that
part is expanded to include data about four diameters, operations and times. This
is depicted in the following table of a structure that has three members which are
arrays: DIAM, OPER and TIME.
PART DESC DIAM OPER TIME
R101 class A rod 126 deburr 15m

122 polish 30m
124 plate 90m
123 polish 30m
Declare structures with arrays
A member of a structure is made into an array the same way that any variable is
made into an array.
With the cursor in any field on the member line, choose one of the following meth-
ods to display the array length dialog:
• Press <Alt + A>
Enter the array length. Press the Enter key to accept the value.
Also, initial values are assigned the same way that they are for arrays. Click in the
Initial Value field of the member and press the Enter key.
DIAM, OPER and TIM1 in the example are new arrays with four elements each.
Note: The initial value of one or more of their elements has been changed

Referencing and accessing data in a structure with arrays
Since an array in a structure is a member, the entire array is accessed as any mem-
ber of a structure is accessed. Enter the structure name and member name, sepa-
rated by a dot or period.
The lowest level of data in a structure with arrays is an element in an array. To
access or reference an element you use a combination of the methods used to
access elements of arrays and members of structures. Input the name of the struc-
ture, the name of the member and an index number for the array element.
For the structure with arrays discussed in this topic, where the structure is named
ROUTING, array element data is accessed as follows:
Con- Con- Con-
DIAM elements
tents OPER elements tents TIME elements tents
ROUTING.DIAM[0] 126 ROUTING.OPER[0] deburr ROUTING.TIM1[0] 15
ROUTING.DIAM[1] 122 ROUTING.OPER[1] polish ROUTING.TIM1[1] 30
ROUTING.DIAM[2] 121 ROUTING.OPER[2] plate ROUTING.TIM1[2] 90
ROUTING.DIAM[3] 123 ROUTING.OPER[3] polish ROUTING.TIM1[3] 30
Note: A variable instead of a constant can be used for the index number.
Array of structures
An array of structures is an array whose elements are structures. By definition of

an array (that each element has the same data type) each structure in the array has
the same format, i.e., if the first member of a structure is a string, then the first
member of all the structures in the array is a string, etc.
As an example, assume that for the array and structure described previously, you
want to have the structured data for all 200 parts. This is depicted in the following
table. Data for only 2 of the 200 parts is shown.
. . . . .
. . . . .
. . . . .
. . . . .
R200 class B rod 113 deburr 20m
Declare an array of structures
To declare an array of structures, follow these steps:

1. Declare the structure as previously described. Add member information
(Names, Types, etc.).
2. Click any field in the line with the structure Name (ROUTING for the exam-
ple).

3. Choose one of the following methods to size your array:
• Press <Alt + A>
The length of the array appears by STRUCT.
4. To initialize members, click the Initial Value field of the desired member and
press the Enter key.
The Change Initial Values dialog appears:
A single element appears with its members. You can use the directional buttons
or the element tabs near the bottom of the dialog to move to the next element.
5. Click in the value field of the member. Type the value.
6. Use one of the following methods to move to the next member value field:
• Click in the value field of the next member.
• Use the up/down arrow keys.
• Press the Enter key.
7. When the values have been loaded, select OK to accept the values, select Can-
cel or click on button to exit the dialog without saving the values or select
Help to display information related to initial values.

Referencing and accessing data in an array of structures
Since a structure in an array is simply an element in the array, the entire structure is
accessed as any element in an array is accessed. Enter the name of the array and
the element's index number.
The lowest level of data in an array of structures is a member in one of the struc-
tures. To access a member, use a combination of the methods used to access mem-
bers of structures and elements of arrays. Input the name of the structure, (all
structures in an array have the same name), its index number, a dot or period and
the name of the member.
For the array of structures previously discussed, where the structures are named
ROUTING, data is accessed as follows:
To access members in To access members in To access members in

the first structure, enter the second structure, the last structure, enter
this enter this this
ROUTING[0].PART ROUTING[1].PART ROUTING[199].PART
ROUTING[0].DESC ROUTING[1].DESC ROUTING[199].DESC
ROUTING[0].DIAM ROUTING[1].DIAM ROUTING[199].DESC
ROUTING[0].OPER ROUTING[1].OPER ROUTING[199].OPER
ROUTING[0].TIM1 ROUTING[1].TIM1 ROUTING[199].OPER
Array of structures with arrays
An array of structures with arrays is an array of structures each of which has one or
more members, which are arrays of data. This is the most complex representation
of data that can be created for the control. It combines the four types of groups of
data - structures, arrays, arrays of structures and structures with arrays.
Building upon the previous examples, assume that structured data is to be created
for the 200 parts, and that each structure should contain the arrayed data for four
operations. The following table depicts the array of structures with arrays. Only 2
of the 200 elements are shown.
. . 122 polish 30m
. . 124 plate 90m
. . 123 polish 30m
.
110 polish 45m
112 plate 120m
111 polish 30m

Declare an array of structures with arrays
Declaring an array of structures with arrays is explained in declare a structure,

declare an array and declare structures with arrays.
The initialization of arrays of structures with arrays is the same as described for
arrays of structures with an additional step for a member, which is an array. That
array is initialized like other arrays are initialized.
In the following example, the DIAM member has been declared an array. To ini-
tialize the elements in the array, click the Initial Value field on the DIAM line and
press the Enter key.
The Change Initial Values dialog appears:
Referencing and accessing the data in an array of structures with arrays
An array of structures with arrays is accessed in the same way that a member in an
array of structures is accessed.
The lowest level of data in an array of structures with arrays is an element in an
array. To access an element, you use a combination of the methods used to access
members and arrays. Input the name of the structure, its index number, a dot or
period, the name of the member and the index number of the element.

For the array of structures with arrays discussed here, where the name of each
structure is ROUTING, the diameter data is accessed as follows for part #s R101
and R200.
To access diameter data To access operation data
for part # R101, enter for part # R200, enter
this: Contents this: Contents
ROUTING[0].DIAM[0] 126 ROUTING[199].OPER[0] deburr

ROUTING[0].DIAM[1] 122 ROUTING[199].OPER[1] polish
ROUTING[0].DIAM[2] 124 ROUTING[199].OPER[2] plate
ROUTING[0].DIAM[[3] 123 ROUTING[199].OPER[3] polish
Attributes
You can assign a retentive, global, global and retentive, external, variable in or vari-
able out attribute to a selected variable in the Software Declarations table. The global,
global and retentive, and external attributes are used when the DOS LDO Merge fea-
ture is used to merge multiple LDOs. The external attribute is also used for TASKS.
Variable in and variable out attributes are used with UDFBs.
You access attributes for a selected variable with one of the following methods:
• Tab to the A (Attributes) column and click,
• Select Tools | Modify Attributes from the menu.
• Right-click and select Modify Attributes.
Clear will remove an attribute from a selected variable as will Delete. Also, if the
selected field is in the A (Attributes) column, you can enter E for External, I for Vari-
able In, O for Variable Out, G for Global, R for Retentive or B for Both Global
and Retentive.
Retentive Attribute
The retentive attribute makes the selected variable retain its value upon a warm
restart or power cycle, but not on a cold restart. Physical I/O points and individual
structure members cannot be made retentive. All other elements, including entire
structures, can be made retentive. Note: Retentive memory is limited to 24K.
Global Attribute
The global attribute is used when an operator interface device or DOS LDO merge
is being used.
When an operator interface device is used, the global attribute identifies the vari-
able as one to be used by the operator interface device.
When DOS LDO merge is used, it identifies the selected variable as the master or
global variable. Any variable with the same name in other LDOs will inherit this
variable’s definition (data type, I/O point, initial value) when the LDOs are
merged.

Both Global and Retentive Attribute
The both global and retentive attribute is used when DOS LDO merge is being
used. It identifies the selected variable as the master or global variable and as
retentive.
External Attribute
The external attribute is used when DOS LDO merge is being used or when the
TASK feature is used. It signals PiCPro that this variable is used in more than one
LDO, and that the variable’s global definition is in another LDO. If the properties
of this variable (data type, I/O point, initial value) differ from the properties of its
global counterpart, the variable will acquire the properties of the global variable
when LDOs are merged.
The external attribute is also applied to a TASK variable that is to be shared with
other tasks. Only mark the variable as External in the TASK.LDO, never in the
main LDO in which the TASK is called.
In and Out Variable Attributes for UDFBs
Variable In designates the variable as an input to a UDFB. When the LDO you are
creating will be converted to a UDFB, every variable you want to use as an input to
the UDFB must have this attribute.
Note: The first variable with the I attribute in the Software Declarations table will
become the EN input of the UDFB. Its data type must be BOOL. Additional
UDFB inputs should be entered in the order you want them to appear on the left
side of the function block.
Variable Out designates the variable as an output to a UDFB. When the LDO
module you are creating will be converted to a UDFB, every variable you want to
use as an output from the UDFB must have this attribute.
Note: The first variable with the O attribute in the declarations table will become
the OK output for the UDFB. Its data type must be BOOL. Additional UDFB out-
puts should be entered in the order you want them to appear on the right side of the
function block.
Editing Software Declarations
If you need to add or edit declarations, you can use the following tools:
• Inserting and deleting in the Software Declarations table
• Cutting, copying and pasting in the Software Declarations table
• Searching in the Software Declarations table
• Purging unused variables from the Software Declarations table.

Inserting/Deleting Software Declarations
You can insert and/or delete entries to the Software Declarations table when it is
active.
To insert software declarations, follow these steps:
1. Click in the table and press the Insert key or select Tools | Insert Symbol from
the menu. A new row will appear above the row the focus was in. If focus is on
the end list, you can either press the Insert key or simply begin typing. A new
row will be inserted.
2. Enter the name of the new entry in the Name column and press the Enter key.
This accepts the name and moves the focus to the Type column.
3. Typically, the Type column will automatically have the same data type as the
previous entry or, if there is no entry, the type defaults to BOOL. If the previ-
ous entry is a BOOL type with an I/O point assigned, the new entry will have
an incremented I/O point assigned to it. If the new entry has a different data
type you must enter the new data type.
4. Enter information in the remaining columns if required.
5. To accept changes to the Software Declarations table, select File | Save and
Close from the menu or press the F10 key. To exit without saving any changes,
select File | Close or press the Esc key.
To delete software declarations, follow these steps:
1. Click in the Name column of the table (or highlight the entire row) of the entry
you want to delete.
2. Select Edit | Delete or press the Delete key. A confirmation box will appear.
You can choose Yes, No, or Cancel. If you choose Yes, the entry will be
deleted if it is not used in the ladder file.
Cutting, Copying, and Pasting Software Declarations

You can cut or copy and paste items within the Software Declarations table or from the
Software Declarations table of one ladder file into the Software Declarations table of
another ladder file.
To cut software declarations, follow these steps:
1. Make the Software Declarations table active.
2. Highlight the entry you want to cut. You can highlight a row in the table by
placing the arrow in the small rectangle region (marked below) until the
pointer arrow becomes a horizontal black arrow pointing to the row. Then click

to select the row. See How to Select Multiple Entries below for more than one
entry.
3. To put the selected information on the clipboard, use one of the following
methods:
• Select Edit | Cut from the menu
• Press <Ctrl + X>
If the entry is not referenced in the ladder file, the entry is removed from the table.
If the entry is referenced in the ladder file, the entry is grayed and is not removed
from the table. If the entry is a structure and the structure or any of its members are
referenced in the ladder file, the entire structure will be grayed. The entry will
remain grouped until it is pasted into a new location in the same declarations table
or until Software Declarations table is closed.
To copy software declarations
1. Make the Software Declarations table active.
2. Highlight the entry you want to copy. You can highlight a row in the table by
placing the arrow in the small rectangle region (marked below) until the
pointer arrow becomes a horizontal black arrow pointing to the row. Then click
to select the row. See How to Select Multiple Entries below for more than one
entry.
3. To put the selected information on the clipboard, use one of the following
methods:
• Select Edit | Copy from the menu
• Press <Ctrl + C>
How to Select Multiple Entries
Multiple entries can be selected at the same time if they are part of the same Soft-
ware Declarations table.

• To select entries next to each other, select an entry, hold down the Shift key
while pressing the up/down arrow or hold down the Shift key and select
another value. The entire block of entries will be displayed as selected.
• To select entries not next to each other, select an entry then hold down the
Ctrl key while left-clicking the other desired entries.
To paste software declarations in another table, follow these steps:
1. Make the Software Declarations table that you want to paste in active.
2. Click anywhere in the table. When you issue the paste command, the paste will
be inserted in the row above where you click. If you want to replace a row,
highlight the row and then paste.
3. To put the clipboard into the table, use one of the following methods:
• Select Edit | Paste from the menu
• Press <Ctrl + V>
Note: If a ladder has a different CPU declared than the one into which you are
pasting the software declaration, the I/O points will be changed.
Reserved Keywords when pasting
If you attempt to paste a variable name that is a reserved keyword, the following
error message will appear:
This message displays the variable that cannot be pasted. Enter a variable name
that is not a reserved keyword and use the appropriate control button.
Control Button Description
Click this button and the dialog box closes. The variable name
OK
entered is validated.
Click this button and the dialog box closes. The variable is
Skip removed from the paste list and is not pasted. All the other vari-
ables will be pasted.
Cancel Click this button and the dialog box closes. Nothing is pasted.
Help Click this button and Help information is displayed.

Duplicate Symbols when Pasting
If you attempt to paste software declarations or networks into another ladder and
the symbols have the same name, type, and array status, the following box appears
with the first symbol in the paste listed in the Symbol Information area. You can
choose to skip the paste of this symbol, use the source (where you are copying
from) definition, the target definition (where you are pasting to), or change the
source name.
If the symbols have the same name, type, and array status and you choose to use
the target definition, the resulting array size could be smaller. Initial values could
change. No attempt is made to make sure one of the array elements being removed
is not referenced in the ladder.
Symbol Information
This area displays information about a duplicate symbol that was
encountered while pasting. It shows the name, type, Attributes, I/O
point, initial value, and long name of the duplicate symbol from the
source and from the target.
Source:
The source is the ladder you are cutting or copying from.
Target:
The target is the ladder you are pasting into.
Note: The source and target can be the same ladder if you are cutting,
copying, and pasting in that ladder's Software Declaration table oth-
erwise they are two distinct ladders.
Skip paste of this symbol
Select this option to skip the paste of this symbol. This will leave the
pasted ladder element unnamed.

Change Source Name
Select this option to alter the name of the duplicate symbol in the
source ladder. Enter the new name in the field provided.
Use Source Definition
Select this option to use the source ladder’s definition for this duplicate
symbol.
Note: If the symbols have the same name, type and array status and
you choose to use the source definition or the target definition, the
resulting array size could be smaller. Initial values could change. No
attempt is made to make sure one of the array elements being removed
is not referenced in the target ladder.
Use Target Definition
Select this option to use the target ladder’s definition for this duplicate
symbol.
Use target definition for all remaining duplicate definitions
Select this option to the target ladder’s definition for this and all
remaining duplicate symbols found.
OK
Click this button after entering the required information to insert this
symbol.
Cancel
Click this button to cancel the paste. Nothing will be pasted.
Help
Click this button to display help for this dialog.
Searching in the Software Declarations Table

You can search for entries in the Software Declarations table using the Find command.
The search will begin at the row that has focus and proceed in the specified direction.

Choose one of the following methods to initiate a search:
• Select Edit | Find from the menu.
• Press <Alt + F3>.
The box below appears and you enter the criteria you want to base your search on.
Find by Name Only
The default is to search by name only.

1. In the Filter By: area, select the Name Only: button if it is not already
selected.
2. Enter the name or portion of a name with Left Match selected (Left Match is
not case sensitive) in the Name: box. The list accessed through the down arrow
will hold all the declared variable names. You may choose from this list if
applicable.
Find by Type
To search by data type:

1. In the Filter By: area, select the Type: button. This will enable the Filter: box.
2. Choose a data type from the drop down list in the Filter box. If you are search-
ing for a function block, click on the fb button and select a function block from
the displayed menu.
Find by I/O Point
To search by I/O point:

1. In the Filter By: area, select the I/O Point: button. This will enable the Filter:
box.
2. Enter an I/O point in the Filter box. The list accessed through the drop down
arrow will hold the most recently searched for points. You may choose from
this list if applicable.

Once you have entered the criteria by which you want to search, click on the Find/
Next button to begin. The focus will move to the row with the first occurrence of
the declaration.
Using the Find Next Command
You can find the next occurrence of the declaration by clicking the Find/Next but-
ton again or by pressing the F3 key, if you have closed the Find dialog.
Purging Unused Variables from the Software Declarations Table

You can remove any variables from your Software Declarations table that are not
being used in the ladder with the Purge Unused command.
To purge unused variables, choose any of the following:
• Select Tools | Purge Unused from the menu
• Press <Alt + P>
• Right-click and select Purge Unused

Working with Networks and Network Elements
Your ladder file consists of executable networks entered by you. They hold the ladder
logic commands and/or structured text that run your application. They are numbered
sequentially by PiCPro as you enter them. The networks are executed in this numerical
order unless a jump command forces execution to be out of sequence.
PiCPro supports two types of networks: LD (Ladder Diagram) and ST (Struc-

tured Text). A network can be either LD or ST but not both.
Execution of the ladder logic and commands occurs left to right, top to bottom within the
network. When entering network elements, you must enter them in the order you want
them to carry out their function, starting from the left and proceeding to the right. The split
screen feature can be used to view large networks.
A label can be added to a network element to facilitate jumps. Comments can be added to
networks to allow for easier identification, or convey other information about the network
both on screen and when the ladder is printed.
Network Size
LD Network Size
A LD network is comprised of a matrix of rectangles (outlined by dots) called
cells. Each cell is approximately the size of the cursor. Each element in the net-
work occupies at least one cell. Elements, like functions, can occupy several cells.
A PiCPro LD network accepts a network with an area of 1 to 255 cells. The area of
the network is the sum of the product of its width (number of columns in widest
row, excluding last row) and its length (number of rows - 1) plus the width of the
last row.
A portion of a LD network is shown below. The cursor on the right occupies one
cell in the network. Note the dots that mark each cell. The function on the left
occupies four vertical cells.

ST Network Size
The ST element is dynamically resized to fit the viewable grid.
• If Enter key is pressed to move the caret to a new line, the Structured Text
element will expand its vertical size to accommodate one additional line of
text.
• Entering and deleting rows of characters along with cut and paste and
menu selections that insert text (e.g. constructs) will cause resizing of the
ST element.
The maximum number of lines in a ST network is 500. Each line is limited to 500
characters. If a line exceeds the 500 character limit, a message will be displayed
indicating the character limit. Furthermore, a ST network is limited by the code it
generates.
At this time the network will have to be split and a new ST network started. If you
want to continue writing the current structured text network, it must be continued
in the new network. Any loop or IF/THEN constructs must be closed in the first ST
network; they can not be continued in the next network.
Network Labels in Networks

You can label a network with the Label command found in the Ladder menu, submenu
Network. You must assign a label to any network you want to jump to. If a Jump com-
mand is in a network and there is no network with the designated label, an error mes-
sage will appear when you attempt to download the module.
A label is one to eight characters long. The characters must be alphanumeric or under-
score. Note: The first character cannot be numeric.

To assign or edit a label on a network, follow these steps:
1. Place the cursor in the network you want to label.
2. Select Ladder | Network | Label from the menu.
3. A text box appears next to the network number. Type in the label you want or
edit an existing one.
Comments in Network Elements

Up to 100 lines (80 characters long) of comments (documentation) can be added to a
network element. The comments appear directly under the network number line. You
can choose to display one or more comment lines as you work in your ladder.
To add comments to your ladder, follow these steps:

1. Select Edit | Properties from the menu.
2. Select the Network tab. Type in the comments you want for the network you
are working in.
To choose the number of comment lines to display, follow these steps:

1. Select View | Options from the menu.
2. Select the User Preferences tab. In the Ladder View Preferences box, enter
the number of comment lines you want displayed at each network.
Note: Although you can choose to display up to 100 comment lines, they
will not all display at the same time. To see all the lines you must
double-click in the comment display box. This takes you to the com-
ment editor where you can see all the comments. To exit the com-
ment editor, choose Cancel.
Constants and Variables in Network Elements

All data elements in your ladder that can be read from or written to are in the form of
variables or constants. A read element can be a variable or a constant. A write element
must be a variable.
Constants
• Constants can be used as input values to function/function blocks.
Note: In a LD network, constants cannot be entered anywhere else in the
network.
• Constant values must be entered in the same form and within the same range a
variable value would be entered in the Software Declarations table.
• Strings cannot be represented as constants. String constants are defined in Soft-
ware Declarations via a variable and then referenced within the ladder file.

Variables
Variables are used in four ways:
• As input values to function/function blocks
• As output values from function/function blocks
• As values that represent the states of contacts and coils in a LD network.
• In expressions in a ST network.
Variables must be declared in the Software Declarations table. There you define
the following:
• A name for the variable
• The data type of the variable
• The initial value for the variable if it is different than the default 0
• The hardware module location if the variable is a physical input or output
• Any attributes that apply to the variable
Variable Names in Networks

Names
See Names and Long Names of Variables in the Software Declarations
section of this chapter for an explanation of variable names.
In a LD network, if a variable name does not fit within its cell and there are
empty cells or cells containing only horizontal wires to the left, the variable
name will extend into the cells to the left (this is not true for Function
Blocks and Task names). The cells to the left will not be included when the
variable name is selected. If a single cell is selected and it contains a vari-
able name, the variable name will be displayed in the status line.
Long Names
See Names and Long Names of Variables in the Software Declarations
section of this chapter for an explanation of long variable names.
When editing a long name, <Ctrl + Tab> can be used to move focus from
the long name edit control to the OK button.
To add/edit long names in a LD network, follow these steps:
1. Place the cursor on the variable you want to add/edit a long name.
2. Select Edit | Properties from the menu.
3. Select the Symbol tab.
4. Enter/edit the long name and click OK.
To view long names in a LD network, choose one of the following methods:
1. Click button on the View Navigator toolbar.

Note: All cells in your ladder file increase in size when you display
Long Names.
2. Select View | Options from the menu.
• Select the User Preference tab.
• In the Hide box, be sure the Symbol Long Name is not
checked.
• Click OK.
LD Elements
The elements that go into creating a LD network include contacts, coils, wires, func-
tions/function blocks, data, jumps, variables and constants.
Contacts
Contacts are boolean elements that represent hard wired circuitry or internal logic
in the ladder. Each boolean element must be assigned a boolean variable declared
in the software declarations table. The variable holds the value of the state of the
input. If the input is OFF or deenergized, the value is 0. If the input is ON or ener-
gized, the value is 1. If the element is a physical input, its location must also be
declared.
Buttons Contact Types
Normally Open
Normally Closed
Positive transition, normally open
Positive transition, normally closed
Negative transition, normally open
Negative transition, normally closed
Note: Transition contacts pass power until the next update of

the coil. Depending on the logic in your ladder, this may not
equal one scan.
Normally Open Contact

Variable = 1 The power flow/logic continuity is provided.
Variable = 0 The power flow/logic continuity is not provided.
Normally Closed Contact

Variable = 1 The power flow/logic continuity is not provided.
Variable = 0 The power flow/logic continuity is provided.
Normally Open Positive Transition Contact

If the last write to the variable caused it to go from 0 to 1, power flow/logic
continuity is provided. If the last write to the variable did not cause it to go
from 0 to 1, continuity is not provided or is dropped.

Normally Closed Positive Transition Contact
continuity is not provided or is dropped.
If the last write did not cause the variable to go from 0 to 1, continuity is pro-
vided.
Normally Open Negative Transition Contact

continuity is provided.
If the last write did not cause the variable to go from 1 to 0, continuity is not
provided or is dropped.
Normally Closed Negative Transition Contact

continuity is not provided or is dropped.
If the last write did not cause the variable to go from 1 to 0, continuity is pro-
vided.
Coils
Coils or control relays are boolean elements that represent hard wired circuitry or
internal logic in the ladder. Each boolean element must be assigned a boolean vari-
able declared in the software declarations table. The variable holds the value of the
state of the output. If the output is OFF or de-energized, the value is 0. If the output
is ON or energized, the value is 1. If the element is a physical output, its location
must also be declared.
Buttons Coil Types
energize
de-energize
set (latch)
reset (unlatch)
Energize Coil
If power flow/logic continuity to this coil occurs, it is turned on.
If power flow/logic continuity to this coil drops, it is turned off.
De-energize Coil
If power flow/logic continuity to this coil occurs, it is turned off.
If power flow/logic continuity to this coil is dropped, it is turned on.

Set (latch) Coil
If power flow/logic continuity to this coil occurs, it is turned on.
If this coil is on and power flow/logic continuity is dropped, it stays on.
If power flow/logic continuity to this coil does not occur, it does not turn on.
Reset (unlatch) Coil

If power flow/logic to this coil occurs, it is turned off.
If this coil is off and power flow/logic continuity drops, it stays off.
If power flow/logic continuity to this coil does not occur, it does not turn off.
Wires
Wires are used in your network to connect other elements. They create data paths
along which data is transferred from one element to another. They can also be used
to broaden or lengthen the spacing of elements on your screen.
There are three types of wires available.
Buttons Wire Types
Horizontal
Vertical
Both (combination)
There are several ways to add wires to your network.

1. Click the toolbar button of the type of wire you want to use and drop it in
the appropriate cell. Note that the cursor changes into the shape of the
selected wire. You are now in the wire drop mode and can continue to place
the chosen wire in your network until you cancel the wire drop mode by
clicking another item or pressing the Esc key.
2. Click the point to point wire button . Position the cursor on the wire
starting point and drag the cursor to the wire terminal point. Release the
mouse button. Note: You must be in the same row (horizontal wires) or
column (vertical wires) for this to work.
3. Select Ladder | Wires from the menu. A fly-out appears from which you
can select Vertical, Horizontal, or Both.

4. Use the following hot keys for the following wires:
Position of Focus After Wire is

Wire Hot Key Placed
Vertical <Ctrl + Shift + V > Remains over vertical wire

<Ctrl + I> Moves to cell above vertical wire
<Ctrl + M> Moves to cell below vertical wire
Horizontal <Ctrl + Shift + H> Remains over horizontal wire
<Ctrl + J> Moves to cell to left of horizontal wire*
Moves to cell to right of horizontal wire*
<Ctrl + K>
Combination <Ctrl + Shift + B> Remains over the combination wire
* Unless you are next to a function/function block in which case focus moves to the cell
below the vertical wire.
The horizontal wire provides a left-to-right horizontal connection between ele-
ments in the network.The vertical wire provides a top-to-bottom vertical connec-
tion between elements in the network. The combination wire provides a branch
connection between elements in the network. The branch must follow this same
left-to-right, top-to-bottom scanning.
Functions/Function Blocks in LD Network

Functions are network elements that allow you to perform operations such as arith-
metic or motion control.
Function blocks are network elements that allow you to perform operations that
must retain data for a period of time, such as timing or counting operations. Func-
tion blocks must be declared in the software declarations table.
Constants can be inputs to any Function/Function Blocks except functions that
operate on STRINGs (string values must be put into variables). A constant value
must be in the range and format it would be in if it were a variable value.
Generally, all input variables and the output variable must have the same data type.
However, this is not true for a function whose purpose is to change a data type, i.
e., converting numeric type data into bitwise type data. It is also not true for inputs
that are providing extraneous data for the operation and outputs that are providing
information about extraneous data for the operation. In all other cases, though, the
output data must match the input data type.
Although input and output data must be of the same type, input and output vari-
ables usually do not have to be unique variables. For instance, you could add the
constant 1 to a variable called VAR1 and place the result in VAR1.

IMPORTANT
If an output variable is unique from an input variable,

the input variable is unaltered by execution of the func-
tion/block. Only the output variable is changed.
Functions that return a string type variable as an output have a unique characteris-
tic. The output variable must be assigned on the input (left) side of the function.
This is necessary because STRINGs require memory allocations before the opera-
tion is performed.
For detailed information on functions/function blocks, please refer to the PiCPro
Function/Function Block Reference Guide.
Data
When entering functions or function blocks into a network, you can choose
from the three categories of data below to enable the connections to these ele-
ments.
Data Fly-outs Descriptions
Selected to enable the connection and entering of

In inputs to functions/function blocks.
In Inverted inverted inputs to functions/function blocks.
Out outputs to functions/function blocks.
To enable Function/Function Block connections, follow these steps:

1. After inserting the function/function block into the network, place the cur-
sor at the first connection you want to make.
2. Select Ladder | Data from the menu and open the fly-out. Make your
choice. Or choose the correct button from the Function toolbar.
3. In the variable scroll box that appears, enter a new or select an existing
variable. If the variable is new and has not been declared in the software
declarations table, you will need to do that.
4. Move onto the next input or output you want to connect and follow step 2
and step 3.

Jump in LD Network
The jump command causes the execution of the ladder to jump or move to the
beginning of a specified network. The specified network must have a label
assigned by you in order for the jump command to find it.
You can jump to a label (with no return) or jump to a subroutine (with return).
Jump Fly-
outs Descriptions
To Label Places the symbol for the jump to label command into the net-
work and prompts you to enter the label of the network to which
execution should jump.
To Subroutine Places the symbol for the jump to subroutine command into the
network and prompts you to enter the label of the network to
which execution should jump.
Return Places the symbol for the return command (<return>) into the
network.
Can be placed:
In a subroutine where it returns you to the network from which
the jump originated
In the main module (typically at the end of the program before
any subroutines) where it takes you to the <End Of Module> in
the ladder
In a UDFB source ladder (typically at the beginning) where it
takes you to the <End Of the Module> if the EN (enable) is not
set.
Notes:
It is recommended that subroutines be placed at the end of your
main module program. A return command should be placed not
only at the end of the subroutine, but also at the end of the main
module directly before the subroutine network. The return at the
end of the subroutine takes you back to the original jump to sub-
routine command network. The return at the end of the module
takes you to the end of the module. If it were not included, the
program would execute the subroutine again.
To insert a jump in your ladder, follow these steps:

1. Place the cursor within the LD network you want to insert the jump into.

2. Select Ladder | Jumps from the menu. From the fly-out, select either To
Label or To Subroutine. Or click the button from the Ladder toolbar.
ST Elements and Structured Text

ST networks are composed of ST statements and comments. The structured text state-
ments that are supported in PiCPro are assignment, conditional, iteration and Func-
tion/Function Blocks. Many of the ST statements are created using expressions.
Structured Text is a higher level programming language whose syntax is similar to
other higher level programming languages such as C, C++, Java, Pascal, Basic, etc...
Expressions
Expressions are used in many of the ST statements and are one of the fundamental
building blocks for many of the ST statements. They are used for calculations and
they resemble mathematical formulas. An expression is a combination of operands
and operators that are used to form an algebraic expression that evaluates to a sin-
gle value and data type. An operand can be a variable, constant, or function call.
Valid expression operators are listed in the table ST Operators-Evaluation Prece-
dence located in Expressions - Operators and Precedence Order. Examples of
very simple to more complex expressions are shown in the following table:
Example Explanation/Description
SPEED Expressions can be as simple as a con-
stant or a variable.
MAX(IN0:=A, IN1:=B) Expressions can also be a function call.
The result from this expression is either
A or B depending on which is larger.
A *(B + MIN(IN0:=C, IN1:=D)) Expressions can be as complex as
needed.
Result:
B is added to the minimum value
of C or D, the result is then multi-
plied by A.
Comments:
• All operands in an expression must be of the same data type. A com-

pile error will result when an operand does not match the data type
of the expression.
• If it is necessary to change the data type on an operand use the data

type conversion functions found in the Function/Function Block
Reference Guide.
• To detect run time errors such as overflow and divide by zero, in ex-
pressions, call the OK_ERROR function. Refer to the Function/
Function Block Reference Guide for a description of this function.

Expressions - Operators and Precedence Order
Expressions are evaluated based on a given precedence order. Valid opera-
tors and their evaluation precedence order are given in the table below. The
precedence order is from highest to lowest. If operators have the same pre-
cedence, they are evaluated from left to right.
ST Operators - Evaluation Precedence

Operator Description Precedence
(...) Parenthesized expression Highest
Function (...) Parameter list of a function, function evaluation
NOT Boolean Complement

- Arithmetic Negation
* Multiplication
/ Division
MOD Modulus operation
+ Addition
- Subtraction
< Less Than

> Greater Than
<= Less Than or Equal To
>= Greater Than or Equal To
= Equal To
<> Not Equal
AND Boolean AND

& Both operators are used interchangeably
XOR Boolean exclusive OR
OR Boolean OR Lowest

P * R / Q + W / X - Y When P :=10, R := 5 , Q := 2, W
:= 15, X := 3, Y := 12
1 2 4 3 5
1 10 * 5 is 50
2 50 / 2 is 25
3 15 / 3 is 5
4 25 + 5 is 30
5 30-12 is 18, which is the

final result
Comments:
Many of the ST operators have an equivalent function that can be called.
Each of these functions provide the same functionality/behavior as their ST
operator equivalent with the following exceptions:
• Functions are evaluated before their ST operator equivalent.
• Functions provide status via OK. This can be used to check for over-
flow, divide by zero, etc.
Comments in ST Elements
In addition to the network comments that can be entered there are two types of ST
comments that can also be entered.
The first type, also known as line comments, begins with a // and end with the
enter key. A line comment can be written on a line by itself or at the end of a line
containing a ST statement.

The other comment style begins with (* and ends with *) and can be placed
wherever it is acceptable to insert one or more spaces within the text itself. These
comments can span multiple lines.
Example of (* and end with *)

(* Title: Determines if limit switch set.
Date: 4/17/02 *)
Example of Line Comment

Area := 3.1416 * Radius * Radius; //Computes area of a circle
Comments:
• (* *) comments cannot be nested (e.g., (* (* comment *) *)).
• Neither type of ST comment can be exported or imported.
Assignment Statements
Assignment statements are used to change the value stored within a variable.
Generic Format
<<Variable>> := <<expression>>;
Expression is evaluated and results are assigned or stored in variable.
A := B + C * (10 / D); Results:
When A := 1090, B :=10, C := 5,
D := 2
Expression evaluates to 35 and
A is then set to 35.
Comments:
• The data type of the <<expression>> must match the data type of the
<<variable>>.
• In its simplest form, an assignment statement is equivalent to the

MOVE function, the assignment statement can be used to copy an
entire structure but cannot be used to copy an entire array. For ex-
ample, if A and B are of type struct, then A := B; will move the entire
contents of struct B into A.
• If a underflow/overflow or divide by 0 occurs when evaluating <<ex-

pression>>, then the value stored in <<variable>> will be unpredict-
able. To determine if this occurred, call the OK_ERROR function.
Refer to the Function/Function Block Reference Guide for a de-
scription of this function.

Conditional Statements
A conditional statement selects and executes one or a group of statements based on
a specified condition.
A conditional statement can be typed into a ST Element directly or can be selected
from Ladder | Structured Text or by clicking the appropriate icon on the Struc-
tured Text Toolbar.
Structured Text in PiCPro allows four conditional statements, IF-THEN, IF-
THEN-ELSE, ELSIF-THEN-ELSE and CASE.
Button Statement
IF-THEN
IF-THEN-ELSE
ELSIF-THEN-ELSE
CASE
IF-THEN
Generic Format
IF <<boolean expression>>THEN
Section 1
This section will execute if the above <<boolean-expression>> is true. If the
above <<boolean-expression>> is not true, then Section 1 will not execute.
END_IF;
IF A > 10 THEN Results:
C := 20; When A is less than or equal to
END_IF; 10, the value of C will not be
changed.
When A is greater than 10, then
C will be set to 20.
Comments:
Section 1 must contain at least one ST statement.

IF-THEN-ELSE
Generic Format
IF <<boolean-expression>> THEN
Section 1
Section 1 will execute when the above <<boolean-expression>> is true.
ELSE
Section 2
If the above <<boolean-expression>> is not true, then this Section will execute.
END_IF;
C := 20; When A is greater than 10,
ELSE then C will be set to 20.
When A is less than or equal
C := 100; to 10, then C will be set to 100
END_IF;
Comments:
Section 1 and Section 2 must each contain at least one ST statement.

ELSIF-THEN-ELSE
Generic Format
IF <<boolean-expression #1>>THEN
Section 1
Section 1 will execute when <<boolean-expression #1>> is true.
ELSIF <<boolean-expression #2>>THEN
Section 2
When <<boolean-expression #2>> is true and <<boolean-expression #1>> is
false, Section 2 will execute.
ELSE
Section 3
If none of the previous <<boolean-expressions>> are true, then Section 3 will
execute.
END_IF;
C := 20; When A is greater than 11, then
ELSIF A := 5 THEN C will be set to 20.
When A is equal to 5, then C
C := B + X; will be set to B+X.
ELSIF A := 6 THEN When A is equal to 6, then C
will be set to B+1.
C := B + 1;
When A is equal to 2, then C
ELSE will be set to 100.
C := 100;
END_IF;
Comments:
• Each section must contain at least one ST statement.
• Additional ELSIF sections can be added if needed.
• The ELSE and Section 3 are optional.

CASE
Generic Format
CASE << integer-expression>>OF
Section 1
This section is evaluated first. Statements (in the form <<int-constant #n>> :
<<statement>> ) that have an integer value that matches the value of the <<inte-
ger expression>> above are executed.
ELSE
Section 2
If no matches to the above <<integer-expression>> are found, then Section 2
will execute.
END_CASE;
CASE SPEED_SETTING OF Results:
1: SPEED := 10; When SPEED_SETTING is equal to
2: SPEED := 20; 1, then SPEED will be set to 10
3: SPEED := 30; When SPEED_SETTING is equal to
4,5: SPEED := 50; 2, then SPEED will be set to 20
6..10: SPEED := 60;
When SPEED_SETTING is equal to
11,14,16..18: SPEED := 70; 3, then SPEED will be set to 30
ELSE When SPEED_SETTING is equal to 4
SPEED := 0; or 5, then SPEED will be set to 50
END_CASE; When SPEED_SETTING is equal to

6, 7, 8 9 or 10, then SPEED will be set
to 60
When SPEED_SETTING is equal to
11, 14, 16 17 or 18, then SPEED will
then be set to 70
When SPEED_SETTING is not equal
to one of the previous values, then
SPEED will be set to 0
Comments:
• The data type of the <<integer-expression>> must be SINT, INT,

DINT, or LINT.
• The ELSE and Section 2 are optional.
• The form of <<int-constant #n>> can be defined as a single, several

or a range of values. A single value is simply an integer constant. A
range of values is defined by separating 2 integer constants by “..”.
Several values are defined by putting together any combination of
single or range of values and separating them with commas (i.e 1..5,
10, 13:). The <<int-constant #n>> is terminated by a “:” .

Note: When specifying a range of values, the first number must be
less than the last number. A compile error will result if the last
number is less than the first number.
• The <<int-constant #n>> cannot overlap. Overlapping <<int-constant
#n>> will result in a compile error.
• All sections must each contain at least one ST statement.
Iteration Statements
Iteration statements are provided for situations where it is necessary to repeat one
or more statements a number of times depending on the state of a particular vari-
able or condition.
Note: An iteration statement must have a finite limit. It is the user/program-
mer’s responsibility to insure that the iteration statement does not take too
long to execute which may cause a scan loss.
An iteration statement can be typed directly into a ST element or can be selected
from Ladder | Structured Text or by clicking the appropriate icon on the Struc-
tured Text Toolbar.
Structured Text in PiCPro allows three iteration statements, WHILE-DO, FOR-
DO, and REPEAT-UNTIL.
Button Statement
WHILE-DO
FOR-DO
REPEAT-UNTIL.

WHILE-DO
Generic Format
WHILE <<boolean-expression>> DO
Section 1
<<boolean-expression>> is evaluated. If <<boolean-expression>> evaluates to
true, Section 1 will execute. This process repeats until <<boolean-expression>>
evaluates to false.
END_WHILE;
ArrayIndex := 0; Results:
WHILE ArrayIndex < 10 DO The first time through the
PartReject[ArrayIndex] := 0; loop, ArrayIndex is 0 and
ArrayIndex := ArrayIndex + 1; PartReject[0] is set to 0. The
END_WHILE; second time through the loop
ArrayIndex is 1 and
PartReject[1] is set to 0. This
process repeats and the loop
terminates when ArrayIndex
is 10.
At the end of this loop, Par-
tReject[0] through PartRe-
ject[9] will be set to 0.
Comments:
• If <<boolean-expression>> initially evaluates to false, Section 1 will

not be executed.
• To prevent an endless loop, ensure that Section 1 includes a ST state-

ment that will cause <<boolean-expression>> to evaluate to false. In
the example above, the ST statement ArrayIndex := ArrayIndex + 1;
causes the <<boolean-expression>> ArrayIndex < 10 to evaluate to
false when ArrayIndex is greater than or equal to 10 and causes the
loop to terminate.
• Section 1 must contain at least one ST statement.

FOR-DO
A FOR-DO statement is used to execute a set of ST statements a fixed number
of times. It is generally used for counting up or counting down. A FOR-DO
statement consists of:
• a starting condition that sets the initial value for the counter of the
FOR-DO statement,
• a limit expression that defines the termination value of the FOR-DO
statement,
• a set of ST statements that are to be executed in the FOR-DO statement,
• a step expression is the value that the counter will be incremented each
time through the FOR-DO statement.
Note: The FOR-DO statement does not provide the same functionality as the
CTD, CTU, or CTUD function blocks and should not be used in place
of these function blocks.
Generic Format
FOR <<count-variable>> := <<initialization-expression>> TO <<limit-expres-
sion>> BY <<step-expression>> DO
Section 1
This is the body of the FOR loop. This contains one or more ST statements.
END_FOR;
Description
1.The <<initialization-expression>> is evaluated and the results stored in
<<count-variable>>. This sets the starting value of the loop.
2. The <<limit-expression>> and the <<step-expression>> are evaluated.
3. The <<limit-expression>> is then compared to the <<count-variable>>.
If the <<count-variable>> is less than or equal to (greater than or equal
to, if counting down) the <<limit-expression>>, continue to Step 4, oth-
erwise the loop terminates.
4. The ST statements in Section 1 are executed.
5. The <<step-expression>> is then added to the <<count-variable>> and
the results are stored in the <<count-variable>>.
6. Go to Step 3.

Example 1 - Count Up
Production_Total := 0;
FOR Index := 0 TO 9 BY 1
DO
Production_Total := Production_Total +
Lane[Index].Production;
END_FOR;
Explanation/Description
Results:
The first time through the FOR-DO statement, Index is 0 and Lane [0].Produc-
tion will be added to Production_Total. The second time through the FOR-DO
statement, Index is 1 and Lane [1].Production will be added to
Production_Total. This process repeats and the FOR-DO statement terminates
when Index is 10.
At the end of this FOR-DO statement the Index will be 10 and
Production_Total will be the sum of Lane [0].Production through Lane
[9].Production.
Example 2 - Count Down
FOR Station_Number := 9 TO 0 BY -1 DO
Station_Pointer := INT2UINT(IN := Station_Number);
IF Station_Available[Station_Pointer] THEN
EXIT;
END_IF;
END_FOR;
Results:
Starting with Station_Number 9 we are looking backwards for the first station that
is available. When an available station is found, the FOR-DO statement termi-
nates and Station_Number will contain the available station. If no stations are
found, then Station_Number will be -1. Each time through the FOR-DO statement
Station_Number is decremented by 1.

Comments:
• The data type for the <<count-variable>>, <<limit-expression>>,

and <<step-expression>> must all be the same and must be of the
data type SINT, INT, DINT, LINT, USINT, UINT, UDINT, or UL-
INT.
• BY and <<step-expression>> are optional. If omitted, 1 is assumed

to be the step value.
• Specifying a <<step-expression>> that is negative causes the FOR-

DO statement to count down. The only data types that are valid with
count down FOR-DO statements are SINT, INT, DINT, or LINT.
Using USINT, UINT, UDINT, or ULINT with a count down FOR-
DO statement will result in a logic error in your program.
• Modifying the <<count-variable>> within Section 1 is not recom-

mended and may produce unpredictable results.
• After the FOR-DO statement is terminated the <<count-variable>>

will contain the value that caused the FOR-DO statement to exit.

REPEAT-UNTIL
Generic Format
REPEAT
Section 1
This section of ST statements are executed.
UNTIL <<boolean-expression>> END_REPEAT;
The <<boolean-expression>> is evaluated. If <<boolean-expression>> evalu-
ates to False, the ST statements in Section 1 are re-executed. When the
<<boolean-expression>> evaluates to True, the loop terminates.
Example 1
ArrayIndex := 0;
REPEAT
PartReject[ArrayIndex ] := 0;
ArrayIndex := ArrayIndex + 1;
UNTIL ArrayIndex > 9 END_ REPEAT;
Results:
The first time through the loop, ArrayIndex is 0 and PartReject[0] is set to
0. The second time through the loop ArrayIndex is 1 and PartReject[1] is
set to 0. This process repeats and the loop terminates when ArrayIndex is
10.
At the end of this loop PartReject[0] through PartReject[9] will be set to 0.
Example 2
REPEAT
FIND (IN1 := Vision_X_String, IN2:= Space_Char,
OUT =>Loc_of_Space);
IF Loc_of_Space > 0 THEN
DELETE (OUT := Vision_X_String,
IN := Vision_X_String, L := 1,
P := Loc_of_Space);
END_IF;
UNTIL Loc_of_Space = 0 END_REPEAT;
Results:
The first time through this loop, find the first space in the string
Vision_X_String. If a space is found, delete it from Vision_X_String. The
second time through this loop find the next space in the string
Vision_X_String. If a space is found, delete it from Vision_X_String. This
process repeats until all spaces are removed from Vision_X_String.
At the end of the loop, all spaces from Vision_X_String will be deleted.

Comments:
• The ST statements in Section 1 always execute at least one time.
• To prevent an endless loop, ensure that Section 1 includes a ST state-

ment that will cause <<boolean-expression>> to evaluate to true. In
Example 1 above, the ST statement ArrayIndex := ArrayIndex + 1;
causes the <<boolean-expression>> ArrayIndex > 9 to evaluate to
true when ArrayIndex is greater than 9 and causes the loop to termi-
nate.
Other Statements in ST
EXIT
This statement can only be used within iteration statements and allows itera-
tion loops to end prematurely.
Generic Format
EXIT;
When this statement is executed, the iteration statement is immediately termi-
nated.
Example
FOR Station_Number := 10 TO 0 BY -1 DO
Station_Pointer := INT2UINT(IN := Station_Number);
IF Station_Available[Station_Pointer] THEN
EXIT;
END_IF;
END_FOR
Results:
When Station_Available [Station_Pointer] is true, the EXIT statement is
executed and the FOR-DO statement is terminated.
Comments:
When the EXIT statement is located within nested iteration statements, exit
shall be from the innermost iteration statement in which the EXIT is
located, that is, control shall pass to the next statement after the innermost
iteration statement that is terminated.

RETURN
Generic Format
RETURN;
This statement, when executed, will cause the subroutine or UDFB to
return to the calling module.
IF NOT EN THEN Results:
RETURN; Assuming this example is in a
END_IF; UDFB and the EN is false, the
RETURN statement causes a
OK := 1;
return to the calling module.
Comments:
• This statement has the same functionality in ST as it does in LD.
• For more information about this statement, refer to the section Jump in
LD Network.
Inserting Conditional and Iteration Statements in ST
When focus is in a ST network, you can use a toolbar or pull-down menu to enter
conditional and iteration statement (e.g. an IF-THEN statement) templates.
Replace the template fields with the desired text.
IF-THEN
Menu
Item
IF-THEN
Toolbar
Button
The cursor will be placed on the first template field. The text is located inside <<
>> and will be highlighted. The first character entered replaces the template field.
Rules for a Structured Text Template
A Structured Text Template Field (e.g. <<bool-expression>>) will act as a single
character.
• If the cursor is located inside a template field, a character entry will over-
write the template field with that character (even though the template field
is not highlighted).
• When dragging a selection, if the beginning or end of the selection ends in
the middle of the template field, the entire template field will be selected.
• When deleting or backspacing over a template field, the entire template
field will be deleted.
• When typing a character and ‘insert mode’ is off, if the character over-
writes the start of a template field, the entire template field will be replaced
with the character.
• You cannot create a template field from the keyboard.
Functions in ST
Functions allow you to perform operations such as arithmetic or motion control.
Functions can be called from a ST statement or from within an expression. See the
Generic Format and Examples below.
For detailed information on Functions, please refer to the PiCPro Function/Func-
tion Block Reference Guide.
A function block can be typed into a ST element directly or can be selected from
the Ladder | Functions menu.

Generic Format - ST Statement
<<FunctionName>> (<<InputParameter1>> := <<Expression1>>,
<<InputParameter2>> := <<Expression2>> , <<OutputParameter1>> =>
<<VariableName1>> , <<OutputParameter2>> => <<VariableName2>> , ...) ;
<<Expression1>>, <<Expression2>> ,... are evaluated. The function is then called with
<<InputParameter1>>, <<InputParameter2>>, .... The results from the function call are
returned in output parameters <<VariableName1>>, <<VariableName2>> , ...
ST Example
BYT2BOOL(IN := WORD2BYT(IN := E_ERRORS),
OUT0 => LossOfFeedback, OUT1 => ExcessError,
OUT3 => UserEstop);
LD Equivalent
Results:
When E_ERRORS is 9 then LossOfFeedback and UserEstop will be enabled.
When E_ERRORS is 3 then LossOfFeedback and ExcessError will be enabled.
Generic Format - ST Expression Operand

<<FunctionName>> (<<InputParameter1>> := <<Expression1>>,
<<InputParameter2>> := <<Expression2>> ,...) ;
<<Expression1>>, <<Expression2>> ,... are evaluated. The function is then called with
<<InputParameter1>>, <<InputParameter2>>, .... The results from the function are used in
the ST expression.

ST Example
JogSpeed:= SEL(G:=JogSlowFastSwitch,
IN0:=SlowJogRate,IN1:=FastJogRate);
LD Equivalent
Results:
When JogSlowFastSwitch is not set, then JogSpeed := SlowJogRate.
When JogSlowFastSwitch is set, then JogSpeed := FastJogRate.
Comments:
• Selecting Ladder | Functions will insert a Function template that
includes the input and output parameters into your ST Element. Input
parameters are identified using := and output parameters are identified
using =>. If more than one parameter is used, they are separated by
commas. Parameters can be specified in any order.
• Output parameters cannot be specified in a function call used in a ST
expression. Output parameters are optional in a function call used in a
ST statement. However, if no output parameters are specified, no
results will be returned from the function.
• Functions that do not return a value cannot be used in a ST expression.
They must be called from a ST statement (e.g. CLOSLOOP).
• Functions that return multiple values, cannot be used in a ST expres-
sion. They must be called from a ST statement (e.g. MOVE, and
BYT2BOOL).
• Although EN is always specified as the first input parameter to a Func-
tion in a LD network, EN cannot be specified as an input parameter to a
ST function.
• The data type for each function input and output parameter must match
the data type of the function definition for that parameter.

Function Blocks in ST
Function Blocks allow you to perform operations that must retain data for a period
of time, such as timing or counting operations. Function Blocks must be declared
in the software declarations table.
For detailed information on Function Blocks, please refer to the PiCPro Function/
Function Block Reference Guide.
A Function Block can be typed into a ST element directly or can be selected from
the Ladder | Functions menu.
Generic Format
<<FunctionBlockInstance>> : <<FunctionBlockTitle>>
(<<InputParameter1>> := <<Expression1>> ,
<<InputParameter2>> := <<Expression2>> ,
<<OutputParameter1>> => <<VariableName1>> ,
<<OutputParameter2>> => <<VariableName2>> , ...) ;
<<Expression1>>, <<Expression2>> ,... are evaluated. The function block is then called
with <<InputParameter1>>, <<InputParameter2>>, .... The results from the function block
call are returned in output parameters <<VariableName1>>, <<VariableName2>> , ...
ST Example
CTU1: CTU(CU := PE, R := FULL, PV := 6, Q => FULL,
CV => CURRENT);
LD Equivalent
Results:
The PE input detects a product on the line. When six products have been completed,
the full output at Q will energize. Current will represent the number of products in the
package. Full would be used to move the finished package out and reset the counter
to zero.

Comments:
• Function Block titles are limited to 8 characters.
• Function Blocks/tasks can not be used in expressions.
• The “:FunctionBlockTitle” is optional and is not part of the standard
IEC1131-3. The “:FunctionBlockTitle” has been included so modules
are easier to read and understand.
• There is a very significant difference between when Function Blocks
are called in ST verses LD. In LD, every Function Block is invoked
with each and every scan. It does not matter what ladder logic sur-
rounds the Function Block. In ST, if a Function Block is in a condition
or iteration statement, the Function Block will not be invoked if the
logic that surrounds it has not been satisfied.
• Selecting Ladder | Function will insert a Function Block template that
includes the input and output parameters into your ST Element. Input
parameters are identified using := and output parameters are identified
using =>. If more than one parameter is used, they are separated by
commas. Parameters can be specified in any order.
• Input and output parameters are optional and only need to be specified
if needed.
• The data type for each Function Block input and output parameter must
match the data type of the Function Block definition for that parameter.
ST Network Considerations
• In a LD network, Function Blocks are called each and every scan. In a ST net-
work, the Function block will not be called every scan but will be called only
when the logic surrounding the Function Block supports it.
• There are no equivalent ST statements for transitional contacts (i.e., Normally
Open Positive Transition Contact, Normally Closed Positive Transition Con-
tact, Normally Open Negative Transition Contact, and Normally Closed Nega-
tive Transition Contact).
• ST networks, as do LD networks, execute every scan. Therefore, it is important
to take this into consideration when creating a ST network.
• Conditional and iteration ST statements can be nested within other conditional
and iteration ST statements to create more complex ST networks.
• An iteration statement must have a finite limit. It is the user/programmer’s
responsibility to insure that the iteration statement does not take too long to
execute because this may cause a scan loss.

Variables in ST Networks
Adding Variables to a ST Network

With focus in a ST Element, do one of the following:
• Click the button from the Structured Text toolbar.

• Select Ladder | Structured Text | Add Variables to ST from the
menu.
• Press <Ctrl + Enter>.
A combo box will appear in the ST network.
If the cursor is on a ST template that specifies a certain type of variable (e.g.

integer), only that type of variable is available in the combo box.
Adding Undefined Variables to Software Declarations - ST Network

1. Enter a new variable in a ST network and either click outside of the network or
use the arrow keys to move out of the ST network. A list of the undefined vari-
ables will be displayed under Pick List:
Note: If an * is displayed before the variable name, the variable has been used
more than once in the ST network and the compiler detects a conflict with
the variable type.

2. Click Add > to move the variable(s) to the Add to Software Declarations list.
3. Click OK and the Software Declarations dialog will be displayed:
4. Put focus on the line in the Software Declarations: Add Unknown ST Vari-
ables dialog.
5. Press the Insert key or select Tools | Insert Symbol. The following dialog will
be displayed.
6. Enter the data type in the Select Datatype: field

After variables have been added to software declarations, the ST network will be
recompiled. If the Forced Declarations field is checked in the User Preferences
tab of the Options dialog, and if any unknown variables still exist, you are
prompted to add the variables to software decalarations.

Note:If the Forced Declarations field is checked you will be forced to enter soft-
ware declarations for unknown variables when:
• Ladder focus has changed from a ST element to another grid or row.
• Save, Save All, or Save As is chosen and a change has been made to
the ladder program.
• Closing the current ladder program or closing PiCPro causes a Save to
occur.
The following is a description of all control buttons for the Declare Unknown
Variables dialog:
Control Button Description
Add> Click this button to move undefined variables selected in Pick

List to Add to Software Declarations List
< Remove Click this button to move undefined variables highlighted in Add
to Software Declarations List to Pick List.
Remove All Click this button to move everything in Add to Software

Declarations List to Pick List.
Select All Click this button to select all undefined variables in the list
above.
Select None Click this button to deselect undefined variables in the list above.
OK Click this button after selecting undefined variables to be added

software declarations. The Software Declarations dialog will be
displayed. Press the Insert key to insert undefined variables.
Cancel Click to close the dialog without adding any undefined variables
to software declarations.
Help Click to display information related to this subject.

Checking Syntax in a ST Element
With focus in a ST Element, do one of the following:
• Click the button from the Structured Text toolbar.

• Select Ladder | Structured Text | Syntax Check ST Element from
the menu
• Press <Ctrl + Alt + S>
A compile and syntax check will occur. Upper and lower case spelling errors of
variables will be corrected automatically. Compiler errors will be displayed in
the Information Window.
Note: This menu item is enabled anytime a ST element is edited.
Using the Right-Click Menu in a ST Element

Various tasks can be performed using the right-click menu while focus is on a ST
Element. The availability of the menu items used to perform these tasks depends
on the location of the cursor. A description of these menu items follows:

Menu Item Description
Help Select to view the on-line Help topics.
Cut Select to cut a highlighted selection.
Copy Select to copy a highlighted selection.
Paste Select to paste an item where the cursor is located.
Insert Provides the choice of inserting a LD or ST network where the

cursor is located. Networks are renumbered if the cursor is not at
the end of the module.
Delete Network Select to delete the network the cursor is located on.
Find/Replace Select to specify a search or a search with a replacement and acti-

vate it.
Find Next Select to execute another search on data from the previous
search.
Info: The information displayed will vary based on the location of the
cursor.
Add ‘variable name’ to Select to add unknown variables to the Software Declarations
Software Declaration table.
Software Declarations Select to open Software Declarations.
Declare All Unknown Select to add unknown variables to Software Declarations.

Variables in Network
Add ‘variable-name’ to If the cursor is on a known variable, select to add the variable to
View List the view list. If multiple variables are highlighted, this item
becomes Add Selected Var(s) to Force List and all variables
selected and declared will be added to the View List.
Add ‘variable name’ to If the cursor is on a known variable, select to add the variable to
Force List the force list. If multiple variables are highlighted, this item
becomes Add Selected Var(s) to Force List and all variables
selected and declared will be added to the Force List.
View UDFB/Task If the cursor is on a UDFB or task, select to open the UDFB or
task.
View Servo Function If the cursor is on a servo function, select to open the servo func-
tion.
View SERCOS Func- If the cursor is on a SERCOS function, select to open the
tion SEROCS function.

Compiling and Downloading
Compiling
When the development is complete, the ladder file can be compiled into one of the fol-
lowing:
• A BIN file which can either be downloaded directly to a control or stored in a
directory or on a disk and later loaded into a control with the Restore command
• A HEX file which allows your ladder file to be copied to an EPROM or to lad-
der flash memory
• A TASK creating a UDFB for use in a main ladder file
• A UDFB creating a customized UDFB for use in other ladder files
Downloading
Downloading sends the active ladder file on your workstation to the CPU memory
after it has been compiled into an executable program.
The source form of your ladder file remains on the workstation. You can edit the
source form, run animation, etc. Any off-line changes you make to the source file
must be downloaded to the control before they take effect. Always backup this
source ladder file to ensure that you will have a copy of your ladder file in its
downloaded form. Include in the backup the filenames for the ladder file with any
of the following extensions:
LDO, REM, SRV, LIB, SRC, FRC, RTD, SVT, SCT, ADV
You can backup this executable form from the control to the workstation by using
the Online | User Program | Backup | Application Program command or the
button on the Basic Online Operations toolbar. You can restore any BIN file
to the control memory with the Online | User Program | Restore command or the
button on the Basic Online Operations toolbar.
Compiling a Bin File

There are two options under the Compile | Bin File command; Compile and Down-
load… and Compile Only.
These commands can also be accessed from the Compile and Download button
or the Compile Only button on the Compiler toolbar.

Compile and Download
The Compile and Download command allows you to create a binary file out of
the active ladder file on your workstation and download it to the control.
1. Ensure that your workstation is connected to the control.
2. To display the Compile and Download Options dialog, do one of the follow-
ing:
• Click the button on the Compiler toolbar

• Select Compile | Bin File | Compile & Download... from the menu..
You have two download options. You can choose to stop the scan and down-
load the ladder file or, if you were able to make on-line changes to the ladder
file, you can choose to patch the scanning ladder. You can also choose to restart
the scan if it was stopped and have animation enabled after the download is
complete.
3. The binary file is compiled and downloaded and the status is reported in the
information window. If the download is successful without any errors, the
memory usage information is shown in the information window.
This displays:
• The amount of retentive memory used in data bytes. (24K limit)
• The amount of memory used for data bytes. (64K limit)
• The amount of memory used for ladder code bytes.
• The total code bytes for your application ladder plus libraries*.
*The total code bytes must not exceed the application memory available on the
CPU module.

Compile Only
The Compile Only command allows you to create a binary file without download-
ing it to the control. This provides an opportunity to check the ladder file for errors
and make any corrections or to build a binary file that can be stored on disk or in a
directory and later restored to the control.
1. Choose the Compile | Bin File | Compile Only command or the button on
the Compiler toolbar.
2. The binary file is compiled and the status is reported in the information win-
dow. If the compile is successful without any errors, the memory usage infor-
mation is shown in the window.
Just like when you perform a compile and download, this displays:
• The amount of memory used for data bytes. (64K limit)
• The amount of memory used for ladder code bytes.
• The total code bytes for your application ladder plus libraries*.
*The total code bytes must not exceed the application memory available on the
CPU module.
Compiling a Hex File

A ladder file that has been opened on your workstation can be saved in Intel 8086 Hex
format. The name of the ladder file becomes the name of the hex file with a .HEX
extension. This file may then be copied to an EPROM programmer to program your
EPROMs or loaded to FLASH memory on processors that support this option.

To Compile a Hex File
1. Open the ladder file you want to compile as a hex file.
2. Choose Compile | Hex from the menu or choose the button from the com-
piler toolbar.
3. If there are no errors, the hex file details are listed in the Information Window
and the compile is complete.
4. The hex file is saved in the directory of the current ladder file with the ladder
filename and the HEX extension.
5. If any errors occur during the compile process, they will be reported to the
Information Window. The compile process will stop and you must edit the lad-
der to resolve the errors and compile again.
The Download Hex command from the Online menu is used to load the file to
flash memory.
Compiling a Task
The logic you enter in a task ladder file is converted into a TASK function block by
compiling it.
To Compile a Task, follow these steps:

1. Open or create the ladder file you want to compile as a TASK.
2. To display the Compile UDFB/Task dialog, do one of the following:
• Click the button from the compiler toolbar.

• Select Compile | Task from the menu.
Under Compile Options, Compile and place in library is selected by default.

Note: The other options are grayed and not available for TASKs.
You must select the library file in which to insert the TASK. You can enter the
name of a new library file in the UDFB Library Name: box. A confirmation mes-
sage will appear. If there are existing libraries listed in the Registered UDFB
Libraries: box, you may select one of them. If the task already exists in one of the
registered UDFB libraries, this library will be selected by default and cannot be
changed.
Note: You cannot place a TASK in any of the standard library files.
Compiling a UDFB, follow these steps:

The logic you enter in a UDFB ladder file is converted into a function block by com-
piling it.
To Compile a UDFB, follow these steps:

1. Open or create the ladder file you want to compile as a UDFB.
2. To display the Compile UDFB/Task dialog, do one of the following:
• Click the button from the compiler toolbar.

• Select Compile | UDFB from the menu
You may choose from the Compile Options to:

Compile and place in library
or
Compile debug version and place in library
The debug version reserves some space for patching. (Adds additional data bits
(40), data bytes (80), and function/jump links (20) to each instantiation of the
UDFB to allow you to perform more extensive on-line changes.)

Note: Minor changes that do not add things like new functions, declarations, or
jump labels can be made on-line without creating a debug version.
You also must select the library file in which to insert the UDFB.
You can enter the name of a new library file in the UDFB Library Name: box. A
confirmation message will appear.
If there are existing libraries listed in the Registered UDFB Libraries: box, you
may select one of them.
You are not allowed to place a UDFB in a standard library file.
If the UDFB already exists in one of the registered UDFB libraries, this library will
be selected by default and cannot be changed.
Settings
The Settings command under the Compile menu allows you to choose settings in four
areas:
1. Ignore Direct I/O
2. Force Soft Bit Memory
3. Generate Map File (Main Ladder Only)
4. Use an Operator Interface

Ignore Direct I/O
If this setting is selected, the compiling of the binary file will occur with all the
direct I/O disabled. Typically, this is used for testing where the current I/O does not
match the specified I/O.
Force Soft Bit Memory

If this setting is selected, soft bit memory is enabled in all Turbo CPUs that do not
have standard soft bit memory. Typically, this is used when data memory is low.
Generate Map File (Main Ladder Only)

If this setting is selected, a symbol map file will be generated for the main ladder,
whenever you do a compile. The map file is saved in the directory of the current
ladder file with the ladder filename and the MAP extension. Subsequent compiles
of the main ladder will automatically delete and regenerate the map file. Typically,
the MAP File is used for debug purposes and to try and optimize data memory
when data memory exceeds 64K.
Operator Interface
Within the operator interface box, there are several settings.
When the Construct Data File checkbox is checked, an operator interface data
file (OID) is created when you compile the BIN file. This file contains the neces-
sary information for the operator interface software.
The Operator Interface Node Number is usually set to 0. But it can be used to cre-
ate multiple displays for a single machine. Available numbers are 0 to 255.
The Operator Interface Output Directory allows you to put the OID file in the
directory of your choice. If you leave this box empty, the OID file will be placed in
the same directory as the ladder file.
Extended Data Memory Feature

If you have a control with a 486 processor running firmware dated August 1, 1999 or
later and at least 512K of application memory, data memory can be extended beyond
the standard 64K. Two additional data memory areas have been added bringing the
total to three, each containing 64K providing a total of 192K of data memory for your
control.
To take advantage of this feature, you do not have to do anything. But you should be
aware of how the processor handles this extended memory feature. When you select
the Compile Only or Compile & Download command, the first data memory area of
64K is allocated. When it is filled and more data area is needed, a second data memory
area is automatically allocated. This data memory is taken from the application mem-
ory. When the second area is filled, a third data memory area is allocated. When that is
filled, an error message will warn you that the control is out of data memory.

After a Compile command, the information window reflects how much data memory
is being used and how much is allocated for each data memory area. Note: The allo-
cated memory may not match 64K exactly. If all three data memory segments are
filled, you may want to optimize your memory usage by getting all three segments as
close to 64K as possible. Call our technical support department for help with this. You
can produce a readable symbol map file using the Compile | Settings box. Check the
Generate Symbol Map check box so that a text file is generated when you compile.
Note: This can only be done from the main ladder file.
IMPORTANT
You must rebuild all UDFBs and TASKs if this is the first time you are
using a version of PiCPro and firmware that have the Extended Data
Memory feature.
Tips on Working with Extended Data Memory

• The extended data memory feature requires a version of firmware dated
August 1, 1999 or later and the CPU has at least 512K of application mem-
ory.. The version can be checked using Online | Status.
• Retained variables and discrete I/O are restricted to the first data segment.
This means you cannot have a combined total of more than 64K of them.
You will get an “out of data memory” error message if this is exceeded.
• UDFBs are restricted to 64K of data memory.
• No structure or array may be larger than 64K. An error message will be
issued if one is found.
• Patching of data is allowed up until the last data memory area is filled. At
that point, a full compile and download is required.
IMPORTANT
UNPREDICTABLE RESULTS MAY OCCUR if you group arrays in

software declarations so that they are treated as one large array using an
index value that exceeds the first array’s limit! It is NOT recommended
that you do this.
It is possible to change the memory configuration in controls with 486DX proces-

sors and the MMC for PC. The default configuration is 256K of RAMDISK and
512K of Application memory. If you find it necessary to change the default config-
uration, use the Download Hex command from the Online menu available before
any files are open.

Animating the Ladder
Animation allows you to monitor the power flow in the LD networks of a ladder diagram
that has been compiled and downloaded to the control and in one or multiple UDFB and/
or TASK ladder files that are displayed. Variables used in ST networks must be animated
in the View List.
To Turn Animation On, follow these steps:

1. Compile and download the ladder.
2. Display any UDFB or Task LDOs you want to animate using the
View | UDFB/Task command.
3. To turn on animation, choose one of the following:
• Click the button on the Advanced Operations toolbar

•Select Online | Animate from the menu
• Power flow is indicated by a heavy wire in a customized color. The default
is red. Use the Options button to change the color. Any energized ele-
ment (contact, coil, etc.) in the ladder will be highlighted in the color cho-
sen.
• Numeric variables are displayed above the variable name. These variables
are updated dynamically as the contents change. You can view things like
timers or counters changing. If the results of working with floating point
numbers yield an infinite, indefinite, or not-a-number result, the OK on the
function will not be set and animation will display the following labels:
Value Output
+Infinity 1.#INF
-Infinity -1.#INF
Indefinite digit.#IND
Not-a-number digit.#NAN
• All variable lengths are dependent on cell size for display. If a string is too
long for the cell, you can view it in the view list.
Ladder with Animation Off Ladder with Animation On, Scan Running

If the scan is stopped while animation is on, the color of the power flow is grayed
to indicate that the control is no longer scanning. When the scan is started again,
animation will resume.
Ladder with Animation On, Scan Off
To Turn Animation Off, do any of the following:

• De-select Online | Animate | LDO from the menu.
• Toggle the button on the Advanced Operations toolbar when the win-
dow which should no longer be animated has focus.
• Enter the edit mode and make a change to the ladder file. A message will
tell you that the workstation version is no longer identical to the control
version. The ladder file must be compiled and downloaded after an edit.
• Access any dialog other than View List or Forcing List.
When animation is turned off, any numeric values shown above the variables are
no longer displayed.
Forcing & Viewing Variables
Forcing is a way to alter the contents of up to 61 variables while the program is running. It
is a powerful tool in isolating a problem. Variables can be forced individually or as a
group. Grouping is an extension of the forcing feature. One example of how it could be
used is to allow you to toggle the state or value of a variable by entering one value or state
in grouping and the other in forcing and then switching between them.
When testing or debugging a software module, you can Force a value into the following:
• An input element to simulate the data input from an application device, which has
not been connected
• An element that enables a function or function block you want to check
• A preset timer variable to check what happens when it times out
When troubleshooting an application, you can Force a value into the following:
• An output element to locate a problem when troubleshooting an application

• Selected elements between an input that works and an output that does not to iso-
late an internal problem.
WARNING
Do not force any variable in a program that is running an application

until you are sure you understand all the effects the changes may cause.
A malfunctioning program may cause injury or damage the machinery.
Note: Forcing is turned off automatically when power is cycled. If you
use the power reset button in PiCPro, a warning message will inform
you of this.
If you have a forcing list open but inactive when you attempt to turn forcing on, you will
get a message that asks if you want to activate forcing. When you switch from the main
ladder force list to a UDFB force list, you turn off the main force list and vice versa.
Briefly, to force a variable, you will do the following:
1. Enter the variable name and value in the Force List.
2. Mark the variable in the Force List to enable it.
3. Turn Force on.
4. If needed, edit the Force List and update the forcing information to the control.
IMPORTANT
Animation may not reflect forced conditions. Physical inputs are

forced at the beginning of the scan. All other variables are forced at the
end of the scan. The writing of variable values by the ladder is not in-
hibited by forcing. Therefore, it is possible to change the state of a coil
during the scan but not see the change in animation.
Entering Variables in the Force List

With the control running and your ladder file open, you are ready to enter variables
into a Force list. Only one Force List is created for each ladder file. It is given the FRC
extension and the same filename as the ladder file.
To bring up the Force list, choose one of the following:
• Click the button from the View Navigator toolbar

• Select View | Forcing List from the menu

The Force List Window appears with focus on the Name column. The window and
columns can be adjusted.
You have four ways to enter a variable into the Force List Window.
Copy/Paste
1. Copy the element in the ladder file that you want to place in the Force List.
2. Open or activate the Force List Window.
3. Position the focus in the Force List Window grid and paste the selection.
If you are in a blank row, the variable you are entering will fill that row.
If you are in a row that already contains a variable, the new variable will
appear in a row above the existing one.
If you are in a row that is highlighted, the new variable will replace that row.
4. Enter a value in the Value column. An error message will appear if the value
you enter is out of range, incompatible, etc.
5. Check the Force Enable and/or Group Enable column.
Drag-n-Drop
2. Select the variable in the ladder to add to the Force List.
3. Drag the selection from the ladder to the Force List row you want to insert the
variable in and release the button.

Right-Click Menu in Ladder
1. Select the variable in the ladder to add to the Force List.
2. Right-click and select Add symbols to Force List. The variable will be added
to the end of the Force List.
Manual Entry
2. Place the focus in the Name column of the Force List.
3. Type in the name of the variable you want to add or click on the down arrow to
bring up a list of all variables in the software declarations table except function
blocks. If the symbol is an array, it will be entered into the list as an ARRAY().
You must enter the index number in the parenthesis.
Turn Forcing/Grouping On/Off
Turn Forcing/Grouping On
In order to activate variable forcing/grouping, the following conditions must be
met:
• The ladder file is open.
• The ladder file has been compiled and downloaded to the control.
• If you make any changes after the download, be sure to compile and down-
load again or the time stamps will be different. If the time stamps are dif-
ferent, an error message will appear and you will not be able to activate
forcing.
• The Force List Window is open.
Note: The window does not have to be active.
If the above conditions are met, you can turn forcing on.

Turning On Forcing/Grouping from the On-Line Menu
1. Check all variables that you want to force and/or group in the Force Enable
column or in the Group Enable column respectively of the Force List.
2. Choose Online | Force | Forcing from the menu to activate forcing. Select OK
from the OK/Cancel confirmation that appears.
3. Choose Online | Force | Grouping from the menu to activate grouping. Select
OK from the OK/Cancel confirmation that appears. Turning off grouping
updates forcing. Turning off forcing turns off grouping. The symbols for forc-
ing and grouping will appear on the status bar when they are on.
Turning On Forcing/Grouping from the Tool Bar Buttons

1. Check all variables that you want to force and/or group in the Force Enable
column or in the Group Enable column respectively of the Force List.
2. Toggle forcing on by choosing the button from the Advanced Operations

toolbar.
3. Toggle grouping on by choosing the button from the Advanced Operations

toolbar.
The symbols for forcing and grouping will appear on the status bar when they are
on.
Turning Off Forcing/Grouping from the On-Line Menu

1. Choose Online | Force | Forcing from the menu to deactivate forcing.
Note: If grouping is on, it will be turned off when forcing is deselected.
2. Choose Online | Force | Grouping from the menu to deactivate grouping.
Turning Off Forcing/Grouping from the Tool Bar Buttons
1. Toggle forcing off by choosing the button from the Advanced Operations
toolbar.
Note: If grouping is on, it will also be toggled off.
2. Toggle grouping off by choosing the button from the Advanced Operations
toolbar.

Updating the control after Force List is edited
While forcing, you can change any entries in the Force List. These changes can then
be updated in the control.
1. Edit the Force List.
2. Choose one of the following methods:
• Click the button from the Online menu.

• Select Online | Force | Update Forcing List from the menu.
Note: If you delete any or all entries from your force list without updating the
control, the entries remain active.
Viewing Enabled Variables
With the control running and your ladder file open, you are ready to enter variables
into a View List. Only one View List is created for each ladder file. It is given the RTD
extension and the same filename as the ladder file.
To bring up the View List, choose one of the following:
• Click the button from the View Navigator toolbar.

• Select View | View List from the menu
The View List Window appears with focus on the Name column. The Window
and columns can be adjusted.
You have four ways to enter a variable into the View List Window:

Copy/Paste
1. Copy the element in the ladder file that you want to place in the View List.
2. Open or activate the View List Window.
3. Position the focus in the View List grid and paste the selection.
If you are in a blank row, the variable you are entering will fill that row.
If you are in a row that already contains a variable, the new variable will
appear in a row above the existing one.
If you are in a row that is highlighted, the new variable will replace that row.
4. Check Enable.
Drag-n-Drop
2. Select the variable in the ladder to add to the View List.
3. Drag the selection from the ladder to the View List row you want to insert the
variable in and release the button.
4. Check Enable.
Right-Click Menu in Ladder

1. Select the variable in the ladder to add to the View List.
2. Right-click and select Add symbols to View List. The variable will be added
to the end of the View List.
3. Check Enable.
Manual Entry
2. Place the focus in the Name column of the View List.
3. Type in the name of the variable you want to add or click on the down arrow to
bring up a list of all variables in the software declarations table except function
blocks. If the symbol is an array, it will be entered into the list as an ARRAY().
You must enter the index number in the parenthesis.
4. Check Enable.
Turning Animation On in the View List

In order to view the variable values which are updated dynamically in the View List,
you must turn animation on in the View List.
1. Ensure that the View List has focus.
2. To turn on animation in the View List, choose one of the following:
• Click the button on the Advanced Operations toolbar

• Select Online | Animate from the menu

Controlling the Scan
When the control is running, the CPU repeatedly scans the application program in its
memory. A scan is the cyclical process of:
1. Reading data from the hardware input modules
2. Using the forcing list to modify input data
3. Executing ladder logic and using the data to update program variables*
4. Using the forcing list to modify output data
5. Sending commands to the hardware output modules
6. Sending data to the workstation to be displayed in animation and/or view
modes
Note: When you created your ladder program, the PiC hardware modules were
declared under Hardware Declarations. Each input/output point was assigned to a spe-
cific logic element through the Software Declarations.
* Step 3 above is referred to as the ladder scan and the remaining steps are referred to
as the system overhead. How long a scan takes depends on the length and complexity
of the program.
IMPORTANT
The PiC or MMC systems shut down as a safety measure if either the
ladder scan or the overhead takes more than 200 ms.
Note: To display the Scan Control menu, select Online | Control Opera-
tions | Scan Control.
WARNING
Do not use any commands in the Scan Control menu until you under-
stand how the control system runs and exactly how the command will
affect the application. Starting or stopping the scan at random may
cause injury or damage to machinery.
Stopping the Scan

When you stop the scan, the current scan is completed, but the logic commands sent to
the output modules are all zero. Power is still on to the system so all elements in the
program - timers, counters, input contacts, output coils, etc. keep their values until the
scan starts again.

To Stop the Scan, choose one of the following:
• Click the button from the Basic Online Operations toolbar

• Select Online | Control Operations | Scan Control | Stop from the menu
Running One Scan

The CPU will run through one complete scan and then send zeros to all the outputs
when this command is issued.
To Run One Scan, choose one of the following:
• Click the button with the BLUE arrow from the Basic Online Operations
toolbar.
• Select Online | Control Operations | Scan Control | Run One from the
menu.
Doing a Hot Restart

If you restart the scan with a hot restart, all the element values are kept as they were
when the scan stopped. The application continues as if the Stop scan command had not
been sent.
To do a Hot Restart, choose one of the following:
• Click the button with the circular RED arrow from the Basic Online Oper-
ations toolbar.
• Select Online | Control Operations | Scan Control | Hot Restart from the
menu.
Doing a Warm Restart

If you restart the scan with a warm restart, all elements that were declared with the
retentive attribute will keep the values they had when the scan stopped. All other ele-
ments return to the initial values they had when the module was first downloaded.
Scanning resumes and the application continues normally.
To do a Warm Restart, choose one of the following:
• Click the button with the circular YELLOW arrow from the Basic Online
Operations toolbar
• Select Online | Control Operations | Scan Control | Warm Restart from the
menu
Doing a Cold Restart

If you restart the scan with a cold restart, all elements are returned to their initial val-
ues declared by you as if the module had just been downloaded.

To do a Cold Restart, choose one of the following:
• Click the button with the circular BLUE arrow from the Basic Online
Operations toolbar
• Select Online | Control Operations | Scan Control | Cold Restart from the
menu
On-line Editing
In normal program development, you edit your ladder and then download the entire mod-
ule to the control to incorporate the changes. The scan is stopped during this download and
you must restart the scan when the download is complete.
There may be times when you need to edit or patch the ladder on-line without stopping the
scan. If you make changes to the ladder that is currently being scanned in the control and
choose compile and download, you are given two choices.
• Stop the Scan and Download (off-line edit)
or
• Patch the Scanning Ladder (on-line edit)
When you choose Patch the Scanning Ladder, only the changes you have just
made will be downloaded and the scan is not stopped. The changes will take effect
at the beginning of the next scan. These changes become a permanent part of the
program in your control. They are included in any backup from the control. When
you are working with UDFBs, you can patch the main module and the source lad-
ders of any UDFB. Animation is turned off when patching but forcing remains on.
When the patch download is complete, the information window will summarize
the resources listed below that you still have available.
• Data Bits (in hard bit systems only)
• Data Bytes
• Code Bytes
• Number of Patches (out of 100)
• Number of Label/Function Links (out of 27)
Patch the Scanning Ladder is not available in the following situations:
• If any changes have been made to the hardware declarations,
you must do a full download stopping the scan to incorporate them into
your ladder.
• If more than 40 internal tasks have been added/modified in the current lad-
der.
• If more than 100 patches have been added to the current ladder
Every time a network is modified, it is considered one patch but could
include several internal tasks.
• If more than 27 label or function links have been established in the current
ladder

• If the network to be patched contains a TASK.
• If the application program is in EPROM memory.
• If you have ignored a previous Save request from PiCPro.
• If you change or add initial values to existing variables,
you must do a full download stopping the scan to incorporate these into
your ladder. You can add new variables with initial values with on-line edit.
To perform an on-line edit or patch, follow these steps:

1. Enter your changes into the ladder. Save the file.
2. To display the Compile and Download Options dialog, choose one of the fol-
lowing:
• Click the button on the Compile toolbar

• Select Compile | Bin File | Compile & Download from the menu.
The Compile and Download Options box appears with the defaults shown.
3. Select Patch the Scanning Ladder and click OK.
To abort a patch
You can undo the last patch downloaded to the control with the Abort Last Patch com-
mand. This will remove the patch from the control but does not remove it from your
ladder. You can redo the patch in your ladder and do another patch download. The
Abort Last Patch command remains enabled after patching a ladder until one of the
following occurs:
• The next full download is performed.
• The ladder doc is closed.
• PiCPro is closed.
1. After a patch has been downloaded to the control, choose one of the following:
• Click the button on the Online toolbar

• Select Online | Control Operations | Abort last patch from the menu
2. The last patch is removed from the control. Edit your ladder to remove it from your
ladder program.

3. To download the edited ladder to the control, choose one of the following:
• Click the button from the Compile toolbar

4. Select Compile | Bin File | Compile and Download from the menu..
IMPORTANT
Aborting the last patch removes the operation but not necessarily the
effect of that operation from the control. For example, if you add a new
network that turns on a new coil and do a patch download followed by
an Abort Last Patch command, the new network is removed from the
control but the coil will remain on.
Printing
You can print your ladder file, the View list, Forcing list, or the Information Win-
dow. Put focus, by clicking, on the window you want printed, and choose File |
Print.
Printing the Ladder

Once your ladder program is developed, you can print it out using the print command.
To print the ladder file, follow these steps:
1. Make the window that contains the ladder active.
2. Choose any of the following to bring up the print dialog box:
• Click the button on the standard toolbar

• Select File | Print from the menu
• Press <Ctrl + P>
• Right-click and select Print

3. Make your selections or accept the defaults and click OK in the print dialog
box.
Selections in the Ladder Network Section of the Print Dialog
Include in Listing
The Include in Listing box is checked (default) and the Entire Ladder selected
(default). If you do not want to print the entire ladder you have two choices.
• You can print a range of networks by selecting Networks and entering a
range in the From: and To: boxes. The From/To boxes initially contain the
range of networks for the entire ladder.
• You can print a previously highlighted ladder selection by choosing Selec-
tion.

Cross Reference
When the Cross Reference box is checked (default), all cross reference informa-
tion on all elements in the ladder is printed. The listing includes:
• Name
• Type
• Source (Where written)
• Used (Where)
The listing is sorted alphabetically by the variable name. At the end of each net-
work, a Network Coil Usage list will be printed listing all the outputs along with
any other networks which reference the same output. Each contact/coil element
will also display cross reference information. Variable names longer than 22 char-
acters are displayed on a separate line followed by the ‘used in’ information.
• Beneath contacts/coils representing direct inputs/outputs, the I/O point is
displayed.
• Beneath all other contacts, the source network(s) is displayed.
If a variable name is longer than 21 characters, the name is displayed on a separate
line. The line(s) following the name display the type, attribute, source and used
information.
Full Comments
When the Full Comments box is checked (default), the entire comment for each
network is printed. If unchecked, the first line of each comment is printed.
Long Names
When the Long Names box is checked (default), the long name is printed below
each element in a ladder network for which you have entered a long name in soft-
ware declarations. This has no impact on ST networks.
Page Break at Function Block

When the Page Break at Function Block box is checked (default), a page break is
inserted to prevent a function block from being printed on two pages if possible.
Fit Width to Page

When the Fit Width to Page box is checked (default), the widest network deter-
mines the font, etc. so that the network will print on the page. If this is not checked,
printing can span multiple pages, both vertically and horizontally. Print size is
affected by current zoom settings and cell width options.

Selections in the Software Declarations Section of the Print Dialog
Include in Listing
When the Include in Listing box is checked (default), the software declarations
table is printed with the ladder. You can choose to sort the software declarations by
one of the following:
• Order Entered (default)
• Alphabetically
• By Type
Note: When you choose to print a portion of your ladder, only the software decla-
rations connected to the printed portion will be included.
If a variable name is longer than 8 characters, the name is displayed on a separate
line. The line(s) following the name display the type, attribute, I/O point, initial
value and long name.
Selections in the Hardware Declarations Section of the Print Dialog
Include in Listing
When the Include in Listing box is checked (default), the hardware declarations
are printed with the ladder.
Printing View List, Force List, or Information Window

You can also open a file and print the View List, Force List, or the Information
Window from the standard Windows print dialog box. Choose one of the follow-
ing:
• View | View List and then choose File | Print
• View | Forcing List and then File | Print
• View | Information Window and then File | Print
To print the view list, force list, or information window, follow these steps:
1. Ensure that the list or window you want to print is active by clicking it. If you
want to print part of the list or window, highlight that portion before choosing
the print command.
2. Choose any of the following to bring up the print dialog box:

• Select File | Print from the menu
• Press <Ctrl + P>

3. Make selections or accept the defaults and click OK in the print dialog box.
Printout Symbols
When you print out a copy of your ladder file, these symbols may appear.
Symbol Description
& Appears in the cross reference section of the printout and in

the Network Coil Usage section at the end of each network
telling you that the output/coil is sourced in more than one
place.
/ Appears in the cross reference section of the printout and

also in the Network Coil Usage section at the end of each
network telling you that the contact is normally closed.
@ If a network contains a complex variable name, an alias will

be substituted in the printout. The alias format is @1 for the
first substitution, @2 for the second substitution…up to
@255. Numbering is restarted within each network.
Appears under a direct input to indicate the following:

I04.01 Input in master rack (I), slot 4 (04), channel 1 (01)
or or
I2.04.01 Input in expansion rack 2 (I2), slot 4 (04), channel 1 (01)
or
A MMC Limited Edition or MMC for PC specific Input
point
Appears under a direct output to indicate the following:

O03.01 Output in master rack (O), slot 3 (03), channel 1 (01)
or or
O2.03.01 Output in expansion rack 2 (O2), slot 3 (03), channel 1 (01)
or
A MMC Limited Edition or MMC for PC specific Output
point

Troubleshooting the Print Option
If your file does not print, check the following:
• Printer is on-line and supplied with paper.
• The computer end of the cable is plugged into the correct port. Make sure the
connections are secure on both ends.
• Run the printer’s diagnostic tests, then try to print the file again.
• If the printer still does not print, check these possibilities:
• An incorrect or damaged cable
• A malfunctioning port on the workstation
• A malfunctioning port on the printer
Building a Dependency List
When you build a dependency list, you create a complete list of all the files that are
related to the module you are currently running in PiCPro. The list can include all the
ladder file source, REM source, UDFB/TASK sources, and UDFB/TASK libraries
required to run the program. If you have FLASH memory installed on your control,
the dependency list can be used to send all the listed files to the FMSDISK using the
Flash Disk Operations under the online menu.
To build a dependency list, follow these steps:

1. Select View | Build Dependency List from the menu.
2. The Build Dependency List box appears. It defaults to include the program
source, the UDFB/TASK source, and the UDFB/TASK libraries.
The Other file section allows you to include additional files in your depen-
dency list.

3. When you click OK, the list is generated and saved to the current folder of the
active ladder. The filename is that of your ladder with a DPL extension.
4. To view your dependency list, open the .dpl file in a text editor program.
Comment Import / Export
Importing Comments
You can import a text file of exported comments (or a text file of comments you have
created) into your ladder file.
1. Select Ladder | Comments | Import from the menu.
2. Browse to the location on your workstation of the text file you want to import
and select it so that it appears in the entry field.
3. Select either the option to update the comments or the options to replace all
comments with the text file.
• Update comments with text file option: This is the default. Only the com-
ments whose index or network number is in the text file will be modified in
the ladder.
• Replace ALL comments with text file … option: ALL comments in the
ladder file will be removed and replaced with the comments defined in the
text file. In other words, any comment in the ladder file that has no counter
part in the text file is removed.
4. Click the Start button. The Action box shows the progress.
Note: After importing comments, the ladder file must be saved to keep these
changes.
Exporting Comments
You can export the ladder comments to a text file. You can then open and edit the text
file using a text editor. This text file can then be imported back into the same ladder or
into a different one.
1. Select Ladder | Comments | Export from the menu.
2. Enter the path and filename for the text file which will hold the comments. The
default will be the path and filename of the ladder file with a .txt extension.
3. Select the option to use index numbers (#n) used by the software to keep track
of each network comment or to use the actual network numbers (@n). The
symbol and number appear above your comment in the text file.
IMPORTANT: Never change the number or use the # (or @) symbol in the
first column of any comment you edit in the text file.
4. Click the Start button. A bar shows the progress.
Note: Comments in a ST network that begin with (* and end with *) are not
exported.

Communications
Communications Settings
Your workstation and control must be set up to communicate with each other. The
Comm Settings command found under the Online menu allows you to set the serial
communications port, the baud rate, the IP address if communicating via Ethernet, and
the type of communications you are doing: serial or Ethernet-TCP/IP.
• The Type section specifies the type of communicating you are doing: Serial,
TCP/IP (if you have an Ethernet card in your workstation), or TCP/IP Relay
(if you do not have an Ethernet card in your workstation), or Local MMC for
PC (if you have an MMC for PC in your workstation). With TCP/IP Relay, you
select an RS232 connection to a control and then an Ethernet connection to
another control that has an Ethernet-TCP/IP module installed. Use the G&L
Ethernet-TCP/IP configuration tool to set up the module. See CHAPTER 8.
• The Serial section is active if you choose Serial or TCP/IP Relay as a commu-
nication type. You select a RS232 communication port that the control is con-
nected to and a baud rate to communicate at.
• If you choose TCP/IP or TCP/IP Relay, the Network section is active. You
enter the IP Address in dotted decimal format, name, or internet format. This
is the address of the control you are communicating with over Ethernet.
• If you click the Net Info button, additional information associated with the IP
Address/Name is displayed. An indication is also provided if the destination IP
Address/Name is on the network and this computer can communicate with it.
• The TCP/IP Timeouts section is available if you choose either TCP/IP or
TCP/IP Relay. Selecting Extend timeouts increases the timeout value for
TCP/IP network and internet connections between PiCPro and the control.
This means that PiCPro will wait longer for a response from the control before
issuing a communications timeout message. Note: If you are experiencing tim-

eouts with your control that is connected via your TCP/IP network or the inter-
net, try running with this option selected. Be aware, however, that because
PiCPro will now wait longer for messages from the control, you will probably
experience a slowdown in the responsiveness of PiCPro (especially animation,
which relies on the receipt of messages from the control to supply the anima-
tion information.)
Communication Status
The current status of communications with the control, as well as additional informa-
tion about the control can be displayed.
To access this information, choose one of the following:
• Click from the basic online operations toolbar

• Select Online | Status from the menu
From the dialog, click the question mark in the top right corner and then click on any
of the status comments displayed to get further information. You cannot change any of
the information from this dialog.
Time Read / Set

The control has its own battery-powered clock located in the CSM. This dialog allows
you to edit the current time and date inside the control.
Get System Time fills the edit fields with the data from the workstation settings.
Note: To ensure that the time for PiCPro in Windows and PiCPro for DOS match, you
must add a line in your CONFIG. SYS file.
The following example applies to a time zone setting of Central Standard Time with a
six hour difference between UTC and local time and Central Daylight Savings time.
Set TZ=CST6CDT
Refer to the DOS documentation regarding the environment variable TZ and how to
set it for your time zone.
Downloading a Hex File
The Download Hex File command allows you to do any of the following;
• Configure application/RAMDISK size.
• Update the control’s firmware.
• Update TCP/IP firmware.
• Update the SERCOS module firmware.
• Load the ladder flash memory on the CPU.
• Clear the ladder flash memory.
• Clear the ladder application memory.
NOTE
Back up your RAMDISK and ladder before downloading new firmware.
To Download a Hex file for a PiC or Standalone MMC

To use the Download Hex command, PiCPro must be running on your workstation and
communicating with a PiC or MMC control. No files can be open. If a file is open, this
command will be grayed and inaccessible.
Follow this procedure to download a hex file:
1. Select Online | Download Hex from the menu.
2. The Download Hex dialog appears. Use Browse to select the Hex file you
want to download. The default location for these files is the Utilities folder for
PiCPro for Windows.
3. Select the appropriate Baudrate, if different from the default of 57600.

4. Select the Port if different from the default (PiCPro port).

5. Click Start to begin downloading the hex file. Read and follow each prompt
carefully. They will tell you to turn the control off and then back on again.
6. A status bar will show you the progress of the download.
7. If any errors occur, they will be reported in the Information Window.
To Download a Hex file to a MMC for PC

To use the Download Hex command, PiCPro must be running on your workstation and
communicating with a PiC or Standalone MMC control. No files can be open. If a file
is open, this command will be grayed and inaccessible.
Follow this procedure to download a hex file:
1. Select Online | Download Hex from the menu.
2. The Download Hex dialog appears. Use Browse button to select the Hex file
you want to download. The default location for these files is the Utilities
folder for PiCPro for Windows.
3. Use Select Port drop down list to select the com ports available on the com-
puter. Select the MMC for PC port.
4. Use the Local checkbox to indicate that the MMC for PC is in the local
machine. If the MMC for PC is not in the computer you are currently using,
uncheck the box.
5. Use the Select TCP/IP location drop down lists to enter the IP Address.
6. Click Start to begin the download process.
7. A status bar will show you the progress of the download.
8. If any errors occur, they will reported in the Information Window.
Configure Application / RAMDISK Size

It is possible to change the memory configuration in controls with 486DX processors
and the MMC for PC. The default configuration is 256K of RAMDISK and 512K of
Application memory. If you find it necessary to change the default configuration, use
the Download Hex command from the Online menu available before any files are
open.
The five memory configuration hex files are found in the Firmware folder in your
PiCPro for Windows folder. (Memory sizes shown are approximate) They are:

• Con512.hex (256K of RAMDISK and 512K of application memory) default
• Con384.hex (384K of RAMDISK and 384Kof application memory) optional
(Cannot be used with extended memory feature)
• Con640.hex (128K of RAMDISK and 640K of application memory) optional
WARNING
The contents of the RAMDISK and APPLICATION

memory areas will be erased when you change the mem-
ory configuration. You will have to reload the contents of
these memory areas after changing the configuration.
Update CPU’s Firmware

To update the CPU firmware, connect the workstation to the control.
Using the Online | Download Hex command, select the appropriate .hex file from the
Firmware folder. Click Start once you have set the proper port and baudrate (if differ-
ent from the default settings).
• For PiC900 systems, select P94X##.hex
• For PiC90 systems, select P904X##.hex
• For standalone MMC, select MMC##.hex
• For analog MMC for PC, select MMCPCA##.hex
• For SERCOS MMC for PC, select MMCPCS##.hex
Where ## is a version number.
Update TCP/IP Module Firmware

To update the Ethernet TCP/IP module firmware, connect the workstation to the
RS232 Com 2 Port on the module.
Using the Online | Download Hex command, select the tcpip##.hex file from the
Firmware folder. Click Start once you have set the proper port and baudrate (if differ-
ent from the default settings).
Where ## is the version number.
Update SERCOS Module Firmware

To update the SERCOS module firmware, connect the workstation to the RS232 Port
on the SERCOS module.
Using the Online | Download Hex command, select the SERCO##.hex file from the
Firmware folder. Click the Start button once you have set the proper port and baudrate
(if different from the default settings). Where ## is the version number.

Update Drive Firmware
To update the drive firmware, connect the workstation to the drive.
Using the Online | Download Hex command, select the DRB####.hex file from the
Firmware folder. Click Start once you have the proper port and baud rate (if different
from the default settings).
Where #### is a version number.
Download Ladder Hex File

A ladder can be downloaded into the CPU flash memory using Online | Download
Hex after you have created the .hex file using Compile | Hex File.
If the battery in the control were to become low on power (or run out), when the CPU
was next powered up, the ladder would be taken from the flash memory and loaded to
the application memory.
Clear Flash Memory

To clear the flash memory in the control, from the Online menu, select Download
Hex. Select the clrflash.hex file from the Firmware folder. Click Start once you have
set the proper port and baudrate (if different from the default settings).
This procedure should be done before using the Clear Application procedure.
Clear Application Memory

If you are using either a standalone MMC or an MMC for PC control, the Clear Appli-
cation Memory command provides a software solution to clearing out a ladder appli-
cation that may not be scanning correctly. When you choose the command from the
Online menu, the Download Hex dialog box appears. The entry field for a hex file is
grayed because PiCPro automatically enters a file called clrapp.hex. This file is down-
loaded to the standalone MMC or MMC for PC when you choose Start. If connected
to an MMC, you will be prompted to turn the control off and on again.
Some examples of common programming errors that require you to do this include:
• Programming a backwards jump and losing the scan
• Declaring the wrong Block I/O and getting a Block I/O error.
When these programming errors occur, communication to the control is lost. By using
the Clear Application Memory command to clear the ladder currently in the MMC or
MMC for PC control, communication is re-established and you can proceed to down-
load a ladder file.

To clear application memory with any MMC CPU:
Select Online | Clear Application Memory from the menu.
IMPORTANT
An action that affects the contents of the application memory, does not
affect the contents of the flash memory, and vice versa.
If a ladder is downloaded to flash memory, and no ladder is loaded in
application memory, the ladder in flash memory is scanned. If subse-
quently, a ladder (the same or another) is downloaded to application mem-
ory, the ladder in application memory is scanned.
The clrapp.hex file does not clear the flash memory, and the clrflash.hex
file does not clear the ladder in application memory.
Backing Up and Restoring User Programs
Backing Up User Programs

Your program in the control memory may be backed up as a binary file directly to a
computer disk. With your workstation connected to the control and communications
established, follow these steps:
1. Select Online | User Program | Backup | Application Program from the
menu. Backup will be bold and selectable if there is an existing communica-
tion link to your workstation.
2. The Backup File to PC dialog appears. The filename of the ladder file cur-
rently in the control memory with a .bin extension will appear in the entry
field.
3. Choose the location where you want to save the binary file and choose Save.
A progress box will tell you the file is being saved to the workstation.
The file can later be restored to the control using the Restore command.
Restoring User Programs

A program file saved in binary format with a .bin extension can be restored to the con-
trol memory by doing the following:
1. Select Online | User Program | Restore from the menu.
2. The Restore File to the Control dialog appears. Restore will be bold and
selectable if there is an existing communication link to your workstation.

3. On your workstation, find the location of the binary file you want to restore
and click on it so that it appears in the entry field. When the correct bin file is
in the entry field, choose Restore. A progress box will tell you the file is being
downloaded to the control.
PiC Restore
You can restore your PiC or MMC controls with the firmware, ladder (hex or binary),
RAM disk data (binary), and flash memory if you ever lose the data in your control. You
will need the required files either previously saved by you or supplied by your OEM.
PiC Restore is available only if an application ladder is not open. From the Online menu,
choose PiC Restore. The following dialog appears.
To restore or save files, enter the path and name of the restore file (.ppr).
The five check boxes allow you to check the files you want sent to the control. (The check
boxes will default to any settings currently in an existing restore file.)
Selecting Restore starts execution of the restore file. When the download is complete
without any errors, the information window will indicate the results by listing the files sent
to the control.
The Save to File button allows you to save the path and file names of the hex, bin, or dpl
files and the check box settings to the restore file.
Note: Generic filenames are shown above. Your filenames and locations will be different.
In addition to using PiC Restore, a standard text editor can be used to create the restore
file. The format for the restore file is shown below. The filenames are listed in the order

they are to be sent to the control and shown in the PiC Restore dialog. Note: Generic file-
names are shown below.
(SendDPL can also be entered as: SendFlash yes C:\filelocation\Ladder.ldo, and any
extension can be used.)
The first field is the type of send: either SendHex, SendBin, SendDPL, SendFlash, or
Empty. The second field contains either a “yes” or a “no” and defines the default value
used for the checkbox. The third field is the name and path of the file. Make sure the type
of file corresponds with the type of send. For example, use SendHex for sending a hex file.
If there is a file type you aren’t using, type in ”Empty No Null” (without the quotes) to so
indicate.

CHAPTER 4 Setting Up the MMC Smart Drive
Overview: MMC Smart Drive Setup
The Drive Setup program in PiCPro allows you to identify all analog interfaced digital drives
used in your application. As each drive is identified, it is put into a Drive List. Within Drive
List view, you can add, remove, rename, cut, copy and paste drives. You can then save infor-
mation to a drive file.
The Drive Setup program also allows you to monitor and/or configure characteristics of the
analog interfaced digital drives in the form of parameters. Drive Data view is activated from
the Drive List view. Within Drive Data, the parameters for each drive can be monitored and/or
configured.
Drive Control Panel/Oscilloscope view, subsequently referred to as Control Panel / Oscillo-
scope view, allows you to view the drive in action. You can capture data throughout the drive
setup process to compare the effect of changes to the parameters.
To use Drive Setup:
1. Start your drive list by creating a new analog interfaced drive system file or opening
an existing analog interfaced drive system file.
2. Build your drive list - add, remove, rename, cut, copy and paste drives.
3. Save the analog interfaced drive system file (name.ADV), subsequently referred to as
drive file.
4. Further refine or monitor parameters from the Drive Data view.
5. Analyze drive operation from the Control Panel / Oscilloscope view using the Oscillo-
scope tool.
Analog Interfaced Drive Terminology

To better understand the remainder of this chapter, you should be familiar with the
following terms:
Drive file/list Access Status - ONLINE or OFFLINE. See ONLINE vs.
OFFLINE Drive List/Drive Data Views for operational details.
The first drive list accessed becomes the ONLINE drive list. Any other drive
lists subsequently accessed are OFFLINE. To change an OFFLINE drive list
to ONLINE, the current ONLINE drive list must be closed. The actual data is
uploaded and monitored for the connected drive if it is in the ONLINE drive
list. Both file data and actual data can be modified for the connected drive if it
is in the ONLINE drive list. Only file data can be modified in OFFLINE drive
lists, actual data is not available.
Setting up the MMC Smart Drive 209

Data – Parameter information is provided in two forms – File and Actual.
File data is the information read from a drive file (.adv) or available to be writ-
ten to a drive file (.adv). File data can be downloaded to a drive on command
if the drive list is ONLINE. File data contains two elements for each parame-
ter, 1) File values and 2) File units. These elements appear as columns in the
Drive Data view.
Actual data is the information uploaded from the connected drive in an
ONLINE drive list. Actual data is dynamic. Changes are downloaded imme-
diately to the connected drive. Actual data can be copied to file data for stor-
age in a drive file (.adv), but cannot be saved directly into a drive file (.adv).
Actual data contains two elements for each parameter, 1) Actual values and 2)
Actual units. These elements appear as columns in the Drive Data view or
Control Panel / Oscilloscope view.
Maintenance Mode
Maintenance mode allows quick identification of an analog interfaced digital
drive.
1. Connect the drive to the workstation and open PiCPro
2. Choose one of the following methods to start Maintenance Mode:
• Click the button on the drive list standard toolbar

• Select Online | Drive Operations | Maintenance from the menu.
Note: If a drive list is already open, the following prompt will be displayed:
Choose OK and close all drive lists, then retry step 2.

• If the drive has not been initialized, you will be prompted to name the drive
and select the motor. See the section titled “Connect to an Uninitialized
Drive not in the Drive List.”
• If the drive has already been initialized, the Drive List view will be dis-
played with a line for the new drive. The Drive Data view will also be dis-
played.
3. Modify, download, or monitor configuration parameters.
4. Save the current configuration to a drive file (.adv).
210 Setting up the MMC Smart Drive

Accessing Drive System Setup
To access Analog Interfaced Drive System setup information, open or create an Analog Inter-
faced Drive System file.
Create a New Analog Interfaced Drive System File

1. Choose one of the following methods to create a drive file:

• Select File | New from the menu
• Press <Ctrl + N>
2. Select Analog Interfaced Drive System from the dialog that appears.
3. Choose OK to create a drive file. Select Cancel or to close the dialog

without creating a drive file. Select Help to display information related to cre-
ating new PiCPro application files.
Open an Existing Analog Interfaced Drive System File

1. Choose one of the following methods to open a drive file:
• Click the button on the standard toolbar.

• Press <Ctrl + O>
2. The Open dialog appears. At the bottom, choose Analog Interfaced Drive System
Files (*.adv) from the drop down list in the Files of type: field. A list of drive files
displays.

3. Select the file you want to open.
• Select Open
• Double-click the file name.
• Press Enter key.
Note: Select Cancel or to exit the dialog without opening a drive file.
4. A drive list will either display as an OFFLINE Drive List view or an ONLINE
Drive List view.
OFFLINE Drive List view
An OFFLINE Drive List view will appear when there is another drive list open.
This is indicated by the word OFFLINE appearing to the right of the filename.
ONLINE Drive List view

An ONLINE Drive List view will appear when it is the only Drive List view being
displayed. An ONLINE Drive List view is indicated by the word ONLINE to the
right of the filename.
In the ONLINE Drive List view, only one analog interfaced digital drive can be
connected at a time.

ONLINE Drive List view Details
This chart shows the possible states of a connected drive appearing in the ONLINE
Drive List view. Each column of information will be explained.
Drive Label Connected? Enabled? Fault?
Drive1 No
Drive2 No Yes/No Fault/Warning description when last con-

nected
Drive3 Yes Yes
Drive4 Yes No
Drive5 Yes Yes Warning(s) description
Drive6 Yes No Warning(s) description
Drive7 Yes No Fault(s) description

Drive Label
The drive label consists of two elements: 1) a drive status icon (shown in the table
below) and 2) an alphanumeric string that represents the drive name.
The drive name must adhere to the following criteria: 1) drive name is limited to
31 characters; 2) first character must be an alpha or underscore; 3) the remaining
characters can be alphanumeric or underscores; 4) the strings are not case sensi-
tive, therefore drive1 is the same as Drive1 or DRIVE1; and 5) drive names must
be unique.
Icon Indication
Drive is not connected.
Black X
Drive connected to PiCPro, drive enabled, no faults.
Green Circle
Drive connected to PiCPro, drive not enabled, no faults.
White Circle
Drive connected to PiCPro, drive enabled, warning(s).
Green Circle
with Yellow
Triangle
Drive connected to PiCPro, drive not enabled, warning(s).
White Circle
with Yellow
Triangle
Drive connected to PiCPro, drive enabled, fault(s).
Red Octagon
Connected?
A Yes in this column indicates the drive is connected to the workstation. Only one
drive can be connected at a time. A No in this column indicates the drive is not
connected to the workstation.
Enabled?
A Yes in this column indicates the connected drive is enabled or previously con-
nected drives were enabled when disconnected from the workstation. A No in this

column indicates the connected drive is not enabled or previously connected drives
were not enabled when disconnected from the workstation.
Faults?
If this column is blank, there are no faults or warnings registered for the connected
drive or the previously connected drives when disconnected from the workstation.
If a single fault or warning exists for the connected drive or existed for the previ-
ously connected drives when disconnected from the workstation, the fault or warn-
ing description will be displayed. If multiple faults or warnings are detected for
the connected drive or the previously connected drives when disconnected from
the workstation, the fault and/or warning numbers will be listed. More details on
the faults and warnings can be obtained in the Drive Data view.
Data - File vs. Actual
Text color indicates whether there are differences between file data and actual data.
If there are differences, the text color is blue. If there are no differences, the text
color is black.

ONLINE Drive List/Drive Data view Scenarios
Connect to Drive in Drive List

Physically connect the drive to the workstation using the PiCPro cable.
The Status bar connection icon will change to

Configuration parameters will automatically be uploaded into actual data for the
newly connected drive.
Differences between file data and actual data will be identified for the newly con-
nected drive.
Drive List view
The drive label icon and drive information will change to reflect the current
status of the newly connected drive.
Drive Data view
The drive label icon and drive information will change to reflect the current
Disconnect the Current Drive and Connect to a Different Drive Already in the
Drive List
Physically disconnect the PiCPro cable from the existing drive and connect it to the
desired drive.
The Status bar connection icon will change to and then change back to .
Configuration parameters will automatically be uploaded into actual data for the
Differences between file data and actual data will be identified for the newly con-
nected drive.
Drive List view
1. The drive label icon will change to for the previously connected drive.
2. The drive label icon and drive information will change to reflect the current
Drive Data view
1. The drive label icon will change to for the previously connected drive.
2. Actual data can no longer be changed for the previously connected drive.
It will remain unchanged until the drive is reconnected.
status of the newly connected drive

Connect to an Initialized Drive not in the Drive List
Physically connect the drive to the workstation using the PiCPro cable.
The Status bar connection icon will change to
A prompt will be displayed asking if you want to add the drive to the drive list
(e.g. Drive6):
Choose Yes to add the drive to the drive list. Select No or Cancel or click
to exit the dialog without adding a drive to the drive list.
Configuration parameters will automatically be uploaded into actual data for
the newly constructed drive.
Actual data is copied to file data for the newly connected drive. There will be
no differences identified between file data and actual data.
Drive List view
1. A line will be added to the drive list for the newly connected drive.
2. The drive label icon and drive information will reflect the current status of
the newly connected drive
Drive Data view
1. Actual and File columns will be added to the Drive Data view for the
the newly connected drive.

Connect to an Uninitialized Drive not in the Drive List
1. Physically connect the drive to the workstation using the PiCPro cable. The
Status bar connection icon is changed to
2. The following prompt will appear:
3. At Name: enter a name for the drive. The drive name must adhere to the fol-
lowing criteria: 1) drive name is limited to 31 characters; 2) first character
must be an alpha or underscore; 3) the remaining characters can be alphanu-
meric or underscores; 4) the strings are not case sensitive, therefore drive1 is
the same as Drive1 or DRIVE1; and 5) drive names must be unique.

4. At Motor Model: select a motor from the dropdown list.
5. Choose Yes to add the drive to the drive list. Select No, Cancel or to close
the dialog without adding the drive to the drive list. Select Help to display
information related to adding drives to drive list.
Drive name, motor model and default values for the remaining drive configuration
parameters will be downloaded to the drive automatically.
Drive List view
1. A line will be added to the drive list for the newly-connected drive.
Drive Data view
1. Actual and File columns will be added to the Drive Data view for the
the newly connected drive.

Drive Information Operations
Insert/Add a New Drive to a Drive List

Up to 32 analog interfaced digital drives are allowed in a drive list.
1. Choose one of the following methods to insert/add a drive to the drive list:
• Select Edit | Insert Drive... from the menu
• Press the Insert key
• Right-click and select Insert Drive...
2. The Insert Drive window will appear.
3. At Name: enter a name for the drive. The drive name must adhere to the fol-
lowing criteria: 1) drive name is limited to 31 characters; 2) first character
must be an alpha or underscore; 3) the remaining characters can be alphanu-
meric or underscores; 4) the strings are not case sensitive, therefore drive1 is
the same as Drive1 or DRIVE1; and 5) drive names must be unique.
4. At Motor Model: select a motor from the drop down list.
5. At Drive Model: select a drive model from the drop down list.
6. Choose OK to insert/add a drive to a drive list. Select Cancel or to close

the dialog without inserting/adding a drive to a drive list. Select Help to dis-
play information related to inserting/adding a drive to a drive list.
File data will be loaded with selected motor model, power section and default
values for the remaining configuration parameters.

If the name of the drive matches the name of the currently connected drive, the
following events will take place:
Configuration parameters will automatically be uploaded into actual
data for the connected drive.
Drive List view

1. A line will be added to the drive list for the connected drive.
2. The drive label icon and drive information will reflect the current
status of the connected drive.
Drive Data view

1. Actual and File columns will be added to the Drive Data view for
the connected drive.
2. The drive label icon and drive information will reflect the current
status of the connected drive.
If the name of the drive does not match the name of the currently connected
drive, the following events will take place:
Drive List view

1. A line will be added to the drive list.
2. The drive label icon will reflect that the drive is not connected.
Drive Data view

1. Actual and File columns will be added for the drive. The Actual
columns will be empty because the drive is not connected.
2. The drive label icon will reflect that the drive is not connected.
Delete a Drive from a Drive List
1. Select the desired drive(s) in the Drive List. See How to Select Drives for
selection methods.
2. Choose one of the following methods to delete a drive from a drive list:
• Select Edit | Delete Drive(s)... from the menu
• Press the Delete key
• Right-click and select Delete Drive(s)...

3. The following window will appear:
4. Choose Yes if you want to delete the selected drive(s). Select No, Cancel
or if you do not want to delete the drive(s) from the Drive List.
If Yes is selected, the drive(s) will be deleted from the Drive List as shown
below.
Note: If the selected drive(s) have outputs overridden, an additional message will
be displayed:
Yes A user fault is set in the drive with overridden outputs.

Control of the outputs is returned to their assigned states.
Then the selected drive(s) are deleted.
No Selected drive(s) are not deleted
Rename a Drive in a Drive List
1. Choose a single line in the Drive List and do one of the following.
• Click the button from the drive list standard toolbar

• Select Edit | Edit Drive Name from the menu
• Press <Ctrl + Shift + N>
• Right-click and select Edit Drive Name

2. The following dialog will be displayed when the drive being renamed is
not the connected drive:
The following dialog will be displayed when the drive being renamed is the
connected drive:
Update Connected Drive Name will be checked by default. If you do not

want to update the connected drive’s name, click the box to uncheck it.
Note: Removing this check allows the name of the drive in the drive list
to be changed but does not change the name of the connected drive.
When OK is selected, the drive’s icon changes to ‘X’ to indicate the
drive name no longer matches the name of the connected drive.
3. At New Name: enter the new name for the drive. The drive name must
adhere to the following criteria: 1) drive name is limited to 31 characters;
2) first character must be an alpha or underscore; 3) the remaining charac-
ters can be alphanumeric or underscores; 4) the strings are not case sensi-
tive, therefore drive1 is the same as Drive1 or DRIVE1; and 5) drive names
must be unique.
4. Choose OK. The drive will be renamed if a valid name has been entered.
Note: Select Cancel or to close the dialog without renaming the drive.
Select Help to display information related to renaming a drive.
Edit Drive Data

1. From the Drive List view, select the drive you want to edit.
2. Choose one of the following methods to edit parameters:
• Click the button on the drive list standard toolbar.

• Double-click on the drive.
• Select Edit | Edit Drive(s) Data from the menu.
• Press <Ctrl + Shift + D>
• Right-click and select Edit Drive(s) Data.
The first time Drive Data is displayed after installing PiCPro, the Basic View
will be displayed. Only parameter values with white backgrounds can be
edited. Parameter values with grayed backgrounds cannot be edited. Moni-
tored parameter values and red text will have gray backgrounds. Some actual
values will have gray backgrounds while the drive is enabled. Disable the
drive to make these parameter values available for editing.
Note: If Drive Enable is not assigned to a drive input, the Drive Enable is on
all the time. To disable the drive to make parameter changes, set a user
fault.
To change parameter values while in Drive Data view, do one of the following:
1. Double-click on the value
2. Select the value and press Enter key.
3. Select the value and just start typing.
Changes to parameter values in the actual data column are sent to the drive
immediately.
Changes to parameter values in the file data column will need to be down-
loaded to the drive if the change is required in the drive. See Download File
Data.
Cut/Copy/Paste from the Drive List View

The Cut, Copy, and Paste Drive(s) commands allow you to cut or copy drives
from one drive list and paste them into another drive list.
The Copy Drive(s) command places a copy of the selected item(s) on the clip-
board.
The Cut Drive(s) command removes the selected item(s) from the drive list
and places them on the clipboard.
Once the selected item(s) are on the clipboard, you can use the Paste Drive(s)
command to add the item(s) to the drive list.
How to Select Drives

Single drive is selected by left-clicking the drive name.
Multiple drives can be selected at the same time if they are part of the same
drive list.
• To select drives next to each other in the drive list, select a drive, hold
down the Shift key while pressing the up/down arrow or hold down the
Shift key and select another drive. The entire block of drives will be dis-
played as selected.

• To select drives not next to each other in the drive list, select a drive then
hold down the Ctrl key while left-clicking the other desired drives within
the same drive list.
Cut a Drive
1. Select the drive(s) you want to cut. See How to Select Drives for selection
methods.
2. Choose one of the following methods to issue the Cut Command:

• Select Edit | Cut Drive(s) from the menu.
• Right-click and select Cut Drive(s).
Note: Cutting a drive in Drive List view cuts the file data for the drive. If the
actual data is different when a cut command is selected, you will be
prompted to decide if actual data should replace the file data before the
cut takes place.
Note: If the selected drive(s) have outputs overridden, an additional message
will be displayed:
Yes A user fault is set in the drive with overridden outputs. Control of
the outputs is returned to their assigned states. Then the selected
drive(s) are cut.
No Selected drive(s) are not cut.
Copy a Drive
1. Select the drive(s) you want to copy. See How to Select Drives for selec-
tion methods.
2. Choose one of the following methods to issue the Copy command:

• Select Edit | Copy Drive(s) from the menu.
• Right-click and select Copy Drive(s).

Note: Copying a drive in Drive List view copies the file data for the drive. If
the actual data is different than the file data when a copy command is
selected, you will be prompted to decide if actual data should replace
the file data before the copy takes place.
Paste a Drive
1. Select a location for the paste.

2. Choose one of the following methods to issue the Paste command:

• Select Edit | Paste Drive(s) from the menu.
• Right-click and select Paste Drive(s).
Note: If there is already a drive list with the same name as the drive to be
pasted, a prompt will be displayed, asking for a new name for the drive
to be pasted.
Save and Save As
1. Select the drive list or Drive Data view you want to save.
2. Choose one of the following methods to issue the Save command:

• Select File | Save from the menu.
• Press <Ctrl + S>.
• Choose Yes when prompted by a dialog whether you wish to save the
file.
The first time the drive file is saved, you will be prompted to provide a file-
name and location. The prompt displays your default directory. Enter a file-
name and location desired. Choose Save to complete the save command. If
Cancel or is chosen, the dialog disappears and the drive file is not saved.

.
If you wish to give the drive file a different name, choose File | Save as... You
will be prompted to provide a filename and location. The prompt displays your
default directory. Enter a filename and location desired. Choose Save to com-
plete the save command. If Cancel or is chosen, the dialog disappears and
drive system file is not saved.
Note: File data is saved with a Save or Save as command. If differences exist
between file data and actual data, you will be prompted to update the file
data with the actual data for each drive in the drive file that has differences
before the Save or Save as is executed. Choose Yes to update the file data
with the actual data for the specified drive. Choose No to keep only the file
data, ignoring the actual data. Choose Cancel or to exit the dialog
without saving the drive file. Once each drive with a difference has been
addressed, the Save or Save as command will execute.
Close
When closing a Drive List view, the associated Drive Data view will also close. If
drives have been modified without being saved, you will be prompted to save the
drive file.

When closing PiCPro, you will be prompted to save any modified drive files that
have not been saved.
Note: If no changes have been made to file data, but differences exist between
file data and actual data, you will be prompted to save the drive file.
Note: If the drive file has drive(s) that have outputs overridden, an additional
message will be displayed.
Yes A user fault is set in the drive with overridden outputs. Control of the
outputs is returned to their assigned states. Then the drive file closes.
No The drive file is not closed.
ONLINE vs. OFFLINE Drive List/Drive Data views

The following operations/commands can be executed from each view.
Operation/Commands ONLINE ONLINE OFFLINE OFFLINE

Drive List Drive Data Drive List Drive Data
Insert/Delete Drive X X
Cut/Copy/Paste Drive X X
Edit Drive Data X X
Save Drive System File X X X X
Save Drive System File X X X X
to Different File
Print Information for All X X X X
or Selection of Drives
Rename a Drive X X
Online | Drive Opera- X X
tions
View Control Panel/ X X
Oscilloscope

Only one drive list can be ONLINE at a time. All other drive lists opened will be
OFFLINE. To change an OFFLINE drive list to ONLINE, the current ONLINE
drive list must be closed.
The OFFLINE Drive List view only maintains file data, whereas the ONLINE
Drive List view maintains file data for all the drives in the drive list and actual data
for all the drives connected since the drive list was opened.
ONLINE Operation
1. When the Drive List view first becomes the ONLINE Drive List view, if
the connected drive is in the drive list, the parameters of the connected
drive are uploaded from the drive to the actual data. The actual data and
file data are compared. The Drive List view and its Drive Data view are
updated to reflect differences between the file data and the actual data. If
the connected drive is not in the Drive List view, you will be prompted to
insert/add the drive. If you choose Yes to the prompt, the drive data will be
uploaded and stored in both the file data and the actual data. The drive will
be added to the Drive List and no differences will be indicated. Note:
When drive maintenance is selected, no differences will be shown, actual
data will be loaded into file data.
2. In the Drive List view, blue text color indicates that differences exist
between file data and actual data of a connected drive or any drive con-
nected since the drive file has been opened. To see the detail of the differ-
ences, double-click on the connected drive in the Drive List view. This
activates the Drive Data view. The various parameters are displayed in col-
umns under Actual data (information uploaded from the drive) and File
data (information read from a saved drive file). Those parameters where
the actual data differs from the file data are displayed in a blue color.
3. When the cable is moved from one drive to another, the actual data for the
previously connected drive is grayed out and can no longer be modified
until the drive is reconnected. If differences existed between file and actual
data, differences will still be indicated by blue text. If the newly connected
drive is already in the Drive List view, drive data automatically uploads
and stores as the actual data. If differences exist, the Drive List view and
its Drive Data view will update to reflect differences between the file data
and the actual data. If, however, the newly connected drive is not in the
Drive List view, you will be prompted to insert/add the drive. If you
choose Yes to the prompt, the drive data will be uploaded and stored in
both the file data and the actual data. The drive will be added to the Drive
List view and no differences will be indicated.
4. When saving the drive file, only the file data is saved to the .adv file. If dif-
ferences exist between file and actual data, you are prompted to copy the
actual data to the file data before the save is executed.
5. When copying a drive from the Drive List view, only the file data is copied.
If differences exist between file data and actual data, you are prompted to
copy the actual data to the file data before the copy is executed.

OFFLINE Operation
While in the OFFLINE Drive List/Drive Data view, actual data will not be uploaded.
Only file data is kept for each drive.
Other Operations in ONLINE Drive List View
Reset Drive Faults

Reset Faults command resets all faults in the connected drive. This command is available
in the ONLINE Drive List view or the Control Panel / Oscilloscope view when the con-
nected drive is selected. To reset faults, follow these steps:
1. Select the connected drive.
2. Choose one of the following methods to issue the Reset Faults command:

• Select Online | Drive Operations | Reset Faults from the menu.
• Press <Ctrl + Shift + F>.
• Right-click and select Reset Faults.
Reset Drive Peaks

Reset Peaks command sets maximum latched values to zero in the connected drive. This
applies to Current-Peak Plus and Current-Peak Minus. This command is only available in
the ONLINE Drive List view, ONLINE Drive Data view or the Control Panel / Oscillo-
scope view when the connected drive is selected. To reset peaks, follow these steps:

• Select Online | Drive Operations | Reset Peaks from the menu.
• Press <Ctrl + Shift + P>.
• Right-click and select Reset Peaks.
Cold Restart
Cold Restart completely resets the drive. This command is available in the ONLINE Drive
List view, ONLINE Drive Data view or the Control Panel / Oscilloscope view when the
connected drive is selected. To cold restart, follow these steps:
2. Choose one of the following methods to issue the Cold Restart command:

• Select Online | Drive Operations | Cold Restart from the menu.
• Right-click and select Cold Restart.
Remove Input Offset

Remove Input Offset removes the analog input offset. This command is available in the
ONLINE Drive List view, ONLINE Drive Data view or the Control Panel / Oscilloscope

view when the connected drive is selected, enabled and not under software control.
To remove input offset, follow these steps:
2. Choose one of the following methods to issue the Remove Input Offset
command:
• Select Online | Drive Operations | Remove Input Offset from
the menu.
• Right-click and select Remove Input Offset.
Set User Fault

Set User Fault creates a disabling fault in the drive. This command is available in
the ONLINE Drive List view, ONLINE Drive Data view or the Control Panel /
Oscilloscope view when the connected drive is selected. To set the user fault, fol-
low these steps:
2. Choose one of the following methods to issue the Set User Fault
command:

• Select Online | Drive Operations | Set User Fault from the
menu.
• Right-click and select Set User Fault.

Configuring / Editing / Monitoring a Drive
Drive Data view is the location to configure/monitor drive characteristics in the form of
parameters. The Drive Data view can be active in the ONLINE and OFFLINE modes. The
Drive Data view, however, must have a Drive List view open first. When a Drive List view is
ONLINE, its Drive Data view is ONLINE also. Closing a Drive List view will also close its
Drive Data view.
Access Drive Data view from Drive List view

From the Drive List view, select a drive in the drive list and use one of the follow-
ing methods:

• Double-click on the drive.
• Select Edit | Edit Drive(s) Data from the menu.
• Right-click and select Edit | Edit Drive(s) Data.

The Drive Data view will be displayed in front of the Drive List view.
Content of Drive Data view

Only one Drive Data view per Drive List view is permitted. Attempts to open
a secondary Drive Data view will result in the open Drive Data view updating
with whatever information is available for the selected drive(s).
The following information is supported:
ONLINE Drive Data View OFFLINE Drive Data View

File Values File Values
File Units File Units
Actual Values
Actual Units

Parameters
Parameters have been grouped into categories. Categories can be collapsed by
selecting the (-) button to the left of the category name. Categories can be
expanded by selecting the (+) button to the left of the category name. The fol-
lowing chart specifies the categories and the views in which they are available:
Category Basic View Expert View Expert View

(ONLINE (OFFLINE
Drive Data Drive Data
view) view)
Basic X
System X X
Command X X
Tuning X X
I/O X X
Limits and X X
Indicators
Fault and X
Warnings
Fault History X
Motor X X
Changing Drive Data views

There are three kinds of Drive Data views available.
1. Basic View contains the parameters most often configured and monitored.
Basic View contains only one category -- Basic.
2. Expert View (ONLINE Drive Data view) contains all parameters -- config-
uration and monitored. This view contains all categories except Basic.
3. Expert View (OFFLINE Drive Data view) contains configuration parame-
ters. Some parameters cannot be changed when the drive is enabled. This
view contains categories with configuration parameters, which is a subset
of the categories available in the ONLINE Drive Data Expert View.
To move between the above views, choose one of the following methods:
1. Click or button along the upper left side of the Drive Data view. The
view name on the button is the view that will be displayed when the button
is clicked.
2. Select View | Basic View or View | Expert View from the menu.

Navigating in the Drive Data view
The Drive Data view contains the same number of drives in the same order as its
Drive List view. You may need to change the view to see the information you are
looking for.
There are four columns of information for each drive in the drive list. The col-
umns are Actual values, Actual Units, File values and File Units. The bolded
words are the column headers in the Drive Data view. Note: Actual values and
actual units are only available in the ONLINE Drive Data view.
Here are some ways to change the look of the Drive Data view:
1. Pressing the up or down arrows moves the cursor to the next category. Unless
the category is expanded, then the cursor moves to the next parameter value
field.
2. Use any of the following methods to collapse categories:
• Select the (-) button to the left of the category name to collapse single cate-
gories.
• Select View | Categories | Collapse All from the menu to collapse all cate-
gories.
• Right-click anywhere in the Actual values or File values column and select
Categories | Collapse All to collapse all categories.
• Click the far-left dark gray cell of any parameter row, all categories will
collapse.
3. Use any of the following methods to expand categories:
• Select the (+) button to the left of the category name to expand single cate-
gories.
• Select View | Categories | Expand All from the menu to expand all cate-
gories.
• Right-click anywhere in the Actual values or File values column and select
Categories | Expand All to expand all categories.
• Double-click in the area below the categories and parameters, all categories
will expand.
4. To toggle between collapsing and expanding single categories, use any of the
following methods:
• Double-click on a dark gray category row of either the Actual or File data
columns.
• Set the cursor to a dark gray category row of either the Actual or File data
columns and press the Enter key.
5. Column width can be adjusted by using the mouse.
• Move the mouse pointer over the line separating two columns. The mouse
pointer will change to a vertical list with horizontal arrows in either side
.

• Hold the left mouse button down and move the mouse left or right to con-
tract, expand or hide the column.
6. Columns can selectively be hidden and shown for all drives in a drive list. To
hide or show the same column for all drives in a drive list:
• Select View | Columns | Show All Actual Values from the menu.
• Select View | Columns | Show All File Values from the menu.
• Select View | Columns | Hide All Actual from the menu.
• Select View | Columns | Hide All File Values from the menu.
• The Units columns can be additionally controlled by the following menu
items. Add a check (click on an item without a check) to show the columns
or remove a check (click on an item with a check) to hide the columns.
• Select View | Columns | Display Actual Units from the menu.
• Select View | Columns | Display File Units from the menu.
• Double-click in the area to the right of the categories and parameters to
show all columns.
Note: When hiding the Actual values or File values columns, their respec-
tive Units columns are also hidden.
7. Columns can selectively be hidden and shown for a single drive in a drive list.
To hide or show a column for a single drive, use one of the following methods:
• Right-click on either the Actual values or File values column. Add a check
to hide or remove a check to show one of the following from the Columns
menu:
• Display Actual Values for This Drive
• Display Actual Units for This Drive
• Display File Values for This Drive
• Display File Units for This Drive
• Double-click on the column header to hide individual columns.
• Move the cursor over the line separating columns until the mouse cursor
changes to or . Double-click on the line to show individual col-

umns.
8. Drives can be selectively hidden/shown.
To hide all drives:
• Select View | Hide All Drives and remove the check for the drive to hide.
To hide a drive, use one of the following:
• Select View | Visible Drives from the menu.
• Right-click on the drive header bar, Actual values column or File values
column and select Hide This Drive.
• Double-click on the drive header bar.
To show all drives:

• Select View | Show All Drives from the menu
To show a drive, use one of the following:
• Select View | Visible Drives and add the check for the drive to show.
• Double-click on the vertical line separating drives.
Find Parameter in Drive Data

This search function is activated from the Drive Data view and locates parameters
for any of the displayed drives.
Select Edit | Find... from the menu to bring up the Find dialog.
Search Column
The radio buttons select where the cursor will end up when the search is complete,
either in the File values column or in the Actual values column.
Search Drive Name
All drives in the drive list will be available for selection from the drop down list.
Data entry is not allowed. The drop down list is sorted alphabetically.
Search Parameter Name
All parameters will be available for selection from the drop down list. Data entry
is not allowed. The drop down list is sorted alphabetically.
Select the Find button to execute the search.
Select the Cancel button to exit the dialog without performing the search.
Select the Help button to display help on this command.

When a match is found
The matching category will be displayed in the text to the left of the Go To button.
You can either find the next match by selecting the Find button again or display
this match by selecting the Go To button, By displaying a match, any collapsed
category will be expanded and any hidden drives or hidden columns will be shown
so that the matching parameter can be displayed.
When a match is not found
When a match is not found, the dialog will display “Not Found.” The first match
will always be found; subsequent searches of the same information may not have a
match. The next search will start from the top of the parameters.
Copy/Paste Parameters
Copy
Single value, multiple values, and entire value columns can be copied. See the
section on How to Select these various groups.

Once values are selected, use one of the following methods to Copy:

• Choose Edit | Copy from the menu.
Paste
A Single value can be pasted anywhere there is a currently configurable value.

Select the value and use one of the following methods to Paste:

• Choose Edit | Paste from the menu.
Multiple values will be pasted onto matching parameters.
Note: When multiple values are to be pasted, all receiving values must be config-
urable. If any are not, an error message will display and the paste command will
not execute.
How to Select
Single value is selected by left-clicking the value.

Multiple values can be selected at the same time if they are part of the same drive
and in the same column.
• To select values next to each other in the column, select a value, hold down
the shift key while pressing the up/down arrow or hold down the shift key
and select another value. The entire block of values will be displayed as
selected.
• To select values not next to each other in the column, select a value, then
hold down the Ctrl key while left-clicking the other desired values in the
same column.
Entire file column can be selected by one of the following methods:
• Left-click on any of the values in the File column and select Edit | Select
All in Col in the menu.
• Right-click on any of the values in the File column and choose Select All
in Col.
• Left-click on the File column header.

Undo
Undo reverses the last edit action. Undo/Redo maintains 10 levels each. Undo
command can be activated by one of the following methods:
• Click button on the drive list standard toolbar.

• Choose Edit | Undo from the menu.
• Press <Ctrl + Z>.
When an Undo operation involves changes to values which are now read-only, the
Undo operation will fail and an error message will be displayed. When the read-
only status of the values change, Undo can be selected and the operation that previ-
ously failed will be performed.
A single Undo operation may contain several commands. For example, when Fac-
tory Defaults are restored for an entire column; all value changes will be stored as
a single Undo command.
Note: Undo command cannot be used to undo output override or toggle an over-
ridden output.
Redo
Redo reverses the last Undo command. Undo/Redo maintains 10 levels each.
Redo command can be activated by one of the following methods:
• Click button on the drive list standard toolbar.

• Choose Edit | Redo from the menu.
• Press <Ctrl + R>.
When a Redo operation involves changes to values which are now read-only, the
Redo operation will fail and an error message will be displayed. When the read-
only status of the values change, Redo can be selected and the operation that previ-
ously failed will be performed.
A single Redo operation may contain several commands. For example, when Fac-
a single Redo command.
Note: Redo command cannot be used to undo/redo output override or toggle an
overridden output.
Monitoring ONLINE Drive Data

Monitored parameters are parameters that cannot be changed. They are available
for observation and comparison.
Monitored parameters read from the drive will be displayed in the current anima-
tion color (default is red) when the drive is connected. When the drive is discon-
nected, the color of the read-only data will change to black to indicate the drive is
no longer connected.

Download File Data
Changes in the file values are not automatically downloaded to the drive. Single
file value, multiple file values or entire file value columns can be downloaded.
Additionally, the file data from another drive in the ONLINE drive list can be
downloaded to the connected drive. This is only available for all the file data from
another drive, not selected values. Note: If the selected drive is not the connected
drive, the connected drive will be renamed to the selected drive’s name.
See the section on How to Select these various groups.
Once values are selected, use one of the following methods to Download:
• Click the button on the drive list standard toolbar

• Select Online | Drive Operations | Download File Data from the menu.
• Right-click and select Download File Data.
When changes in the File column are downloaded, the Actual column will be
updated to reflect the downloaded values.
Some configuration parameters can only be downloaded while the drive is dis-
abled. If an attempt is made to download any of these parameters while the drive
is enabled, an error message will be displayed and the download will be aborted.
File data can only be downloaded if the File firmware version matches that of the
Actual firmware revision.
Print Drive Information

With either a drive list open and having focus or drive data view open and having
focus, the Drive Print Settings dialog can be displayed by choosing one of the fol-
lowing:
• Click button from the drive list standard toolbar.

• Select File | Print . . . from the menu.
The following settings can be adjusted to get a printed document:

1. Under the Printer: box, there are two items to configure:
• The drop-down list in the Name: field allows you to choose known print-
ers. The printers can reside locally or on a network.
• The Properties button opens up a dialog to further configure the chosen
printer. Select OK to accept the printer properties. Select Cancel or click
the to exit the properties dialog without changing the settings.
2. Under the Items to Print: box, there are two selections:
• Drive List. This box should be checked if you wish to print the Drive List
view.
• Drive Data. This box should be checked if you wish to print the Drive
Data view. When this box is checked, the Drives to Print: box and Print
Data Options box are available for configuration.
3. Under the Drives to Print: box, there are three options:
• The large white box lists the drives available in the focused drive list. Any
number of drives in the drive list can be selected for printing. The drives
are sorted alphabetically.
• Select All. Click this button to include all drives in the list for the printout.
• Select None. Click this button to remove all drives from the list for the
printout.

4. Under the Data Print Options: box, there are two ways to configure the out-
put:
• Number of Drives across one page (horizontal). This field defines the
number of drives to be printed across one page. The range is 1 to 4. The
field can be edited or you can use the up and down arrows at the end of the
field to select a number between 1 and 4.
• Fit all parameters on one page. If this box is checked, all visible parame-
ters will be printed on one page. If this box is not checked, each page will
have 50 visible parameters printed.
When the settings are satisfactory, select Print to queue the output to a printer.
Select Cancel or click the to exit the dialog without printing. Select Help to
display information related to this subject.
Restore Factory Defaults

Factory defaults can be restored for selected values or entire columns of Actual
data or File data. If Actual data is restored to factory defaults, the changes will
download to the drive immediately. If File data is restored to factory defaults, the
changes will need to be downloaded to the drive, if required.
To restore factory defaults, choose one of the following methods:

• Select Edit | Restore Factory Defaults from the menu.
• Right-click on selected values and choose Restore Factory Defaults.
Output Override
You may want to force a situation to observe the results. One way is to override
outputs. The control of the overridden output is exclusively with the PiCPro user.
The PiCPro user can toggle the overridden output and can also remove the over-
ride.
Outputs can be overridden only if the following criteria are met:
• The drive must be connected and in the ONLINE drive list.
• Drive Data view and/or Control Panel / Oscilloscope view must be active
for the ONLINE drive list.
Note: If communications with the connected drive are lost while the drive has
overridden outputs, the following actions will be taken in the drive:
• (34) SW Ctrl Comm Timeout fault will be set.
• The control of the overridden output will be taken from PiCPro and
returned to the states currently assigned to the output.

Override Output
To override an output, do one of the following:
• Put focus on an output and select Online | Drive Operations | Override
Output from the menu.
• Right-click on an output and select Override Output.
A check mark will appear in front of the menu item to indicate Override Output
is selected. The word OVERRIDDDEN will appear in the current animation
color next to the light bulb of the output to indicate Override Output is active.
The status of the output will not change. The output can only be changed by the
PiCPro user with a request for the output to be toggled.
Toggle Overridden Output
To toggle an overridden output, do one of the following:

• Put focus on an overridden output and select Online | Drive Opera-
tions | Toggle Output from the menu.
• Right-click on an overridden output and select Toggle Output.
Remove an Override
To remove an override, do one of the following:

• Put focus on an overridden output and select Online | Drive Opera-
tions | √ Override Output from the menu.
• Right-click on an overridden output and select √ Override.
The check mark will disappear from in front of the menu item to indicate
Override Output is no longer selected. A confirmation message will be dis-
played.

Control Panel / Oscilloscope View
Control Panel / Oscilloscope view can be used to setup and tune the drives. The
Control Panel / Oscilloscope view, however, must have a Drive List view open
first. Closing a Drive List view will also close its Control Panel / Oscilloscope
view.
The Control Panel / Oscilloscope view can be used to display a saved trace.
Note: It is recommended to maximize the PiCPro display before activating the

Control Panel / Oscilloscope view. There is a massive amount of infor-
mation in this view. It is more easily accessed and analyzed from a full
screen view.

Accessing Control Panel / Oscilloscope view
With an ONLINE drive list, one of the following methods will open the Control
Panel / Oscilloscope view:

• Select View | Control Panel / Oscilloscope… from the menu.
• Right-click and select Control Panel / Oscilloscope…
Content of Control Panel / Oscilloscope view

There are three main areas in this view.
• Oscilloscope
• Control Panel
• Parameters
The Oscilloscope area is located in the upper left corner. It is the only area that
cannot be hidden. The Oscilloscope area will expand and contract accordingly as
the Control Panel area and Parameters area are hidden and shown.
The Control Panel area is located in the lower left corner. It can be hidden and
shown. The Control Panel area will not expand or contract due to the Parameters
area being hidden or shown.
The Parameters area is located in the right side. It can be hidden and shown. The
Parameters area will not expand or contract due to the Control Panel area being
hidden or displayed. The Parameters area is using the same format and much of
the same information as the Drive Data view.
The Parameters area has the following modes available:
• Monitor/Oscilloscope Mode
• Tuning Mode
• Velocity Control Mode
• Current Control Mode
• Auto Tuning Control Mode
The Parameters area displays only actual data. File data cannot be modified from
the Control Panel / Oscilloscope view.
Several parameters use a scrollbar to determine a value. The scrollbar applies to
the parameter directly preceding it and functions in the following manner. The
value can be entered into the parameter actual value field or selected with a scroll-
bar control. Movement of the scrollbar button produces a coarse change in value.
The value can be fine-tuned by clicking on the arrows of the scrollbar to incre-
ment/decrement by 1 or clicking between the scroll box and the arrows to incre-

ment/decrement by 10. Note: This applies to any parameter that uses a scrollbar
for value adjustment.
Parameters have been grouped into categories. Categories can be collapsed by

selecting the (-) button to the left of the category name. Categories can be
expanded by selecting the (+) button to the left of the category name. The follow-
ing chart specifies the categories and the views in which they are available:
Category Monitor / Tuning Velocity Current AutoTuning

Oscilloscope Mode Control Control Control
Mode Mode Mode Mode
System x x x x x
Command x x x x x
Tuning Monitor x x x x x
I/O x x x x x
Limits & Indicators x x x x x
Faults & Warnings x x x x x
Fault History x x x x x
Motor x x x x x
Channel A x x x x x
Channel B x x x x x
Channel C x x x x x
Channel D x x x x x
Scope Setup x x x x x
Tuning Control x x x x
Manual Velocity Turning x
Settings
Manual Current Tuning x
Settings
Auto Tuning Settings x
Changing Control Panel / Oscilloscope modes

There are four modes available in the Parameters area.
1. Monitor / Oscilloscope Mode contains the parameters most often monitored.
In this view, the Oscilloscope is usable to monitor any parameter. There are no
provisions to change anything in the drive or to control the drive.

2. Tuning Mode contains the parameters and settings required to tune a drive.
The capability is provided to adjust the drive velocity tuning parameters. The
velocity P, I, and D gains and Inertia Ratio may be adjusted along with control-
ling the low pass filter. These parameters have no effect when running the
drive in current control mode.
3. Velocity Control Mode contains the parameters and settings required to run a
drive in velocity mode. A category is added that allows for software control of
the drive by specifying velocity. Four commands can be issued to the drive:
forward, reverse, sine wave and square wave. These are selected from a drop
down list. The velocity is specified in RPM. Forward causes the drive to run
with a constant positive command. Reverse causes the drive to run with a con-
stant negative command. For the sine and square wave modes a period is
selected from a dropdown list. Although the drive must be stopped to change
the command mode, the velocity and period can be adjusted while the drive is
running.
While parameters are used to control the drive, they cannot initiate or terminate
motion. Motion is started/stopped by the start/stop motion pushbuttons in the
Control Panel area.
When entering or leaving Velocity Control View, the drive must be disabled to
prevent unexpected motion. A dialog will appear accordingly.

4. Current Control Mode contains the parameters and settings required to run a
drive in current mode. A category is added that allows for software control of
the drive by specifying current. Current Control mode operates exactly the
same as the Velocity Control mode, except that the current controls are in
Amps. The tuning parameters have no effect while running in current control
mode.
5. Auto Tuning Control Mode allows the interface to setup and execute an auto
tune cycle. While executing the auto tune cycle, the drive is under software
control and being operated in current mode. The Current Limit parameter is a
percentage of the motor continuous current and the Distance Limit parameter
limits the number of revolutions of the motor for the forward and reverse
stroke of the auto tune cycle.
Motion is initiated by the Start/Stop Motion button in the Drive Control group
of the Control Panel. The drive will oscillate for a few seconds and then stop.
The auto tune cycle can be stopped at any time by clicking the Stop Motion
button.
When the drive has completed the auto tune cycle, the following dialog will be
displayed. Select Yes to disable the drive and change the parameters in the
drive. Select No, Cancel or to close the dialog without updating the param-
eters in the drive.

To move between the above views, choose one of the following methods:
Select Mode | Monitor, Mode | Tuning, Mode | Control Panel | Velocity Con-
trol, Mode | Control Panel | Current Control or Mode | Control Panel | Auto
Tuning from the menu.
Navigating in the Control Panel / Oscilloscope view

The Control Panel / Oscilloscope view contains the connected drive from the
ONLINE drive list.
Note: The Control Panel / Oscilloscope view only interfaces with a connected
drive.
Display Control Panel
This command shows the pushbuttons and indicators below the oscilloscope. Oth-
erwise the oscilloscope trace covers the full height of the screen.
Select View | Show Control Panel from the menu to display the command area.
A √ will appear in front of the menu item to indicate the feature is activated.
Select View | √ Show Control Panel from the menu to hide the command area.
The √ will disappear from in front of the menu item to indicate the feature is deac-
tivated.
Display Parameters
This command shows the parameters to the right of the oscilloscope. Otherwise
the oscilloscope trace covers the full width of the screen.
Select View | Show Parameters from the menu to display the parameter area. A √
will appear in front of the menu item to indicate the feature is activated.
Select View | √ Show Parameters from the menu to hide the parameter area. The
√ will disappear from in front of the menu item to indicate the feature is deacti-
vated.
Changing the Parameters area
There are two columns of information for the connected drive from the ONLINE
drive list. The columns are Actual values and Actual Units. The bolded words
are the column headers in the Parameters area of the Control Panel / Oscilloscope
view.
Here are some ways to change the look of the Parameters area of the Control Panel
/ Oscilloscope view:
1. Pressing the up or down arrows, moves the cursor to the next category.
Unless the category is expanded, then the cursor moves to the next parame-
ter value field.
2. Use any of the following methods to collapse categories:
• Select the (-) button to the left of the category name to collapse single
categories.

• Select View | Categories | Collapse All from the menu to collapse all
categories.
• Right-click anywhere in the Actual values column and select Catego-
ries | Collapse All to collapse all categories
• Click the far-left dark gray cell of any parameter row, all categories will
collapse.
3. Use any of the following methods to expand categories:
• Select the (+) button to the left of the category name to expand single
categories.
• Select View | Categories | Expand All from the menu to expand all
categories.
• Right-click anywhere in the Actual values column and select Catego-
ries | Expand All to expand all categories
• Double-click in the area below the categories and parameters, all cate-
gories will expand.
4. To toggle between collapsing and expanding single categories, use any of
the following methods:
• Double-click on a dark gray category row of either the Actual or File
data columns.
• Set the cursor to a dark gray category row of either the Actual or File
data columns and press the Enter key.
File Menu Features

The features made available by the File menu are performed on files used by the
Control Panel / Oscilloscope view. These operations do not address the drive files.
While some drive parameter values can be modified from the Control Panel /
Oscilloscope view, the changes cannot be saved from this view. You must move to
the Drive List view or the Drive Data view to save the drive parameter value
changes to the drive file.
Save Trace…
This feature saves the entire current trace data to a tab-delimited text file (*.txt).
1. Select File | Save Trace … from the menu.
2. Save As dialog appears for filename and location. The current drive name
will be the default filename with a .txt extension.
3. Enter the filename and locate it.
4. Select Save to save the file and close the dialog. Click or select Can-
cel to close the dialog without saving the file.
Even though the saved trace is a text file, it is not intended that the file be modi-
fied. MMC Smart Drive.xls has been developed to generate a plot similar to
what is seen in the Oscilloscope area of the Control Panel / Oscilloscope view.

MMC Smart Drive.xls is part of the Applications installation. It can be found in
the tools directory (C:\Program Files\Giddings & Lewis\Applications
V##.#.#\Tools). Where ##.#.# is the version of the Applications CD.
Restore Trace…
This feature reads in a trace from a previously saved tab-delimited text file (*.txt).
1. Select File | Restore Trace … from the menu.
2. Open dialog appears for filename and location.
4. Select Open to open the file and close the dialog. Click or select Can-
cel to close the dialog without opening the file. An additional selection is
available. You can check Open as read-only box for read-only access to
the trace file.
Note: A dialog will appear if discrepancies are detected in the format of the
restored trace file.
Save Scope Template…
This feature saves the oscilloscope settings and the velocity, current and auto tun-
ing control settings in a *.scp file for use on other drives. Typically, this feature
would be used to establish a favorite group of settings that can be called into any
drive. None of the drive parameters are saved in this file, only the control panel
and oscilloscope settings.
1. Select File | Save Scope Template… from the menu.
2. Save As dialog appears for filename and location.
4. Select Save to save the file and close the dialog. Click or select Can-
cel to close the dialog without saving the file.
Note: For a specific drive, all the above mentioned settings along with all the
drive data is saved in the *.adv file.
Recall Scope Template…
This feature reads a previously saved control panel and oscilloscope settings
(*.scp).
1. Select File | Recall Scope Template… from the menu.
2. Open dialog appears for filename and location.
4. Select Open to open the file and close the dialog. Click or select Can-
cel to close the dialog without opening the file. An additional selection is
available. You can check Open as read-only box for read-only access to
the trace file.
Note: Template files (*.scp) have a signature that is checked on recall. A dialog
will appear if there is a problem.
Restore Parameters
This feature restores the drive to the condition it was in before entering the Control
Panel/Oscilloscope view.
1. Select File | Restore Parameters from the menu.
2. A dialog will appear to confirm this action.
Print Trace…
This feature prints the current trace screen on the selected printer.
1. Select File | Print Trace… from the menu.
2. Print dialog appears to set print characteristics.
3. Select OK to print the trace and close the dialog. Click or select Can-
cel to close the dialog without printing the trace.
Note: Only what is visible on the screen is printed.
Close Oscilloscope
This feature closes the Control Panel/Oscilloscope view.

Select File | Close Oscilloscope from the menu.
Note: If attempting to exit under software control of the drive, a dialog appears to
confirm this action.
Oscilloscope Channel Configuration

The Oscilloscope can display up to four channels of information. Each channel
has a group of settings that describe how the information will appear on the screen.
With the exception of the Signal setting, all the settings can be changed whether
the Oscilloscope is running or stopped. The settings are found in the Parameters
area under categories Channel A, Channel B, Channel C or Channel D.
Oscilloscope Channel Signal
The channel signal setting is the drive variable you wish to monitor with the oscil-
loscope. The channel signal is selected from a tree control type list of signals in
any of the Parameters area views. Any signal can be used in any channel. To

return the field to undefined, move to the field and press the Delete key. Note:
Data entry is not allowed in this field.
Oscilloscope Channel Scale
The channel scale setting establishes the number of vertical units per division on
the oscilloscope display for this channel. The oscilloscope vertical display
defaults to + 11 divisions. This field's drop down list provides the available
choices.
Oscilloscope Channel Offset
The channel offset setting establishes the value that appears at the vertical center of
the oscilloscope trace. A value can be entered directly into this field. This field
also has scrollbar value control. See Content of Control Panel / Oscilloscope view
for scrollbar operation.
Oscilloscope Channel Color
The channel color setting allows you to select a different color for each of the
channels. The channels are defaulted to different colors. This field's drop down
list provides alternate choices.
Oscilloscope Channel Hide
The channel hide setting allows you to remove a channel from the display. Even
though the hidden channel will not be displayed, data is still being recorded so that
the channel can be displayed at any time and the data will be correct. This field's
drop down list provides a Yes/No choice. No is default.

Oscilloscope Setup
The settings described in this section define the characteristics for the trigger and
sampling of the trace.
Trigger Signal
Trigger signal setting is the drive variable the drive monitors to create a trigger
event. The trigger signal is selected from a tree control type list of signals in any
of the Parameters area views. Any signal can be used. To return the field to unde-
fined, move to the field and press the Delete key. Note: Data entry is not allowed
in this field.
Trigger Level
Trigger level is the value of the trigger signal at which the trigger should occur.
Acceptable range is -2,147,483,648 to 2,147,483,647 (+2^31).
Trigger Edge
Trigger edge setting is three-selection choice from a drop down list

1. Intermediate triggers once the buffer position criteria are met.
2. Rising triggers when the present value is greater than the last value and the
present value is great than or equal to the trigger level.
3. Falling triggers when the present value is less than the last value and the
present value is less than or equal to the trigger level.
Trigger Mode
Trigger mode setting is a two-selection choice from a drop down list.

1. Continuous captures data, displays it and then re-arms the trigger so that
another data capture occurs automatically. This process will continue until
it is manually stopped.
2. Single allows the trigger event to occur once and then ends the process.
The trigger must be armed again for another data capture to occur.

Buffer Trigger Position
To view an event, buffer trigger position setting allows you to adjust where in buff-
ered data the trigger occurs. If this value is 0, then all the data will be buffered
from after the trigger occurred. If this value is 50, then half the data will be buff-
ered from before and half will be buffered from after the trigger occurred. If this
value is 100, then all the data will be buffered from before the triggered occurred.
Buffer trigger position field is a percentage ranging from 0 to 100. A value can be
entered directly into the field. It also has a slider control selection. There are 600
words of trigger capture buffer. For one channel of a word variable, there are 600
entries. For two channels of a word variable, there are 300 entries for each chan-
nel. For one channel of a double word variable, there are 300 entries…
Sample Rate
Sample rate setting specifies the rate at which data is captured. The acceptable
range is 0.125 to 8191 milliseconds. Values can be entered directly into this field.
Note: Sample rate applies only to the trigger mode, which runs in foreground.
Samples per Division
Samples per division setting is a four-selection choice from a drop down list. This
setting specifies the number of samples to display per each major division along
the horizontal axis.
Secondary Scale
Secondary scale setting is a four-selection choice from a drop down list. This set-
ting specifies which channel's scale to display on the right side of the oscilloscope
when more than one channel is being displayed. By default, the first channel's
scale is displayed on the left and the second channel's scale is displayed on the
right, in the appropriate color.
Note: If an invalid channel is selected, a dialog will indicate the problem.
Line Weight
The thickness or width of the lines used in the Oscilloscope traces can be adjusted
by using the drop down list. There are three selections; thin, medium and thick.

Control Panel Features
Pushbuttons and indicators are located in the Control Panel area of the Control
Panel / Oscilloscope view. They are arranged in the following four columns:
1. Oscilloscope
2. Channel Definition
3. Drive Status
4. Drive Control
Oscilloscope Group
This group of pushbuttons controls the trace.
Arm Trigger
Click this button to initiate data capture with the oscilloscope setup information.
The drive will begin capturing data, waiting for the trigger event to occur. Data is
captured in foreground at the sample rate specified.
Run Continuous
Click this button to run the oscilloscope continuously, where there is no trigger and
the capture rate is determined by how fast the workstation is capable of processing
the data. Data is captured in background whenever requested by the workstation.
Stop
Click this button to stop the oscilloscope, whether running in trigger mode or con-
tinuous.
Trigger State Indicator
The trigger state indicator reflects the current state of the drive trigger mechanism.
• Solid Idle - When not using the oscilloscope
• Solid Running - When running the oscilloscope in continuous mode
• Blinking Waiting for Trigger - When the capture mechanism is armed and
looking for a trigger
• Blinking Triggered - When a trigger has been encountered, but the capture
buffer is not yet full
• Solid Triggered - When the capture is complete and being displayed

Channel Definition
The information in this column is a summary of the channels being displayed. The
information included is the color of the trace, the signal description and the scal-
ing. When running in continuous mode, the latest actual value is displayed. When
a channel is hidden, the text for that channel is grayed out.
Drive Status
This group of indicators reflects the current status of the connected drive.
Enabled / Disabled
This status indicates whether the drive is enabled or disabled. Enabled with a
green background indicates the drive is enabled. Disabled with a yellow back-
ground indicates the drive is either physically not enabled or the drive has not been
enabled by software control.
Warning / Fault
This status indicates the fault condition of the drive. No Fault with a green back-
ground indicates the drive has no active faults or warnings. Warning Fault with a
yellow background indicates that at least one warning is active. Disabling Fault
with a red background indicates that at least one fault is active.
Drive Control
This group of pushbuttons is used to run the drive while in software control. Soft-
ware control of the drive is allowed while on the Velocity Control mode, Current
Control mode or Auto Tuning Control mode in the Parameters area of the Control
Panel / Oscilloscope view. Pushbuttons unavailable for use will be grayed out.
Enable / Disable
The text on the pushbutton (Enable or Disable) is the action that will be taken
when the pushbutton is clicked and proper conditions exist in the drive for the
action to take place. If the software control of the drive cannot be enabled due to
the drive not physically being enabled or a disabling fault being active, messages
will be generated identifying the problem.
Set User Fault
Click this button to set user fault. The user fault is a disabling fault, which will
immediately disable the drive. This button is operational while on the Control
Panel / Oscilloscope view.
Clear Faults
Click this button to clear existing faults. If conditions have not been changed to
eliminate the fault, the fault indication will come back. This button is operational
while on the Control Panel / Oscilloscope view.

Start / Stop Motion
The text on the pushbutton (Start Motion or Stop Motion) is the action that will
be taken when the pushbutton is clicked and proper conditions exist in the drive for
the action to take place. If the software control of the drive cannot be enabled due
to the drive not physically being enabled or a disabling fault being active, mes-
sages will be generated identifying the problem. The type of motion will be deter-
mined by the Parameters area mode selected; Velocity Control mode, Current
Control mode or Auto Tuning Control mode.
Alignment Mode
Overview
Alignment mode is used to establish an operational relationship between a feedback
device and a motor magnetic position. After the motor and feedback devices are
aligned, the feedback device provides the precise location of the motor magnetic posi-
tion.
For the purposes of alignment, PiCPro recognizes the following types of feedback
devices:
• Incremental Encoders
• Resolvers
PiCPro cannot perform alignment if it is connected to a drive with a motor having a
Stegmann encoder. PiCPro will only support Stegmann encoders that have been pre-
programmed by G&L Motion Control.
The Alignment Tool is only available with MMC Smart Drive firmware versions 2.2
or greater. If alignment is attempted with an earlier version of drive firmware the fol-
lowing message will appear:

Accessing Alignment Mode
1. From the ONLINE drive list view, use one of the following methods to open
the Control Panel / Oscilloscope view:

• Select View | Control Panel / Oscilloscope… from the menu.
• Right-click and select Control Panel / Oscilloscope…
2. Select Mode | Control Panel | Alignment Control. The following message
will be displayed:
3. Click Yes to continue. Click No or Cancel to exit the dialog.

4. If Yes is selected, the drive will be disabled and set to alignment mode. The
Control Panel / Oscilloscope grid view will appear as follows:
5. The Control Panel / Oscilloscope status will appear as follows:

Parameters in Alignment Mode
Notes:
• The Parameters area displays only actual data. File data cannot be modified
from the Control Panel / Oscilloscope view.
• While parameters are used to control the drive, they cannot initiate or terminate
motion. Motion is started/stopped by the start/stop motion pushbuttons in the
Control Panel area.
• The Parameters area displays only actual data. File data cannot be modified
from the Control Panel / Oscilloscope view.
Changing the Parameters area
Changes are made to the Parameters area the same as in Drive Control Panel
Mode.
File Menu Features
File menu features are the same as in Drive Control Panel Mode.
Oscilloscope Channel Configuration and Setup
Oscilloscope channel configuration and setup is performed the same as in

Drive Control Panel Mode.
Control Panel Features
Pushbuttons and indicators are located in the Control Panel area of the Control
Panel / Oscilloscope view and are the same as in the Drive Control Panel
Mode.
Alignment Mode for a Motor with Incremental Encoder
Overview
Current Limit (percentage of continuous current that will align the motor) can
be entered. The default value is 25%.
The current will be applied when Start Motion is clicked at the Drive Control
Panel and remain until the automatic alignment cycle is complete or Stop
Motion is clicked.
While the current is applied, the Current Limit can be changed. The motor will
be commanded to magnetic zero, and then incrementally commanded to the
next magnetic zero over several sequential moves. When the cycle is complete
or Stop Motion is selected, the process will discontinue.

Alignment Successful for Motor with an Incremental Encoder
Alignment complete is continuously monitored. When alignment is successful

and complete, and the recommended offset is small (+/- 15 degrees), PiCPro
will indicate that no change is required. A prompt will be displayed. The fol-
lowing is an example prompt:
Click OK to continue.
If the offset is larger (>15 degrees) a prompt will appear asking if the Hall Off-
set in the .csv file and the motor’s Hall Offset should be updated. The follow-
ing is an example prompt:
• Click Yes to update the custom motor file and drive.

• Click No or Cancel to discontinue alignment.
Notes:
• When a successful alignment has been indicated, the value can be man-
ually entered into the motor table.
• The G&L Controls standard motor personality file cannot be modified.
• Upon completion of motor alignment a message is displayed recom-
mending a Hall Offset. However, the Hall Offset for a standard motor
cannot be changed. The following prompt will be displayed alignment
is performed on a standard motor:

A new custom motor must be created to use the recommended Hall
Offset (refer to Chapter 5: Custom Motors).
Alignment Unsuccessful for Motor with an Incremental Encoder
If alignment is complete, and the alignment is unsuccessful, an alignment error

message will be displayed. The following are examples of the type of messages
that may be displayed:
Pole to Pole Count is invalid:
Click OK to continue. Make sure the counts per rev and number of
poles are correct in the motor data file.
No hall transition detected:
Click OK to continue. Make sure the hall sensors are connected cor-
rectly to the drive.
Too many hall transitions detected:
Click OK to continue. Try again. If the problem persists, there may be

a problem with the hall sensors in the motor.
Hall to hall count invalid:
Hall sequence invalid:
Click OK to continue. Make sure the hall sensors are connected cor-
rectly to the drive.

Alignment Mode for a Motor with a Resolver
Overview
A resolver uses an Index Offset instead of a Hall Offset and therefore does not
have Hall sensors. Functionality includes Current Limit adjustment, drive
enable, and starting motion.
Alignment Successful for Motor with a Resolver
When alignment is complete, and alignment is successful, PiCPro will do one

of the following:
• If the recommended offset is small (+/- 15 degrees) PiCPro will indi-
cate no change is required. A message will be displayed as shown in the
following example:
• If the offset is larger (>15 degrees) a prompt will appear asking if the Index
Offset in the .csv file and the motor’s Index Offset should be updated. The fol-
lowing display is an example prompt:
• Click Yes to update the custom motor file and drive.

• Click No or Cancel to discontinue alignment.

Notes:
• When a successful alignment has been indicated, the value can be manually
entered into the motor table.
• The G&L Controls standard motor personality file cannot be modified.
• Upon completion of motor alignment, a message is displayed recommend-
ing an Index Offset. However, the Index Offset for a standard motor cannot
be changed. The following prompt will be displayed alignment is per-
formed on a standard motor:
A new custom motor must be created to use the recommended Index Offset
(refer to Chapter 5: Custom Motors).
Alignment Unsuccessful for Motor with a Resolver
If alignment is complete, and the alignment is unsuccessful, a pole-to-pole

alignment error message will be displayed. The following is an example of
this type of message:
Pole to Pole Count is invalid:

Cases When PiCPro Cannot Perform Alignment
Stegmann Encoder
PiCPro cannot perform alignment if it is connected to a drive with a motor hav-

ing a Stegmann encoder. PiCPro will only support Stegmann encoders that
have been pre-programmed by G&L Motion Control. If the attempt is made to
do so the following error message will be displayed:
Motor with alignment mode of Move, Move Minimum, or Hall then Index
PiCPro cannot perform alignment when connected to a drive with a motor hav-
ing an alignment mode of ‘Move’, ‘Move Minimum’, or ‘Hall then Index’. If
the attempt is made to do so, an error message will be displayed as follows:

CHAPTER 5 Custom Motors
Overview: Custom Motors
When PiCPro is installed, a list of standard motors is also installed. This is the list of
motors that is available when specifying motor model for a drive. If the motor model
being used is not found in the list, a custom motor must be created.
If non-standard motors are being used, there are two choices available for creating cus-
tom motor files:
• Custom motor files can be created in PiCPro using the procedures included in
this manual.
• G&L Motion will create the custom motor files.
The motor(s) are first sent to G&L Motion Control for testing by G&L Engi-
neers who specialize in the creation of custom motor files. The engineers cre-
ate a custom motor file and a speed torque curve for each motor. Contact the
G&L Motion Sales Department for further information.
A custom motor file (.csv) contains motor data for a single motor. The Custom Motor
View allows configuration of Custom Motor parameters.
Custom motor files are read:
• at the startup of PicPro
• if the location of the custom motor files is changed
Accessing Custom Motor Setup
Create a New Custom Motor File

1. Choose one of the following methods to display the New dialog and create a
new custom motor file:
• Click on the standard toolbar

• Press <Ctrl + N>
2. Select Custom Motor from the dialog that appears.
3. Click OK to create a Custom Motor File. Select Cancel or click to close

the dialog without creating a Custom Motor file. Select Help to display infor-
mation related to creating new Custom Motor files.
Custom Motors 269

To Open an Existing Custom Motor File
1. To display the Open dialog, choose one of the following methods:
• Click on the standard toolbar and browse to the folder containing

the existing Custom Motor files.
• Press <Ctrl + O>
2. The Open dialog box appears. At the bottom, choose Custom Motor Files
(*.csv) from the drop down list in the Files of type: box. A list of all existing
custom motor files is displayed.
3. Select the desired file to be opened.
270 Custom Motors

4. Use one of the following methods to open the file:
• Click Open.
• Double-click the file name.
Note: Select Cancel or click to close the dialog without creating a Custom
Motor file.
Configuring and Editing a Custom Motor File
The Custom Motor grid view is the location in which custom motor parameters are
configured. The grid view provides the ability to:
• Edit, copy and paste motor data within the grid.
• Restore default data and load default values from another motor.
Additional
Pull Down
Menus
Custom Motors 271

Navigating in the Custom Motor Data View
There are two columns of information for each parameter, Values and Units. The col-
umn width can be adjusted by using the mouse.
• Move the mouse pointer over the line separating two columns. The pointer will
change to a vertical list with horizontal arrows on either side .
• Hold the left mouse button down and move the mouse left or right to contract,
expand or hide the column.
• Move the cursor over the line separating columns until the mouse cursor
changes to or . Double-click on the line to show individual columns.
How to Select Parameter Values

A single value is selected by clicking on the value.
The entire file column can be selected by one of the following methods:
• Left-click on any of the values in the File column and select Edit | Select All
in Col in the menu.
• Right-click on any of the values in the File column and choose Select All in
Col.
• Left-click on the Value column header.
• Left-click in the first or the last Value cell. Hold down the mouse button and
drag up or down to select the entire column.
• To select multiple value cells, left-click in the first or the last value cell of the
desired selection of value cells. Hold down the mouse button and drag up or
down to select the cells.
Editing Custom Motor Values

To change parameter values while in Custom Motor Data view do the following:
1. Select the value.
2. Enter the changes.
3. Press the Enter key. If the value entered is out of the acceptable range, a
prompt will appear. The requested entry range depends on the value type.
4. If the above prompt is displayed, enter the proper value and press Enter.
272 Custom Motors

Copying/Pasting Parameter Values
Copy
A single value, multiple values, or the entire values column can be copied. Once
values are selected, use one of the following methods to Copy:

• Choose Edit | Copy from the menu.
Paste
A Single value can be pasted anywhere there is a configurable value. Select the
value and use one of the following methods to Paste:

• Choose Edit | Paste from the menu.
Multiple values will be pasted onto matching parameters.
Undo
Undo reverses the last edit action. Undo maintains 10 levels. An undo command
can be activated by one of the following methods:
• Click on the drive list standard toolbar.

• Choose Edit | Undo from the menu.
• Press <Ctrl + Z>.
A single Undo operation may contain several commands. For example, when Fac-
a single Undo command.
Custom Motors 273

Redo
Redo reverses the last Undo command. Redo maintains 10 levels. A redo com-
mand can be activated by one of the following methods:
• Click on the drive list standard toolbar.

• Choose Edit | Redo from the menu.
• Press <Ctrl + R>.
A single Redo operation may contain several commands. For example, when Fac-
a single Redo command.
Loading Default Data from Another Motor

Load Default Data From Another Motor provides the ability to choose a known
motor from a list. The selected motor’s default values will replace all entries for
the custom motor currently displayed.
1. Use one of the following methods to load the data from another motor:
• Click the button on the custom motor standard tools toolbar.

• Select Edit | Load Default Data From Another Motor... from the
menu.
• Right-click on selected values and choose Load Default Data From
Another Motor... .
The following prompt will be displayed:
2. Select the motor from which the default values will be copied.
3. Click OK or press Enter.
274 Custom Motors

Restoring Factory Defaults
Factory defaults can be restored for selected values. To restore factory defaults,
choose one of the following methods:

• Select Edit | Restore Factory Defaults from the menu.
• Right-click on selected values and choose Restore Factory Defaults.
Saving to a New Custom Motor File
A custom motor is added to the list of available motors in PiCPro when it's custom
motor file is saved. If a custom motor existing in PiCPro is modified using PiCPro, the
custom motor data will be updated when the file is saved.
Choose File | Save as... The following prompt will be displayed:
Enter a file name and the desired location. Click Save to save the new file. Click Can-
cel or cancels the new file save process.
The default file save location will be the custom motor directory. If the file is saved to
the custom motor directory, the new motor name will be added to all motor dropdown
lists. If the file is saved to a different location, a message will be displayed indicating
that the custom motor data will not be used because the file was not saved to the cus-
tom motor directory.
Custom Motors 275

Note: If files are added to the custom motor directory outside of PiCPro while
PiCPro is running, one of the following procedures must be performed before
the motors found in those files will appear in any of the motor drop down lists:
• PiCPro must be stopped and restarted.
• The Refresh button on the Drive Setup tab in the Options dialog must
be pressed.
Printing Custom Motor Information
To print custom motor information choose one of the following:
• Click from the drive list standard toolbar.

• Select File | Print . . . from the menu.
When the settings are satisfactory, select Print to queue the output to a printer.
Select Cancel or click the to exit the dialog without printing. Select Help to
display information related to this subject.
276 Custom Motors

Deleting a Custom Motor File
PiCPro does not provide functionality to delete a custom motor. To delete a custom
motor do the following:
1. Right click Start and click Explore to display the Windows Explorer view.
2. Navigate to the folder that contains the custom motor files.
Note: The default location for custom motors is a subdirectory

(subfolder) of the installed personalities directory (folder)
titled CustomMotors.
3. Select the custom motor (.csv) file and delete it from the Custom Motor
folder.
4. Do one of the following:
• From within PiCPro, select View | Options. Select the Drive Setup tab
and click the Refresh button.
• Close and restart PiCPro.
Custom Motors 277

Changing the Location of Custom Motor Files
When PiCPro is installed a CustomMotors directory is created as a subdirectory of the

Personalities directory (installed location\Personalities\CustomMotors). All custom
motor files found in the CustomMotor directory are read when PiCPro starts.
To change the location of the custom motor files do the following:
1. Select View | Options and click the Drive Setup tab. The following will be
displayed:
Location Contains the directory path of custom motor files.
... Displays a dialog for browsing to the custom motor directory.
Refresh Forces PiCPro to reread all custom motor files in the custom
motor directory.
2. Click ... to browse to the desired folder.

3. Click OK or Apply to save the change. The custom motor files (.csv) are
read and Motor Data Status is reevaluated for open drive files.
Note: The custom motor files can also be read and motor data status reevalu-
ated by selecting View | Options and clicking Refresh.
To Cancel the Location Change of Custom Motor Files
Click Cancel, click , or press Esc on the keyboard.
278 Custom Motors

Information Window Messages
When custom motor files are read, messages will be displayed in the information win-
dow if one of the following conditions exists:
• A custom motor file is found whose name matches that of a motor already in
the installed motor file.
• A custom motor file with an invalid checksum is found.
• A custom motor file is found that includes parameters not supported by the
current personality files.
Note: If the motor file is saved in the current version of PiCPro, any unused
information will be lost.
• A custom motor file is found that was created with an earlier version of PiCPro
that did not support all of the motor parameters supported in the current ver-
sion PiCPro. If motor parameters are missing, default values will be given to
the missing motor parameters.
Custom Motors 279

280 Custom Motors
CHAPTER 6 Servo Setup and Tuning
Servo Setup Overview
The Servo Setup program in PiCPro is used to enter setup data for all digitizing
and servo axes used in your application. Each axis you insert appears in a list
sorted by the axis type. It also allows you to read servo setup parameters in the
servo view list and write selected parameters to an axis in the servo force list.
A general overview of the procedure to incorporate servo setup into your applica-
tion program follows:
1. Use servo setup to enter setup data for your application.
2. Save the setup file (name.SRV).
3. With the compile command, make a function containing all the setup data.
Assign an appropriate name to the function. This function is placed in a library
file you create (name.LIB) which PiCPro can find. This library file will hold
all servo functions defined by you for your application.
4. Use PiCPro to create an application program (name.LDO).
5. Include the setup function you made, along with the STRTSERV standard
motion function, in a network of your ladder program.
Note: When setup data is called in a ladder, it is copied into the RAM
memory of the CPU.
6. Download the application to the control. The setup data for your application is
sent to the CPU in the form of the function.
7. Read and write setup parameters to fine-tune each axis in your application.
Note: This creates a .SVT file for the Servo View List and the Servo Force
List.
Accessing Servo Setup
There are several ways to access the Servo Setup program.

Create a New Servo Setup File
1. To display the New dialog, choose one of the following:
• Click on the button on the standard toolbar.

• Select File | New from the menu.
2. Select ServoSetup from the dialog box that appears.
3. Select the CPU type (PiC, MMC or MMC for PC).
Note: The default selection is the last selection made.
4. Choose OK.
Servo Setup and Tuning 281

Note: In the PiCPro MMC-Limited Edition, the CPU type is always MMC and is
therefore not an option on this dialog box.
To Open an Existing Servo Setup File
1. To display the Open dialog, choose one of the following:

• Select File | Open from the menu.
2. The Open dialog box appears. At the bottom, choose ServoSetup Files (*.srv)
from the drop down list in the Files of type: box. This brings up a list of all
existing servo setup files.
3. Highlight the file you want to open
4. To open the file, choose one of the following:

• Click Open.
• Double-click on the file.
The Servo Setup list view will appear:
282 Servo Setup and Tuning

Note: If Time axes are included, they will be displayed after digitizing axes in
the Servo Setup list view (e.g Axis Label 26 above). Input and Output
data are not included for Time axes (refer to To Insert a Time Axis).
Note: If an axis is specified as a DLS Communication Master axis, a (M) will
appear before the axis name in the first column of the servo setup list.
If you attempt to open an existing SRV file in the PiCPro MMC-Limited Edition,
and the SRV file was previously saved for a PiC or MMC for PC CPU, the follow-
ing confirmation prompt will be displayed that indicates the types of changes that
will be made to the servo setup information for this file.
To Open file from the setup function in your ladder

If you have already created a servo setup function with your setup data and have
included it in your ladder, you can access the servo setup file from there.
1. Place focus on the setup function in your ladder.
2. Choose one of the following methods to view a servo function:

• Select View | Servo Function from the menu.
• Right-click and select View Servo Function.
3. Then select the desired setup function from the fly-out list.
Note: In order to open a servo setup file from within your ladder, the servo file and
the servo function must have the same name. Any servo setup file created with
PiCPro for Windows automatically has the same name as the servo setup function.
However, any DOS servo setup file may not have the same name as the servo setup
function. Change the name of the .srv file to match the name of the servo setup
function if you want to be able to open the file from within the ladder and/or be
able to force axis values using the Servo Force List.
To Open file from Windows explorer
1. Open Windows Explorer and find the .srv file you want to open.
2. Select the .srv file that you want to open and double-click on it. The Servo
Setup window is displayed.
Inserting an Axis in Servo Setup
An axis is added to Servo Setup by using the Insert command from the menu,
pressing the Insert key, or right clicking and selecting one of the insert menu
items. You can insert a servo, digitizing (read-only) or time axis. Digitizing axes
have no output type. Time axes have no input or output type.
Servo setup will number the axes sequentially as they are inserted.
Each time you insert an axis you must enter the axis properties for that axis.
Servo Axis Limitations
In PiCPro for Windows Professional Edition, regardless of the CPU type selected,
the limitations are:
• The maximum number of servo axes is 32. The first 16 servo axes are num-
bered from 1 to 16 and the second 16 are numbered from 101 to 116.
• The maximum number of digitizing axes is 32. The digitizing axes are
numbered from 49 to 80.
• The maximum number of time axes is 4. The time axes are numbered from
25-28.
In PiCPro for Windows MMC-Limited Edition, the standalone MMC CPU is lim-
ited to:
• The maximum number of servo axes is 4 if axes are D/A Encoder. The
servo axes are numbered from 1 to 4.
• The maximum number of servo axes is 8 if axes are SERCOS. The axes are
numbered from 1-8.
• The maximum number of digitizing axes is 1 if axis is Encoder. The digi-
tizing axis is numbered 49.

• The maximum number of digitizing axes is 8 if axes are SERCOS axes.
The axes are numbered 49-56.
• The maximum number of time axes is 4. The time axes are numbered from
25-28.
• The input and output channel numbers of a servo D/A Encoder axis must
be the same as the axis number.
• The input channel number of a digitizing Encoder axis must be 5.
Note: All axes must be the same type in a standalone MMC or MMC for PC Servo
Setup function regardless of which PiCPro Edition it is created in.
To insert a Servo Axis

1. Select Insert | Servo Axis from the menu. If the CPU type selected is a PiC or
MMC, the Insert Axis Properties dialog appears as follows:
2. Enter a name for the axis in the Axis Label: field.

3. The Axis Number: is entered by PiCPro in sequential order. These can, how-
ever, be changed.
4. Enter the Output Type: and Input Type: in those fields if they are different
from the defaults you see above. Typically, a servo axis has a D/A output and
an Encoder input.
Note: If you need to change the defaults, change the Output Type first since
the Input Type choices vary based on your output selection.

If Output Type: selected is SERCOS, the Insert Axis Properties dialog appears
as follows:
When the CPU type is MMC for PC, the SERCOS axis can be designated as the
DLS Communications Master Axis by clicking on Communications Master. As
the Insert Axis Properties dialog shows:
Select Actual or Commanded to specify the Position to be broadcast. The

default is Actual. Actual must be selected if the Communications Master axis
is a Time or a digitizing SERCOS axis. Commanded is only available for a
normal SERCOS axis.
Regardless of the CPU type, if the Output Type: selected is Virtual, the addi-
tional tabs disappear. Input and output device configuration is not required. In

the case of MMC for PC CPU type, DLS designation is also available with the
Virtual axis as the Insert Axis Properties dialog shows:
5. Click on the tabs that appear to configure the output and input devices for your
application. Typically, you will need to specify at least the input and output slot
and channel for each device.
6. When you are done configuring your input and output properties, click on
Apply to activate the Axis Data button for this axis OR click on OK to con-
tinue inserting axes.
Note: An MMC for PC SRV file can only contain 1 axis specified as a digitiz-
ing DLS axis or a Communications Master.
Input / Output Types

The various combinations of Input and Output types are listed below.
CPU For a For a

Type Servo Axis Digitizing Axis
Inputs Output Inputs Output
PiC Encoder D/A (+/- 11V) Encoder No
Resolver D/A Resolver Output
Analog D/A Analog
TTL D/A TTL
SERCOS SERCOS
No Input Stepper
Virtual Virtual
Standalone MMC Encoder D/A (+/- 10V) Encoder No
SERCOS SERCOS SERCOS Output
Virtual Virtual
MMC for PC Encoder D/A (+/- 10V) Encoder No
SERCOS SERCOS SERCOS Output
Virtual Virtual DLS

D/A Output Setup
To configure the D/A Output
1. Enter the Slot: and Channel: location of the D/A module.
• For a PiC CPU: Slot is between 3 – 13, Channel is 1– 8
• For a standalone MMC: Slot is limited to 1, 3, 4, 5 or 6, Channel is 1 – 4.
Note: In the PiCPro MMC-Limited Edition, Slot is limited to 1 and
channel is limited to axis number. If the axis number is later
changed, you must modify the channel number.
• For an MMC for PC: Slot is 1 – 8, where it represents the ASIU number,
Channel is 1– 4.
2. Click OK.
Encoder Input Setup

To configure the Encoder Input
1. Enter the Slot: and Channel: location of the encoder module.
2. Select the correct Encoder Driver:
3. Select the correct Encoder Type:
Note: Quadrature type assumes that there are four counts for each quadrature
cycle. The rising and falling edges of both channel A and channel B are counted.
Pulse type counts either channel A or channel B so that one count is recorded per
cycle.
4. Click OK.

The options available on the Encoder tab will vary depending on CPU type.
CPU Type Slot Channel Driver Type

PiC 3-13 1-4 Differential Quadrature
Single-ended Pulse
Standalone 1 1-4 Servo Differential Quadrature
MMC 1-5 Digitizing
Standalone 1 or 3-6 1-4 Servo Differential Quadrature
MMC PLUS 1-5 Digitizing
MMC for PC 1-8 (ASIU) 1-4 Servo Differential Quadrature
1-5 Digitizing
Note: In PiCPro MMC-Limited Edition, slot is limited to 1 and channel is limited
to axis number for servo axes. When a new axis is inserted, channel will be set to
axis number. If axis number is later changed, you must modify the channel number
too. Channel is limited to 5 for a digitizing axis.

Resolver Input Setup (Only for PiC CPU)
To configure the resolver input
1. Enter the Slot: and Channel: location of the resolver module.
2. Click OK.
Note: An inductosyn device may also be used. Choose resolver if you will be using
an inductosyn.
Analog Input Setup (Only for PiC CPU)
To configure the analog input
1. Enter the Slot: and Channel: location of the analog input module.
2. Select the Filter Time: from the drop down list.
3. If you are using the module in the 4/20 mA Offset: mode, select Yes from the
drop down list.
Note: The Bipolar: box will be changed to No and the unipolar input Range
(Volts): will be changed to 0 to 5. These defaults cannot be changed when in
the 4/20 mA mode.
4. If you are not using the module in the 4/20 mA Offset: mode, select the Bipo-
lar or Unipolar voltage range from the drop down list.
5. Click OK.

TTL Input Setup (Only for PiC CPU)
To configure the TTL input
Selections for the TTL configuration are based on the type of feedback device.
1. Enter the Slot: and Channel: location of the TTL input module.
2. Select the Data Valid: from the drop down list. (See the note below).
3. Enter the Number of Data Bits: your device requires.
• A minimum of eight bits is required.
• A maximum of 16 and a minimum of eight bits can be used if Same or
Gray code is selected. The 24th input is not used.
• A maximum of 23 bits can be used if High or Low is selected with the 24th
bit used as an indicator of valid data.
4. The Input Sign: field defaults to unsigned. Most TTL devices return an
unsigned pattern with one end of travel all 1’s and the other end all 0’s. If the
device returns a signed pattern with all 0’s in the center of travel, change the
default to signed.
5. Click OK.
Note: TTL data is defined as valid depending on what is selected from the list.
Binary High Whenever input 24 is high, the inputs are not
allowed to change.
Low Whenever input 24 is low, the inputs are not

allowed to change.
Same Whenever two consecutive reads of the inputs are the

same, the 24th input is not used.
Gray This is an alternative to binary encoding. Only one bit of a gray

Code code number changes at a time. The 24th input is not used.

SERCOS Setup
When a SERCOS slave is connected to a servo axis, SERCOS is chosen as the
feedback module.
To configure a SERCOS axis
1. Enter the Slot: and Ring: numbers for the SERCOS axis. The slot number
identifies the slot in which the SERCOS module is installed in the control. The
ring number identifies whether this slave axis is on the first or second ring on a
SERCOS module.
2. Enter the Slave Number: for the SERCOS axis. The number entered here must
match the address of the slave.
Note: The slot number, ring number, and slave number correspond to the SRS
input on the SERCOS functions which identify this slave axis.
3. Indicate whether or not the drive is a Centurion Drive.
Different SERCOS drives use a different number of update cycles to accept a
command position and return an actual position. This number of update cycles
affects the accuracy of the approximate position error in the control.
The Position Error Cyclic Update Offset: allows the position error approxi-
mation to be optimized for the SERCOS drive being used. A default value of
zero provides the optimum approximation for a Centurion drive. When the
drive type is Centurion (Yes is checked), Position Error Cyclic Update Off-
set: is set to 0 and cannot be changed.
If a different drive is used (Centurion Drive is set to No), this number may be
changed (within the range [-5,2]) to achieve a more accurate position error
approximation in the control. Reducing the number will increase the approxi-
mate position error value. Increasing the number will reduce the approximate
position error value. The control’s approximate position error is only used for
display (READ_SV and Servo View List), In Position calculations, and Excess
Following Error calculations. Changing this value does not affect the actual
position error in the drive used to maintain closed loop control of the axis.
When the drive type is Centurion (Yes is checked), Position Error Cyclic
Update Offset: is set to 0 and cannot be changed:

When the drive is not Centurion (No is checked), Position Error Cyclic
Update Offset: defaults to 0 but can be changed to any value between -5 and
2:
Note: For a SERCOS Digitizing Axis, Position Error Cyclic Update Offset:
fields are always hidden because they do not apply to digitizing axes.
SERCOS SETUP
Number of Slaves per Slot Ring Slave

CPU Type Rings Ring Number Number Number
PiC 16 8 3-13 1-2 1-8
standalone 1 8 1 1 1-8
MMC

SERCOS SETUP

MMC for PC 1 32 1 1 1-32
Stepper Setup (Only for PiC CPU)

To configure the stepper module
1. Enter the Slot: and Channel: location of the stepper module.
2. Enter the Type: of stepper you are using, CW/CCW or Step/Direction. The
default is CW/CCW.

Default axes using Auto Fill (Standalone MMC)
Auto Fill is only available in PiCPro when a standalone MMC is the Target CPU.
1. Select Insert | Auto Fill Default Axes from the menu.
2. Select 4 1/2 Axes, 2 1/2 Axes, or SERCOS Axes from the resulting fly-out
menu.
If axes are present when one of these menu items is selected, a message will be dis-
played to indicate that all axes must be removed before default axes can be
inserted. If the axis count is 0 and 4 1/2 Axes or 2 1/2 Axes is selected, 4 or 2 servo
axes will be added and 1 digitizing axis will be added. The servo axes will have an
input type of Encoder and an output type of D/A. The digitizing axis will have an
input type of encoder. The servo axes will be named AXIS1-4. The digitizing axis
will be named AXIS49.
If the axis count is 0, and SERCOS Axes is selected, 8 SERCOS servo axes and 8
SERCOS digitizing axes will be added. Slot and ring will be set to 1. The slave
numbers will be 1-8. The servo axes will be named AXIS 1-8. The digitizing axes
will be named AXIS 49-56.
To insert a Time Axis

• Select Insert | Time Axis from the menu.
• Press the Insert key and select Time Axis.
• Right-click select Insert | Time Axis.
Up to 4 time axes can be inserted.
The Insert Axis Properties box appears.
2. Enter a name for the axis in the Axis Label: box.

3. The Axis Number: is entered by PiCPro in sequential order. These can, how-
ever, be changed. The axis number for a time axis is limited to 25 - 28.
Note: Output Type: and Input Type: are not available for a Time Axis and
appear as None.
4. Click on Apply to activate the Axis Data button for this axis OR click on OK
to continue inserting axes.
Editing a Servo Setup File
Your servo setup file contains the data for one or more axes. When you open a
servo setup file, the axes are ordered by axis type (Servo, Digitizing, Time) . You
entered the properties and data for each axis when you inserted them into the file.
You can edit that information.
Editing Axis Properties
You can access the axis properties box in one of the the following ways:
• With the axis selected, select Edit | Axis Properties from the menu
• With the axis selected, press Enter key.
• With the axis selected, right-click and select Axis Properties.
• Double-click on the axis.
Make the necessary changes and choose OK.
Editing Axis Data
You can access the axis data box in one of the following ways:
• With the axis selected, select Edit | Axis Data from the menu.
• With the axis selected, press <Alt + Enter>.

• With the axis selected, right-click and select Axis Data.
Make the necessary changes to Scaling, Iterator, or Position Loop Data and choose
OK.
Servo / Digitizing Axis Setup Data Categories
There are three categories of servo axis data in the Servo Setup program:
1. Scaling data - sets up the ratio between feedback units, ladder units, and axis
units. This allows you to enter axis units instead of feedback units in the appro-
priate places for iterator and position loop data in setup. The three type of units
are defined below:
• Feedback units - the units the servo software uses to perform its calcula-
tions and issue its commands in.
• Ladder units - the units used in the ladder program. They must be integers.
• Axis units - the units of measurement (inches, millimeters, degrees) for the
system. They may be integers or non-integers (decimals) and are used in
the Servo setup program to enter certain types of setup data.
2. Iterator data - specifies how data such as limits, ramps, filters, and rollovers
will be handled by the move iterator.
3. Position loop data - provides the servo software with information on how the
axis is set up for the position loop.

Entering Scaling Data
Input Feedback units, ladder units, and ladder units/axis units establish a scaling ratio be-
Scaling tween the feedback units the servo software uses to perform its calculations and issue
its commands, the units used in the ladder, and the units entered in setup.
Note: When using SERCOS feedback, it is recommended that the units be entered in
a 1:1 ratio.
Feedback Units - These are the units the servo software uses to perform its calcula-
tions and issue its commands.
Ladder Units - These are the units used in the ladder program. Ladder units must be
integers and cannot be fractional values.
The ratio of the feedback device signal to the control feedback units is:
• One revolution of a resolver = x feedback units
• One pulse of an encoder = one feedback unit
• One cycle of a quadrature type encoder equals four pulses.
Note: You cannot enter fractional values here.
Ladder Units/Axis Units - Axis units are the units of measurement (inches, millime-
ters, degrees) used in your system. They are used to enter values for several setup pa-
rameters.
Enter the ratio of ladder units to axis units. (1, 10, 100, 1,000, 10,000, or 100,000)
IMPORTANT
Keep in mind that certain iterator and position loop data is entered in axis units. The
default values are also in axis units and are sometimes at the upper limit of an accept-
able value (ramps and software limits). If you choose a ratio for your ladder units/axis
units that is greater than 1, then these default values will exceed the limit. Change the
default value to a lower value for those parameters.
Output These three parameters provide the information the controller needs to be able to cal-
Scaling culate how much voltage the analog output will need to operate the axis at a certain
speed and how many feedback units will be received for each motor revolution.
Commanded Voltage - Enter commanded voltage in millivolts.
Motor RPM at Voltage - Enter the motor RPM at the Commanded Voltage entered.
Counts/Motor Revolution – Enter the number of feedback units that occur for each
motor revolution.
Note: The Commanded Voltage, Motor RPM at Voltage, and Counts/Motor

Revolution parameters are used for scaling servo calculations by the servo
software. They do not represent limits. They do not apply to Stepper, SER-
COS, digitizing or time axes.

Calculate The Calc Defaults button can be used to calculate new default values of Iterator Data
Defaults and Position Loop Data as long as the ratio of feedback units to ladder units (FU/LU)
is less than 65535. (Not available for Digitizing Axes)
Data Field Default Calculation
Velocity Limit (AU/min) Counts/Motor Rev x Motor RPM at
Voltage x AU/LU x LU/FU
Acceleration Ramp (AU/min/sec) Velocity Limit / 2 sec.
Deceleration Ramp (AU/min/sec) Velocity Limit / 2 sec.
Controlled Stop Ramp (AU/min/sec) Velocity Limit / .2 sec.
Software Limit (Upper) (AU) 536870911 / (FU/LU x LU/AU)
Software Limit (Lower) (AU) -536870912 / (FU/LU x LU/AU)
Following Error Limit (AU) (Counts/Motor Rev / 8)

x (AU/LU) x (LU/FU)
In Position Band (AU) 10 LU x AU/LU
(+) Integral Error Limit (AUFE x update) In Position Band x 10
(-) Integral Error Limit (AUFE x update) -In Position Band x 10
Max Acceleration (AU/min/sec (3/2) x Velocity Limit / 3 sec.
Constant Jerk (3) (Max Acceleration) / 3 sec.

Note: If the result of a calculation would exceed the upper limit or fall below the
lower limit of a given field, the field will be set to that limit.

Determining Scaling Information
To determine what scaling information to enter for the number of FU/min/volt of
the D/A, you can use the Servo Force list (write) and the Servo View List (read).
1. Highlight the axis in Servo Setup and open the View | Servo Force List.
2. Click the Add/Remove to bring up the Pick List Dialog.
Button Description
Add All Click to add all items from the Pick list to the Chose list.
Add> Click to add selected item from the Pick list to the Chose list.
< Remove Click to remove selected item from the Pick list.
Remove All Click to remove all items from the Pick list.
OK Click to save changes made to the Chose list.
Cancel Click to close without saving changes made to the Chose list.
3. Highlight and then Add> the Feed Forward Percent parameter to the list.
4. Click OK.
5. Enter 100% for the value of Feed Forward Percent.
6. Move the axis at a fixed velocity in either always the positive or always the
negative direction.
7. Observe the following error in the Servo View List. If the following error is not
zero, the velocity scaling is incorrect.
8. Change the Motor RPM at Voltage in the Output Scaling of Axis Data.
For example, if you are jogging in the positive direction and the error is always
negative, increase the RPMs and vice versa.

9. Make the servo setup function and download the ladder to the control.
10. Again, observe the following error in the Servo View List.
11. Repeat the above steps until the following error is close to zero.
12. Finally, remake the servo setup function and perform a complete download of
the ladder.
Entering Iterator Data for Servo Axis

The following parameters comprise the Iterator Data for Servo, SERCOS, or Stepper
Axis:
Iterator Data Description

Velocity Limit (AU/min) Enter the maximum velocity the motor should ever be commanded
to in axis units/min. Limits the maximum motor RPM. Does not
apply to a slave axis.
WARNING
The position loop may cause the axis to travel faster than this speed
if enough position, integral, and/or derivative error accumulates.
Typical values are 100,000 to 10,000,000 AU/min (where 1 AU = 1

LU), not to exceed 4095 FU/update. Note: If 1 AU does not equal 1
LU, scale these values accordingly.
Slow Velocity Filter (ms) Enter in milliseconds the filter time constant it will take to smooth
out a “step” change in velocity while the axis is moving at slow
velocities.
Note: Specifically, the value entered represents the milliseconds
that the servo software takes to carry out 63.2% of the step change.
Range = 0 - 10,000 ms
Fast Velocity Filter (ms) Enter the milliseconds the filter time constant it will take to smooth
out a “step” change in velocity while the axis is moving at fast
velocities.
Note: Specifically, the value entered represents the milliseconds
that the servo software takes to carry out 63.2% of the step change.
Range = 0 - 10,000 ms
Slow/Fast Velocity Enter the velocity in axis units/minute (AU/min) at which the slow
Threshold (AU/min) or fast velocity filter should be applied.
Typical value is 0, not to exceed 4095 FU/update.
Rollover Position (AU) Enter the rollover position in axis units.
Valid range is 0 to 536,870,911 FU. If the value is zero, rollover is
off. If the value is non-zero, rollover is on.
Ignore Limits? An Until Ref. here allows a machine reference to occur without
exceeding the software limits designated earlier. This is useful if
you exceed the software limits because of how far you have to travel
to your reference switch or where your reference switch is located.
After the machine reference is complete, the software limits are in
effect. If Yes is selected, software limits cannot be set and .srv file
cannot be saved to a format prior to V13.0. If No is selected, soft-
ware limits are always in effect.
Software Limit (Upper) Enter the software-imposed upper travel limit in axis units. Exceed-
(AU) ing this limit will generate a C-stop condition.
Typical values are 100 to 1,000,000 AU (where 1 AU = 1 LU), not
to exceed 536,870,911 FU. Note: If 1 AU does not equal 1 LU,
scale these values accordingly.
Software Limit (Lower) Enter the software-imposed lower travel limit in axis units. Exceed-
(AU) ing this limit will generate a C-stop condition.
Typical values are 100 to 1,000,000 AU (where 1 AU = 1 LU), not
to exceed 536,870,911 FU. Note: If 1 AU does not equal 1 LU,
scale these values accordingly

Resumable E-Stop Options are Yes or No. Select Yes to allow Resumable E-Stop.
Allowed? Default value is No.
If Yes is selected, the E_STOP function and the Excess Following

Error E-Stop will execute a Resumable E-Stop. When a Resumable
E-Stop occurs, the following happens:
1. The servo loop is opened.
2. Zero voltage is sent to the analog outputs.
3. The moves in the active and next queues remain intact.
4. The axis’ Normal Interpolator remains running.
5. The axis goes into Resume Mode. In Resume Mode, the axis
will follow the Resume Interpolator. The Resume Interpola-
tor will output zero velocity until the RESUME function is
called. The RESUME function can only be called after the
Resumable E-Stop has been reset and the servo loop has
been closed. The axis remains in Resume Mode until the
RESUME function brings it back on path or until a non-
resumable E-Stop occurs and cancels Resume Mode.
If No is selected, the E_STOP function and the Excess Following

Error E_STop will execute a normal E_Stop (i.e. open the servo
loop, zero voltage to the Analog outputs, and clear the active and
next queues)
The E_STOP function and the Excess Following Error E-Stop are
the only types of E-Stops that are resumable. All other types of
E_Stops will execute normally regardless of this selection.

Linear Iterator
Acceleration Ramp Enter the rate in axis units/minute/second at which the servo soft-
(AU/min/sec) ware will iterate the axis to reach a higher velocity command.
Typical values are 10,000 to 10,000,000 AU/min/sec
(where 1 AU = 1 LU), not to exceed 1023 FU/update/update.
Note: If 1 AU does not equal 1 LU, scale these values accordingly.
Deceleration Ramp Enter the rate in axis units/minute/second at which the servo soft-
(AUmin/sec) ware will iterate the axis to reach a lower velocity command.
Typical values are 10,000 to 10,000,000 AU/min/sec (where 1 AU =
1 LU), not to exceed 1023 FU/update/update. Note: If 1 AU does
not equal 1 LU, scale these values accordingly.
Controlled Stop Ramp Enter the rate in axis units/minute/second at which the servo soft-
(AU/min/sec) ware will iterate the axis to reach a controlled stop.
Typical values are 10,000 to 10,000,000 AU/min/sec
(where 1 AU = 1 LU), not to exceed 1023 FU/update/update.
Note: If 1 AU does not equal 1 LU, scale these values accordingly.
S-Curve Iterator
Enable S-Curve Check this box to enable the S-Curve Iterator. If enabled, S-Curve is
the default iterator for this axis. If not enabled, it cannot be enabled
from the ladder.
S-Curve Wizard Selectable if Enable S-Curve box is checked. Select this button to
display the S-Curve Wizard dialog that will assist in defining max
acceleration and constant jerk for Move Accel/Decel and Controlled
Stop Decel.
Move Accel/Decel
Max Acceleration Enter the maximum acceleration for Move Accel/Decel.
(AU/min/sec)
Constant Jerk Enter the constant jerk for Move Accel/Decel.
(AU/min/sec/sec)
Controlled Stop
Decel
Max Acceleration Enter the maximum acceleration for Controlled Stop Decel.
(AU/min/sec)
Constant Jerk Enter the constant jerk for Controlled Stop Decel.
(AU/min/sec/sec)

Entering S-Curve Data for Servo Axis
Using this dialog, S-Curve information can be specified for both Move Accel/
Decel and Controlled Stop Decel. Selecting Move Accel/Decel will display
known information for Move Accel/Decel. Selecting Controlled Stop Decel will
display known information for Controlled Stop Decel.
When initially displayed:
• Move Accel/Decel will be selected.
• If S-Curve information has previously been entered, existing values will be
entered, and checkboxes checked accordingly. The slider will indicate the
relationship between acceleration and jerk. The resulting S-Curve will be
drawn with Distance Traveled displayed at the top.
• If S-Curve information has not been entered, Velocity will be checked and
set to a value equal to that of Velocity Limit as specified in the iterator
data. In addition, Time will be checked and set to a value of 3 seconds.
Constant Jerk and Max Acceleration will be calculated based on the initial
1/3 of the time at constant jerk, the next 1/3 of the time at constant maxi-
mum acceleration, and the final 1/3 of the time at constant jerk. The slider
will be set to approximately 1/3 from the left. And the resulting SCURVE
will display Distance Traveled.
The checkboxes are used to indicate data that is entered. The values for fields
where the checkbox is not checked will be calculated. At least two fields, but no
more than three at the most can be checked in order for a calculation to take place
and the graph to be updated. The spinner controls increment or decrement the
value in the associated field by 1% of the value. They are enabled when the associ-
ated checkbox is checked.
The following parameters comprise the S-Curve data:
S-Curve Data Description

Move Accel/Decel: Select this button to display the S-Curve information for Move
Accel/Decel.
Controlled Stop Decel: Select this button to display the S-Curve information for Controlled
Stop Decel. Note: This button will be disabled if S-Curve is being
defined for a time axis.
Relationship Between Enter % acceleration here or use the slider to express the relation-
Acceleration and Jerk ship between acceleration and jerk. When the slider is positioned at
(Edit Control and slider the far left, the relationship is 0% acceleration, 100% jerk. If posi-
are enabled when no tioned at the far right, the relationship is 100% acceleration, 0%
more than 2 checkboxes jerk. If positioned in the middle, the relationship is 50% accelera-
are checked.) tion, 50% jerk.
Velocity (Au/min): Check this box to use the velocity entered in the calculations.
If the Velocity checkbox is checked, a velocity can be entered here
and the spinner can be used to increase or decrease the value entered
in the edit control.
If the Velocity checkbox is not checked, the adjacent edit control
(data entry field) will be grayed and disabled. The calculated veloc-
ity will be displayed here.
Time (sec): Check this box to use the time entered in the calculations.
If the Time checkbox is checked, a time can be entered here and the
spinner control can be used to increase or decrease the value entered
If the Time checkbox is not checked, the adjacent edit control (data
entry field) will be grayed and disabled. The calculated time will be
displayed here.
Max Acceleration Check this box to use the acceleration entered in the calculations.
(AU/min/sec): If the Max Acceleration checkbox is checked, an acceleration can be
entered here and the spinner control can be used to increase or
decrease the value entered in the edit control.
If the Max Acceleration checkbox is not checked, the adjacent edit
control (data entry field) will be grayed and disabled. The calcu-
lated Max Acceleration will be displayed here.
Constant Jerk Check this box to use the jerk entered in the calculations.
(AU/min/sec/sec) If the Constant Jerk checkbox is checked, Constant Jerk can be
If the Constant Jerk checkbox is not checked, the edit control (data
entry field) will be grayed and disabled. The calculated Constant
Jerk will be displayed here.
Distance Traveled (AU): If an S-Curve is displayed, the distance traveled is displayed here.
OK Click to save data and return to the Iterator Data tab of the Axis
Data dialog.
Cancel Click to close the dialog without saving data and return to the Itera-
tor Data tab of the Axis Data dialog.
Help Click to display information related to the S-Curve Wizard dialog.

Entering Iterator Data for Digitizing Axis

Rollover Position (AU) Enter the rollover position in axis units (AU) in this field.
Valid range is 0 to 536,870,911 FU. If the value is zero, rollover
position is off. If the value is non-zero, rollover position is on.
Entering Position Loop Data for Servo Axis

Position loop data provides the servo software with information on how the axis is
set up for the position loop.

Position Loop Data Description
Input Provides a software method of changing the polarity of the position
Polarity feedback device. If the input polarity is incorrect, the axis will either
run away or move in the wrong direction. If this occurs, enter the
opposite polarity here.
Output Provides a software method of changing the polarity of the analog
Polarity output. If the output polarity is incorrect, the axis will either run
away or move in the wrong direction. If this occurs, enter the oppo-
site polarity here.
Analog If it is not possible to get a zero volts reading from a voltmeter
Output placed across the analog output channel for the axis, enter the
Offset (mV) amount of voltage in millivolts that allows you to reach a zero read-
ing.
Range: -10,000 to +10,000 mV
Feed Enter a percentage (from 0 to 100%) that you want the position loop
Forward to compensate for the lag that occurs between the generation of the
Percent following error and the correction of that error by the PID calcula-
tions.
Range: 0 to 100%
Proportional Gain Proportional gain calibrates corrective action proportional to the
(AU/min/AUFE) amount of following error. The value entered represents the axis
unit per minute for each axis unit of following error.
Typical values are 1,000 - 5,000 AU/min/AUFE
Integral Gain Integral gain determines corrective action proportional to the
(AU/min/AUFE x min)) amount of following error summed over the time duration of the
error at a zero velocity command. The longer the following error
exists, the greater the integral error. The value entered represents the
number of axis units per minute per axis unit of following error
times minutes. Typical value is 0. If required, up to 32,000 AU/min/
AUFE x min
(+) Plus Integral Error Tell the position loop to ignore any additional integral error beyond
Limit (AUFE x update) the value entered when the axis is moving in a positive direction.
Typical value is 0. Valid ranges are 100,000 to 500,000,000 AUFE
x update (where 1 AU = 1 LU). Note: If 1 AU is not equal to 1 LU,
scale these values accordingly.
(-) Minus Integral Error Tells the position loop to ignore any additional integral error beyond
Limit (AUFE x update) the value entered when the axis is moving in a negative direction.
Typical value is 0. Valid ranges are -500,000,000 to -100,000,000
AUFE x update (where 1 AU = 1 LU). Note: If 1 AU is not equal to
1 LU, scale these values accordingly.
Derivative Gain Derivative gain determines the corrective action proportional to the
(AU/min/AUFE/min) magnitude of change of the following error. The value entered rep-
resents the number of axis units per min for each axis unit of follow-
ing error per minute. Typically, this is set to 0. Typical value is 0.
Valid ranges are up to 500 AU/min/AUFE/min
Following Enter the amount of excess error in axis units to allow before an E-
Error Limit stop condition occurs. Typical values are 10 to 10,000 AU (where 1
(AU) AU = 1 LU), not to exceed 536,870,911 FU. Note: If 1 AU is not
equal to 1 LU, scale these values accordingly.

Position Loop Data Description
Update Rate (ms) Enter in milliseconds, (1, 2, 4, or 8) how often the servo update
occurs. 4 ms is adequate for most applications. Lower values con-
sume more CPU processing time. If too many axes have too low an
update rate, the CPU may not have enough processing time avail-
able to run the application program.
The iteration rate is eight times the servo update rate:
SUG (ms) Iteration Rate (ms)
.25 2
.5 4
1 8
2 16
4 32
8 64
For digitizing axes, the update rates are .25, .5, 1, 2, 4, 8, or 16 ms.
A rate can be selected for each axis.
Note: In master/slave moves, the iteration rate is the same as the

servo update rate. The update rate for the master axis and the slave
axis must be the same in any master/slave move.
In-Position Band (AU) Enter the distance in axis units that the axis must be on either side of
its endpoint before the in position flag is set. This in-position flag
can be used in your program. Typical values are 10 to 1,000 AU
(where 1 AU = 1 LU), not to exceed 536,870,911 FU. Note: If 1 AU
is not equal to 1 LU, scale these values accordingly.
Time Axis Setup Data Categories
There is only a single category of time axis setup data in the Servo Setup program
that:
• specifies how data such as rollover, max acceleration and constant jerk will
be handled by the move iterator,
• allows you to calculate default values for max acceleration and constant
jerk.
Note: There must be at least one Servo or Digitizing axis defined if a Time
Axis defined.

Entering Iterator Data for Time Axis

Rollover Position Enter the rollover position in counts (cnt) in this field.
(cnt) Valid range is 0 to 536,870,911 cnt. If the value is zero, rollover is
off. If the value is non-zero, rollover is on.
Enable S-Curve Check this box to enable S-Curve for this axis. If enabled, S-Curve is
the default iterator for this axis.
S-Curve Wizard Selectable if Enable S-Curve box is checked. Select this button to dis-
play the S-Curve Wizard dialog that will assist in defining max accel-
eration and constant jerk for Move Accel/Decel.
Max Acceleration Enter the maximum acceleration for Move Accel/Decel. Valid range
(cnt/min/sec) is 1 to 6.291455813e13.
Constant Jerk Enter the constant jerk for Move Accel/Decel. Valid range is 1 to
(cnt/min/sec/sec) 7.84319766e15.
Calc Defaults Select this button to initialize Max Acceleration to 30,000 cnt/min/sec
and Constant Jerk to 30,000 cnt/min/sec/sec.

Entering S-Curve Data for Time Axis
Using this dialog, S-Curve information can be specified for Move Accel/Decel.
Controlled Stop Decel is disabled and grayed because it is not valid for a time
axis.
When initially displayed:
• Move Accel/Decel will be selected.
• If Max Acceleration and Constant Jerk are 0 when the S-Curve Wizard
button is pressed, Max Acceleration and Constant Jerk will be calculated
using a time of 3 seconds, a velocity of 60,000 cnt/min and a value of 33
for the relationship between acceleration and jerk.
• If S-Curve information has previously been entered, existing values will be
entered, and checkboxes checked accordingly. The slider will indicate the
relationship between acceleration and jerk. The resulting S-Curve will be
drawn with Distance Traveled displayed at the top.
The checkboxes are used to indicate data that is entered. The values for fields
where the checkbox is not checked will be calculated. At least two fields, but no
more than three at most can be checked in order for a calculation to take place and
the graph to be updated. The spinner controls increment or decrement the value in
the associated field by 1% of the value. They are enabled when the associated
checkbox is checked.

S-Curve Data Description
Move Accel/Decel: Select this button to display the S-Curve information for Move
Accel/Decel.
Controlled Stop Decel: This button is disabled. It is not valid for a time axis.
Relationship Between Enter % acceleration here or use the slider to express the relation-
Acceleration and ship between acceleration and jerk. When the slider is positioned at
Jerk (Edit Control and the far left, the relationship is 0% acceleration, 100% jerk. If posi-
slider are enabled when tioned at the far right, the relationship is 100% acceleration, 0%
no more than 2 check- jerk. If positioned in the middle, the relationship is 50% accelera-
boxes are checked.) tion, 50% jerk.
Velocity (cnt/min): Check this box to use the velocity entered in the calculations.
If the Velocity checkbox is checked, a velocity can be entered here
and the spinner can be used to increase or decrease the value entered
If the Velocity checkbox is not checked, the adjacent edit control
(data entry field) will be grayed and disabled. The calculated veloc-
ity will be displayed here.
Time (sec): Check this box to use the time entered in the calculations.
If the Time checkbox is checked, a time can be entered here and the
spinner control can be used to increase or decrease the value entered
If the Time checkbox is not checked, the adjacent edit control (data
entry field) will be grayed and disabled. The calculated time will be
displayed here.
Max Acceleration Check this box to use the acceleration entered in the calculations.
cnt/min/sec): If the Max Acceleration checkbox is checked, an acceleration can be
If the Max Acceleration checkbox is not checked, the adjacent edit
control (data entry field) will be grayed and disabled. The calcu-
lated Max Acceleration will be displayed here.
Constant Jerk Check this box to use the jerk entered in the calculations.
(cnt/min/sec/sec) If the Constant Jerk checkbox is checked, Constant Jerk can be
If the Constant Jerk checkbox is not checked, the adjacent edit con-
trol (data entry field) will be grayed and disabled. The calculated
Constant Jerk will be displayed here.
Distance Traveled (cnt): If an S-Curve is displayed, the distance traveled is displayed here.
OK Click to save data entered and return to the Iterator Data tab of the
Axis Data dialog.
Cancel Click to close the dialog without saving data and return to the Itera-
tor Data tab of the Axis Data dialog.
Help Click to display information related to the S-Curve Wizard dialog.

Importing / Exporting Axis Data
Axis data can be imported from or exported to a file, which can be read by a spread-
sheet or text editor. The data file will be in comma separated values (.csv) format.
Exporting Axis Data
From the Axis Data dialog, click the Export button. To replace an existing file, select
the filename from the dropdown most recently used list or use the browse (...) button.
To create a new file, that can be opened by Excel®, enter a complete filename (include
full path information) with a .csv extension. Click the Export button.
Importing Axis Data

From the Axis Data dialog, click the Import button. Select the filename from the
dropdown most recently used list, use the browse (...) button, or type in the full path
and filename. Then click the Import button.

Any error or warning messages will appear in the Import Status: box. The line number and
type of error or warning will be listed. These errors or warnings could be caused by an
invalid data field identifier, invalid value, or a field that is not valid for a particular type of
axis. You can select to Skip Errors, which will ignore any invalid lines and import only
valid data, or Cancel Import, which will close the dialog without importing any data. You
can also exit this dialog by using the in upper right corner, or press the ESC key.
File Format for Servo Data File
You can create your own data file for importing using Excel or any text editor. However,
there are some important rules to follow when developing this .csv file. You might want to
consider exporting data first which will give you the full names of the identifiers with all the
proper spacing, and the needed id and version information in your file. You can then edit the
data elsewhere, and import it.
The first line of the file must contain the following id and version: PiCPro Servo
•
Data, V2.0 OR you can use PSD, V2.0. PiCPro cannot import the file without this
line. When exporting a file, PiCPro will add the version of PiCPro used to export the
data to the end of this line.
• Each line is made up of 2 fields separated by a comma: identifier,value. The first
specifies the data field, the second the value for that field. Any or all identifiers can
be used. If an identifier isn’t used, no change will be made to that axis data. If multi-
ple entries for the same identifier are encountered, only the last one read will be
used.
• Each line ends in a carriage return, line feed.
• To include a comment in the file, use // as a comment delimiter. Any information fol-
lowing this delimiter will be ignored.
• The data field identifiers can be entered using either the complete or abbreviated
form and are not case sensitive.
Data Field Identifiers
Shown in the first column is the complete identifier. The second column shows the abbrevi-
ated identifier. The third column shows the valid range of values. The final column lists the
axes type for which the data field is NOT valid. Only valid data fields can be imported.
Complete Data Field Abbrev. Value Range NOT valid for
Identifier Identifier Axis Type
Feedback Units FU 1 – 4294967295
Ladder Units LU 1 – 4294967295
Ladder Units/Axis Units LU2AU 1, 10, 100, 1000, 100000,
1000000
Commanded Voltage (mV) CV 1 – 10000 Stepper,
SERCOS,
Digitizing,
Time
Motor RPM at Voltage RPM 1 – 10000 Stepper,
SERCOS,
Digitizing,
Time

Counts/Motor Revolution CPMR 1 – 100000 Stepper,
SERCOS,
Digitizing,
Time
Velocity Limit (AU/min) VL 0.0 – 4294967295.0 Digitizing,
Time
Acceleration Ramp (AU/min/sec) AR 0.0 – 3839941406.0 Digitizing,
Time
Deceleration Ramp (AU/min/sec) DR 0.0 – 3839941406.0 Digitizing,
Time
Controlled Stop Ramp (AU/min/sec) CSR 0.0 – 3839941406.0 Digitizing,
Time
Slow Velocity Filter (ms) SVF 0 – 10000 Digitizing,
Time
Fast Velocity Filter (ms) FVF 0 – 10000 Digitizing,
Time
Slow/Fast Velocity Threshold (AU/min) SFVT 0.0 – 4294967295.0 Digitizing,
Time
Rollover Position (AU) RP -2147483648.0 –
2147483647.0
Ignore Limits? IL Yes, No, Until Refer- Digitizing,
enced, Y, N, U Time
Software Limit (Upper) (AU) SLU -2147483648.0 – Digitizing,
2147483647.0 Time
Software Limit (Lower) (AU) SLL -2147483648.0 – Digitizing,
2147483647.0 Time
Input Polarity IP Positive, Negative, P, N Stepper,
SERCOS,
Time
Output Polarity OP Positive, Negative P, N Stepper,
SERCOS,
Digitizing,
Time
Analog Output Offset AOO -10000 – 10000 Stepper,
SERCOS,
Digitizing,
Time
Feed Forward Percent FFP 0 – 100 Stepper,
SERCOS,
Digitizing,
Time
Proportional Gain (AU/min/AUFE) PG 0 – 20000 Stepper,
SERCOS,
Digitizing,
Time

Integral Gain (AU/min/AUFE x min) IG 0 – 32000 Stepper,
SERCOS,
Digitizing,
Time
(+) Integral Error Limit (AUFE x update) PIEL 0.0 – 2147483647.0 Stepper,
SERCOS,
Digitizing,
Time
(-) Integral Error Limit NIEL -2147483648.0 – 0.0 Stepper,
SERCOS,
Digitizing,
Time
Derivative Gain (AU/min/AUFE/min) DG 0 – 1000 Stepper,
SERCOS,
Digitizing
Following Error Limit (AU) FEL 0.0 – 4294967295.0 Stepper,
Digitizing,
Time
Update Rate (ms) UR 16*, 8, 4, 2, 1, .5, .25 Time
In Position Band (AU) IPB 0.0 – 4294967295.0 Stepper,
Digitizing,
Time
Move Accel/Decel Max Acceleration MACCEL 1 - 6.291455813e13 Digitizing
(AU/min/sec)
Move Accel/Decel Constant Jerk (AU/ MJERK 1 - 7.864319766e15 Digitizing
min/sec/sec)
Controlled Stop Decel Max Acceleration CACCEL 1 - 6.291455813e13 Digitizing
(AU/min/sec)
Controlled Stop Decel Constant Jerk CJERK 1 - 7.864319766e15 Digitizing
(AU/min/sec/sec)
S-Curve Enabled? SCRVEN No, Yes, N, Y Digitizing
Resumable E-Stop Allowed REA No, Yes, N, Y Digitizing
*Note: 16 is only valid for Digitizing Axes

Copying Axis Information
Once you have entered an axis in servo setup and entered all the axis data for that
axis, you can use the copy/paste commands to add additional axes with the same
information.
How to copy and paste an entire axis
1. Select the axis you want to copy. Select Edit | Copy from the menu, press
<Ctrl + C> or right-click and select Copy.
2. To insert a new axis place the focus on the EOF line and select Edit | Paste
from the menu, press <Ctrl + V> or right-click and select Paste. If there is
already an axis with the same number as the one you are pasting, you will be
advised that the axis will be pasted with the first available, valid axis number.
You can confirm or cancel the procedure.
3. The Axis Properties dialog will appear, with the prompt in the Axis Label:
box. You must give the axis a new label as there cannot be duplicates in the .srv
file. You can also make any other changes to the axis properties or axis data
that you wish.
How to copy axis data from one axis to another
From the servo setup screen you can also copy Position Loop, Iterator, and Scaling
data for one axis into the axis data for another axis. This is a time-saver if the axis
data parameters for both axes are similar. If some of the axis parameters for the
second axis need to be changed, you can edit them after you have copied the axis
data to the second axis.
1. Highlight the axis with the data you want to copy. Select Edit | Copy from the
menu, press <Ctrl + C> or right-click and select Copy.
2. Highlight the axis with the data you want to copy. Select Edit | Paste from the
menu, press <Ctrl + V> or right-click and select Paste.
3. If you need to change some of the parameters for the second axis, select Edit |
Axis Data from the menu or press <Alt + Enter> to bring up the axis data box.
Note: When pasting axes, the servo view list and servo force list information will
not be pasted. That information must be manually entered.

Pasting between .srv files with different CPU types
When copying from and pasting to files of different CPU types, you will be
prompted that the slot, channel, or slot/ring/slave values will be set to zero. You
must edit the axis to enter valid values.
If you are pasting into a standalone MMC or an MMC for PC file, you will also be
asked to select the axis type, either D/A Encoder or SERCOS.
When pasting between files with different CPU types, you will receive a warning
to check the input polarity. The input polarity of a PiC CPU is reversed from that
of the standalone MMC or MMC for PC. You must edit the axis data to avoid
unexpected motion when the ladder is run.
• If a digitizing DLS axis is pasted into a MMC for PC or PiC SRV file, an error
message will be displayed. A digitizing DLS axis can only be pasted when the
target CPU is MMC for PC.
• If an axis created in a MMC for PC SRV file and specified as a DLS Commu-
nications Master, is pasted into a MMC or PiC SRV file, a message will be dis-
played indicating that DLS Communications Master information will be
removed.

Saving a Servo Setup File
Save your file at regular intervals as you work on it.

To save a new file
1. Select File | Save from the menu.

2. In the Save As dialog that appears, choose a drive and folder where you want
to save your setup file.
3. Enter a name in the File name: box. Note: It is strongly recommended that the
filename use the DOS 8.3 naming convention of 8 characters, a period, and 3
characters.
4. Click Save.
To save an existing file
1. Choose one of the following:

• Select File | Save from the menu.
• Select File | Save As from the menu to change the name and/or location of
a file. By giving the file a different name when you save it, you create a
copy of the existing file while keeping the original intact.
2. Select the location for the file in the Save in: box.
4. Click Save.
To save a file in a format readable by a previous version of PiCPro
Servo Setup files that are created or modified in V14.0 or later cannot be opened
directly by earlier versions of PiCPro.
Do the following to save an SRV file for use with an earlier version of PiCPro for
Windows:
2. In the Save as type: list, select the desired type.
3. Click Save. Any errors will be displayed in the Information Window.
Printing Axis Information
You can print the axis information (scaling, iterator, and position loop information)
for one or all axes in your servo setup program.
To print axis information
1. Open the Servo Setup file (.srv) that you want to print. If you just want to print
the axis information for one axis, select that axis.

• Select File | Print from the menu.
• Press <Ctrl + P>.
The print dialog appears and you can click OK. If you want to print the axis data
for all axes in your setup file, choose All in the print dialog and click OK.
Making a Servo Setup Function
After you have entered all the setup information for all the axes in your applica-
tion, you will create a servo setup function to store all this information. This func-
tion will be stored in the servo library you designate and can then be called in your
ladder program to initialize the setup data for your application. The axes setup
information will then be sent to the control when you download your application.
The name of the function will be the same as the name of the .srv file name. It will
appear in the list of functions in PiCPro.
Note: Function names are limited to 8 characters.
To create a servo setup function
1. After all the setup information for all your axes has been entered, select Com-
pile | Make Function from the menu.
2. The Save As dialog will appear if you have not previously saved your setup
file. Choose the location you want to save your .SRV file to. There is a default
that is entered in the File name box beginning with Servo1.SRV. You can
accept this name or enter your own.
Note: The second setup file you create will have the default name
Servo2.SRV, the third will be Servo3.SRV and so on.
Note: It is strongly recommended that the filename use the DOS 8.3 nam-
ing convention of 8 characters, a period, and 3 characters.
3. The Compile SRV box appears. The Registered ServoSetup/SercosSetup
Libraries: section will hold the names of any setup libraries you have created
previously. You may choose from this list or create a new Servo Setup Library
by entering one in the Library Name: box.
Note: If you are recompiling a function that was created earlier, you must
place the function in the same library where it was originally locat-
ed. You cannot select a new library location. The Library Name:
box will be disabled (grayed out).
4. Click OK to insert the servo setup function into the chosen library. If you are
creating a new library a prompt will appear asking if you want to create a new
library. If the directory path specified for the new library is not found in the
current library path, a prompt will be displayed asking if this path should be
added.
Choosing Yes will define the library path so PiCPro can locate the function.
The library and setup function will immediately show up in PiCPro under Lad-
der | Functions and in the Functions list on the toolbar
5. Do a full compile and download of the ladder using this function.

To initialize setup data in your ladder
The servo setup function you compile with the Servo Setup program must be
incorporated into your ladder program. To initialize all the setup data you use the
standard motion function STRTSERV with your setup function. Below is a net-
work designed to do this. The example setup function is labeled SERVOSET.
Converting a Servo Setup File CPU Type
1. Select Edit | Convert Target CPU To from the menu.

2. A confirmation prompt will be displayed that indicates the types of changes
that will be made to the servo setup information for this file. You will need to
manually enter the slot, channel, and slot/ring/slave values.
Note: This function is not available in PiCPro MMC-Limited Edition.

Axis Tuning
Axis tuning allows you to make adjustments to offsets and gains for an axis
through software rather than hardware. When the ladder containing your servo
setup file is downloaded and scanning in the control, any servo axis defined in
your servo setup file can be tuned using the Servo Force List (Write) and the Servo
View List (Read) in Servo Setup. When you change a value through the Servo
Force List, a prompt will appear when you close the force list asking if you want to
update the axis data for the selected axis. If you answer Yes, the data will become a
permanent part of your program.
Note: In order to use Servo View and Servo Force, the latest version of the
motion library must be installed. This occurs automatically if you choose
Typical as an installation choice.
Axis Tuning using Forcing
You can write values into certain servo variables for an axis running in the control
using the Servo Force List.
To force an axis servo variable in the Servo Force list
1. Open the ladder containing your servo function. Choose one of the following
methods:
• Select the servo setup function, right-click and select View Servo Func-
tion.
2. Select the axis you want to force variable values on.
• Select View | Servo Force List from the menu.
• Right-click and select Servo Force List.
A Servo Force List can be opened for each servo axis you have defined in
Servo Setup. A Servo Force List cannot be opened for a digitizing axis. The
Axis number appears in the title bar of each list.
4. Use the Add/Remove button to edit the forcing list.
5. Click in the check box of the variables you want to force.
6. Enter a value for the variable in the Value column. A message will appear if
the value is out of range for the variable.
7. Click Update Forcing to send the updated values to the CPU

.
Axis Tuning using Viewing

You can read values from certain servo variables for an axis running in the CPU
using the Servo View List.
To view an axis servo variable in the Servo View list
1. Open the ladder containing your servo function. Choose one of the following
methods:
• Select the servo setup function, right-click and choose View Servo Func-
tion.
2. Select the axis you want to view variable values on.
• Select View | Servo View List from the menu.
• Right-click and select Servo View List.
A Servo View List can be opened for each servo axis you have defined in
Servo Setup. The Axis number appears in the title bar of each list.
4. Use the Add/Remove button to edit your view list.

Axis Tuning Variables
The following servo variables can be added to or removed from the Servo Force
List:
• Proportional Gain
• Integral Gain
• Derivative Gain
• D/A Offset
• Slow Speed Filter
• Feed Forward Percent
Note: The Servo Force List variables can also be written to and read from your
ladder using the TUNEREAD and TUNEWRIT functions.
In addition to the servo variables listed above, the Servo View List can display the
following servo variables:
• Position Error
• Command Velocity
• Actual Position
• Command Position
• D/A Output Voltage
• Move Type
• Next Move
• Emergency Errors
• Controlled Stop Errors
• Programming Errors
• Loop State
• Resume Distance
• Resume Mode
For a digitizing axis, Actual Position and Emergency Errors are the only variables
that can be displayed in the view list. The force list is not available for a digitizing
axis, or a time axis.
CHAPTER 7 PiCPro and SERCOS
SERCOS Setup Background Information
SERCOS is a Serial, Realtime, Communication System developed to interface

with digital controls and drives. Fiber optic cables are used to transmit data serially
with noise immunity and fast update times. SERCOS allows motion control in
velocity, torque, or position modes.
Sheffield Automation recommends that you acquire a copy of the NEMA SER-
COS Specification for reference information, especially if you will be performing
advanced control techniques. The SERCOS Specification is available through
ANSI. To order, call ANSI at (212) 642-4900 and ask for Manual IEC 61491. The
web page for SERCOS North American user’s group is www.sercos.com.
SERCOS allows you to create a digital instead of an analog motion control net-
work. A typical control/SERCOS network is illustrated below. The network con-
sists of up to eight digital drives connected to one master in a ring topology in
which messages travel unidirectionally. The network can support two fiber optic
rings from one SERCOS module.
Control SERCOS
Module
Master
1 2 8 1 2 8
(up to 8) (up to 8)
Digital Drives (Slaves) Digital Drives (Slaves)
Typically, the SERCOS drive accepts position commands from the control
whereas an analog drive accepts velocity commands. In SERCOS, the position
loop that compares the commanded position to the actual position and then applies
a PID algorithm to the difference is performed in the drive rather than in the con-
trol.
PiCPro and SERCOS 325

SERCOS and the control work together to provide a mechanism to control the
drive through communications. The following are all part of how communications
is established between the control master and the drive slaves.
• Each drive identified with a unique number
• Five communication phases (0-4) that must be passed through before oper-
ation begins
• The AT and MDT telegrams
• The cyclic data containing IDN numbers
• The service channel containing data
The following are all part of how control is performed once communications is
established.
• The value of the IDN in cyclic data

• The value of the data transferred over the service channel
• The mode defined by the status word
• The state of the control and status words
Note: Currently, PiC/SERCOS and standalone MMC/SERCOS configura-

tions support up to eight slaves on a ring where each slave controls
a single drive. MMC for PC/SERCOS supports up to thirty-two
slaves on a ring. None of the configurations support a slave control-
ling a group of drives as described in the SERCOS Specification.
You define the SERCOS configuration for all the SERCOS axes using Sercos-
Setup in PiCPro.
SERCOS Functions
The Motion library contains the following function/function blocks in the groups
listed. Refer to the Function/Function Block Reference Guide for a complete
description of the function/function blocks.
SCA_… function blocks have an AXIS input to identify the SERCOS axis that
has been initialized in Servo setup.
SCS_… function/function blocks identify the SERCOS axis by slot, ring, and
slave number.
SCR_… function/function blocks apply to one ring.
SC_… function applies to all rings.
326 PiCPro and SERCOS

DATA Group
SCA_CTRL Writes control bits to the MDT for a servo axis
SCA_RCYC Reads cyclic data from the AT for a servo axis
SCA_RECV Receives data from the service channel of the AT for a servo axis
SCA_SEND Sends data to the service channel of the MDT for a servo axis
SCA_STAT Reports the status from the AT for a servo axis
SCA_WCYC Writes cyclic data to the MDT for a servo axis
ERRORS Group
SCA_ERST Resets E-errors and closes the loop on a servo SERCOS axis
INIT Group
SCA_CLOS Reads the current position and closes the loop on a servo SERCOS
axis
MOVE_SUP Group
SCA_PBIT Initializes the SERCOS fast input (probe input)
REF Group
SCA_ACKR Acknowledges the reference cycle for a servo axis
SCA_REF Starts the reference cycle on the servo SERCOS axis
SCA_RFIT Initializes the reference cycle on the servo SERCOS axis
SERC_SLV Group
SCS_ACKR Acknowledges the reference cycle for a non-servo axis
SCS_CTRL Writes the control bits to the MDT
SCS_RECV Receives data from the service channel of the AT for a non-servo axis
SCS_REF Starts the reference cycle on the non-servo SERCOS axis
SCS_SEND Sends data to the service channel of the MDT
SCS_STAT Reports the status from the AT
SERC_SYS Group
SCR_CONT Continues communication if it was halted after Phase 2
SCR_ERR Reports ring errors
SCR_PHAS Reports the highest phase number completed
SC_INIT Copies the user data into the SERCOS module
Using Standard Motion Functions and Variables

There are certain things you should be aware of when using SERCOS feedback
with the motion library of PiCPro.
READ_SV/WRITE_SV Functions
These READ_SV and WRITE_SV variables cannot be used when using SERCOS
feedback on an axis.
Var # Name
27 Backlash compensation
28 TTL feedback
46 Set user PID command
47 User PID command
All other READ_SV/WRITE_SV variables can be used with an axis using SER-
COS feedback.
TUNEREAD/TUNEWRIT Functions
The filter variable is the only one that can be read and written by these functions
when using a SERCOS axis. The remaining TUNEREAD/TUNEWRIT variables
cannot be used with a SERCOS axis.
CLOSLOOP/OPENLOOP Functions
The CLOSLOOP function is not called on a SERCOS axis. The SCA_CLOS func-
tion block is used to close the loop on the SERCOS axis. The top three bits of the
SERCOS control word are set on subsequent SERCOS updates. When the OPEN-
LOOP function is called, the top three bits of the SERCOS control word are
cleared on subsequent SERCOS updates.
E_RESET Function
The E_RESET function is not called on a SERCOS axis. The SCA_ERST is used
to reset E-stop conditions on a SERCOS axis. The SCA_ERST function will read
the current position of the drive prior to closing the position loop.
STRTSERV Function
The SERCOS ring must be into Phase 4 of its communication cycle before the ser-
vos can be initialized. Call STRTSERV after Phase 4 has started.
An additional error can appear at the ERR output with a SERCOS axis;
Error # 5 The axis update rate in PiCPro is different
from the SERCOS ring update rate.
Using SERCOS Functions/Blocks with TASKS

Some of the SERCOS functions/function blocks can be used in TASK LDOs as
well as in Main LDOs.
For use in Main LDOs only For use in TASK or Main LDOs
SC_INIT SCR_CONT
SCA_RECV SCR_ERR
SCA_SEND SCR_PHAS
SCA_CLOS SCS_CTRL
SCA_ACKR SCS_STAT
SCA_REF SCA_CTRL
SCA_ERST SCA_RCYC
SCS_SEND SCA_WCYC
SCS_RECV
SCS_ACKR
SCS_REF

SERCOS Telegrams
SERCOS has a master/slave communications structure with the control as the mas-
ter and the drives as the slaves. All the communication between the two is done
with messages referred to as telegrams. A telegram is an ordered bit stream carry-
ing data and timing information.
There are three standard telegrams used in SERCOS communication as described
below:
1. MST - Master Synchronization Telegram - sent by the control to the drives
to set the timing and synchronization for everything that happens on the net-
work.
2. AT - Amplifier Telegram - sent by the drives to the control.
3. MDT - Master Data Telegram - sent by the control to the drives after it
receives the last AT in a cycle.
The type of data transferred by these telegrams is determined by the telegram type
you enter in SERCOS setup. IDN 15 contains the telegram types available. They
are described below.
IDN 15
(Telegram Type) Description
0 No data
1 Torque control
2 Velocity control, velocity feedback
3 Velocity control, position feedback
4* Position control, position feedback
5 Position and velocity control, position and velocity
feedback
6 Velocity control
7 User-defined
*If the slave will be controlled by Motion.Lib, 4 or 7 is the telegram type number
that is entered in SERCOS setup and the primary mode (defined by IDN 32) must
be set to the position mode. If telegram 7 is selected IDN 47 must be part of the
MDT and IDN 51 must be part of the AT.
IDNs
SERCOS has a system of identification numbers (IDNs) used to access specific
data. You can find a list of these IDNs in the SERCOS specification. There is a
standardized set covering the following categories:
1. General parameters 6. Definitions of telegram contents
2. Diagnostics 7. Drive operation modes
3. Lists of operation data 8. Standard operation data
4. Internal and external signals 9. Drive parameters
5. Manufacturer’s specifications
There is also a drive manufacturer-defined set of IDNs available.

Below is a list of IDNs that must be supported by any slave device you are using.
They are listed in the order they are worked through as Phase 2 and 3 proceed. For
complete descriptions of these IDNs, consult the SERCOS specification.
IDN
READ Description
Phase 2 00003 Shortest AT Transmission Starting Time (T1min)
00004 Transmit/Receive Transmission Time (TATMT)
00005 Minimum Feedback Processing Time (T4TMT)
00088 Receive to Receive Recovery Time (TMTSY)
00090 Command Value Proceeding Time (TMTSG)
00096 Slave Arrangement 0
WRITE Description
00001 Control Unit Cycle Time, Tncyd
00002 Communication Cycle Time, Tscyc
00006 AT Transmission Starting Time (T1)
00007 Feedback Acquisition Capture
00009 Position of Data Record in MDT
00010 Length of Master Data Telegram
00015 Telegram Type Parameter
00032 Primary Operation Mode
00089 MDT Transmission Starting Time
R/W Description
00099 Reset Class 1 Diagnostic
00127 CP3 Transition Check
Phase 3 00128 CP4 Transition Check
Working with Procedure Command Function IDNs

There are two types of IDNs used in SERCOS.
1. Parameter Data IDNs
These handle simple commands (i.e., IDN 100 where the value
for gain can be read or written). You define the values for these
IDNs.
2. Procedure Command Function (PCF) IDNs
These are commands that take a longer time to execute (i.e., IDN
262, load parameter data or homing cycle). With PCFs, the one
word DATA values hold bit patterns that relay the progress of
the function. The MDT has two bits and the AT has five bits. All
PCFs use these bits the same way. This bit field provides the
communication between the master and the slave.
Follow these steps to use a PCF IDN from your ladder.
1. Start the procedure by sending the PCF IDN with the data value of 3 using the
SCS_SEND or SCA_SEND functions. This sets (bit 0 = 1) and enables (bit 1 =
1) the PCF. SIZE for PCF IDNs is one word.

2. In the SCS_RECV or SCA_RECV function blocks, enter a 1 as the ELEM
member of the DATA structure.
3. Continually read the PCF IDN value using SCS_RECV or SCA_RECV func-
tion blocks. If the command was received by the drive, a status of 7 will be
read. This means the drive acknowledges the command set (bit 0 = 1) and
enabled (bit 1 = 1). If no error occurs and the procedure is complete, a status of
3 is returned. This means the drive acknowledges the command set (bit 0 = 1)
enabled (bit 1 = 1), and executed (bit 2 = 0). This may take only a few SER-
COS updates or several minutes depending on the PCF. If an error occurred
during the procedure, status bit 3 will equal 1.
Note: There is a change bit (bit 5) in the status word which can be used to
avoid continually reading the PCF IDN value as described above. See the SER-
COS specification for more information on this change bit.
4. After the read value of the PCF IDN equals status of 3, the command set (bit 0
= 1), the enabled (bit 1 = 1), and executed (bit 2 = 0), or the read value has sta-
tus bit 3 set (> 8), the PCF must be sent again using the SCS_SEND or
SCA_SEND functions with data = 0. This cancels the procedure by sending the
PCF IDN with bit 0 = 0.
This procedure and other advanced SERCOS features are described in the SER-
COS specification. Refer to section 7.4.4 of the NEMA SERCOS specification for
more detailed information on PCFs.
Note: PCFs may not be used in the SERCOS setup list.
You can also work with PCFs using the Online | Execute Procedure CMD within
SERCOS setup.
SERCOS Phases
During initialization, the SERCOS system moves through five communication
phases (0 through 4) before normal communication can begin. These are summa-
rized below.
Phase # Description
Phase 0 Closes the communication ring and allows initialization to proceed.
Phase 1 Identification phase where the control addresses each drive individ-
ually and waits for an acknowledgment.
Phase 2 Sets parameters for cyclic data transmission.
Phase 3 Sets parameters for non-cyclic or service channel data transmis-
sion.
Phase 4 The SERCOS ring can begin normal operation as defined by the
application.
The movement through these five communication phases occurs in sequential
order. In SERCOS setup, it is possible to decide to halt the movement after the
completion of Phase 2 allowing you to send additional IDNs specific to your appli-
cation which you did not enter in SERCOS setup and then resume moving through
Phase 4. At the end of Phase 4, you have another opportunity to send IDNs.

Cyclic Operation
After initialization is complete, SERCOS transmits critical data such as command
values, feedback values, etc. in synchronized, cyclic form. This data is updated
cyclically in real time at the update rate set in the control. You define the cyclic
data by choosing the Define Cyclic Data button within the Insert Slave box.
Service Channel
Non-critical data such as diagnostics, loop gains, etc. are transferred over a service
channel. This data is transferred once each cycle and goes both ways. It may take
several cycles to transfer data. The transfer is initiated by the control. Both opera-
tions within your ladder and within SERCOS setup make use of the service chan-
nel.
Comparing Cyclic Data and Service Channel Transfers

Cyclic Data Service Channel Data
Words in the telegram (AT/MDT) One word in the telegram (AT/MDT) is
are devoted to each piece of cyclic shared by all service channel requests. The
data to be transferred. content of the word changes with each ser-
vice channel request.
Data included in the cyclic data Service channel requests have no effect
causes the telegram to be larger. Con- on the length of the telegrams. One word
sequently, more communication time in the telegram is devoted to the service
is used. channel whether there are any requests or
not.
Cyclic data is sent every time a Only one word of the service channel
communication cycle occurs on the data is sent each communication update.
ring. Several updates are required to send or
receive data over the service channel.
You define cyclic data in SERCOS You make service channel requests from
setup and you cannot change this after the ladder or from SERCOS setup after
the ring has completed phase 4. communications is established. The
Note: Once communications is estab- requests are queued up on the SERCOS
lished, you can access the cyclic data module and are completed in order.
with the SCA_RCYC and Note: The ladder has priority over SER-
SCA_WCYC functions. COS setup.
Cyclic data can only be sent after Service channel data can be sent after
phase 4 is completed. the completion of phases 2, 3, or 4.
Only the operation data of an IDN Any element (name, attribute, units,
can be sent as cyclic data. minimum value, maximum value, and
operation data) of an IDN can be sent over
the service channel.

Service Channel Background Information
For a complete description of the activity on the service channel, read the Non-
Cyclic Data Exchange section of the SERCOS specification.
There is one word in the AT (from drive to control) and one word in the MDT
(from control to drive) that is dedicated to service channel communication. One
word of the service channel data is transmitted each way between the control and
the drive during each update. Both the ladder and SERCOS setup use the service
channel.
From the ladder, the following functions request information over the service
channel:
SCA_RECV SCA_SEND SCA_REF SCA_CLOS
SCS_RECV SCS_SEND SCS_REF
From SERCOS setup, the following online commands request information over
the service channel:
Execute Receive IDN Receive Send IDN Upload Drive
Procedure CMD Continuous Information
Keep the following in mind:
• The ladder requests are used for machine control.
• SERCOS setup requests are used for diagnosis.
• Only one request is processed on the ring at a time. It must be completed
before the next one begins.
• The SERCOS module allows the ladder to queue up to 16 requests to the
service channel.
• The ladder requests in the queue have priority over any requests coming
from SERCOS setup.
• All ladder queue requests (1 to 16) will be processed before any requests
from SERCOS setup.
• Resources are consumed in the transfer of information.
• The throughput of the service channel for a slave is also affected by the ser-
vice channel activity of other slaves on the ring.
Examples of Ladder Design to Access the Service Channel

There are many possible ways to design your ladder to access the service channel
and base ladder logic on the results. In the examples presented here, partial logic is
used to illustrate three approaches to monitoring the data of three IDNs in the lad-
der.
Example 1 Logic that gives priority to the ladder requests
In this example, you want to read IDN 1, read IDN 2, read IDN 3, then read IDN 1
when IDN 1 is complete, read IDN2 when IDN2 is complete, and read IDN3 when
IDN3 is complete and repeat. This example uses three queues because all three are

queued when START transitions. Any SERCOS setup requests will be processed
after the three queues have finished.

Example 2 Logic that allows SERCOS Setup commands to be read sooner
In this example, you want to read IDN1. Read IDN 2 when IDN 1 is complete.
Read IDN 3 when IDN 2 is complete. Read IDN 1 when IDN 3 is complete and
repeat. Using the logic shown below, only one queue is used because each request
is queued after the previous one is complete. This allows requests from SERCOS
setup to be processed after each function block.

Example 3 Logic that allows one IDN to be read more frequently.
In this example, you want to read IDN1 more frequently than IDN 2 or 3. Read
IDN1. Read IDN 2 when IDN 1 is complete. Read IDN 1 again. Read IDN 3 when
IDN 2 is complete and repeat. This example uses two queues: one for IDN1 and
one shared by IDN 2 and IDN 3.
SERCOS Setup Overview
Two approaches to SERCOS startup are presented next. In the first situation, it is
assumed that you are simply replacing your analog drives with SERCOS drives
and not attempting to use the advanced features available. In the second situation,
you are planning to use the advanced features available with SERCOS.
Replacing Your Analog System with SERCOS

When you are replacing your analog system with a SERCOS system, the analog
output module and the feedback module are both replaced by the SERCOS com-
munication module in the control. The fiber optic cable will replace the analog
voltage wires and the feedback wires. The drive will connect to the feedback
device and send that information back to the control over the SERCOS cable.
An overview of the procedure to follow if you simply want to use SERCOS with-
out any advanced features is summarized here.
In SERCOS Setup:
1. Enter a ring for each SERCOS ring.
2. For each ring, set the update rate, the baud rate to the rate of the drive, and No
pause after phase 2.
3. Enter a slave for each drive on each ring.
4. Leave the setup list empty.
5. Define the cyclic data to telegram 4 for all drives.
6. Define the operation mode for all slaves to operate in position control, with
Following Distance, Cyclic and System Interface.
7. Make a SERCOS setup function.
In Servo Setup, define each slave axis for basic control:
1. Select SERCOS as the Input and Output Type for the axis.
2. Make other selections for the servo axes for your application.
3. Make a servo function.
In PiCPro, program a ladder that will initialize the SERCOS slaves, then the servo
axes.
1. Call the SERCOS function you’ve made and then the SC_INIT function.
2. Call SCR_PHAS to read the phase and logic to detect phase 4.
3. When phase 4 is complete, call the servo function you made, then the STRT-
SERV function.
You can now control the axes using the same functions you used for analog servos
(with some exceptions including referencing and tuning).
Using SERCOS Advanced Features

There are features offered by a SERCOS system that go beyond simply replacing
the analog signal with a digital interface. In addition to position command and
feedback, other information can be exchanged between the drive and the control or
the workstation. In order to use these advanced features, it is necessary to upload
the IDN list that resides in the drive. This list holds all the information that can be
read/written from/to the drive. The list also indicates the units and range for each
IDN in the list. With this information, SERCOS setup can read or write this infor-
mation, define custom cyclic data, or change modes.
The ladder functions can use the advanced features to read and write data as well.
It is not required that the IDN list be uploaded from the drive in order to program
the ladder. But the contents of the drive IDN list provide the feature description for
the drive. Knowing the drive features available will aid you in your ladder design.
An overview of the procedure to follow if you want to use SERCOS with
advanced features is summarized here.
In SERCOS Setup:
1. Enter a ring for each SERCOS ring.

2. For each ring, set the update rate, the baud rate to the rate of the drive, and No
pause after phase 2.
3. Enter a slave for each drive on each ring.
4. Leave the setup list empty.
5. Define the cyclic data to telegram 4 for all drives.
6. Define the operation mode for all slaves to operate in position control, with
Following Distance, Cyclic and System Interface.
7. Make a SERCOS setup function.
In Servo Setup, define each slave axis:
1. Select SERCOS as the Input and Output Type for the axis.
2. Make other selections for the servo axes for your application.
3. Make a servo function.
In PiCPro, program a ladder that will initialize the SERCOS slaves, then the servo
axes.
1. Call the SERCOS function you’ve made and then the SC_INIT function.
2. Call SCR_PHAS to read the phase and logic to detect phase 4.
When phase 4 is complete, read the IDN list from the drive in SERCOS setup.
1. Select Online | Upload Drive Information from the menu.
2. Enter a unique file name and click Upload now. The status bar indicates
progress. This can take several minutes per drive. Typically, you only need to
upload this information once for each drive type.
3. The drive file (.csv) is a comma-separated variable file that can be read by a
text editor or spreadsheet.
Once the IDN list is read from the drive and SERCOS is initialized from the lad-
der, SERCOS setup can be used for the following:
• Run the drive via the battery box feature.
• Read the value of IDNs either once or continuously.
• Write the value of IDNs.
• Execute procedure command functions
• Customize the cyclic data.
• Operate the drive in different modes: position, velocity, or torque.
• Use secondary feedback. Secondary feedback can be read by customizing
the telegram and using the SCA_RCYC function in your ladder. Motion.lib
does not read secondary feedback.
Axis Positioning and Referencing in SERCOS
You can control axis position using either servo or non-servo SERCOS function/
function blocks. In SERCOS setup, the telegram type must be Telegram 4 position
mode. As defined by the SERCOS specification, with Telegram 4 IDN 47 is cyclic

data sent from the control to the slave. IDN 51 is cyclic data sent from the slave to
the control. When using a servo axis, SERCOS is selected as the feedback type in
Servo Setup.
With a Servo SERCOS Axis
The servo setup data is made into the User setup function in servo setup. The
STRTSERV function installs all the data. Both functions are put in your ladder.
To close a SERCOS axis loop, use the SCA_CLOS function. It will read IDN 47,
update the servo data with the new position, send the value as commanded posi-
tion, read rollover on position information, and set the control bits to cause the
drive to close it.
To reference the axis, the SCA_RFIT function block must be called and completed
prior to calling FAST_REF or LAD_REF.
Another option is to reference the axis using the SERCOS drive’s reference cycle
via the SCA_REF function block. This function block reads the value for IDN 47
as the last step in the reference process and returns this value in the RSLT output.
Use the SCA_ACKR function block to acknowledge that the reference cycle is
complete. Control will return to the control after this function block is called.
Opening SERCOS Setup
With the SERCOS Setup program, you will create a *.src file containing data for
all the slaves in your SERCOS system. You convert this *.src file to a function in
order to send all the data to the control so that the SERCOS slaves can be initial-
ized. There are several ways to access the SERCOS Setup program.
To create a new SERCOS setup file
2. Select SercosSetup from the box that appears
3. Select target CPU type (PiC, MMC or MMC for PC).

4. Choose OK.
Note: In the MMC-Limited Edition of PiCPro, Target CPU selection is not

made. Target CPU is always standalone MMC.
To open an existing SERCOS setup file
2. The Open dialog box appears. At the bottom, choose SERCOS Setup Files
(*.src) from the drop down list in the Files of type: box. This brings up a list of
all existing SERCOS setup files.
3. Highlight the file you want to open and click Open or press the Enter key.
Note: If you attempt to open a PiC or MMC for PC SERCOS setup file in the
MMC-Limited Edition, you will be prompted to convert the file to a standalone
MMC format. When opening an MMC for PC file in the MMC-Limited Edition,
the baud rate of the ring is 8 or 16, and the baud rate will be set to 4.
To open an existing SERCOS setup file from the setup function in a ladder
If you have already created a SERCOS setup function with your setup data and
have included it in your ladder, you can access the SERCOS setup file from there.
1. Place focus on the setup function in your ladder
2. Right-click and select View SERCOS Function.
or
Select View | SERCOS Function from the menu and then select the desired
setup function from the fly-out list.
Note: In order to open a SERCOS setup file from within your ladder, the SERCOS
file and the SERCOS function must have the same name. Any SERCOS setup file
created with PiCPro for Windows automatically has the same name as the SER-
COS setup function. However, any DOS SERCOS setup file may not have the
same name as the SERCOS setup function. Change the name of the *.src file to
match the name of the SERCOS setup function if you want to be able to open the
file from within the ladder.
To open an existing SERCOS setup file from Windows explorer
1. Open Windows explorer and find the *.src file you want to open.
2. Double-click on the *.src file you want to open and the SERCOS Setup win-
dow will appear.

Inserting / Editing SERCOS Rings
A ring is added to SERCOS Setup by using the Insert menu. Each time you insert
a ring you must insert the slave axes you are connecting to that ring and any IDNs
required.
Inserting / Editing a SERCOS ring
1. Select Insert | Ring from the menu. The Insert Master Ring box appears.
2. Enter the slot number (3-13) identifying the slot in which your SERCOS mod-
ule is installed in the control rack.
3. Enter the ring number (1-2).
Note: If a standalone MMC or an MMC for PC CPU is selected, only 1 ring
can be entered. Slot and ring are limited to a value of 1.
4. The default update rate is 4 ms. Choose an Update Rate from the drop down
list (1, 2, 4, or 8) if you want to change this. The update rate for any ring cannot
exceed the CPU update rate. The CPU update rate is the fastest of all servos
initialized. If the SERCOS slave axis is a servo axis, the ring update rate must
be the same as the axis update rate.
Note: If 1 ms is chosen as an update rate, only one ring with six slaves on that
ring can be used regardless of CPU type. All other update rates allow two rings
with eight slaves on each when used with a PiC CPU.
5. Choose the Baud Rate from the drop down list (2 or 4 for PiC and standalone
MMC, and 2, 4, 8, or 16 for MMC for PC).
6. Choosing YES for Pause after Phase 2 allows you to send/receive additional
IDNs via the ladder if required. Use the SCR_CONT function to continue on
through phase 4.
7. Choose OK to accept your ring configuration.
Once you have entered a ring in SERCOS setup, you can edit it by highlighting the
line the ring is on and pressing the Enter key or selecting Edit | Ring Data from
the menu. This brings up the Edit Master Ring Data box.
To insert another ring, highlight an existing ring or the end of rings line and press
the Insert key. The ring will be inserted above the highlighted line.

Inserting / Editing SERCOS Slaves
Inserting / Editing a SERCOS slave

After the ring has been entered, highlight the End of Slaves line in the Setup
screen and press the Insert key or select Insert | Slave from the menu. The Insert
Slave box appears.
1. Enter the name you want to assign to the slave axis.

2. If the CPU is a standalone MMC or PiC, enter the slave number (1-8).
If the CPU is an MMC for PC, enter the slave number (1-32).
Note: The number entered here must match the address switch set on the slave.
With a PiC or standalone MMC CPU, the slaves on a ring must be numbered to
match the quantity of slaves entered. For example, if you are entering three slave
axes on this ring, number them in any order: 3, 1, 2; or 1, 3, 2 or 1, 2, 3. However,
they cannot be numbered as 1, 2, 4.
If the CPU is an MMC for PC, enter the slave number (1-32) that matches the
address switch set on the slave. Slaves do not have to be numbered to match the
quantity of slaves entered. This is known as “Slave Gapping” and is allowed only
with an MMC for PC CPU. If you later change the CPU type, you will need to
renumber the slaves accordingly.

3. The Telegram: number defaults to 4. If the slave will be controlled by
motion.lib, then this is the telegram number you want. If you want to change to
one of the numbers listed below, you can do so under Define Cyclic Data.
Telegram # Description
0 No data
1 Torque control
2 velocity control, velocity feedback
3 Velocity control, position feedback
4 Position control, position feedback
5 Position and velocity control, position and velocity feedback
6 Velocity control
7 User-defined
4. Enter the name and location of the DriveIDN ListFilename: for this slave.
Use the Browse button to locate the file if necessary.
5. If this axis is a digitizing axis (external feedback will be used), check the Digi-
tizing Axis box. The telegram changes to 7, Digitizing Axis Probe Edge
checkboxes become active, and IDN 53 is added to the AT (if not already
present).
Note: A valid drive filename must be specified before you can select the Digi-
tizing Axis box.
6. In the Probe Inputs section, you can select whether the positive or negative
edge of the probe input should be used for a servo or digitizing axis. If you use
probe edges in your ladder, be sure to check them here in setup. The Telegram
defaults to 7 when a probe input box is checked. The following IDNs will be
added to the AT if they are not already present:
• Servo Axis - 130 for positive edge, 131 for negative edge
• Digitizing Axis - 132 for positive edge, 133 for negative edge
• For either Servo or Digitizing Axis - 179 if any box is checked
Once you have inserted a slave in setup, you can edit it by highlighting the line it is
on and pressing the Enter key or select the Edit | Slave Data from the menu. The
Edit Slave Data dialog appears. The Edit dialog looks just like the Insert dialog.

Edit Startup IDN List
When you click on Edit Startup IDN List, the following dialog box appears.
If you are entering IDN numbers to be used at startup with this slave axis, double-
click on the END OF LIST entry in the IDN number column or press the Insert
key. The Insert IDN box appears.
To edit an existing entry, double-click on that entry in the list or press the Enter
key. The Insert IDN box appears and you can make the necessary changes to the
selected IDN.
If you press the Insert key on an existing entry, you can add a new IDN. It will be
entered directly above the existing one.
You can also cut/copy/paste entries within this list using the <Ctrl + X, Ctrl + C,
and Ctrl +V > keys.

Inserting / Editing IDNs
Enter the data for the IDN to be added to the startup list.
The Slot/Ring/Slave Information identifies the slave you are inserting an IDN
for.
The System IDNs button brings up a list of system IDNs from the SERCOS spec-
ification. If you select an IDN from this list, it will appear in Number:.
The Drive IDNs button brings up a list of drive IDNs from the file you uploaded
from the drive. If you select an IDN from this list, it will appear in Number:.
You can choose an IDN that is not in any list by entering its number from the range
of 1 to 65535 (S1 to S32767 or P0 to P32767) in the Number: field.
The Name: box displays the IDN name for an IDN number that can be found in
any list.
The Length: box indicates the size of the data (two or four byte, variable length
one, two, or four byte data strings). This information is usually found in the system
or drive IDN file. If not, refer to the SERCOS specification and enter the size listed
there.
The Element: box indicates the SERCOS element to use.
Min: displays the minimum value allowed for the selected IDN.
Units: displays the units used with the selected IDN.
Max: displays the maximum value allowed for the selected IDN.

The IDN Data box allows you to enter the value within the minimum/maximum
range given.
Clicking OK will place the data entered into the startup list. Cancel allows you to
exit without saving any data.
Define Cyclic Data
From the Edit Slave Data box, click on Define Cyclic Data.
The Slot/Ring/Slave Information identifies the slave you are defining cyclic data
for.
The Telegram area allows you to choose from the list of telegrams shown in a
drop down list.
The telegram you choose is held in IDN 15. The MDT: and AT: telegram boxes
hold the IDNs connected to the telegram you select.
Note: Once SERCOS is initialized, you cannot change this configuration. The
operation mode must support these cyclic data requirements.

If you choose any Telegram number from the drop down list excluding number 7,
the cyclic data will be defined for you. If you choose number 7, you must be sure
that the drive IDN list has been uploaded from your drive and stored in a file. Then
you define the cyclic data.
If you choose any telegram other than 7, you do not have to make any other
choices.
If you choose telegram 3, 4, or 5, you are using feedback 1 on the drive.
If you choose telegram 11, 12, or 13, you are using feedback 2 on the drive.
If you choose telegram 7, you must also define a list of IDNs for sending and
receiving cyclic data.
The MDT and AT buttons to the right of the MDT: and AT: description boxes are
only active if telegram 7 is chosen. They include lists of IDNs from IDN 187 (AT)
and IDN 188 (MDT). These come from the drive list that you uploaded from your
drive. You click on an IDN in the list to add it to the description. You can click on
a highlighted IDN in the list to remove it from the description.
Note: When you are working with motion.lib, select either telegram 4 or telegram
7. If you choose 4, nothing further needs to be done. If you choose 7, IDN 47
(position read) must appear in the MDT description and IDN 51 for feedback 1
(IDN 53 for feedback 2) (position write) must appear in the AT description. You
can then place additional IDNs in the description from the MDT/AT lists.
The list of IDNs for MDT become IDN 24 and for AT become IDN 16.

Cyclic Data Structures
From the Define Cyclic Data box, click on Cyclic Data Structures.
If you are using the SCA_RCYC and SCA_WCYC functions from motion.lib, you
will need to include the structures in the Cyclic Data Structures box in your lad-
der. The Copy to Clipboard button allows you to transfer these structures to your
software declarations table with the Paste command. The structure ILISTW is
used with the SCA_WCYC function and the structure ILISTR is used with the
SCA_RCYC function.

Define Operation Modes
From the Edit Slave Data box, click the Define Operation Modes button.
A SERCOS slave can operate in up to eight modes provided the drive you are
using supports them. The modes are defined and enabled in the Define Operation
Mode dialog box.
The slave is identified in the Slot/Ring/Slave Information area.

The enabled modes are shown in the Enabled Mode area.
When the Define Operation Mode box is opened, the Primary Mode tab is
enabled with the defaults shown. You can change these defaults for the Primary
Mode and you can enable any other mode and change the defaults connected to
them. Simply click on the tab you want to define and enable.
The modes must support the cyclic data requirements that are configured using the
Define Cyclic Data dialog.

Operation Mode Application Note
Typically, you will operate in the Primary Mode, which represents position con-
trol. If your drive must operate in an additional mode such as torque, one or more
of the Secondary modes is defined. The options you choose will depend on the fea-
tures of the drive. If you choose something that is not supported by your drive, an
error will be reported by the SCR_ERR function when the SC_INIT function
block is called during the initialization of the drive. After you have made your
SERCOS setup function, downloaded it to the control, and started the scan, your
selections will be sent to the drive after phase 2. If an error occurs, it will appear in
the SCR_ERR function and the initialization will stop. The slave number, the IDN,
and the reason for the error are reported on the SLV, IDN, and SERR outputs
respectively.
The option of Cyclic or Service Channel determines whether the command for
this mode will be sent to the drive over the cyclic data or the service channel. Since
torque control usually requires a fast update time, you would want to use cyclic
data. Velocity control, on the other hand, can use the service channel. If cyclic is
chosen, a custom telegram must be created. To do this, click on the Define Cyclic
Data button in the Edit Slave Data dialog.
When you are using motion.lib to operate the drive, you use the position or Pri-
mary Mode. Position commands are sent to the drive. When operating in a Second-
ary Mode, the ladder has the responsibility of setting the mode and sending the
appropriate commands.
The mode can be set by calling the SCA_CTRL function with the OPTN input set
to 1. Prior to calling SCA_CTRL, the default is the primary mode. You can discon-
nect motion.lib from the drive by writing a 1 to WRITSV variable 48. Then you
use the SCS_CTRL function to write the loop state, the cyclic data, and the opera-
tion mode to the drive.
The command is sent to the drive by the ladder. It is based on the mode selected
and whether the transmission will be cyclic or service channel. If cyclic is chosen,
the SCA_WCYC function is used to write the command from the ladder. It is rec-
ommended that this function be called from a task that is executed every servo
update.
Copying SERCOS Data
Once you have entered a SERCOS configuration in setup, you can use the copy/
cut/paste commands.
How to use the copy/cut/paste commands
1. Enter the SERCOS configuration.
2. Select the ring(s) or slave(s) you want to copy or cut and choose one of the fol-
lowing methods:
• Click or buttons on the standard toolbar

• Select Edit | Copy or Edit | Cut from the menu.

• Press <Ctrl + C> (copy) or <Ctrl + X> (cut).
• Right-click and select Copy or Cut.
Note: When you cut/copy a ring its slaves are also cut/copied.
3. Place the focus on the location you want to paste into and choose one of the
following methods:
• Click button on the standard toolbar.

• Select Edit | Paste from the menu
• Right-click and choose Paste.
The configuration will be pasted above the selected location.
Note: Pasting is limited by the valid number of rings and slaves allowed for the
CPU type.
4. Double-click on the slave. Make the necessary changes and choose OK.
Cut/Copy/Paste Limitations (between different SRC files)
When you cut/copy/paste between setup files that were created for different CPU
types, you will receive confirmation messages about converting the slot, ring and
slave values to zero. Each ring and slave will have to be edited to enter valid val-
ues.
If you are trying to paste more rings than allowed by the CPU type, you will
receive an error message, and nothing will be pasted.
In some cases when pasting rings, more slaves will be pasted than allowed for the
CPU type. They will have to be manually deleted.
If you are trying to paste more slaves than allowed by the CPU type, you will
receive an error message, and nothing will be pasted.
When pasting a slave, the Receive Continuous and Send IDN entries for that slave
will not be pasted. That information must be manually entered.
When pasting a ring from MMC for PC to PiC or standalone MMC, if the baud
rate of the ring is 8 or 16, the baud rate will be set to 4.
<Ctrl + C> (copy) or <Ctrl + X> (cut), and <Ctrl + V> (paste) can also be used
when editing the Startup IDN, Receive Continuous, and Send IDN lists.

Saving a SERCOS Setup File
It is a good idea to save your file at regular intervals as you work on it.
Using the Save command, you can save the file under its existing name.
Using the Save As command, you can specify a new filename and/or a location
where you want to store the file.
To save a new file
1. Select File | Save from the menu.
2. In the Save As box that appears, choose a drive and folder where you want to
save your setup file.
3. Enter a name in the File name: box. Note: It is strongly recommended that the
filename follow the DOS 8.3 naming convention of 8 characters, a period, and
3 characters.
4. Click Save.
To save an existing file
Select File | Save from the menu
To save a file under a different name or in a different location
You can use the File | Save As command to change the name and/or location of a
file. By giving the file a different name when you save it, you create a copy of the
existing file while keeping the original intact.
2. Select the location for the file in the Save in: box.
4. Click Save.
To save in a format readable by a previous version of PiCPro
SERCOS Setup files created or modified in V13.0 cannot be read by previous ver-
sions of PiCPro.
• To save the file in a format that can be read by older versions of PiCPro
select File | Save As from the menu.
• In the Save as type: combo box, select the desired PiCPro version.
• If invalid information for the specified format exists in the file, details will
be shown in the Information Window to indicate the invalid ring(s) or
slave(s).
• If the CPU type is MMC for PC, the file cannot be saved in a format read-
able by older versions of PiCPro.

Printing SERCOS Setup
You can print a highlighted selection or all the information in the SERCOS Setup
file.
To print SERCOS data
1. Open the SERCOS Setup file (*.src) that you want to print. If you just want to
print the data for one ring, select that ring. If you want to print the data for a
slave, select that slave.
2. Choose one of the following methods to bring up the print dialog:
• Click button from the standard toolbar.

• Select File | Print from the menu.
• Select <Ctrl + P>.
3. The print dialog box appears and you can click OK.
4. If you want to print the data for everything in your setup file, choose All in the
print dialog box and click OK.
Making a SERCOS Setup Function
After you have entered all the SERCOS setup information, you will create a SER-
COS setup function to store all this information. This function will be stored in the
SERCOS library you designate and can then be called in your ladder program to
initialize the SERCOS setup data for your application. The SERCOS setup infor-
mation will then be sent to the control when you download your application.
The name of the function will be the same as the name of the *.src file name. It
will appear in the list of functions in PiCPro.
To create a SERCOS setup function
1. After all the setup information has been entered, select Compile | Make Func-
tion from the menu.
2. The Save As box will appear if you have not previously saved your setup file.
Choose the location you want to save your .SRC file to.
There is a default that is entered in the File name: box beginning with
SERCOS1.SRC. You can accept this name or enter your own.
Note: The second setup file you create will have the default name
SERCOS2.SRC, the third will be SERCOS3.SRC and so on. It is strongly rec-
ommended that the filename be 8 characters, a period, and 3 characters.
3. The Compile SRC box appears. The Registered ServoSetup/SercosSetup
Libraries: section will hold the names of any setup libraries you have created
previously. You may choose from this list or create a new SERCOS Setup
Library by entering one in the Library Name: box. Note: If you are recompil-

ing a function that was created earlier, you must place the function in the same
library where it was originally located. You cannot select a new library loca-
tion. The Library Name: box will be disabled (grayed out).\
4. Click OK to insert the SERCOS setup function into the chosen library. If you
are creating a new library, a prompt will appear asking if you want to create a
new library. If the location of the new library is not part of the PiCPro Library
paths, a prompt will appear asking if the path should be added. Choosing Yes
will define the library path so PiCPro can locate the function. The library and
setup function will immediately show up in PiCPro under Ladder | Functions
and in the Functions list on the toolbar.
To initialize setup data in your ladder
The SERCOS setup function you compile with the SERCOS Setup program must
be incorporated into your ladder program. To initialize all the setup data you use
the standard motion SC_INIT function block with your setup function. Below is a
network designed to do this. The example setup function is labeled SERCOS~1.

Upload Drive Information
To use additional SERCOS features beyond replacing the analog signal with a dig-
ital interface, it is necessary to upload the drive information from the drive. This
information is in the form of a list of IDNs. The list will show all the information
that can be read or written from the drive. It will indicate the units and the limits
for each IDN in the list. Using this information, SERCOS setup can read or write
information, define custom cyclic data, or change modes.
To upload this IDN List, select Online | Upload Drive Information from the main
menu. This dialog provides the capability to upload the IDN List from a single
device or for all of the slaves defined in SERCOS Setup
1. To upload drive information for a single drive, select Upload drive info for a
single slave as shown below:
• Select a slot/ring/slave (SRS) from the drop down list.

Available slave axes will be listed in the drop down list for SRS:. Choose
the slave to which the drive information is to be uploaded.
• Select a Drive IDN List Filename.
The Drive IDN List Filename: box allows entry of a path and filename or
the capability of searching for a folder and filename by using the Browse
button. It is recommended that the .csv extension be used since it allows
the file to be opened in Excel. However, any three letter extension can be
used.
• Finally, select Upload Now to begin the upload process.
The Status: line will indicate that the upload is complete, whether or not the
process was halted due to an error, or if your workstation is waiting for a re-
sponse. The status bar will show the progress of the upload.

2. To upload drive information for all the drives listed in SERCOS setup, select
Upload drive info for all slaves listed in SERCOS Setup as shown below:
Select Upload Now to begin the upload process for all slaves listed in SER-
COS Setup.
SRS:, Device IDN List Filename, and Status will update to reflect which
slave is currently being uploaded, the filename the IDN List is being written
to, and the status of the current slave’s upload.
The Upload All Progress bar indicates the progress for the upload of all
slaves. It indicates the number of SERCOS slaves that have been updated
versus the total number of SERCOS slaves to upload.
Errors that occur during the upload as well as the completion status of each
upload are provided in the information window.
Notes:
• Upload can only be done in phase 2 or 4.

• The upload time can vary considerably based on the type of drive, the num-
ber of IDNs supported and the type of control being used.
Changing IDN Data and Uploading IDNs Note

Changing the data value of some IDNs can change related IDNs also. One example
is the IDNs that control scaling. For example, IDN 76 position data scaling type
determines the units of IDN 47 position command value (inches, millimeters, etc.).
The attribute and units elements of IDN 47 change based on the value of IDN 76.
If your drive allows you to write the data value of IDN 76, the drive should also
make corresponding changes to the attribute and unit elements of IDN 47.

When you upload the IDN list from the drive, the units and attributes of each IDN
are read and stored in the drive file. If, for example, changes are made to IDN 76
after the list is uploaded, IDN 47 attribute and unit elements will be different in the
drive than in the drive file.
Always upload the drive IDNs after you make changes to IDNs that affect other
IDNs. You can read the drive documentation to determine which IDNs affect the
attribute and unit elements of other IDNs. Following is a list of common ones:
76 Position data scaling type

77 Linear position data scaling factor
78 Linear position data scaling exponent
79 Rotational position resolution
44 Velocity data scaling type
45 Velocity data scaling factor
46 Velocity data scaling exponent
160 Acceleration data scaling type
161 Acceleration data scaling factor
162 Acceleration data scaling exponent
86 Torque/force data scaling type
93 Torque/force data scaling factor
94 Torque/force data scaling exponent
Converting a SERCOS setup file’s CPU Type
Select Edit | Convert Target CPU To | PiC or MMC or MMC for PC from the
menu.
A message box similar to the following will appear.
When you convert from one CPU type to another, all slot, ring, and slave values
are set to zero. You will need to edit each one to assign the correct slot, ring and
slave values. In cases where more rings or slaves are present than allowed for the
chosen CPU type, you will need to delete them. The compile function will not
allow you to have more rings or slaves than valid for the CPU type and all must
have valid values.

Valid values are:

PiC 16 8 3-13 1-2 1-8
standalone 1 8 1 1 1-8
MMC
MMC for PC 1 32 1 1 1-32
Note: Converting to a new CPU type will remove all entries from the Receive
Continuous and Send IDN lists. The information will have to be manually loaded.
When converting from MMC for PC to PiC or standalone MMC, if the baud rate of
the ring is 8 or 16, the baud rate will be set to 4.
Copying an SRS structure to the clipboard
You can copy an SRS Structure to the clipboard for the slave that is currently
selected. This structure contains slot, ring and slave information. The structure can
be pasted into software declarations and used as the input to the SERCOS func-
tions that need SRS.
The procedure is as follows:
1. Open or create a SERCOS Setup file.
2. Select the Slave by clicking on the line containing the Slave.
3. Select Edit | Create SRS Structure from the menu

The SRS Structure has now been copied to the clipboard and is available for
pasting to software declarations.
Note: If any slot, ring, or slave number was set to zero (because of a conversion of
CPU type, or because of pasting between files for different CPU types) and was
not manually changed to a valid number, an error message will be displayed, and
the SRS Structure will not be pasted to the clipboard.

Battery Box
The battery box feature allows you to command velocity motion of a SERCOS
slave from PiCPro.
IMPORTANT – It is the operator’s responsibility to prevent possible damage to
machinery that is connected to the drive due to overspeed or direction errors.
Select Online | Batterybox from the menu.
Using the Battery Box

The following procedure describes the steps to take to use the battery box to con-
trol the SERCOS drive.
1. In SERCOS setup, define the operation mode for the SERCOS slave as veloc-
ity over the service channel. It is recommended that you use one of the second-
ary modes for this since the primary mode is used by motion.lib. Click the
mode tab, and click the Enabled box. Select the Velocity Control and the Ser-
vice Channel radio buttons. Click OK when finished.
2. The Drive IDN S91 is the velocity limit for the battery box. If S91 is changed
to enable the battery box (i.e. Send IDN), then the Drive IDN list file must be
updated as well. If S91 is left at 0, the battery box velocity will be no greater
than 0 preventing axis movement. Note: Reference IEC61491for additional
information on this IDN.
3. Ensure that all motion is stopped.
4. Call the OPENLOOP function to open the servo loop
Note: It is important to remember that there is a loop in the control and also a
loop in the SERCOS drive that must be opened.
5. Call the CLSLOOP? function to ensure that both loops have been opened.

6. Use the WRITE_SV function to set variable 48 to one. This prevents
motion.lib in the control from controlling the drive. You can now use the bat-
tery box to move the axis.
Note: The drive loop is closed while the battery box is active. It does not open
when you exit the battery box.
7. The Slot/Ring/Slave Information (SRS:) defaults to the selected slave in the
SERCOS Setup List. If no slave was selected, all of the other controls in the
dialog are disabled until you fill in the SRS.
8. Select the operation mode.
9. Type in the velocity or adjust the slider. You can also use the up and down but-
tons.
10. Select either Plus or Minus for the direction.
11. Click Start. Once started, the motion continues until you click on the Stop but-
ton.
OR
12. Click Jog Mode for jogging the SERCOS drive and follow the directions
shown in the dialog box.
Note: With either method, there may be some delay between selecting an
action and the drive motor reacting depending on the speed of the workstation.
13. When you are finished using the battery box, exit it.
14. Use the WRITE_SV function to set variable 48 to zero. This gives control back
to motion.lib in the control and both loops will be opened as in step 2.
15. Ensure that all motion is stopped.
16. Call the SCA_CLOS function to close the loop.
17. Call the CLSLOOP? function to confirm that both loops are closed.
You are now ready to resume control using motion.lib in the control.

Receive IDNs
You can receive information on an IDN from the drive with this feature (Online |
Receive Idn...). If you have a slave selected, the Slot/Ring/Slave Information
will default to it. If there is no information in the SRS: box, you cannot proceed.
You can choose from four categories of IDNs: System, Drive, Cyclic Data, or
Startup IDNs.
The Number:, Name:, Length:, and Element: boxes will be filled in when you
select an IDN from one of the lists.
Or you can enter an IDN number (Range from 1 to 65535; or S1 - 32767 or P0 -
32767). If the number you entered can be found in one of the IDN lists, the data
length will be displayed. If it cannot be found, you must enter the data length.
Valid values will be listed in the drop down list.
The Element: box allows you to select what element of the IDN you want to
receive. The default is the operation data. Other elements include the name,
attribute, units, minimum value, and maximum value. Choose them from the drop
down list.
After you have entered the IDN number, the Receive button is activated. Click it to
read the requested IDN from the drive. The Receive button changes to Abort.
The Status: box reports on the progress of the receive command.
The Data box holds the data for the requested IDN. If the IDN is a string and is not
completely displayed, double-click on the Data entry to view the entire string. If
the IDN requested is a variable length array, a grid will be displayed. Each array
element is displayed in a separate row.
Receive Continuous IDN Data
You can choose to receive IDN data continuously. Select Online | Receive Con-
tinuous... from the menu. Add new IDNs to the list by double-clicking or pressing
the Insert key on the End List line. The Insert IDN dialog appears.
Click in the Enable column to choose which IDNs you want to receive continu-
ously.
With Receive Continuous, the Element column can include operation data,
attribute, minimum value, and maximum value.
Note: Variable length data cannot be requested in Receive Continuous.

Use Receive Idn.
To delete an entry from the receive continuous list, click in the first column or
select the entire row and press the Delete key. A warning message will appear.
Click OK if you want to proceed with the deletion.
To cut, copy, and paste in the list use the <Ctrl + X, Ctrl + C, and Ctrl +V > keys.
When the Receive button is chosen, all the enabled IDNs will be received continu-
ously. The button text changes to Abort. You can choose Abort to halt the receive
continuous command. The Status: field reports on the status of the receive contin-
uous command.

Inserting / Editing IDNs for Receive Continuous
To insert a new IDN in the Receive Continuous list, you can double-click on the
End List line or press the Insert key when the focus is on any line. The new IDN
will be inserted above the line focus is on.
To edit an existing IDN in the Receive Continuous list, you can double-click on the
entry or press the Enter key. To enter a new IDN when the focus is on an existing
entry, press the Insert key. The new IDN appears above the selected line.
The Insert IDN box shown below appears.
The SRS: information must be entered in order to proceed.

You can choose an IDN from any of the four IDN buttons or enter one from the
range 1 to 65535 or S1 to S32767 or P0 to P32767 in the Number: field.
If the number you entered is located in any of the IDN lists, a name will appear in
the Name: field and a value will appear in the Length: field.
If the number is not found in any of the IDN lists, no name appears in the Name:
field and you must enter the length in the Length: field.
The Element: field defaults to operation data. You can change this to attribute,
minimum, maximum, or data from the drop down list.
Units: displays the type of units for the selected IDN.
Click OK to add the information entered to the Receive Continuous list. Click
Cancel to ignore any changes and return to the Receive Continuous box.

Send IDNs
If you want to send IDNs, select the Online | Send IDN from the menu or right-
click and select Send IDN. Add new IDNs to the list by double-clicking or press-
ing the Insert key on the End List line. The Insert IDN box appears and you enter
the information for the IDN you want to add to the Send List.
Once your list is complete, you must check the box in the Enable column if you
want to send that IDN when you select the Send button.
You can cut/copy/paste entries within this list using the <Ctrl + X, Ctrl + C, and
Ctrl +V > keys.
When the Send button is selected, the text changes to Abort so that you can select
it to stop the transfer at any time.
The Status: bar reports on the progress of the send command. Communication and
drive errors that may occur are also reported here.
The Save To Startup button saves the IDNs you highlight to the appropriate star-
tup list. You may want to do this after you know the data you have entered is work-
ing for your application.
Note: Only IDNs with the Operation Data element can be saved to the startup list.

Inserting/Editing IDNs for Send
To insert a new IDN in the Send list, you can double-click on the End List line or
press the Insert key when the focus is on any line. The new IDN will be inserted
above the line focus is on.
To edit an existing IDN in the Send list, you can double-click on the entry or press
the Enter key.
The Insert IDN box shown below appears.
The SRS: information must be entered in order to proceed.

You can choose an IDN from any of the four IDN buttons or enter one from the
range 1 to 65535 or S1 to S32767 or P0 to P32767 in the Number: field.
If the number you entered is located in any of the IDN lists, a name will appear in
the Name: field and a value will appear in the Length: field.
If the number is not found in any of the IDN lists, no name appears in the Name:
field and you must enter the length in the Length: field.
The Element: field defaults to operation data and indicates the SERCOS element
to use. You can change this to attribute, minimum, maximum, or data from the
drop down list.
Min: displays the minimum value allowed for the selected IDN.
Units: displays the units used with the selected IDN.
Max: displays the maximum value allowed for the selected IDN.
The IDN Data box allows you to enter the value within the minimum/maximum
range given.

Click OK to place the data into the Send List. Click Cancel to exit without saving
any data.
Execute Procedure Command
The Online | Execute Procedure CMD Command Function (PCF) allows you to
select and execute SERCOS procedure commands.
The Slot/Ring/Slave Information must be entered in order to proceed. If you have
selected a slave in SERCOS setup, it will appear in the SRS: box. You can choose
one from the drop down list.
The System PCFs and the Drive PCFs buttons hold lists of PCFs from the system
file or the drive file respectively. Select a PCF (IDN) from a list or enter one. It
will be displayed in the Number: box. The name appears in the Name: box.
Once the PCF has been entered, the Execute button is active. Click it to send the
PCF IDN to the drive and begin the procedure. The progress of the procedure will
be noted to the right of the Execute button.
The Execute button converts to a Cancel button when progress begins.

Ring State
By using Online | Ring State... you can read the State Information shown below
for a ring.
The Version: represents the version number of the firmware on the SERCOS mod-
ule.
The Last Completed Phase: gives the phase number including whether the ladder
is halted after phase 2.
The Ring Error State: displays one of the ring error numbers shown below if one
occurs.
ERR# Description What to do/check

0 No error
3 Axis is not initialized, is not a SER- SERCOS board in correct slot
COS axis, or the slot/ring/slave speci- SR structure members correct
fication is incorrect.
17 The SERCOS module did not receive Check connection
an expected AT response. Cable could
be disconnected.
20 Phase 0 detected that the ring is not Check connection
complete. Ensure drive is turned on
65 Error occurred calculating when MDT Too many slaves on one ring
should occur. One or more drives cannot accom-
modate required MDT
66 Error occurred calculating when drive Too many slaves on one ring
data valid. One or more drives cannot accom-
modate command times
67 Error occurred calculating when Too many slaves on one ring
feedback data valid. One or more drives cannot accom-
modate feedback capture times
68 Error occurred calculating total time Too many slaves on one ring
required for communication cycle. Cyclic data on slaves too long
Update rate too fast
69 Error occurred calculating cyclic data Too many slaves on one ring
memory for SERCON processor. Cyclic data on slaves too long
memory for internal memory map. Cyclic data on slaves too long
71 Error occurred calculating service Too many slaves on one ring
channel memory map. Cyclic data on slaves too long
74 CPU on SERCOS module has too Too many slaves on one ring
many tasks during update. Cyclic data on slaves too long
128 Slave error occurred. Read SERR SLV output contains slave number
output to identify error. The SLV IDN output contains the IDN
output indicates the slave number. transfer that caused the error
SERR output contains the drive
generated error number
Read Drive diagnostic IDN 95
136 Individual slave will not respond. The Address switch on drive does not
SLV output indicates the slave match slave number
number. Baud rate switch on drive does not
match rate in ring definition
SLV output contains slave number
that does not respond
144 Individual slave cannot carry out a SLV output contains slave number
Procedure Command Function. The IDN output contains the Procedure
SLV output indicates the slave Command Function that caused the
number. error
For IDN = 127, read IDN 22 to
read list of IDNs still required by the
drive
drive
The Slave Number: can be 1 to 8 when using a PiC or standalone MCC or 1-32
when using an MMC for PC CPU.
The IDN: is either a S (system) or P (product) IDN number.
The Slave Error: holds the SERR if one occurs.
Status: provides current information on the status of the ring.
Selecting the Update button updates the ring data in the box.
Slave Status/Control
In SERCOS, there is a status word from each slave to the control and there is a
control word from the control to each slave. You can read the data in each word
using the Online | Slave Status/Control command that brings up the box shown
below.
The Control section displays the control word data continuously. The three lines
for the Drive: tell whether it’s on or off, enabled or not, halted or restarted. The
Operation Mode: indicates which mode is in effect. The Realtime Bits indicate
whether they are on or off. The word Value: is displayed in hex.
The Status section displays the status word data continuously. The Drive: line tells
whether the drive is ready or not, the logic is ready, and the power is active or not.
The Error: line reports on whether or not an error has occurred. The Operation
Mode: indicates which mode is in effect. The Realtime Bits indicate whether they
are on or off. The word Value: is displayed in hex.

IDN Lists
There are lists of IDNs for the system, the drive, the cyclic data, the startup, the
system PCFs, and the drive PCFs. While working in SERCOS setup, there are sev-
eral dialog boxes that allow you to access these lists of IDNs. You can also view
the system and drive IDN lists from the View menu.
Options for IDN Display

There is an Options command found in the View menu in SERCOS setup. It
allows you to choose how IDN numbers (1 to 65635) will be displayed. There are
two groups of IDN numbers:
• The P group is specific to the drive manufacturer’s product. They range
from 32768 to 65635 or P0 to P32767.
• The S group is defined by the SERCOS specification. They range from 1 to
32767 or S1 to S32767.
You can choose to display IDNs with the P and S format (default) or with numbers
only.
Note: Not all drive manufacturers support the P and S format.
When the Display with P and S option is selected, if you enter an IDN number
without the letter prefix, it will be added for you when you tab off of the IDN field.
When the Display as Number option is selected, if you enter an IDN number with
the letter prefix, it will be converted to the number only when you tab off the IDN
field.
After selecting the IDN display format you want, choose OK to accept your format
and close the dialog box. If you choose Apply, your format will be applied but the
dialog box does not close.

IDN Lists
The system IDN list appears when you click on the System IDNs button in a dia-
log box or choose View | View System IDN from the menu.
If under View | Options in SERCOS setup, Display with P and S is chosen, the
System IDNs are identified with an S preceding the IDN number.
If Display as Number is chosen, then the system IDNs are numbered from 1 to
32767.
Clicking on the Number column sorts the list by number; clicking on the Name
column sorts the list by name. Also, the columns will toggle between ascending
and descending order.
You can use the Find Name String button to bring up an IDN Search box.
When you click on the Drive IDNs button in a dialog box, it displays a list of IDNs
that you uploaded from the drive. You can sort by number or name, toggle the sort
order, search by name, and print this drive IDN list.
When you click on the Cyclic Data IDNs button in a dialog box, it displays a list
of IDNs that you entered as cyclic data.
The Startup IDNs button in a dialog box displays a list of IDNs you entered for
startup.

Finding a Specific IDN in an IDN List
When viewing an IDN list, you can use the Find Name String dialog box to help
you locate a specific IDN. If you know the name or part of the name of the IDN
you want to search for, the Find Name String dialog locates the IDNs that match
your search criteria quickly and easily.
To find specific text in an IDN list, follow these steps:

1. Click the Find Name String button on the IDN list you are viewing. This will
display the box above.
2. Type the desired text to search for in the field labeled Find Name String:.
3. Select the direction you wish to search, Forward or Backward, from the cur-
rently highlighted IDN.
4. Click the Find/Next button to begin the search.
5. If a matching IDN is found, the IDN number is highlighted. To search again for
another match, click the Find/Next button again.
6. The most recently searched for names will appear in the drop down list.
Printing IDNs from an IDN list

When viewing an IDN List, you can use the IDN printing dialog to print the IDN
list.
To print an IDN list, follow these steps:

1. Click the Print button on the IDN list you are viewing. This displays the IDN
printing box shown above.
2. Select Brief Listing to print the IDN number, name, and data for all of the
IDNs in the list.
3. Select Full Listing to print all the IDN elements for all the IDNs in the list.
4. Click OK. This will display the Print dialog for your default printer.
Viewing Variable Length Data from an IDN List

Some IDNs in IDN lists have variable length operation data. This is indicated by
the word Variable appearing in the Operation Data column of the list. (S00018 is
an example.)
To view this data you must use the Variable Operation Data dialog box shown
below.
To view variable length operation data, follow these steps:

1. Right-click on the IDN with variable data in the IDN list. This will display a
popup menu. Select the View Variable Data item from this menu. This brings
up the Variable Operation Data box shown above.
2. The variable length Operation Data is listed in this dialog under the heading
Data.
3. You will notice a column to the left of the data labeled Data Index. This is just
a column that numbers the data items in the displayed list. It is not a part of the
Operation Data itself.
4. When finished, click OK to close the dialog box.
Specifying the SRS for Viewing the Drive IDN List

In order to view the Drive IDN List from the View menu on the menu bar, you
must indicate which drive you want.

Using the Request Slot/Ring/Slave dialog box, select the appropriate SRS which
uniquely identifies the desired drive.
To specify the SRS, follow these steps:

1. From SERCOS Setup, select View | View Drive IDN from the menu.
2. The Request Slot/Ring/Slave box shown above appears. You specify which
drive by selecting the appropriate SRS from the drop down list provided.
3. After choosing the SRS, click the OK button. The Drive IDN list for the speci-
fied drive will be displayed.
Troubleshooting SERCOS
Here are a few tips on troubleshooting while working in SERCOS.

Communication Problems
• Communication phase 4 must be completed before you can begin to con-

trol.
• The ERR output of the SC_INIT function block can provide information
on what went wrong during communication.
• If SC_INIT executes correctly with no errors, you should check for ring
errors next using the SCR_ERR function or within SERCOS setup using
the Online | Ring State command. Information reported here indicates
problems with moving through the communication phases.
• Check the phase number completed by using the SCR_PHAS function or
within SERCOS setup using the Online | Ring State command.
• If the drive will not advance into phase 3 or 4, it is possible that there are
IDNs that need to be defined. The IDNs that have not yet been defined are
contained in IDN 22 and 23. This list can be read from the ladder using the
SCA_RECV or SCS_RECV function or within SERCOS setup using the
Online | Receive Idn command.

Control Problems
• If the loop will not close, you can read the status of the drive using the
SCA_STAT or SCS_STAT function or the Online | Slave Status/Control
command. The control word has 16 bits. Bits 1 and 2 indicate the state of
power stage the drive is in. Bits 8, 9, and 10 indicate the operation mode.
You may also want to read IDNs 11, 12, and 13.
• A loss of feedback error may occur if the ring has not reached phase 4.
• If the drive does not accept IDNs, the drive may not support the feature.
Check the SERR output of a SERCOS function to learn more.
• Use SCS_ or SCA_RECV functions to read IDN 95. IDN 95 contains a text
diagnostic message with basic error conditions reported from the drive.
• IDN 11, 12, and 13 are diagnostic IDNs that report common control prob-
lems. Consult your drive documentation for the bit definition of these
IDNs.

CHAPTER 8 Working With Tasks and UDFBs
UDFBs
The User Defined Function Block (UDFB) feature allows you to convert the logic
in a ladder module (.LDO) into an individual function block. The name you give to
the LDO becomes the name of the UDFB. The UDFB is inserted into a library file
(.LIB) and appears in the list of available functions. It can then be used in a net-
work of any module you create.
Using the UDFB feature results in an application program that is better organized,
more readable, and easier to maintain. Some ways UDFBs can be used include:
• UDFBs can segregate the logic for a section of an application program
(i.e. diagnostics, fault logging, etc.).
• Custom functions with a higher level of functionality can be created
(i.e. analog output with ramping).
• A single UDFB can replace in-line programming of repetitive machine
functions
(i.e. axis one fault control, axis two fault control, etc.).
The UDFB follows the same conventions as the standard function blocks found in
PiCPro. It must be declared in the software declarations table when it is used in the
network of a module. You assign a name to it when it is declared.
Creating a UDFB
Briefly, you will do the following to create and use a UDFB.
1. Open a new ladder diagram and enter ladder logic which will accomplish what
you want the UDFB to do.
2. Mark the variables that you want to appear as labels in the UDFB template as
inputs or outputs in the software declarations table.
3. Compile the UDFB.
4. Open another ladder diagram in which you want to use the UDFB and insert
the UDFB from the Function list into a network. It will have to be declared in
the software declarations table and given a name (CITY in the example below.)
Ladder Structured Text
<<INSTANCE NAME>>:MICE(EN:=<<BOOL>>,
,IN1:=<<BOOL>>, IN2:=<<BOOL>>, IN_N:=<<NUMERIC>>,
OK => <<BOOL>>;
Working With Tasks and UDFBs 377

The EN input and the OK output are required. The remaining inputs and outputs
are determined by you when creating the module.
Naming the UDFB
The name of the LDO module will become the name of the UDFB when you com-
pile it. If you have not saved the module previously, you will be prompted to enter
the name at compile time. If the name is more than eight characters, it will be trun-
cated. Be sure to choose a name that does not already exist in another module you
may want to convert to a UDFB or in a standard function/function block supplied
by PiCPro.
Scanning UDFB Logic
The logic contained in the UDFB is scanned regardless of whether or not there is
power flow into the EN input. Therefore, in the majority of cases, you will want to
include the following lines of logic in your UDFB module.
Ladder Structured Text
IF NOT EN THEN
RETURN;
END_IF;
OK :=1;
This ensures that you will always have control of the EN and OK in any module
you use the function block in. It causes the program to jump to the end of the
UDFB logic if the EN is not set. This prevents the logic in the function block from
being scanned unless the EN is set.
Note the wire in the empty network #N with the JUMPEND label. PiCPro does not
allow empty networks. A horizontal wire was added so that the empty network
error is not generated.
The only situation where you would not want to control the EN and OK in this
manner is if you create a UDFB which would need to work when the EN is not set.
The TOF (timer off) standard function block is an example. The function block
continues to execute after the EN is reset.
378 Working With Tasks and UDFBs

Contents of the UDFB LDO module
Only the logic you want handled by the UDFB should be included in the module.
The size of any UDFB can be up to 64K. The size of your UDFB will be listed in
the information window when you compile.
Size of UDFB Libraries
You may have one or multiple UDFB libraries. Because PiCPro copies the entire
UDFB library whenever you use the Compile | UDFB command during program
development, it is recommended that you keep the size of the UDFB library under
100K. This will improve the time it takes to build UDFBs.
The UDFB library will appear under the Ladder | Functions | USER menus. The
individual UDFBs will appear in a fly-out from the library. In the example below
the function block named MICE is located in the library called CATS.
The UDFB will also appear in the list in the Function toolbar.

Data Handling in UDFBs
Data is passed to the UDFB from its inputs in one of two ways depending on its
type.
• If the internal input is any variable other than a structure, string, or an array,
then the value of the external input is passed to the UDFB. This value is
acted upon internally in the UDFB leaving the external variable
unchanged.
• If the internal input is a structure, string, or an array, then a pointer is
passed to the UDFB. This pointer gives the location of the associated data
in the calling program. The data is acted upon outside the UDFB.
IMPORTANT
Data is copied and pointers are passed into a UDFB only when there is
power flow to the first input (EN). String, array, or structure pointers
within a UDFB must not be accessed until power flow to the EN has
occurred.
Compiling the UDFB

When you have entered all your logic for the UDFB in your ladder, marked all the
Inputs and Outputs that you want to appear in the UDFB template, and saved the
module, you can compile the UDFB and place it in a library. Select Compile |
UDFB from the menu.
Note: If you are recompiling a function that was created earlier, you must place the
function in the same library where it was originally located. You cannot select a
new library location. The UDFB Library Name: box will be disabled (grayed
out).
Editing a UDFB
You can edit the UDFB either on-line or off-line depending on the types of
changes you are making. PiCPro will determine this and make the appropriate
options available in the Compile Options box.
Off-Line Editing
When you are doing off-line editing, the first two choices are available.
The Compile and place in library option changes the module in the library and
requires a full download. If you add any function/blocks and/or declarations that
require initializations, you must compile the UDFB and do a full download. The
scan is stopped.

The Compile debug version and place in library option also changes the module
in the library and requires a full download with the scan stopped. But it allows you
to create a debug version of the UDFB. Creating a debug version adds additional
data bits (40), data bytes (80), and function/jump links (20) to each instance of the
UDFB for more extensive on-line changes.
Note: Minor changes that do not add things like new functions,
declarations, or jump labels can be made on-line without creating a debug version.
On-Line Editing
When you are doing on-line editing, the third choice becomes available.
The Patch the scanning function option allows you to make an on-line edit
change to this UDFB. This does not change the version of the module in the
library, but does allow you to continue to animate and do on-line editing.
Viewing a UDFB
When you are working in the ladder in which you have entered your UDFB (called
the parent ladder), you can view the UDFB ladder by selecting View | UDFB/Task
from the menu or by right clicking on the function in the ladder and then selecting
View.
Viewing the Parent Ladder
When you are working in the UDFB ladder, you can view the parent ladder by
selecting View | Parent from the menu or by right clicking anywhere in the ladder
and selecting View | Parent Ladder.

UDFB Software Declarations
Variables of any type with optional initial values may be declared for use in the
UDFB module. However, variables cannot be external, retained, global, or discrete
I/O.
Note: If you need to add discrete I/O in order to test the UDFB module, be sure to
remove them from the module and the software declarations table before compil-
ing the UDFB.
The variables which will become the inputs for the UDFB may be any data type
except function blocks.
The variables which will become the outputs for the UDFB may be any data type
except function blocks, structures, arrays, and strings.
Inputs that are structures, arrays, and strings all pass pointers to the UDFB and,
therefore, cannot be used as outputs. It is possible, however, to design a function
block in which the result of the function block being executed ends up in a struc-
ture, array, or string used as an input.
Naming the Variables
Up to the first four characters you assign to the UDFB input and output variables
in the software declarations table will become the labels in the UDFB template.
Software Declarations Entries Example UDFB Template
Order of UDFB Inputs and Outputs

The first input and the first output will always become the EN (enable) and the OK
of the function block. Their data type is boolean. It is recommended that they
appear before any other UDFB inputs and outputs in the software declarations
table.
Additional UDFB inputs and outputs should be entered in the software declara-
tions table in the order you want them to appear in the function block template.
The inputs appear on the left side of the template and the outputs on the right.

Number of UDFB Inputs and Outputs
The maximum number of inputs or outputs for a UDFB is 64. It is recommended
that you keep the number to a minimum (under 16). More can be declared if neces-
sary, but transferring all the inputs and outputs to and from a function block does
use scan time. There is also the constraint of the 255 element matrix to consider. If
you have a large number of inputs, you may want to enter them as a structure using
just one input.
Marking UDFB Inputs and Outputs
You must mark all the inputs and outputs for the function block in the software
declarations table using the attribute tool. When you compile your UDFB ladder,
these inputs and outputs will appear on the UDFB template in the order you have
entered them. Remember that the EN input and the OK output must be entered in
the software declarations table before any other UDFB inputs or outputs. Their
data type is boolean.
To mark a variable as an input or output in the software declarations table:
1. Place the focus anywhere in the row of the software declarations table that
holds the variable you want to mark.
• Select Tools | Modify Attributes | Variable In or Variable Out from the
menu.
• Right-click Modify Attributes | Variable In or Variable Out.
• With focus on a cell in the attribute column, type I or O.
All of these methods will enter the I or O symbol in the Attribute column.
Tasks
A task is a programming tool that allows you to create a module (.LDO) that will
execute at periodic intervals or on the rising or falling edge of a boolean variable
from within your main LDO. This provides the ability to schedule events from
your main LDO.
WARNING
Use discretion when programming tasks in your LDO. You must have
a thorough understanding of how they work and what effect they will
have on your program to ensure that your program will execute
properly.
Tasks are programmed similar to UDFBs. You convert the task LDO into a func-
tion block that is stored in a library. Whenever PiCPro is executed, the task will be
available through this library under the Functions menu. It can then be used in a
network of your main LDO.
Comparing UDFBs and Tasks
There are some differences between tasks and UDFBs.
• Tasks can access I/O modules located in the main rack of the control.
UDFBs cannot.
• A task cannot be programmed within another task or within a UDFB. A
UDFB can be nested within another UDFB.
• The on-line edit feature cannot be used in a network containing a task.
• Forcing is not allowed in a task.
• When you insert tasks into your main LDO, the function block template is
always the same. You cannot program any inputs or outputs for a task.
They are predefined.
Types of Tasks
There are three types of tasks available.
1. Servo Interrupt Tasks - triggered on the 1, 2, 4, 8, or 16 millisecond servo time
tick.
2. Hardware Interrupt Tasks - triggered on a hardware event.
3. System Tick Tasks - triggered on a multiple of the 10 millisecond system tick
task.
Note: Variables 44 through 48 are available to be used with servo tasks using the
READ_SV and WRITE_SV functions. Refer to the Function/Function Block Ref-
erence Guide for information on these variables.
When multiple tasks are declared in the main LDO, the task that is declared first in
the software declarations table is executed first.
When a task is triggered in the main LDO, the following hierarchy occurs.
• System tasks will interrupt the main LDO.
• Hardware tasks will interrupt system tasks and the main LDO.
• Servo tasks will interrupt hardware tasks, system tasks, and the main LDO.

Using the Task Template
Every task you create and subsequently use in your main LDO will use the tem-
plate shown below. FILE will be replaced with the name of your task LDO file
when you compile the task. You will provide a NAME when you declare the func-
tion block in the software declarations table of your main LDO.
TASK Template Description

Inputs: EN (BOOL) - enables execution
SERV (TIME) - 1, 2, 4, 8, or 16ms constant for servo task.
Enter in the T# format.
HDWR (BOOL) - I/O point used to trigger the hardware
interrupt task must be programmed as Data In or Data
Inverted which inverts a boolean input. Never program a
wire or contact to this BOOL input.
SYST (TIME) - constant or variable based on 10ms system
time tick. If a time is entered that is not a multiple of 10, it
will be rounded up to the next 10ms increment. Time must
be less than 10.92 minutes. Enter in the T# format.
Outputs: OK (BOOL) - set if EN is on and the TASK is successfully
installed. Does not indicate whether or not the task has
run.
FAIL (BOOL) - set if ERR is not equal to zero.
ERR (INT) - Zero if no error, non-zero if an error.
Structured Text
<<INSTANCE NAME>>:FILE(EN:= <<BOOL>>,

SERV:= <<TIME>>, HDWR:= <<BOOL>>, SYST:= <<TIME>>,
OK => <<BOOL>>; FAIL => <<BOOL>>, ERR => <<INT>>;
The EN must be on for a task to run. The SERV, HDWR, and SYST inputs are
mutually exclusive. Only one can be connected at a time depending on whether
your task is a servo, hardware, or system interrupt task.
Errors at the ERR output of the Task
The errors that can appear at the ERR output are:
ERR # Description
1 Task installation failure
2 The time tick requested is larger than 10.92 minutes.
3 The servo task is faster than the servo interrupt time.

Using Functions from the I/O and Motion Libraries
There are some rules that apply to functions from the standard I/O and Motion
libraries when working with tasks.
I/O Functions
Functions in these groups that access an I/O module must be called in the main
LDO or within the same task.
ANLGIN ANLGOUT JKTHERM READFDBK RTDTEMP

STEPPER
I/O functions in these groups can be called in the main LDO only.
COMM NETWORK
These I/O functions can be called in both the main LDO and the task LDO.
BAT_OK? PID IPACCEPT IPCLOSE IPCONN

IPHOSTID IPIP2NAM IPLISTEN IPNAM2IP IPREAD
IPRECV IPSEND IPSOCK IPWRITE
Motion Functions
These motion functions can only be called in the main LDO.
STRTSERV CAM_OUT MEASURE REGIST SCURVE

SC_START SCA_SEND SCA_RECV SCA_CLOS SCA_ACKR
SCA_REF SCA_ERST SCS_SEND SCS_RECV SCS_ACKR
SCS_REF SCA_PBIT SCA_RFIT
These motion functions may not interrupt each other, i.e. if one function is access-
ing a queue, a second function is not allowed to interrupt the first function and
access the same queue. If this occurs, the function in the interrupting task will not
execute and the OK will not be set.
DISTANCE POSITION VEL_END VEL_STRT GR_END

RATIOCAM RATIOPRO RATIOSLP RATIOSYN RATIO_GR
RATIO_RL REP_END SYN_END FAST_REF LAD_REF
IN_POS? NEWRATIO NEW_RATE ABRTALL ABRTMOVE
Q_AVAIL? Q_NUMBER FAST_QUE C_RESET E_RESET
PART_CLR PART_REF
These motion functions can be called in both the main LDO and any task LDO.
ACC_DEC CAPTINIT CAPTSTAT CLOSLOOP CLSLOOP?

COORD2RL C_ERRORS C_STOP E_ERRORS` E_STOP
E_STOP? HOLD HOLD_END OPENLOOP P_ERRORS
P_RESET RATIOSCL READ_SV READ_SV REF_DNE?
REF_END TME_ERR? TUNEREAD TUNEWRIT WRITE_SV
R_PERCEN SCR_CONT SCR_ERR SCR_PHASE SCS_CTRL
SCA_RCYC SCS_STAT SCA_WCYC RESUME RESMODE?

The STATUSSV motion function can only be called once because it does a read
and then clear of all but one status flag. After an event occurs, only the first read of
the status will recognize the corresponding flag.
Comparing Declaration Rules for Main and Task LDOs
There are rules for making hardware and software declarations in the main and
task LDOs.
Hardware Declarations
Description in Main LDO in Task LDO

Hardware module used in task LDO Yes Yes
Hardware module used in main LDO Yes No
Hardware module used in both LDOs Yes Yes
Software Declarations
Description in Main LDO in Task LDO

Hardware input used in task LDO No Yes
Hardware input used in main LDO Yes No
Hardware input used in both LDOs Yes Yes
Hardware output used in task LDO No Yes
Hardware output used in main LDO Yes No
Hardware output used in both LDOs Not allowed
Variable used in task LDO No Yes
Variable used in main LDO Yes No
Variable used in both LDOs Yes Yes (Mark
External*)
*Never mark with the External attribute in software declarations any direct I/O
used in the LDO.
Hardware modules and I/O points may be used in multiple task LDOs. They must
be declared in all task LDOs they are used in.

Creating a Task
Briefly, you will do the following to create and use a task.

1. Open a new ladder diagram and enter ladder logic which will accomplish what
you want the task to do.
2. Mark as External any variable in the software declarations table of the task
LDO that will be used in the task LDO and in the main LDO.
3. Compile the task.
4. Open another ladder diagram which will be the main LDO where you want to
run the task(s). Insert the task from the Function list into a network. It will have
to be declared in the software declarations table and given a name at that time.
5. Set up the type of interrupt (servo, hardware, or system) you want and when it
will run.
Before you begin to create a task program or use tasks in your main LDO, keep in
mind the following:
• Tasks can access I/O located in the main rack of the control. Declare any
hardware module whose I/O you use in a task in both the main LDO and in
the task LDO hardware declarations table. (In the main LDO, all hardware
modules must be declared whether the main LDO uses them or not. In the
task LDO, only the hardware modules used in the task LDO must be
declared in the task LDO.)
• Hardware outputs used in a task may not be used in the main LDO. Hard-
ware inputs may be used in a task and in the main LDO. Hardware inputs
and outputs used in one task may be used in other task(s). Declare them
only in the software declarations table of the LDO(s) they will be used in.
• Inputs are strobed at the beginning of a task. Outputs are strobed at the end
of a task.
Note: When the task is running, only the inputs and outputs in the task, not
the inputs and outputs in the main LDO, will be strobed.
• Do not use timer functions in a task.
• Tasks can be animated but cannot be forced or patched.
• Tasks cannot be programmed within another task or within a UDFB.
• If software data information in a task needs to be shared with other tasks,
declare it as External in the software declarations table of the task LDO.
This data must also be declared in the software declarations table of the
main LDO whether the main LDO uses it or not. In the main LDO, it is
never marked as External or Global.
Note: Never assign the External attribute to direct I/O used in the LDO.
• To ensure that the data to be transferred between LDOs is from the same
scan, interlock multiple externals, arrays, structures, and variables. This
can be done with semaphore flags.

•Hardware interrupts can come from the first input in each group of eight on
the digital input modules (numbers X.1, X.9, X.17, or X.25) or from the
fast input on the encoder/resolver modules. The fast inputs for a PiC CPU
must be numbered as X.1 for channel one, X.3 for channel two, X.5 for
channel three, and X.7 for channel four. X represents the slot number for
the module. The fast inputs for a standalone MMC or MMC for PC must be
numbered IFAUX#.1, IFAUX#.2, IFAUX#.3, and IFAUX#.4, where # rep-
resents slot number for standalone MMC and ASIU number for MMC for
PC.
• Servo interrupt tasks put the heaviest burden on system resources. Always
try to conserve system resources by using the appropriate task, i.e., do not
use a servo task when a system or hardware task can accomplish the same
thing.
Naming the Task
The name of the LDO module will become the name of the task when you compile
it. If you have not saved the module previously, you will be prompted to enter the
name at compile time. If the name is more than eight characters, it will be trun-
cated. Be sure to choose a name that does not already exist in another module you
may want to convert to a task or in a standard function/function block supplied by
PiCPro.
Task Hierarchy
When tasks are triggered in the main LDO, system tasks will interrupt the main
LDO: hardware tasks will interrupt system tasks and the main LDO; and servo
tasks will interrupt hardware tasks, system tasks, and the main LDO.
If there are multiple tasks of one type in the main LDO, the task that is declared
first in the software declarations table will execute first.

Priority Between the Main LDO, Hardware Tasks, and System Tasks

Priority Between the Main LDO, Hardware Tasks, and Servo Tasks

Interlocking Data in Tasks
Whenever data is exchanged between the main LDO and a task LDO, there is a
possibility of inaccurate data being transferred. This is dependent on when a task
interrupts the main LDO or interrupts a lower priority task accessing the same
data.
In order to preserve the integrity of the data that is being read/written, you need to
program an interlock between the main LDO and the task LDO. One method of
interlocking data is to use semaphore flags. A semaphore flag refers to a way of
communicating between the main LDO and a task LDO when a significant event
has occurred.
Setting up Semaphore Flags
In setting up semaphore flags, the main LDO energizes a LOCK flag which pre-
vents the task LDO from reading or writing data while data is being transferred to
or from the main LDO. After the data transfer is complete, the main LDO
de-energizes the LOCK flag and the task LDO is allowed to read or write the data.
There are two examples that follow. The first shows data being transferred from
the task LDO to the main LDO. The second shows the data being transferred from
the main LDO to the task LDO. In both examples the main LDO has control of the
data even though tasks of higher priority are accessing it.
Semaphore Flag Example 1 - Data Transfer from Task LDO to Main LDO
The MOVE function with a task output TO data structure is used in both the main
and task LDO. The TO structure acts as a buffer for the data transfer. The TO
structure is marked External (only in the task LDO software declarations table, not
the main LDO software declarations table) allowing that data to be used by both
the main and task LDOs.
In the Main LDO
When the MOVE function in the main LDO is enabled, the following sequence of
events occurs.
1. TO.LOCK is energized by moving LOCK into TO.LOCK.
2. TO.COUNT is moved into COUNT.
3. TO.LOCK is de-energized by moving UNLOCK into TO.LOCK.

The variables in the software declarations table of the main LDO are:
Variable Definition
TO Task output structure
.LOCK Semaphore flag
.COUNT Count variable to be written by the task LDO
COUNT Main LDO count variable
LOCK IN1 to MOVE function, set to 1
UNLOCK IN3 to MOVE function, set to 0
The declarations in the main LDO software declarations table are:
In the Task LDO

In the task LDO, the following sequence of events occurs.
1. If TO.LOCK is off, then move the data (Step 2).
If TO.LOCK is on, do not move the data.
2. T_COUNT is moved into TO.COUNT.
The variables in the software declarations table of the task LDO are:
Variable Definition
TO Task output structure
.COUNT Count variable to write to the main LDO
T_COUNT Task variable to be transferred into COUNT in main
LDO

The declarations in the task LDO software declarations table are:
Semaphore Flag Example 2 - Data Transfer from Main LDO to Task LDO
The MOVE function with a task input TI data structure is used in both the main
and task LDO. The TI structure acts as a buffer for the data transfer. The TI struc-
ture is marked External (only in the task LDO software declarations table, not the
main LDO software declarations table) allowing that data to be used by both the
main and task LDOs.
In the Main LDO
When the MOVE function in the main LDO is enabled, the following sequence of
events occurs.
1. TI.LOCK is energized by moving LOCK into TI.LOCK.
2. SETPOINT is moved into TI.STPT.
3. TI.LOCK is de-energized by moving UNLOCK into TI.LOCK.

Variable Definition
TI Task input structure
.COUNT Setpoint to be read by the task LDO
SETPOINT Main LDO setpoint
LOCK IN1 to MOVE function, set to 1
UNLOCK IN3 to MOVE function, set to 0
In the Task LDO

In the task LDO, the following sequence of events occurs.
1. If TI.LOCK is off, then move the data (Step 2).
If TI.LOCK is on, do not move the data.
2. TI.STPT is moved into T_STPT.

Variable Definition
TI Task input structure
.STPT Setpoint to be read by the task LDO
T_STPT Main LDO setpoint

CHAPTER 9 DeviceNet - Ethernet - TCP/IP
G&L DeviceNet Configuration Software
The diagram below illustrates a typical DeviceNet set up.

DeviceNet Scanner Module
PC PiC
Software
Download .LDO File to PiC PiCPro DeviceNet
PiCPro Port
Configuration (.UCT) File Port
exported to PiCPro
DeviceNet Conf. Software Download .UCP File to Config.
Personality File (.UCP) DeviceNet Scanner Module
Port
DeviceNet Network
Overview of setting up a DeviceNet Network

1. Use the G&L DeviceNet Configuration Software to provide information about
your DeviceNet system. This information includes a description of input and
output data associated with each node, tags (variable names) for this data, and
the address of each node. (See DeviceNet procedure that follows this section.)
2. Always use the “export” command of the G&L DeviceNet Configuration Soft-
ware to generate two files in your workstation:
Current configuration file (.UCT) for PiCPro.
Current personality file (.UCP) for the DeviceNet scanner module.
For PiC and standalone MMC:
3. Use the G&L DeviceNet Configuration Software to download the personality
file to the DeviceNet scanner module. Be sure the PiCPro cable is connected to
the Configuration Port.*
4. Design your ladder program using PiCPro (refer to the fieldbus function/func-
tion blocks in the Function/Function Block Reference Guide and the Theory of
Operation section for your DeviceNet Scanner Module in the appropriate
Hardware Manual).
Typically DeviceNet communication is opened with a FB_OPN function
block. After this is done FB_STA is used to continually monitor for possible
error conditions and to update the on-line (ONLI) status flag. Once the network
is on-line the FB_SND and FB_RCV functions are used to transfer variables to
and from the memory image in the DeviceNet Scanner Module. The
DeviceNet Scanner Module in turn transfers this memory image from and to
actual I/O hardware associated with the tagged variables.
DeviceNet - Ethernet - TCP/IP 397

Once a DeviceNet network is properly on-line, only severe electrical noise or a
hardware error will cause the network to go off-line. Detection of a negative
transition of the on-line status flag (from FB_STA) can be used as a warning
that data from and to the DeviceNet network may no longer be correct. The
value of each device status byte (described at the end of this chapter) can serve
as a similar warning. In applications where DeviceNet data affects safety, these
warnings should be used by the ladder for taking appropriate action.
5. Use PiCPro to download the ladder file to the control. Be sure the PiCPro cable
is connected to the PiCPro Port.*
6. Connect the DeviceNet cable to the DeviceNet Port on the DeviceNet scanner
module.
*Note: Before downloading the personality file, make sure the ladder scan in the
CPU is stopped. The PiCPro cable from your workstation is first used to download
the personality file; this cable must be connected to the Configuration Port on the
DeviceNet scanner module. You then need to connect this cable to the PiCPro Port
on the CPU module in order to download the ladder.
For MMC for PC:
Use the PiCPro Download Hex feature to load the personality file via local or
remote Ethernet. There are no cables or ports to connect directly. However, the lad-
der scan in the MMC for PC must be stopped before downloading.
Procedure for using the G&L DeviceNet Configuration Software
There are several ways to accomplish the following. Once you become familiar
with the operations, you can use whichever method you prefer. Note: Additional
information can be obtained by selecting Help from the menu or by using the Help
button in a given dialog.
1. Select the G&L DeviceNet Configuration Software icon to get to the applica-
tion window.
2. Select File | New from the menu to bring up your working screen. A window
will appear with the heading GLDNCFG1. This is the default name for your
configuration files. It should be renamed when saving the file to match the base
name of your ladder file.
3. Select the Network (Network Configuration) symbol and right-click to bring
up a menu. Select Properties to bring up the Node Properties menu. This
allows you to change the name and description of your DeviceNet system. It is
recommended that you use the name of your configuration file.
Select OK to exit this menu.
4. If the symbol for the G&L DeviceNet scanner module is not already displayed,
right-click to bring up another menu and select New. This will display the sym-
bol for the scanner module. Right-click on this symbol to bring up a menu and
select Properties. A menu with five tabs appears (only the first three are pres-
ently used). Enter appropriate information.
398 DeviceNet - Ethernet - TCP/IP

• General TAB
Enter a name for the scanner module or leave it as the default name
Scanner1. Check “Assign network parameters” in order to program the fol-
lowing:
• Always leave MAC ID at 0.
• Select appropriate baud rate (125K bps, 250K bps, or 500K bps).
• Leave the Scan Interval at the default setting of 0 for the fastest update
rate possible for this scanner.
• Select Apply.
• I/O TAB
(Not used for the G&L scanner module.)
• Tag TAB
You will come back to this tab after the other DeviceNet nodes are entered.
For now, select OK.
5. With the G&L Scanner symbol highlighted, right-click to bring up a menu and
select New. This brings up a Select New Node menu.
Select Device and select OK to enter a Device or node symbol.
Right-click on this to bring up a menu and select Properties.
A menu with three tabs appears.
• Identity TAB
Assign a “Name” and a “Description”.
Select a MAC ID for this slave node.
Other information is optional.
• I/O TAB
Select either “Polled” or “Strobed”.
If Polled is selected, enter the number of “Input” and/or “Output” bytes
associated with the node. Leave Update Interval blank.
If Strobed is selected, enter the number of bytes input/bools associated with
the node. (Strobed outputs are not supported, COS and Cyclic are not sup-
ported.)
Select Apply.
• Tag TAB
Select New and then Edit. Another menu with two tabs appears.
Names TAB
Assign a Tag Name for an object (variable) in the DeviceNet node. Use
the same name as used when defining the variable in your ladder with
PiCPro.
Tag TAB
Select the appropriate I/O Type and select a Data Type to match the data
type for that variable in your ladder.
Select OK to go back one level and select OK to get to the node symbol.
6. Repeat Step 5 for each DeviceNet slave node in your network.
7. After all nodes are entered, select the G&L Scanner symbol to highlight it.
Right-click to bring up the Node Properties menu again.
Now select the Tags Tab.
Select New and then Edit. A Tag Properties menu appears allowing you to
assign a variable name for the status of each node you defined.
Under the Tag Tab, select Device x Status where x is the MAC ID of the
desired node. Also, select WORD for Data Type. A description of the Device
Status Word is shown at the end of this topic.
8. After assigning a device status variable for each node, go back two levels.
Select the G&L Scanner symbol.
Right-click to bring up a menu.
Select Export to bring up the Save As menu. Use the same base file name and
the same directory as used for your ladder.
When you Save, several files will be saved with the same base name but with
different extensions. One of these files (.UCT) will be used by PiCPro when
downloading your ladder. Another file (.UCP) will be used by this G&L
DeviceNet Configuration Software when downloading the personality file to
the DeviceNet scanner module.
9. For PiC and standalone MMC CPUs, after exiting the Save As menu, right-
click on the G&L Scanner symbol to bring up a menu. This time select Down-
load. You must have the PiCPro cable connected between your workstation
and the configuration port on the DeviceNet scanner module. Select the Down-
load button and wait for the operation to be completed.
Note: If the Download dialog indicates the Baud Rate as “Not Connected”,
first check for proper cabling. Then, be sure the ladder scan in the CPU is
stopped.
For the MMC for PC CPUs, use PiCPro Professional Edition, select Online |
Download Hex. Enter the name of the personality file (.ucp) and select the
port as MMC for PC. More information on this can be found in Chapter 3.
10. Return to the application screen and save your file before exiting.
Note: The on-line configuration option and EDS files are not supported in the
G&L DeviceNet Configuration Software.
Device Status Word
A 16-bit device status word for each slave device can optionally be tagged.
(Refer back to step 7 of the procedure for using the G&L DeviceNet Configuration
Software.) The word has the following format:
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
(Reserved) IDLE STATUS
STATUS Device status code (see next table)

IDLE Received idle, the device is configured to send one or more bytes of
input data but is currently sending zero-length (idle) input messages

Device Status Code
Status Description Status Description
00h (Reserved) 0Dh Invalid I/O connection 1 input size

01h Device idle (not being scanned) 0Eh Error reading I/O connection 1 input
size
02h Device being scanned 0Fh Invalid I/O connection 1 output size
03h Device timed-out 10h Error reading I/O connection 1 output
size
04h UCMM connection error 11h Invalid I/O connection 2 input size
05h Master/Slave connection set is busy 12h Error reading I/O connection 2 input
size
06h Error allocating Master/Slave con- 13h Invalid I/O connection 2 output size
nection set
07h Invalid vendor ID 14h Error reading I/O connection 2 output
size
08h Error reading vendor ID 15h Error setting I/O connection 1 packet
09h Invalid device type 16h Error setting I/O connection 2 packet
0Ah Error reading device type 17h Master/Slave connection set sync
fault
0Bh Invalid product code 18h Error setting Production Inhibit Time
0Ch Error reading product code 19h-FFh (Reserved)
Ethernet - TCP/IP Configurator
This section covers the configuration of an Ethernet network for PiC and standal-
one MMC. This procedure is not needed when using an MMC for PC.
Overview of setting up an Ethernet Network
The following steps summarize what you need to do to set up an Ethernet network.
1. Use the Ethernet - TCP/IP Configurator within PiCPro to configure your sys-
tem. (See procedure at the end of this section.)
2. Send the configuration information to the Ethernet - TCP/IP module using the
PiCPro cable connected to the RS232 Com 2 port on the module.
3. Always cycle power after changing Ethernet settings.
4. Design your ladder program using PiCPro.
5. Download the ladder file to the control using the PiCPro cable connected to the
PiCPro Port.*

6. Make your connections to your Ethernet - TCP/IP system.
*Note: The PiCPro cable is first used to download the configuration file by con-
necting it to the RS232 Com 2 port on the Ethernet - TCP/IP module. You then
need to connect it to the PiCPro Port on the CPU module in order to download the
ladder.
Block Diagram of Ethernet - TCP/IP Setup
Ethernet - TCP/IP Module
PC Download .TCP File to PiC

Software
Ethernet - TCP/IP Module
TCP/IP Configurator
Configuration File (.tcp) RS232
PiCPro COM 2
Download .LDO File to PiC Port
PiCPro
Ladder File (.ldo)
Ethernet Network
Ethernet - TCP/IP Configuration Procedure

To set up an Ethernet – TCP/IP network, you will need to use the Ethernet –
TCP\IP Configurator.

1. With PiCPro running on your workstation, select Online | Configure TCP/IP .
. . from the menu and the following dialog appears. If you do not have all the
information needed for this dialog box, see your network administrator.
Animation of your program is halted when the configurator is chosen. All entries
are blank except the Ethernet Port and Comm Port entries.
2. Enter the information in the following entry fields.
• IP Address
Enter the IP address of the host in dotted decimal notation. Note: If DHCP
is checked, you do not have to enter an address here.
• Subnet mask
Enter the Subnet mask in dotted decimal notation. Note: If DHCP is
checked, you do not have to enter an address here.
• Ethernet Port
There are three choices for the PiC900 Ethernet module: UTP (default),
BNC, and AUI. There is one choice for the standalone MMC Ethernet
module: UTP.
• Name of this host
Enter the name of the PiC or standalone MMC host.
• Gateway
Enter the gateway node by name if a name server is present. Otherwise,
enter it by address in dotted decimal notation.
• Domain name
Enter the domain name of this host.

• Domain name server
Enter the address of the domain name server in dotted decimal notation.
• Open
Choosing the Open button allows you to open a previously saved .tcp file.
• Save
Choosing the Save button saves the TCP/IP configuration data to a .tcp file.
• Comm Port
Enter the workstation communications port you want to use from the drop
down list. The list can hold up to nine ports depending on how many are
available on your workstation. Currently the baud rate is set at 9600.
• DHCP
By checking the DHCP check box, the module asks for an IP address and
other information. If this data is not available over the network, the infor-
mation you entered will be used.
• Set Values
Choosing the Set values button sends the entered data to the Ethernet -
TCP/IP module via the PiCPro cable connected from the workstation to the
RS232 COM2 port on the module.
• Get Values
Choosing the Get values button retrieves the data from the Ethernet - TCP/
IP module via the PiCPro Cable connected from the workstation to the
RS232 COM2 port on the module. The data fills in the appropriate fields in
the configurator dialog box.
3. After all the information is entered, choose Save button to save your configura-
tion data to a *.tcp file.
4. Connect the PiCPro cable between your workstation and the COM2 port on the
Ethernet - TCP/IP module.
5. Choose the Set values button to send the entered data to the Ethernet - TCP/IP
module.
6. Cycle power.

CHAPTER 10 G&L Profibus Configuration Software
The diagram below illustrates a typical Profibus set up.
Profibus Scanner Module
Workstation PiC
Software
Download .LDO File to PiC PiCPro Profibus
PiCPro Port
Configuration (.UCT) File Port
exported to PiCPro
Profibus Configuration Download .UCP File to Config.
Software Port
Profibus Scanner Module
Personality File (.UCP)
Profibus Network
Overview of setting up a Profibus Network

1. Use the G&L Profibus Configuration Software to provide information about
your Profibus system. This information includes a description of input and out-
put data associated with each node, tags (variable names) for this data, and the
address of each node. (See procedure that follows this section.)
2. Always use the File | Export Tags and File | Export Binary from the menu of
the G&L Profibus Configuration Software to generate two files in your work-
station:
Current configuration file (.UCT) for PiCPro.
Current personality file (.UCP) for the Profibus scanner module.
For PiC and standalone MMC:
3. Use the G&L Profibus Configuration Software to download the personality file
to the Profibus scanner module. Be sure the PiCPro cable is connected to the
Configuration Port.*
4. Design your ladder program using PiCPro (refer to the fieldbus function/func-
tion blocks in the Function/Function Block Reference Guide and the Theory of
Operation section for your Profibus Scanner Module in the appropriate Hard-
ware Manual).
Typically Profibus communication is opened with a FB_OPN function block.
After this is done FB_STA is used to continually monitor for possible error
conditions and to update the on-line (ONLI) status flag. Once the network is
on-line the FB_SND and FB_RCV functions are used to transfer variables to
and from the memory image in the Profibus Scanner Module. The Profibus
Scanner Module in turn transfers this memory image from and to actual I/O
hardware associated with the tagged variables.
G&L Profibus Configuration Software 405

Once a Profibus network is properly on-line, only severe electrical noise or a
hardware error will cause the network to go off-line. Detection of a negative
transition of the on-line status flag (from FB_STA) can be used as a warning
that data from and to the Profibus network may no longer be correct. The value
of each device status byte (described at the end of this chapter) can serve as a
similar warning. In applications where Profibus data affects safety, these warn-
ings should be used by the ladder for taking appropriate action.
5. Use PiCPro to download the ladder file to the control. Be sure the PiCPro cable
is connected to the PiCPro Port.*
6. Connect the Profibus cable to the Profibus Port on the Profibus scanner mod-
ule.
*Note: Before downloading the personality file, make sure the ladder scan in the
CPU is stopped. The PiCPro cable from your workstation is first used to download
the personality file; this cable must be connected to the Configuration Port on the
Profibus scanner module. You then need to connect this cable to the PiCPro Port
on the CPU module in order to download the ladder.
For MMC for PC:
Use the PiCPro Download Hex feature to load the personality file via local or
remote Ethernet. There are no cables or ports to connect directly. However, the lad-
der scan in the MMC for PC must be stopped before downloading.
Procedure for using the G&L Profibus Configuration Software
There are several ways to accomplish the following. Once you become familiar
with the operations, you can use the method you prefer. Note: Additional informa-
tion can be obtained by selecting Help from the menu or by using the Help button
in a given dialog.
1. Select the G&L Profibus Configuration icon to get to the application window.
2. Select File | New from the menu to bring up your working screen. A window
will appear with the heading New Network Configuration. Select Scanner (to
the left of G&L Profibus Sca...). The working screen will then appear with the
default name GLPBCFG1. Another window will also appear prompting for
scanner properties. Enter the appropriate information as follows:
• General TAB
Enter a name for the scanner module or leave it as the default name Scan-
ner. This scanner is a network master and the station address is typically
left at 0.
• Parameters TAB
Typically, leave Scan Cycle Times in Auto.
3. Select the Profibus_DP and double-click to define overall network properties.
A window with the heading of Network will appear with 3 tabs, as follows.
• General TAB
Select the desired network baud rate. All nodes have to be capable of sup-
porting the rate selected. The highest station address can be left at 126.
406 G&L Profibus Configuration Software

• Timing TAB
The timing parameters are defined in tbit units. Tbit equals 1/baud rate.
The default values are typically used.
• Parameters TAB
Again, the default values for the parameters are typically used.
4. Add nodes under scanner by selecting Slaves in the left-hand window. By drill-
ing down, an icon and description for the desired node can be found. This fea-
ture is based upon information stored in .gsd files in a subdirectory of your
choosing. You have to obtain the .gsd files from the manufacturer of the parts
you wish to use. Most manufacturers have links to their sites from www.profi-
bus.com. Once an icon is found and selected, drag and drop it under the scan-
ner symbol. A window will appear with specific information about the node.
• General TAB
Assign a specific name if so desired and select a unique station address for
this node in the network.
• Modules TAB
If there are plug in modules associated with the node, add the description(s)
for those modules.
• Address TAB
Do not modify offsets. The default settings are required for the Sheffield
Automation applications.
• Tag TAB
Select a tag name for each available variable.
• Std. Prms TAB
Some parts have additional information and do not require modification.
• Ext. Prms TAB
• Diagnostics TAB
Continue to drag and drop icons from the *.gsd files in the slave directory until
all nodes have been defined for the network.
5. Select File | Export Tags from the menu. You will be prompted for a file name
with a .uct extension. Then select File | Export Binary from the menu. You
will be prompted for a file name with a .ucp extension.
Use the same base file name and same directory as that used for your ladder.
One of these files (.uct) will be used by PiCPro when down loading your lad-
der. Another file (.ucp) will be used by G&L Profibus Configuration when
down loading the personality file to the Profibus scanner module.
G&L Profibus Configuration Software 407

6. For PiC and standalone MMC CPUs, after exiting the File menu, right-click on
the G&L Scanner symbol to bring up a menu. This time select Download. You
must have the PiCPro cable connected between your workstation and the con-
figuration port on the Profibus scanner module. Select the Download button
and wait for the operation to be completed.
Note: If the Download dialog indicates the Com Port as “Not Connected”, first
check for proper cabling. Then, be sure the ladder scan in the CPU is stopped.
7. For MMC for PC CPUs, use PiCPro Professional Edition, click Online |
Download Hex from the menu. Enter the name of the personality file (.ucp)
and select the port as MMC for PC. More information on this can be found in
topic Download a Hex File.
8. Return to the application screen and save your file before exiting.
Device Status
There is a status byte variable associated with each node (slave). It can be tagged
with the G&L Profibus Configuration Software. When this byte is equal to zero,
the node has not been detected properly by the G&L scanner module. When equal
to 80h, the node is OK.
408 G&L Profibus Configuration Software

APPENDIX A - Quick Reference to In/Out Function Data
Function Input/Output Data Type Reference
This is a quick reference giving the data types of all the inputs and outputs of the functions
and function blocks used in PiCPro. The input or output is on the left and the data type is on
the right.
If an input/output is listed more than once, it has more than one data type depending on the
function it comes from. In that case, the functions are listed below the input/output and data
type. All the various IN inputs and OUT outputs are covered in tables that follow.
Data Type Reference

4mA0...................................... BOOL CNT............................................. INT DONE .....................................BOOL
10ms....................................... BOOL CNTL........................................ UINT DROP .......................................DINT
100ms..................................... BOOL COMN................................STRUCT DTST .................................. STRING

CONF.................................STRUCT DVSR.....................same NUMERIC
A as DVND or DINT if DVND = TIME
COS ........................... REAL/LREAL
ACC.......................................LREAL
CSTP ......................................BOOL E
ACCL..................................... UDINT
CU...........................................BOOL ELEM........................................UINT
ACT .......................................... DINT
CV ............................................... INT EN...........................................BOOL
PID
ERR ........................................BOOL
ACT .............................................INT D
TME_ERR?, ANLG_OUT
IPREAD, IPRECV, IPWRITE, DABL.......................................BOOL
NETRCV, NETSND, READ, ERR ............................................ INT
DATA ....................................... DINT
WRITE ASSIGN, CLOSE, CONFIG,
DATA ................................... ARRAY COORD2RL, DELFIL, FB_STA,
ACTV.....................................WORD
IO_CFG FRESPACE, IPACCEPT,
ANGL.......................... REAL/LREAL IPCLOSE, IPCONN, IPHOSTID,
DATA .................................STRUCT IPLISTEN, IPNAM2IP, IPREAD,
AXIS .......................................USINT IPRECV, IPSEND, IPSOCK,
SCA_RECV, SCA_SEND,
B SCS_RECV, SCS_SEND IPWRITE, OI_SER, NETOPEN,
NETRCV, NETSND, OPC_ENET,
BEG........................................ BOOL DAY....................................... UINT OPEN, READ, RENAME,
RESUME, SCA_ACKR,
BIPO....................................... BOOL DBUF ........ ARRAY, STRUCT, STRING SCA_CLOS, SCA_CTRL,
BKPR...................................... BOOL DCNT.......................................... INT SCA_ERST, SCA_PBIT,
SCA_RCYC, SCA_RECV,
BNDW ................................... UDINT DECL .....................................UDINT SCA_REF, SCA_SEND,
BTVL ........................................ DINT DEN............................................. INT SCA_WCYC, SCR_ERR,
SCS_ACKR, SCS_CTRL,
BUFR ........ARRAY, STRUCT, STRING DERR.......................................... INT SCS_RECV, SCS_REF,
SCS_SEND, SEEK, STATUS,
C DEST .............ARRAY OF STRUCT TUNEWRIT, WRITE
CAM .............. ARRAY OF STRUCT DID.........................................USINT ERR ............................... SINT, UINT
CD .......................................... BOOL DIFF ...........................(same as IN0) IO_CFG, SC_INIT
CFG.....................................STRING DIM........................................... DINT ERR ....................................... USINT
CFGZ...................................STRING DIR......................................STRING A_INCHIT, A_INCHRD,
CHAN .....................................USINT DIST......................................... DINT A_INMDIT, ARTCHIT,
ARTDCHRD, ARTDMDIT,
CLRC........................................ UINT DISTANCE, FAST_QUE ATMPCHIT, ATMPCHRD,
DIST.......................................UDINT ATMPMDIT, STRTSERV,
CLSD...................................... BOOL CAPTINIT, SCR_CONT,
CMD ......................................... UINT REGIST SERVOCLK
CNFG .................................STRUCT DVND................ NUMERIC or TIME ERRS.................................... WORD
Appendix A - Function Data Type Reference 409

ESTP ......................................BOOL MAIN.................................. STRUCT OUTs......................(See Last Table)
ET ............................................ TIME MAN........................................ BOOL P
F MAST .................................... USINT P ...................................... NUMERIC
FAHR......................................BOOL MAX.............................same as MIN DELETE, INSERT, MID,
REPLACE
FAIL ........................................BOOL MCND................NUMERIC or TIME
PHAS .....................................USINT
FAST...................................... USINT MDST .......................................DINT
PLUS...................................... BOOL
FU .............................................DINT µsec..........................................UINT
PNT ........................................USINT
FUNC..................................... USINT MIN ..............................................any
PNUM.....................................USINT
G MODE..........................................INT
PORT ..................................STRING
G .............................................BOOL MOVE................................ STRUCT
OI_SER
H MPLR ....................same NUMERIC
as MCND or DINT if MCND = TIME PORT ....................................... UINT
HILT ........................................BOOL
MSTR .......................................DINT IPCONN, IPSEND, OPC_ENET
HNDL.......................................... INT
N POS.......................................... DINT
CLOSE, CONFIG, OPEN, READ,
SEEK, STATUS, WRITE N ............................................ USINT POSN............ ARRAY OF STRUCT
HNDL........................................UINT NAME ................................. STRING PRB........................................USINT
IPACCEPT, IPCLOSE, IPCONN, NAMZ ................................. STRING PRI ......................................... BOOL

IPLISTEN, IPREAD, IPRECV, NODE .................................... USINT PROD......................same as MCND
IPSEND, IPSOCK, IPWRITE
NUM ............................................INT PROT ....................................... UINT
HOSZ.................................. STRING
RATIOSCL PT............................................. TIME
I
NUM ................................ NUMERIC PTR ............... ARRAY OF STRUCT
I147....................................... WORD
NUM2STR, STR2NUM PV................................................INT
IDN............................................UINT
NUM ...........................REAL/LREAL Q
IGNR......................................UDINT
EXP, LOG, LN Q............................................. BOOL
INDX ...................................... USINT
NUM ...................................... USINT QAVL...................................... BOOL
INPS........................................BOOL
IO_CFG, STR2USI, USIN2STR QTY.......................................... DINT
INs......................... (See Next Table)
O QTY........................................USINT
IPZ ...................................... STRING
OFF ..........................................DINT BIO_PERF, PLS
IST ..................................... STRUCT
OFST........................................UINT QUE........................................USINT
J
OIER............................................INT QUOT...................... same as DVND
JERK..................................... LREAL
OIFL........................................ BOOL R
K
OK........................................... BOOL R............................................. BOOL
K.......................................NUMERIC
ON ............................................DINT RACK .....................................USINT
L ONCE ..................................... BOOL RATE..................................... UDINT
L .................................................. INT ONLI ....................................... BOOL RATE........................................ TIME
LD ...........................................BOOL OPTN .................................... USINT SERVOCLK
LEN............................................. INT SC_INIT, SCA_CTRL, RDNE..................................... BOOL
LGTH .....................................UDINT SCS_CTRL
REAL............. ARRAY OF STRUCT
LOG ............................REAL/LREAL OPTN ....................................WORD
REFD ....................................... DINT
LOLT.......................................BOOL FAST_REF, LAD_REF,
RATIOCAM, RATIOSCL, REM ........................ same as DVND
LN ...............................REAL/LREAL RATIOSLP, RATIO_RL, REQ........................................ BOOL
LU .............................................DINT SCA_REF, SCS_REF
RETR ..................................... BOOL
ORG ............................................INT
M REV........................................ BOOL
410 Appendix A - Function Data Type Reference

ROOT.........................same as SQR T
RNGE.....................................USINT TAN............................ REAL/LREAL
RPER .....................................USINT TASK..................................STRUCT
RPTP...................................... BOOL TBUF ........ ARRAY, STRUCT, STRING
RSCD .................................STRUCT TCNT .......................................... INT
RSLT ........................................ DINT TIME......................................... UINT
RSMD..................................... BOOL TOLR .....................................UDINT
RVAL...................................... BOOL TYPE......................................USINT
S V
SDIR....................................... BOOL VALU........................................... INT
SDST........................................ DINT VAR...........................................SINT
SEG1..................................STRUCT VARS .................................STRUCT
SERR ....................................... UINT W
SET ........................................ BOOL WEEK .....................................BOOL
SID..........................................USINT
SIN.............................. REAL/LREAL
SIZE ......................................... DINT
SIZE .......................................USINT
CAPTINIT
SLOT......................................USINT
SLPE ............. ARRAY OF STRUCT
SLV........................................... UINT
SPT .......................................... DINT
SQR.............. UDINT, UINT, USINT,
or constant
SR.......................................STRUCT
SRCE ............ ARRAY OF STRUCT
SRS....................................STRUCT
SSTR........................................ DINT
STAT .................................. DWORD
FB_STA
STAT ...........................................INT
NETMON, SCA_REF, SCS_REF,
STATUS
STAT .....................................WORD
SCA_STAT, SCS_STAT,
STATUSSV,
STEPSTAT
STOP...................................... BOOL
STR .....................................STRING
STRC..................................STRUCT
STRT...................................... BOOL
SUM .............................same as IN1

IN inputs
[Inputs for extensible functions are followed with (ext).]
]
Input Data type Functions

IN any SIZEOF
BITWISE NOT, ROL, ROR, SHL, SHR
BOOL TOF, TON, TP
DATE DATE2STR
DATE_AND_TIME CLOCK, DT2DATE, DT2STR, DT_2_TOD
NUMERIC ABS, NEG
STRING DELETE, LEFT, MID, RIGHT
TIME TIME2STR
TIME_OF_DAY TOD2STR
same as MIN LIMIT
IN0 NUMERIC or TIME SUB
any except STRUCT SEL
IN0 (ext) any except STRUCT MUX
IN1 any except BOOL or STRUCT NE
BOOL SCA_CTRL, SCS_CTRL
DATE D_TOD2DT, S_D_D
DATE_AND_TIME A_DT_T, S_DT_DT, S_DT_T
STRING FIND, INSERT, REPLACE
TIME_OF_DAY A_TOD_T, S_TOD_T, S_TOD_TO
same as IN0 SEL, SUB
IN1 (ext) any MOVE
any except BOOL or STRUCT EQ, GE, GT, LE, LT, MAX, MIN
BITWISE AND, OR, XOR
NUMERIC or TIME ADD
STRING CONCAT
same as IN0 MUX
IN2 BOOL SCA_CTRL, SCS_CTRL
DATE S_D_D
DATE_AND_TIME S_DT_DT
TIME A_DT_T, A_TOD_T, S_DT_T, S_TOD_T
TIME_OF_DAY D_TOD2DT, S_TOD_TO
same as IN1 NE
STRING FIND, INSERT, REPLACE
IN2 (ext) same as IN1 ADD, AND, EQ, GE, GT, LE, MAX, MIN, OR, XOR
STRING CONCAT, REPLACE
IN3 BOOL SCA_CTRL, SCS_CTRL

OUT outputs
Output Data type Functions

OUT BOOL CAM_OUT, EQ, GE, GT, LE, LT, NE, PLS
DATE DT2DATE
DATE_AND_TIME A_DT_T, CLOCK, D_TOD2DT, S_DT_T
same as IN ABS, NEG, NOT, ROL, ROR, SHL, SHR
same as IN0 MUX, SEL
same as IN1 AND, OR, XOR
same as MIN LIMIT
NUMERIC FIND
UINT SIZEOF
TIME S_D_D, S_DT_DT, S_TOD_TO
TIME_OF_DAY A_TOD_T, DT2TOD, S_TOD_T
OUT1 same as IN1 MAX, MIN, MOVE
STRING CONCAT, DATE2STR, DELETE, DT2STR, INSERT,
OUT----OUT LEFT, MID, REPLACE, RIGHT, TIME2STR, TOD2STR,
NOTE
There are also INs/OUTs on all the data type conversion functions. In those functions, the
IN is always the data type you are converting from and the OUT is always the data type
you are converting to.

APPENDIX B - Errors
Function Error Codes
The categories of function errors are:

General function errors
I/O block function block errors
String function errors
Stepper errors
Start servo function errors
General Function Errors

For all functions, the output variables will have unpredictable values and the output at OK, DONE, or Q
will not be energized whenever the following occurs.
An output variable does not have enough bits to hold the result.
An output variable is an unsigned integer and the result is negative.
The operation attempts to divide a number by zero.
The input data is invalid.
I/O Function Block Error Codes

If an error occurs when the I/O functions execute, the following occurs.
The output at DONE is not energized.
The output at FAIL is energized.
The output at ERR holds one of error numbers listed below.
Error # Error Description
01 opcode_error
Invalid device open mode specified for function (e.g. 16#602)
02 handle_error
The handle to a function is invalid. Possible reasons include:
Using I/O functions with an unopened handle
Attempting to do a READ on a handle opened for WRITE
ONLY
Attempting to do a WRITE to a handle opened for READ
ONLY
03 already_open
Reserved for Sheffield Automation. Internal GLOS error
04 open_error
OPEN mode (READ/WRITE/APPEND) specified is invalid.
05 device_empty
Reserved for Sheffield Automation
Appendix B - Errors 415

06 read_error
Depending on the device you are using, this error will be one of
those listed below.
DISK driver detects a checksum error on the DISK. Media
error on DISK reading disk FCB (File Control Block).
A parity, overrun, or framing error exists in the data in the input
buffer of the COM port.
07 write_error
Error writing to the device
08 write_protect
09 device_error
Caused by any of the following:
The Seek origin is not A00, A01, or A02.
Improper device name (Choices are PICPRO:, RAMDISK:,
FMSDISK:, or USER:)
Attempting to do a STATUS on a file
Attempting to do a file operation on a non-DOS device
Bad parity in the configuration string or a hardware error in
configuring the port
Attempting to do a second or subsequent operation before the
first one was completed
10 out_of_handles
Too many files open. A maximum of 10 handles can be used.
READ/WRITE or APPEND operations use two handles.
READ ONLY or WRITE ONLY operations use one handle.
11 invalid_device
Improper device name (Choices are PICPRO:, RAMDISK:,
FMSDISK:, USER:, or any name you have assigned at the
NAMZ input of a function block)
12 invalid_file_name
Filename format is wrong.
Filename is too large.
13 too_many_drivers
14 too_many_ connections
416 Appendix B - Errors

15 read_write_ error
Error reading or writing a disk file
16 device_error
17 file_not_open
Attempting a READ, WRITE, or SEEK on a file that is not open.
18 invalid_access
Caused by any of the following:
Attempting to CLOSE a file that was not open
SEEK has a problem seeking a new location.
Attempting to write to a file opened for read only
19 file_not_in_ dir
Caused by one of the following:
Filename not found in directory
Volume name not found in directory
20 file_already_ open
Attempting to OPEN a file that is already open
21 write_protect
Error occurs when attempting to delete a READ ONLY file from
DISK.
22 mode_error
Caused by one of the following:
Invalid mode input to OPEN
Invalid mode input to SEEK
23 out_of_handles
A maximum of 10 handles are available in the control. This error
means there are no more handles available (too many files open).
24 end_of_dir
No more directory entries
25 function_locked
Reserved for Sheffield Automation. Internal GLOS error.
26 rename_new_ exists
27 rename_old_open
28 rename_no_old

29 attrib_ invalid
Reserved for Sheffield Automation. Internal GLOS error.
30 handle_too_large
31 disk_error
General error on disk drive
32 device_parity_error
33 end_of_devices
Device driver for the device specified not found
34 io_dev_aborted
35 duplicate_ filename
36 no_memory
37 no_buffers
No memory to get more file buffers
38 dir_not_empty
39 dir_not_found
40 out_of_fats
No more entries available in the FAT (File Attribute Table).
Reduce the number of files in this directory.
41 sdir_exists
42 filespec_too_ long
43 no_default_ device
44 parameter_error
Occurs if the value entered at the CNT input of the READ
function block is larger than the declared size of a string used as
the BUFR input.

String Function Errors
If an error occurs when a string function executes the following occurs.
The output at OK is not energized.
The STRING variable output will be null (have a length of zero).
CONCAT Function An error occurs if
The length of IN1 > the length of OUT

The length of IN2 > the length of OUT
The length of IN1 + the length of IN2 > the length of OUT
IN2, IN3, IN4…IN17 = OUT
DELETE Function An error occurs if
P=0
P > 255
P > length of IN
L > 255
The length of IN - L > the length of OUT
FIND Function An error occurs if
The length of IN1 = 0

The length of IN2 = 0
The length of IN2 > the length of IN1

INSERT Function An error occurs if
P=0
P > 255
P > ength of IN
IN2 = OUT
The length of IN1 + the length of IN2 > the length of OUT
LEFT Function An error occurs if
L > 255
L > the length of OUT
MID Function An error occurs if
P=0
P > 255
P > length of IN
L > 255
L > the length of OUT

REPLACE Function An error occurs if
P=0
P > 255
P>length of IN1
L > 255
IN1 = OUT
IN2 = OUT
The length of IN1 + the length of IN2>the length of OUT
RIGHT Function An error occurs if
L > OUT
L > 255
Function Errors
6008 Function: No Definition for Function
The definition for the function _ was not found. Changes to this file cannot be
saved unless the function stub is removed.
PiCPro cannot locate the library containing the function. Check that you are point-
ing at the correct library and close and reopen your file.
Servo C-Stop, E-Stop, and Programming Error Codes
There are four types of errors that can occur when working with servo control. The first three apply to
individual axes. The fourth, timing errors, is connected to the entire system.
1. C-stop (controlled-stop) errors
2. E-stop (emergency stop) errors
3. P (programming) errors
4. Timing errors

Servo C (controlled) - stop errors
When a C-stop (Controlled-stop) error occurs on an individual servo axis, the following happens:
The axis remains in servo lock and the axis is brought to a controlled stop at the rate specified by
the controlled stop ramp in servo setup.
The active and next queues are cleared.
The FAST_QUE mode is canceled when the C-stop is reset.
Hex* Value
Bit Location (decimal in
(low byte) Error Description ladder)
8 Part reference error
Move was in progress when a part reference or a part clear func- 8080
tion was called. (32896)
7 Part reference dimension error
When the dimension for the part reference was converted to 8040
feedback units, it was too big to fit into 29 bits. (32832)
6 Distance or position move dimension error
When the dimension for the move was converted to feedback 8020
units, it was to big to fit into 31 bits. (32800)
5 Feedrate error
When the feedrate for the move was converted to feedback units 8010
per servo update, it was too big to fit into 32 bits or it exceeded (32784)
the velocity limit entered in setup.
Note: This error can occur with feedrate override, new feedrate,
position, distance, velocity, or machine reference moves.
4 Machine reference error
When the dimension for the machine reference was converted to 8008
feedback units, it was too big to fit into 29 bits. (32776)
3 User-defined C-stop
When this bit is set, a user-defined C-stop has occurred. 8004
(32772)
2 Negative software limit exceeded
The command position exceeded the user-defined negative soft- 8002
ware end limit. (32770)
1 Positive software limit exceeded
The command position exceeded the user defined positive soft- 8001
ware end limit. (32769)
*When more than one error occurs, the hex values are OR’d. For example, if 8001
and 8004 occur, the result is 8005 hex (32773 decimal).
Servo E (emergency) - stop errors

When a E-stop (Emergency-stop) error occurs on an individual servo axis, the following happens:
The system is out of servo lock.
A zero voltage is sent to the analog outputs.
The active and next queues are cleared.
The FAST_QUE mode is canceled when the E-stop is reset.
EXCEPTION:
If a User-Set or Excess Error E-Stop occurs while Resumable E-Stop Allow is set (Servo Setup or
WRITE_SV/READ_SV Variable 63), a Resumable E-Stop will occur and the following happens:
The system is out of servo lock.
A zero voltage is sent to the analog outputs.
The moves in the active and next queues remain intact.
The axis’ Normal Interpolator remains running.
The axis goes into Resume Mode. In Resume Mode, the axis will follow the Resume Interpolator.
The Resume Interpolator will output zero velocity until the RESUME function is called. The
RESUME function can be called after the Resumable E-Stop has been reset and the servo loop
has been closed. The axis remains in Resume Mode until the RESUME function brings it back onto
the Normal Interpolator’s path or until a non-resumable E-Stop cancels Resume Mode.
Hex* Value
8, 7 Not Used
6 SERCOS error
Cyclic data synchronization error 8020

(32800)
5 SERCOS error
SERCOS drive E-stop - Status word bits 15, 14, and 13 not 8010
equal to 1 1 0 respectively. (32784)
4 User-set
An E-stop on a servo axis has occurred which was called in the 8008
ladder using the ESTOP function. (32776)
3 Overflow error
A slave delta overflow during runtime has occurred. This prob- 8004
lem is most likely to occur if you are moving at a high rate of (32772)
speed and/or the slave distance is very large compared to the
master distance.
There are two conditions that can set this bit.
1 In
FU, if the master moved position times the slave distance
entered is greater that 31 bits.
2 In
FU, if the master moved times the SDIS divided by the
MDIS > 16 bits.
2 Excess error
When an excess following error has occurred, the axis has 8002
exceeded the limit entered in the Servo setup program as the (32770)
following error limit. This represents the maximum distance the
commanded axis position can be from the actual axis position.
1 Loss of feedback
A loss of feedback from the feedback device has occurred. 8001

Available for servo and digitizing axes. (32769)
* When more than one error occurs, the hex values are OR’d. For example, if 8001

Servo P (programming) - errors
P- (Programming) errors occur during master/slave moves or a FAST_QUE call. P-errors may prevent:
The move from being placed in the queue (or if the move is in the queue, abort the move)
or
The OK on the function from being set

Hex* Value
8 The FAST axis in the FAST_QUE function moved too far in the
wrong direction
8080
The axis traveled more than 65,535 FU in the opposite direction of the (32896)
value entered in DIST of the FAST_QUE function.
7 Profile number not found
Data for a profile move is not valid. 8040

(32832)
6 Master axis not available
This error can occur when using the FAST_QUE function or the func- 8020
tions for master/slave moves (RATIO_GR, RATIOSYN, or RATIO- (32800)
PRO). The conditions that can set this bit include:
1 Master axis or fast axis not initialized
2 Interrupt rates different for axes
3 Axis
at slave input is the same as axis at master input in master/
slave moves
5, 4, 3, 2 Not Used ---
1 Master start position for lock on
When the dimension for the lock position was converted to feedback 8001
units, it was too big to fit into 32 bits. (32769)
Hex* Value
(high byte) Error Description ladder)
8 A programming error has occurred. There must be at least one other 8000
bit set in the word. (32768)
7, 6, 5 Not Used ---
4 Master axis beyond start point 8800
(34816)
The master axis is beyond its starting point for a ration synchronization
(RATIOSYN) move.
3 Slave axis beyond start point 8400
(33792)
The slave axis is beyond its starting point for a ratio synchronization
(RATIOSYN) move.
2 Master distance not valid 8200
(33280)
When the master distance is converted to feedback units, it is greater
than 16 bits.
1 Slave distance not valid 8100
(33024)
When the slave distance is converted to feedback units, it is greater
than 16 bits.
*When more than one error occurs, the hex values are OR’d. For example, if 8100

Servo Timing Errors
All the servo calculations for one interrupt must be completed in the time frame
selected by you in servo setup before the next interrupt begins. If they are not com-
pleted, a timing error occurs. The timing error is connected to the entire system.
This error is monitored in the ladder program with the TME_ERR? function. If the
boolean output at ERR is set, a timing error is occurring. Depending on the system,
this can affect performance.
IMPORTANT
Always set an E-Stop on all axes when a timing error occurs.
SERCOS Error Codes
Ring Errors
The ring errors listed below appear at the ERR output of the SCR_ERR function
and will appear on the Ring Error State line in the Ring State dialog.
ERR# Description What to do/check

3 Axis is not initialized, is not a SER- SERCOS board in correct slot
COS axis, or the slot/ring/slave speci- SR structure members correct
fication is incorrect.
17 The SERCOS module did not receive Check connection
an expected AT response. Cable could
be disconnected.
20 Phase 0 detected that the ring is not Check connection
complete. Ensure drive is turned on
65 Error occurred calculating when MDT Too many slaves on one ring
should occur. One or more drives cannot accom-
modate required MDT
66 Error occurred calculating when drive Too many slaves on one ring
data valid. One or more drives cannot accom-
modate command times
67 Error occurred calculating when feed- Too many slaves on one ring
back data valid. One or more drives cannot accom-
modate feedback capture times
68 Error occurred calculating total time Too many slaves on one ring
required for communication cycle Cyclic data on slaves too long
Update rate too fast

memory for SERCON processor. Cyclic data on slaves too long
memory for internal memory map. Cyclic data on slaves too long
71 Error occurred calculating service Too many slaves on one ring
channel memory map. Cyclic data on slaves too long
74 CPU on SERCOS module has too Too many slaves on one ring
many tasks during update. Too many Cyclic data on slaves too long
slaves on one ring.
128 Slave error occurred. Read SERR out- SLV output contains slave number
put to identify error. The SLV output IDN output contains the IDN
indicates the slave number. transfer that caused the error
SERR output contains the drive
generated error number
136 Individual slave will not respond. The Address switch on drive does not
SLV output indicates the slave num- match slave number
ber. Baud rate switch on drive does not
match rate in ring definition
SLV output contains slave number
that does not respond
144 Individual slave cannot carry out a SLV output contains slave number
Procedure Command Function. The IDN output contains the Procedure
SLV output indicates the slave num- Command Function that caused the
ber. error
drive
drive

Slave Errors
The slave errors listed below appear at the SERR output of certain slave SERCOS
functions and will appear on the Slave Error line in the Ring State dialog.
SERR # Description
4097 This IDN does not exist.
4105 The data for this IDN may not be accessed.
8193 The name does not exist.
8194 The name transmission is too short.
8195 The name transmission is too long.
8196 The name may not be changed.
8197 The name is write-protected.
12290 The attribute transmission is too short.
12291 The attribute transmission is too long.
12292 The attribute is write-protected at this time.
16385 The units do not exist.
16386 The units transmission is too short.
16387 The units transmission is too long.
16388 The units may not be changed.
16389 The units are write-protected at this time.
20481 The minimum value does not exist.
20482 The minimum value transmission is too short.
20483 The minimum value transmission is too long.
20484 The minimum value may not be changed.
20485 The minimum value is write-protected.
24577 The maximum value does not exist.
24578 The maximum value transmission is too short.
24579 The maximum value transmission is too long.
24580 The maximum value may not be changed.
24581 The maximum value is write-protected.
28674 The data is too short.
28675 The data is too long.
28676 The data may not be changed.
28677 The data is write-protected at this time.
28678 The data is smaller than the minimum value.
28679 The data is larger than the maximum value.
28680 The bit pattern for this IDN is invalid.

TCP/IP Error Codes
The following errors can be reported out of the ERR output on the IPXXXX function blocks.
ERR Description ERR# Description

0 No error 40 Destination address required
1 Not owner 41 Protocol wrong type for socket
2 No such file or directory 42 Protocol not available
3 No such process 43 Protocol not supported
4 Interrupted system call 44 Socket type not supported
5 I/O error 45 Operation not supported on socket
6 No such device or address 46 Protocol family not supported
7 Arg list too long 47 Address family not supported
8 Exec format error 48 Address already in use
9 Bad file number 49 Can’t assign requested address
10 No children 50 Socket operation on non-socket
11 No more process 51 Network is unreachable
12 Not enough core 52 Network dropped connection on reset
13 Permission denied 53 Software caused connection abort
14 Bad address 54 Connection reset by peer
15 Directory not empty 55 No buffer space available
16 Mount device busy 56 Socket is already connected
17 File exists 57 Socket is not connected
18 Cross-device link 58 Can’t send after socket shutdown
19 No such device 59 Too many references: can’t splice
20 Not a directory 60 Connection timed out
21 Is a directory 61 Connection refused
22 Invalid argument 62 Network is down
23 File table overflow 63 Text file busy
24 Too many files open 64 Too many levels of symbolic links
25 Not a typewriter 65 No route to host
26 File name too long 66 Block device required
27 File too large 67 Host is down
28 No space left on device 68 Operation now in progress
29 Illegal seek 69 Operation already in progress
30 Read-only file system 70 Operation would block
31 Too many links 71 Function not implemented
32 Broken pipe 72 Operation cancelled
33 Resource deadlock avoided 1000 There is a non-zero terminated string that
requires zero termination, or there is a zero
length string.
34 No locks available 1001 There is a CNT input that is too large
35 Unsupported value 1002 The SLOT number requested does not contain
an Ethernet board
36 Message size 1003 Either the firmware does not support TCP/IP
or there is no Ethernet board in the rack
37 Argument too large 1004 The IPZ buffer is too small
38 Result is too large 1005 TCP/IP stack failure. Socket no longer valid.
10000 Any error code above 10000 when using these functions blocks was generated by Microsoft.
and up Please check their documentation.

Compile Error Messages (Ladder)
If the compile process is unsuccessful, errors will be reported in the information window. Typically,
you must re-edit the ladder to correct the errors and recompile.
These errors can be the following types:
1. Fatal - indicates a severe problem that prevents the compile from being completed.
2. Error - indicates a program syntax error.
3. Warning - provides an informational message. A warning does not prevent the com-
pile command from being completed, but it is recommended that the situation that
caused the warning be corrected.
If a compile error does occur, you can double-click on it in the information window and it will navigate
you to the place in the ladder where the error occurred. You can get help on an error by single clicking
on the error in the information window and pressing the F1 key.
1000 BINARY: BUILD

A file open exception has occurred. Error opening file __.
PiCPro has attempted to open the indicated file (usually a BIN or temporary file) and was unsuc-
cessful.
Tip
Ask these questions:
Is the disk drive full?
Is the disk drive write protected?
Is the TEMP/TMP environment variable pointing to a valid drive?
1002 BINARY: OUT OF MEMORY
Out of control application memory space.
The ladder code that is being compiled requires more memory than is available in the processor
specified in the hardware declarations.
1003 BINARY: FUNCTION NOT FOUND
_ not found in libraries.
There is a function required by your application that cannot be found.
Tip
Check to make sure your library paths are correct.
1004 BINARY: ARRAY MISMATCH

External data typing error, array mismatch, _ task _.
The indicated external variable declared in the indicated task was found in the main module, but one
is declared as an array and the other is not. They cannot be different.
Tip
Either declare both as an array or not.
1005 BINARY: EXTERNAL UNDEFINED
External _ in task _ has no source in the main module.
A variable marked with the external attribute in the software declarations table in the task ladder was
not declared in the main ladder as required.
Tip
Any variable used in a task that has been marked as external must also be declared in the main lad-
der whether or not the main ladder uses it. It must never be marked as external in the main ladder,
only in the task ladder.

1006 BINARY: TYPE MISMATCH
External data typing error, _ in task _, _.
The indicated external variable in the indicated task was found in the main module, but the variable
types are different as indicated. The types must match.
Tip
Be sure that the variable type of the external variable in a task has been declared in the main ladder
with the same variable type.
1007 BINARY: OUT OF PATCHES
More than 100 patches. A scan stopped, full module download is required.
The control provides for 100 patches which have been used up.
Tip
Do a full download to incorporate all the existing patches in the application.
After a full download, the patch area is again available for another 100 patches.
As you work with on-line edit, check the resources available summary in the information window to
see how many patches you have left.
1008 BINARY: TOO MANY PATCHES
Too many patch operations at once. A scan stopped, full module download is required.
There is a limit of 40 internal operations in any one patch download, depending on memory avail-
able. Every time a network is modified it is considered one patch, but it could include several internal
operations. This error simply means you are trying to do too much at one time.
Tip
Do a full download and proceed.
1009 BUILDER: NAME CHANGE
Windows filename _ changed to _ in the control.
The control only supports the original DOS 8.3 filename format. The filename supplied does not com-
ply with that format and has been modified as indicated for use in the control. This is an informational
message.
Tip
Use the DOS format of a maximum of 8 characters followed by a period, then 3 characters when
naming your files.
1010 OLE: HARDWARE CHANGED
Hardware declarations have changed.
Changes to existing hardware declarations will prevent a patch download.
Tip
If you make changes to the hardware declarations table, you must perform a compile and download
before attempting to patch the ladder.
1011 OLE: UDFB BIT MEMORY
Out of function block bit memory. A remake of this library function is required, along with a
full compile and download.
There is at least one new BOOLEAN variable for which there is no room reserved in the control data
memory. Either a debug version of the UDFB is not being used, or there have already been 40 addi-
tional bits used since the last remake and full download.
Tips
Remake the UDFB to incorporate any new variables and download the entire application.
or
Delete the additional variable(s) and all the places they are used.
Note: If you plan on adding variables you must have a debug version of the UDFB downloaded.
When working with on-line edit, check the resources available summary in the information window.

1012 OLE: UDFB BYTE MEMORY
Out of function block byte memory. A remake of this library function is required, along with a
full compile and download.
There is at least one new variable for which there is no room reserved in the control data memory.
Either a debug version of the UDFB is not being used or there have already been 80 additional
bytes used since the last remake and full download.
Tips
Remake the UDFB to incorporate any new variables and download the entire application.
or
Delete the additional variable(s) and all the places they are used.
1013 OLE: UDFB LINKS
Out of local label/function links.
There is at least one new function or network label for which there is no room reserved in this UDFB
code memory. Either a debug version of the UDFB is not being used, or there have already been 20
additional network labels or functions used since the last remake and full download.
Tips
Remake the UDFB to incorporate the new labels and download.
or
Delete the additional labels and functions.
1014 OLE: GLOBAL LINKS
Too many functions/labels. Out of global link table space.
PiCPro establishes a link table for labels and/or function/blocks added during on-line editing. There
is a limit of 26 links. Every time you do a full download, this link area becomes available again.
Tip
Do a full download when you get this message and the link area will become available.
1015 OLE: LABEL UNDEFINED
Network label _ is undefined.
Network labels are required on Jump to Label and Jump to Subroutine commands. If you enter a
label that you have not assigned to a network, you will get this error.
Tip
Ensure that any network you want to jump to has a label assigned to it.
If you get this error after entering a label with the jump command, make sure the label exists and/
or check the spelling of the label to ensure it matches the label of the destination network.
1072 COMPILE: BUILD ERROR OBSOLETE
Displayed when the attempt is made to compile (bin, hex, task, UDFB) a ladder that specifies an
obsolete CPU in Hardware Declarations.
Tip
Edit Hardware Declarations and select proper CPU.
1073 APP: OUT OF RETAINED DATA MEMORY
Data memory has been exceeded. The limit is 24K.

Dependency List Error Messages
1016 DEPEND: FILE EXCEPTION

This error can occur when building a dependency list.
1018 DEPEND: FILE READ EXCEPTION
This error can occur when reading a file during the building of a dependency list.
1019 DEPEND: FILE WRITE EXCEPTION
This error can occur when writing a file during the building of a dependency list.
1020 DEPEND: SRVFILE NOT FOUND
The servo file could not be found.
1021 DEPEND: SCRFILE NOT FOUND
The SERCOS file could not be found.
Library Error Messages
1033 BINARY: PIC LIBRARY DIFFERENCE

Function/block LEVEL 1 version difference.
If you attempt to patch a UDFB network after completing a full download and then edit and
recompile the UDFB, you will get this error.
Tips
You must perform a full download whenever you want to change a network containing a UDFB that
has been edited and recompiled since the previous full download.
Hardware Declarations Error Messages

The following errors or messages can be received when working with hardware declarations.
4000 HWD: REMOTE TO NONE
You have selected a master rack only hardware configuration. Your hardware is currently configured
for remote I/O. All expansion rack information will be deleted and irretrievable.
4001 HWD: PiC9 BOARDS
Selecting a PiC9 CPU automatically puts a Servo Encoder declaration in slot 3 of the master rack
and an In/Out 24V DC declaration in slot 4 of the master rack. If you currently have modules
declared in these slots, they will be replaced.
4002 HWD: REMOTE TO BLOCK
You have selected a block I/O hardware configuration. Your hardware is currently configured for
remote I/O. All expansion rack information will be deleted and irretrievable if you continue.
4003 HWD: BLOCK TO NONE
You have selected a master rack only hardware configuration. Your hardware is currently configured
for remote I/O. All block I/O information will be deleted and irretrievable.
4004 HWD: BLOCK TO REMOTE
You have selected a remote I/O hardware configuration. Your hardware is currently configured for
block I/O. All block I/O information will be deleted and irretrievable.
4006 HWD: DELETE BLOCK
When you delete a block I/O module, block I/O modules after the deleted module are shifted down
and renumbered accordingly. If you want to remove the module without shifting, change the module
to an Empty module.

4008 HWD: MAXIMUM RACKS EXCEEDED
The maximum number of expansion racks allowed exists. PiCPro currently supports a maximum of
seven expansion racks.
4009 HWD: INSERT BLOCK WARNING
When you insert a block I/O module, all block I/O modules after the inserted module are shifted up
and renumbered accordingly.
4010 HWD: MAXIMUM BLOCKS EXCEEDED
PiCPro currently supports 77 block I/O modules. You cannot execute an Insert After or Paste Insert
After on block module 77.
4011 HWD: NO CLIPBOARD
The workstation system clipboard could not be opened for the requested function (copy, cut). This
indicates a problem with your workstation. Make sure another application does not currently have
the clipboard open.
4013 HWD: INVALID PASTE
The keys <Ctrl + V> initiate a Paste command. Either nothing has been previously copied or the
command is invalid for the currently selected item.
4014 HWD: RESOLVER EXPANSION
There is an Input Resolver (2 or 4 ch) module on the clipboard. You cannot use either of these mod-
ules in an expansion rack.
4015 HWD: NOT BLOCK CPU
The CPU currently specified in the Master Rack does not support block I/O.
4016 HWD: NOT REMOTE CPU
The CPU currently specified in the Master Rack does not support remote I/O.
4017 HWD: LAST BLOCK NOT EMPTY
th
The 77 block module is not an Empty module. Performing any Insert function will remove this mod-
ule.
4019 HWD: TOO MANY RACKS
This version of PiCPro supports only seven expansion racks.
The ladder you are loading currently has eight expansion racks.
The eighth expansion rack will not be included in hardware declarations. Saving a ladder in this con-
dition will not save the eighth rack and render the hardware declarations for the eighth rack as irre-
trievable.
4021 HWD: INVALID COPY
The keys <Ctrl + C> initiate the Copy command. That command is invalid for the currently selected
item.
4022 HWD: INVALID CUT
The keys <Ctrl + X> initiate the Cut command. That command is invalid for the currently selected
item.
4023 HWD: INVALID PASTE/INSERT
The keys <Ctrl + A> initiate the Paste Insert After command. Either nothing has been previously
copied or the command is invalid for the currently selected item.
4024 HWD: INVALID DELETE
The Delete key initiates the delete command. That command is invalid for the currently selected
item.
4025 HWD: INVALID INSERT
The Insert key initiates the Insert After command. This command is invalid for the currently selected
item.

4026 HWD: I/O CONFLICT
The current module in the specified slot of the master rack does not match the hardware declaration
information which has been downloaded to the control.
4027 HWD: NO SOFT BIT
The binary file being downloaded to the control requires a CPU in the control which can handle soft-
ware bit memory. The CPU currently declared in the hardware declarations is not capable of han-
dling soft bit memory.
4029 HWD: CONFIRM SWITCH PIC TO STANDALONE MMC
When you switch from a PiC CPU to a standalone MMC CPU, this confirmation box will appear ask-
ing if you want to continue. If you do, slots 1 and 2 will hold modules for the chosen MMC configura-
tion, slots 3 and 4 are emptied, and slots 5 to 13 and remote I/O are removed. You will want to check
the I/O points in your software declarations table to ensure they are mapped to the correct locations.
If they are not, make the necessary edits before you proceed.
4030 HWD: CONFIRM SWITCH STANDALONE MMC TO PIC
When you switch from an MMC CPU to a PiC CPU, a confirmation box will appear asking if you
want to continue. If you do, slots 3 and 4 will be emptied, a CSM appears in slot 1, the chosen CPU
appears in slot 2, and slots 5 to 13 are added to the master rack. The Remote I/O option is made
available. You will want to check the I/O points in your software declarations table to ensure they are
mapped to the correct locations. If they are not, make the necessary edits before you proceed.
4031 HWD: CONVERT INVALID MMC CPU FORMAT
If you attempt to open a ladder with a PiC CPU type in the MMC-Limited Edition of PiCPro, you can
choose to convert the PiC CPU to an MMC CPU. However, all the I/O in the main and remote racks
will be removed in the conversion to an MMC CPU. Software Declarations should be checked to
ensure the I/O is mapped to the correct locations after the conversion. See Conversion References
in this section.
4032 HWD: PASTE CONFIRM SWITCH MMC TO PIC
You are warned of the consequences of pasting the CPU type from one hardware declarations table
to another with a different CPU type.
4033 HWD: PASTE CONFIRM SWITCH PIC TO MMC
You are warned of the consequences of pasting the CPU type from one hardware declarations table
to another with a different CPU type.
4034 HWD: MMC EDITION DOWNLOAD TO STANDALONE MMC ONLY
When working with PiCPro MMC-Limited Edition, you can only download ladders to a standalone
MMC control.
4035 HWD: DOWNLOAD FAILURE CPU TYPE MISMATCH
The CPU type you have selected in your ladder program does not match the CPU type in your con-
trol. Edit your hardware declarations so that the CPU type in your ladder matches the CPU type in
your control.
4036 HWD: OUT OF DATA MEMORY
Out of Data Memory. Out of memory error. Your program requires more memory than is avail-
able in the Control CPU.
This is a compile time error of a main ladder. This can occur when the data memory required for
retained variables (retentive) and declared hardware exceeds 64K.
This error can also occur on older style CPUs that have hardbit memory, when the number of
retrained BOOL's and declared hardware data memory exceeds 8K.
The only corrective action in either case is to reduce the amount of hardware or retained variables.
Contact Sheffield Automation for help in optimizing data memory usage.

4037 HWD: LADDER CONFIGURABLE I/O
You have chosen to enable Ladder Configurable I/O. This allows the ladder to continue scanning
even if there has been a failure in the remote or block I/O connected to your system. I/O in the main
rack will continue to work unless there has been a failure in the main I/O. If that occurs, all I/O in the
system becomes non-operational. If the CPU is an analog MMC for PC CPU, ladder configurable
I/O applies only to Block I/O. If there has been a failure in ASIU I/O, all I/O in the system becomes
non-operational.
Warning
Since this will allow the control to continue to scan even if there are I/O errors, the function block
IO_CFG must be used to allow the ladder to react to I/O.
Tip
If you need information on IO_CFG, open Function Block Help by selecting Help | Function/Func-
tion Block Help from the menu. Select the Index tab and then scroll down until you see IO_CFG.
Double-click on it. A description of this function block is then displayed on the right.
4038 HWD: CONVERT INVALID MMC FOR PC CPU
The ladder you are trying to open has an MMC for PC type CPU and you are using PiCPro MMC-
Limited Edition software.
You are asked if you would like to convert the existing ladder to use a standalone MMC CPU
instead.
Note: Master Rack and ASIU I/O will be removed because the standalone MMC CPU does not sup-
port this kind of I/O. Software Declarations should be checked to ensure the I/O is mapped to the
correct locations after the conversion. See Conversion References in this section.
4039 HWD: LAST ASIU MODULE IS NOT EMPTY
ASIU 8 is not empty. An empty ASIU will be inserted below the ASIU with focus. All ASIUs below the
one currently selected will be moved down, and what was ASIU 8 will be removed.
4040 HWD: INSERT ASIU WARNING
An empty ASIU will be inserted below the ASIU currently selected and all subsequent units will be
shifted down.
4041 HWD: MAXIMUM ASIU MODULES EXIST
The maximum number of ASIU I/O slots already exist and therefore, no other modules can be
inserted after ASIU 8.
4042 HWD: CONFIRM SWITCH MMC TO MMC FOR PC
When you switch from a standalone MMC to an MMC for PC CPU, this confirmation box will appear
asking if you want to continue. If you do, slot 1 will hold the chosen MMC for PC module, slot 2 is
emptied and slots 3 and 4 are removed.
Note: The I/O points defined in Software Declarations should be checked to ensure they are correct.
4043 HWD: CONFIRM SWITCH MMC FOR PC ANALOG CPU TO DIGITAL CPU
When you switch from an MMC for PC Analog Servo CPU to a Digital Servo CPU, all of the ASIUs
will be removed. You are asked to confirm this action.
Note: The I/O points defined in Software Declarations should be checked to ensure they are cor-
rect.
4044 HWD: CONFIRM SWITCH PIC TO MMC FOR PC
When you switch from a PiC CPU to an MMC for PC CPU, slot 2 will be emptied and slots 3-13 will
be removed. All remote I/O will also be removed. You are asked to confirm this action.
rect.
4045 HWD: CONFIRM DELETE ASIU
When you delete an ASIU module, all of the subsequent module locations will be shifted. You are
asked to confirm this action.

4046 HWD: PASTE NON-MMC FOR PC ANALOG SERVO
When you attempt to paste a non-MMC for PC Analog Servo master rack on an existing MMC for
PC Analog Servo master rack, all ASIU I/O will be removed. You are asked to confirm this action.
4047 HWD: CONFIRM SWITCH MMC FOR PC ANALOG SERVO TO PIC
When you switch from an MMC for PC Analog Servo CPU to a PiC CPU, a CSM will be put into slot
1, the selected PiC CPU will be put in slot 2, and slots 3 – 13 will be added to the master rack. All
ASIU I/O will be removed. You are asked to confirm this action.
rect. See Conversion References in this section.
4048 HWD: CONFIRM SWITCH MMC FOR PC DIGITAL SERVO TO PIC
When you switch from an MMC for PC Analog Servo CPU to a PiC CPU, a CSM will be put into slot
1, the selected PiC CPU will be put in slot 2, and slots 3 – 13 will be added to the master rack. All
ASIU I/O will be removed. You are asked to confirm this action.
rect. See Conversion References in this section.
4049 HWD: CONFIRM SWITCH MMC FOR PC ANALOG SERVO TO STANDAL-
ONE MMC
When you switch from an MMC for PC Analog Servo to a standalone MMC, the contents of slots 1
and 2 will be replaced, and slots 3 and 4 will be added to the master rack. All ASIU I/O will be
removed. You are asked to confirm this action.
Note: The I/O points defined in Software Declarations should be checked to ensure they are correct
4050 HWD: CONFIRM SWITCH MMC FOR PC DIGITAL SERVO TO STANDALONE
MMC
When you switch from an MMC for PC Digital Servo to a standalone MMC, the contents of slots 1
and 2 will be replaced, and slots 3 and 4 will be added to the master rack. You are asked to confirm
this action.
Note: The I/O points defined in Software Declarations should be checked to insure they are correct.
4057 HWD: LADDER CONTINUE SCAN WITH ASIU
WARNING: This will allow the control to continue to scan with I/O errors in the Master Rack,
Block I/O or ASIUs. The function block IO_CFG must be used to allow the ladder to react to I/
O errors.
This message is displayed when the “Reconfigurable Block I/O and continue to scan with Mas-
ter Rack, Block or ASIU failures” radio button is selected.
Click OK to close the message box and return to the dialog to continue editing. The radio button is
selected.
Click Cancel to close the message box and return to the dialog to continue editing. The radio but-
ton is not selected.
4058 HWD: TASK I/0 ERROR
This message is displayed when the attempt is made to compile a task with Remote Rack or Block
I/O modules declared.
4059 HWD: DOWNLOAD FAILURE CPU TYPE MISMATCH OBSOLETE CPU
A ladder that specifies a valid CPU has been compiled but the CPU in the control is obsolete.
•PiCTurbo2, part number 502-3814-00 with a 486DX processor is not compatible with PiCPro
Version 13.0 or later. Use PiCPro Version 12.x or earlier.
•All other PiC CPU models with a 186 or 486SX processor are not compatible with PiCPro
version 11.0 or later. Use PiCPro Version 10.x or earlier.
4060 HWD: DOWNLOAD FAILURE MMC/MMCPLUS CPU TYPE MISMATCH
An attempt has been made to compile and download a ladder with a MMC PLUS and one or more
MMC Analog Servo modules in slots 3 - 6 into a control, which has a MMC CPU.

4061 HWD: CONFIRM SWITCH PIC TO MMC PLUS
When you switch from a PiC CPU to a MMC PLUS CPU, slot 1 will be filled with MMC 2 or 4 axis
Analog Servo Module. Slot 2 will be filled with a MMC PLUS In/Out 24V DC Module. slots 3-6 will
be emptied. Slot 7 and up will be removed. All remote I/O will also be removed. Any Block I/O
defined will remain. You are asked to confirm this action.
rect.
4062 HWD: CONFIRM SWITCH MMC FOR PC ANALOG SERVO TO MMC PLUS
When you switch from a MMC for PC Analog Servo to a MMC PLUS, slot 1 will be filled with a MMC
Analog Servo Module. Slot 2 will be filled with a MMC PLUS In/Out 24V DC module. Slots 3 - 6 will
be added. All ASIU I/O will be removed. Any Block I/O defined will remain. You are asked to con-
firm this action.
Note: The I/O points defined in Software Declarations would be checked to ensure they are correct.
4063 HWD: CONFIRM SWITCH MMC FOR PC DIGITAL SERVO TO MMC PLUS
When you switch from a MMC for PC Digital Servo to a MMC PLUS, slot 1 will be filled with a MMC
Analog Servo Module. Slot 2 will be filled with a MMC PLUS In/Out 24V DC module. Slots 3 - 6 will
be added. All ASIU I/O will be removed. Any Block I/O defined will remain. You are asked to con-
firm this action.
4064 HWD: CONFIRM SWITCH MMC PLUS TO MMC
When you switch from a MMC PLUS, slot 1 will be filled with a MMC Analog Servo Module. Slot 2
will be filled with a MMC In/Out 24V DC module. Slots 3 and 4 will be emptied if they contain MMC
Analog Servo Modules. Slots 5 and 6 will be removed. Any Block I/O defined will remain. You are
4065 HWD: CONFIRM SWITCH MMC PLUS TO MMC FOR PC
When you switch from a MMC PLUS to MMC for PC, slot 1 will be filled with a MMC for PC CPU.
Slot 2 will be emptied. Slots 3 - 6 will be removed. Any Block I/O defined will remain. You are
4066 HWD: CONFIRM SWITCH MMC PLUS TO PIC
When you switch from a MMC PLUS to a PiC, slot 1 will be filled with a CSM Module. Slot 2 will be
filled with a PiC CPU. Slots 3 - 6 will be emptied. Slots 7 - 13 will be added. Any Block I/O defined
will remain. You are asked to confirm this action.
rect.
Ladder Error Messages
5000 COMPILE: INVALID TYPE

Data type mismatch. ‘Data type’ supplied. ‘Data type’ required.
The data type of the variable does not match the data type required.
Tip
Enter the correct data type.

5001 COMPILE: DOUBLE DEFINED
‘Label’: has already been defined as a Label, cannot use again.
The specified label you have entered is already defined in another network. Each label must be
unique.
Tip
Delete this label and enter a new label
5002 COMPILE: EMPTY NETWORK
Empty network not allowed.
Whenever an empty network is included in a ladder, an error message will appear. Delete the
empty network if it is not needed or enter the necessary ladder logic.
Example of Error
Network 2 is empty.
Note: If a network has a label assigned to it but no logic to execute (empty), the label will be ignored
and may cause an undefined label error message to appear. If you need the network (i.e. when
designing UDFBs), you can prevent this error by simply adding a horizontal wire in the empty net-
work. The error will be avoided and you will be able to successfully compile your UDFB.
Tip
Whenever an empty network is included in a ladder, an error message will appear.
Delete the empty network if it is not required.
Enter ladder logic.
5003 COMPILE: CONNECTION ERROR
DATA IN, DATA OUT, or CONSTANT must be directly connected to a function/function block.
Example of Error
The SUM DATA OUT variable is not connected to the ADD function.

Tips
To correct this error do one of the following:
Move the cell containing the DATA IN, DATA OUT, or CONSTANT to the function/function block
input or output.
Delete the cell containing the DATA IN, DATA OUT, or CONSTANT.
5004 COMPILE: FUNCTION ON LEFT RAIL
‘Function’: Function or Function Block cannot be directly connected to left rail.
You cannot connect a function/function block directly to the left power rail.
Example of Error
Incorrect Correct
Function incorrectly placed at left
Function correctly positioned.
power rail.
Tip
Function/function blocks can never be placed in the first column of your network. Reposition the
function/function block to column two or greater and make the appropriate connections.
5005 COMPILE: DELETED NETWORK CONTAINS TASK
Deleted Network contains a task and cannot be patched. A scan stopped, full module down-
load is required.
You cannot use the patch feature when you delete a network that contains a task.
Tip: Whenever you delete a network that contains a task, you must stop the scan and perform a full
download.
5006 COMPILE: NOT ENOUGH INPUTS
‘Function Name’: Function requires ‘#’ inputs, only ‘#’ supplied.
You have not supplied the correct number of required inputs for the function you are using.
Example of Error
An input at IN2 is required. Ensure that the correct number of inputs have been supplied to the func-
tion.

Tip
Ensure that the correct number of inputs has been supplied to the function.
5007 COMPILE: INPUT REQUIRED
Input required
Some function blocks have inputs that are required.
Example of Error
The IST input on the PID function block requires an input and none was entered.
Tip
Enter the required function block input
5008 COMPILE: NETWORK CONTAINS TASK
Modified network contains a task and cannot be patched. A scan stopped, full download is
required.
You cannot use the patch feature when you modify a network that contains a task. You must stop
the scan and perform a full download.
Tip
Whenever you make changes to a network that contains a task, you must stop the scan and perform
a full download.

5009 COMPILE: FUNCTION CONNECTION ERROR
Connection Error. Function or Function Block must be connected to each other by wires.
When connecting function/function blocks, you must leave at least one empty column between them
and connect the outputs of the first to the inputs of the second with wires or contacts/coils.
Example of Error
Do not place a second function/function block directly next to an existing one..
Incorrect Correct
NE function incorrectly placed directly
NE function correctly positioned and connected.
next to the AND function.
Tip
Function/function blocks cannot be directly connected to each other. Leave a column between them
and use wires or contacts/coils to make the required connection.
5010 COMPILE: VARIABLE REQUIRED
Variable name required.
DATA IN, DATA OUT, CONTACTS, and COILS all require variables or constants.
Example of Error
The name of the variable at the SUM output is missing.
Tips
You must enter a variable name declared with the appropriate data type to the DATA IN, DATA OUT,
or the CONTACT/COIL location. The DATA IN may have a constant entered in place of a variable
name. The data type for the contact/coil variable is always a boolean.
Note: Under the View | Options menu in User Preferences, you can choose to turn on Force Dec-
larations. PiCPro will then prompt you to declare a variable each time you are required to enter one.

5011 COMPILE: DATAOUT CONNECTION ERROR
Connection Error. DATA OUT cannot be connected to first output.
DATA OUT cannot be connected to the first output on a function/function block. The first output can
only be a contact/coil or a wire or left disconnected.
Example of Error
Incorrect Correct
The DATA OUT variable OKFLAG is incorrect. The set coil with variable name OKFLAG is an
example of a correct connection to the first output
of the ADD function.
Tip
A wire or a contact/coil can be connected to the first output (i.e. the OK) of a function/function block
if desired. You may choose not to make any connection to the first output if you do not need to
receive the output data.

5012 COMPILE: INVERT DATA TYPE WARNING
Data inversion not allowed on non-boolean data types. Input will not be inverted.
You can only invert boolean inputs on functions or function blocks. If you attempt to invert a non-
boolean input this warning will appear and the input will be treated as a Data In, not as a Data
Inverted.
Tips
Change input to be a boolean constant, variable, or wire.
Make the data input a Data In instead of Data Inverted.
Consider changing the data type of the non-boolean variable to boolean.
5013 COMPILE: BOOLEAN REQUIRED
Incorrect data type specified, boolean required.
A contact or coil has been assigned a variable name that is some other data type than the boolean
required.
Tips
Enter a valid boolean variable.
Declare variable as a boolean in the software declarations table.
5014 COMPILE: LABEL REQUIRED
Label required.
The label of the network you want to jump to with the Jump to Label or Jump to Subroutine com-
mands must be entered with the jump command.
Example of Error
The Jump to Label and the Jump to Subroutine entries require a label of the network the jump is
going to.
Incorrect Correct
No labels entered for the Jump to
Labels have been correctly entered with the
Label or Jump to Subroutine com-
Jump to Label and Jump to Subroutine com-
mands.
mands.
Tips
Ensure that you have assigned a label to the network you want to jump to.
or
Remove the Jump to Label or Jump to Subroutine entry.
5015 COMPILE: LABEL UNDEFINED
Label is not defined.
Network labels are required on Jump to Label and Jump to Subroutine commands. If you enter a
label that you have not assigned to a network, you will get this error.
Tips
Ensure that any network you want to jump to has a label assigned to it.
If you get this error after entering a label with the jump command, make sure the label exists and/
or check the spelling of the label to ensure it matches the label of the destination network.

5016 COMPILE: NPX REQUIRED
Requires a CPU with an NPX processor.
A warning appears when a variable name or constant has been defined with a data type that
requires a CPU with an NPX processor. The CPU currently declared in the Hardware Declarations
table does not have an NPX processor.
Tips
Declare a CPU with an NPX processor in the Hardware Declarations table.
or
Change the data type from REAL, LREAL, LINT, etc. to a data type that does not require a NPX
processor.
5017 COMPILE: INVALID BRANCH
Invalid branch.
An invalid branch has been attempted. Two or more wires/rungs may form a branch only if the data
types being passed on the wire are boolean.
Example of Error
Incorrect
An invalid branch is formed by the wires from the SUM outputs of the ADD functions going to the
IN1 input of the EQ function. The SUM outputs are non-boolean data types and cannot be branched
this way. Note: The OK outputs from the ADD functions could form a valid branch since they are
both boolean data types.
Correct
The correct method of branching the above example is shown below.

Tip
It is valid to branch as shown in the incorrect example above if the two branch sources are both
boolean data types.
5018 COMPILE: INTERNAL ERROR
An internal error has occurred. Please contact Sheffield Automation.
Tips
If you receive an internal error, take the following steps.
1 Write down the error number and the exact wording of the error message.
2 Note the version of software you are using.
3 Save your ladder file.
4 Send the above information, your ladder file and all related files to Sheffield Automation.
5019 COMPILE: INTERNAL LABEL NOT FOUND
Tips
5020 COMPILE: INTERNAL EMPTY LIST
Tips

5021 COMPILE: INTERNAL UNKNOWN ELEMENT
Tips
5022 COMPILE: INTERNAL NO TEMPLATE
Tips
5023 COMPILE: INTERNAL NO DESTINATION
Tips
5024 COMPILE: INTERNAL INVALID OUTPUT COUNT
Tips
5025 COMPILE: INTERNAL LDO ERROR
Tips

5026 COMPILE: INTERNAL INVALID DATA TYPE
Tips
If you receive an internal error, take the following steps:
5027 COMPILE: NO NETWORKS
Ladder does not contain any networks.
The ladder you are attempting to compile does not contain any networks.
Tips
Load a ladder that does contain networks.
Program network(s) into your ladder and compile again.
5028 COMPILE: INVALID ARRAY INDEX
Array index must be either UINT or USINT.
The data type of the index for an array must be either a USINT or UINT.
Tips
Use a variable or constant that is a USINT or UINT.
Change the variable’s data type to USINT or UNIT.
5029 COMPILE: PARAMETER ERROR
Parameter error.
The parameter does not meet the necessary requirements for this function or function block.
Tip
Review the documentation associated with the function/function block you are working with and cor-
rect the input.
5030 COMPILE: INVALID CONSTANT

Invalid constant. Constant value must be in the range ‘#’ to ‘#’.
Example of Error
The constant 40 at the NUM input (declared as a WORD) of the ROR function is out of range for this
input. The valid range is from 0 to 31.
Tip
Ensure that the value you enter as a constant is within the required range. The range is based on
the number of bits specified for the data type.

Range if IN data type is less than Range if IN data type = 8
8 bytes bytes
(BYTE, WORD, or DWORD) (LWORD)
0 - 31 0 - 63
5031 COMPILE: TASK IN FUNCTION

Tasks may not be called from within functions.
You have attempted to call a task from within a UDFB.
Tip
Program a task within the main ladder only.
5032 COMPILE: TOO MANY TASK INPUTS
Too many task inputs specified. Task inputs SERV, HDWR, and SYST are mutually exclusive.
Only one may be specified.
Task inputs SERV, HDWR, and SYST are mutually exclusive. You may specify only one of these
inputs for a task.
Example of Error
Incorrect Correct
All three TASK inputs (SERV,
Only one TASK input has been
HDWR, and SYST) have been
entered.
entered.
Tip
Select only one of three inputs for a task function block,
5033 COMPILE: TASK INPUT REQUIRED

An input is required at one of the task inputs.
You have not connected any input at any of the task inputs of SERV, HDWR, or SYST.
Example of Error
Incorrect Correct
None of the three TASK inputs
One TASK input must be entered.
(SERV, HDWR, and SYST) has
been entered.

Tip
Connect one input on the task function block depending on whether your task is a servo, hardware,
or system interrupt task.
5034 COMPILE: DATA IN REQUIRED
Input must be DATA IN or DATA INVERTED.
When you want to use an I/O point to trigger a hardware interrupt task, the HDWR input of the task
function block must be data in or data inverted. Never program a wire or contact for this input.
Example of Error
Incorrect Correct
A wire has been connected to the
Data In and the variable IN1 has been
HDWR input of the TASK function
entered at the HDWR input of the
block.
TASK function block.
Tips
Enter DATA IN or DATA INVERTED for the HDWR input of the task function block.
or
Convert the wire or contact to a DATA IN or DATA INVERTED.
5035 COMPILE: MAX IO EXCEEDED
The number of function block inputs or outputs exceed 64.
Tips
2 Note the version of the software you are using.

5036 COMPILE: BAD TASK SERV
Input must be one of the following constants: T#1MS, T#2MS, T#4MS, T#8MS or T#16MS.
When you want to trigger a servo interrupt task, the SERV input of the task function block must be
one of these servo time tick constants: T#1MS, T#2MS, T#4MS, T#8MS or T#16MS.
Example of Error
Incorrect Correct
An invalid constant has been
One of the valid servo time ticks has
entered for the SERV input of the
been entered at the SERV input of the
Tip
Enter T#1MS, T#2MS, T#4MS, T#8MS or T#16MS at the SERV input of the task function.
5037 COMPILE: MAIN RACK ONLY

I/O point must be from main rack only.
Tasks can only access I/O modules located in the main rack.
Tip
Enter only an I/O point from an I/O module in the main rack to trigger a hardware interrupt task.
5038 COMPILE: IO POINT REQUIRED
I/O point required.
When you want to use an I/O point to trigger a hardware interrupt task, you must enter the I/O point
at the HDWR input of the task function block.
Tip
Enter an I/O point at the HDWR input of the task function block
5039 COMPILE: INPUT REQUIRES BOOLEAN VARIABLE
Boolean variable required.
A constant was entered as an input and a boolean variable is required.
Tip
Enter an boolean variable instead of a constant.
5101 COMPILE: INVALID USE OF KEYWORD
Keyword cannot be used as a variable name.
A keyword variable was found in a Structured Text statement. Keywords are not allowed as variable
names and cannot be used as variable names in Structured Text statements. Change the name of
this variable in software declarations.
Tip
Replace keyword with a variable that is not a keyword.

5102 COMPILE SYNTAX ERROR
Syntax Error.
The structured text syntax entered does not match the rules for structured text statements. Verify
the statement or expression where the error occurred to make sure that it is syntactically correct.
Tip
Double-click on the error message and examine the statement were the error has occurred. If in an
expression make sure that:
• a “)” is not missing.
• an operator is not missing.
If in a structured text statement make sure that an extra keyword or that a keyword was not used out
of context.
Correct the syntax error and then recompile.
5103 COMPILE: INVALID ASSIGNMENT STATEMENT
Missing or Invalid assignment statement.
The assignment statement used to form a FOR loop is not syntactically correct.
Tip
Enter a correct assignment statement in the FOR loop.
5104 COMPILE: EXIT OUTSIDE LOOP
EXIT statement used outside of loop.
Exit statements can only be used within an iteration statement.
Tip
Delete the EXIT statement or move within an iteration statement.
5105 COMPILE: NO MATCHING WHILE
END_WHILE without a matching WHILE statement.
An END_WHILE statement was encountered that does not have a matching WHILE statement.
Tip
Delete the END_WHILE statement.
5106 COMPILE: NO MATCHING REPEAT
UNTIL or END_REPEAT without a matching REPEAT statement.
An UNTIL or END_REPEAT statement was encountered that does not have a matching REPEAT
statement.
Tip
Delete the UNTIL or END_REPEAT statement.
5107 COMPILE: NO MATCHING FOR
END_FOR without a matching FOR statement.
An END_FOR statement was encountered that does not have a matching FOR statement.
Tip
Delete the END_FOR statement.

5108 COMPILE: NO MATCHING IF
ELSIF, ELSE, or END_IF without a matching IF statement.
An ELSIF, ELSE or END_IF statement was encountered that does not have a matching IF statement.
Tip
Delete the ELSIF, ELSE, or END_IF statement.
5109 COMPILE: UNEXPECTED KEYWORD

Unexpected Keyword found - TO, THEN, DO, NOT, OR, XOR, AND.
Keyword is used out of context.
Tip
Delete the keyword entered or fix the syntax error associated with this keyword.
5110 COMPILE: NESTING ERROR #1

Nesting error - Expecting UNTIL-END_REPEAT before END_WHILE.
Structured Text statements can be nested inside other structured statements. A statement that is
nested within another statement must be entirely within the outer most statement. No overlapping of
statements are allowed.
Example of Error:
Incorrect: Correct:
WHILE A DO WHILE A DO
REPEAT REPEAT
END_WHILE; UNTIL B END_REPEAT;
UNTIL B END_REPEAT; END_WHILE;
Tip
Ensure that the REPEAT statement is entirely within the WHILE statement as the Correct example
illustrates above.
Nesting error - Expecting END_FOR before END_WHILE.
Example of Error:
Incorrect: Correct:
FOR I=0 TO 5 DO FOR I=0 TO 5 DO
END_WHILE; END_FOR;
END_FOR; END_WHILE;
Tip
Ensure that the FOR statement is entirely within the WHILE statement as the Correct example illus-
trates above.

Nesting error - Expecting ELSIF, ELSE, or END_IF before END_WHILE.
Example of Error:
Incorrect: Correct:
IF B THEN IF B THEN
END_WHILE; END_IF;
END_IF; END_WHILE;
Tip
Ensure that the IF statement is entirely within the WHILE statement as the Correct example illustrates
above.

Nesting error - Expecting END_WHILE before UNTIL-END_REPEAT.
Example of Error:
Incorrect: Correct:
REPEAT REPEAT
UNTIL B END_REPEAT; END_WHILE;
END_WHILE; UNTIL B END_REPEAT;
Tip
Ensure that the WHILE statement is entirely within the REPEAT statement as the Correct example
illustrates above.

Nesting error - Expecting END_FOR before UNTIL-END_REPEAT.
Example of Error:
Incorrect: Correct:
REPEAT REPEAT
FOR I := 0 TO 5 DO FOR I := 0 TO 5 DO
UNTIL B END_REPEAT; END_FOR;
END_FOR; UNTIL B END_REPEAT;
Tip
Ensure that the FOR statement is entirely within the REPEAT statement as the Correct example illus-
trates above.

Nesting error - Expecting ELSIF, ELSE, or END_IF before UNTIL-END_REPEAT
Example of Error:
Incorrect: Correct:
REPEAT REPEAT
IF B THEN IF B THEN
UNTIL B END_REPEAT; END_IF;
END_IF; UNTIL B END_REPEAT;
Tip
Ensure that the IF statement is entirely within the REPEAT statement as the Correct example illus-
trates above.

Nesting error - Expecting END_WHILE before END_FOR
Example of Error:
Incorrect: Correct:
END_FOR; END_WHILE;
END_WHILE; END_FOR;
Tip
Ensure that the WHILE statement is entirely within the FOR statement as the Correct example illus-
trates above.

Nesting error - Expecting UNTIL-END_REPEAT before END_FOR.
Example of Error:
Incorrect: Correct:
REPEAT REPEAT
END_FOR; UNTIL B END_REPEAT;
UNTIL B END_REPEAT; END_FOR;
Tip
Ensure that the REPEAT statement is entirely within the FOR statement as the Correct example illus-
trates above.

Nesting error - Expecting END_IF before END_FOR.
Example of Error:
Incorrect: Correct:
IF A THEN IF A THEN
END_FOR; END_IF;
END_IF; END_FOR;
Tip
Ensure that the IF statement is entirely within the FOR statement as the Correct example illustrates
above.
Nesting error - Expecting END_WHILE before END_IF.
Example of Error:
Incorrect: Correct:
IF A THEN IF A THEN
WHILE B DO WHILE B DO
END_IF; END_WHILE;
END_WHILE; END_IF;
Tip
Ensure that the WHILE statement is entirely within the IF statement as the Correct example illustrates
above.

Nesting error - Expecting UNTIL END_REPEAT before END_IF.
Example of Error:
Incorrect: Correct:
IF A THEN IF A THEN
REPEAT REPEAT
END_IF; UNTIL B END_REPEAT;
UNTIL B END_REPEAT; END_IF;
Tip
Ensure that the REPEAT statement is entirely within the IF statement as the Correct example illus-
trates above.

Nesting error - Expecting END_FOR before END_IF
Example of Error:
Incorrect: Correct:
IF A THEN IF A THEN
END_IF; END_FOR;
END_FOR; END_IF;
Tip
Ensure that the FOR statement is entirely within the IF statement as the Correct example illustrates
above.
5122 COMPILE: MISSING MATCHING CASE

END_CASE without a matching CASE statement.
An END_CASE statement was encountered that does not have a matching CASE statement.
Tip
Delete the END_CASE statement.

Nesting error - Expecting END_CASE before END_WHILE.
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
1..10: 1..10:
SPEED := SPEED + 10; SPEED := SPEED + 10;
END_WHILE; END_CASE;
END_CASE; END_WHILE;
Tip
Ensure that the CASE statement is entirely within the WHILE statement as the Correct example illus-
trates above.

Nesting error - Expecting END_CASE before UNTIL-END REPEAT.

Example of Error:
Incorrect: Correct:
REPEAT REPEAT
CASE A OF CASE A OF
1..10: 1..10:
UNTIL A END_REPEAT; END_CASE;
END_CASE; UNTIL A END_REPEAT;
Tip
Ensure that the CASE statement is entirely within the REPEAT statement as the Correct example
illustrates above.

Nesting error - Expecting END_CASE before END_FOR.
Example of Error:
Incorrect: Correct:
FOR I:=0 TO 5 DO FOR I:=0 TO 5 DO
CASE A OF CASE A OF
1..10: 1..10:
END_FOR; END_CASE;
END_CASE; END_FOR;
Tip
Ensure that the CASE statement is entirely within the FOR statement as the Correct example illus-
trates above.

Nesting error - Expecting END_CASE before END_IF.
Example of Error:
Incorrect: Correct:
IF A THEN IF A THEN
CASE A OF CASE A OF
1..10: 1..10:
END_IF; END_CASE;
END_CASE; END_IF;
Tip
Ensure that the CASE statement is entirely within the IF statement as the Correct example illustrates
above.
Nesting error - Expecting END_WHILE before END_CASE or CASE selector
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
1..10: 1..10:
WHILE B DO WHILE B DO
END_CASE; END_WHILE;
END_WHILE END_CASE;
Tip
Ensure that the WHILE statement is entirely within the CASE statement as the Correct example illus-
trates above.
Nesting error - Expecting UNTIL-END_REPEAT before END_CASE or CASE selector.
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
1..10: 1..10:
REPEAT REPEAT
END_CASE; UNTIL A END_REPEAT;
UNTIL A END_REPEAT; END_CASE;
Tip
Ensure that the REPEAT statement is entirely within the CASE statement as the Correct example
illustrates above.

Nesting error - Expecting END_FOR before END_CASE or CASE selector.

Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
1..10: 1..10:
FOR I:=0 TO 5 FOR I:=0 TO 5
END_CASE; END_FOR;
END_FOR; END_CASE;
Tip
Ensure that the FOR statement is entirely within the CASE statement as the Correct example illus-
trates above.

Nesting error - Expecting END_IF before END_CASE or CASE selector.
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
1..10: 1..10:
IF A THEN IF A THEN
END_CASE; END_IF;
END_IF; END_CASE;
Tip
Ensure that the IF statement is entirely within the CASE statement as the Correct example illustrates
above.
5131 COMPILE: MISSING SELECTOR

Missing or expecting CASE selector
A CASE selector must immediately follow the OF in the case statement.
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
SPEED := SPEED + 10; 1..10:
END_CASE; SPEED := SPEED + 10;
END_CASE;
Tip
Add missing CASE selector.

5132 COMPILE: MISSING INTEGER
Missing Integer.
In the example below an integer number should appear after the “,” in the CASE Selector.
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
1,: 1,2:
END_CASE; END_CASE;
Tip
Either eliminate the extra comma or add integer number to the CASE selector.
5133 COMPILE: MISSING PARAMETER

Missing Function/Function Block Parameter.
Two commas right next to each other as illustrated in the example below is a syntax error and implies
that a function/function block parameter is missing.
Example of Error:
Incorrect:
MAX(IN1:=A, ,IN2:=B);
Tip
Remove the extra comma or add another function/function block parameter between the commas.
5134 COMPILE: INVALID CONSTANT

Invalid Hex, Octal or Binary Constant.
An invalid character was used in a Hex, Octal, or a binary constant. See the manual for the proper
syntax of these constants.
Example of Error:
16#G1AF is an invalid Hex constant because it contains the letter G.
Tip
• Verify that the hex number only contains the digits 0-9 and the letters A-F.
• Verify that the octal number only contains the digits 0-7.
• Verify that the binary number only contains the digits 0-1.
Make appropriate changes.
5135 COMPILE: EXPRESSION SYNTAX ERROR

Expression syntax error.
The structured text syntax entered does not match the rules for structured text statements. Verify the
expression where the error occurred to make sure that it is syntactically correct.
Tip
Double-click on the error message and examine the statement where the error has occurred. Ensure
that:

5136 COMPILE: MISSING CLOSE COMMENT
Missing closing comment indicator "*)".
A comment start “(*” was encountered that does not have a matching comment end “*)”.
Tip
Find the end of comment and add “*)”.
5137 COMPILE: EXPECTING INTEGER

Expecting Integer.
Non-Integer constant value entered where an Integer constant value is expected. In the example
below, B should be an integer constant. Only integer constants are allowed in CASE selectors.
Example of Error:
Incorrect:
CASE A OF
1,B:
SPEED := SPEED + 10;
END_CASE;
Tip
Enter only an Integer constant or delete the characters that caused the error.
5138 COMPILE: INVALID CASE EXPRESSION

Invalid CASE expression.
The structured text syntax for the entered CASE expression does not match the rules for structured
text statements. Verify the expression where the error occurred to make sure that it is syntactically
correct.
Tip
Double click on the error message and examine the statement where the error has occurred. Ensure
that:
5139 COMPILE: EXPECTING VARIABLE

Expecting variable or parameter name to the left of ":=" or "=>".
Example of Error:
FOR := 0 TO 5
;
END_FOR;
In the above example the assignment variable is missing.
Tip
Add the missing variable or parameter name to the left of the “:=” or “=>”.

5140 COMPILE: MISSING FOR ASSIGNMENT
Missing assignment statement that initializes the iteration variable in a FOR loop.
As illustrated in the example below the assignment statement used to initialize the loop counter
(LOOP vs. LOOP:=0) is missing or incomplete.
Example of Error:
Incorrect: Correct:
FOR LOOP TO 5 FOR LOOP:=0 TO 5
; ;
END_FOR; END_FOR;
Tip
Enter a complete assignment statement for the loop counter.
5141 COMPILE: FUNCTION BLOCK RESYNC

Syntax error in Function/Function block parameter.
The structured text syntax entered does not match the rules for structured text Function/Function
Block parameters. Verify the statement or expression where the error occurred to make sure that it is
syntactically correct.
Tip
Double-click on the error message and examine the statement where the error has occurred. The
offending characters will be highlighted.
• Ensure that “,” follows the Function/Function Block parameter.
• If error occurs right after an expression, verify the expression for accuracy.
5142 COMPILE: INVALID ASSIGNMENT

Invalid expression assignment statement.
Tip
5143 COMPILE: FUNCTION BLOCK PARAMETER ERROR

Expression must be assigned to a Function/Function Block input or output parameter name
using ":=" or "=>".
The input or output parameter used in a function or function block is incomplete. The parameter
name and “:=” or “=>” are missing.
Tip
Enter the complete function or function block parameter (i.e., IN0:=A+1 or OUT1=>B).

5144 COMPILE: STATEMENT SYNTAX ERROR
Statement syntax error.
The structured text syntax entered does not match the rules for structured text statements. Verify the
statement or expression where the error occurred to make sure that it is syntactically correct.
Tip
Double-click on the error message and examine the statement where the error has occurred. If in an
expression make sure that:
If in a structured text statement, that user makes, an extra keyword does not exist or that a keyword
was not used out of context
5145 COMPILE: MISSING EXPRESSION

Missing or incomplete expression.
A required expression is missing in a ST statement. In example #1 the assignment statement does
not have an expression. In example #2 the MAX function is missing an expression after “IN1 :=”.
Example of Error #1
A := ;
Example of Error #2
MAX(IN1:=, IN2:=A, OUT1=>B);
Tip
Enter an expression.
5146 COMPILE: NEGATIVE SUBSCRIPT

Array subscripts cannot be negative.
Array subscripts cannot be negative and must be in the range 0 and 998, inclusive. Therefore, the
negative sign is not permissible on an array subscript.
Tip
Ensure that the array subscript is between 0 and 998.
5147 COMPILE: NEGATIVE CONSTANT

Unary operator ("-") not allowed on this constant.
The unary operator “-“ is not valid on constants that begin with 16# (Hex), 8# (Octal), 2# (Binary),
TOD# (Time of Day), DT# (Date and Time), and T# (Time).
Tip
Enter a valid constant value by removing the unary operator “-“.
5148 COMPILE: POWER OPERATOR NOT SUPPORTED

The operator Raise to Power ("**") is not currently supported.
The operator Raise to Power ("**") is not currently supported in PiCPro but may be supported in a
future release of PiCPro.
Tip
Replace Raise to Power ("**") operator with an expression that performs that same calculation .

5160 COMPILE: NO PARSER INTERFACE
INTERNAL ERROR: Failed to initialize/obtain parse engine interface.
Tip
5161 COMPILE: NO GRAMMAR FILE

Cannot continue with compile. Missing internal system file "filename".
Tip
5162 COMPILE: PARSER SYNCH ERROR

INTERNAL ERROR: Parser is out of sync with parse tree in routine "%s".
Tip
5163 COMPILE: BY 0 NOT ALLOWED

Constant value of 0 not allowed after BY. Value produces infinite loop.
Specifying a constant value of 0 after the BY in a FOR loop is not allowed. Allowing this would cause
an infinite loop that would scan loss the control.
Tip
Enter a non-zero constant value after the BY in the FOR loop.
5164 COMPILE: DUPLICATE SELECTOR VALUE OR RANGE

Duplicate selector value or selector range overlaps with a previous selector.
The selector values or range of values used in a CASE statement must be unique and cannot over-
lap.

Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
2: 2:
1..10: 1, 3..10:
END_CASE; END_CASE;
Tip
Ensure that no selector values overlap and change accordingly.
5165 COMPILE: SELECTOR RANGE OUT OF ORDER

Selector range values should be from lowest to highest.
When specifying a selector range, the range must be lowest value first then highest value.
Example of Error:
Incorrect: Correct:
CASE A OF CASE A OF
10..1: 1..10:
END_CASE; END_CASE;
Tip
Ensure that the range is lowest value first then highest value. Typically, all that needs to be done is to
reverse the range values.
5166 COMPILE: FUNCTION MUST RETURN VALUE

Function must return a value to be used in an expression.
Functions that do not return a result, such as STEPCNTL, cannot be called directly from an expres-
sion. Functions that fall into this category must be invoked as independent standalone ST instruc-
tions that have similar syntax to a function block call.
Tip
Remove the function call from the expression and use function block syntax to make the function call.
Results from the function call can then be used in the expression.
5167 COMPILE: TOO MANY FUNCTION OUTPUTS

Functions that contain multiple output values cannot be used in an expression.
Functions such as MOVE and BY2TBOOL have multiple outputs. These functions cannot be called
directly from any expression. Functions that fall into this category must be invoked as independent
standalone ST instructions that have similar syntax to a function block call. In this case, function out-
put parameters are typically specified.
Tip
Remove the function call from the expression and use function block syntax to make the function call.
Results from the function call can then be used in the expression.

5168 COMPILE: FUNCTION UNDEFINED
Function, Function Block, or Function Block title is not defined.
The specified Function, Function Block, instance name, or title is not defined.
Tip
• Check the spelling of the Function, Function Block, instance name, or title.
• Ensure that the specified Function or Function Block is in a library (.lib) that is defined in the
PiCPro Libraries path.
5169 COMPILE: FUNCTION BLOCK TITLE MISMATCH

":Function Block Title" syntax cannot be used with Functions. Ignoring......
The syntax “Function Block instance name:Function Block title” is only valid with Function Blocks.
Specifying this syntax with a Function is an error.
Tip
Remove “:Function Block Title” from the specified function call.
5170 COMPILE: FUNCTION BLOCK IN EXPRESSION

Function Blocks cannot be used with an expression.
Only Functions can be called from an expression. Function Blocks cannot be called from an expres-
sion. Function Block calls are independent standalone statements in ST. The results from a Function
Block call can be used in any expression.
Tip
Remove the Function Block call from the expression and make the call to the Function Block a stan-
dalone ST statement. If necessary, use results from the Function Block call in an expression.
5171 COMPILE: FUNCTION PARAMETER ALREADY SPECIFIED

Input/Output parameter was already specified.
A Function or Function block parameter input or output can only be specified once per Function or
Function Block call. The specified parameter name was already specified for this Function or Func-
tion Block.
Tip
Remove either of the duplicated parameter names.
5172 COMPILE: FUNCTION I/O PARAMETER NOT DEFINED

Input/Output parameter is not defined for this Function or Function Block.
The specified input or output parameter name is not defined for this function. Verify this name against
the definition.
Tip
• Check the spelling of the input or output name.
• Replace the specified input or output name with a valid input or output name.
5173 COMPILE: FUNCTION OUTPUT NOT ALLOWED

Cannot specify an output parameter on a function used within an expression.
When a Function is specified in an expression, output parameters cannot used. The results from the
function call are directly used in the expression.
Tip
Remove all output parameters from this Function call.

5174 COMPILE: NOT DEFINED AS FUNCTION BLOCK
Not defined as a Function Block.
The specified variable is not defined as a function block in software declarations.
Tips
• Check the spelling of the variable name.
• Replace specified variable with one that is defined as a function block.
5175 COMPILE: BAD FUNCTION BLOCK TITLE

Function Block Title entered does not match definition. Ignoring......
The specified function block title does not match the function block title defined in software declara-
tions for the specified function block instance name.
Tips
• Change Function Block title so it matches definition in software declarations.
• Ensure that the right function block instance name is specified.
5176 COMPILE: VARIABLE REQUIRES SUBSCRIPT

Variable is defined as an array and requires an array subscript.
The specified variable is defined as an array and requires an array subscript.
Tips
• Add array subscript to variable.
• Verify spelling of variable name.
5177 COMPILE: STRUCTURE UNDEFINED

Variable is not defined or data type of defined variable is not a structure.
The variable is not defined as a structure in software declarations or is not defined at all.
Tips
• Define the specified variable as a structure.
• Replace specified variable with one that is defined as a structure.
5178 COMPILE: VARIABLE UNDEFINED

Variable is not defined.
The specified variable is not defined in software declarations.
Tips
• Define the specified variable.
• Replace specified variable with one that is defined.

5179 COMPILE: VARIABLE NOT AN ARRAY
Variable is not defined as an array.
The specified variable is used as an array but is not defined as an array in software declarations.
Tips
• Remove the array subscript
• Define the specified variable as an array.
• Replace specified variable with a defined array name.
5180 COMPILE: STRUCTURE ELEMENT UNDEFINED

Structure Element is not defined.
The specified structure element name is not defined in software declarations.
Tips
• Check the spelling of the element name.
• Define the specified element name.
• Change the specified element name to one that is already defined.
5181 COMPILE: SUBSCRIPT OUT OF RANGE

Constant value for array subscript is out of range. Range values are 0 to 998.
Array constants must be between 0 and 998.
Tip
Ensure that the constant value specified for the array subscript is between 0 and 998.
5182 COMPILE: REQUIRED INPUT NOT SPECIFIED

"Input Parameter Name" - Required input not specified.
There are certain input parameters in a function or function block that are required and are not
optional. These parameters must be specified when calling this function or function block.
Tip
Enter the required function or function block parameter.
5183 COMPILE: MISUSED RELATIONAL OPERATOR

A logical operator (OR, XOR, or AND) must be used to separate expressions containing differ-
ent relational operators.
Expressions such as:
A<B<C<D
Is legitimate in our implementation of ST, while the expression:
A<B<C>D
Is invalid in our implementation of ST. To correct the second expression, it should be rewritten as:
A < B < C AND C > D
The basic rule of thumb is all operands in a relational expression must use the same relational opera-
tor. If more than one relational operator is required to form the expression then a logical expression
must be used.
Tip
Separate into two or more relational expressions and separate with a logical operator.

5184 COMPILE: BAD CONSTANT
Invalid constant, value too large or improperly formed.
The constant entered is either syntactically incorrect or is too large. For more information about con-
stant syntax rules, see the manual.
Tip
Ensure that the constant entered is syntactically correct and within the range of the data type.
5185 COMPILE: CANNOT INTERMIX OPERATORS

Cannot intermix logical operators with arithmetic operators. Resultant data types do not
match.
Example of Error:
D : = A + 5 AND B + C;
If A and B are defined as integers, then this statement does not make logical sense and results in this
error.
Tip
Ensure that logical operators and arithmetical operators do not get intermixed in the same expres-
sion.
5186 COMPILE: INTERNAL PARSER ERROR

INTERNAL ERROR: In first Pass of Structure Text. Report error code - "%d"
Tip
5187 COMPILE: MISSING TERM

Missing “term”
In parsing a ST network the expected next term was not present.
Example
WHILE DO
Note in the example above that the expression in the WHILE is missing and the END_WHILE state-
ment is missing. This example will generate 2 errors: Missing “expression” and Missing
“END_WHILE”.
Tip
Review the syntax of the statement that has the error and then add in the missing term.

5188 COMPILE: BAD ERROR NUMBER
INTERNAL ERROR: Error number out of range: %s.
Tip
5189 COMPILE: NETWORK CODE SIZE EXCEEDED

Exceeded network code size limit. Limit is 4095, Actual is %s.
The binary code generated for any given network within a ladder is limited to 4095 bytes. If you
receive this error the offending network must be split into 2 or more networks.
Tip
Split network into 2 or more networks.
5190 COMPILE: VARIABLE NAME TOO LONG

Variable names are limited to 63 characters.
A variable name as defined in software declarations is limited to 63 characters. The variable name
entered contains more than 63 characters. See the manual for the syntax rules of a variable name.
Tip
Reduce the size of the variable name entered to 63 characters or less.
5191 COMPILE: FUNCTION NAME TOO LONG

Function name or Function Block title is limited to 8 characters.
Function names and Function Block titles are limited to 8 characters. The name entered contains
more than 8 characters.
Tip
Reduce the size of the Function name or Function Block title to 8 characters or less.
5192 COMPILE: INVALID FUNCTION BLOCK NAME

Function Block instance name contains an invalid character.
Function Block instance names can only consist of characters that are alphanumeric or contain an “_”
(underscore). Characters not part of this set cause this error. For more information about Function
Block instance name syntax rules see the manual.
Tip
Delete the invalid characters and verify that the Function Block instance name is not misspelled.
5193 COMPILE: UNDEFINED FUNCTION BLOCK INSTANCE NAME

Function Block variable/instance name is not defined.
The specified Function Block instance name is not defined in software declarations.
Tip
Verify the Function Block instance name is not misspelled. If misspelled, correct the spelling; other-
wise, define the Function Block instance name in software declarations.

5194 COMPILE: FUNCTION INPUT NOT ALLOWED
Function input parameter "EN" is not allowed in a ST network function call.
When invoking a Function in a ST network, the input parameter enable (i.e., EN) should not be spec-
ified. Functions in a ST network always execute unless there is conditional code around the Function
call.
Example:
IF INPUT1 THEN
B := MAX(IN1:=C, IN2:=D);
END_IF;
Tip
Delete this parameter from the Function call and if necessary, add a conditional statement around the
Function call to conditionally execute the function.
5195 COMPILE: COUNTDOWN FOR NOT ALLOWED

Countdown FOR loop is not allowed when data type is unsigned.
Countdown FOR loops are not permissible when the data type specified for the counter variable is
USINT, UINT, UDINT, or ULINT.
Tips
• Change the data type used for the counter in the FOR loop to be SINT, INT, DINT, or LINT.
• Change the conditions of the FOR loop to count up versus counting down.
• Change the constant after BY to be positive.
• Consider using a WHILE loop instead of a FOR loop. Most FOR loops can be easily converted
into a WHILE loop.
7002: FUNCTION REQUIRES NPX
Function _ requires numeric coprocessor
requires a CPU with an NPX processor to process and the CPU declared in the Hardware Declara-
tions table does not have an NPX processor.
Tips
processor.
7003: LIBRARY NOT FOUND
_ was not found.
When PiCPro scanned the libraries, it found a library which it cannot now open to retrieve functions
for compiling. Possibly the library has been deleted or renamed with Windows Explorer while
PiCPro was running. The library has to be found for the compile to be successful.
Tips
Check the library paths.
Go to the libraries dialog and click OK to rescan the libraries.
Do not make any changes to the library paths or directories from outside of PiCPro when PiCPro
is running.

7004: TASK IO CONFLICT
Task _ contains an I/O board conflict.
The I/O used by this task cannot be different than the I/O specified by the main module.
Tip
Compare the hardware declarations for this task module and for the main module and ensure that
the I/O declared is the same.
9001 COMPILE: NPX REQUIRED
Incompatible Variable _/_/_. Use of _ type requires a CPU with an NPX processor.
requires a CPU with an NPX processor to process and the CPU declared in the Hardware Declara-
tions table does not have an NPX processor.
Tips
processor.
9002 COMPILE: NEW STRUCTURE MEMBER
‘__.__’ is a new structure member that cannot be properly assigned. A scan stopped, full
module download is required.
If you add a new member to an existing structure, you must perform a full download with the scan
stopped in order for PiCPro to recognize the new member.
9003 COMPILE: MODIFIED STRUCTURE MEMBER
‘__.__’ is an existing structure member that has been modified. A scan stopped, full module
download is required.
If you modify an existing structure member, you must perform a full download with the scan stopped
in order for PiCPro to recognize the modification.
9004 COMPILE: FUNCTION MODIFIED
‘__’ is an existing function block instance that has been modified. A scan stopped, full mod-
ule download is required.
If you modify a function block, you must perform a full download with the scan stopped in order for
PiCPro to recognize the modification.
9005 COMPILE: INVALID ATTRIBUTE
Invalid symbol attribute in ‘__’.
There is an invalid symbol attribute in the software declaration table.
Tip
Ensure that the attributes you assign to any variable in the software declarations table is valid.
9006 COMPILE: SYMBOL MODIFIED
‘__’ is an existing variable that has been modified. A scan stopped, full module download is
required.
If you modify an existing variable, you must perform a full download with the scan stopped in order
for PiCPro to recognize the modification.
9007 COMPILE: NEW RETAINED
‘_____’ is a new RETAINED variable that cannot be properly assigned. A scan stopped, full
module download is required.
If you enter a new variable with the retained attribute, you must perform a full download with the
scan stopped in order for PiCPro to recognize the new retained variable.

9008 COMPILE: FUNCTION INITIALIZATION REQUIRED
‘_____’ calls for initialization. A remake of this library function is required, along with a full
module download.
If you make changes that require initialization i.e. change initial values, add function/function blocks,
declarations, (Note: strings always require initialization), you must recompile the function block and
perform a full module download.
Tips
Whenever a change is made that requires initialization, you must:
Recompile the function block.
Download the module.
9009 COMPILE: NEW/MOVED INPUT/OUTPUT
A new/moved input/output ‘____’ cannot be added in a patch. A remake of this library is
required, along with a full download.
You have attempted to patch the module after adding a new or moving an existing input or output.
This requires that you recompile the module and perform a full download.
Tip
Select Compile | Bin File | Compile & Download from the menu.
9010 COMPILE: I/O NOT AN INPUT
‘_____’ calls for an input point ‘____’ in rack ‘____’ slot ‘____’ which is not configured.
The hardware configuration defined by the hardware declarations table is compared to the software
configuration when a module is compiled. PiCPro will detect an error if you attempt to define an
input point at an output location.
Tip
Ensure that discrete I/O points declared in software match the hardware declarations.
9011 COMPILE: I/O NOT AN OUTPUT
‘_____’ calls for an output point ‘____’ in rack ‘____’ slot ‘____’ which is not configured.
configuration when a module is compiled. PiCPro will detect an error if you attempt to define an out-
put point at an input location.
Tip
9012 COMPILE: CANNOT FIND FUNCTION
Unable to locate function block ‘____’ in the function/ block libraries.
The function block cannot be found in the function/block libraries.
Tip
Compile the function block and designate the library it should be stored in.
9013 COMPILE: INSUFFICIENT DATA MEMORY
Out of data memory. Out of memory error. Your program requires more memory than is avail-
able in the Control CPU.
You have reached the memory limits on your current system.
9014 COMPILE: INPUT NOT ALLOWED
‘_____’, input not allowed in TASK.
The input you have entered is not allowed in a TASK.
Tip
Do not mark any variables in the software declarations table with the Variable In attribute in a task
ladder.

9015 COMPILE: OUTPUT NOT ALLOWED
‘_____’, output not allowed in task.
The output you have entered is not allowed in a task.
Tip
Do not mark any variables in the software declarations table with the Variable Out attribute in a task
ladder.
9016 COMPILE: FIRST IN IS NOT A BOOLEAN
‘_____’, the first input, is not a BOOLEAN.
UDFBs require that the first input be a boolean.
Tip
Enter the BOOL data type in the software declarations table for the first input to your UDFB.
9017 COMPILE: FIRST OUTPUT IS NOT A BOOLEAN
‘_____’, the first output, is not a BOOLEAN.
UDFBs require that the first output be a boolean.
Tip
Enter the BOOL data type in the software declarations table for the first output to your UDFB.
9018 COMPILE: INVALID FUNCTION INPUT
‘_____’ is an invalid function INPUT.
Inputs to UDFB can be any data type except function blocks.
9019 COMPILE: INVALID FUNCTION OUTPUT
‘_____’ is an invalid function output.
Outputs to UDFBs can be any data type except function blocks, structures, arrays, and strings.
9020 COMPILE: EXTERNAL INITIAL VALUE IGNORED
Initial value for EXTERNAL ‘_____’ is ignored.
An initial value was entered for a variable with an EXTERNAL attribute. PiCPro ignores that value.
Tip
Since UDFBs cannot have any variables marked EXTERNAL, do not apply this attribute to any
UDFB variable, nor enter an initial value for it.
9022 COMPILE: NO BOOLEAN INPUTS
No UDFB Variable In attributes.
The first input to the UDFB must be a boolean and it must be assigned the Variable In attribute in
the software declarations table.
Tip
When creating an UDFB, ensure in the software declarations table that the first input:
Is a boolean.
Is assigned the Variable In attribute.
9023 COMPILE: TOO MANY INPUTS
Too many UDFB Variable In attributes.
The total number of inputs and outputs for any UDFB is 64. You have exceeded that number.
Tip
It is recommended that you keep the number of inputs and outputs to the UDFB to a minimum
(under 16). More can be declared if necessary, but transferring all the inputs and outputs to and
from a function block does use scan time. There is also the constraint of the 255-element matrix to
consider. If you have a large number of inputs, you may want to enter them as a structure using just
one input.

9025 SWD: INSERT NEW SYMBOL
If you insert a new symbol into your ladder that has not previously been declared in the software
declarations table, a message will ask if you want to add the new symbol now. If you choose Yes,
the software declarations table appears and you can insert the new symbol. If you choose No, you
will not be able to add the undeclared symbol to your ladder until it has been declared.
9026 SWD: AUTO INSERT
This symbol cannot be inserted into a structure.
When you have entered a variable name in your ladder and are prompted to enter it in the software
declarations table, you cannot insert the new variable in software declarations if the focus is on a
structure member or on END_STRUCT.
Tip
Move the focus anywhere else in the table or to End List and press the Insert key.
9027 SWD: DIRECT I/O
Direct I/O points cannot be assigned in the software declarations table in the following situations:
If the variable is a member of a structure.
If the variable has an initial value.
9028 SWD: INITIAL VALUE
Initial values cannot be assigned in the software declarations table in the following situation:
If the variable has an I/O point assigned to it.
9029 SWD: VAR IN
You have attempted to assign the Variable In attribute to a symbol that cannot accept it. The Vari-
able In attribute cannot be assigned to the following:
To the member of a structure (Attributes can only be defined for the entire structure)
To a variable with the function block type
To a variable with an I/O point assigned
9030 SWD: VAR OUT
You have attempted to assign the Variable Out attribute to a symbol that cannot accept it. The Vari-
able Out attribute cannot be assigned to the following:
To the member of a structure (Attributes can only be defined for the entire structure.)
To a variable with the function block, structure, string, or array type
9031 SWD: FUNCTION
You have attempted to assign the Function data type to a symbol that cannot accept it. The Function
data type cannot be assigned to the following:
To the member of a structure
9032 SWD: STRUCTURE
You have attempted to assign the Structure data type to a symbol that cannot accept it.
9033 SWD: ARRAY
You have attempted to assign the Array data type to a symbol that cannot accept it.
9034 SWD: TYPE CHANGE
If you attempt to change the data type of a symbol with an initial value to an incompatible data type,
an error message will appear.
9035 SWD: RETENTIVE
You have attempted to assign the Retentive attribute to a symbol that cannot accept it. The Reten-
tive attribute cannot be assigned to the following:

9036 SWD: NAME FORMAT
You have either left a variable unnamed or assigned a duplicate name. Every variable entered in
your ladder must have a unique name assigned to it in the software declarations table.
9037 SWD: DIRECT I/O FORMAT
Direct I/O must be entered in the software declaration table as boolean data type. The address for-
mat must follow the conventions for master rack, expansion rack, block I/O, or ASIU I/O as listed
below.
Master Rack, PiC CPU
The master or CPU rack is #0. Expansion racks are numbered 1 - 7, where #1 is the rack con-
nected to the master, #2 is the rack connected to #1, etc. Slots are numbered left to right when fac-
ing the PiC rack. Slot 1 and slot 2 are reserved for the CSM/CPU module. On an expansion rack,
slot 2 is reserved for the I/O driver module.
Enter four to six characters.

2nd 0-1 First digit of module slot number* (can omit if 0)
3rd 0-9 Second digit of the module slot number*
5th 0-3 First digit of channel number** (can omit if 0)
* Valid slot numbers are 3 - 13.

Example: If the input is in the master rack at slot 4, channel 3, enter: I4.3
Expansion Rack I/O

Note:Expansion Rack I/O is only available if PiC CPU is chosen. Expansion Rack I/O is not avail-
able for any MMC CPU.
Enter six to eight characters.

2nd 1-7 Expansion rack number
4th 0-1 First digit of module slot number* (can omit if 0)
5th 0-9 Second digit of the module slot number*
7th 0-3 First digit of channel number** (can omit if 0*)
*Valid slot numbers are 3 - 13.

Example: If the output is from expansion rack #7 at slot 12, channel 10, enter: O7.12.10
Master Rack Standalone MMC CPU

(Three Options)
nd AUX, FAUX Connector/Type
2
rd 1-6 Slot Number
3
4 th . (point) Used as a separator
th 0-4 First digit of channel number
5
6 th 0-6 Second digit channel number
OR
nd GEN Connector/Type
2

OR
2nd 1-6 Slot Number
ASIU I/O for MMC for PC CPU

(Two Options)
2nd GEN, AUX, FAUX Connector/Type
rd 1-8 ASIU number
3
th . (point) Used as a separator
4
th 0-6 Second digit channel number
6
OR
2nd 1-8 ASIU number
Block Expansion Rack I/O

Note:Block Expansion Rack I/O is only available for certain CPUs.
Enter five to seven characters.
1st B Block
nd I or O Input or Output
2
rd 0 - 7 First digit of module number* (can omit if 0)
3
th 0 - 9 Second digit of the module number*
4
5 th . (point) Used as a separator
th 0 - 6 First digit of point number** (can omit if 0)
6
7 th 0 - 9 Second digit of point number**
*Valid block module numbers = 1 - 77.
**Valid point numbers = 1 - 64.
Example: If the input is in block I/O module 33, point 5, enter: BI33.5
Blown Fuse Status

The status of up to four fuses on an AC Output, DC Output, or a combination I/O module can be
made available to your ladder program. You declare the fuses as inputs in the software declara-
tions table. On modules having both inputs and outputs, the points are numbered sequentially
(starting at 1 for inputs and starting at 1 for outputs) in the software declarations table as shown in
the two examples below.
The 24 V DC Output 16 point The 24V I/O 16/8 source

module with four fuses module with two fuses
Name Type I/O Point Name Type I/O Point

. . . . . .
. . . . . .
. . . . . .
FB3 BOOL I4.3 . . .
FB1 BOOL I5.17
FB2 BOOL I5.18
Short Circuit Detection
The status of the short circuit detection feature of the general DC outputs for the standalone MMC,
the MMC for PC ASIU, and the block I/O output modules can be made available to the ladder dia-
gram. There is one circuit for each group of outputs. The module’s hardware description defines
how many output points are in a common electrical group. You declare the circuit as an input in
Software Declarations.
16 point DC out Mixed (8 in/ 8 DC out)

Block I/O BI#.1 or 2 BI#.9
Standalone MMC ISGEN.1 or 2 not applicable
MMC for PC ISGEN#.1 or 2 not applicable
For example: If the short circuit input is from a 24VDC input and output block I/O, module number
33, there is only one group of outputs, the detection input is 9, enter: BI33.9
If the short circuit input is from the GEN outputs for a standalone MMC, there are two groups of
outputs (1 to 8 and 9 to 16), there can be two detection inputs: ISGEN.1 and ISGEN.2. The detec-
tion input from an ASIU would also include the ASIU number.
Fast Inputs
PiC CPU
The fast inputs available on the encoder, resolver, and servo encoder hardware modules can be
declared as inputs:
For Channel 1 For Channel 2 For Channel 3 For Channel 4
X.1 X.3 X.5 X.7
Standalone MMC CPU
The fast inputs available on the standalone MMC can be declared as inputs: (where # is the slot
number 1- 6)
MMC For PC CPU
The fast inputs available on the MMC for PC can be declared as inputs: (where # is the ASIU
number 1- 8)
9038 SWD: ARRAY FORMAT

Only variables in the software declarations table that are not yet referenced in the ladder can be
made into arrays. The size of an array must be between 2 and 999 elements. Function block data
type cannot be made into an array.
9039 SWD: COMPLEX NAME FORMAT
If the format of a complex name is incorrect, an error message appears.

9042 SWD: FIND NAME FORMAT
When using the Find/Find Next command in the software declarations table, the following applies:
When searching by Name, you can enter the structure or member name, but not an element of an
array or an array of structures name.
When Whole Name match is selected, an entry is required in the Name box.
9044 SWD: INITIAL VALUE LIMITS
9044 SWD: INITIAL VALUE LIMITS
You have exceeded the limits on initial values in the software declarations table. The limits are:
Data Type Minimum Value Maximum Value

BOOL 0 1
BYTE 0 255
DATE D#1988-1-1 D#2051-12-31
DATE_AND_TIME DT#1988-1-1-00:00:00 DT#2051-12-31-23:59:59
DINT -2,147,483,648 2,147,483.647
DWORD 0 4,294,967,295
FUNCTION BLOCK N/A N/A
INT -32,768 32,767
LINT -9,223,372,036,854,775,808 9,223,372,036,854,775,807
LREAL * *
LWORD 0 18,446,744,073,709,551,615
REAL * *
SINT -128 127
STRING 0 255 ASCII characters
STRUCT N/A N/A
TIME 0 T#49d17h2m47s294ms
T#1193h2m47s294ms
T#71582m47s294ms
T#4294967s294ms
T#4294967294ms
TIME_OF_DAY TOD#00:00:00 TOD#23:59:59
UINT 0 65,535
UDINT 0 4,294,967,295
ULINT 0 9,223,372,036,854,775,807
USINT 0 255
WORD 0 65,535
*Validation done for invalid characters.
9045 SWD: STRING FORMAT

You cannot change the length of a string in the software declarations table to a value that is shorter
than the length of any initial values entered.
9046 SWD: SAVE CHANGES
All your changes to the software declarations table will be lost if you do not save before exiting.
9047 SWD: FORCE LIST ENTRY LIMITATIONS
Entries in the Force List must be explicit. For example, to enter an element of an array, enter name
(3), not name (index).
9048 SWD: STRING LENGTHS EXTENDED
If you edit the initial values for an array of strings and any of the strings are now longer than the
declared string length, these string lengths will be automatically extended.
9049 SWD: STRING LENGTH EXTENDED
If you edit the initial values for a string and the string is now longer than the declared string length,
the string length will be automatically extended.

9051 COMPILE: OI LIBRARY NOT AVAILABLE
The ASFB file for storing PiC Operator Interface information could not be located in the
library directories.
If you are using the Operator Interface feature, you must have the Operator Interface ASFBs
installed. They are in the opinter.lib supplied by Sheffield Automation.
Tip
Check the following:
The Operator Interface ASFBs have been installed on your workstation.
The path to the opinter.lib containing the ASFBs is defined.
9052 COMPILE: INVALID STRING SPECIFIED
The string you have specified is invalid.
9053 COMPILE: UDFB DISCRETE IO
Discrete I/O cannot be declared in UDFB.
You cannot declare discrete I/O points in the software declarations table of a UDFB.
Tip
Even though you cannot use discrete I/O in the finished UDFB, you may need to add discrete I/O in
order to test your UDFB. If you do this, be sure to remove all discrete I/O before you compile the
UDFB.
9054 COMPILE: NO BOOLEAN OUTPUTS
No UDFB Variable Out attributes.
The first output to the UDFB must be a boolean and it must be assigned the Variable Out attribute in
the software declarations table.
Tips
When creating a UDFB, ensure in the software declarations table that the first output:
Is a boolean.
Is assigned the Variable Out attribute.
9055 COMPILE: TOO MANY OUTPUTS
Too many UDFB Variable Out attributes.
The total number of inputs and outputs for any UDFB is 64. You have exceeded that number.
Tip
It is recommended that you keep the number of inputs and outputs to the UDFB to a minimum
(under 16). More can be declared if necessary, but transferring all the inputs and outputs to and
from a function block does use scan time. There is also the constraint of the 255 element matrix to
consider. If you have a large number of inputs, you may want to enter them as a structure using just
one input.
9056 COMPILE: BLOCK I/O NOT INPUT
‘_____’ calls for an input point ‘_____’ in block ‘_____’ which is not configured.
configuration when a module is compiled. PiCPro will detect an error if you attempt to define an
input point at an output location.
Tip

9057 COMPILE: BLOCK I/O NOT OUTPUT
‘_____’ calls for an output point ‘_____’ in block ‘_____’ which is not configured.
configuration when a module is compiled. PiCPro will detect an error if you attempt to define an out-
put point at an input location.
Tip
9058 COMPILE: INVALID UDFB ATTRIBUTE
Invalid symbol attribute in ‘_____’.
There is an invalid symbol attribute in the software declarations table for the UDFB.
Tip
Ensure that the attributes you assign to any variable in the software declarations table is valid. For
variables that will be inputs or outputs to the UDFB, attributes may not be external, retained, global,
or discrete I/O.
9059 SWD: MODIFY NAME USED IN LADDER
When you attempt to modify the name of a symbol used in your ladder, this warning/confirmation
message appears. Changing the name of a symbol means that every occurrence of the name in
your ladder will be changed.
9060 SWD: DELETE
You can delete any selected item from the software declarations table that is not used in your lad-
der. If you want to delete a structure, you must be sure to select the entire structure.
9061 SWD: STRUCTURE ATTRIBUTES
You have attempted to add an attribute to a member of a structure.
9062 SWD: PASTE IN STRUCTURE
You cannot insert a function block, structure, or a symbol with a direct I/O point into a structure.
9063 SWD: SYMBOL EXISTS TYPE INVALID
You cannot name a ladder element with the name of an existing symbol whose data type is invalid
for this ladder element.
9064 SWD: INVALID ARRAY COUNT EDIT
You cannot enter a name in your ladder which is an array without entering the array index. Con-
versely, you cannot enter a name with an array index if the array does not exist.
9065 SWD: INVALID CONSTANT EXPRESSION
The constant you entered is invalid.
9066 SWD: INVALID CONSTANT TYPE
The constant you entered is valid but the data type of the constant is not the data type required.
9067 SWD: FUNCTION BLOCKS UNAVAILABLE
The function block menu cannot be displayed from within the software declarations table.
9082 SWD: TOO BIG FOR SEGMENT
STRUCT or STRING too big, must be less than 64K.

A structure or string variable declared in Software Declarations exceeds the maximum size allowed
(64K bytes).
Double clicking on the error in the information window will reposition you to the declaration in software
declarations that is causing the problem. Edit the structure or string variable in Software Declarations
and recompile.

9083 SWD: INSUFF DATA MEMORY
Out of Data Memory. A scan stop and a full compile and download is required.
This error occurred while patching in new software declarations variables and extended data memory
is being used for this ladder.
There are a total of 3 data segments. They are only used as needed. Patching of declarations can
only occur until the current segment is full. If the current segment becomes full when you patch in new
declarations, you'll get this message. Then you must do a full compile and download of the ladder. If a
full compile and download does not fix the problem, all three segments are full and you must optimize
your usage of data memory by consulting with Sheffield Automation Tech Support.
9086 SWD: INVALID NAME SPECIFIED
“Variable name” cannot be inserted. It is not a valid variable name.

Variable names are limited to 63 characters where the first character is an alpha character and the
remaining characters are alphanumeric or underscores.
9090 COMPILE: DUPLICATE INPUTS NOT ALLOWED

Input: The first four characters must be different from other inputs.
When compiling a UDFB, the input names are truncated to four characters. The truncated input must
be different from the other truncated inputs. Double-click on the error in the information window to dis-
play that variable in software declarations. Rename the variable to make the first four characters of the
variable name different from the other inputs.
9091 COMPILE: DUPLICATE OUTPUTS NOT ALLOWED

Output: The first four characters must be different from other outputs.
When compiling a UDFB, the output names are truncated to four characters. The truncated output
must be different from the other truncated outputs. Double-click on the error in the information win-
dow to display that variable in software declarations. Rename the variable to make the first four
characters of the variable name different from the other outputs.
Fieldbus Error Messages
9071 FIELDBUS: LIBRARY NOT AVAILABLE

The library file for storing control fieldbus interface information could not be located in the
library directories.
Check that you have indicated the correct directory for the libraries. Select File | PiCPro Libraries...
from the menu.
9072 FIELDBUS: UNRECOGNIZED FORMAT

Unrecognized fieldbus information file format.
Your ladder’s UCT file does not have the correct format. The most likely cause is manual editing of the
UCT file. Re-create this file using the G&L DeviceNet TM Configurator.
9073 FIELDBUS: UNDEFINED TAG

Fieldbus information file line ‘_______’. ‘_______’ undefined Tag Name.
The tag name specified in the error message cannot be found in the software declarations for the
associated ladder. The tag name may have been spelled wrong when it was entered in the G&L
DeviceNet TM Configurator. If so, run the Configurator and correct the problem. Or the variable really
does need to be added to your ladder’s software declarations. If this is the case, go to software decla-
rations and add a variable with the same name and type as declared in the Configurator.

9074 FIELDBUS: INVALID LOCATION
Fieldbus information file line ‘_______’. ‘_______’ invalid IRAM Location.
The tag name specified in the error message has an invalid IRAM location configured for it. The most
likely cause of this error is manual editing of the UCT file. Re-create the file using the G&L DeviceNet
TM
Configurator.
9076 FIELDBUS: INVALID MASK

Fieldbus information file line ‘_______’. ‘_______’ undefined Bit Mask.
The tag name specified in the error message has an invalid bit mask associated with it. The valid val-
ues are 0 through 7. The most likely cause of this error is manual editing of the UCT file. Re-create the
file using the G&L DeviceNet TM Configurator.
9077 FIELDBUS: INVALID TYPE

Fieldbus information file line ‘_______’. ‘_______’ invalid Data Type.
The tag name specified in the error message has a data type that does not match the corresponding
variable’s type in the ladder’s software declarations. Run the G&L DeviceNet TM Configurator and
change the data type for this tag name to match the type for the same variable in software declarations
- OR - edit the software declarations for your ladder and change the variable’s type.
9078 FIELDBUS: INVALID SIZE

Fieldbus information file line ‘_______’. ‘_______’ invalid Size.
The tag name specified in the error message has an invalid size associated with it. The most likely
cause of this error is manual editing of the UCT file. Re-create the file using the G&L DeviceNet TM
Configurator.
9079 FIELDBUS: INVALID UPDATE

Fieldbus information file line ‘_______’. ‘_______’ invalid Update.
The tag name specified in the error message has an invalid update type associated with it. The cur-
rently supported values are “Polled Input” (bit0=1) and “Polled Output” (bit 1=1). The most likely cause
of this error is manual editing of the UCT file. Re-create the file using the G&L DeviceNet TM Configura-
tor.
9080 FIELDBUS: INVALID FORMAT

Fieldbus information file line ‘_______’. Invalid format. ‘_______’
The specified line in your UCT is invalid. The most likely cause of this error is manual editing of the
UCT file. Re-create the file using the G&L DeviceNet TM Configurator.
9081 FIELDBUS: INVALID SLOT

Fieldbus information file line ‘_______’. Invalid Slot information.
The specified line in your UCT has an invalid slot number associated with it. The most likely cause of
this error is incorrect manual editing of the UCT file. Make sure the Slot number is within the valid
range of 3 through 13.

Servo Setup Error Messages
11001 SERVO: INVALID AXIS CUT COPY

The axis data you were attempting to cut or copy has been corrupted. Close the program without
saving any changes and try again.
11002 SERVO: INVALID AXIS PASTE
The axis data you are attempting to paste has been corrupted. Close the program without saving
any changes and try again.
11003 SERVO: INVALID AXIS LABEL
You must enter a unique axis label for each axis you are entering before proceeding. This label can
be up to eight characters in length.
11004 SERVO: TUNE NO PARENT
When you attempt to view or force variables within servo setup, the servo setup file must be opened
from within the parent ladder by choosing Servo function from the View menu. If you open the .SRV
file using the Open command, viewing and forcing will be disabled.
11005 SERVO: TUNE NO MAIN
If you attempt to activate servo viewing and forcing when the path to the main ladder has not been
defined, an error will occur.
11007 SERVO: NO MORE DATA
This is an internal software condition. Please note error number and consult factory.
11008 SERVO: AXIS INFO UNREADABLE
The axis data has been corrupted.
11019 SERVO: NO AXIS DEFINED
No axes have been defined for this servo setup function. Insert one or more axes into the servo
setup program.
11020 SERVO: SOFTWARE UPPER LIMIT CALCULATION ERROR
Overflow calculating the Software Upper Limit. Check your inputs for Axis #__.
In servo setup you have entered scaling data for feedback units (FU) and ladder units (LU) and the
software upper limit. The software uses the formula shown to convert this information into feedback
units and checks that the result is within the acceptable range.
software upper limit * FU = N (where N must be within range of -536870912 to 536870911 FU)
LU
Tip
Adjust the axis data information so that the result of the conversion calculation will fall within the
acceptable range.
11021 SERVO: SOFTWARE LOWER LIMIT CALCULATION ERROR
Overflow calculating the Software Lower Limit. Check your inputs for Axis #__.
software lower limit. The software uses the formula shown to convert this information into feedback
software lower limit * FU = N (where N must be within range of -536870912 to 536870911 FU)
LU
Tip
acceptable range.

11022 SERVO: FOLLOWING ERROR LIMIT CALCULATION ERROR
Overflow calculating Excess Error Limit. Check your inputs for Axis # __.
excess error limit. The software uses the formula shown to convert this information into feedback
excess error limit * FU = N (where N must be within range of 0 to 536870911 FU)

LU
Tip
acceptable range.
11023 SERVO: IN POSITION BAND CALCULATION ERROR
Overflow calculating the In Position Band. Check your inputs for Axis # __.
in position band. The software uses the formula shown to convert this information into feedback
in position band * FU = N (where N must be within range of 0 to 536870911 FU)

LU
Tip
acceptable range.
11024 SERVO: ROLLOVER POSITION CALCULATION ERROR
Overflow calculating the Rollover Position. Check your inputs for Axis # __.
rollover position. The software uses the formula shown to convert this information into feedback
rollover position * FU = N (where N must be within range of 0 to 536870911 FU)

LU
Tip
acceptable range.
11025 SERVO: PLUS INTEGRAL LIMIT CALCULATION ERROR
Overflow calculating Plus Integral Error Limit. Check your inputs for Axis # __.
plus integral error limit. The software uses the formula shown to convert this information into feed-
back units and checks that the result is within the acceptable range.
plus integral error limit * FU = N (where N must be within range of 0 to 536870911 FU)
LU
Tip
acceptable range.

11026 SERVO: MINUS INTEGRAL LIMIT CALCULATION ERROR
Overflow calculating Minus Integral Error Limit. Check your inputs for Axis # __.
minus integral error limit. The software uses the formula shown to convert this information into feed-
minus integral error limit * FU = N (where N must be within range of -536870912 to 0 FU)
LU
Tip
acceptable range.
11027 SERVO: VELOCITY LIMIT CALCULATION ERROR
Overflow calculating Velocity Limit. Check your inputs for Axis # __.
In servo setup you have entered scaling data for feedback units (FU) and ladder units (LU), the
update rate, and the velocity limit (entered in LU/min). The software uses the formula shown to con-
vert this information into feedback units per iteration and checks that the result is within the accept-
able range.
velocity limit * FU * 8 * update rate = N (where N must be within range of 0 to 32767 FU/iteration)
LU
Tip
acceptable range.
Note: When using a formula in any of the Servo error calculations calling for an update rate entry,
use the number of milliseconds for an update rate value, i.e. for a 2 ms update rate, use “2”.
11028 SERVO: INTEGRAL GAIN CALCULATION ERROR
Overflow calculating Integral Gain. Check your inputs for Axis # __.
update rate, and the integral gain. The value entered in setup for integral gain represents the ladder
units per minute per ladder unit of following error (FE) times minutes. The software uses the formula
shown to convert this information into feedback units and checks that the result is within the accept-
able range.
integral gain value * 3253 * update rate = N (where N must be within range of 0 to 32767)
FU/min-volt
Tip
acceptable range. A typical value for integral gain entered in setup is zero. If required, up to 32,000
LU/min/LUFE * min. can be entered.

11029 SERVO: PROPORTIONAL GAIN CALCULATION ERROR
Overflow calculating Proportional Gain. Check your inputs for Axis # __.
proportional gain. The value entered in setup for proportional gain represents the ladder units per
minute for each ladder unit of following error. The software uses the formula shown to convert this
information into feedback units and checks that the result is within the acceptable range.
proportional gain value * 762601 = N (where N must be within range of 0 to 32767 FU)
FU/min-volt
Tip
acceptable range. Typical values for proportional gain entered in setup are from 1,000 to 5,000 LU/
min/LUFE.
11030 SERVO: DERIVATIVE GAIN CALCULATION ERROR
Overflow calculating Derivative Gain. Check your inputs for Axis # __.
update rate, and the derivative gain. The value entered in setup for derivative gain represents the
ladder units per minute for each ladder unit of following error per minute. The software uses the for-
mula shown to convert this information into feedback units and checks that the result is within the
acceptable range.
derivative gain value * 178734 = N (where N must be within range of 0 to 32767 FU)
FU/min-volt * update rate
Tip
acceptable range. A typical value for derivative gain entered in setup is zero. If required, up to 500
AU/min/AUFE/min can be entered.
11031 SERVO: FEED FORWARD CALCULATION ERROR
Overflow calculating Feed Forward Factor. Check your inputs for Axis # __.
update rate, and the feed forward percent. The software uses the formula shown to convert this
information into feedback units and checks that the result is within the acceptable range.
feed forward percent * 457560436 = N (where N must be within range of 0 to 524272)

FU/min-volt * update rate
Tip
acceptable range.

11032 SERVO: CSTOP RAMP CALCULATION ERROR
Overflow calculating Controlled Stop Ramp. Check your inputs for Axis # __.
update rate, and the controlled stop ramp in ladder units/minute/second. The software uses the for-
acceptable range.
cstop ramp * FU * update rate * update rate = N (where N must be within a range shown below)
LU * 937500
If SERCOS, then N must be within the range of 1 to 536870911.0 FU.
If Encoder, Resolver, or TTL, then N must be within the range of 1 to 67108864.0 FU.
If Analog Output or Stepper, then N must be within the range of 1 to 262144.0 FU.
Tip
acceptable range. Typical values entered in setup are 10,000 to 10,000,000 LU/min/sec, not to
exceed 1023 FU/update/update.
11033 SERVO: ACCEL RAMP CALCULATION ERROR
Overflow calculating Acceleration Ramp. Check your inputs for Axis # __.
update rate, and the acceleration ramp in ladder units/minute/second. The software uses the for-
acceptable range.
acceleration ramp * FU * update rate * update rate = N (where N must be within a range shown
LU * 937500 below)
Tip
acceptable range. Typical values entered in setup are 10,000 to 10,000,000 LU/min/sec not to

11034 SERVO: DECEL RAMP CALCULATION ERROR
Overflow calculating Deceleration Ramp. Check your inputs for Axis # __.
update rate and the deceleration ramp in ladder units/minute/second. The software uses the formula
shown to convert this information into feedback units and checks that the result is within the accept-
able range.
deceleration ramp * FU * update rate * update rate = N (where N must be within a range shown
LU * 937500 below)
Tip
acceptable range. Typical values entered in setup are 10,000 to 10,000,000 LU/min/sec, not to
11035 SERVO: BUILDER FEED OVERRIDE
This is an internal error. Please make a note of the error number and consult factory.
11036 SERVO: SLOW FILTER CALCULATION ERROR
Overflow calculating Slow Velocity Filter. Check your inputs for Axis # __.
update rate, the slow filter, and the slow velocity filter in milliseconds. When the slow filter is non-
zero, the software uses the formula shown to convert this information into feedback units and
checks that the result is within the acceptable range.
65535 * (1 - e(-Y)) = N (where N must be within range of 0 to 65535)
and where:
-Y = -(update rate/slow filter)
Tip
acceptable range.

11037 SERVO: FAST FILTER CALCULATION ERROR
Overflow calculating Fast Velocity Filter. Check your inputs for Axis # __.
update rate, the fast filter, and the fast velocity filter in milliseconds. When the fast filter is non-zero,
the software uses the formula shown to convert this information into feedback units and checks that
the result is within the acceptable range.
65535 * (1 - e(-W)) = N (where N must be within range of 0 to 65535)
and where:
-W = -(update rate/fast filter)
Tip
acceptable range.
11038 SERVO: FILTER VELOCITY THRESHOLD CALCULATION ERROR
Overflow calculating Slow/Fast Velocity Threshold. Check your inputs for Axis # __.
update rate, and the slow/fast velocity threshold in ladder units/minute. The software uses the for-
acceptable range.
velocity threshold * FU * update rate = N (where N must be within range of 1 to 65535 FU)
LU * 60000
Tip
acceptable range. Typical value entered in setup is zero, not to exceed 4095.
11039 SERVO: FILTER LAG CALCULATION ERROR
Overflow calculating Velocity Filter Lag Error. Check your inputs for Axis # __.
In servo setup you have entered scaling data for feedback units (FU), and ladder units (LU), the
update rate, the velocity threshold, and the fast velocity filter in milliseconds. When the fast filter is
non-zero, the software uses the formula shown to convert this information into feedback units and
checks that the result is within the acceptable range.
(V * FU * update rate)/(LU * 65535 * (1-e(-Y))) = N (where N must be within range of 0 to 65535)
and where:
V = velocity threshold
-Y = -(update rate/slow filter)
Tip
acceptable range.

11040 SERVO: UPDATE SCALING CALCULATION ERROR
Overflow calculating Servo Update Rate. Check your inputs for Axis # __.
The selected update rate entered in milliseconds is out of range.
Tip
acceptable range.
4ms is adequate for most applications. Lower values consume more CPU processing time. If too
many axes have too low an update rate, the CPU may not have enough processing time available to
run the user program.
11041 SERVO: D/A OFFSET CALCULATION ERROR
Overflow calculating Analog Output Offset. Check your inputs for Axis # __.
The D/A offset is out of range.
Tip
acceptable range.
11042 SERVO: BUILDER NOT FOUND
If the filename is invalid when a function is made, this message appears. Please make a note of the
error number and consult the factory.
11043 SERVO: BUILDER NEW FILE
If the filename is not filled in when a function is made, this message is displayed. Please make a
note of the error number and consult the factory.
11044 SERVO: UPDATE DIFFERENCES CALCULATION ERROR
Invalid ratio between slowest/fastest update rates with Axis # __ and Axis # __.
The ratio between the updates of the fastest and slowest is greater than 16.
Tip
Adjust the update rate in the position loop data of axis data so that the result of the conversion cal-
culation will fall within the acceptable range.
11099 SERVO: NEWER VERSION SERVO FILE
This file was made with a newer version of PiCPro than the one you are currently using. You must
open the file in the PiCPro version it was created with. The file can then be saved as for the older
version of PiCPro.
See “To save a file in a format readable by a previous version of PiCPro” Saving a Servo Setup
File for more information.
11102 SERVO: OVERFLOW CONSTANT JERK ERROR
Overflow calculating Constant Jerk for Move Accel/Decel.
There was an overflow calculating Constant Jerk for Move Accel/Decel.
In Servo Setup you have entered scaling data for feedback units (FU), ladder units (LU) and Ladder
Units to Axis Units (LU2AU), the update rate, and the Constant Jerk for Move Accel/Decel in ladder
units/minute/second/second. The software uses the formula shown to convert this information into
feedback units and checks that the result is within the acceptable range.
Constant Jerk * FU * update rate * update rate * update rate * LU2AU = N (where N >0
LU * 60000 * 1000 * 1000 and < 67108863.0)
Tip
Adjust the axis data information so that the results of the conversion calculation will fall within the
acceptable range.

Note: When using a formula in any of the Servo error calculations calling for an update rate entry, use
the number of milliseconds for an update rate value (e.g. for a 2 ms update rate, use 2).
11103 SERVO: OVERFLOW MAX ACCELERATION

Overflow calculating Max Acceleration for Move Accel/Decel.
There was an overflow calculating Max Acceleration for Move Accel/Decel.
In Servo Setup you have entered scaling data for feedback units (FU) ladder units (LU) and Ladder
Units to Axis Units (LU2AU), the update rate, and the Max Acceleration for Move Accel/Decel in ladder
units/minute/second. The software uses the formula shown to convert this information into feedback
Max Acceleration * FU * update rate * update rate * LU2AU = N (where N >0

LU * 60000 * 1000 and < 67108863.0)
Tip
acceptable range.
11104 SERVO: OVERFLOW CALCULATING CONSTANT JERK FOR CON-

TROLLED STOP DECEL
Overflow calculating Constant Jerk for Controlled Stop Decel.
There was an overflow calculating Constant Jerk for Controlled Stop Decel.
In Servo Setup you have entered scaling data for feedback units (FU), ladder units (LU) and Ladder
Units to Axis Units (LU2AU), the update rate, and the Constant Jerk for Controlled Stop Decel in ladder
units/minute/second/second. The software uses the formula shown to convert this information into
feedback units and checks that the result is within the acceptable range.
Constant Jerk * FU * update rate * update rate * update rate * LU2AU = N (where N >0
LU * 60000 * 1000 * 1000 and < 67108863.0)
Tip
acceptable range.
11105 SERVO: OVERFLOW CALCULATING MAX ACCELERATION FOR CON-

TROLLED STOP DECEL
Overflow calculating Constant Jerk for Controlled Stop Decel.
There was an overflow calculating Max Acceleration for Controlled Stop Decel.
In Servo Setup you have entered scaling data for feedback units (FU) ladder units (LU) and Ladder
Units to Axis Units (LU2AU), the update rate, and the Max Acceleration for Controlled Stop Decel in
ladder units/minute/second. The software uses the formula shown to convert this information into feed-
Max Acceleration * FU * update rate * update rate * LU2AU = N (where N >0

LU * 60000 * 1000 * 1000 and < 67108863.0)

Tip
acceptable range.
11116 AXIS: PASTE INVALID AXIS NUMBER ERROR

“Axis is not a valid axis number for this CPU type. Axis will be inserted as axis number
X. Do you want to continue?”
This dialog is displayed in the MMC-Limited Edition when copying an axis with an invalid axis number.
The file was created or modified using the Professional Edition.
11171 AXIS: PASTE IMAGE AXIS ERROR

A DLS axis can only be pasted if the target CPU is an MMC for PC
An attempt has been made to paste a digitizing DLS axis into a servo setup where the target CPU is
not an MMC for PC
11800 AXIS: CUT

Check that you want to cut the selected axis.
11801 AXIS: DELETE
Check that you want to delete the selected axis.
11802 AXIS: MAXIMUM ALLOWED
You have exceeded the maximum number of axes and cannot proceed with pasting your selection.
11803 AXIS: PASTE DUPLICATE ERROR
Axis # already exists. The axis will be inserted as axis #_. You can choose to continue or cancel.
11804 AXIS: PASTE INCOMPATIBLE TYPE
When you paste an axis over another axis, both axes must be the same type: servo or digitizing.
11805 AXIS: PASTE DIFFERENT I/O
The axis data you are pasting is from an axis with an input type of _ and on output type of _. You can
choose to continue or cancel.
11806 AXIS: PASTE DIFFERENT INPUT TYPE
The axis data you are pasting is from an axis with an input type of _. You can choose to continue or
cancel.
11807 FORCE: UPDATE CONFIG DATA WITH FORCE VALUES
Forcing values have changed. You can choose to update the axis configuration data with the current
forcing values or cancel.
11808 FORCE: ENTRY ERR PGAIN
The value entered in the Force List data for proportional gain is out of the acceptable range.
11809 FORCE: ENTRY ERR IGAIN
The value entered in the Force List data for integral gain is out of the acceptable range.
11810 FORCE: ENTRY ERR DGAIN
The value entered in the Force List data for derivative gain is out of the acceptable range.
11811 FORCE: ENTRY ERR FEEDFWD
The value entered in the Force List data for feed forward percentage is out of the acceptable range.
11812 FORCE: ENTRY ERR SFILTER
The value entered in the Force List data for the slow speed filter is out of the acceptable range.

11813 FORCE: ENTRY ERR DAOFF
The value entered in the Force List data for the D/A offset is out of the acceptable range.
11850 SERVO: MMC AXES NOT SAME TYPE
This error message is displayed when attempting to compile a standalone MMC or MMC for PC
SRV file which contains more than one axis type. All axes must be either D/A Encoder or SERCOS
axes, but not both.
11853 SERVO: DOCUMENT ALREADY OPEN
Unable to save document. A document with this name is already open, please save to a dif-
ferent name.
You cannot perform a “Save As” to a file that is already open. Either “Save As” to a different name
or cancel this “Save As,” close the conflicting open document, and do the “Save As” again.
11854 SERVO: COMPILE ABORTED
The version of PiCPro specified for the open project does not match the version of PiCPro
that is running. Compilers are different for different versions of PiCPro. You cannot compile
this function in this version of PiCPro while the project is open.
You cannot compile in this situation.
You can either:
Launch the correct version of PiCPro (that is specified in the project)
Change the version of PiCPro in the project to the one you are currently running
Close the project. Open the Servo Setup file and compile.
11856 SERVO: UNKNOWN CPU TYPE
This message is displayed if the CPU in the file is not a PiC, standalone MMC, or an MMC for PC.
11857 SERVO: SAVE AS FAILED
ferent name.
This error message is displayed when using Save As with a PiC or standalone MMC SRV file to an
earlier version of PiCPro.
Invalid means:
There may be too many axes
Invalid axes numbers are specified
An invalid axis number or axis type is specified
Ladder feedback units exceed 65535
A slot, channel, ring, or slave number is invalid.
You can highlight the error number in the Information Window and press F1, or you can access
more information about the error number from the index on the Help menu.
11858 SERVO: SAVE AS FAILED
ferent name.
This error message is displayed when using Save As with a PiC or standalone MMC SRV file to an
earlier version of PiCPro.
Invalid means:
There may be too many axes
Invalid axes numbers are specified
An invalid axis number or axis type is specified
Ladder feedback units exceed 65535
A slot, channel, ring, or slave number is invalid.
You can highlight the error number in the Information Window and press F1, or you can access
more information about the error number from the index on the Help menu.

11859 SERVO: INVALID PIC AXIS
This error message is displayed when using Save As to save a PiC file in a previous PiCPro version
(10.0 through 11.0) which contains one or more axes with a slot, channel, ring, or slave value of
zero. Also displayed when attempting to compile a PiC SRV file where any of the axes has a 0 value
for slot, channel, ring, or slave.
11860 SERVO: INVALID MMC DIGIT AXIS
This error is displayed when using Save As with a standalone MMC SRV file which contains a digi-
tizing axis with a slot, channel, ring, or slave value of zero to a previous version of PiCPro (10.2
through 11.0). It is also displayed when compiling a standalone MMC SRV file where any of the
axes has a 0 value for slot, channel, ring, or slave.
11861 SERVO: INVALID MMC FOR PC DIGIT AXIS
This error message is displayed when saving or compiling an MMC for PC SRV file which contains
a digitizing axis with a slot, channel, ring, or slave value of zero.
11862 SERVO: INVALID MMC SERVO AXIS
This error is displayed when using Save As with a standalone MMC SRV file, which contains a
servo axis with a slot, channel, ring, or slave value of zero to a previous version of PiCPro (10.2
through 11.0). It is also displayed when compiling a standalone MMC SRV file where any of the
axes has a 0 value for slot, channel, ring, or slave.
11863 SERVO: INVALID MMC FOR PC SERVO AXIS
This error message is displayed when saving or compiling an MMC for PC SRV file, which contains
a servo axis with a slot, channel, ring, or slave value of zero.
11864 SERVO: MMC TOO MANY AXES
This error message is displayed when using Save As with a standalone MMC SRV file which con-
tains more axes than allowed in previous versions of PiCPro (10.2 through 11.0). It is also displayed
in the MMC-Limited Edition when compiling a standalone MMC SRV file, which contains more axes
than are allowed.
11866 SERVO: INVALID MMC DIGIT AXIS NUMBER
tains a digitizing axis with an invalid axis number or axis type combination to a previous version of
PiCPro (10.2 through 11.0). It is also displayed in the MMC-Limited Edition when compiling a stan-
dalone MMC SRV file, which contains a digitizing axis with an invalid axis number or axis type com-
bination.
11867 SERVO: INVALID MMC SERVO AXIS NUMBER
tains a servo axis with an invalid axis number or axis type combination to a previous version of
PiCPro (10.2 through 11.0). It is also displayed in the MMC-Limited Edition when compiling a stan-
dalone MMC SRV file, which contains a digitizing axis with an invalid axis number or axis type com-
bination.
11868 SERVO: INVALID AXIS FU OR LU EXCEEDS 65535
This error message is displayed when using Save As to save an SRV file into a previous version for-
mat (10.2 through 11.0) when the file contains an axis whose feedback units or ladder units exceed
65535.
11869 SERVO: UNABLE TO ANIMATE
This error message is displayed when downloading a ladder which does not contain the STRTSRV
function, viewing the servo setup function in the ladder, displaying a servo view or force list, and
selecting “Viewing On” or “Forcing On”.
11870 SERVO: INVALID AXIS FU/LU RATIO EXCEEDS 65535
This error message is displayed when compiling a servo setup function which contains an axis
whose Feedback Units to Ladder Units ratio is larger than 65535.

11873 SERVO: DUPLICATE AXIS NUMBER
This message is displayed when attempting to change the axis number to a number that is already
in use by another axis. The axis number can be changed when inserting or editing the axis proper-
ties.
11877 SERVO: WARNING INPUT POLARITY REVERSED
This message is displayed any time an axis or axes is converted or pasted between PiC and stan-
dalone MMC or MMC for PC CPU types. To change the polarity, select the axis, select Edit | Axis
Data, select the Position Loop Data tab, and change the input polarity.
Warning: If the input polarity is not changed, unexpected motion may occur.
11885 SERVO: INVALID MMC EDITION SERVO AXIS
This error message is displayed in the MMC-Limited Edition when using Save As with a standalone
MMC SRV file which contains a servo axis with a slot, channel, ring, or slave value of zero to a pre-
vious version of PiCPro (10.2 through 11.0). It is also displayed when compiling a standalone MMC
SRV file where any of the axes has a 0 value for slot, channel, ring, or slave.
11886 SERVO: INVALID MMC EDITION DIGIT AXIS
This error message is displayed in the MMC-Limited Edition when using Save As with a standalone
MMC SRV file which contains a digitizing axis with a slot, channel, ring, or slave value of zero to a
previous version of PiCPro (10.2 through 11.0). It is also displayed when compiling a standalone
MMC SRV file where any of the axes has a 0 value for slot, channel, ring, or slave.
11915 SERVO: TOO MANY MASTER AXES
More than one axis is specified as a DLS Communications Master axis. Only one Communications
Master is allowed.
Tip
Determine which axis should be the Communications Master axis. Edit the other Communications
Master axes and uncheck the Communications Master checkbox.
11916 SERVO: TOO MANY IMAGE AXES
More than one axis is specified as a digitizing DLS axis. Only one digitizing axis is allowed.
Tip
Determine which axis should be the digitizing DLS axis. Edit the other digitizing DLS axis and select
a different Input Type.
11917 SERVO: MASTER AND IMAGE AXIS INVALID
Both a DLS Communications Master axis and a digitizing DLS axis have been specified. A servo
setup function can include one or the other but not both.
SERCOS Error Messages

11895 SERCOS: SLAVE NUMBER GREATER THAN 16
This error message is displayed when using Save As to save an MMC for PC SRV file that specifies
a SERCOS axis with a slave number greater than 16 in a format readable by PiCPro V12.0.
12002 SERCOS: IDN VALUE FORMAT
An invalid value has been specified. The acceptable ranges are listed below.
Range
Two byte value = -32768 to 32767
Four byte value = -2,147,483,648 to 2,147,483,647
12003 SERCOS: CUT DELETE
A confirmation prompt asking if you are sure you want to cut or delete this ring or slave appears.
You may choose to proceed or cancel.

12004 SERCOS: FATAL ERROR CREATING TEMP FILE
The slave data could not be edited because a temporary file could not be created.
12005 SERCOS: INVALID SELECTION
You have selected more than eight slaves to be cut/copied. The limit is eight since that is the maxi-
mum that can be pasted on a ring.
You may select rings or slaves; you cannot select both. If both are selected, an error will occur.
12006 SERCOS: RING INFO UNREADABLE
The ring data is corrupted.
12007 SERCOS: SLAVE INFO UNREADABLE
The slave data is corrupted.
12008 SERCOS: NO RING
No rings have been defined. Define a ring in SERCOS setup and proceed.
12009 SERCOS: NO SLAVE
No slaves have been defined in Slot/Ring __. Define slaves in SERCOS setup.
12010 SERCOS: DUPLICATE
There is a duplicate slot definition at ___. Slot definitions cannot be duplicated.
12011 SERCOS: DUPLICATE SLAVE
There are duplicate slave numbers entered. Each slave must have a unique number.
12012 SERCOS: NOT SEQUENTIAL
The slave numbers must be sequential.
12013 SERCOS: CLEAR DATA VALUE
A confirmation prompt asking if you are sure you want to clear the selected data. You may choose to
proceed or cancel.
12014 SERCOS: INTERNAL ERROR
An internal error of flag byte out of range has occurred. Report this error to Sheffield Automation.
12015 SERCOS: NOT INITIALIZED
SERCOS is not initialized in your ladder. The SC_INIT function block was not successfully called in
your ladder.
12016 SERCOS: SERVER QUEUE IS FULL
The server queue is full. Too many requests have been made. The requested information exceeds
the available buffer space in the control.
12017 SERCOS: SERCOS BOARD DOES NOT SUPPORT ANIMATION
The SERCOS board you have does not support animation. Contact Sheffield Automation for new
SERCOS firmware.
12018 SERCOS: ERR 3
The axis is not a SERCOS axis, is not initialized, or slot/ring/slave specification is incorrect.
Check that your SERCOS module is in the correct slot.
Check that the SC_INIT function block in your ladder was called successfully to initialize SER-
COS.
12019 SERCOS: DRIVE ERROR
This is a drive error. Refer to your drive documentation for information on it.
12020 SERCOS: UNDEFINED INTERNAL ERROR
An undefined error has been detected. Write down the error message and the error number and
contact Sheffield Automation.

12021 SERCOS: NO ATTRIBUTE IN FILE
The attribute is missing for <IDN> in <IDN filename>.
All IDNs must have an attribute. If an attribute is missing from your drive IDN file, contact your drive
manufacturer and then contact Sheffield Automation. We may be able to help you with a work-
around. If an attribute is missing from your system IDN file, contact Sheffield Automation.
12025 SERCOS: DOCUMENT ALREADY OPEN
Unable to save document. A document with this name is already open. Please save to a dif-
ferent name.
You cannot perform a “Save As” to a file that is already open. Either “Save As” to a different name
or cancel this “Save As,” close the conflicting open document, and do the “Save As” again.
12026 SERCOS: VERSION MISMATCH
The version of PiCPro specified for the open project does not match the version of PiCPro
that is running. Compilers are different for different versions of PiCPro. You cannot com-
plete these function in this version of PiCPro while the project is open.
You cannot compile in this situation.
You can either:
Launch the correct version of PiCPro (that is specified in the project)
Change the version of PiCPro in the project to the one you are currently working on
Close the project. Open the SERCOS Setup file and compile.
12027 SERCOS: INVALID RING SPECIFIED %s. SLOT AND RING CANNOT BE 0
A ring in your file has a slot or ring value set to zero. You must specify a valid slot or ring value
before you can save this file in a previous version format (10.2 through 11.0) or compile the function.
12029 SERCOS: INVALID SLAVE SPECIFIED %s. SLAVE NUMBER CANNOT BE 0
A slave in your file has slave number of zero. You must specify a valid slave number before you can
save this file in a previous version format (10.2 through 11.0) or compile the function.
12030 SERCOS: TOO MANY RINGS HAVE BEEN SPECIFIED
The file has too many rings specified for the CPU type. The ring(s) must be deleted, or the CPU type
changed before the file can be saved in a previous version format (10.2 through 11.0) or the function
compiled.
12031 SERCOS: TOO MANY SLAVES HAVE BEEN SPECIFIED
The file has too many slaves specified for the CPU type. The slave(s) must be deleted, or the CPU
type changed before the file can be saved in a previous version format (10.2 through 11.0) or the
function compiled.
12435 SERCOS: CANNOT REMOVE FROM CYCLIC DATA
<IDNs in cyclic data> cannot be removed from cyclic data unless the <corresponding type>
checkbox is unchecked.
The specific cyclic data mentioned in this message cannot be removed from cyclic data unless the
corresponding checkbox is unchecked.
Edit the slave data (close the Cyclic Data dialog first) and uncheck the specified checkbox. The IDN
you were trying to remove will automatically be removed from cyclic data.

APPENDIX C - PiCPro Reference Card - Errors/Variables
Reference Card C-stop Bit Location Hex
Error (low byte) Value
(in
8 7 6 5 4 3 2 1
# STRTSERV Function ladder)
Errors Part reference error E 8080
0 No error (32896)
1 Bad user function data Part reference dimen- E 8040

sion error (32832)
2 Not enough low memory
Distance or position E 8020
3 Feedback module(s) not found
move dimension error (32800)
4 Analog module(s) not found
Feedrate error E 8010
5 Update rate (SERCOS axis only) (32784)
6 CPU type Machine reference E 8008
7 Wrong CPU error (32776)
8 Bad cyclic data (SERCOS axis only) User-defined E 8004

C-stop (32772)
9 Invalid firmware
Negative software E 8002
23 Outdated servo setup data
limit exceeded (32770)
24 Servo setup data
Positive software limit E 8001
exceeded (32769)
Word output from STATUSSV function
Programming Bit Location Hex
Characteristic Binary value Hex Error (high byte) Value
(in lad-
Move started 00000000 0000000(1) 0001 8 7 6 5 4 3 2 1 der)
Fast input occurred 00000000 000000(1)0 0002 Set whenever a P error X 8000
Fast input on 00000000 00000(1)00 0004 occurs. (32768)
Good mark detected 00000000 0000(1)000 0008 Master axis beyond E 8800
start point (34816)
Bad mark detected 00000000 000(1)0000 0010
DIST + TOLR 00000000 00(1)00000 0020 Slave axis beyond start E 8400
point (33792)
exceeded
Fast input rising 00000000 0(1)000000 0040 Master distance not E 8200
valid (33280)
E-stop Bit Location Hex Slave distance not E 8100

Error (low byte) Value valid (33024)
(in
8 7 6 5 4 3 2 1 Programming Bit Location Hex
ladder)
Error (low byte) Value
SERCOS syn- E 8020 (in
chronization (32800) 8 7 6 5 4 3 2 1 ladder)
error
The FAST axis in the E 8080
SERCOS drive E 8010
FAST_QUE function (32896)
E-stop (32784)
moved too far in
User-set E 8008 wrong direction
(32776)
Profile number not E 8040
Overflow error E 8004 found (32832)
(32772)
Master axis not 8020
Excess error E 8002 E
available (32800)
(32770)
Master start position for E 8001
Loss of E 8001 lock on (32769)
feedback (32769)
Appendix C - PiCPro Reference Card 501

Variables used with the READ_SV (Read column) and WRITE_SV (Write column) func-
tions. These variables are used with servo (S), time (T), and/or digitizing (D) axes.
V# Variable Description Read Write V# Variable Description Read Write
1 Actual position S, T, D T 29 Reference switch position S
2 Move Type S 30 Filter time constant S S

11 position, 12 distance, 14 veloc-
ity start, 16 fast/ladder reference, 31 Filter error limit S S
18 ratiopro, 20ratiosyn/gear, 22
32 Velocity compensation flag S S
ratiocam, 23 ratioslp, 24 ratioreal
33 Filter lag S
3 Command position S, D
34 Position change over several S, D S, D
4 Position error S
interrupts
5 Slow velocity filter error S
35 Part reference offset S, D
6 Command velocity S, T T
36 Software upper limit S S
7 Position change S, D
37 Software lower limit S S
8 Feedback last S, D
38 Commanded position (before S, D
9 Fast input position S, D slow velocity filter)
10 Reg/ref position change S, D 39 Following error limit S S
11 Consecutive bad marks S, D S, D 40 In-position band S S
12 Rollover on position S, T, D S, T, D 41 Current segment number S
13 Slave offset incremental S S 42 Slave distance into segment S
14 Master offset incremental S S 43 Master distance into segment S
15 Slave offset absolute S S 44 Set user iteration command S S
16 Master offset absolute S S 45 User iteration command S S
17 Slave offset filter S 46 Set user PID command S S
18 Master offset filter S 47 User PID command S S
19 Fast input direction S, D 48 Disable servo software S S
20 Fast input distance S, D 49 (Reserved)
21 Reversal not allowed S S 50 Override endlimit check S S
22 Fast input position (software) S, D 51 SERCOS command position S
23 Position (software) of axis 1 with S, D S, D 55 Queued move type S

fast input on axis 2 11 position, 12 distance, 14 veloc-
ity start, 16 fast/ladder reference,
24 Registration switch S, D S, D 18 ratiopro, 20ratiosyn/gear, 22
ratiocam, 23 ratioslp, 24 ratioreal
25 Fast queuing S S
58 SERCOS modulo value S
26 Synchronized slave start S, D, T S, D,T
59 Command position based Master/ S S
27 Backlash compensation S S Slave
28 TTL feedback S, D S, D 60 Servo axis S-curve interpolation S S
61 SERCOS velocity compensation S S
62 Velocity compensation filter S S
63 Resumable E-Stop allow S
64 Resume distance S
502 Appendix C - PiCPro Reference Card

SERCOS Errors
The errors listed below can appear at the ERR output of certain SERCOS functions/function blocks.
ERR # Description
0 No error
1 IDN queue was busy when called.
2 Quantity specified in the .AVAIL structure member is not large enough for received data.
3 Axis is not initialized, is not a SERCOS axis, or the slot/ring/slave specification is incorrect.
4 Invalid data in DATA input structure
5 Error reset function could not be completed.
6 SERCOS ring 1 busy
7 SERCOS ring 2 busy
8 SERCOS ring 1 configuration size error
9 SERCOS ring 2 configuration size error
10 Function block enabled while already in process
11 Bit 3 or bit 8 set in the procedure command acknowledgment (data status)
Either operation data invalid or procedure command error
12 Not enough pool memory available
13 Change bit in status word was zero after reference complete.
14 The IDN queue was cleared during an IDN transfer, typically caused by calling the SC_INIT function while an IDN is
being read or written.
15 SERCOS module is unavailable for IDN transfer because the phase-to-phase transistion in progress is between phase 2
and phase 4.
16 Slave response timed out
17 The SERCOS module did not receive an expected AT response. SERCOS cable may be disconnected.
18 Number of SERCOS slots equals zero.
19 The SERCOS module did not receive an expected MDT response. SERCOS cable may be disconnected.
20 Phase 0 detected that the ring is not complete. The optic cable could be open or drive turned off.
21 The SERCOS module firmware is outdated for the features requested from a newer version of the motion library.
22 The SERCOS module firmware is a newer version and the motion library is outdated and unable to interface.
23 The version of PiCPro used to create the SERCOS setup data is outdated for the features requested from the library or the
SERCOS module firmware.
24 The version of PiCPro used to create the SERCOS setup data is a newer version and the library is unable to interface.
25 A two-ring SERCOS module was specified in SERCOS setup but the module is a one-ring SERCOS module.
26 Invalid PRB input on the SCA_PBIT or SCA_RFIT function blocks or invalid OPTN input on the SCA_RFIT function
block.
27 The SERCOS setup data was configured for a different CPU (PiC, MMC, or MMC for PC).
28 The SERCOS ring is not currently halted in phase 2. SERCOS setup may not have specified "Pause after Phase 2".
29 The axis is in Resume Mode or Resumable E-Stop Allow (READ_SV/WRITE_SV Variable 63) is set
30 The drive status word (bit 13=1) indicates an error.
31 An E-stop condition exists for this axis in the PiC900.
32 Incorrect phase number, contact Sheffield Automation.
33 Incorrect address error, contact Sheffield Automation.
34 Incorrect AT number error, contact Sheffield Automation.
35 Variable 48 is set to 1 and you’ve attempted to close the loop
36 OPTN input is invalid.
37 The quantity specified in the .AVAIL structure member is not large enough for the received data. The actual size of the
received data is returned in the .ACTUAL structure member. This error is reported by the motion library software
38 Open loop was requested while SCA_CLOS was in progress.
48 Service channel not ready when attempt to send/receive non-cyclic data
49 No data to send or receive
50 The value of the .SIZE member of the TASK input structure does not match the byte count in the SERCOS module.
51 The value of the .SIZE member of the MAIN input structure does not match the byte count in the SERCOS module.
65 Error occurred calculating when MDT should occur.
66 Error occurred calculating when drive data valid.
67 Error occurred calculating when feedback data valid.
68 Error occurred calculating total time required for communication cycle.
69 Error occurred calculating cyclic data memory for SERCON processor.
Appendix C - PiCPro Reference Card 503

70 Error occurred calculating cyclic data memory for internal memory map.
71 Error occurred calculating service channel memory map.
72 Incorrect ring error, contact Sheffield Automation.
73 Incorrect AT count error, contact Sheffield Automation.
74 CPU on SERCOS module has too many tasks during update.
128 Slave error occurred. Read SERR output to identify error. The SLV output indicates the slave number.
136 Slave will not respond in phase 1. The SLV output indicates the slave number.
144 Procedure command error - The slave number can be viewed at the SLV output and the IDN number at the IDN output.
152 CRC error. The bit pattern received by the SERCOS receiver is corrupted.
The errors listed below can appear at the SERR output of certain SERCOS functions/func-
tion blocks.
SERR # Description SERR # Description
4097 This IDN does not exist. 20482 The minimum value transmission is too short.
4105 The data for this IDN may not be accessed. 20483 The minimum value transmission is too long.
8193 The name does not exist. 20484 The minimum value may not be changed.
8194 The name transmission is too short. 20485 The minimum value is write-protected.
8195 The name transmission is too long. 24577 The maximum value does not exist.
8196 The name may not be changed. 24578 The maximum value transmission is too
short.
8197 The name is write-protected. 24579 The maximum value transmission is too long.
12290 The attribute transmission is too short. 24580 The maximum value may not be changed.
12291 The attribute transmission is too long. 24581 The maximum value is write-protected.
12292 The attribute is write-protected at this time. 28674 The data is too short.
16385 The units do not exist. 28675 The data is too long.
16386 The units transmission is too short. 28676 The data may not be changed.
16387 The units transmission is too long. 28677 The data is write-protected at this time.
16388 The units may not be changed. 28678 The data is smaller than the minimum value.
16389 The units are write-protected at this time. 28679 The data is larger than the maximum value.
20481 The minimum value does not exist. 28680 The bit pattern for this IDN is invalid.
Data Capture
Axis variables that can be captured on a servo interrupt basis with the CAPTINIT
function.
VAR Description Type VAR Description Type
1 Actual position DINT 9 Prefilter commanded DINT
2 Fast input BYTE 10 Prefilter command change INT
3 Commanded position DINT 11 Remaining master offset DINT
4 Position error DINT 12 Remaining slave offset DINT
5 Slow velocity filter error INT 13 Command change DINT
6 Command change INT 14 Position change DINT
7 Position change INT 15 Prefilter command change DINT
8 Feedback position DINT
Error numbers and descriptions for CAPTINIT function ERR output are:
0 No error
1 The CAPTSTAT function has not stopped capturing data from a previous data capture
initialization.
2 An axis number in the structure is invalid.
3 The limit of eight variables in the array of structures has been exceeded.
4 Parameter number in the structure is out of range.
5 The CAPINIT function was called before the STRTSERV function was called.
504 Appendix C - PiCPro Reference Card

APPENDIX D - Stepper Reference Card
Stepper Reference Card
# Profile Commands Range # Control Words
1 Distance move ±2,147,352,575 steps 1 Enable profile
2 Position move ±2,147,352,575 steps 2 Pause profile
3 Velocity move ±1,000,000 steps/sec 3 Continue profile
4 Set maximum velocity 1-1,000,000 steps/sec 4 E-stop
5 Set acc/dec rate 1-16,777,215 steps/sec/sec 5 C-stop
6 Set reference ±2,147,352,575 steps 6 Step/direction mode

(default)
7 Pause N/A 7 CW/CCW mode
Word output from STEPSTAT function
Characteristic Binary value Decimal Hex
Profile enabled 00000000 0000000x(1) 1 0001
Profile paused 00000000 000000x(1)0 2 0002
At velocity 00000000 00000x(1)00 4 0004
Que empty 00000000 0000x(1)000 8 0008
Que full 00000000 000x(1)0000 16 0010
Control word not processed 00000000 00x(1)00000 32 0020
Errors displayed in the .ERROR member of stepper structure #
No error 0
Invalid rack number or remote rack not available 1
Invalid slot number 2
Module not found at rack and slot location or not enough channels on module 3
Invalid command number 4
Invalid data for the command 5
Invalid control number 6
Stepper function called before STEPINIT function called 7
Appendix D - Stepper Reference Card 505

506 Appendix D- Stepper Reference Card
APPENDIX E - Diagnostic LED Error Codes
Error Codes
While the control is running, the DIAG LED on the CPU module (status software with
MMC for PC) will flash a three digit code signal if there is an error. For example, if there
is a long pause-flash-pause-flash-flash-pause-flash-flash-flash-long pause, the code is 123.
The errors are described below
Code Error Description
122 No math coprocessor Attempted to perform floating point operation with no math coprocessor
installed on the CPU.
123 Scan too long A ladder scan loss has occurred because the CPU takes more than 200 ms to
scan the application program.
Whenever the scan light is out, the discrete outputs go to the OFF state and
the analog outputs are zeroed.
124 Excessive overhead The system overhead update time is excessive.
125 Insufficient memory There is insufficient memory on the CPU to run the current program.
126 No hardware bit memory There is no bit memory installed on the CPU and the program requires it.
127 No software bit memory There is no bit memory capability via software and the program requires it.
222 Driver error No driver support on the CPU for the I/O module. Update your system
EPROMs.
22_ Master rack error The I/O modules in the master rack do not match what was declared in the
hardware master declaration table. The number of flashes in the third digit
identifies the slot number that is in error.
231* No daughter board There is no communications daughter board installed on the CPU when
attempting to do expansion I/O communications.
232* Communications error A failure has occurred in remote I/O communications.
233* Number of racks error The number of expansion racks in the system does not match the number of
expansion racks declared in the expansion hardware declaration table.
24_ Master rack error The I/O modules in the MMC for PC master rack do not match what was
declared in the hardware master declaration table. The number in the third
digit identifies the slot number that is in error.
25_ ASIU Error The ASIU modules found do not match what was declared in the hardware
master declaration table. One or more ASIU modules may have the same
address switch setting. The number in the third digit indicates the ASIU
address.
3_ _* Expansion rack error The I/O modules in the expansion rack(s) or the block I/O modules do not
match what was declared in the expansion hardware declaration table.
For rack expansion:
The number of flashes in the second digit indicates the remote rack
(1 through 8). The number of flashes in the third digit indicates the slot num-
ber.
For block I/O modules:
The number of flashes in the second and third digits indicates the block I/O
module (01 through 77). The second digit will flash a 1 - 7, 10 for 0. The third
digit will flash a 1 - 9, 10 for 0. For example, if the second digit flashes 3
times and the third digit flashes 10 times, the module is 30.
260 ASIU Data Overrun Error The specified nmber of axes at the specified update rate exceeds the through-
put capacity of CPU to ASIU communications.
* Errors connected with I/O expansion. Refer to the I/O Driver Module write-up in the PiC900 Hardware
Manual for more information.
Appendix E- Diagnostic LED Error Codes 507

508 Appendix E - Diagnostic LED Error Codes
APPENDIX F - IBM ASCII Chart
ASCII Chart
Dec Hex Char Dec Hex Char Dec Hex Char Dec Hex Char
00 0x00 NUL 32 0x20 SPC 64 0x40 @ 96 0x60 `
01 0x01 33 0x21 ! 65 0x41 A 97 0x61 a
02 0x02 34 0x22 " 66 0x42 B 98 0x62 b
03 0x03 © 35 0x23 # 67 0x43 C 99 0x63 c

04 0x04 ® 36 0x24 $ 68 0x44 D 100 0x64 d
05 0x05 ß 37 0x25 % 69 0x45 E 101 0x65 e
06 0x06 ™ 38 0x26 & 70 0x46 F 102 0x66 f
07 0x07 BEL 39 0x27 ' 71 0x47 G 103 0x67 g
08 0x08 BS 40 0x28 ( 72 0x48 H 104 0x68 h
09 0x09 HT 41 0x29 ) 73 0x49 I 105 0x69 i
10 0x0A LF 42 0x2A * 74 0x4A J 106 0x6A j
11 0x0B VT 43 0x2B + 75 0x4B K 107 0x6B k
12 0x0C FF 44 0x2C , 76 0x4C L 108 0x6C l
13 0x0D CR 45 0x2D - 77 0x4D M 109 0x6D m
14 0x0E 46 0x2E . 78 0x4E N 110 0x6E n
15 0x0F j 47 0x2F / 79 0x4F O 111 0x6F o

16 0x10 ˜ 48 0x30 0 80 0x50 P 112 0x70 p
17 0x11 ÿ 49 0x31 1 81 0x51 Q 113 0x71 q
18 0x12 Þ 50 0x32 2 82 0x52 R 114 0x72 r
19 0x13 ! 51 0x33 3 83 0x53 S 115 0x73 s
20 0x14 ¶ 52 0x34 4 84 0x54 T 116 0x74 t
21 0x15 § 53 0x35 5 85 0x55 U 117 0x75 u
22 0x16 - 54 0x36 6 86 0x56 V 118 0x76 v
23 0x17 Þ 55 0x37 7 87 0x57 W 119 0x77 w
24 0x18 ¦ 56 0x38 8 88 0x58 X 120 0x78 x
25 0x19 Ø 57 0x39 9 89 0x59 Y 121 0x79 y
26 0x1A Æ 58 0x3A : 90 0x5A Z 122 0x7A z
27 0x1B ¨ 59 0x3B ; 91 0x5B [ 123 0x7B {
28 0x1C ¿ 60 0x3C < 92 0x5C \ 124 0x7C :
29 0x1D 61 0x3D = 93 0x5D ] 125 0x7D }
30 0x1E s 62 0x3E > 94 0x5E ^ 126 0x7E ~
31 0x1F t 63 0x3F ? 95 0x5F _ 127 0x7F ›
Appendix F - BM ASCII Chart 509

Dec Hex Char Dec Hex Char Dec Hex Char Dec Hex Char
128 0x80 Ç 160 0xA0 à 192 0xC0 ¿ 224 0xE0 ‡
129 0x81 ü 161 0xA1 í 193 0xC1 ¡ 225 0xE1 ·
130 0x82 é 162 0xA2 ó 194 0xC2 ¬ 226 0xE2 ‚
131 0x83 â 163 0xA3 ú 195 0xC3 Ð 227 0xE3 „
132 0x84 ä 164 0xA4 ñ 196 0xC4 ƒ 228 0xE4 ‰
133 0x85 à 165 0xA5 Ñ 197 0xC5 Ý 229 0xE5 Â
134 0x86 å 166 0xA6 ª 198 0xC6 ý 230 0xE6 Ê
135 0x87 ç 167 0xA7 º 199 0xC7 « 231 0xE7 Á
136 0x88 ê 168 0xA8 ¿ 200 0xC8 » 232 0xE8 Ë
137 0x89 ë 169 0xA9 © 201 0xC9 … 233 0xE9 È
138 0x8A è 170 0xAA ™ 202 0xCA þ 234 0xEA ¾
139 0x8B ï 171 0xAB ´ 203 0xCB À 235 0xEB Î
140 0x8C î 172 0xAC ¨ 204 0xCC Ã 236 0xEC ×
141 0x8D ì 173 0xAD ¡ 205 0xCD Õ 237 0xED ý
142 0x8E Ä 174 0xAE « 206 0xCE Œ 238 0xEE Œ
143 0x8F Å 175 0xAF » 207 0xCF œ 239 0xEF «
144 0x90 É 176 0xB0 × 208 0xD0 – 240 0xF0 ½
145 0x91 Æ 177 0xB1 ± 209 0xD1 — 241 0xF1 ±
146 0x92 Æ 178 0xB2 ð 210 0xD2 “ 242 0xF2 Š
147 0x93 ô 179 0xB3 Š 211 0xD3 ” 243 0xF3 ð
148 0x94 ö 180 0xB4 ¥ 212 0xD4 ‘ 244 0xF4 Ù
149 0x95 ó 181 0xB5 µ 213 0xD5 ’ 245 0xF5 €
150 0x96 û 182 0xB6 ¹ 214 0xD6 ÷ 246 0xF6 ³
151 0x97 ù 183 0xB7 ² 215 0xD7 Þ 247 0xF7 Ý
152 0x98 ÿ 184 0xB8 ³ 216 0xD8 ÿ 248 0xF8 °
153 0x99 Ö 185 0xB9 ¼ 217 0xD9 Ÿ 249 0xF9 •
154 0x9A Ü 186 0xBA ½ 218 0xDA ⁄ 250 0xFA Ž
155 0x9B ¢ 187 0xBB ª 219 0xDB ¤ 251 0xFB Ð
156 0x9C £ 188 0xBC º 220 0xDC ‹ 252 0xFC ¸
157 0x9D ¥ 189 0xBD ¾ 221 0xDD › 253 0xFD ″
158 0x9E û 190 0xBE æ 222 0xDE ? 254 0xFE ž
159 0x9F ü 191 0xBF ø 223 0xDF ? 255 0xFF
510 Appendix F - BM ASCII Chart

APPENDIX G - Time Axes
Using a Time Axis
The time axis feature allows a servo axis to be slaved to time instead of a physical
master position transducer. All the master/slave functions can be used with a time
axis.
If time axes are going to be used they must be defined in Servo Setup. There are
four axis numbers reserved for a time-based master; 25, 26, 27, and 28. This is the
number used to identify the master time axis on the input to a master/slave func-
tion i.e. RATIO_GR.
The S_CURVE or ACC_DEC functions or the command velocity variable 6 can be
used to move a time axis. The time axis can be manipulated with variables 1, 12,
and 26. Use the WRITE_SV and READ_SV functions to work with these vari-
ables.
Referencing a Time Axis
Actual Position (Variable 1)
The actual position variable allows you to read the position of the time axis or
change the current position by writing a value with the WRITE_SV function.
Range: +2,147,483,647 to -2,147,836,648 counts.
Controlling Time Axis Velocity
You can use either the S-CURVE or ACC_DEC functions or the command veloc-
ity variable 6 to move a time axis.
S_CURVE and ACC_DEC Functions
When using the S_CURVE or ACC_DEC functions with a time axis, you can use
the distance, position, or velocity moves to move the axis. The S_CURVE or
ACC_DEC functions must be called first when using these moves. See the
S_CURVE and ACC_DEC descriptions in the Function/Function Block Reference
Guide.
Command Velocity (Variable 6)
If you are not using the S_CURVE or ACC_DEC functions, the command velocity
variable can be used to define how fast the time axis will travel. It is programmed
in counts per second. When the WRITE_SV function is called with variable 6, the
time axis will step to the programmed velocity.
For example, if a value of 1000 is programmed as the number of counts per second
for the velocity, then the time axis would move one count in one millisecond. If the
master distance (MDST) was set at 1000 and the slave distance (SDST) was set at
2000 in the RATIO_GR function, it would take the slave axis one second to move
2000 units.
511
By entering a zero, the time axis is stopped. This provides the ability to synchro-
nize multiple slave axes. You call all the moves you want to synchronize and then
write a non-zero value to variable 6. All the axes will begin motion at the same
time.
Note: In order for all slave axes to start at the same time, the master start position
of any master/slave move with a MSTR input would have to have the same value
(or zero) at its MSTR input. If the option to ignore master start is selected, the
slave axes will start when the master axis begins to move.
An alternative method for synchronizing slave starts is to use variable 26.
Range:+/-2,000,000 counts/sec.
Rollover on Position with a Time Axis
The rollover on position variable allows you to select where the time axis will reset
to zero. The variable is entered in ladder units.
Note: Without rollover on position, when 2,147,483,647 is reached, the next
number will be -2,147,483,648. The count continues to zero and back
up to 2,147,483,647, etc.
Range: 1 to 536,870,912 counts (Entering a zero turns rollover on position off.)
Synchronizing Slave Axes with a Time Axis
The synchronized slave start variable allows you to tell the time axis which of its
slave axes must be queued up before any of them begin their move. Each slave axis
you want to synchronize is identified by setting a bit in a DINT using the lower 16
bits where the LSB = axis 1 and the MSB = axis 16. When the last set axis has
been queued, all the slave axes will begin their move on the next interrupt.
The WRITE_SV function with variable 26 must be called before the move. It can
be called again when you want to identify a different set of synchronized slave
axes. Change the bits only after the slave axes identified in the first WRITE_SV
function have started to move.
Writing a zero to variable 26 clears all identified axes. The READ_SV function
can be used to read the number of slave axes being synchronized.
512
APPENDIX H - Stepper Axis Module Notes
Introduction - Stepper Axis Module
Stepper motors can be controlled by either of the following methods:

• The stepper motor control module (SMCM) using the PiCPro stepper func-
tions.
• The stepper axis module (SAM) using servo setup and the move types
available in the PiCPro motion library. It can be a master or a slave in the
application.
This appendix covers the stepper axis module. Any move type from the motion
library can be used to perform motion control with the stepper except those move
types requiring a fast input. There is no feedback from the stepper axis module.
Servo setup is used to set up the stepper axis module and create a start servo func-
tion. Once all the setup data has been entered, compile the servo function. This
function will be stored in the servo library and can then be called in your ladder
program to initialize the setup data for your application.
Notes on using Motion Library Functions and Variables with the Stepper
This section summarizes things you should be aware of when using the stepper and
the motion library of PiCPro.
READ_SV/WRITE_SV Functions
These READ_SV and WRITE_SV variables cannot be used when using the step-
per on an axis.
Var # Name
4 Position error
9 Fast input position (Hardware)
10 Registration/referencing position change
11 Consecutive bad marks
19 Fast input direction
20 Fast input distance
24 Registration switch
27 Backlash compensation
28 TTL feedback
29 Reference switch position
46 Set user PID command
47 User PID command
48 Disable servo software
All other READ_SV and WRITE_SV variables can be used with a stepper.
Note: Feedback units are stepper units. Ladder units may still be used.
TUNEREAD/TUNEWRIT Functions
The filter variable is the only one that can be read and written by these functions
when using a stepper axis. The remaining TUNEREAD/TUNEWRIT variables
cannot be used with a stepper axis.
Appendix H - Stepper Axis Module Notes 513

CLOSLOOP, OPENLOOP, REGIST, and MEASURE Functions
These functions cannot be used on a stepper axis.
Reference-Related Functions
The reference-related functions in PiCPro on the left below cannot be used with a
stepper axis. The functions on the right can be used with a stepper axis.
Not Available with Stepper Available with Stepper
FAST_REF PART_REF
LAD_REF PART_CLP
REF_DNE
REF_END
STRTSERV Function
Call STRTSERV to initialize the stepper axis and begin the stepper motion.
ERRORS
There is no loss of feedback or excess error. If an E-stop error occurs, the com-
mand to the stepper will be zeroed.
514 Appendix H - Stepper Axis Module Notes

APPENDIX I - Toolbar Buttons
Here is a list of the toolbars available in PiCPro.
• Servo - Standard Toolbar and SERCOS - Standard Toolbar
• Drive List - Standard Toolbar
• Custom Motor
• Standard
• Basic Online Operations
• Advanced Operations
• Ladder
• View Navigator
• Function/Function Block
• Compiler
• Structured Text Tools
• Insert New Network
Toolbars and tool buttons are shown below.
Appendix I - Toolbar Buttons 515

Servo - Standard Toolbar and SERCOS - Standard Toolbar
New Document
Open Document
Save Document
Cut
Copy
Paste
Print
About
Help
Options
Stop the Scan
Run One Scan
Hot Restart (Red Arrow)
Warm Restart (Yellow Arrow)
Cold Restart (Blue Arrow)
Backup User Program
Restore User Program
Reset Power
Control Status
Drive Maintenance
516 Appendix I - Toolbar Buttons

Drive List - Standard Toolbar
New Document
Open Document
Save Document
Cut
Copy
Paste
Undo
Redo
Print
About
Help
Options
Display Drive Data
Rename Drive
Drive Maintenance
Download to Drive
Reset Faults
Reset Peaks

Set User Faults
Cold Restart
Control Panel

Custom Motor Toolbar
New Document
Open Document
Save Document
Cut
Copy
Paste
Undo
Redo
Print
About
Help
Options
Choose Default Motor Values

Standard Toolbar
New Document
Open Document
Save Document
Cut
Copy
Paste
Print
About
Help
Options

Basic Online Operations Toolbar
Stop the Scan

Run One Scan
Hot Restart (Red Arrow)
Warm Restart (Yellow Arrow)
Cold Restart (Blue Arrow)
Backup User Program
Backup Ramdisk
Restore User Program

Reset Power
PiC Status
Drive Maintenance
Advanced Operations Toolbar
Toggle Animation
Toggle Forcing
Group Enable
Update Force Values
Abort last patch

Ladder Toolbar
Pointer
Normally Open Contact
Normally Closed Contact
Normally Open Positive Transition Contact
Normally Closed Positive Transition Contact
Normally Open Negative Transition Contact
Normally Closed Negative Transition Contact
Energized Coil
De-energized Coil
Set Coil
Reset Coil
Horizontal Wire
Vertical Wire
Combination Wire
Point to Point Wire
Jump to Label
Jump to Subroutine
Return from Jump

View Navigator Toolbar
Display Software Declarations

Displays Hardware Declarations
Displays View List
Update Forcing List
Toggles Long Name Display
Zoom Display Out
Zoom Display In
Function/Function Block Toolbar
Function/Function Block List

Place the Selected Function
Data In
Data In Inverted
Data Out
Compiler Toolbar
Compile Bin File

Compile and Download Bin File
Dump a Hex-86 File
Build a Task
Build a UDFB

Structured Text Tools Toolbar
IF-THEN
IF-THEN-ELSE
ELSEIF-THEN-ELSE
CASE
FOR-DO
WHILE-DO
REPEAT-UNTIL
Insert Variable
Check ST Syntax

Insert New Network Toolbar
Insert Ladder Network
Insert Structured Text Network

APPENDIX J - Module Filenames
The following tables list the files that are created during the programming process.
Extensions Type of File Created/Updated Upon
ADV Drive parameters from an analog interface Save from MMC Smart
Analog Interfaced Digi- digital drive and associated motor param- Drive Setup
tal Drive System File eters.
BAK Backup copy of library file - the version Save

Library Backup created with the last save
BIN Compiled (PiC language) ladder file - Compile or compile and

Binary cannot be converted back into uncompiled download
state for animating, etc.
DPL List of all the files the currently loaded Build dependency list
Dependency List module depends upon
FRC List of variables that can be forced and Save, if forced variables
Forcing their values are designated
G&L Compresses the project file created in New project

Giddings & Lewis Project Manager
HEX Hex representation of the ladder file Hex compile

Hexadecimal
HTM HTML Help file you create to define your Edit Function Block Help
HTML UDFBs
LBK Backup copy of the ladder file -- the ver- Save

Ladder Backup sion previous to the version created with
the last save
LDO Ladder or network logic file Save
Ladder Diagram Object
LIB User-defined functions/function blocks to Make function, compile
Library be used in ladder UDFB/Task
LST Print file containing ladder, REM, cross Print

List reference, formatted for printing
MAP Produces a readable symbol map file Compile when Generate

MAP Symbol Map is checked
in Settings
OID Used to support the operator interface or Compile when Construct
Operator Interface Defi- Ethernet module Data File is checked in
nition Settings
PPR Used to restore program to the control Save to File is chosen in

PicPro Restore the PiC Restore dialog
Appendix J - Module Filenames 525

PRJ Contains a project generated from Project New project
Project Manager
RBK Backup copy of the remarks file Save

Remarks Backup
REM The documentation or comments for all Save
Remarks networks in a module
RTD List of variables in the View Variables Edit view list

Real Time Display List
SCP Contains the control panel and oscillo- Save Scope Template
Scope Template scope settings
SCT Viewing and tuning data for the SERCOS Save

SERCOS View/Tune axes used in application
SRC SERCOS setup data for SERCOS axes Save

SERCOS setup used in application
SRV Setup data for all servo axes used in appli- Save
Servo setup cation
SVT Viewing and tuning data for the servo Save

Servo View/Tune axes used in application
TXT Contains the oscillosope trace Save Trace

Trace Text
UCP Used by the configuration tool when Save from the G&L
Universal Communica- downloading the personality file to the DeviceNet Configuration
tion Personality DeviceNet scanner module Tool
UCT Used by PiCPro when downloading your Save from the G&L
Universal Communica- ladder DeviceNet Configuration
tion Text Tool
526 Appendix J - Module Filenames

APPENDIX K - Service Pack Installation
Service Pack Installation
The WiseUpdate installation update program allows you to locate PiCPro Service Packs
at a specified Sheffield Automation Internet website location. This program is automati-
cally installed when PiCPro is installed.
Note: Connection to the Internet is required to use this program.
This update program can be used on either a case by case manual basis or be set to work
automatically.
Service Pack Update Installation - Manual Method
The update program can be started manually in one of three ways:

• From the Windows Start menu select:
Start | Programs | PiCPro for Windows | Check for PiCPro Vxx
Updates.
Where xx represents the version of software installed.
• From within PiCPro, using Help | Check for Updates. If the updated pro-
gram is started from the PiCPro Help menu, it can be run at the same time
as PiCPro.
527
• Or after PiCPro installation is complete by using a check box.
Check the box for Yes, I want to check the Internet for updates and
Click Finish.
Note: If the update program is downloaded, it will not be installed
until PiCPro is closed.
528
The update program can now be downloaded as follows:
1. The following window will be displayed:
Clicking on the Advance button will bring up a dialog that allows you to
change the Internet access server and the time period between update
checks.
2. Make the desired changes in the Advanced Settings dialog and click
OK.
529
3. Click Next and the update program will check for any PiCPro updates.
If you already have the latest PiCPro Service Pack, a message box will
be displayed stating the following:
You are currently running the latest version of PiCPro V14.0 "Edi-
tion" Please check for updates again in the future. Click OK.
If a new PiCPro Service Pack exists, a dialog will be displayed stating

the following:
Your are now ready to download the update to PiCPro Vxx.xx Edi-
tion.
If PiCPro is opened, PiCPro will automatically be closed before the

download starts.
Press the Next button to begin the download. After the update is
downloaded you will be prompted to run the installation to update
your software to the newest version.
4. After the download is complete, a dialog will be displayed stating the

following:
The update for PiCPro Vxx.xx Edition has been successfully down-
loaded.
5. Click the Finish button to execute the update installation.
Service Pack Installation - Automatic Mode
When run in automatic mode, the update program is added to the start of PiCPro
and is executed every time PiCPro is started.
530
The update program is set up for automatic mode by doing the following:
1. From the PiCPro menu, choose View | Options.
2. Check the box for Automatically Check for Updates.

3. Specify the time period between updated checks in the Check every
___ days field.
4. Click OK.
5. Follow steps 1 through 5 from the previous section titled “Service Pack
Update Installation - Manual Method.
531
532
APPENDIX M - Virtual Axis
Virtual Axis
A virtual axis is a servo axis with no feedback hardware and no command output hardware.
It can perform all the same functions as a normal servo axis: motion functions, master/
slave functions, registration, referencing, etc. A virtual axis is created by specifying “Vir-
tual” for the Output Type and Input Type of a servo axis in Servo Setup.
The control uses the virtual axis’ command position to generate a simulated feedback posi-
tion. If the rollover position = 0, when a feedback value of 2,147,483,647 is reached, the
next value will be -2,147,483,648. The count continues to zero and back up to
2,147,483,647, etc.
When using REGIST, FAST_REF, MEASURE, or FAST_QUE with a virtual axis, the lad-
der can simulate the fast input by calling the VFASTIN function.
Note: When all of the axes in an MMC for PC Analog control are declared as virtual axes,
it is required that at least one ASIU is connected to the control.
533
534
APPENDIX N- Firmware
Firmware
To determine whether you need to update firmware, select Online | Status from
the menu. Check the date you see here with the date of *.hex files in the Firm-
ware folder. Typically, you should be using the most current versions.
Here are the firmware (*.hex) files available:
Firmware Files Description
DRB####.hex MMC Smart Drive firmware

MMCPCA##.hex MMC for PC with an analog CPU
MMCPCS##.hex MMC for PC with a SERCOS CPU
MMC##.hex Standalone MMC
P904X##.hex PiC90 with a 486 processor (9041, 9043)
P94X##.hex PiC900 with a 486 processor (941, 943, 945, 947)
SERCO##.hex SERCOS module firmware
TCPIP##.hex Ethernet module firmware
CLRAPP.hex Clears ladder application on standalone MMC’s
and MMC for PC’s
CLRFLASH.hex Clears control’s flash memory
Where ## or #### are the versions numbers. See readme.txt for the versions com-
patible with this PiCPro software.
Memory Configuration Files are provided for configurable memory in PiC94x or
MMC for PC processors.
Memory Configuration Files
Firmware Files Application Memory RAMDisk Memory

CON512.hex (default) 512K 256K
CON640.hex 640K 128K
CON384.hex 384K 384K
CON704.hex 704K 64K
CON768.hex 768K 0K
Appendix N - Firmware 535

536 Appendix N - Firmware
APPENDIX O - Things to Consider When Con-
verting an Application from One CPU Type to
Another
• IPSTAT
The Ethernet functions for a PiC or standalone MMC do not require the
IPSTAT function because those CPU models have an external Ethernet
Module. An MMC for PC ladder with Ethernet functions will require the
IPSTAT function for its connection to the host operating system. Note:
IPSTAT will always return OK for a PiC or standalone MMC. OK will be
returned whether the reset input is on or off.
• A_INCHRD or A_IN_MMC
A PiC or MMC for PC ladder with an A/D input requires A_INCHRD.
A standalone MMC with an A/D input can use A_IN_MMC OR
A_INCHRD.
• I/O Points
All non-Block I/O points should be checked. (Block I/O points are not
affected by a change in CPU type.)
• Servo and SERCOS Setup
Any servo or SERCOS setup functions used must be opened, converted to
the new CPU type, and compiled.
• Serial Port Functions
When converting a ladder to an MMC for PC, all serial port functions must
be removed. (For example, OI_SER, etc.)
Appendix O - Things to Consider When Converting an Application from One CPU Type to Another 537
538 Appendix O - Things to Consider When Converting an Application from One CPU Type to Another
Application Note 1
Reading and Writing STRINGs from a Structure
The following applies only to Reading and Writing STRINGs that are members of
a Structure using just the structure name as the Memory Area (BUFR) input to
the READ and WRITE function blocks in PiCPro.
Any variable of type 'STRING' has an actual size that is 2 more than its 'Declared'
length. These two bytes are in the beginning of the STRING and are normally hid-
den from the user. The first byte contains the maximum or 'Declared' length of the
STRING, and the second byte contains the actual length of the STRING.
This means that the structure size will be increased by two bytes for every
STRING element in the structure.
Examples:
1. MY_STRUC STRUCT
.ONE DINT
.NAME STRING[10]
.TWO DINT
END_STRUCT
Example 1 has a size of 20 bytes (4 bytes for .ONE, 12 bytes for the .NAME ele-
ment and 4 bytes for .TWO).
2. MY_STR2 STRUCT
.NAMES STRING[10](0..3)
END_STRUCT
Example 2 has a size of 48 bytes (12 bytes for each STRING of 10, and it is an
array of 4 STRINGs).
So if you Write a structure that contains a 'STRING' type member, it is important
to write out the complete structure (i.e. if you write out MY_STR2 make sure you
write out 48 bytes and not 40 bytes).
Similarly if you Read into a structure that contains a STRING type member, it is
important to read in the complete structure (i.e. if you read in MY_STR2 make
sure you read in 48 bytes and not 40 bytes).
This does not apply if you Read from/Write to a STRING type variable itself. In
the example above, it would not apply if you read from/write to
MY_STRUC.NAME or MY_STR2.NAMES(3). In this case, PiCPro automati-
cally updates the two hidden length bytes as the STRING is read in.
Application Notes 539

Some additional examples:
1. Consider a ladder with a structure declared as:
MY_STR2 STRUCT
.NAMES STRING[10](0..3)
END_STRUCT
To write out all four STRINGs in the structure completely, you would use,
To read all four STRINGs into the structure completely, you would use,
Note that this also means that the device you are reading the STRINGs from in this
manner MUST store them in the following format:
1 BYTE 'Declared' Length in PiCPro (In this example 10)
1 BYTE Actual Length of the STRING (actual number of characters in this
STRING)
(The actual length must be less than or equal to the declared length)
BYTES of the STRING itself. (In this example 10 Bytes. Even if the actual number
of characters in the STRING is less than the Declared Length, the STRING must
be padded up to the declared length. You can use any character you choose to pad
the STRING.)
540 Application Notes

If you are reading from/writing to the STRING itself, you do not need to account
for the two hidden bytes as in the examples below. PiCPro will automatically
update these bytes when it knows the input to BUFR is a 'STRING'.
2. Consider a STRING declared as:
NAMES STRING[10](0..3)
To write out just one STRING completely, you would use,
To read in the NAME written above, you would use,
Application Notes 541

542 Application Notes
INDEX codes
diagnostic 507
A
coil 142
aborting a patch 192 cold restart 190
advanced operations toolbar 520 command velocity (variable 6) 511
analog input setup 290 comment export 199
analog output offset 308 comment import 199
animating the ladder 181 comments 139
application note communications
reading strings from a structure 539 baud rate 200
arrays 116 extend timeouts 200
ASCII infrared drivers 4
chart 509 IP address 200
ASIU I/O numbering 478 port 200
AT - Amplifier Telegram 329 serial 200
attribute 128 settings 200
external 129 TCP/IP 200
global and retentive 129 comparing to cyclic data 332
retentive 128 comparing to service channel 332
variable in/out 129 comparing UDFBs and Tasks 384
auto fill axes 295 compile error messages
axis data 296 ladder 430
axis positioning,SERCOS 338 compiler toolbar 522
axis properties 296 compiling
axis tuning 322 Bin file 173
using forcing 322 Hex file 175
using viewing 323 ladder 173
variables 324 SERCOS setup function 353
B servo setup function 320
Task 176
backup 206 UDFB 177, 380
backup application 173 computer workstation 3
basic online operations toolbar 520 configuration
battery box 359 DeviceNet software 398
Bin file 173 Profibus software 405
block expansion rack I/O connecting hardware 4
numbering 110, 478 constants 139
blown fuse status 111, 478 contacts 141
build a dependency list 198 controlling a time axis velocity 511
C converting
servo setup CPU 321
calculate defaults 299 copying
calling Technical Support 3 a Project 48
changing memory configurations 19 an item 75
Clear application memory 206 axis information 317
closing files 86 between SRC files 350
543
hardware declarations 98 dragging and dropping 77
SERCOS data 350 drive list-standard toolbar 517
software declarations 130 duplicate 84
SRS structure 358 E
copying and deleting 73
creating editing
a New Project 40 axis data 296
new files 51 axis properties 296
SERCOS setup file 339 function block help 21
servo setup file 211, 281 hardware declarations 97
servo setup function 320 IDNs 345
Task 388 IDNs for send 365
UDFB 377 servo setup 296
C-stop error codes 421, 422 software declarations 129
customer service 2 startup IDN list 344
customizing PiCPro 11 UDFB 380
cutting an item 74 encoder input setup 288
cyclic data structures 348 entering
cyclic operation 332 forcing variables 183
iterator data 301, 305, 311
D iterator data for time axis 307, 310
D/A output setup 288 network 70
data handling in UDFBs 380 position loop data 307
data type scaling data 298
arrays 116 entering software declarations 102
numeric 114 error codes 415
structures 116 C-stop error codes 421, 422
time 115 diagnostic 507
data types E-stop error codes 422
inputs/outputs 409 function codes 415
define cyclic data 346 LED codes 507
define operation mode 349 programming error codes 424
Delete 73 servo timing error function 426
dependency list 198 stepper 514
errors 433 error messages
derivative gain 308 compile ladder 430
determining scaling information 300 dependency list 433
device status (Profibus) 408 hardware 433
device status code 401 library 433
device status word 400 servo 485
DeviceNet configuration software 397 E-stop error codes 422
procedure 398 execute procedure command 366
diagnostic error codes 507 exiting 86
dialog boxes 10 expansion rack I/O
displaying/hiding toolbars 16 numbering 109, 477
Download a hex file 202 export comments 199
544
extended data memory 179 H
working with 180 hardware connections 4
external attribute 129 hardware declarations 88
F closing 101
copying 98
fast inputs 112
cutting 98
faults, diagnostic 507
editing 97
feed forward percent 308
pasting 99
files
printing 100, 196
created types 525
saving 101
extensions 525
hardware error messages 433
organizing 17
help 19
filter search 83
creating Function Block Help 21
find
editing Function Block help 21
IDNs 372
Function Block 20
finding and replacing 80
Whats This 19
finding duplicates 84
help files 10
focus 68
Hex file 175
following error limit 308
forcing I
entering variables 183 I/O point 105
variables 182 I/O Points, numbering 108
forcing/grouping 185 IDNs 329
Function Block Help 20, 21 insert for receive continuous 363
edit 21 insert for send 365
function/function blocks 145 insert startup 345
data 145 parameter data 330
functions PCF 330
error codes 415 print 372
inputs receive 361
data types 409 receive continuous 363
outputs search 372
data types 409 send 364
SERCOS 326 import comments 199
SERCOS setup 353 information window 6
servo setup 320 infrared communication drivers 4
with Stepper Axis Module 513 initial values 112
functions toolbar 522 prefixes 112
G initialize
servo setup data 321
G&L scanner symbol 400
in-position band 309
G&L TCP/IP configuration software
input polarity 308
procedure 402
input scaling 298
global and retentive attribute 129
insert new network toolbar 524
grouping 185
inserting
IDNs 345
545
IDNs for send 365 jump command 146
networks 70 label 138
software declarations 130 wires 143
installation numeric 114
program directory 17 O
integral error limit 308
integral gain 308 off-line editing (UDFB) 380
interlocking Task data 392 on-line editing 191
introduction to PiCPro 1 on-line editing (UDFB) 381
iterator data 301, 305, 311 online Help system
iterator data for time axis 307, 310 printing 20
opening
J a Project 43
jump command 146 an existing ladder 53
SERCOS setup file 339
L
servo setup file 282
label 138 operation mode
ladder toolbar 521 defining 349
LED error codes 507 operator interface 179
libraries 17 options
library setting 11
error messages 433 options for IDN display 370
long names 103 organizing your PiCPro files 17
M output
polarity 308
master rack I/O scaling 298
numbering 477 Overview
MDT - Master Data Telegram 329 Using Projects 23
memory configurations 19
memory, extended data 179 P
menu bar 9 parameter data IDNs 330
MMC for PC pasting an item 75
SERCOS 326 patching the ladder 191
MST - Master Synchronization Telegram 329 PCF
N IDNs 330
phases
naming SERCOS 331
Task 389 PiC
UDFB 378 and SERCOS 326
variables 103 restore 19
NEMA SERCOS Specification 325 PiCPro
network closing files 86
coil 142 copy command 73
comments 139 creating files 51
contacts 141 customizing 11
elements 141 define 1
function/function blocks 145
546
deleting command 73 procedure 406
entering networks 70 program directory 17
exiting 86 programming error codes 424
filtering search 83 Project 43
finding and replacing 80 copy 48
finding duplicates 84 include sources 27
getting started 1 launch 47
libraries 17 new 40, 41
opening a file 53 open 43, 44
organizing files 17 open compressed 44
printing 19 open from control 44
programs 1 print 48
reference card 501 save as 48
saving 85 uncompress 44, 45
scanning 189 version mismatch 47
searching in 82 project
selecting items 68 paths 49
splitting the screen 86 Projects 23
starting 22 projects
tools 67 commands 23
work area 5 managing 23
working in 51 proportional gain 308
pointer tool 67 purging unused variables 136
position loop data 307 R
printing 19
comments 195 racks
cross reference 195 numbering 109
force list 196 receive continuous IDNs
hardware declarations 196 SERCOS
IDNs 372 IDNs
information window 196 receive continuous 362
ladder 193 receive IDNs 361
long names 195 recommended workstation 3
online Help system 20 reference card
projects 48 PiCPro 501
SERCOS 353 referencing a time axis 511
servo setup axis information 319 requirements 3
view list 196 resolver input setup 290
procedure restore 173, 206
DeviceNet configuration software 398 restore PiC 19
G&L TCP/IP configuration software 402 retentive attribute 128
Profibus configuration software 406 ring errors 367
procedure command 366 ring state 367
Procedure Command Function 330 rollover on position with a time axis 512
Profibus configuration software 405 running one scan 190
547
S receive 361
receive continuous 363
saving
send 364
files 85
startup list 344, 345
hardware declarations 101
upload drive file 362
prior version PiCPro 319
IDNs, changing data 356
SERCOS setup file 352
IDNs, uploading 356
servo setup 319
initialize setup data in your ladder 354
scaling information 300
inserting rings 341
scanner symbol 400
inserting slaves 342
scanning 189
MDT 329
cold restart 190
MST 329
hot restart 190
numbering slaves 342
stopping 189
operation mode
warm restart 190
application note 350
search IDNs 372
options for IDN display 370
searching 82
phases 331
software declarations 134
printing 353
selected cells 69
receive continuous IDNs 362
selecting items 68
receive IDNs 361
semaphore flags 392
referencing axes 338
SERCOS
replacing analog system 336
advanced features 337
ring errors 367
and MMC for PC 326
ring state 367
and PiC 326
rings,inserting 341
and standalone MMC 326
saving setup file 352
AT 329
send IDNs 364
axis positioning 338
service channel 332
battery box 359
accessing 333
changing IDN data and uploading IDNs
background information 333
356
servo axis 292
copying between SRC files 350
setup 325, 339
copying data 350
setup function 353
creating setup file 339
slave status/control
cyclic data structures 348
slave status/control 369
cyclic operation 332
slaves,inserting 342
define cyclic data 346
specifying the SRS 373
define operation modes 349
SRS structure
execute procedure command 366
copy to clipboard 358
functions 326
standard Motion Functions and Variables
IDNs 329
327
display options 370
startup IDN List 344
find 372
telegrams 329
insert for send 365
troubleshooting 374
parameter data 330
upload drive information 362
PCF 330
using Functions/Blocks with TASKS 328
printing 372
548
variable length data 373 SERCOS setup 292
SERCOS standard toolbar 516 TTL input 291
service channel 332 update rate 309
accessing 333 servo standard toolbar 516
background information 333 setting user preferences 11
servo settings command 178
calculate defaults 299 size of UDFB Libraries 379
error messages 485 slave gapping 342
timing error function 426 software declarations 102
servo setup 281 attributes 128
analog input 290 copying 130
analog output offset 308 cutting 130
auto fill axes 295 editing 129
creating entering 102
file 211, 281 fast inputs 112
function 320 I/O point 105
D/A output 288 initial values 112
data categories 297 long names 103
derivative gain 308 pasting 130
editing 296 purging unused variables 136
encoder input 288 searching 134
entering specification
iterator data 301, 305, 311 NEMA SERCOS 325
iterator data for time axis 307, 310 split screen 86
entering scaling data 298 SRS structure
feed forward percent 308 copying 358
following error limit 308 standalone MMC
initializing 321 SERCOS 326
in-position band 309 starting PiCPro 22
input polarity 308 startup IDN list 344
input scaling 298 status
integral error limit 308 blown fuse 111, 478
integral gain 308 status bar 8
iterator data 297 displaying/hiding 9
open existing file 282 stepper
output polarity 308 axis module 23, 513
output scaling 298 error handling 514
overview 209, 269, 281 reference card 505
position loop data 297, 307 using functions with 513
printing 319 stopping the scan 189
proportional gain 308 STRING
resolver setup 290 read/write from STRUCT 539
saving 319 structured text constructs toolbar 523
scaling data 297 structures 116
scaling information 300 support services 2
549
T comparing to Task 384
compiling 177, 380
Task 377
creating 377
comparing to UDFB 384
data handling 380
compiling 176
edit 380
creating 388
inputs and outputs
hardware declarations 387
marking 383
interlocking data 392
number of 383
naming 389
order of 382
semaphore flags 392
library size 379
naming 378
template 385
types 384
view 381
using Functions 386
parent ladder 381
technical support 2
Uncompressing a Project 44
telegrams
update rate 309
SERCOS 329
upload drive information 362
time 115
user preferences 11
time axis 511
User Programs
rollover on position 512
backup 206
setup data categories 305
restore 206
synchronizing slave axes with 512
using a time axis 511
timeouts 200
using projects 23
title bar 9
toolbar 515 V
advanced operations 520 variable in/out attribute 129
basic online operations 520 variable length data
compiler 522 viewing 373
customizing 15 variables 103, 113, 139
displaying/hiding 16 forcing 182
docking 16 names and long names 103
drive list-standard 517 view navigator toolbar 522
functions 522 viewing
insert new network 524 enabled variables 187
ladder 521 parent ladder 381
moving 16 UDFB 381
SERCOS 516
SERCOS standard 516 W
servo standard 516 web site 2
structured text constructs 523 Window elements 9
view navigator 522 wires 143
troubleshooting work area
SERCOS 374 PiCPro 5
TTL input setup 291 working with extended memory 180
U working with split screen 86
workstation 3
UDFB 377
550
Z
zooming 67
551
552

M1301-7003 14.1 PiCPro SoftwareManual

Uploaded by

Copyright:

Available Formats

M1301-7003 14.1 PiCPro SoftwareManual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M1301-7003 14.1 PiCPro SoftwareManual

Uploaded by

Copyright:

Available Formats

PiCPro for Windows ™ ®

G&L Motion Control

Progress is an ongoing commitment at G&L Motion Control. We continually strive to offer

IBM is a registered trademark of International Business Machines Corporation.

Introduction to PiCPro for Windows .................................................................. 1

CHAPTER 2-Working with Projects ....................................................... 23

CHAPTER 3-Working with Ladders ........................................................ 51

A PiCPro Session ................................................................................................ 51

CHAPTER 4-Setting Up the MMC Smart Drive ...................................... 209

Overview: MMC Smart Drive Setup .................................................................. 209

CHAPTER 5-Custom Motors ................................................................... 269

Overview: Custom Motors .................................................................................. 269

CHAPTER 6-Servo Setup and Tuning .................................................... 281

Servo Setup Overview ........................................................................................ 281

CHAPTER 7-PiCPro and SERCOS ......................................................... 325

SERCOS Setup Background Information .......................................................... 325

CHAPTER 8-Working With Tasks and UDFBs ....................................... 377

UDFBs ................................................................................................................ 377

CHAPTER 9- DeviceNet - Ethernet - TCP/IP .......................................... 397

G&L DeviceNet Configuration Software ........................................................... 397

CHAPTER 10- G&L Profibus Configuration Software .......................... 405

Overview of setting up a Profibus Network ................................................. 405

APPENDIX A - Quick Reference to In/Out Function Data ..................... 409

Function Input/Output Data Type Reference ...................................................... 409

APPENDIX B - Errors ............................................................................... 415

Function Error Codes .......................................................................................... 415

APPENDIX C - PiCPro Reference Card - Errors/Variables ................... 501

Reference Card ................................................................................................... 501

Stepper Reference Card ...................................................................................... 505

APPENDIX E - Diagnostic LED Error Codes .......................................... 507

Error Codes ......................................................................................................... 507

APPENDIX F - IBM ASCII Chart ............................................................... 509

ASCII Chart ....................................................................................................... 509

APPENDIX G - Time Axes ........................................................................ 511

Using a Time Axis .............................................................................................. 511

APPENDIX H - Stepper Axis Module Notes ............................................ 513

Introduction - Stepper Axis Module ................................................................... 513

APPENDIX I - Toolbar Buttons ................................................................ 515

Servo - Standard Toolbar and SERCOS - Standard Toolbar ............................. 516

APPENDIX J - Module Filenames ............................................................ 525

APPENDIX K - Service Pack Installation ................................................ 527

Service Pack Installation ..................................................................................... 527

Virtual Axis ......................................................................................................... 533

APPENDIX N- Firmware ........................................................................... 535

Firmware ............................................................................................................. 535

APPENDIX O - Things to Consider When Converting an Application from One

Application Note 1 ................................................................................... 539

Reading and Writing STRINGs from a Structure ............................................... 539

Getting Started with PiCPro for Windows 1

PiCPro for Windows Professional Edition is the full-featured member of the

Sheffield Automation is committed to providing customers with high-quality tech-

2 Getting Started with PiCPro for Windows

The recommended requirements for a workstation are:

Memory Consult operating system for additional memory needs.

Video 800 x 600 or higher resolution is required, 16-bit or greater color.

Disk drives Typically, 100 MB of hard disk space is required.

Getting Started with PiCPro for Windows 3

PiCPro for Windows is available on CD.

4 Getting Started with PiCPro for Windows