distributed power system sa3100 drive configuration and programming · 2015-10-03 · 1-2 sa3100...

Distributed Power SystemSA3100 Drive Configurationand Programming

Instruction Manual
S-3056-1

Throughout this manual, the following notes are used to alert you to safety considerations:

Important: Identifies information that is critical for successful application and understanding of the product.

!ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.

!ATTENTION:Only qualified electrical personnel familiar with the construction and operation of this equipment and the hazards involved should install, adjust, operate, or service this equipment. Read and understand this manual and other applicable manuals in their entirety before proceeding. Failure to observe this precaution could result in severe bodily inury or loss of life.

ATTENTION:DC bus capacitors retain hazardous voltages after input power has been disconnected. After disconnecting input power, wait five (5) minutes for the DC bus capacitors to discharge and then check the voltage with a voltmeter to ensure the DC bus capacitors are discharged before touching any internal components. Failure to observe this precaution could result in severe bodily inury or loss of life.

ATTENTION:The user must provide an external, hardwired emergency stop circuit outside of the drive circuitry. This circuit must disable the system in case of improper operation. Uncontrolled machine operation may result if this procedure is not followed. Failure to observe this precaution could result in bodily injury.

ATTENTION:Only qualified Rockwell personnel or other trained personnel who understand the potential hazards involved may make modifications to the variable configuration and application tasks. Any modifications may result in uncontrolled machine operation. Failure to observe this precaution could result in damage to equipment and bodily injury.

ATTENTION:Registers and bits in the UDC module that are described as “read only” or for “system use only” must not be written to by the user. Writing to these registers and bits may result in improper system operation. Failure to observe this precaution could result in bodily injury.

ATTENTION: Electronic motor overload protection must be provided for each motor in an AutoMax™ drive application to protect the motor against excessive heat caused by high currents. This protection can be provided by either the THERMAL OVERLOAD software block or an external hardware device. Applications in which a single power module is controlling multiple motors cannot use the THERMAL OVERLOAD software block and must use an external hardware device or devices to provide this protection. Failure to observe this precaution could result in damage to, or destruction of, the equipment.

The information in this user’s manual is subject to change without notice.

Ethernet™ is a trademark of Xerox Corporation.Windows™ is a trademark of Microsoft Corporation.AutoMax™ is a trademark of Rockwell Automation.

©1998 Rockwell International Corporation

CONTENTS

Chapter 1 Introduction

Chapter 2 Configuring the UDC Module, Regulator Type, and Parameters2.1 Adding a Universal Drive Controller (UDC) Module ........................................ 2-12.2 Entering the Drive Parameters ........................................................................ 2-32.3 Configuring the Vector with Constant Power Regulator .................................. 2-5

2.3.1 Power Module Data Screen (Vector with Constant Power)................... 2-52.3.2 Motor Data Screen (Vector with Constant Power) ................................ 2-6

2.3.2.1 Constant Magnetization or Manual Compensation ................. 2-72.3.2.2 Constant Power Motor Data Screen ....................................... 2-9

2.3.3 Feedback Data Screen (Vector with Constant Power)........................ 2-122.3.4 PMI Meter Port Selection Screen (Vector with Constant Power) ........ 2-14

2.4 Configuring the Volts per Hertz (V/Hz) Regulator.......................................... 2-162.4.1 Power Module Data Screen (Volts per Hertz) ..................................... 2-162.4.2 Configuration Data - Setup (Volts per Hertz)....................................... 2-182.4.3 V/Hz Characteristic Screen (Volts per Hertz) ...................................... 2-202.4.4 Feedback and Control Data Screen (Volts per Hertz)......................... 2-212.4.5 PMI Meter Port Selection Screen (Volts per Hertz)............................. 2-22

2.5 Configuring Flex I/O....................................................................................... 2-242.6 Generating Drive Parameter Files and Printing Drive Parameters ................ 2-25

Chapter 3 Configuring the UDC Module’s Registers3.1 Register and Bit Reference ConventionsUsed in this Manual ......................... 3-33.2 Flex I/O Port Registers (Registers 0-23) ......................................................... 3-6

3.2.1 Digital Data Formats.............................................................................. 3-73.2.2 Analog Data Formats ............................................................................ 3-83.2.3 Flex I/O Status and Error Codes ........................................................... 3-9

3.3 UDC/PMI Communication Status Registers (Registers 80-89/1080-1089) ... 3-113.4 Command Registers (Registers 100-199/1100-1199)................................... 3-193.5 Feedback Registers (Registers 200-299/1200-1299).................................... 3-273.6 Application Registers (Registers 300-599, Every Scan) (Registers 1300-1599,

Every Nth Scan) ............................................................................................ 3-503.7 UDC Module Test I/O Registers (Registers 1000-1017) ............................... 3-53

3.7.1 UDC Module Test Switch Inputs Register (Register 1000) ................. 3-533.7.2 UDC Module Meter Port Setup Registers (Registers 1000-1017)....... 3-55

3.7.2.1 Resolution of Meter Port Data............................................... 3-563.8 Interrupt Status and Control Registers (Registers 2000-2047) ..................... 3-61

Chapter 4 Application Programming for DPS Drive Control4.1 AutoMax Tasks................................................................................................ 4-14.2 UDC Tasks ...................................................................................................... 4-1

4.2.1 Typical Structure of a UDC Task........................................................... 4-34.2.2 Local Tunable Variables........................................................................ 4-6

4.2.2.1 Calculating Local Tunable Values........................................... 4-74.2.3 UDC/PMI Task Communication ............................................................ 4-7

4.3 AutoMax Processor Task and UDC Task Coordination .................................. 4-9

Table of Contents I

Chapter 5 On-Line Operation5.1 Loading the UDC Module’s Operating System ................................................5-15.2 Loading the Drive Parameters and UDC Tasks ...............................................5-15.3 Running, Stopping, and Deleting UDC Application Tasks ...............................5-25.4 UDC Information Log and Error Log ................................................................5-3

Appendix A SA3100 Vector Regulator Register Reference ........................................................ A-1

Appendix B SA3100 Volts / Hertz Regulator Register Reference ............................................... B-1

Appendix C SA3100 Local Tunable Variables............................................................................. C-1

Appendix D Vector with Constant Power Regulator .................................................................... D-1

Appendix E Volts per Hertz (V/Hz) Regulator.............................................................................. E-1

Appendix F Status of Data in the AutoMax Rack After a STOP_ALL Command or STOP_ALL Fault ...................................................................................................... F-1

Appendix G Torque Overload Ratio Parameter Precautions .......................................................G-1

Appendix H Default Carrier Frequency and Carrier Frequency Limit for Drive Horsepower Ranges ................................................................................................ H-1

Appendix I Vector with Constant Power Parameter Entry Example.............................................I-1

Appendix J Commissioning Procedure for Non-Constant Power Algorithim Operation...............J-1

II SA3100 Drive Configuration and Programming

List of Figures

Figure 2.1 – Adding a UDC Module.......................................................................... 2-2Figure 2.2 – Adding Flex I/O..................................................................................... 2-3Figure 2.3 – Drive Parameter Entry Screen (Vector with Constant Power).............. 2-4Figure 2.4 – Power Module Data Parameter Entry Screen (Vector with

Constant Power)................................................................................... 2-5Figure 2.5 – Motor Data Parameter Entry Screen used for Constant Magnetization or

Manual Compensation ......................................................................... 2-6Figure 2.6 – Motor Data Parameter Entry Screen used for Constant Power............ 2-9Figure 2.7 – Feedback Data Parameter Entry Screen (Vector with Constant

Power) ................................................................................................ 2-12Figure 2.8 – PMI Meter Port Selection Entry Screen (Vector with Constant

Power) ................................................................................................ 2-14Figure 2.9 – Power Module Data Parameter Entry Screen (Volts per Hertz) ......... 2-16Figure 2.10 – Configuration Data Setup Parameter Entry Screen (Volts per

Hertz).................................................................................................. 2-18Figure 2.11 – V/Hz Characteristic Parameter Entry Screen (Volts per Hertz) ........ 2-20Figure 2.12 – Speed Feedback and Control Parameter Entry Screen (Volts per

Hertz).................................................................................................. 2-21Figure 2.13 – PMI Meter Port Selection Entry Screen (Volts per Hertz)................. 2-22Figure 2.14 – Flex I/O Parameter Entry Screen ..................................................... 2-24Figure 3.1 – UDC Task Scan.................................................................................. 3-50Figure 3.2 – Nth Scan Interrupts............................................................................. 3-52Figure 4.1 – UDC Task Scan.................................................................................... 4-2Figure 4.2 – Recommended Run Permissive Logic ................................................. 4-9Figure 4.3 – Data/Time Flow for UDC Module and PMI ......................................... 4-10Figure C.1 – Capacitance Used for Resolver Balancing ..........................................C-9Figure D.1 – Vector With Constant Power Regulator Block Diagram.......................D-2Figure E.1 – Volts/Hertz Control Regulator Block Diagram......................................E-3Figure E.2 – Constant Torque Volts/Hertz Curve .....................................................E-4Figure E.3 – Variable Torque 7-Point Volts/Hertz Curve ..........................................E-4

Table of Contents III

IV SA3100 Drive Configuration and Programming

List of Tables

Table 1.1 – SA3100 Documentation (Binder S-3053) .............................................. 1-2Table 1.2 – SA3100 Power Structure Service Manual Cross Reference ................. 1-2Table 2.1 – Restricted Drive Type Combinations ..................................................... 2-2Table 2.2 – Maximum Slip Per Number of Poles...................................................... 2-8Table 2.3 – Standard Resolvers ............................................................................. 2-13Table 2.4 – PMI Meter Port Parameters (Vector with Constant Power) ................. 2-15Table 2.5 – PMI Meter Port Parameters (Volts/Hertz) ............................................ 2-23Table 3.1 – UDC Module Configuration Views and Registers .................................. 3-4Table 3.2 – UDC Module Dual Port Memory Register Organization. ....................... 3-5Table 3.3 – Flex I/O Reserved Registers.................................................................. 3-6Table 3.4 – Supported Flex I/O Modules .................................................................. 3-7Table 3.5 – Analog Data ........................................................................................... 3-8Table 3.6 – Register 10/22 - Flex I/O Module 0 and Module 1 Faults ...................... 3-9Table 3.7 – Register 11/23 - Flex I/O Module 2 Faults ........................................... 3-10Table 3.8 – UDC Module Meter Port Setup Registers............................................ 3-55Table D.1 – Dual Wound Motor Handshake Program ..............................................D-3

Table of Contents V

VI SA3100 Drive Configuration and Programming

CHAPTER 1Introduction

SA3100 drives operate under the control of the AutoMax™ Distributed Power System (DPS). DPS drives are controlled through coordination among:

• Tasks written by the programmer for the AutoMax Processor.

• Tasks written by the programmer for the Universal Drive Controller (UDC) module.

• The control algorithm and a number of software routines executed by the Power Module Interface (PMI) regulator.

The data and commands required by the PMI operating system to carry out its functions are provided by the programmer through the AutoMax rack configuration and the UDC task. The programmer provides this information by:

• Entering the drive parameters.

• Configuring the registers in the UDC module.

• Defining the values of the pre-defined local tunables.

• Writing the UDC task.

This manual describes the configuration and programming necessary to control SA3100 drives. Refer to the publications listed in table 1.1 for detailed descriptions of the components of an SA3100 drive system.

The AutoMax Programming Executive Version 3.5A (M/N 57C657) or later is required to support the SA3100 Drive. Drive regulators are sold separately. The AutoMax Programming Executive instruction manual describes the AutoMax DPS Software Executive in detail.

This instruction manual assumes that you are familiar with the AutoMax Programming Executive software and makes reference to it throughout. This manual does not describe specific applications of the standard hardware and software.

Introduction 1-1

Related Publications

The user must become familiar with the other instruction manuals that describe the SA3100 drive system. The documentation that describes the SA3100 drive is contained in binder S-3053 and is listed in table 1.1.

Power structure replacement parts and service procedures are contained in the instruction manuals listed in table 1.2.

Table 1.1 – SA3100 Documentation (Binder S-3053)

Document Document Part Number

Drive System Overview S-3005

Universal Drive Controller Module S-3007

Fiber Optic Cabling S-3009

SA3100 Drive Configuration & Programming S-3056

SA3100 PMI Regulator S-3057

SA3100 Power Modules S-3058

SA3100 Diagnostics, Troubleshooting, & Start-Up Guidelines

S-3059

Information Guide S-3054

Table 1.2 – SA3100 Power Structure Service Manual Cross Reference

AC Input Voltage

DC BusInput Voltage Nominal HP Frame Size

Use Service Manual 1336

Force-

200 VAC -

240 VAC[A]

310 VDC[Q]

001

B 6.11

003

007

010

015

020

C 6.12025

030

040

D 6.13050

060

075

E 6.14100

125

1-2 SA3100 Drive Configuration and Programming

380 VAC -

480 VAC[B]

513 VDC-

620 VDC[R]

001

B 6.11

003

007

010

015

020

025

030

040C 6.12

050

060

D 6.13075

100

125

150

E 6.14200

250

300

F 6.14350

400

450

G 6.15500

600

800 H 6.15


AC Input Voltage



Force-

Introduction 1-3

Additional information about using the SA3100 drive is found in the wiring diagrams, prints, and other documentation shipped with each drive system. Always consult the prints shipped with your drive system for specific information about installing, operating, and maintaining your drive.

500 VAC -

600 VAC[C]

675 VDC-

800 VDC[W]

001

B 6.11

003

007

010

015

020

025

C 6.12030

040

050

060

075

D 6.13100

125

150

E 6.14200

250

300

350F 6.16

400

450

G 6.15500

600

650

800 H 6.15


AC Input Voltage



Force-


CHAPTER 2Configuring the UDC Module,

Regulator Type, and Parameters

The Rack Configurator application in the AutoMax Programming Executive is used to configure the modules in a rack. Using the Rack Configurator, you create a graphical representation of the actual modules in the rack. See the AutoMax Programming Executive instruction manual for more information on configuring racks.

You can access the Rack Configurator by selecting the Configure Rack option from the Rack menu of the System Configurator. An empty AutoMax rack will be displayed initially.

2.1 Adding a Universal Drive Controller (UDC) Module

The UDC module may be placed in any slot in an AutoMax rack that contains at least one AutoMax processor module (M/N 57C430A, 57C431, or 57C435). Note that the UDC module cannot be used in a remote I/O rack. The rack does not require a Common Memory module (M/N 57C413 or 57C423) unless more than one AutoMax Processor is being used. A rack may contain up to ten UDC modules.

Some AutoMax modules,e.g., the Common Memory module and the Ethernet© Interface module, may have an effect on the slot allocation in the rack that limits where other modules may be inserted. See the appropriate instruction manual for additional information. A UDC module may also be placed in a rack containing a set of the AutoMax drive controller modules (B/M57401, 57405, 57406, and 57408).

Use the following procedure to add a UDC module to a rack. Refer to figure 2.1.

Step 1. Select an empty slot in the rack.

Step 2. Select Add from the Configure menu. A dialog box listing the available modules will be displayed on the screen.

Step 3. Select the UDC module.

!ATTENTION:Only qualified personnel familiar with the construction and operation of this equipment and the hazards involved should install, adjust, operate, or service this equipment. Read and understand this manual and other applicable manuals in their entirety before proceeding. Failure to observe this precaution could result in severe bodily injury or loss of life.

ATTENTION:Only qualified Rockwell personnel or other trained personnel who understand the potential hazards involved may make modifications to the rack configuration. Any modifications may result in uncontrolled machine operation. Failure to observe this precaution may result in damage to equipment and bodily injury.

Configuring the UDC Module, Regulator Type, and Parameters 2-1

Step 4. Select a product type and a regulator (control) type for both drive A and drive B. See section 2.1.1 for regulator selection rules. The remainder of this chapter assumes that you have selected an SA3100 Drive Product with a Vector with Constant Power Regulator or Volts/Hertz Regulator.

Step 5. Select OK to add the UDC module to the rack and return to the Rack Configuration screen.

Rules for Configuring/Selecting Drives for the UDC Module

The following drive configuration rules apply to all DPS systems:

1. The A and B drives do not both have to be used. You can configure only one.

2. Your A/B drive type combination is restricted only if you select an SD3000 (12-Pulse) drive, an SF3000 drive, or an SA3000 Parallel Inverters drive for either drive A or drive B. For these products, you are restricted to the drive type combinations shown in table 2.1. All other drive type combinations are allowed.

Figure 2.1 – Adding a UDC Module

Table 2.1 – Restricted Drive Type Combinations

If you choose for Drive A . . . Then your choices for Drive B are . . .

SD3000 12-Pulse Main SD3000 12-Pulse Auxiliary

SF3000No PMI AttachedSD3000 (6-Pulse)SF3000

SA3000 Parallel Inverters SA3000 Parallel Inverters Auxiliary


2.2 Entering the Drive Parameters

Drive parameters are application-specific data that describe your installation’s Power Modules, feedback devices, and motors. This information is loaded to the UDC module, which in turn automatically downloads it to the PMI when the two are first connected over the fiber-optic link. This information is also stored off-line with the Programming Executive. Note that the drive parameters will be retained by the UDC module during a Stop All fault or command to the rack.

Once a UDC module has been added to the rack, use the Zoom In command to begin entering the drive parameters. See the AutoMax Programming Executive instruction manual for more information on Zooming in and out.

Use the following procedure to enter the drive parameters. Section 2.3 describes how to load the drive parameter files when you are finished. Note that if you enter drive parameter data that is unexpected or out of range, a “warning” or “error” message will appear on the screen. A warning message indicates that the data you have just entered will be accepted by the Programming Executive, and you will be able to generate drive parameter files; however, you may experience degradation of drive performance. An error message indicates that the data you have just entered is unacceptable, and you will not be able to generate drive parameter files.

Step 1. Zoom into the UDC module. The Power Module Interface (PMI) screen will be displayed. You can also access this screen directly by double-clicking the UDC module.

This screen shows either one or two PMI diagrams, depending upon the information you previously entered. One PMI will be shown for drive A and one for drive B, if used. Entered commands will only affect the selected drive.

Each PMI diagram will show a Flex I/O port (Port 0) and the analog or digital Flex I/O modules that are connected to the PMI. Initially, no Flex I/O is connected.

Step 2. The SA3100 supports one Flex I/O port, Port 0, per PMI. If Flex I/O is to be connected to the PMI, click on Port 0. Select Add under the Configure menu to add the Flex I/O rail to the PMI port. See figure 2.2.

Figure 2.2 – Adding Flex I/O


Step 3. Use the Configure Parameters option to access the Parameter Entry screens. For the Vector with Constant Power regulator, you must access the Power Module Data, Motor Data, Feedback Data, and Meter Port Selection screens (see figure 2.3). For the Volts per Hertz regulator you must access the Power Module Data, Configuration Data - Setup, Volts/Hz Characteristic, Feedback Data, and Meter Port Selection screens. An additional screen is used for configuring Flex I/O. Each of these screens is described in detail in the following sections.

Note that the AutoMax slot number of the UDC module is shown at the top of the screens. The screens prompt for specific information depending upon the item that is being configured.

Step 4. When you have made entries for the drive parameters on all of the parameter entry screens, you should select the “Verify” option displayed at the bottom of the screen. If any of the values you entered are invalid or out of range, the parameter that is invalid will be highlighted so that you can change the value. When you have finished entering drive parameters, select “Save” to save the values to the database.

.

Figure 2.3 – Drive Parameter Entry Screen (Vector with Constant Power)

(This area contains specific parameter data about the selected device.)


2.3 Configuring the Vector with Constant Power Regulator

The following sections (2.3.1 to 2.3.4) describe the parameter entry screens for the SA3100 Vector with Constant Power regulator. These screens are accessed by selecting SA3100 as the product type and Vector with Constant Power as the regulator type when configuring the UDC module parameters. If your drive uses the Volts per Hertz regulator refer to section 2.4.

2.3.1 Power Module Data Screen (Vector with Constant Power)

The Power Module Data screen allows you to enter specific information about your power system configuration and the type of Power Module being used. See figure 2.4.

Power System Configuration

• DC Input Voltage or AC input Voltage

Select the type of input line voltage (AC input or DC input) and then enter the input voltage value.

Select DC Input Voltage if this is the DC bus voltage. Select AC Input Voltage if this is the AC RMS voltage that is being converted to DC bus voltage. This voltage determines which group of Power Modules may be selected from the Part Number list. The default selection is DC Input Voltage.

• MCR Connected To Output Contactor

If you have a motor control relay (MCR) on the output of the drive (output contactor), select this option. If there is only a manual disconnect switch and no contactor under automatic control, do not select the output contactor option. The default selection is no contactor.

Figure 2.4 – Power Module Data Parameter Entry Screen (Vector with Constant Power)


Power Module

• Part Number

Select a part number from the list of supported Power modules (x nnn, where x is the voltage code and nnn is the horsepower rating). The current ratings in the list are the rated RMS currents at the drive’s default carrier frequency as listed in Appendix H, with no overload at 40° ambient temperature. The power module is capable of 150% of the maximum amps value for 1 minute. There is no default selection. You must choose a part number from the list.

The motor must be able to operate off the Power Module selected at the voltage level entered as the Input Voltage parameter. A warning will be issued when if an incompatibility is found.

• Carrier Frequency

The carrier frequency selected will determine the Power Module’s switching frequency. You can select from a list of preset carrier frequencies: 1.5 kHz, 2 kHz, 4 kHz, 6 kHz, 8 kHz, 10 kHz or 12 kHz; or you can enter a value between 1.5 kHz and 12 kHz in increments of 100 Hz. The hardware in some cases will have slightly coarser resolution at the higher frequencies. See Appendix H for the default carrier frequency and carrier frequency limit for the Power Module you have selected.

All Power Modules are rated at their default switching frequency, but they can be operated above this limit by de-rating the unit’s output. Refer to the SA3100 Power Modules instruction manual (S-3058) for more information.

2.3.2 Motor Data Screen (Vector with Constant Power)

The Motor Data parameter screen allows you to enter specific information about the motor you are using. (If you are using a high slip motor, see Appendix B for additional information.) See figure 2.5.

Figure 2.5 – Motor Data Parameter Entry Screen used for Constant Magnetization or Manual Compensation


• Constant Magnetization, Manual Compensation, or Constant Power

These selections define the method the system will use to determine the value used for magnetizing current in the control algorithm.

The default selection is Manual Compensation which allows operation in the constant power region up to 2:1. In this case, the value in register 104/1104 (FLX_REF%) is used to scale local tunable STATOR_IZ_E1% where 4095 equals full magnetizing current.

Select Constant Magnetization to use the value stored in local tunable STATOR_IZ_E1% for the magnetizing current value. The PMI Processor calculates this value in response to the PMI_TUN@ command.

Select Constant Power to allow operation in the constant power region up to 4:1. In this case, the PMI Processor calculates magnetizing current using motor voltage feedback (flux loop).

2.3.2.1 Constant Magnetization or Manual Compensation

For these two selections, you will need to supply the following information:

• Rated Power (Range: 1 HP to 800 HP or 1 KW to 600 KW)

Enter the power rating of the motor and select HP (default) or KW. There is no default value.

NOTE: 1 HP = 0.746 KW.

• Rated Motor Voltage (Volts RMS) (Range: 100V to 575V)

Enter the rated RMS motor voltage. There is no default value. A warning message will be displayed if the value entered is less than 60% or greater than 100% of the AC Input Voltage parameter. (Note that if the input voltage was entered as DC, it is converted to AC by the system for this test.)

• Rated Motor Current (Amps RMS) (Range: 1.0A to 3000.0A)

Enter the rated RMS motor current exactly as it appears on the motor nameplate. The resolution is 0.1 amp. There is no default value. The value can range from 25% to 100% of the Power Module’s rating at the selected carrier frequency.

• Torque Overload Ratio (%) (Range: 25 to 400)

The Torque Overload Ratio determines the maximum RMS current that can be supplied to the motor by the Power Module. The ratio affects only the Iq (torque) component of RMS current to the motor. Enter the torque overload ratio in percent of rated motor torque, which can be calculated from the rated speed and HP. For example, 150% of rated motor torque is entered as 150. The default value is 100. The resolution is 1%. See Appendix E for how to calculate the effect of the ratio on maximum RMS current.

A warning will be generated if the following condition is not met:

Rated Motor Current ∗ Torque Overload Ratio100

<= Power Module Rated Amps @ Selected Carrier Frequency


If a warning appears, it is likely that the maximum RMS current that can be supplied to the motor at the torque overload ratio level selected is too high for the Power Module selected. See Appendix E for more information on determining the maximum RMS current that will result from the ratio entered.

• Frequency at Rated Voltage (Hz) (Range: 1 to 600)

This value is used to determine the frequency at which the motor enters the constant power range. Enter the value in Hz. Resolution is 0.1 Hz. There is no default value.

• Rated Full Load Speed (RPM) (Range: 10 to 10,000)

This value is used to determine the rated slip of the motor at the rated motor frequency. This value is found on the motor’s nameplate. Enter the value in RPM. The resolution is 1 RPM. There is no default value.

• Motor Poles (2, 4, 6, 8, 10, 12, 14, or 16)

This value is used to determine the relationship between drive output frequency and motor shaft speed. Because this number is not readily available, the number of motor poles will be calculated automatically based on the other parameters you have entered and will be displayed on the screen. You must then select this calculated value from a list of the preset values. There is no default value.

The following formula will be used to calculate the number of motor poles:

120 ∗ Frequency at Rated Voltage / Rated Full Load Speed

The resulting number will be rounded down to the nearest whole even number. Note that this formula may not result in the correct number of motor poles if you are using a high slip motor, such as a NEMA design D motor. See table 2.2 for the maximum slip per number of motor poles that will result in a correct calculation.

For example, on an 8-pole motor, if slip is greater than 19%, the calculated value will be incorrect. You must then enter the correct value.

Table 2.2 – Maximum Slip Per Number of Poles

Number of Poles Maximum Slip

2 49%

4 33%

6 24%

8 19%

10 16%

12 14%


2.3.2.2 Constant Power Motor Data Screen

When Constant Power is selected, a new screen is displayed, and the following information must be entered. See figure 2.6.

• Rated Power (Range: 1 HP to 800 HP or 1 KW to 600 KW)

Enter the power rating of the motor and select HP (default) or KW. There is no default value.

NOTE: 1 HP = 0.746 KW.

• Rated Motor Voltage (Volts RMS) (Range: 100V to 575V)

Enter the rated RMS motor voltage. There is no default value. A warning message will be displayed if the value entered is less than 60% or greater than 100% of the AC Input Voltage parameter. (Note that if the input voltage was entered as DC, it is converted to AC by the system for this test.)

• Maximum Motor Voltage (Volts RMS) (Range: 100V to 575V)

Enter the maximum RMS motor voltage. There is no default value. In motor designs where motor voltage reaches its maximum value at rated speed, this value will be equal to the value entered in the Rated Motor Voltage parameter.

In motor designs where motor voltage continues to rise after reaching rated speed, this value will be greater than the value entered in the Rated Motor Voltage parameter. This information is found on the motor design data sheet.

• Total Current Rating Points (Range: 1 to 5)

Enter the rated RMS motor current exactly as it appears on the motor nameplate. The resolution is 0.1 amp. There is no default value. The value can range from 25% to 100% of the Power Module’s rating at the selected carrier frequency.

Figure 2.6 – Motor Data Parameter Entry Screen used for Constant Power


• Speed (RPM) (Range: 10 to 10,000)

Enter all speed values in RPM; the resolution is 1 RPM. There are no default values.

Base: Enter the base (rated) speed of the motor. The base speed value represents the speed where the motor enters the constant power region. This value is used to determine the rated slip of the motor at the rated motor frequency. This value is found on the motor’s nameplate.

S1: Enter the speed at which maximum voltage is reached. If the rated voltage is not equal to the maximum voltage of the motor, the PMI Processor will automatically calculate the value of S1 when you select “Verify.” If rated voltage and maximum voltage are the same, you must enter this value manually. This information is located on the motor design data sheet.

S2-S4: Enter additional speed values as required by the motor design. The additional speed values represent taper points of the constant power region. Note that the additional speed values cannot be greater than four times the base speed.

• Current (Amps)

Enter all current values in amps; the resolution is 0.1 amp. This value can range from 25% to 100% of the Power Module’s rating at the selected carrier frequency.

Base: Enter the base (rated) RMS motor current exactly as it appears on the motor nameplate. There is no default value.

Enter additional current values at each speed (e.g., C1 corresponds to the motor current level at speed S1). This information is located on the motor design data sheet.

• Torque Overload Ratio (%) (Range: 25 to 400)

The Torque Overload Ratio determines the maximum RMS current that can be supplied to the motor by the Power Module. The ratio affects only the Iq (torque) component of RMS current to the motor. Enter the torque overload ratio in percent of rated motor torque, which can be calculated from the rated speed and HP. For example, 150% of rated motor torque is entered as 150. The default value is 100. The resolution is 1%. See Appendix E for how to calculate the effect of the ratio on maximum RMS current.

A warning will be generated if the following condition is not met:

Note that the Power Module Rated Amps at Carrier Frequency value is based on either the carrier frequency selected during parameter entry or the carrier frequency calculated by the system, whichever is greater. The carrier frequency is calculated by the system using the following equation:

Calculated Carrier Frequency = 20 ∗ Freq. at Rated Voltage ∗ Max. SpeedBase Speed

Rated Motor Current ∗ Torque Overload Ratio100

<= Power Module Rated Amps @ Selected Carrier Frequency


If a warning appears, it is likely that the maximum RMS current that can be supplied to the motor at the torque overload ratio level selected is too high for the Power Module selected. See Appendix E for more information on determining the maximum RMS current that will result from the ratio entered.

Base: Enter the base (rated) torque overload ratio.

O1-O4: Enter the additional overload ratios at each speed, S1 to S4. This information is located on the motor design data sheet.

• Frequency at Rated Voltage (Hz) (Range: 1 to 400)

This value is used to determine the frequency at which the motor enters the constant power range. Enter the value in Hz * 10. The resolution is 0.1 Hz. There is no default value.

• Motor Poles (2, 4, 6, 8, 10, 12, 14, or 16)

This value is used to determine the relationship between drive output frequency and motor shaft speed. Because this number is not readily available, the number of motor poles will be calculated automatically based on the other parameters you have entered and will be displayed on the screen. You must then select this calculated value from a list of the preset values. There is no default value.

The following formula will be used to calculate the number of motor poles:

120 ∗ Frequency at Rated Voltage ÷ Rated Full Load Speed

The resulting number will be rounded down to the nearest whole even number. Note that this formula may not result in the correct number of motor poles if you are using a high slip motor, such as a NEMA design D motor. See table 2.2 for the maximum slip per number of motor poles that will result in a correct calculation.


2.3.3 Feedback Data Screen (Vector with Constant Power)

The Feedback Data Parameter Entry Screen allows you to enter specific information about the resolver connected to the Resolver and Drive I/O module on the PMI. See figure 2.7.

• Over Speed Limit (RPM) (Range: 10 to 10,000)

This value is used to determine the maximum safe output frequency of the drive. There is no default value. Over Speed Limit should generally be equal to or less than the motor maximum safe speed or the driven equipment maximum safe speed, whichever is lower. If a value less than Rated Full Load Speed of the motor is entered, a warning will be generated.

• Speed Feedback Type

You must select Resolver. The No Speed Feedback option is not allowed for vector regulators.

Resolver Data

• Resolver Type (x1, x2, x5)

Select the resolver type from the three choices: x1, x2, or x5. The “None” option is not allowed for vector regulators. The resolver selected must be able to operate at the Over Speed Limit of the motor.

• Resolution

This value is used to configure the PMI’s resolver-to-digital converter for either 12-bit or 14-bit conversion of the resolver data. The 12- or 14-bit modes are designed to be used with the following resolvers:

Figure 2.7 – Feedback Data Parameter Entry Screen (Vector with Constant Power)


For the most accurate velocity control, always select the resolver (x1, x2, or x5) with the maximum speed closest to, and greater than, the maximum speed of your application. See the SA3100 PMI instruction manual for more information regarding the Resolver & Drive I/O module and the supported resolvers.

Control Selections

• Output Rotation ( UVW, UWV )

This parameter allows you to reverse the direction of rotation of the output without re-wiring the motor leads. Select UVW (default) or UWV. Note that the resolver cosine connections must also be interchanged. See the SA3100 Diagnostics, Troubleshooting, and Start-Up Guidelines instruction manual (S-3059) for more information on motor orientation.

Table 2.3 – Standard Resolvers

ResolverBase Part No.

x1 x2 x5

Suffix

613469 -1R -1S

613469 -2R -2S

800123 -R -S -T

800123 -1R -1S -1T

800123 -2R -2S -2T


2.3.4 PMI Meter Port Selection Screen (Vector with Constant Power)

The Meter Port Selection Parameter Entry screen allows you to enter specific information about what variables are to be output on the four PMI D/A channels (the four meter ports on the PMI motherboard. See figure 2.8.

Table 2.4 lists the values that can be displayed on the PMI meter ports using the Vector with Constant Power regulator. You must enter a Minimum Value and a Maximum Value for each selection except when you select Port Not Used. The Minimum Value is the value at which to output -10V. The Maximum Value is the value at which to output +10V. The system software then places the units per volt on the screen based on the Minimum/Maximum Values.

The Minimum Value must not be less than -32768. The Maximum Value must not be greater than 32767. The Minimum Value must be less than the Maximum Value. Note that the PMI meter ports have 8-bit resolution and are updated on the average of every 1.0 milliseconds.

See the PMI Regulator instruction manual (S-3057) for more information about the PMI meter ports. See section 3.7.2.1 of this instruction manual for information about resolution of data.

Figure 2.8 – PMI Meter Port Selection Entry Screen (Vector with Constant Power)


PMI meter ports can also be set up on-line using the “Setup UDC” selection from the Monitor menu as described in the AutoMax Programming Executive instruction manual. If the meter ports are set up during parameter entry, the information is loaded onto the UDC module in the AutoMax rack along with all other parameter data. The meter port setup can then be changed on-line under “Setup UDC,” but this method would not actually write over the PMI meter port setup that was loaded to the rack. Instead, the new setup would be valid only until there was a Stop All or a power cycle, in which case the original setup would be used to determine what data to send out of the meter ports.

Table 2.4 – PMI Meter Port Parameters (Vector with Constant Power)

• Port Not Used

• Torque Reference (Counts)

• Torque Feedback (Counts)

• Flux Reference (Counts)

• Flux Feedback (Counts)

• DC Bus Voltage (Volts)

• DC Bus Current (Amps ∗ 10)

• Ground Fault Current (Amps ∗ 10)

• Motor Voltage Feedback (Volts)

• Motor Current Feedback ( Amps ∗ 10 )

• Id Current Reference (Counts)

• Id Current Feedback (Counts)

• Vd Reference (Counts)

• Iq Current Reference (Counts)

• Iq Current Feedback (Counts)

• Vq Reference (Counts)

• Slip Frequency (Hz ∗ 100)

• Output Frequency (Hz ∗ 10)

• User Analog Input (Counts)

• Speed Feedback (RPM)

• Application Data (Units)

• Flex Module 0 (Counts)


• Flex Module 2 Channel 0 (Counts)





• Power Module Heat Sink Temp (°C)


2.4 Configuring the Volts per Hertz (V/Hz) Regulator

The following sections (2.4.1 to 2.4.5) describe the parameter entry screens for the SA3100 Volts per Hertz regulator. These screens are accessed by selecting SA3100 as the product type and Volts per Hertz as the regulator type when configuring the UDC module. If your drive uses the Vector with Constant Power regulator refer to section 2.3.

The parameter screens are set up to provide a good starting point with the volts per hertz characteristic when the Enable Tuning command (register 100/1100, bit 1, PMI_TUN@) is issued. You can tune this curve by running the motor unloaded and monitoring motor current when going through the frequency range of interest. The curve should be modified to minimize current consumption/transients when going through the frequency range of interest.

2.4.1 Power Module Data Screen (Volts per Hertz)

The Power Module Data screen allows you to enter specific information about your power system configuration and the type of Power Module being used. See figure 2.9.

Power System Configuration

• DC Input Voltage or AC input Voltage

Select the type of input line voltage (AC input or DC input) and then enter the input voltage value.

Select DC Input Voltage if this is the DC bus voltage. Select AC Input Voltage if this is the AC RMS voltage that is being converted to DC bus voltage. This voltage determines which group of Power Modules may be selected from the Part Number list. The default selection is DC Input Voltage.

Figure 2.9 – Power Module Data Parameter Entry Screen (Volts per Hertz)


• MCR Connected To Output Contactor

If you have a motor control relay (MCR) on the output of the drive (output contactor), select this option. If there is only a manual disconnect switch and no contactor under automatic control, do not select the output contactor option. The default selection is no contactor.

Power Module

• Part Number

Select a part number from the list of supported Power modules (x nnn, where x is the voltage code and nnn is the horsepower rating). The current ratings in the list are the rated RMS currents at the drive’s default carrier frequency as listed in Appendix H, with no overload at 40° ambient temperature. The power module is capable of 150% of the maximum amps value for 1 minute. There is no default selection. You must choose a part number from the list.

The motor must be able to operate off the Power Module selected at the voltage level entered as the Input Voltage parameter. A warning will be issued when if an incompatibility is found.

• Carrier Frequency

The carrier frequency selected will determine the Power Module’s switching frequency. You can select from a list of preset carrier frequencies: 1.5 kHz, 2 kHz, 4 kHz, 6 kHz, 8 kHz, 10 kHz or 12 kHz; or you can enter a value between 1.5 kHz and 12 kHz in increments of 100 Hz. The hardware in some cases will have slightly coarser resolution at the higher frequencies. See Appendix H for the default carrier frequency and carrier frequency limit for the Power Module you have selected.

All Power Modules are rated at their default switching frequency, but they can be operated above this limit by de-rating the unit’s output. Refer to the SA3100 Power Modules instruction manual (S-3058) for more information.


2.4.2 Configuration Data - Setup (Volts per Hertz)

The Configuration Data - Setup parameter screen allows you to enter the following information about the Volts per Hertz regulator. See figure 2.10.

• Asynchronous or Synchronous Carrier

The default is asynchronous carrier, which can be used for most applications. Synchronous mode provides synchronization between the fundamental frequency output from the drive and the carrier frequency. This causes minimal circulating currents when inverters are swiched online.

Select Synchronous Carrier to cause the drive to synchronize the fundamental and the carrier whenever the commanded frequency is greater than 15 Hz.

• Constant or Variable Torque

These buttons provide for the selection of the variable torque or constant torque volts per hertz curve. The default is Constant Torque. When the Variable Torque button is selected, the Constant Voltage Frequency, Motor Rated Frequency, and Maximum Frequency fields are set to the same point.

• Unmodulated Six Step

Use this button to select the option of having the drive output an unmodulated six step waveform when at maximum output voltage.

Unmodulated six step is defined as the lack of any modulating pulses in the output waveform of the drive. Users who want maximum voltage output from the drive should select this option.

Figure 2.10 – Configuration Data Setup Parameter Entry Screen (Volts per Hertz)


• Current Limit

Selecting this button enables the current limit function in the drive. Specify the limiting current value in the Current Limit Amps field. Resolution is 0.1 amp.

• Current Limit Delay

Current Limit Delay provides a time delay for the drive to operate in the current limit region before executing the current limiting functions. If the regulator detects that output current has reached the specified limit, it will respond by setting bit 2 or 3 in register 204/1204. After the specified time delay, the regulator will set bit 4 in register 203/1203 (WRN_RIL@) and begin modifying the output frequency. Enter the value in seconds.

• Full Load Amps (Amperes)

Enter the default rated motor current. Resolution is 0.1 amp.

• Frequency Ramp Rate (Hertz/Second)

Frequency Ramp Rate specifies an adjustable limit for the maximum allowable rate of change in the frequency output. Enter the value in hertz per second.


2.4.3 V/Hz Characteristic Screen (Volts per Hertz)

The V/Hz Characteristic parameter screen allows you to enter specific information about the motor and V/Hz regulator. See figure 2.11.

• Maximum Frequency (Hertz)

Maximum Frequency defines the maximum frequency which will be output from the drive. Resolution is 0.001 Hz.

• Constant Voltage Frequency (Hertz)

Constant Voltage Frequency is the frequency point on the volts per hertz curve that marks the beginning of the constant voltage region. The voltage remains constant for all frequencies at or above the constant frequency point. Resolution is 0.001 Hz.

• Motor Rated Frequency (Hertz)

Motor Rated Frequency is divided into Motor Rated Voltage to define the motor rated V/Hz excitation. Resolution is 0.001 Hz.

• Motor Rated Voltage (Volts)

Motor Rated Voltage divided by Motor Rated Frequency defines the motor rated V/Hz excitation. Enter the value in volts.

• Operating Volts/Hz (Volts/Hertz)

The Operating Volts/Hz entry represents the volts per hertz ratio value. The value entered must be less than or equal to the Motor Rated Voltage divided by the Motor Rated Frequency. If no value is entered, a default value equal to the Motor Rated Voltage divided by the Motor Rated Frequency is provided. Resolution is 0.01V/Hz.

Figure 2.11 – V/Hz Characteristic Parameter Entry Screen (Volts per Hertz)


• Voltage Boost Volts (Volts)

Voltage Boost Volts and Voltage Boost Frequency define a point on the V/Hz curve where the slope changes, typically to accommodate low frequency instability. Resolution is 0.01V. Voltage Boost Volts is typically used to extend the range at constant torque to lower frequencies. This can also be used to avoid the “low frequency instability region” which is found in some motors with low or no connected inertia and low friction loads. When using the voltage boost with the variable torque configuration, the voltage value raises or lowers the central portion of the V/Hz characteristic (see Figure E.3).

• Voltage Boost Frequency (Hertz)

Voltage Boost Frequency and Voltage Boost Volts define a point in the V/Hz curve where the slope changes, typically to accommodate low frequency instability. Resolution is 0.001 Hz.

• Voltage Offset at Zero Hertz (Volts)

Voltage Offset at Zero Hertz is the voltage to be added at zero hertz to adjust the initial point on the volts per hertz curve. Resolution is 0.001V.

2.4.4 Feedback and Control Data Screen (Volts per Hertz)

No speed feedback is used with the Volts per Hertz regulator. The following Control Data Parameters can be entered with this screen. See figure 2.12.

Figure 2.12 – Speed Feedback and Control Parameter Entry Screen (Volts per Hertz)


• Over Speed Limit (RPM) (Range: 10 to 20,000)

This value is used to determine the maximum safe output frequency of the drive. There is no default value. Over Speed Limit should generally be equal to or less than the motor maximum safe speed or the driven equipment maximum safe speed, whichever is lower. If a value less than Rated Full Load Speed of the motor is entered, a warning will be generated.

• Speed Feedback Type

No Speed Feedback is the default setting.

Control Selections

• Output Rotation ( UVW, UWV )

This parameter allows you to reverse the direction of rotation of the output without re-wiring the motor leads. Select UVW (default) or UWV. See the SA3100 Diagnostics, Troubleshooting, and Start-Up Guidelines instruction manual (S-3059) for more information on motor orientation.

2.4.5 PMI Meter Port Selection Screen (Volts per Hertz)

The Meter Port Selection Parameter Entry screen allows you to enter specific information about what variables are to be output on the four PMI D/A channels (the four meter ports on the PMI motherboard. See figure 2.13.

Table 2.5 lists the values that can be displayed on the PMI meter ports. You must enter a Minimum Value and a Maximum Value for each selection except when you select Port Not Used. The Minimum Value is the value at which to output -10V. The Maximum Value is the value at which to output +10V. The system software then places the units per volt on the screen based on the Minimum/Maximum Values.

Figure 2.13 – PMI Meter Port Selection Entry Screen (Volts per Hertz)


The Minimum Value must not be less than -32768. The Maximum Value must not be greater than 32767. The Minimum Value must be less than the Maximum Value. Note that the PMI meter ports have 8-bit resolution and are updated on the average of every 1.0 milliseconds.

See the PMI Regulator instruction manual (S-3057) for more information about the PMI meter ports. See section 3.7.2.1 of this instruction manual for information about resolution of data.

PMI meter ports can also be set up on-line using the “Setup UDC” selection from the Monitor menu as described in the AutoMax Programming Executive instruction manual. If the meter ports are set up during parameter entry, the information is loaded onto the UDC module in the AutoMax rack along with all other parameter data. The meter port setup can then be changed on-line under “Setup UDC,” but this method would not actually write over the PMI meter port setup that was loaded to the rack. Instead, the new setup would be valid only until there was a Stop All or a power cycle, in which case the original setup would be used to determine what data to send out of the meter ports.

Table 2.5 – PMI Meter Port Parameters (Volts/Hertz)

• Port Not Used

• Voltage Reference (Volts)

• Voltage Reference (Counts)

• Voltage Feedback (Volts)

• Voltage Feedback (Counts)

• Frequency Reference (Hertz ∗ 10)

• Voltage Auxiliary Reference (Volts)

• DC Bus Voltage (Volts)

• DC Bus Current (Amps ∗ 10)

• Ground Fault Current (Amps ∗ 10)

• Motor Voltage Feedback (Volts)

• Motor Current Feedback (Amps ∗ 10)

• Output Frequency Hz ∗ 10)

• User Analog Input (Counts)

• Speed Feedback (RPM)

• Carrier Frequency (KHz ∗ 10)

• Application Data (Units)








• Power Module Heat Sink Temp (°C)


2.5 Configuring Flex I/O

The Configure Flex I/O Parameter Entry Screen allows you to configure your Flex I/O Modules, if Flex I/O is being used with your system. See figure 2.14.

A maximum of three Flex I/O modules is allowed. Module 0 and Module 1 must be digital; Module 2 can be either digital or analog.

• Module 0

Select a digital I/O module from the pull-down list. Only the supported digital I/O modules will be displayed. There is no default selection. You must choose a module from the list.

• Module 1

Select a digital I/O module from the pull-down list. Only the supported digital I/O modules will be displayed. There is no default selection. You must choose a module from the list.

• Module 2

Select an analog or digital I/O module from the pull-down list of supported modules. There is no default selection. You must choose a module from the list.

• Filter Time

This parameter is used only with input modules. The system determines the default filter time for the module selected. You may select a different time from a pull-down list.

Figure 2.14 – Flex I/O Parameter Entry Screen


• Channel 0 to Channel 7

If an analog I/O module is selected for Module 2, you must configure the channels for the analog module appropriately. No error checking is done by the system. The channels all default to “not used”.

2.6 Generating Drive Parameter Filesand Printing Drive Parameters

When you have completed all of the drive parameter screens, you can select “Close” to leave the Parameter Entry Screens and return to the master rack diagram with the UDC module selected. Zoom out or select the Exit command from the Configure menu to return to the System Configurator.

You can generate the drive parameter files by using the steps that follow.

Step 1. From the System Configurator, access the Task Manager by selecting the Manage Tasks command from the Rack menu.

Step 2. Select the Generate Configuration command from the Commands menu.

Step 3. Check the Generate Drive Parameter Files option in the Generate Files dialog box, and then select OK.

A file containing the newly-entered drive parameters will be created. The file will be named PARAMxx.POB, where xx is the slot number of the UDC module. Note that the drive parameter files must be loaded to the rack before (or at the same time as) the UDC application tasks are loaded to the rack. Refer to the AutoMax Programming Executive instruction manual for more detailed information.

You can print the drive parameters for a UDC module you specify by using the Print command from the Rack menu in the System Configurator. Refer to the AutoMax Programming Executive instruction manual for step-by-step instructions.


CHAPTER 3Configuring the UDC Module’s

Registers

The Variable Configurator application in the AutoMax Programming Executive is used to assign common variable names to the dual port memory registers on the UDC module. You can access these variable names by declaring them using the BASIC statement COMMON. The dual port memory has 2048 16-bit registers that are available to the AutoMax Processor and to the tasks that run on the UDC module.

The drive A and drive B registers that are assigned variable names will be latched into internal memory at the beginning of every scan of the UDC task to provide for a consistent context for evaluation. The UDC tasks (A and B) may be started and stopped independently of each other. At the end of the scan, the variables that have changed will be written back to the dual port memory.

Note that the dual port memory on the UDC module is treated like I/O data in terms of how the data is affected by Stop All commands and power cycling.

You can access the Variable Configurator by selecting Configure Variables from the Configure menu in the Rack Configurator. Refer to the AutoMax Programming Executive instruction manual for the procedures used to configure variables.

The sections that follow describe the registers you can configure in each view:

• The Port 0 Flex I/O Rail view is used to configure the registers assigned to the hardware that is attached to the PMI Flex I/O port. (These registers can also be accessed by double-clicking the PMI view.)

!ATTENTION:Only qualified electrical personnel familiar with the construction and operation of this equipment and the hazards involved should install, adjust, operate, or service this equipment. Read and understand this manual and other applicable manuals in their entirety before proceeding. Failure to observe this precaution could result in severe bodily injury or loss of life.

ATTENTION:Only qualified Drive Systems personnel or other trained personnel who understand the potential hazards involved may make modifications to the variable configuration. Any modifications may result in uncontrolled machine operation. Failure to observe this precaution could result in damage to equipment and bodily injury.

ATTENTION:Registers and bits in the UDC module that are described as “read only” or for “system use only” must not be written to by the user. Writing to these registers and bits may result in improper system operation. Failure to observe this precaution could result in bodily injury.

Configuring the UDC Module’s Registers 3-1

• The Command Registers view is used to configure pre-defined drive control registers that are written to either by an AutoMax application task or by a UDC application task and then sent to the PMI.

• The Feedback Registers view is used to configure the feedback registers that display the current status of the drive. These registers are written to by the PMI.

• The Application Registers Updated Every Scan view is used to configure the application registers that are used for the passing of application-specific control and status data between an AutoMax Processor and the UDC module on every scan. This register range is shared by drive A and drive B.

• The Application Registers Updated Every Nth Scan view is used to configure the application registers that are used for the passing of application-specific control and status data between an AutoMax Processor and the UDC module on every Nth scan, where “N” is defined in register 2001. This register range is shared by drive A and drive B.

• The UDC Module Test I/O Register view is used to configure the register that displays the status of the UDC module’s test switches and LED indicators. This view is also used to configure the UDC module’s D/A meter ports.

• The Interrupt Status and Control Registers view is used to configure the registers that control a user-defined interrupt to an AutoMax task and enable the CCLK signal on the backplane.

The Gain Data values that are used by the PMI are NOT mapped to the UDC module’s dual port registers. The gain values are held in local tunables with reserved names which must be defined in the UDC task for the drive (A or B). The programmer must use the pre-assigned local tunable reserved names described in Appendix B of this manual.

Note that register values are generally in the appropriate engineering units and that the variable names provided here are suggestions only; your variable names may be different. Duplicate common variable names are not permitted within any one rack.

Table 3.1 lists the configuration views in the AutoMax Programming Executive, the registers to be configured in each, and the section of this instruction manual in which the registers are discussed.

Table 3.2 lists the UDC dual port registers in numerical order.


3.1 Register and Bit Reference ConventionsUsed in this ManualRegister numbers are shown using the convention A/B, where A is the drive A register number and B is the drive B register number. Note that the Interrupt Status Control registers and the Application registers are the same for both drive A and drive B.

Register descriptions are shown in the following format:

• Register Name: Functional name of the register (e.g., Torque Reference Register).

• Register Numbers: Memory addresses of registers A and B.

• Sug. Var. Name: Suggested variable name for the register (e.g., TRQ_REF%).

• Units: Scaling unit applied to the value stored in the register (e.g., counts, amps *10, etc.).

• Range: The upper and lower limits of the value, where applicable (e.g. -4095 to +4095).

• Access: The level of access by the application task (Read, Write, or Read/Write).

Throughout this manual, bit descriptions are shown in the following format:

• Bit Name: Functional name of the bit (e.g., DC Bus Over Voltage Fault).

• Bit Number: The specific bit location within the register (e.g., Bit 0).

• Hex Value: The position within the 16 bit register (e.g., Bit Number 4 = 0010H)

• Sug. Var. Name: Suggested variable name for this bit (e.g., FLT_OV@ ).

• Access: The level of access by the application task (e.g., Read/Write).

• UDC Error Code: A drive fault’s corresponding error code (e.g. 1018). This is reported in the log for the task in which the error occurred.

• LED: The corresponding status LED, where applicable (e.g., EXT FLT on the PMI Regulator).

Register Name Register Numbers

[Functional description] Sug. Var. Name:Units:Range:Access:

[Additional descriptive details, if required]

Bit Name Bit Number

[Functional description] Hex Value:Sug. Var. Name:Access:UDC Error Code:LED:

[Additional descriptive details, if required]


Table 3.1 – UDC Module Configuration Views and Registers

View Register RangeDescribed in Section:

Port 0 Flex I/O Drive A: 0- 11Drive B: 12-23

3.2

UDC/PMI Communication Status Registers Drive A: 80-89Drive B: 1080-1089

3.3

Command Registers Drive A: 100-108Drive B: 1100-1108

3.4

Feedback Registers Drive A: 200-222Drive B: 1200-1222

3.5

Application Registers Updated Every Scan 300-599 3.6

Application Registers Updated Every Nth Scan 1300-1599 3.6

UDC Module Test I/O Registers 1000-1017 3.7

ISCR Data Registers 2000-2001 3.8


Table 3.2 – UDC Module Dual Port Memory Register Organization.

Registers Function

0 - 23 Flex I/O registers

24-79 System Use Only

80-89 UDC/PMI communication status registers for drive A(monitor only)


100-108 Command registers for drive A


200-222 Feedback registers for drive A


300-599 Application registers updated every scan for drives A and B


1000 UDC module test switch register

1001-1017 UDC module meter port setup registers


1080-1089 UDC/PMI communication status registers for drive B(monitor only)


1100-1108 Command registers for drive B


1200-1222 Feedback registers for drive B


1300-1599 Application registers updated every Nth scan for drives A and B


2000-2010 Interrupt Status and Control registers for drives A and B



3.2 Flex I/O Port Registers (Registers 0-23)

The Flex I/O Port 0 view is used to assign variable names and configure the registers used for the Flex I/O port on the PMI. If you have no hardware attached to this port, do not configure these registers. All of the Flex I/O data for PMI A and PMI B is combined into one section of the dual port memory. The appropriate variable configuration screen will be displayed based on the hardware that you have specified is connected to the port.

Note that the use of each register is a function of the type of Flex I/O module configured. After a Stop All, outputs are reset to zero and inputs continue to be updated.

The Flex I/O interface is designed to handle up to three Flex I/O modules. Registers 0/12 and 1/13 are reserved for digital I/O. Registers 2/14 to 9/21 can be used for a digital I/O module or an analog module. Registers 10/22 and 11/23 are used for Flex I/O status and error codes.

Table 3.3 lists the UDC registers reserved for Flex I/O.

Table 3.3 – Flex I/O Reserved Registers

Drive A Registers

Drive B Registers Description

0 12 Flex I/O Module 0, Digital (input or output)

1 13 Flex I/O Module 1, Digital (input or output)

2 14 Flex I/O Module 2, Digital or Analog 0 (input or output)

3 15 Flex I/O Module 2, Analog 1 (input or output)





8 20 Flex I/O Module 2, Analog 6 (input)

9 21 Flex I/O Module 2, Analog 7 (input)

10 22 Flex System Faults, Modules 0 and 1 faults

11 23 Flex I/O Module 2 faults


Table 3.4 lists the Flex I/O modules that are supported by the SA3100 system. Refer to the appropriate Flex I/O instruction manuals for specific information about the Flex I/O modules used in your system.

3.2.1 Digital Data Formats

Some digital I/O modules are only 8 bits and do not require the full 16 bits of the assigned UDC register. If the module is only 8 bits, then bits 8 through 15 are not used. Bit 0 is defined as Digital I/O channel 0, bit 1 is channel 1, etc.

Flex I/O module IB10X0B6 (10 input/6 output digital combo module) is mapped to UDC memory as shown below, with the lower ten bits configured as inputs and the upper 6 bits as outputs.

0 = Output

I = Input

Table 3.4 – Supported Flex I/O Modules

Module Type Catalogue Number Publication Number

Digital 24V DC

16 Point DC Sink Input 1794-IB16 1794-5.4

16 Point DC Source Output 1794-OB16 1794-2.3

16 Point DC Source Input 1794-IV16 1794-5.28

16 Point DC Sink Output 1794-OV16 1794-5.29

10 Input / 6 Output DC Combo 1794-IB10XOB6 1794-5.24

Digital 120V AC

8 Point AC Input 1794-IA8 1794-5.9

8 Point AC Output 1794-OA8 1794-5.10

Analog

8 Point Analog Input 1794-IE8/B 1794-5.6

4 Point Analog Output 1794-OE4/B 1794-5.5

4 Input / 2 Output Analog 1794-IE4XOE2/B 1794-5.15

Relay

8 Point Relay Output 1794-OW8 1794-5.19

Data Format: 8-bit Digital I/O

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Data - - - - - - - - I/O I/O I/O I/O I/O I/O I/O I/O

Data Format: Module IB10X0B6 - 10 Input / 6 Output Digital Combo

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Data O O O O O O I I I I I I I I I I


3.2.2 Analog Data Formats

Data is returned from the Flex I/O module’s analog-to-digital converter with 12-bit resolution. The value is left-justified into a 16-bit field, reserving the most significant bit for a sign bit.

A/D Unipolar Data 11 10 09 08 07 06 05 04 03 02 01 00

⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓Analog Value 0* 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

Input * = Always positive

A/D Bipolar Data S 10 09 08 07 06 05 04 03 02 01 00

⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓Analog Value S 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

D/A Data S 11 10 09 08 07 06 05 04 03 02 01 00

Output ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓ ⇓Analog Value S 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

Table 3.5 – Analog Data

Current (mA)

4-20mA Mode

0-20mA Mode Voltage (V)

+/- 10 Volt Mode 0-10 Volt ModeInput Output

-10.5 -32768 -32768

0 0 -10.0 -31200 -31208

1 1560 -9.0 -28080 -28088

2 3120 -8.0 -24960 -24968

3 4680 -7.0 -21840 -21848

4 0 6240 -6.0 -18720 -18728

5 1927 7800 -5.0 -15600 -15608

6 3854 9360 -4.0 -12480 -12488

7 5782 10920 -3.0 -9360 -9368

8 7710 12480 -2.0 -6240 -6248

9 9637 14040 -1.0 -3120 -3128

10 11565 15600 0 0 0 0

11 13492 17160 1.0 3120 3120 3120

12 15420 18720 2.0 6240 6240 6240

13 17347 20280 3.0 9360 9360 9360

14 19275 21840 4.0 12480 12480 12480

15 21202 23400 5.0 15600 15600 15600

16 23130 24960 6.0 18720 18728 18728

17 25057 26520 7.0 21840 21848 21848

18 26985 28080 8.0 24960 24968 24968

19 28912 29640 9.0 28080 28088 28088

20 30840 31200 10.0 31200 31208 31208

21 32767 32760 10.5 32752 32760 32760


3.2.3 Flex I/O Status and Error Codes

Register 10/22 contains status and error codes for Flex I/O Module 0 and Module 1. The memory map is shown in table 3.6.

Table 3.6 – Register 10/22 - Flex I/O Module 0 and Module 1 Faults

Bit Name Description

0 Flex Bus Fault Set if the Flex Bus Interface on the PMI Regulator has faulted.

1 Flex Clock Warning Set if the Flex I/O clock is not running.

2 Flex Scratch Pad Warning Set if a read/write Flex I/O memory error is detected.

3 Flex Dual Port Warning Set if a read/write Flex I/O dual port memory error is detected.

8 Module 0 Not Plugged In Set if no device is detected at the Module 0 port.

9 Module 0 Communication Error Set if there is a serial communication error with Module 0.

10 Module 0 Bad ID Set if a non-supported module ID is received from Module 0 or if the module ID received does not match the configured ID.

11 Module 0 Location Error Set if an analog module is physically located in the Flex I/O rail location designated for Module 0, and Module 0 has been configured for a Digital module.

12 Module 1 Not Plugged In Set if no device is detected at the Module 1 port.


14 Module 1 Bad ID Set if a non-supported module ID is received from Module 1 or if the module ID received does not match the configured module ID.

15 Module 1 Location Error Set if an analog module is physically located in the Flex I/O rail location designated for Module 0 or Module 1, and Module 1 has been configured for a Digital module.


Register 11/23 contains status and error codes for Flex I/O Module 2. The memory map is shown in table 3.7.

Table 3.7 – Register 11/23 - Flex I/O Module 2 Faults

Bit Name Description

0 Module 2 Not Plugged In Set if no device is detected at Module 2 port.


2 Module 2 Bad ID Set if a non-supported module ID is received from Module 2 or if the module ID received does not match the configured ID.

8 Channel 0 - Open Output/ Underrange Input

Bits 8 to 15 are set if there is an open output (4 - 20 mA current output only) or an under range input (4 - 20 mA current input only).

If a digital input is installed for Module 2 these bits are not used.









3.3 UDC/PMI Communication Status Registers(Registers 80-89/1080-1089)

The UDC/PMI Communication Status Registers display the status of the fiber-optic communications between the UDC module and the PMI. Two consecutive errors will be indicated by a communication fault, and the drive will stop. Refer to register 202/1202, bit 15, for more information. Note that the communication status registers are for system use only and can only be monitored. They cannot be defined during configuration for access within the application task. The status of these registers will be retained after a Stop All.

UDC Module Communication Status Register 80/1080

The UDC Module Communication Status register contains bits which describe any errors or warnings report-ed on the UDC module related to UDC/PMI communication. These bits are latched when set and will remain set until a fault reset or warning reset is issued.

Invalid Receive Interrupt Bit 0

The Invalid Receive Interrupt bit is set if the interrupt generated by the Universal Serial Controller (USC) is not properly marked.

Hex Value: 0001HSug. Var. Name: N/AAccess: Read onlyUDC Error Code: N/ALED: N/A

No End of Frame Status Received Bit 1

The No End of Frame Status Received bit is set if the USC does not report an End of Frame condition when the receive interrupt is generated.


CRC/Framing Error Bit 2

The CRC/Framing Error bit is set if the USC reports a CRC or Framing error on the last frame (message) received.


Overrun Error Bit 3

The Overrun Error bit is set if the USC reports a receive first-in, first-out overrun.



UDC Module Communication Status Register (Continued) 80/1080

DMA Format Error Bit 4

The DMA Format Error bit is set if the length of the received message does not match the length encoded in the message itself.


Transmitter Underrun Bit 5

The Transmitter Underrun bit is set if the USC reports a transmit first-in, first-out underrun.


CCLK Communication Synchronization Error Bit 6

The CCLK Communication Synchronization Error bit is set if two or more CCLK counter ticks occur and no message is received.

Hex Value: 0040HSug. Var. Name: N/AAccess: Read onlySug. Var. Name: VDC_RUN@UDC Error Code: N/ALED: N/A

External Loopback Data Error Bit 7

The External Loopback Data Error bit is set during the UDC module loopback test if the transmit message does not match the receive message. This test is performed only at power up or after a reset.


Missed Gains Bit 8

The Missed Gains bit is set if gain data from the PMI could not be written because memory was being written to when the gain values were received.



UDC Module Communication Status Register (Continued) 80/1080

Multiplexed Data Verification Failure Bit 9

The Multiplexed Data Verification Failure bit is set if data which is multiplexed into command/feedback messages does not verify correctly.


No Matching PMI Operating System Present Bit 10

The No Matching PMI Operating System Present bit is set if the correct PMI operating system is not present in the UDC module’s operating system and the PMI is requesting an operating system.


This condition will cause the loading of the PMI operating system to fail. However, the UDC module and the PMI will continue to retry loading the PMI operating system.

Invalid PMI Operating System Header Bit 11

The Invalid PMI Operating System Header bit is set if the UDC module cannot locate a valid PMI operating system header when attempting to load an operating system to a PMI.



Incompatible PMI Hardware Bit 12

The Incompatible PMI Hardware bit is set if the PMI hardware is not compatible with the PMI operating systems in the UDC operating system.


UDC Module Receive Count Register 81/1081

This register contains the number of messages received by the UDC module from the PMI. This is a 16-bit value that rolls over when it reaches its maximum.

Sug. Var. Name: N/AUnits: CountsRange: 0-32000Access: Read only


UDC Module CRC Error Count Register 82/1082

This register contains the number of messages with CRC errors received by the UDC module from the PMI.

Sug. Var. Name: N/AUnits: CountsRange: N/AAccess: Read only

UDC Module Format Error Count Register 83/1083

This register contains the number of messages with format errors received by the UDC module from the PMI.


PMI Communication Status Register 84/1084

The PMI Communication Status register contains bits which describe any errors or warnings reported by the PMI related to UDC/PMI communication. These bits are latched when set and will remain set until a fault reset or warning reset is issued.

Invalid Receive Interrupt Bit 0

The Invalid Receive Interrupt bit is set if the interrupt generated by the Universal Serial Controller (USC) is not properly marked.


No End of Frame Status Received Bit 1

The No End of Frame Status Received bit is set if the USC does not report an End of Frame condition when the receive interrupt is generated.


CRC/Framing Error Bit 2

The CRC/Framing Error bit is set if the USC reports a CRC or Framing error on the last frame (message) received.



PMI Communication Status Register (Continued) 84/1084

Overrun Error Bit 3

The Overrun Error bit is set if the USC reports a receive first-in, first-out overrun.


DMA Format Error Bit 4

The DMA Format Error bit is set if the length of the received message does not match the length encoded in the message itself.


Transmitter Underrun Bit 5

The Transmitter Underrun bit is set if the USC reports a transmit first-in, first-out underrun.


CCLK Communication Synchronization Error Bit 6

The CCLK Communication Synchronization Error bit is set if two or more CCLK counter ticks occur and no message is received.


UDC CCLK Communication Synchronization Error Bit 8

The UDC CCLK Communication Synchronization Error bit is set if two UDC CCLK counter ticks occur and no message is received from the PMI.




Multiplexed Data Verification Failure Bit 9

The Multiplexed Data Verification Failure bit is set if data multiplexed into command/feedback messages does not verify.


Invalid PMI Start Operating System Address Bit 12

The Invalid PMI Start Operating System Address bit is set by the PMI if the operating system is not within the allocated operating system address area.



Insufficient PMI Memory to Load the PMI Operating System Bit 13

The Insufficient PMI Memory to Load the PMI Operating System bit is set by the PMI if there is insufficient memory for loading the operating system.



Invalid PMI Load Address Bit 14

The Invalid PMI Load Address bit is set by the PMI if the address at which it is to load the operating system is invalid.





PMI Operating System Overflow into Stack Memory Bit 15

The PMI Operating System Overflow into Stack Memory bit is set by the PMI if the loading of the PMI operating system will overrun the PMI stack memory area.



PMI Receive Count Register 85/1085

The PMI Receive Count Register contains the number of messages received by the PMI. This is a 16-bit value that rolls over when it reaches its maximum.


PMI CRC Error Count Register 86/1086

This register contains the number of messages with CRC errors re-ceived by the PMI.


PMI Format Error Count Register 87/1087

This register contains the number of messages with format errors re-ceived by the PMI.



UDC Module Fiber-Optic Link Status Register 88/1088

This register shows the current operating state of the fiber-optic link to the PMI. The lower byte (bits 0-7) shows the actual link status while the upper byte (bits 8-15) shows whether the communication taking place is synchronized or not.

Sug. Var. Name: N/AUnits: N/ARange: N/AAccess: Read only

If the lower byte is equal to:

xx01H: the UDC module is waiting for a request from the PMI for an operating system.

xx02H: the UDC module is downloading an operating system to the PMI.

xx03H: the UDC module and the PMI are exchanging data.

xx06H: the external loopback test is being conducted on the fiber-optic link.

If the upper byte is equal to:

01xxH: the communication between the UDC module and the PMI is synchronized.

02xxH: the communication between the UDC module and the PMI is not synchronized.

UDC Module Transmitted Message Count Register 89/1089

This register contains the number of messages transmitted by the UDC module.



3.4 Command Registers (Registers 100-199/1100-1199)

The Command Registers view is used to configure command registers. These registers are used for command data sent to the PMI by the UDC module at the end of every scan of the UDC Processor. Note that the bits in these registers (except bit 15 in register 100/1100) are used to command action only and do not indicate the status of the action commanded. The feedback registers (registers 200/1200 to 299/1299) are provided for this purpose. The status of the command registers is not retained after a Stop All.

.

Drive Control Register 100/1100

The Drive Control Register contains the bits that control the operation of the drive. The SA3100 drive can op-erate in one of four modes: idle, minor loop run, PMI tuning, or bridge test. The default operating mode is idle. The other three modes are selected using the Drive Control register. Each of these modes is described in de-tail in the SA3100 Diagnostics, Troubleshooting, and Start-Up Guidelines instruction manual (S-3059).

All bits in this register (except bit 15) can only be written to by a task on an AutoMax Processor. They cannot be written to by a task on a UDC module. All read/write bits in this register are edge-sensitive and must be maintained to assert the command.

Enable PMI Run Bit 0

The Enable PMI Run bit is set to enable the motor regulation minor loop in the PMI Regulator.

Hex Value: 0001HSug. Var. Name: PMI_RUN@Access: Read/WriteUDC Error Code: N/ALED: N/A

Enable Tuning Bit 1

The Enable Tuning bit is set to begin the Auto-Tune procedure.

When the PMI Regulator completes this task, it sets bit 1 in register 200/1200.

Hex Value: 0002HSug. Var. Name: PMI_TUN@Access: Read/WriteUDC Error Code: N/ALED: N/A

Setting this bit requests the PMI Regulator to calculate the values for local tunables STATOR_R_E4% (stator resistance), STATOR_T_E4% (stator time constant), and STATOR_IZ_E1% (no load stator current).

In Volts per Hertz mode, setting this bit enables the V/Hz inverter to reset the tunable gains used for generating the V/Hz curve to their default values.


Drive Control Register (Continued) 100/1100

Bridge Test Enable Bit 2

The Bridge Test Enable bit is set to begin the bridge test procedure.

Hex Value: 0004HSug. Var. Name: BRG_TST@Access: Read/WriteUDC Error Code: N/ALED: N/A

The bridge test turns on individual or sets of power devices in the Power Module in order to verify the gate cable connections and power device operation. The value in the Bridge Test Code register (105/1105) is used to select which power devices to turn on.

This test is normally performed at the factory and should not have to be performed again unless the power devices are replaced. Refer to the SA3100 Diagnostics, Troubleshooting, and Start-Up Guidelines instruction manual (S-3059) for further information on performing the bridge test.

!ATTENTION:The motor must be disconnected before this test is run. Failure to observe this precaution could result in damage to, or destruction of, the equipment.

Bus Enable Bit 4

The Bus Enable bit is set to request the PMI Regulator to close the pre-charge contactor.

Hex Value: 0010HSug. Var. Name: BUS_ENA@Access: Read/WriteUDC Error Code: N/ALED: N/A

When bus voltage is greater than the value in the undervoltage threshold tunable variable (UVT_E0%) and has reached a steady state, and feedback indicates that the pre-charge contactor has closed, the PMI Regulator will set bit 4 of register 200/1200 (DC Bus Ready). Refer to the SA3100 Power Modules instruction manual (S-3058) for more information about internal DC bus control.

DC Braking On Bit 5

The application task sets the DC Braking On bit to cause the drive to apply DC current injection braking. The magnitude of the DC current is controlled by register 108/1108 (BRK_REF%).

Hex Value: 0020HSug. Var. Name: BRK_ON@Access: Read/WriteUDC Error Code: N/ALED: N/A



Synchronous Transfer Request* Bit 7

*Reserved for future use.

The application task sets the Synchronous Transfer Request bit to begin matching the Voltage, Period, and Phase of the drive’s PWM output to an external source.

Hex Value: 0080HSug. Var. Name: SX_REQ@Access: Read/WriteUDC Error Code: N/ALED: N/A

When synchronization is ready, register 200, bit 7 (SYN_OK@) is turned on to indicate that the synchronous transfer may be done.

Fault Reset Bit 8

The Fault Reset bit is set and reset to clear the Drive Fault register 202/1202. After a drive fault is latched, the Drive Fault register must be cleared before the drive can be re-started.

Hex Value: 0100HSug. Var. Name: FLT_RST@Access: Read/WriteUDC Error Code: N/ALED: N/A

To clear the Drive Fault register any command bits that have been set in the Drive Control register (100/1100) must first be turned off. Once the cause of the fault has been corrected, the Fault Reset bit must be turned on and then off again. The Fault Reset bit will clear the entire Drive Fault register. Then the desired command bits may be turned on again.

The Fault Reset bit is edge-sensitive, i.e., leaving it set will not clear the fault register continuously. Note that if the fault condition still exists after register 202/1202 is cleared, it will continue to trigger drive faults until the problem has been corrected.

Warning Reset Bit 9

The Warning Reset bit is set and reset to clear the Drive Warning register 203/1203. This bit is edge-sensitive, i.e., leaving it set will not clear the warning register continuously.

Hex Value: 0200HSug. Var. Name: WRN_RST@Access: Read/WriteUDC Error Code: N/ALED: N/A

Bit 10

Reserved for future use. Hex Value: 0400HSug. Var. Name:Access: Read onlyUDC Error Code: N/ALED: N/A



Bit 11


Bit 12

Reserved for Future Use. Hex Value: 1000HSug. Var. Name:Access: Read onlyUDC Error Code: N/ALED: N/A

UDC Task Running Bit 15

The UDC Task Running bit is a status bit that indicates that the UDC task is running. This bit is used by the PMI Regulator to prevent the minor loop from running if the UDC task is not running.

Hex Value: 8000HSug. Var. Name: UDC_RUN@Access: Read onlyUDC Error Code: N/ALED: N/A

This bit must NOT be written to by the user. This is a status bit that must only be written to by the operating system.

I/O Control Register 101/1101

The I/O Control Register contains the bits that control the EXT FLT LED on the PMI, the Auxiliary Output on the Resolver & Drive I/O board, and the operation of the resolver external strobe input.

No Slip Adjustment (Vector with Constant Power) Bit 0

The No Slip Adjustment command bit is set during constant power drive commissioning. Setting this bit causes the drive to disable slip accommodation.

Hex Value: 0001HSug. Var. Name: NO_ADJ@@Access: Read/WriteUDC Error Code: N/ALED: N/A

No Slip Smoothing (Vector with Constant Power) Bit 1

The No Slip Smoothing command bit is set during constant power drive commissioning. Setting this bit causes the drive to disable magnetizing current interpolation.

Hex Value: 0002HSug. Var. Name: NO_INTR@Access: Read/WriteUDC Error Code: N/ALED: N/A


I/O Control Register (Continued) 101/1101

External Fault LED Bit 2

The External Fault LED command bit is set by the application task to turn on the EXT FLT LED on the PMI Regulator.

Hex Value: 0004HSug. Var. Name: EXT_LED@Access: Read/WriteUDC Error Code: N/ALED: EXT FLT

Auxiliary Output Bit 4

The Auxiliary Output command bit is set to turn on the auxiliary output on the Resolver & Drive I/O board.

Hex Value: 0010HSug. Var. Name: AUX_OUT@Access: Read/WriteUDC Error Code: N/ALED: AUX OUT

Enable Resolver Calibration Test Bit 6

The Enable Resolver Calibration Test bit is set to begin the test that determines the resolver’s balance value. This value will be stored in the pre-defined local tunable RES_BAL%.

Hex Value: 0040HSug. Var. Name: RES_CAL@Access: Read/WriteUDC Error Code: N/ALED: N/A

This bit is edge sensitive. The test will turn off if the bit is reset. Refer to register 201/1201, bits 6 and 7, for information on the calibration test complete bits. Refer to the PMI Regulator instruction manual (S-3057) for additional resolver calibration information.

Enable External Strobe Bit 8

The Enable External Strobe bit is set to enable the external strobe on the resolver to capture the position of the resolver when the rising edge of the external strobe is detected. As long as this bit is set, the external strobe is enabled.

Hex Value: 0100HSug. Var. Name: STR_ENA@Access: Read/WriteUDC Error Code: N/ALED: N/A

If this bit is set in conjunction with bit 9, the resolver position is captured on both the rising and falling edges of the input signal. See register 201/1201, bits 8 and 9, for additional information. The resolver position data is placed in the Resolver Strobe Position register (register 216/1216).


I/O Control Register (Continued) 101/1101

Enable External Strobe Falling Edge Bit 9

The Enable External Strobe Falling Edge bit is set to enable the external strobe on the resolver to capture the position of the resolver when the falling edge of the external strobe is detected. As long as this bit is set, the external strobe is enabled.

Hex Value: 0200HSug. Var. Name: STR_ENF@Access: Read/WriteUDC Error Code: N/ALED: N/A

If this bit is set in conjunction with bit 8, the resolver position is captured on both the rising and falling edges of the input signal. See register 201/1201, bits 8 and 9, for additional information. The resolver position data is placed in the Resolver Strobe Position register (register 216/1216).

Enable STATOR_IZ_E1% Tuning (Vector with Constant Power) Bit 10

The Enable STATOR_IZ_E1% Tuning bit is set to start the procedure to tune the value of STATOR_IZ_E1%.

Hex Value: 0400HSug. Var. Name: TUNE_IZ@Access: Read/WriteUDC Error Code: N/ALED: N/A

Note that this procedure is used in Vector with Constant Power applications only. Refer to Appendix B for more information on this procedure.

Dynamic Torque Overload Ratio On Bit 12

The Dynamic Torque Overload Ratio On bit is set to allow the torque overload ratio to be altered dynamically by the contents of the FLX_REF% register.

Hex Value: 1000HSug. Var. Name: TORD_ON@Access: Read/WriteUDC Error Code: N/ALED: N/A

Note that this feature cannot be utilized with the configuration to manually alter the magnetization current of the motor, or utilized with the dual-wound motor configuration. The overload ratio is modified by the contents of FLX_REF% with a value of 4095 being defined as equal to the configured overload ratio. Therefore, a value of 2048 will reduce the overload ratio by one-half.

UDC Module External Loopback Bit 15

The UDC Module External Loopback bit is set to enable the external loopback test on the UDC module’s fiber-optic ports.

Hex Value: 8000HSug. Var. Name: UDC_LB@Access: Read/WriteUDC Error Code: N/ALED: N/A

Register 101, bit 15, controls the COMM A test while register 1101, bit 15, controls the COMM B test. This bit must be reset to 0 before the loopback connector is removed from the UDC module’s fiber-optic ports. Refer to the Fiber-Optic Cabling instruction manual for specific instructions on performing the loopback test.


Torque Reference Register (Vector) 102/1102

In Vector mode, register 102/1102 functions as the Torque Reference Register. The value in this register is the reference sent to the PMI Regulator for use in the Vector control algorithm minor loop.

Sug. Var. Name: TRQ_REF%Units: CountsRange: -4095 to +4095Access: Read/Write

This value corresponds to the torque produced by the configured maximum motor current (rated motor current ∗ motor overload ratio). Values of -4095 and +4095 represent full scale torque in either direction. The value in this register is limited to not exceed +/- 4095.

See register 203/1203, bit 4, for additional information.

Frequency Reference Register (V/Hz) 102/1102 and 103/1103

In Volts per Hertz mode, registers 102/1102 and 103/1103 form a double precision register that contains the frequency reference value. Register 102/1102 holds the high word. Register 103/1103 holds the low word.

Sug. Var. Name: FRQ_REF!Units: Hz ∗ 1000Range: +/- 600 HzAccess: Read/Write

The value is entered in Hz ∗ 1000. For example, a value of 400,000 represents 400.000 Hz.

See register 203/1203, bit 4, for additional information.

Flux Reference Register (Vector) 104/1104

In Vector mode, register 104/1104 functions as the Flux Reference register. The value in this register defines the ratio used to scale the value for magnetizing current (STATOR_IZ_E1%).

Sug. Var. Name: FLX_REF%Units: CountsRange: 0 to 4095Access: Read/Write

This value is used when the Enable UDC Flux Reference option has been selected during parameter entry for the SA3100 Vector regulator, or the Manual Compensation option has been selected for the SA3100 Vector regulator with Constant Power. For example, if register 104 = 4095, then the full value of STATOR_IZ_E1% will be used for magnetizing current. When the TORD_ON@ bit is set, this value scales the overload ratio.

Boost Voltage Reference (V/Hz) 104/1104

In Volts per Hertz mode, register 104/1104 functions as the Boost Voltage Reference register. The value in this register is used to increase the voltage derived from the V/Hz characteristic curve in order to increase torque and decrease slip.

Sug. Var. Name: VLT_REF%Units: Volts ∗ 10Range: +/- 5VAccess: Read/Write


Bridge Test Code Register 105/1105

The value written to the Bridge Test Code register determines which power device to turn on during the bridge test.

Sug. Var. Name: TST_CODE%Units: N/ARange: N/AAccess: Read/Write

The six least significant bits correspond to the six power devices:

Bit 0 U Upper Power DeviceBit 1 V Upper Power DeviceBit 2 W Upper Power DeviceBit 3 U Lower Power DeviceBit 4 V Lower Power DeviceBit 5 W Lower Power Device

Patterns that turn on the same device in the upper and lower bridge are not accepted, and no device will be turned on. Bit 4 in the Drive Warning register (203/1203) is set if an illegal pattern is used.

When a value of -1 is entered in this register, the test will cycle through each power device individually in the following order: U-, U+, V-, V+, W-, W+.

Refer to the SA3100 Diagnostics, Troubleshooting, and Start-Up Guidelines (S-3059) for more information about the bridge test.

PMI D/A Output Register 106/1106

The value in the PMI D/A Output Register can be displayed on one of the four PMI Regulator meter ports. See section 3.6.2.

Sug. Var. Name: PMI_DA%Units: See belowRange: See belowAccess: Read/Write

This register can contain any variable in the AutoMax system as long as it is a 16-bit integer. Double-integer or floating point values cannot be displayed on the PMI Regulator’s D/A meter ports. The desired value must be copied into this register by an application task. The value in the register is transmitted to the PMI Regulator at the end of every scan.

Synchronous Transfer Volts Register* 107/1107


The Synchronous Transfer Volts register is used during a synchronous transfer to hold the value of the external voltage source. The value is scaled in volts.

Sug. Var. Name: SA_V%Units: VoltsRange: N/AAccess: Read/Write

DC Braking Reference Register 108/1108

The value in the DC Braking Reference register regulates the magnitude of braking current that is output when the BRK_ON@ signal (register 100, bit 5) is asserted.

Sug. Var. Name: BRK_REF%Units: Amps ∗ 10Range: Motor rated ampsAccess: Read/Write


3.5 Feedback Registers (Registers 200-299/1200-1299)

The Feedback Registers view is used to configure the feedback registers that display the current status of the drive. These registers are updated by the PMI and sent to the UDC module over the fiber-optic link before every scan of the UDC task. The status of these registers is retained after a Stop All.

Drive Status Register 200/1200

The bits in the Drive Status register indicate the current state of the drive. They reflect the status of the activity initiated through the Drive Control Register (register 100/1100). All the bits in this register are written to by the PMI.

Torque / Frequency Control OnBit 0

The PMI sets the Torque Control On (Vector mode) or Frequency Control On (V/Hz mode) status bit in response to the PMI_RUN@ command after all of the interlock tests are passed to indicate that the minor loop is running and the motor is energized.

Hex Value: 0001HSug. Var. Name: TRQ_ON@ or

FRQ_ON@Access: Read onlyUDC Error Code: N/ALED: N/A

Automatic Tuning Complete Bit 1

The PMI sets the Automatic Tuning Complete status bit in response to the PMI_TUN@ command when the tuning procedure is complete.

Hex Value: 0002HSug. Var. Name: PMI_ATC@Access: Read onlyUDC Error Code: N/ALED: N/A

In Vector mode, the PMI processor sets this bit to indicate that the calculations for local tunables STATOR_R_E4% (stator resistance), STATOR_T_E4% (stator time constant), and STATOR_IZ_E1% (no load stator current) are complete.

In Volts per Hertz mode, the PMI processor sets this bit when the Reset V/Hz Curve Point Gains procedure is complete. The bit is turned off when PMI_TUN@ is turned off.

Refer to Appendix B for more information on the local tunables and gains variables.

Torque / Frequency Reference Saturation Plus Bit 2

In Vector mode, the PMI sets the Torque Reference Saturation Plus bit when the system is requesting maximum positive torque from the drive.

In Volts per Hertz mode, the Frequency Reference Saturation Plus bit is set when the current limit option has been selected, and current feedback is at the positive limit.

Hex Value: 0004HSug. Var. Name: TRF_SP@ or

FRF_SP@Access: Read onlyUDC Error Code: N/ALED: N/A


Drive Status Register (Continued) 200/1200

Torque / Frequency Reference Saturation Minus Bit 3

In Vector mode, the PMI sets the Torque Reference Saturation Minus bit when the system is requesting maximum negative torque from the drive.

In Volts per Hertz mode, the Frequency Reference Saturation Minus bit is set when the current limit option has been selected, and current feedback is at the negative limit.

Hex Value: 0008HSug. Var. Name: TRF_SM@ or

FRF_SM@Access: Read onlyUDC Error Code: N/ALED: N/A

DC Bus Ready Bit 4

The PMI Regulator sets the DC Bus Ready status bit in response to the BUS_ENA@ command when the following conditions are detected:

Hex Value: 0010HSug. Var. Name: BUS_RDY@Access: Read onlyUDC Error Code: N/ALED: N/A

• DC bus voltage is greater than the undervoltage threshold value stored in local tunable UVT_E0% and has reached a steady state

• feedback indicates that the pre-charge contactor has been commanded ON (i.e., to close).

Refer to the SA3100 Power Modules instruction manual (S-3058) for more information about internal DC bus control.

Constant Power Region (Vector with Constant Power) Bit 5

If the drive has been configured to operate in the Vector with Constant Power mode, the PMI Regulator will set the Constant Power Region bit when the drive is operating in the constant power range (flux weakening occurs).

Hex Value: 0020HSug. Var. Name: PWR_RNG@Access: Read onlyUDC Error Code: N/ALED: N/A

OK Synchronous Transfer* Bit 7


The PMI processor sets the OK Synchronous Transfer bit when the drive’s output voltage, period, and phase are matched to the external source and synchronous transfer may be done.

Hex Value: 0080HSug. Var. Name: SX_OK@Access: Read onlyUDC Error Code: N/ALED: N/A


Drive Status Register (Continued) 200/1200

Fault Detected Bit 8

The PMI Regulator sets the Fault Detected status bit if any fault is detected. This bit is reset by bit 8 of register 100/1100.

Hex Value: 0100HSug. Var. Name: FLT@Access: Read onlyUDC Error Code: N/ALED: N/A

See the description of the Drive Fault register (202/1202) for more information.

Warning Detected Bit 9

The Warning Detected status bit is set if any warning is detected. This bit is reset by bit 9 of register 100/1100.

Hex Value: 0200HSug. Var. Name: WRN@Access: Read onlyUDC Error Code: N/ALED: N/A

See the description of the Drive Warning register (203/1203) for more information.

CCLK Synchronized Bit 14

The PMI Regulator sets the CCLK Synchronized status bit when CCLK in the UDC module is synchronized with CCLK in the PMI Regulator.

Hex Value: 4000HSug. Var. Name: CCLK_OK@Access: Read onlyUDC Error Code: N/ALED: N/A

This bit is set to zero if CCLK is not turned on in the AutoMax rack or if there have been two consecutive instances when CCLK is not synchronized after the application task has turned CCLK on. In this case, the feedback data from the PMI is not current.

This bit should normally be used only in the start permissive logic for the drive (which must be true only once to start the drive). It does not normally have to be used in the run permissive logic for the drive (which must be true during the entire execution of the task. Note, however, that applications requiring very tight synchronization between the UDC module and the PMI (e.g., positioning applications) may require the use of this bit in the run permissive logic.

Refer to the Communication Lost Fault bit description (register 202/1202, bit 15) for more information.

PMI Operating System Loaded Bit 15

The PMI Regulator sets the PMI Operating System Loaded status bit when the operating system has been successfully downloaded from the UDC module to the PMI Regulator after power-up.

Hex Value: 8000HSug. Var. Name: PMI_OK@Access: Read onlyUDC Error Code: N/ALED: N/A


I/O Status Register 201/1201

The bits in the I/O Status register indicate the current state of the inputs on the Resolver & Drive I/O board.

Run Permissive Input Bit 0

The Run Permissive Input bit displays the status of the input signal connected to pin A on the DRIVE I/O connector. When the signal is present, this bit is set.

Hex Value: 0001HSug. Var. Name: RPI@Access: Read onlyUDC Error Code: N/ALED: RPI

This signal typically originates from the drive’s coast-to-stop circuit.

M-Contactor Feedback Bit 1

The M-Contactor Feedback bit reflects the status of the M-contactor feedback input signal, which is connected to the AUX IN1 input on the Resolver & Drive I/O board. When the input signal is present, this bit is set.

Hex Value: 0002HSug. Var. Name: M_FDBK@Access: Read onlyUDC Error Code: N/ALED: AUX IN1

Auxiliary Input 2 Bit 2

The Auxiliary Input 2 bit reflects the status of the 115 VAC auxiliary input 2 on the Resolver & Drive I/O board. When the input signal is present, this bit is set.

Hex Value: 0004HSug. Var. Name: AU_INX2@Access: Read onlyUDC Error Code: N/ALED: AUX IN2



Hex Value: 0008HSug. Var. Name: AUX_IN3@Access: Read onlyUDC Error Code: N/ALED: AUX IN3





I/O Status Register (Continued) 201/1201




Resolver Gain Calibrated Bit 6

The Resolver Gain Calibrated status bit is set when the resolver gain calibration procedure is complete. This procedure is performed when the value stored in local tunable RES_GAN% is set to zero.

Hex Value: 0040HSug. Var. Name: RES_GAN@Access: Read onlyUDC Error Code: N/ALED: N/A

Resolver Balance Calibrated Bit 7

The Resolver Balance Calibrated status bit is set when the resolver balance calibration procedure is complete. This procedure is performed when the Enable Resolver Calibration Procedure bit (register 101/1101, bit 6) is set and the motor is tuning.

Hex Value: 0080HSug. Var. Name: RES_BAL@Access: Read onlyUDC Error Code: N/ALED: N/A

External Strobe Detected Bit 8

The External Strobe Detected status bit is set when the external strobe on the motor’s resolver is detected. Register 216/1216 displays the position of the resolver at the time of the strobe.

Hex Value: 0100HSug. Var. Name: STR_DET@Access: Read onlyUDC Error Code: N/ALED: N/A

Note that this bit is set for only one scan, allowing a strobe to be detected every scan. The UDC task must check the External Strobe Detected bit each scan to ensure the validity of the strobe data in register 216/1216.

External Strobe Level Bit 9

The External Strobe Level status bit is set or reset by the system when the external strobe is detected. It indicates whether the external strobe level was rising (1) or falling (0).

Hex Value: 0200HSug. Var. Name: STR_LVL@Access: Read onlyUDC Error Code: N/ALED: N/A


I/O Status Register (Continued) 201/1201

STATOR_IZ_E1% Tuning Complete (Vector with Constant Power) Bit 10

The STATOR_IZ_E1% Tuning Complete status bit is set to indicate that the system has successfully tuned the value in STATOR_IZ_E1%.

Hex Value: 0400HSug. Var. Name: TUNED_IZ@Access: Read onlyUDC Error Code: N/ALED: N/A

Note that this procedure is used in Vector with Constant Power applications only. Refer to Appendix B for more information on this procedure.

Drive Fault Register 202/1202

The bits in the Drive Fault register indicate the cause of a drive shutdown. The bits in this register are latched until they are reset by setting the Fault Reset bit (bit 8) of the Drive Control register (100/1100, bit 8). After turning the Fault Reset bit on, the drive may be re-started after turning the desired command bit in register 100/1100 off and then back on again. If the fault condition still exists, the identifying bit in this register will immediately set again.

The fault conditions reported in this register result in turning off the drive. The UDC task is not stopped automatically if a drive fault occurs unless it is specifically instructed to in the application task. The user must ensure that the AutoMax application task tests register 202/1202 and takes appropriate action if a fault occurs.

Note that the status of this register is also reported in the error log for the task in which the error occurred. Most faults reported in this register are also indicated by the EXT FLT or P.M. FLT LEDs on the PMI Regulator.

DC Bus Overvoltage Fault Bit 0

The DC Bus Overvoltage Fault bit is set if DC bus voltage exceeds:

• 396 volts for 230 VAC Power Modules



Hex Value: 0001HSug. Var. Name: FLT_OV@Access: Read onlyUDC Error Code: 1018LED: EXT FLT

DC Bus Overcurrent Fault Bit 1

The DC Bus Overcurrent Fault bit is set if DC bus current exceeds 125% of the rated Power Module current.

Hex Value: 0002HSug. Var. Name: FLT_DCI@Access: Read onlyUDC Error Code: 1020LED: P.M. FLT


Drive Fault Register (Continued) 202/1202

Ground Current Fault Bit 2

The Ground Current Fault bit is set if ground current exceeds the hardware trip point.

Hex Value: 0004HSug. Var. Name: FLT_GND@Access: Read onlyUDC Error Code: 1021LED: EXT FLT

For models A001/Q001 and A003/Q003 the hardware trip point is 20A @ 10V.For all other models it is 100A @ 10V.

Instantaneous Overcurrent Fault Bit 3

The Instantaneous Overcurrent (IOC) Fault bit is set if either of the following conditions is detected:

Hex Value: 0008HSug. Var. Name: FLT_IOC@Access: Read onlyUDC Error Code: 1017LED: P.M. FLT

• Output current is greater than 200% of the peak RMS current. Bits 0 to 5 in register 204/1204 indicate which power device detected the overcurrent.

• An inverter power device fault is detected. Bit 6 in register 204/1204 will be set if the IOC fault is due to a power device overcurrent.

Power Supply Fault Bit 4

The Power Supply Fault bit is set if the output of the isolated +12V supply, or the output of the external power supply for a G or H frame drive, falls below the configured low voltage threshold.

Hex Value: 0010HSug. Var. Name: FLT_12V@Access: Read onlyUDC Error Code: 1022LED: P.M. FLT

Register 222/1222 provides additional diagnostics if this fault occurs.

Bit 5

Reserved for future use. Hex Value: 0020HSug. Var. Name:Access: Read onlyUDC Error Code: 1023LED:



Charge Bus Time-Out Fault Bit 6

The Charge Bus Time-out Fault bit is set to indicate any of the conditions listed below. Register 222/1222 provides additional diagnostics if this fault occurs.

Hex Value: 0040HSug. Var. Name: FLT_CHG@Access: Read onlyUDC Error Code: 1024LED: EXT FLT and

P.M. FLT

• The DC bus is not fully charged within 10 seconds after the bus enable bit (register 100/1100, bit 4) is set.

• The drive is on and feedback indicates that the pre-charge contactor has opened.

• DC bus voltage is less than the value stored in the Power Loss Fault Threshold (PLT_E0%) tunable variable.

• The lack of 115VAC or 24V DC applied to the precharge module on common bus units (C through H-frame).

If the Charge Bus Time-Out Fault bit is set, verify that incoming power is at the appropriate level. If the power level is correct, the problem is in the Power Module.

Over Temperature Fault Bit 7

The Over Temperature Fault bit is set if the thermistor in the Power Module detects a temperature of 100° C or more.

Hex Value: 0080HSug. Var. Name: FLT_OT@Access: Read onlyUDC Error Code: 1016LED: P.M. FLT

Resolver Broken Wire Fault Bit 8

The Resolver Broken Wire Fault bit is set if a sine or cosine signal from the resolver is missing due to a broken wire or if the resolver gain tunable (RES_GAN%) has been set too low.

Hex Value: 0100HSug. Var. Name: FLT_TBW@Access: Read onlyUDC Error Code: 1008LED: FDBK OK

Resolver Fault Bit 9

The Resolver Fault bit is set if the fuse blows on the Resolver & Drive I/O board. This indicates the board has failed and must be replaced.

Hex Value: 0200HSug. Var. Name: FLT_RES@Access: Read onlyUDC Error Code: 1009LED: N/A



Overspeed Fault Bit 10

The Overspeed Fault bit is set if the motor’s velocity exceeds the value entered as the Overspeed Trip (RPM) configuration parameter.

Hex Value: 0400HSug. Var. Name: FLT_OSP@Access: Read onlyUDC Error Code: 1010LED: EXT FLT

Power Technology Fault Bit 11

The Power Technology Fault bit is set to indicate a problem with the AC power technology circuit on the PMI Regulator motherboard.

Hex Value: 0800HSug. Var. Name: FLT_PTM@Access: Read onlyUDC Error Code: 1011LED: OK

Register 222/1222 provides additional diagnostics if this fault occurs.

Bit 12

Reserved for future use. Hex Value: 1000HSug. Var. Name:Access: Read onlyUDC Error Code: 1012LED:

PMI Regulator Bus Fault Bit 13

The PMI Regulator Bus Fault bit is set if the Resolver & Drive I/O board or the AC power technology circuit does not respond to requests from the PMI Processor. This indicates a hardware problem in the PMI Regulator.

Hex Value: 2000HSug. Var. Name: FLT_BUS@Access: Read onlyUDC Error Code: 1013LED: N/A

UDC Run Fault Bit 14

The UDC Run Fault bit is set if the UDC task stops while the minor loop is running in the PMI Regulator.

Hex Value: 4000HSug. Var. Name: FLT_RUN@Access: Read onlyUDC Error Code: 1014LED: N/A



Communication Lost Fault Bit 15

The Communication Lost Fault bit is set if the fiber-optic communication between the PMI Processor and the UDC module is lost due to two consecutive errors of any type.

Hex Value: 8000HSug. Var. Name: FLT_COM@Access: Read onlyUDC Error Code: 1015LED: COMM OK

This bit is set only after communication between the PMI Regulator and UDC module has been established. This bit should be used in the run permissive logic for the drive. Also refer to the CCLK Synchronized bit (register 200/1200, bit 14).

Drive Warning Register 203/1203

The warnings indicated by the Drive Warning register cause no action by themselves. Any resulting action is determined by the application task. The user must ensure that the AutoMax application task monitors register 203/1203 and takes appropriate action if any of these conditions occurs. If a warning condition is detected, the corresponding bit is latched until the Warning Reset bit (bit 9) of the Drive Control register (register 100/1100) is set.

DC Bus Overvoltage Warning Bit 0

The DC Bus Overvoltage Warning bit is set if the DC bus voltage rises above the overvoltage threshold value stored in local tunable OVT_E0%.

Hex Value: 0001HSug. Var. Name: WRN_OV@Access: Read onlyUDC Error Code: N/ALED: N/A

The torque is automatically limited to avoid an overvoltage fault. Bit 4 of the Drive Warning register will also be set to indicate the torque is being limited by the system. Refer to the SA3100 Power Modules instruction manual (S-3058) for more information about internal DC bus control.

DC Bus Undervoltage Warning Bit 1

The DC Bus Undervoltage Warning bit is set if the DC bus voltage drops below the undervoltage threshold stored in local tunable UVT_E0%.

Hex Value: 0002HSug. Var. Name: WRN_UV@Access: Read onlyUDC Error Code: N/ALED: N/A

The torque is automatically limited to avoid an undervoltage fault. Bit 4 of the Drive Warning register will also be set to indicate the torque is being limited by the system. Refer to the SA3100 Power Modules instruction manual (S-3058) for more information about internal DC bus control.


Drive Warning Register 203/1203

Ground Current Warning Bit 2

The Ground Current Warning bit is set if ground current exceeds the ground current level stored in local tunable GIT_E1%.

Hex Value: 0004HSug. Var. Name: WRN_GND@Access: Read onlyUDC Error Code: N/ALED: N/A

Voltage Ripple Warning Bit 3

The Voltage Ripple Warning bit is set if the ripple on the DC bus exceeds the voltage ripple threshold value stored in local tunable VRT_E0%.

Hex Value: 0008HSug. Var. Name: WRN_VR@Access: Read onlyUDC Error Code: N/ALED: N/A

This bit is intended to be used to detect an input phase loss if three-phase AC input is used, but it can also be used for a common bus supply.

Reference In Limit Warning Bit 4

In Vector mode, the Reference in Limit Warning bit is set if the reference to the regulator exceeds the maximum value permitted (+/- 4095) or is being limited by the system in response to an overvoltage or undervoltage warning.

Hex Value: 0010HSug. Var. Name: WRN_RIL@Access: Read onlyUDC Error Code: N/ALED: N/A

In Volts per Hertz mode, this bit is set if current limit is selected and the regulator has detected a specified current output within a specified time limit. The regulator will begin adjusting output frequency to limit current.

This bit is also used by the bridge test to indicate an illegal test code. Refer to the Bridge Test Enable bit (register 100/1100, bit 2) for additional information on the bridge test.

Tuning Aborted Warning Bit 5

The Tuning Aborted Warning bit is set if any of the automatic tuning procedures (e.g., resolver balance and gain calibration) is not successful.

Hex Value: 0020HSug. Var. Name: WRN_TUN@Access: Read onlyUDC Error Code: N/ALED: N/A


Drive Warning Register (Continued) 203/1203

Bit 6


Over Temperature Warning Bit 7

The Over Temperature Warning bit is set if the Power Module’s heatsink reaches a temperature of 90° C.

Hex Value: 0080HSug. Var. Name: WRN_OT@Access: Read onlyUDC Error Code: N/ALED: N/A

Bad Gain Data Warning Bit 8

The Bad Gain Data Warning bit is set if any of the following conditions is detected:

Hex Value: 0100HSug. Var. Name: WRN_BGD@Access: Read onlyUDC Error Code: N/ALED: N/A

• A current minor loop gain variable or a vector algorithm variable has been modified by the user outside of acceptable limits. The invalid value will be ignored by the system and the last acceptable value entered will be used. For a description of the tunable variables, refer to Appendix B.

• Drive parameter(s) have been loaded that are outside of acceptable limits. This is also part of an interlock test that will prevent the drive from entering the run mode. See register 205/1205, bit 0.

• The following relationship between the power loss fault threshold (PLT_E0%), the undervoltage warning threshold (UVT_E0%), and the overvoltage warning threshold (OVT_E0%) is not true: PLT_E0% < UVT_E0% < OVT_E0%.

• OVT_E0% > 986V for 575 VAC Power Modules,> 789V for 460 VAC Power Modules,> 396V for 230 VAC Power Modules.

Thermistor Open Circuit Warning Bit 9

The Thermistor Open Circuit Warning bit is set if an open is detected in the Power Module’s thermistor circuit.

Hex Value: 0200HSug. Var. Name: WRN_TOC@Access: Read onlyUDC Error Code: N/ALED: N/A


Drive Warning Register (Continued) 203/1203

Bit 12


Flex I/O Communication Warning Bit 13

The Flex I/O Communication Warning bit is set if a Flex I/O communication problem is detected and logged in registers 10, 11, 22, or 23. Refer to tables 3.6 and 3.7.

Hex Value: 2000HSug. Var. Name: WRN_FLX@Access: Read onlyUDC Error Code: N/ALED: I/O FLT

CCLK Not Synchronized Warning Bit 14

The CCLK Not Synchronized Warning bit is set if the CCLK counters in the PMI Regulator and the UDC module are momentarily not synchronized.

Hex Value: 4000HSug. Var. Name: WRN_CLK@Access: Read onlyUDC Error Code: N/ALED: N/A

PMI Communication Warning Bit 15

The PMI Communication Warning bit is set if a fiber-optic communication error is detected between the PMI Processor module and the UDC module.

Hex Value: 8000HSug. Var. Name: WRN_COM@Access: Read onlyUDC Error Code: N/ALED: N/A

Communication errors in two consecutive messages will result in a drive fault.

Power Device Status Register 204/1204

The bits in the Power Device Status register indicate the status of the Power Module and its power devices.

Phase U-Upper IOC A Bit 0

The Phase U-Upper IOC A bit is set if an overcurrent is detected in the phase U upper power device.

Hex Value: 0001HSug. Var. Name: U_UPA@Access: Read onlyUDC Error Code: N/ALED: N/A


Power Device Status Register (Continued) 204/1204

Phase V-Upper IOC A Bit 1

The Phase V-Upper IOC A bit is set if an overcurrent is detected in the phase V upper power device.

Hex Value: 0002HSug. Var. Name: V_UPA@Access: Read onlyUDC Error Code: N/ALED: N/A

Phase W-Upper IOC A Bit 2

The Phase W-Upper IOC A bit is set if an overcurrent is detected in the phase W upper power device.

Hex Value: 0004HSug. Var. Name: W_UPA@Access: Read onlyUDC Error Code: N/ALED: N/A

Phase U-Lower IOC A Bit 3

The Phase U-Lower IOC A bit is set if an overcurrent is detected in the phase U lower power device.

Hex Value: 0008HSug. Var. Name: U_LOA@Access: Read onlyUDC Error Code: N/ALED: N/A

Phase V-Lower IOC A Bit 4

The Phase V-Lower IOC A bit is set if an overcurrent is detected in the phase V lower power device.

Hex Value: 0010HSug. Var. Name: V_LOA@Access: Read onlyUDC Error Code: N/ALED: N/A

Phase W-Lower IOC A Bit 5

The Phase W-Lower IOC bit is set if an overcurrent is detected in the phase W lower power device.

Hex Value: 0020HSug. Var. Name: W_LOA@Access: Read onlyUDC Error Code: N/ALED: N/A



Inverter Power Device Fault Bit 6

The Inverter Power Device Fault bit is set if the gate driver turns off an output power device (IGBT) to protect it from an overcurrent.

Bit 3 in register 202 will also be set.

Hex Value: 0040HSug. Var. Name: IPMA@Access: Read onlyUDC Error Code: N/ALED: N/A

If an output short circuit occurs, a high current will flow in the IGBT causing its collector-to-emitter voltage to increase to a level much higher than normal. The gate driver detects this condition and instantly shuts off the IGBT to prevent its destruction.

Bit 7


Bit 8


Bit 12


Bit 13

Reserved for future use.

.

Hex Value: 2000HSug. Var. Name:Access: Read onlyUDC Error Code: N/ALED: N/A



Bit 14


Bit 15


Interlock Register 205/1205

Interlock tests are executed whenever bit 0, 1, 2, or 4 of register 100/1100 is set. The first problem detected will be indicated by the corresponding bit in the Interlock register. Note that these bits will prevent the torque minor loop from running. Refer to the SA3100 Diagnostics, Troubleshooting, and Start-Up Guidelines instruction manual (S-3059) for more information about interlock tests.

Configuration Parameters Not Loaded Bit 0

The Configuration Parameters Not Loaded bit is set if the configuration parameters have not been downloaded into the UDC module from the Programming Executive or if the parameters are outside of acceptable limits.

Hex Value: 0001HSug. Var. Name: IC_CNF@Access: Read onlyUDC Error Code: N/ALED: N/A

Valid Gains Not Loaded Bit 1

The Valid Gains Not Loaded bit is set if the following pre-defined local tunables are zero or if a UDC task containing these variables has not been loaded to the PMI:

Hex Value: 0002HSug. Var. Name: IC_GAIN@Access: Read onlyUDC Error Code: N/ALED: N/A

CML_WC0% FLUX_WCO% GIT_E1% IST_E1%

OVT_E0% PLT_E0% SLIP_ADJ_E3%1 STATOR_IZ_E1%STATOR_T_E4% STATOR_R_E4% UVT_E0%

1. Vector with Constant Power mode only


Interlock Register (Continued) 205/1205

RPI Missing Bit 2

The RPI Missing bit is set if the Run Permissive input on the Resolver & Drive I/O board is not on.

Hex Value: 0004HSug. Var. Name: IC_RPI@Access: Read onlyUDC Error Code: N/ALED: N/A

Faults Need Reset Bit 3

The Faults Need Reset bit is set if previous faults (register 202/1202) have not been cleared.

Hex Value: 0008HSug. Var. Name: IC_FLT@Access: Read onlyUDC Error Code: N/ALED: N/A

Rising Edge Required Bit 4

The Rising Edge Required bit is set if a rising edge is not detected on a command bit in register 100/1100.

Hex Value: 0010HSug. Var. Name: IC_RISE@Access: Read onlyUDC Error Code: N/ALED: N/A

This interlock bit will be set if the application task has set the Fault Reset bit (register 100/1100, bit 8) but has not cleared and then re-enabled any command bits.

More Than One Request Bit 5

The More Than One Request bit is set if more than one operating mode is requested at a time in register 100/1100 (bits 0, 1, 2).

Hex Value: 0020HSug. Var. Name: IC_MORE@Access: Read onlyUDC Error Code: N/ALED: N/A

Bus Not Ready Bit 6

The Bus Not Ready bit is set when turning on the drive if the DC bus is not ready.

Hex Value: 0040HSug. Var. Name: IC_BUS@Access: Read onlyUDC Error Code: N/ALED: N/A

The bus is ready when the DC bus voltage is greater than the undervoltage threshold value stored in local tunable UVT_E0% and has reached a steady state, and feedback indicates that the pre-charge contactor has closed.

This interlock bit will also be set when turning on the drive if the bus enable bit (register 100/1100, bit 4) has not been set. Refer to the SA3100 Power Modules instruction manual (S-3058) for more information about internal DC bus control.


Interlock Register (Continued) 205/1205

MCR Did Not Close Bit 7

The MCR Did Not Close bit is set if the optional output contactor did not close when commanded to do so.

Hex Value: 0080HSug. Var. Name: IC_MCR@Access: Read onlyUDC Error Code: N/ALED: N/A

Bit 8


Bit 9

Reserved for future use.

.

Hex Value: 0200HSug. Var. Name:Access: Read onlyUDC Error Code: N/ALED: N/A

Incompatible Resolver Bit 10

The Incompatible Resolver bit is set if Resolver & Drive I/O boards B/M 60001 or B/M 60001-1 are detected in the PMI Regulator.

Hex Value: 0400HSug. Var. Name: IC_IRES@Access: Read onlyUDC Error Code: N/ALED: N/A

DC Bus Voltage (Volts) Register 206/1206

The DC Bus Voltage (Volts) register contains the voltage of the DC bus. It is scaled in units of volts.

Sug. Var. Name: BUS_VDC%Units: VoltsRange: N/AAccess: Read only

DC Bus Current (Amps) Register 207/1207

The DC Bus Current (Amps) register contains the measured current in the DC bus. The value is scaled in amps times 10. For example, 50.1 amps would be represented as 501.

Sug. Var. Name: BUS_IDC%Units: Amps ∗ 10Range: N/AAccess: Read only


Ground Current Feedback (Amps) Register 208/1208

The Ground Current Feedback (Amps) register contains the measured RMS ground current. This value is scaled in amps times 10. For example, 50.1 amps would be represented as 501.

Sug. Var. Name: GI_FB%Units: Amps ∗ 10Range: N/AAccess: Read only

Voltage Feedback (Volts RMS) Register 209/1209

In Vector mode, the Voltage Feedback (Volts RMS) register contains the measured RMS motor voltage scaled in volts.

In Volts per Hertz mode, this register contains the fundamental frequency RMS volts.

Sug. Var. Name: V_FB%Units: RMS voltsRange: N/AAccess: Read only

Current Feedback (Amps RMS) Register 210/1210

The Current Feedback (Amps RMS) register contains the measured RMS motor current. This value is scaled in amps times 10. For example, 50.1 amps would be represented as 501.

Sug. Var. Name: I_FB%Units: Amps ∗ 10Range: N/AAccess: Read only

Current Feedback Normalized Register (Vector) 211/1211

In Vector mode, register 211/1211 functions as the Current Feedback Normalized register. This register contains the measured RMS motor current. The data is normalized so that +/- 4095 counts is equal to the rated motor current times the motor overload ratio.

Sug. Var. Name: I_FBN%Units: CountsRange: +/- 4095Access: Read only

This register is used as the I_FDBK parameter in the THERMAL OVERLOAD control block used in DPS drives to monitor the motor for thermal overload.

Volt Command Register (V/Hz) 211/1211

In Volts per Hertz mode, register 211/1211 functions as the Volt Command feedback register. This register contains the commanded voltage (fundamental frequency, RMS volts). The value is scaled in volts.

Sug. Var. Name: V_CMD%Units: RMS voltsRange:Access: Read only

Id Feedback Normalized Register (Vector) 212/1212

In Vector mode, register 212/1212 functions as the Id Feedback Normalized register. This register contains the Id component (magnetizing current) of the current feedback. The data is normalized so that 4095 counts is equal to the full value of magnetizing current (STATOR_IZ_E1%).

Sug. Var. Name: ID_FBN%Units: CountsRange: 0 to 4095Access: Read only


Iq Feedback Normalized Register (Vector) 213/1213

In Vector mode, register 213/1213 functions as Iq Feedback Normalized register. This register contains the Iq (torque producing) component of the current feedback. The data is normalized so that +/- 4095 counts corresponds to the torque reference (TRQ_REF%).

Sug. Var. Name: IQ_FBN%Units: CountsRange: +/- 4095Access: Read only

Output Frequency Register (V/Hz) 212/1212 and 213/1213

In Volts per Hertz mode, registers 212/1212 and 213/1213 function as the Output Frequency register. This double precision register contains the output frequency value of the drive. Register 212/1212 holds the high word. Register 213/1213 holds the low word. The value is scaled in Hz ∗ 1000.

Sug. Var. Name: F_CMD!Units: Hz ∗ 1000Range: 0 to 600,000Access: Read only

User Analog Input Register 214/1214

The User Analog Input register contains the measured user analog input value from the Resolver Feedback connector on the Resolver & Drive I/O board.

Sug. Var. Name: ANA_IN%Units: Counts (Volts)Range: -2048 to +2047

(-10V to +10V)Access: Read only

Resolver Scan Position Register 215/1215

The Resolver Scan Position register contains the electrical position of the resolver at the beginning of the UDC task scan. This register is reset to zero at power-up.

Sug. V ar. Name: RES_SCN_POS%Units: CountsRange: -32768 to +32767Access: Read only

Resolver Strobe Position Register 216/1216

The Resolver Strobe Position register contains the electrical position of the resolver at the time a strobe signal is detected.

Sug. Var. Name: RES_STR_POS%Units: CountsRange: -32768 to +32767Access: Read only

Current Feedback Normalized Register (V/Hz) 216/1216

In Volts per Hertz mode, register 216/1216 functions as the Current Feedback Normalized register. This register contains the measured RMS motor current. The data is normalized so that +/- 4095 counts is equal to the rated motor current times the motor overload ratio.

Sug. Var. Name: I_FBN%Units: CountsRange: +/- 4095Access: Read only

This register is used as the I_FDBK parameter in the THERMAL OVERLOAD control block used in DPS drives to monitor the motor for thermal overload.

Note that the regulator uses a value of 150% overload for this function. If another value of overload ratio is desired, it must be communicated to the regulator via the dual port register 711/1711.


Revolutions Per Minute Register 217/1217

The Revolutions Per Minute register contains the speed of the motor in RPM. A positive number in this register indicates a forward direction; a negative number indicates a reverse direction.

Sug. Var. Name: RPM%Units: RPMRange: N/AAccess: Read only

Note that this register is not intended for closed loop control.

Slip Feedback Register (Vector) 218/1218

In Vector mode, register 218/1218 functions as the Slip Feedback register. This register displays the amount of rotor slip. The displayed value is equal to Hertz times 100. For example, 5 Hz would be displayed as 500.

Sug. Var. Name: SLIP_FB%Units: Hz ∗ 100Range: N/AAccess: Read only

Carrier Frequency Register (V/Hz) 218/1218

In Volts per Hertz mode, register 218/1218 functions as the Carrier Frequency register. This register contains the drive’s present carrier frequency. The value is scaled in kHz ∗ 10.

Sug. Var. Name: CARR_FB%Units: kHz ∗ 10Range: N/AAccess: Read only

Selected Variable Register 219/1219

The Selected Variable register contains the value of the variable that is selected for display on PMI meter port 4.

Sug. Var. Name: SEL_VAR%Units: N/ARange: N/AAccess: Read only

This register provides monitoring of data in the UDC module that is normally only available within the PMI regulator. Refer to chapter 2 for more information on displaying variables on the PMI Regulator’s meter ports.

(Unused) 220/1220

Reserved for future use Sug. Var. Name:Units:Range:Access:

(Unused) 221/1221

Reserved for future use Sug. Var. Name:Units:Range:Access:


AC Power Technology Calibration and Power-Up Faults:

If any of the following calibration and power-up diagnostic faults occurs, replace the PMI Regulator motherboard. These faults indicate a hardware failure of the AC power technology circuit on the motherboard. Register 202, bit 11 (FLT_PTM@) will be set.

Run Time AC Power Technology Hardware Faults:

Diagnostic Fault Code Register 222/1222

The Diagnostic Fault Code register displays an error code to help diagnose the cause of a problem reported in other registers.

Note that this register is available for monitoring only. It cannot be referenced in an application task.

Sug. Var. Name: DIAG_FLT%Units: N/ARange: N/AAccess: Read only

Code Fault

1 D/A high voltage error (+3.3V 10% out of tolerance)

2 D/A low voltage error (-3.3V 10% out of tolerance)

3 Torque current loop proportional gain not within calibration limits (14<g<30)

4 Flux current loop proportional gain not within calibration limits (14<g<30)

5 Flux current loop integrator time constant not within calibrated limits

6 Torque current loop integrator time constant not within calibrated limits

7 Modulation index error

8 Harmonic DAC limit error

9 Modulation range error

10 Harmonic DAC range error

11 Programmable current limit or the ground fault limit fault

12 Voltage feedback integrator error

13 A/D converter interrupt error

14 Pulse Width Modulator frequency error

15 DC bus current not zero at power-up.

16 Phase U current not zero at power-up.

17 Phase W current not zero at power-up.

Code Fault Description/Action

20 Power supply monitor trip AC power technology power supply level out of tolerance. Replace the PMI Regulator motherboard and/or power supply.

21 AC power technology watchdog time-out

AC power technology circuit watchdog timer expired. Replace the PMI Regulator motherboard.


Run Time AC Power Technology Hardware Faults (Continued):

DC Bus Pre-charge Faults:

Diagnostic Fault Code Register (Continued) 222/1222


22 A/D interrupt overrun An interrupt from the power technology circuit was detected before the previous interrupt was processed. Replace the PMI Regulator motherboard.

23 Gate power test 1 fault Gate power is on when the MCR is off and Gate Enable is on. Replace the PMI Regulator motherboard.

24 Not used.

25 Gate power test 3 fault Gate power is on when the MCR is off and Gate Enable is on. Replace the PMI Regulator motherboard.

26 Gate power loss Loss of gate power feedback while in run. Replace the PMI Regulator motherboard.


100 Pre-charge closed Pre-charge is requested to close when Pre-charge is already closed.

101 Pre-charge did not close The pre-charge did not close within 2 seconds.

102 Pre-charge open Pre-charge is closed but AC power technology status indicates it is open.

103 Pre-charge did not open Pre-charge is commanded to open but does not do so after one second.

104 Pre-charge opened The AC power technology circuit detected that the pre-charge opened while in run.

105 No used

106 Charge time-out Minimum bus voltage is not detected within 10 seconds after bus enable.

107 AC line fault AC line status from Power Module not detected.

108 Charge ripple fault DC ripple voltage above tolerance.

200 Diag_12V PS Isolated 12V power supply is out of tolerance.

201 Diag_PS_Ext_PS External ±15V power supply (for G or H-frame units) is out of tolerance.


3.6 Application Registers (Registers 300-599, Every Scan) (Registers 1300-1599, Every Nth Scan)

The application registers are used to pass application-specific data between the AutoMax Processor and the UDC module.

Memory is allocated for a maximum of 600 application registers. There are 300 registers that can be used every scan (registers 300-599) and 300 registers that can be used every Nth scan (registers 1300-1599). “N” is defined in register 2001. Note that the status of application registers is not retained after a STOP ALL.

Application registers 300-599 can be used every scan of UDC tasks. Registers within this range written to by a UDC task are updated by the UDC operating system from its local memory to dual port memory after each task is run. Registers within this range written to by an AutoMax task are read by the UDC operating system from dual port memory and copied into the UDC local memory at the beginning of each scan in order to have a consistent context for evaluation. See figure 3.1.

Note that the same bits or registers must not be written to (and used as outputs) by both an AutoMax task and a UDC task.

Application registers 1300-1599 can be used every Nth scan of the UDC task. Nth scan registers should be used when it is necessary to synchronize one or more UDC tasks to an AutoMax task.

The registers within this range (1300-1599) that are written to by a UDC task are updated by the UDC operating system from its local memory to dual port memory at the end of the scan that occurs before the Nth scan (N-1). At that time, an interrupt will be generated by the UDC operating system to indicate that new data has been written to the dual port memory. Refer to the 2000-series registers for more information on interrupts. An AutoMax task must have defined a hardware EVENT in order to be able

Figure 3.1 – UDC Task Scan

Input A Run A Output A Input B Run B Output B

UDC Scan*

Feedback F

rom P

MI

Com

mand to P

MI

*Task B can act on Task A outputs within a scan.

Latch “every scan”registers that areinputs to task B

Write “every scan”registers that areoutputs from task A

Latch “every scan”registers that areinputs to task A

Write “every scan”registers that areoutputs from task B


to respond to an interrupt from the UDC module. Registers within this range that are written to by an AutoMax task are read by the UDC operating system from dual port memory and copied into the UDC local memory at the beginning of the Nth scan. See figure 3.2.

The following data types can be defined in the application register area: boolean (bit), integer (16 bits), double integer (32 bits), and real (32 bits). Because of the way in which read and write operations occur in the UDC dual port memory, however, the programmer must assign boolean variables carefully within pairs of 16-bit registers.

The UDC operating system generally operates on the amount of memory called for by the data type, e.g., when it is requested to write to a 16-bit (integer) value, it writes only to those specific 16 bits. However, in the case of boolean variables, the UDC operating system always operates on 32 bits at a time. It is not possible for the operating system to write to only one bit within a register. The remaining 31 bits in the register pair will be written over as well, possibly resulting in corrupted data.

Within any pair of 16-bit registers beginning on an even number boundary, i.e., registers 300 and 301, 302 and 303 (but not registers 301 and 302), all boolean variables must be either inputs or outputs. If there are no bits assigned within a particular register pair, then one 16-bit register can be an output and the other 16-bit register can be an input, or both can be inputs or outputs. Alternatively, the entire register pair can be defined as a real or double integer value.

Note that if you are referencing a 32-bit value (real or double integer) in the UDC dual port from an AutoMax task, the operation is being performed by the AutoMax Processor, which operates on 16 bits of data at a time. In such a situation, you must employ some form of software handshaking in the AutoMax task to ensure that both the upper and lower order 16 bits represent the current value of the variable. This is required for 32-bit values in the “every” scan register range. The handshaking can be done by using software “flags” to indicate that data can be read. It is also possible to read the data multiple times (typically three times) and compare the values.

!ATTENTION: If you use double integer variables, you must implement a software handshake between the transmitter and the receiver to ensure that both the least significant and the most significant 16 bits have been transmitted before they are read by the receiving application program. Failure to observe this precaution could result in bodily injury or damage to equipment.


Figure 3.2 – Nth Scan Interrupts

Latc

h “e

very

sca

n"

Out

put B

Inpu

t AR

un A

Out

putA

Inpu

t BR

un B

Sca

n 1

Sca

n 2

Sca

n 3

Sca

n 4

Sca

n 5

Sca

n N

(n-1

)

Out

put B

Inpu

t AR

un A

Out

putA

Inpu

t BR

un B

Latc

h N

th s

can

regi

ster

s th

at a

rein

puts

to b

oth

task

s A

and

B.

UD

C o

pera

ting

syst

em g

ener

ates

inte

rrup

t to

Aut

oMax

Pro

cess

or.

Latc

h “e

very

sca

n” r

egis

ters

use

das

inpu

ts to

task

A

Writ

e “e

very

sca

n” r

egis

ters

that

are

out

puts

from

task

A

Latc

h “e

very

sca

n”re

gist

ers

that

are

inpu

ts to

task

B.

Writ

e “e

very

scan

” re

gist

ers

that

are

ou

tput

s fr

omta

sk B

.

Writ

e “e

very

scan

" re

gist

ers

that

are

ou

tput

s fr

omta

sk B

.

Latc

h “e

very

sca

n" r

egis

ters

that

are

inpu

ts to

task

A

Writ

e “e

very

sca

n" r

egis

ters

that

are

out

puts

from

task

A

regi

ster

s th

at a

rein

puts

to ta

sk B

Writ

e “N

th s

can"

reg

iste

rsth

at a

re o

utpu

ts fr

om b

oth

task

s A

and

B

Sca

n 5

(n-1

)S

can

6(N

th s

can)

Zoo

m in

Zoo

m in

Val

ue in

sca

ns p

er in

terr

upt r

egis

ter

= 6

Sca

n 2

Sca

n 3

Sca

n 4

Sca

n 1

UD

C M

odul

e

Aut

oMax

Pro

cess

or w

ith T

ask

Ser

vici

ngIn

terr

upts

from

UD

C m

odul

e.

Aut

oMax

Pro

cess

or T

ask*

*S

ervi

cing

UD

C in

terr

upt

*CC

LK is

turn

ed o

n in

the

Aut

oMax

rac

k by

the

Aut

oMax

task

.**

As

long

as

this

Aut

oMax

task

can

exe

cute

in th

e in

terv

al b

etw

een

UD

C u

pdat

es (

and

inte

rrup

ts, i

n th

is c

ase)

ther

e w

ill b

e no

task

ove

rlap

in th

e A

utoM

ax P

roce

ssor

.


3.7 UDC Module Test I/O Registers (Registers 1000-1017)

This view is used to configure the UDC module’s Test Switch Inputs Register and the Meter Port Setup Registers.

3.7.1 UDC Module Test Switch Inputs Register (Register 1000)

This view is used to configure the register that displays the status of the test switches and LED indicators on the UDC module. Writing to this register will not change the state of the LEDs. The status of this register is retained during a Stop All.

UDC Test Switch Inputs Register 1000

Pushbutton Input Bit 0

The Pushbutton Input bit is on when the UDC’s pushbutton is pressed.

Hex Value: 0001HSug. Var. Name: UDC_PB@Access: Read onlyUDC Error Code: N/ALED: N/A

Switch Up Input Bit 1

The Switch Up Input bit is on when the test switch is in the up position.

Hex Value: 0002HSug. Var. Name: SWIT_UP@Access: Read onlyUDC Error Code: N/ALED: N/A

Switch Down Input Bit 2

The Switch Down Input bit is on when the test switch is in the up position.

Hex Value: 0004HSug. Var. Name: SWIT_DN@Access: Read onlyUDC Error Code: N/ALED: N/A

Operating System OK LED Bit 8

The Operating System OK LED bit shows the status of the Operating System OK LED on the UDC module ( 0 = OFF; 1 = ON).

Hex Value: 0100HSug. Var. Name: N/AAccess: Read onlyUDC Error Code: N/ALED: OS OK on UDC

module


UDC Test Switch Inputs Register (Continued) 1000

COMM A OK LED Bit 9

The COMM A OK LED bit shows the status of the COMM A OK LED on the UDC module ( 0 = OFF; 1 = ON).

Hex Value: 0200HSug. Var. Name: N/AAccess: Read onlyUDC Error Code: N/ALED: COMM A OK

on UDC module

Drive A Fault LED Bit 10

The Drive A Fault LED bit shows the status of the Drive A Fault LED on the UDC module ( 0 = OFF; 1 = ON).

Hex Value: 0400HSug. Var. Name: N/AAccess: Read onlyUDC Error Code: N/ALED: DRV A FLT

on UDC module

COMM B OK LED Bit 11

The COMM B OK LED bit shows the status of the COMM B OK LED on the UDC module ( 0 = OFF; 1 = ON).

Hex Value: 0800HSug. Var. Name: N/AAccess: Read onlyUDC Error Code: N/ALED: COMM B OK

on UDC module

Drive B Fault LED Bit 12

The Drive B Fault LED bit shows the status of the Drive B Fault LED on the UDC module ( 0 = OFF; 1 = ON).

Hex Value: 1000HSug. Var. Name: N/AAccess: Read onlyUDC Error Code: N/ALED: DRV B FLT

on UDC module


3.7.2 UDC Module Meter Port Setup Registers (Registers 1000-1017)

Registers 1001-1017 are used to configure the UDC module’s meter ports. This configuration determines what variables from the UDC module’s dual port memory are to be displayed on the meter ports at the end of the UDC scan. At system power-up, the output values of the ports are reset to zero.

To map a UDC variable to a specific meter port at power-up, refer to table 3.8 and use the following procedure. Note that the setup register configurations are retained during a Stop All.

For each meter port:

Step 1. Place the register number of the variable you wish to display in the appropriate Variable Register Number register.

Step 2. If an individual bit of the register is to be displayed, enter it in the Bit Number register as 100 (bit 00) to 115 (bit 15).

Step 3. Place the value (maximum 32767) that will represent +10V in the Maximum Value register.

Step 4. Place the value (minimum -32768) that will represent -10V in the Minimum Value register.

Step 5. Set register 1001 (Initiate Change in Setup) equal to a non-zero value to store the new setup register configurations in memory.

The UDC module’s meter ports are updated once per scan once the UDC task is running and CCLK is on. They are updated every 5 milliseconds when CCLK is off.

UDC meter ports can also be set up on-line using the “Setup UDC” selection from the Monitor menu as described in the AutoMax Programming Executive instruction manual. This setup is valid only until there is a power cycle, in which case the meter ports default to outputting zero voltage and the UDC Setup screen is cleared on power-up.

Refer to the UDC module instruction manual (S-3007) for more information about the UDC module’s meter ports.

Table 3.8 – UDC Module Meter Port Setup Registers

UDC Module Meter PortSetup Registers

MeterPort 1

MeterPort 2

MeterPort 3

MeterPort 4

Change Setup Register 1001 1001 1001 1001

Variable Register Number Register 1002 1006 1010 1014

Bit Number Register 1003 1007 1011 1015

Maximum Value Register 1004 1008 1012 1016

Minimum Value Register 1005 1009 1013 1017


3.7.2.1 Resolution of Meter Port Data

For meter ports, the output values will be clamped at the outside (+/-10V) limits. Note that if you select to display a data range that is narrower than the actual range of the data, your output values will not change until the value returns to within the range you selected to display. In other words, data is being updated at the rate described above, but the actual output voltage may not change.

If the actual data being sent to the meter port is significantly smaller than the upper and lower limits assigned by the programmer, the effective resolution of the 8-bit D/A circuit (1 part in 255) will degrade. To calculate the step change indicated on the meter port, calculate the sum or the absolute values of the upper and lower limits (the entire range of possible values) assigned to the port. Then scale this number by 255 in order to determine the minimum step change that will cause the D/A output to change.

For example, suppose the programmer sets the +10V and -10V limits at +4095 and -4095, respectively, but the actual value varies only between +1024 and -1024. Then:

8190/255 = 32 counts

This means that although the actual data is being updated, the meter port output will change only when the data changes by 32 or more counts. This level of granularity might be acceptable if the range of the data were actually 8190 counts, but might not be acceptable if the data range is only 4095 counts. If the programmer had assigned the limits +/- 1024, the D/A output step change would be only 8 counts: 2048/255 = 8.

Initiate Change in Setup Register 1001

Set this register equal to a non-zero value to store the new setup register configurations in UDC memory. You must use this register whether you are changing the meter port setup via an application task or via I/O Monitor.

Sug. Var. Name: N/AUnits: N/ARange: N/AAccess: Read/Write


Meter Port 1

UDC Module Meter Port 1 Register Number Register 1002

UDC register number (0 - 2044) to be mapped to meter port 1. Sug. Var. Name: N/AUnits: N/ARange: N/AAccess: Read/Write

UDC Module Meter Port 1 Bit Number Register 1003

Bit number of the UDC register specified in register 1002 that is to be mapped to port 1. Enter a value of 100 (bit 00) to 115 (bit 15) as required. Enter a value of zero if all of the register’s bits are to be displayed.


UDC Module Meter Port 1 Maximum Value Register 1004

Set this register to the number that will represent +10V. The maximum allowable value is 32767.


UDC Module Meter Port 1 Minimum Value Register 1005

Set this register equal to the number that will represent -10V. The minimum allowable value is -32768.



Meter Port 2













Meter Port 3













Meter Port 4













3.8 Interrupt Status and Control Registers (Registers 2000-2047)

This view is used to configure registers that control the operation of interrupts to a task on an AutoMax Processor in the rack and to enable CCLK in the rack. These registers are used for Drive A and B. Only one UDC task should write to these registers. Note that the status of these registers is not retained after a Stop All.

Interrupt Status Control Register 2000

The Interrupt Status Control register contains the following information. Only bit 6 can be written to by the user. All other bits are read only.

Sug. Var. Name: UDC_ISCR%Units: N/ARange: N/AAccess: See individual

bits

Interrupt Line Identification Bit 0


Interrupt Line Identification Bit 1


Interrupt Allocated Bit 2


Interrupt Generated This Scan Bit 4



Interrupt Status Control Registers (Continued) 2000

CCLK Counting Bit 5


Enable CCLK on the Multibus Backplane Bit 6

CCLK must be enabled in the rack for the UDC module to execute its task(s) and communicate synchronously with the PMI.

Hex Value: 0001HSug. Var. Name: N/AAccess: Read/WriteUDC Error Code: N/ALED: N/A

Only one module per rack should enable CCLK. If CCLK is enabled on multiple modules in the rack, an overlap error will result (error code 38). Other modules that can enable CCLK include the M/N 57C409, 57C421, and the 57C411.

The UDC module uses CCLK to determine when it should run its tasks. CCLK is also used as the time reference for all UDC modules in the rack so that they are all synchronized to start at specific time periods. If interrupts to the AutoMax Processor are required, register 2001 must be set to the desired value before CCLK is enabled.

Interrupt Enabled Bit 7

The Interrupt Enabled bit, when set by the operating system, indicates that a hardware EVENT has been defined in an AutoMax task.


No other programming is required for the UDC operating system to generate an interrupt in the interval defined in register 2001.

Interrupt Status Bit 15

The Interrupt Status bit is set to indicate that an interrupt is being generated at this time.



Scans Per Interrupt Register 2001

The Scans Per Interrupt register contains the number of times a UDC task is to be scanned between updates of the Nth scan application registers.

Sug. Var. Name: SPI%Units: N/ARange: See below.Access: Read/Write

Note that you must write the desired value to this register before you turn on CCLK. The default value is zero (i.e., not applicable because an interrupt is not being used but is updated each scan). One is a permissible value. If a hardware EVENT is defined in an AutoMax application task, this register will also specify when the interrupt occurs, i.e., every Nth scan. See chapter 4 for more information on interrupts.


CHAPTER 4Application Programming

for DPS Drive Control

Distributed Power Drive products are sold only as part of engineered systems. The application programming required for each engineered system is developed in response to each customer’s specifications. Information in this chapter is general enough to apply to most engineered systems; however, implementation details may vary. Always refer to your wiring diagrams for specific information about your engineered system.

4.1 AutoMax Tasks

AutoMax tasks are used to implement safety interlocks, coordinate multiple UDCs, and collect data from UDC modules in the rack. They can access all common memory and I/O in the AutoMax rack, including the dual port memory in the UDC module. AutoMax drive control tasks are generally written in control blocks and PC/Ladder Logic language. Typically these tasks control the Drive Control register (100/1100) and the I/O Control register (101/1101). AutoMax tasks can access registers in the UDC’s dual port memory in the same way as tasks on the UDC module itself, i.e., by declaring them COMMON.

4.2 UDC Tasks

UDC tasks operate on registers in the UDC dual port memory described in chapter 3, as well as on local task-specific variables in order to control some application variable (e.g., speed) and to calculate the required reference values for the selected control algorithm. The UDC task is sometimes referred to as an “outer” or “major” control loop. Note, however, that there may be more than one outer loop per task. In this case the control loops are nested, or “cascaded,” within the UDC task.


ATTENTION:Only qualified Rockwell personnel or other trained personnel who understand the potential hazards involved may make modifications to the application tasks. Any modifications may result in uncontrolled machine operation. Failure to observe this precaution could result in damage to equipment and bodily injury.

Application Programming for DPS Drive Control 4-1

UDC tasks must be written in the Control Block language, a language designed specifically for drive control. To differentiate them from Control Block tasks written for AutoMax Processors, they must be specified as UDC tasks in the Programming Executive software. Like Control Block tasks on AutoMax Processors, UDC tasks can include a number of BASIC language statements and functions; however, those that allow task suspension or delay are not supported.

UDC tasks are created, compiled, loaded, and monitored in the same way as Control Block tasks for AutoMax Processors. UDC task variables can be monitored, set, tuned, and forced like AutoMax task variables. Note that the UDC module is accessed for monitoring and loading through the serial port on the leftmost AutoMax Processor (or over the DCS-NET network), which is used for all connections to the rack.

Any UDC dual port register that is to be used in a UDC task must be defined as COMMON in the task. Recall that UDC dual port memory registers are either reserved for a specific use such as Flex I/O data or available for application-specific purposes to the programmer. Registers that are not specifically identified in one of these two ways in the Programming Executive software or in this instruction manual must not be written to by either the UDC or AutoMax tasks because they are being used by the operating system.

Generally, the common variables on the UDC module are either written to only by AutoMax tasks (“read only” to UDC tasks), or they are written to only by a UDC task (“read only” to AutoMax tasks). The former are typically variables that control an action, e.g., requesting the minor loop to run, and the latter are typically status variables, e.g., indicating the status of the fiber-optic communication link.

UDC tasks can access only the UDC module’s own dual port memory. They cannot access other variables in the rack unless an AutoMax task writes those variable values to the application-specific registers in the UDC dual port.

Figure 4.1 illustrates one UDC task scan..

Figure 4.1 – UDC Task Scan

Input A Run A Output A Input B Run B Output B

UDC Scan*

Feedback F

rom P

MI

Com

mand to P

MI

*Task B can act on Task A outputs within a scan.

Latch “every scan”registers that areinputs to task B

Write “every scan”registers that areoutputs from task A

Latch “every scan”registers that areinputs to task A

Write “every scan”registers that areoutputs from task B


All common input values for the UDC task are first read from the dual port memory and then stored in a local buffer in order to have a consistent context for evaluation. The task is then executed. After the task has been executed, the common output values from the UDC task are written from the local memory buffer to dual port memory.

The only exception to this pattern are the common variables in the “Nth” scan application register area. These registers are updated immediately before every “Nth” scan only, as defined by the user. See section 4.3 and figure 4.3 for more information on “Nth” scan interrupts. See section 4.2.3 for more information on the command and feedback messages.

4.2.1 Typical Structure of a UDC Task

They typical structure of a UDC task is described in the following paragraphs. The first part of the task, described in steps 1 to 4 below, is considered task initialization. This part of the task will only run on the initial scan of the task or on any subsequent re-start.

Step 1. Local and common variable definitions

This section of the task defines names for values internal to the task (LOCALs) and all UDC dual port memory registers used in the task (COMMONs).

Step 2. Pre-defined local tunable variable definitions

This section defines the variables that are used by the PMI for functions such as tuning the control algorithm and calibrating the resolver. The UDC task “skeleton” file in the Programming Executive software includes these local tunable definitions. See section 4.2 and Appendix B for more information.

Step 3. Initialization

a. UDC Meter port set-up: The registers whose values will be output on the UDC Meter Ports are defined here. These registers can also be defined on-line using the Programming Executive software (optional).

b. Scans per update definition: The scans-per-update register (2001 for both drive A and B) is defined to tell the UDC Processor when to update the Nth scan registers, and optionally, also when to interrupt an AutoMax Processor task that has defined a hardware EVENT tied to the UDC’s interrupt register. The AutoMax task can then read from and write to the UDC dual port memory registers, and coordinate with the other tasks in the system (optional).

c. Any other initialization required for the application.

This portion of the task (steps 1 to 3), before the SCAN_LOOP block, only executes the first time that the task is scanned, after a STOP ALL command and subsequent Run command, or after power is recycled to the rack.


Step 4. SCAN_LOOP block/Enabling CCLK

This control block tells the UDC operating system how often to execute the task based on the constant clock (CCLK) signal on the rack backplane. Note that the CCLK signal must be enabled by a task in the rack before any UDC tasks in the rack can be scanned beyond their SCAN_LOOP blocks. Note that CCLK must be enabled again after a STOP ALL in the rack. CCLK is enabled by setting the appropriate “CCLK enable” bit on certain modules in the rack, such as the UDC module, CCLK must be enabled on one module only. If CCLK is enabled on multiple modules in the rack, an overlap error will result (error code 38).

The UDC task runs based on “ticks;” one tick is equal to one 500 ) CCLK interval. The value can range from 1 to 20 ticks.

The programmer must specify how often the task should run in the TICKS parameter of the SCAN_LOOP block in the task itself. The TICKS value represents the number of 500 will occur. In order to calculate this value, both drive A and drive B tasks must be considered together because they execute one immediately following he other (A, then B). See figure 4.1 for more information.

When determining the value to enter, the programmer must consider how long it will take both tasks to actually run, allow some time for processing overhead, and use the resulting value to determine the TICKS value for the SCAN_LOOP block in both the drive A and drive B tasks. The AutoMax Control Block Language manual (J-3676) lists the execution times of the Control Blocks.

For example, if the programmer assigns UDC task A a TICKS parameter of 8 (4 msec), then UDC task B must also have TICKS defined at 8, and both tasks must be able to execute within an 8 tick window of time, or an overlap error will result and all tasks in the rack will stop. If the tick rates do not match, error code 956 will be reported for one or both tasks in the error log; and all tasks in the rack will be stopped.

Note that, unlike Control Block tasks on AutoMax Processors, UDC tasks cannot run on a hardware or software event basis. The EVENT parameter cannot be specified in the SCAN_LOOP block in UDC tasks. This means that there is no time-out for execution of the UDC tasks. If the UDC task is scanned to the SCAN_LOOP block and CCLK is not on, the task will simply wait without timing out.

Note that no other control blocks are permitted before the SCAN_LOOP block. BASIC statements, however, are permitted before the SCAN_LOOP block.

Step 5. Other Control Block and BASIC statements or functions

This portion of the task consists of the logic specifically required for the application. This portion of the UDC task (after the SCAN_LOOP block) is the only part of the task that executes after the initial scan of the task, after a STOP ALL command and subsequent Run command, or after power is cycled to the rack.


Step 6. Motor thermal overload protection

Electronic thermal overload protection for SA3100 drives is normally provided by the THERMAL OVERLOAD block. The following briefly describes how the THERMAL OVERLOAD block works, how to program the block, and what adjustments are possible. Each UDC task must contain a THERMAL OVERLOAD block, unless motor thermal overload protection is provided by a hardware device. See J-3676, the Control Block Language instruction manual, for the structure of the block.

The THERMAL OVERLOAD control block is used to create a model of the temperature in a single device, such as a motor or power module, controlled by a DPS drive and to turn on an alarm when an overload condition exists. The block calculates a rise in temperature based on current feedback. When operating above 100%, if the rise in temperature exceeds the programmed limit, the OVERLOAD output will turn on. After the overload condition is detected, the rise in temperature must return to the 100% or less condition before the drive will be allowed to turn on again.

The operation of the block is programmed through four block input parameters: LIM_BAR, THRESHOLD, TRIP_TIME, and I_FDBK. The value used for LIM_BAR must be the same value entered as the motor overload ratio during drive parameter configuration. The value used for THRESHOLD selects the percent of full load current at which overload is detected. The value used for TRIP_TIME selects the time, in seconds, within which the block must detect an overload after a step from 100% current to LIM_BAR. The main input to the THERMAL OVERLOAD block is I_FDBK. I_FDBK represents current feedback from the PMI in counts (register 211/1211), scaled so that LIM_BAR is 4095 counts.

The main output from the block is OVERLOAD. This boolean block will be turned on when a thermal overload is detected. The OVERLOAD output must be programmed in a Ladder Logic task to turn off the drive when the fault is detected. The block also has an output called CALC_RISE. Current feedback is squared, scaled, passed through a Lag filter, and then written to CALC_RISE.

!ATTENTION:Electronic motor overload protection must be provided for each motor in a Distributed Power Drive application to protect the motor against excessive heat caused by high currents. This protection can be provided by either the THERMAL OVERLOAD software block or an external hardware device. Applications in which a single power module is controlling multiple motors cannot use the THERMAL OVERLOAD software block and must use an external hardware device or devices to provide this protection. Failure to observe this precaution could result in damage to, or destruction of, the equipment.


Consider an example in which LIM_BAR is defined to be 150% of full load current, THRESHOLD is 114%, and TRIP_TIME is 60 seconds. When I_FDBK is at 100%, CALC_RISE will reach a steady state value of 1000

(1002 / 10). With THRESHOLD at 114%, the trip point for CALC_RISE will

be 1300 (1142 / 10). If I_FDBK is at steady state (100%) and then is stepped to 150%, CALC_RISE will integrate up to 1300 in 60 seconds and OVERLOAD will turn on. The OVERLOAD output will stay on until the rise decays to less than 1000. If I_FDBK remains less than 114%, CALC_RISE will remain less than 1300 and OVERLOAD will not turn on.

The rate at which the CALC_RISE block parameter counts up and down is calculated so that a step from 100% to LIM_BAR will turn on the OVERLOAD in TRIP_TIME seconds. If current feedback steps from 100% to a value less than current limit, it will take longer to detect the overload. If I_FDBK is stepped from zero to LIM_BAR, the block will take approximately four times the value of TRIP_TIME to detect the overload.

UL 508C section 56.1.3 specifies that when subjected to 200% of rated full load motor current, the overload protection must trip in at least eight (8) minutes. Because TRIP_TIME is calibrated from 100% to current limit, and TRIP_TIME from zero to current limit is approximately four times longer, the maximum trip time that is allowed is 2 minutes (120 seconds). To meet UL listing requirements, any value greater than 120 seconds is internally limited to 120 seconds.

The National Electric Code (430-32; 1993) requires that thermal overloads protecting motors having a 1.0 service factor trip at load currents no greater than 115% of full load. To meet NEC requirements, the THRESHOLD block parameter has a default value of 114% and should not be set higher.

4.2.2 Local Tunable Variables

A set of local tunable variables with reserved (pre-defined) names is used to store different types of values for use in drive control. For a description of the local tunable variables used in SA3100 drives, refer to Appendix B.

All pre-defined local tunables must be defined in each UDC task (using the BASIC language LOCAL statement) in order for the task to be loaded onto the UDC module. Although all of these variables are not necessarily used in the UDC task itself, they must be defined there in order to provide a mechanism for passing the values between the UDC module and the PMI. For convenience, all these variables are already defined in the UDC task “skeleton” file in the AutoMax Programming Executive, with “HIGH,” “LOW,” “STEP,” and “CURRENT” values.

Your application task must define these variables using the same “HIGH,” “LOW,” and “STEP” limit values as the ones found in the skeleton task. Note that you can only change the “CURRENT” value in the application task. If the UDC operating system needs to clamp a value at the higher or lower limit, it changes the actual value in the task and writes error code 958 into the error log for the task.

The local tunable values can be modified through the application task on the UDC module and by the operator using the Monitor function. See the BASIC language instruction manual, J-3675, for more information on local tunable variables and the WRITE_TUNE statement. Local tunable variables cannot be forced.


Like all tunable values in the AutoMax environment, the values of these UDC task tunables are retained through a power loss. Note that the programmer can also define other local tunable variables for application-specific purposes, but that the total number of all local tunables in a UDC task cannot exceed 127.

4.2.2.1 Calculating Local Tunable Values

Depending upon the type of local tunable variable, the “CURRENT” value, i.e., the value to be used for the next scan of the PMI, can be determined in one of the following ways:

1. Self Tune.

The programmer can request the PMI to generate the values for some of the variables. For example, the programmer can set the resolver calibration command bit in register 101/1101 to cause the PMI to adjust the resolver balance.

When the PMI has generated the values, it sends them to the UDC module over the fiber-optic link. The UDC module stores the values in the corresponding tunable variables. A copy of these values is maintained in the PMI for use in the execution of the control algorithm.

2. Tune values from the Programming Executive software and tasks.

The Monitor function in the Programming Executive allows all local tunables to be modified on-line within the limits defined in the LOCAL statement in the UDC task. Note that this is not recommended for the resolver calibration values because these values can be generated more precisely by the PMI during auto-tuning. At the end of the UDC task scan, the new values are sent to the PMI to be used in the execution of the control algorithm.

3. Enter the desired value into the “CURRENT” field for each LOCAL statement.

The programmer can choose to enter the desired values for local tunables in the “CURRENT” field of the corresponding LOCAL statement or leave them unchanged.

4.2.3 UDC/PMI Task Communication

Coordination between the two PMIs running their respective PMI tasks (drives A and B) and the UDC module running the corresponding UDC tasks is managed through the command and feedback messages sent over the fiber-optic link. The programmer does not control the operating system on the PMI. The timing of the PMI is based on the regulator selected.

A command message is sent to the PMI by the UDC module at the end of every scan of the UDC task. Each message contains the data in registers 100-106/1100-1106, Flex I/O data, and the values of the pre-defined local tunables that have changed. Note that some data may be sent over the course of several command messages.

A feedback message is sent to the UDC module by the PMI immediately before the beginning of every scan of the UDC task, i.e., immediately before the CCLK timer expires. Each message contains the data for registers 200-221/1200-1221, as well as any Flex I/O data that has changed from the last feedback message.


The exchange of command and feedback register data is synchronized through the use of the constant clock signal (CCLK) on the UDC module as described below. CCLK also enables the coordination of all UDCs in a rack because they will all use the same time base for task execution. Note that all UDC modules in a rack are not required to have the same value in the TICKS parameter of the SCAN_LOOP block in both their tasks. In other words, if the UDC module in slot 6 has TICKS = 10 in its tasks, and the UDC module in slot 7 has TICKS = 20 in its tasks, the tasks on the UDC module in slot 6 will execute twice as often as the tasks on the UDC module in slot 7, but they will execute on the same time basis, i.e., time zero is determined by CCLK timer expiration.

As soon as the UDC module and PMI are connected over the fiber-optic link, the PMI will request its operating system from the UDC module. Recall that the PMI operating system is part of the UDC operating system. As long as the UDC module has its own operating system and parameter object file, it will download to the PMI the correct operating system.

In order for the PMI and the UDC module to be synchronized, the UDC module must have its operating system, parameter object file, and configuration loaded. In addition, CCLK must be turned on in the AutoMax rack.

If the UDC tasks are already loaded onto the UDC module when the PMI requests its operating system, the UDC module will also send information about when the PMI should send feedback register data required by the UDC task(s). This ensures that the data is measured or calculated as close as possible to the time it is needed in order to ensure it is as current as possible for the next scan of the UDC task(s).

The UDC operating system determines the feedback register message timing required by examining the SCAN_LOOP block in each UDC task so that the feedback will arrive at the UDC module just before it is needed. For example, if the TICKS parameter value in the SCAN_LOOP block were 10, feedback data would be needed by the UDC module immediately before 10 x 500 µsec time expires.

At first, when the UDC module and PMI(s) are powered up and connected via the fiber-optic link, their system clocks are not synchronized. In order for the PMI and UDC module to be synchronized to the same clock signal for communicating command and feedback data on a regular and predictable basis, an AutoMax task must turn on the CCLK signal in the rack. Until CCLK is turned on, command and feedback messages are sent periodically, but not on a predictable basis.

CCLK can be turned on by setting the appropriate bit in UDC register 2000 (the interrupt status and control register for both A and B drive tasks), or by setting a bit in another module that can turn on CCLK. Only one module in the rack must turn on CCLK. Note that after a STOP ALL occurs in the rack, CCLK will be disabled and must be re-enabled again in order for UDC tasks to go into run. See figure 4.3 at the end of this chapter for the typical data flow between the UDC module and the PMI.

To verify that communication between the UDC module and the PMI is resulting in up-to-date feedback data, it is recommended that the drive’s run permissive logic include the CCLK synchronized status bit (register 200/1200, bit 14, CCLK_OK@) and the communication lost fault bit (register 202/1202, bit 15, FLT_COM@) as shown in figure 4.2.


Refer to the individual bit descriptions in this manual for more information.

4.3 AutoMax Processor Task and UDC Task Coordination

Recall that all tasks running on AutoMax Processors have access to the UDC dual port registers, but that UDC tasks can only access those common variables that represent registers in their own dual port memory. Task coordination between the UDC module and the AutoMax Processor is generally handled through periodic hardware interrupts generated by the UDC module. An AutoMax task needs to define a hardware “event” that will trigger some action by an AutoMax task, using the BASIC statement EVENT. The EVENT statement must reference the hardware interrupt status and control register ISCR% (register 2000 in the UDC dual port memory).

Although the UDC operating system itself actually causes the interrupt, a task in the rack (AutoMax or UDC) must write to the scans per update register in the UDC dual port (register 2001) in order to define the number of UDC task scans between updates of the Nth scan application registers (1300-1599), and between hardware interrupts. See figure 3.2 for more information.

Note that the register values being latched on every Nth scan provide a consistent context for evaluation of Control Block statements, but that BASIC statements in UDC tasks read and write data immediately: that is, they do not read from and write to a local buffer. Referencing the same common values in both Control Block and BASIC statements in one task can result in errors.

Figure 4.2 – Recommended Run Permissive Logic

CCLK_OK@ COM_FLT@ RUN_PERM@

RUN_PERM@

StartPermissive

Logic


Figure 4.3 – Data/Time Flow for UDC Module and PMI

(Bac

kgro

und)

(For

egro

und)

PM

IP

roce

ssor

UD

CM

odul

e

Aut

oMax

Pro

cess

or

Aut

oMax

task

writ

es n

ew

valu

es to

con

trol

com

man

d an

d

appl

icat

ion

regi

ster

s in

UD

C

dual

por

t mem

ory

Dia

gnos

tics,

Com

mun

icat

ion,

Man

agem

ent,

etc.

Vec

tor

*

Ass

umpt

ions

:

1. T

he U

DC

task

(s)

have

bee

n pu

t int

o ru

n be

fore

the

vect

or c

ontr

ol a

lgor

ithm

is tu

rned

on.

*Com

mun

icat

ion

of c

omm

and

and

feed

back

reg

iste

rs b

etw

een

the

UD

C a

nd P

MI s

ynch

roni

zed

UD

C ta

sks

and

PM

I c

ontr

ol a

lgor

ithm

s ar

e no

t syn

chro

nize

d. T

he v

ecto

r co

ntro

l alg

orith

m r

uns,

on

the

aver

age,

eve

ry 1

mse

c.

10 m

sec.

(20

ticks

)


CHAPTER 5On-Line Operation

The ON LINE! command in the System Configurator and the Task Manager applications allows you to access options such as loading, running, and monitoring tasks in the AutoMax rack. All of the options are described in detail in the AutoMax Programming Executive instruction manual.

The following sections provide a summary of some of the options as applied to the UDC module and UDC tasks. Note that the operating systems must be loaded onto the Processor modules and UDC modules in the AutoMax rack before attempting to use any of the on-line options.

5.1 Loading the UDC Module’s Operating System

The UDC module requires an operating system as well as the AutoMax Processor. The operating system can be loaded to a UDC module by using the Load Operating System command from the Command menu in the System Configurator. Refer to the AutoMax Programming Executive instruction manual for the procedure. The operating system(s) must be loaded to the AutoMax Processor(s) at the same time or before loading the UDC module operating system.

The operating system may be loaded to the UDC module in a specified slot or to all UDC modules in the rack. It is possible to re-load a single UDC module’s operating system without having to re-load the operating systems to all of the UDC modules in the rack.

The leftmost AutoMax Processor in the rack will check for compatibility between the AutoMax operating system and the UDC operating system. If a UDC module is replaced with another UDC module that already contains an incompatible operating system, the new UDC module will be disabled and its “OS OK” LED will be turned off.

5.2 Loading the Drive Parameters and UDC Tasks

The drive parameters specified when the UDC module is configured can be thought of as the UDC configuration. In addition to the AutoMax Processor, the UDC module must have its configuration loaded before it can execute any tasks. The drive parameters and UDC tasks can be loaded to the UDC by selecting “L” for Load from the ON LINE Transfer menu. Several options, which are briefly described in the following paragraphs, will be displayed on the screen.


On-Line Operation 5-1

The option “A” for ALL will automatically load the rack (i.e., AutoMax Processor configuration, the drive parameters for all the UDC modules in the rack, and all tasks for the rack, including all UDC tasks).

The drive parameters may be loaded to the UDC module in a specified slot or to all UDC modules in the rack. When the drive parameters are loaded, the AutoMax Programming Executive will determine if the drive parameters are compatible with the existing rack configuration. If the drive parameters are not compatible, an error message will be displayed on the computer screen.

UDC tasks may also be loaded to the UDC modules in the rack. If this option is chosen, the Programming Executive will display a list of all the AutoMax tasks and UDC tasks for the system. Select the task to be loaded from the list. Note that the rack configuration and the drive parameters must be loaded before loading UDC tasks to a UDC module.

Refer to the AutoMax Programming Executive instruction manual for the complete Load procedure.

5.3 Running, Stopping, and Deleting UDC Application Tasks

Running UDC Tasks

A UDC application task is required in order to control a Distributed Power System drive. To control two drives, two UDC tasks are required. Once it is loaded to the UDC, a UDC application task is included in the on-line task list with the AutoMax Processor application tasks. It can be run, stopped, monitored, or deleted in the same way as any other application task. The priority field will be set to “N/A” for UDC application tasks. The task for drive A always executes first, followed by the task for drive B.

The Run All command will run all AutoMax and UDC tasks. The UDC module’s tasks can be run whether or not the following conditions are met:

• the PMI Regulator is communicating with the UDC module

• the PMI Regulator’s operating system has been loaded from the UDC module to the PMI Regulator (which happens automatically when the PMI Regulator is connected to the UDC module).

Stopping UDC Tasks

UDC application tasks (both tasks A and B together) must run at least every 10 milliseconds. Once the SCAN_LOOP statement is executed, the UDC module will cause a Stop All in the rack if the task does not complete its scan within 10 milliseconds.

!ATTENTION:Understand the application before starting a task. Outputs may change states, resulting in machine movement. Failure to observe this precaution could result in bodily injury.

ATTENTION:It is the responsibility of the user to ensure that the application process stops in a safe manner when the application tasks stop. Failure to observe this precaution could result in bodily injury.


Deleting UDC Tasks

When a UDC application task is deleted, any local variables which were forced are removed from the force table. The task’s error log is also cleared.

5.4 UDC Information Log and Error Log

The information log and error log for a UDC task can be displayed by selecting “I” for Info/Log from the ON LINE menu. Refer to the AutoMax Programming Executive instruction manual for the procedure.

The information log for a slot containing a UDC module will display the UDC operating system’s part number, the utilization of the CPU resources in the UDC module, and various memory and PMI rack statistics. Select “U” from the Info/Log menu to display the information log. Note that the UDC module’s CPU utilization should not exceed 75%.

Like AutoMax tasks, UDC tasks can access the error log by using the BASIC statement CLR_ERRLOG@ and BASIC function TST_ERRLOG@. The error log will display the first, second, and last errors and will maintain them until power is cycled.

On-Line Operation 5-3

APPENDIX ASA3100 Vector Regulator

Register Reference

REGISTER MAP

Registers Function 0-23 Flex I/O port registers

24-79 System Use Only80-89 UDC/PMI comm. status registers for drive A90-99 System Use Only

100-106 Command registers for drive A107-199 System Use Only200-222 Feedback registers for drive A223-299 System Use Only300-599 Application registers updated every scan

for drives A and B600-999 System Use Only

1000 UDC module test switch register1001-1017 UDC module meter port setup registers1018-1079 System Use Only1080-1089 UDC/PMI comm. status registers for drive B1090-1099 System Use Only1100-1106 Command registers for drive B1107-1199 System Use Only1200-1222 Feedback registers for drive B1223-1299 System Use Only1300-1599 Application registers updated every scan

for drives A and B1600-1999 System Use Only2000-2010 Interrupt Status and Control registers for

drives A and B2011-2047 System Use Only

REGISTER/BIT DESCRIPTIONS

FLEX I/O PORT REGISTERS

A / B 0 / 12 PMI Module 0, Digital I/O 1 / 13 PMI Module 1, Digital I/O 2 / 14 PMI Module 2, Digital or Analog I/O 3 / 15 PMI Module 2, Analog 1 I/O 4 / 16 PMI Module 2, Analog 2 I/O 5 / 17 PMI Module 2, Analog 3 I/O 6 / 18 PMI Module 2, Analog 4 I/O 7 / 19 PMI Module 2, Analog 5 I/O 8 / 20 PMI Module 2, Analog 6 Input 9 / 21 PMI Module 2, Analog 7 Input10 / 22 Flex System Fault Bits, PMI Module 0 & 1 Faults

Bit 0 Flex Bus Fault 1 Flex Clock Fault 2 Flex Scratch Pad Fault 3 Flex Dual Port Fault 4 - 7 Not Used 8 Module 0 Not Plugged In 9 Module 0 Communication Error10 Module 0 Bad ID11 Module 0 Location Error12 Module 1 Not Plugged In13 Module 1 Communication Error14 Module 1 Bad ID15 Module 1 Location Error

FLEX I/O PORT REGISTERS (CONTINUED)

11 / 23 Flex Module 2 Fault BitsBit 0 Module 2 not plugged in 1 Module 2 communication error 2 Module 2 Bad ID code 3 - 7 Not Used 8 Channel 0 output open/input underrange 9 Channel 1 output open/input underrange10 Channel 2 output open/input underrange11 Channel 3 output open/input underrange12 Channel 4 output open/input underrange13 Channel 5 output open/input underrange14 Channel 6 output open/input underrange15 Channel 7 output open/input underrange

UDC-PMI COMMUNICATION STATUS

A/B80 /1080 UDC Module port status

Bit 0 Invalid rcr interrupt 1 No end of frame status 2 CRC/framing error 3 Overrun error 4 DMA format error 5 Transmitter underrun 6 CCLK comm sync error 7 Loopback data error 8 Missed gains 9 Multiplexed data verification error10 No matching PMI OS11 Invalid PMI OS header12 Incompatible PMI H/W

81 /1081 UDC module good msg. recvd. count82 /1082 UDC module CRC error count83 /1083 UDC module format error count84 /1084 PMI port status

Bit 0 Invalid rcr interrupt 1 No end of frame status 2 CRC/framing error 3 Overrun error 4 DMA format error 5 Transmitter underrun 6 CCLK comm sync error 8 UDC CCLK comm sync error 9 Multiplexed data verification error12 Invalid PMI start OS address13 Insuff. PMI memory to load PMI OS14 Invalid PMI load address15 PMI OS overflow

85 /1085 PMI good msg. recvd. count86 /1086 PMI CRC error count87 /1087 PMI format error count88 /1088 Comm/link status89 /1089 UDC transmitted msg. count

COMMAND REGISTERS

A/B100/1100 Drive Control

Bit 0 Enable PMI loop PMI_RUN@ 1 Enable tuning PMI_TUN@ 2 Bridge test enable BRG_TST@ 4 Bus enable BUS_ENA@ 5 DC braking on BRK_ON@ 6 Vector align request VOA_REQ@ 8 Fault reset FLT_RST@ 9 Warning reset WRN_RST@15 UDC task running (status)* UDC_RUN@

101/1101 I/O ControlBit 0 No slip adjustment NO_ADJ@ 1 No slip smoothing NO_INTR@ 2 External fault LED EXT_LED@ 4 Auxiliary output AUX_OUT@ 6 Enable resolver calibration RES_CAL@ 8 Enable external strobe STR_ENA@ 9 External strobe falling edge STR_ENF@10 STATOR_IZ_E1% tuning TUN_IZ@12 Torque overload ratio TORD_ON@15 UDC module loopback test UDC_LB@

102/1102 Torque reference TRQ_REF%103/1103 <not used>104/1104 Flux reference FLX_REF%

Id reference (dual-wound motor) ID_REF%105/1105 Bridge test code TST_CODE%106/1106 PMI D/A output PMI_DA%107/1107 <not used>

Vector orientatn ref (dual-wnd mtr)VO_REF%108/1108 DC braking reference BRK_REF%109/1109 <not used>

FEEDBACK REGISTERS

A/B200/1200 Drive status

Bit 0 Torque control on TRQ_ON@ 1 Auto tuning complete PMI_ATC@ 2 Torque ref saturation plus TRF_SP@ 3 Torque ref sat minus TRF_SM@ 4 DC bus ready BUS_RDY@ 5 Constant power region PWR_RNG@ 8 Fault detected FLT@ 9 Warning detected WRN@10 Vector align WRN_VOA@13 Flex I/O updated (System use)14 CCLK synchronized CCLK_OK@15 PMI OS loaded PMI_OK@

201/1201 I/O statusBit 0 Run permissive input RPI@ 1 M-contactor feedback M_FDBK@ 2 Auxiliary input 2 AUX_IN2@ 3 Auxiliary input 3 AUX_IN3@ 4 Auxiliary input 4 AUX_IN4@ 5 Auxiliary input 5 AUX_IN5@ 6 Resolver gain calibrated RES_GAN@ 7 Resolver balance calibrated RES_BAL@ 8 External strobe detected STR_DET@ 9 External strobe level STR_LVL@10 Stator IZ tuning complete TUNED_IZ@

SA3100 Vector Regulator Register Reference A-1

FEEDBACK REGISTERS (CONTINUED)

A/B202/1202 Drive Fault

Bit 0 DC bus overvoltage fault FLT_OV@ 1 DC bus overcurrent fault FLT_DCI@ 2 Ground current fault FLT_GND@ 3 Instantaneous overcurrent FLT_IOC@ 4 Power supply fault FLT_PWR@ 6 Charge bus time-out fault FLT_CHG@ 7 Over temperature fault FLT_OT@ 8 Resolver broken wire fault FLT_TBW@ 9 Resolver fault FLT_RES@10 Over speed fault FLT_OSP@11 Power technology fault FLT_PTM@13 PMI bus fault FLT_BUS@14 UDC run fault FLT_RUN@15 Communication lost fault FLT_COM@

203/1203 Drive WarningBit 0 DC bus overvoltage warning WRN_OV@ 1 DC bus undervoltage warning WRN_UV@ 2 Ground current warning WRN_GND@ 3 Voltage ripple warning WRN_VR@ 4 Reference in limit warning WRN_RIL@ 5 Tuning aborted warning WRN_TUN@ 7 Over temperature warning WRN_OT@ 8 Bad gain data warning WRN_BGD@ 9 Thermistor open warning WRN_TOC@13 Flex I/O comm. warning WRN_FLX@14 CCLK not synchronized WRN_CLK@15 PMI communication warning WRN_COM@

204/1204 Power Device StatusBit 0 Phase U -upper IOC A U_UPA@ 1 Phase V -upper IOC A V_UPA@ 2 Phase W-upper IOC A W_UPA@ 3 Phase U-lower IOC A U_LOA@ 4 Phase V-lower IOC A V_LOA@ 5 Phase W-lower IOC A W_LOA@ 6 Inverter Power Device Fault IPMA@

205/1205 InterlockBit 0 Configuration not loaded IC_CNF@ 1 Valid gains not loaded IC_GAIN@ 2 Run permissive missing IC_RPI@ 3 Faults need reset IC_FLT@ 4 Rising edge required IC_RISE@ 5 More than one request IC_MORE@ 6 Bus not ready IC_BUS@ 7 MCR did not close IC_MCR@10 Incompatible resolver IC_IRES@


Drive Data A/B

206/1206 DC bus voltage (volts) BUS_VDC%207/1207 DC bus current (amps * 10) BUS_IDC%208/1208 Ground current (amps * 10) GI_FB%209/1209 Voltage feedback (Vrms) V_FB%210/1210 Current feedback (Irms * 10) I_FB%211/1211 Current fdbk (normalized) I_FBN%212/1212 Id fdbk (normalized) ID_FBN%213/1213 Iq feedback (normalized) IQ_FBN%214/1214 User analog input ANA_IN%(-2048 = -10V to 2047 = 10V)215/1215 Resolver Scan Position RES_SCN_POS%(-32768 to 32767)216/1216 Resolver Strobe Position RES_STR_POS%(-32768 to 32767)217/1217 Motor speed feedback (RPM) RPM%

Id feedback (dual-wound mtr) ID_FBK%218/1218 Slip feedback (Hz * 100) SLIP_FB%

Carrier frequency (V/Hz) F_CARR%Vector orient ref (dl-wnd mtr) VO_FBK%

219/1219 Selected variable SEL_VAR%220/1220 Not used221/1221 Not used222/1222 Diagnostic fault code DIAG_FLT%

300 - 599 Application registers updated every scan - A/B

UDC MODULE TEST INPUTS

1000 SwitchesBit 0 UDC pushbutton UDC_PB@ 1 UDC switch UP position SWIT_UP@ 2 UDC switch DOWN position SWIT_DN@

LEDs 8 OS OK 9 Comm A OK10 Drive A status11 Comm B OK12 Drive B status

METER PORT SETUP

1001 Initiate change in setup (non-zero value)1002 Port 1 UDC register number (0-2047)1003 Port 1 bit number (100-115, 0 = all bits)1004 Port 1 maximum value1005 Port 1 minimum value1006 Port 2 UDC register number (0-2047)1007 Port 2 bit number (100-115, 0 = all bits)1008 Port 2 maximum value1009 Port 2 minimum value1010 Port 3 UDC register number (0-2047)1011 Port 3 bit number (100-115, 0 = all bits)1012 Port 3 maximum value1013 Port 3 minimum value1014 Port 4 UDC register number (0-2047)1015 Port 4 bit number (100-115, 0 = all bits)1016 Port 4 maximum value1017 Port 4 minimum value

APPLICATION REGISTERS

1300 - Application registers updated every1599 Nth scan - A/B

INTERRUPT STATUS AND CONTROL (ISCR)

2000 Interrupt status and control UDC_ISCR%Bit 0 Interrupt line ID 2 Interrupt allocated 4 Interrupt generated this scan 5 CCLK counting 6 Enable CCLK to backplane* 7 Interrupt enabled15 Interrupt status* Only bit 6 in register 2000 can be written to by the programmer. All other bits in register 2000 are read only.

2001 Scans per interrupt

LOCAL TUNABLE VARIABLES

Current minor loop crossover CML_WCO%frequency (1 = 1 radian/sec)Flux loop crossover frequency FLUX_WCO%(1 = 1 radian/sec)Ground current warning threshold GIT_E1%(10 = 1 amp)Over voltage warning threshold OVT_E0%(1 = 1 volt)Power loss fault threshold PLT_E0%(1 = 1 volt)Resolver balance RES_BAL%(Default CURRENT value = 0)Resolver gain RES_GAN%(Default CURRENT value = 0)Slip adjustment (1000 = gain of 1000) SLIP_ADJ_E3%No load stator current (10 = 1 amp) STATOR_IZ_E1%Stator resistance (1000 = 1 ohm) STATOR_R_E4%Stator time constant (10 = 1 msec) STATOR_T_E4%Under voltage warning threshold UVT_E0%(1 = 1 volt)Voltage ripple warning threshold VRT_E0%(1 = 1 volt)

INTERNAL GAIN TUNABLE VARIABLES(Peak Amps * 10)

Internal gain point one IGN1!Internal gain point two IGN2!Internal gain point three IGN3!Internal gain point four IGN4!Internal gain point five IGN5!Internal gain point six IGN6!Internal gain point seven IGN7!Internal gain point eight IGN8!Internal gain point nine IGN9!Internal gain point ten IGN10!

A-2 SA3100 Drive Configuration and Programming

APPENDIX BSA3100 Volts / Hertz Regulator

Register Reference

REGISTER MAP

Registers Function 0-23 Flex I/O port registers

24-79 System Use Only80-89 UDC/PMI comm. status registers for drive A90-99 System Use Only

100-106 Command registers for drive A107-199 System Use Only200-222 Feedback registers for drive A223-299 System Use Only300-599 Application registers updated every scan

for drives A and B600-999 System Use Only

1000 UDC module test switch register1001-1017 UDC module meter port setup registers1018-1079 System Use Only1080-1089 UDC/PMI comm. status registers for drive B1090-1099 System Use Only1100-1106 Command registers for drive B1107-1199 System Use Only1200-1222 Feedback registers for drive B1223-1299 System Use Only1300-1599 Application registers updated every scan

for drives A and B1600-1999 System Use Only2000-2010 Interrupt Status and Control registers for

drives A and B2011-2047 System Use Only

REGISTER/BIT DESCRIPTIONS

FLEX I/O PORT REGISTERS

A / B 0 / 12 PMI Module 0, Digital I/O 1 / 13 PMI Module 1, Digital I/O 2 / 14 PMI Module 2, Digital or Analog I/O 3 / 15 PMI Module 2, Analog 1 I/O 4 / 16 PMI Module 2, Analog 2 I/O 5 / 17 PMI Module 2, Analog 3 I/O 6 / 18 PMI Module 2, Analog 4 I/O 7 / 19 PMI Module 2, Analog 5 I/O 8 / 20 PMI Module 2, Analog 6 Input 9 / 21 PMI Module 2, Analog 7 Input10 / 22 Flex System Fault Bits, PMI Module 0 & 1 Faults

Bit 0 Flex Bus Fault 1 Flex Clock Fault 2 Flex Scratch Pad Fault 3 Flex Dual Port Fault 4 - 7 Not Used 8 Module 0 Not Plugged In 9 Module 0 Communication Error10 Module 0 Bad ID11 Module 0 Location Error12 Module 1 Not Plugged In13 Module 1 Communication Error14 Module 1 Bad ID15 Module 1 Location Error

FLEX I/O PORT REGISTERS (CONTINUED)

11 / 23 Flex Module 2 Fault BitsBit 0 Module 2 not plugged in 1 Module 2 communication error 2 Module 2 Bad ID code 3 - 7 Not Used 8 Channel 0 output open/input underrange 9 Channel 1 output open/input underrange10 Channel 2 output open/input underrange11 Channel 3 output open/input underrange12 Channel 4 output open/input underrange13 Channel 5 output open/input underrange14 Channel 6 output open/input underrange15 Channel 7 output open/input underrange

UDC-PMI COMMUNICATION STATUS

A/B80 /1080 UDC Module port status

Bit 0 Invalid rcr interrupt 1 No end of frame status 2 CRC/framing error 3 Overrun error 4 DMA format error 5 Transmitter underrun 6 CCLK comm sync error 7 Loopback data error 8 Missed gains 9 Multiplexed data verification error10 No matching PMI OS11 Invalid PMI OS header12 Incompatible PMI H/W

81 /1081 UDC module good msg. recvd. count82 /1082 UDC module CRC error count83 /1083 UDC module format error count84 /1084 PMI port status

Bit 0 Invalid rcr interrupt 1 No end of frame status 2 CRC/framing error 3 Overrun error 4 DMA format error 5 Transmitter underrun 6 CCLK comm sync error 8 UDC CCLK comm sync error 9 Multiplexed data verification error12 Invalid PMI start OS address13 Insuff. PMI memory to load PMI OS14 Invalid PMI load address15 PMI OS overflow

85 /1085 PMI good msg. recvd. count86 /1086 PMI CRC error count87 /1087 PMI format error count88 /1088 Comm/link status89 /1089 UDC transmitted msg. count

COMMAND REGISTERS

A/B100/1100 Drive Control

Bit 0 Enable PMI loop PMI_RUN@ 1 Enable tuning PMI_TUN@ 2 Bridge test enable BRG_TST@ 4 Bus enable BUS_ENA@ 5 DC braking on BRK_ON@

7 Synch transfer request1 SYN_REQ@ 8 Fault reset FLT_RST@ 9 Warning reset WRN_RST@15 UDC task running (status)* UDC_RUN@

101/1101 I/O ControlBit 2 External fault LED EXT_LED@ 4 Auxiliary output AUX_OUT@ 6 Enable resolver calibration RES_CAL@ 8 Enable external strobe STR_ENA@ 9 External strobe falling edge STR_ENF@10 STATOR_IZ_E1% tuning TUN_IZ@15 UDC module loopback test UDC_LB@

102/1102 Frequency reference (high) FRQ_REF(H)!103/1103 Frequency reference (low) FRQ_REF(L)!104/1104 Boost voltage reference VLT_REF%

Id reference (dual-wound motor) ID_REF%105/1105 Bridge test code TST_CODE%106/1106 PMI D/A output PMI_DA%

107/1107 Synchronous transfer volts1 SX_V%Vector orientation ref (dl-wnd mtr)VO_REF%

108/1108 DC braking reference BRK_REF%109/1109 <not used>

FEEDBACK REGISTERS

A/B200/1200 Drive status

Bit 0 Frequency control on FRQ_ON@ 1 Auto tuning complete PMI_ATC@ 2 Freq ref saturation plus FRF_SP@ 3 Freq refsaturation minus FRF_SM@ 4 DC bus ready BUS_RDY@ 7 OK to synch transfer SYN_OK@ 8 Fault detected FLT@ 9 Warning detected WRN@13 Flex I/O updated (System use)14 CCLK synchronized CCLK_OK@15 PMI OS loaded PMI_OK@

201/1201 I/O statusBit 0 Run permissive input RPI@ 1 M-contactor feedback M_FDBK@ 2 Auxiliary input 2 AUX_IN2@ 3 Auxiliary input 3 AUX_IN3@ 4 Auxiliary input 4 AUX_IN4@ 5 Auxiliary input 5 AUX_IN5@ 6 Resolver gain calibrated RES_GAN@ 7 Resolver balance calibrated RES_BAL@ 8 External strobe detected STR_DET@ 9 External strobe level STR_LVL@10 Stator IZ tuning complete TUNED_IZ@

1. Feature reserved for future releases.

SA3100 Volts / Hertz Regulator Register Reference B-1


A/B202/1202 Drive Fault

Bit 0 DC bus overvoltage fault FLT_OV@ 1 DC bus overcurrent fault FLT_DCI@ 2 Ground current fault FLT_GND@ 3 Instantaneous overcurrent FLT_IOC@ 4 Power supply fault FLT_PWR@ 6 Charge bus time-out fault FLT_CHG@ 7 Over temperature fault FLT_OT@ 8 Resolver broken wire fault FLT_TBW@ 9 Resolver fault FLT_RES@10 Over speed fault FLT_OSP@11 Power technology fault FLT_PTM@13 PMI bus fault FLT_BUS@14 UDC run fault FLT_RUN@15 Communication lost fault FLT_COM@

203/1203 Drive WarningBit 0 DC bus overvoltage warning WRN_OV@ 1 DC bus undervoltage warning WRN_UV@ 2 Ground current warning WRN_GND@ 3 Voltage ripple warning WRN_VR@ 4 Reference in limit warning WRN_RIL@ 5 Tuning aborted warning WRN_TUN@ 7 Over temperature warning WRN_OT@ 8 Bad gain data warning WRN_BGD@ 9 Thermistor open warning WRN_TOC@11 <reserved>13 Flex I/O comm. warning WRN_FLX@14 CCLK not synchronized WRN_CLK@15 PMI communication warning WRN_COM@

204/1204 Power Device StatusBit 0 Phase U -upper IOC A U_UPA@ 1 Phase V -upper IOC A V_UPA@ 2 Phase W-upper IOC A W_UPA@ 3 Phase U-lower IOC A U_LOA@ 4 Phase V-lower IOC A V_LOA@ 5 Phase W-lower IOC A W_LOA@ 6 Inverter Power Device Fault IPMA@

205/1205 InterlockBit 0 Configuration not loaded IC_CNF@ 1 Valid gains not loaded IC_GAIN@ 2 Run permissive missing IC_RPI@ 3 Faults need reset IC_FLT@ 4 Rising edge required IC_RISE@ 5 More than one request IC_MORE@ 6 Bus not ready IC_BUS@ 7 MCR did not close IC_MCR@10 Incompatible resolver IC_IRES@


Drive Data A/B

206/1206 DC bus voltage (volts) BUS_VDC%207/1207 DC bus current (amps * 10) BUS_IDC%208/1208 Ground current (amps * 10) GI_FB%209/1209 Voltage feedback (Vrms) V_FB%210/1210 Current feedback (Irms * 10) I_FB%211/1211 Volt command V_CMD%212/1212 Output frequency (high) F_CMD(H)!213/1213 Output frequency (low) F_CMD(L)!214/1214 User analog input ANA_IN%(-2048 = -10V to 2047 = 10V)215/1215 Resolver Scan Position RES_SCN_POS%(-32768 to 32767)216/1216 Current fdback normalized I_FBN%217/1217 Motor speed feedback (RPM)RPM%

Id feedback (dual-wound mtr)ID_FBK%218/1218 Carrier frequency F_CARR%

Vector orient ref (dl-wnd mtr) VO_FBK%219/1219 Selected variable SEL_VAR%220/1220 Not used221/1221 Not used222/1222 Diagnostic fault code DIAG_FLT%

300 - 599 Application registers updated every scan - A/B

UDC MODULE TEST INPUTS

1000 SwitchesBit 0 UDC pushbutton UDC_PB@ 1 UDC switch UP position SWIT_UP@ 2 UDC switch DOWN position SWIT_DN@

LEDs 8 OS OK 9 Comm A OK10 Drive A status11 Comm B OK12 Drive B status

METER PORT SETUP

1001 Initiate change in setup (non-zero value)1002 Port 1 UDC register number (0-2047)1003 Port 1 bit number (100-115, 0 = all bits)1004 Port 1 maximum value1005 Port 1 minimum value1006 Port 2 UDC register number (0-2047)1007 Port 2 bit number (100-115, 0 = all bits)1008 Port 2 maximum value1009 Port 2 minimum value1010 Port 3 UDC register number (0-2047)1011 Port 3 bit number (100-115, 0 = all bits)1012 Port 3 maximum value1013 Port 3 minimum value1014 Port 4 UDC register number (0-2047)1015 Port 4 bit number (100-115, 0 = all bits)1016 Port 4 maximum value1017 Port 4 minimum value

APPLICATION REGISTERS

1300 - Application registers updated every1599 Nth scan - A/B

INTERRUPT STATUS AND CONTROL (ISCR)

2000 Interrupt status and control UDC_ISCR%Bit 0 Interrupt line ID 2 Interrupt allocated 4 Interrupt generated this scan 5 CCLK counting 6 Enable CCLK to backplane* 7 Interrupt enabled15 Interrupt status* Only bit 6 in register 2000 can be written to by the programmer. All other bits in register 2000 are read only.

2001 Scans per interrupt

LOCAL TUNABLE VARIABLES

Current minor loop crossover CML_WCO%frequency (1 = 1 radian/sec)Ground current warning threshold GIT_E1%(10 = 1 amp)Over voltage warning threshold OVT_E0%(1 = 1 volt)Power loss fault threshold PLT_E0%(1 = 1 volt)Resolver balance RES_BAL%(Default CURRENT value = 0)Resolver gain RES_GAN%(Default CURRENT value = 0)Under voltage warning threshold UVT_E0%(1 = 1 volt)Voltage ripple warning threshold VRT_E0%(1 = 1 volt)

VOLTAGE POINT TUNABLE GAINS (1000 = 1 volt)

Point 0 Voltage P0VT_E3!Point 1 Voltage P1VT_E3!Point 2 Voltage P2VT_E3!Point 3 Voltage P3VT_E3!Point 4 Voltage P4VT_E3!Point 5 Voltage P5VT_E3!Point 6 Voltage P6VT_E3!

FREQUENCY POINT TUNABLE GAINS (1000 = 1 Hz)

Point 0 Frequency P0HZ_E3!Point 1 Frequency P1HZ_E3!Point 2 Frequency P0HZ_E3!Point 3 Frequency P3HZ_E3!Point 4 Frequency P4HZ_E3!Point 5 Frequency P5HZ_E3!Point 6 Frequency P6HZ_E3!

B-2 SA3100 Drive Configuration and Programming

SA3100 Volts / Hertz Regulator Register Reference B-3

B-4 SA3100 Drive Configuration and Programming

APPENDIX CSA3100 Local Tunable

Variables

C.1 Current Minor Loop Gain Variables

The stator resistance and the stator time constant values can be generated automatically by using the enable tuning command (register 100/1100, bit 1). The values generated by the system should not require adjustment. If any of these values are modified outside of acceptable limits, the new value will be ignored and the last acceptable value entered will be used. Bit 8 in warning register 203/1203 will also be set to indicate the value entered was invalid.

CML_WCO% Current Minor Loop Crossover Frequency

The value of the Current Minor Loop Crossover Frequency sets the desired response of the current minor loop. The higher the value, the more quickly the drive responds to a change in torque reference current.

Units: Rads/SecDefault Value: 1000Low Limit: 1000High Limit: 4000Step: 1

This value is entered in radians per second. Note that if this value is adjusted too high, the current minor loop will become unstable.

FLX_WCO% Flux Loop Crossover Frequency

The value of the Flux Loop Crossover Frequency is used to adjust the bandwidth of the flux loop used in the Constant Power version of the SA3100 Vector regulator.

Units: Rads/SecDefault Value: 10Low Limit: 5High Limit: 50Step: 1

The value is entered in radians per second, where 1 = 1 radian/second.

STATOR_R_E4% Stator Resistance

The value of the Stator Resistance is used to adjust the gain of the current minor loop. It is also used in flux feedback calculations.

The value is entered in ohms times 10000, e.g., a resistance of 0.1 ohm is entered as 1000.

Units: Ohms ∗ 10000Default Value: 10Low Limit: 0High Limit: 20000Step: 1

SA3100 Local Tunable Variables C-1

C.2 Vector Algorithm Gain Variables

The vector algorithm gain variables are used to adjust the gain of the vector control algorithm. The no load stator current variable can be generated automatically by using the enable tuning command in register 100/11000. The value generated by the system should not require adjustment. If this value is modified outside of acceptable limits, the new value will be ignored and the last acceptable value entered will be used. Bit 8 in warning register 203/1203 will also be set to indicate the value entered was invalid.

STATOR_T_E4% Stator Time Constant

The value of the Stator Time Constant is used to adjust the gain of the current minor loop.

The value is entered in seconds times 10000, e.g., 50 msec (0.05 Sec) is entered as 500.

Units: Secs ∗ 10000Default Value: 10Low Limit: 0High Limit: 10000Step: 1

STATOR_IZ_E1% No Load Stator Current

The value in this variable represents the amount of magnetizing current (flux).

This value is entered in amps times 10, e.g., a no load stator current of 10 amps is entered as 100.

Units: Amps ∗ 10Default Value: 10Low Limit: 0High Limit: 8486Step: 1

Verifying STATOR_IZ_E1% When Using High Slip Motors

The value in local tunable STATOR_IZ_E1% is generated automatically by the system by setting the Enable Auto Tune bit in the Drive Control register (register 100/1100, bit 1, PMI_TUN@). However, if a high slip motor is being driven, the value calculated for this variable may not be correct. With high slip motors, it is important to verify the value in this variable using the following procedure:

Step 1. With no load, command the motor to its synchronous speed with no load. Synchronous speed in RPM = 120 ∗ fo/n, where fo = rated motor frequency in hertz and n = number of motor poles.

Step 2. At synchronous speed, monitor motor voltage using register 209.

Step 3. Modify the value in STATOR_IZ_E1% until motor voltage is approximately 97% of rated motor voltage.

Example:

The following example applies the above procedure to verify the value of STATOR_IZ_E1% for a 60 Hz, 4-pole high slip motor with a rated motor voltage of 460V, a rated speed of 1755 RPM, and rated full load current of 11.9A:

Step 1. Command the motor to its synchronous speed with no load:Synchronous speed = 120 ∗ 60/4 = 1800 RPM,Command = (1800/1755) ∗ 4095 = 4200 counts.

Step 2. At synchronous speed, monitor motor voltage using register 209.

Step 3. Modify the value in STATOR_IZ_E1% until motor voltage is between 472V and 435V. The higher value is preferred.

C-2 SA3100 Drive Configuration and Programming

Tuning STATOR_IZ_E1% for Constant Power Applications

The SA3100 Constant Power operating system has the capability of accommodating temperature changes via modification of the slip value. This modification of the slip value is accomplished through the use of a PMI reference magnetizing current table, which enables the PMI to determine when a load change has occurred.

When a load change occurs, the output of the flux loop will increase. This increased output is compared to the value from the reference table. The difference between the two generates a change in slip. The change in slip causes a reduction in flux loop output which, in turn, causes the flux loop output to be the correct value for the magnetizing current value at that point in the speed range.

In order to tune or calibrate the table, a speed loop is implemented in the UDC module. This speed loop must be set up so that a value of 4095 counts of speed reference corresponds to the maximum speed of the drive (i.e. four times the maximum voltage speed). The following table indicates the speed reference points at which data is to be obtained: Note that the values saved in the IGNn! variables will be in units of amps ∗ 100.

Ref. Point Speed Reference

CountsWhere the Value is

Saved

One 409 STATOR_IZ_E1%

Two 10231

1. Equal to maximum voltage speed.

The number of reference points required depends upon the speed range of the application:

For a 2 to 1 range, reference points 1 to 7 are used.



IGN1!

Three 1125 IGN2!

Four 1227 IGN3!

Five 1329 IGN4!

Six 1635 IGN5!

Seven 1941 IGN6!

Eight 2247 IGN7!

Nine 2859 IGN8!

Ten 4095 IGN9!

STATOR_IZ_E1% No Load Stator Current


STATOR_IZ_E1% (continued) No Load Stator Current

Use the following procedure to implement each reference point in the speed loop calculation:

Step 1. With the drive’s motor unconnected, set bits 0 and 1 of register 101/1101.

Step 2. Command the speed loop to the appropriate speed reference

Step 3. When the speed is reached, set bit 10 of register 101/1101 in the UDC.

Step 4. Monitor register 203/1203 and bit 10 of register 201/1201.

Step 5. If register 203/1203 is set to 20H, reset bit 10 of register 101/1101 and proceed to step 7.

Step 6. If bit 10 of register 201/1201 was set, reset bit 10 in register 101/1101 and continue with the next speed point as described in step 3. When all the required speed points have been completed, proceed to step 8.

Step 7. If register 203/1203 contains a value of 20H, verify that the speed scaling of the speed loop is correct and lower the initial value of Stator_IZ_E1%. The output of the flux loop may be in saturation. Try lowering Stator_IZ_E1% by 5%. Reset the warning, and continue with the next speed point as described in step 3.

Step 8. Reset bits 0 and 1 of register 101/1101.

Note that in Dual Wound Motor Applications (Parallel Inverter Drives) use the previous procedure with the following additions:

• After using the reference point data for drive A (register 101), use the reference point data for drive B (register 1101).

• Ensure that the vector orientation alignment request bit (bit 6, 0040H) is set in register 1100.

SLIP_ADJ_E3% Slip Adjustment

Rotor slip is calculated automatically by the system. The value in this variable is used to adjust the resulting rotor slip value. As Slip Adjustment is increased, higher stator frequency is produced.

Units: Gain ∗ 1000Default Value: 850Low Limit: 500High Limit: 1500Step: 1

Note that slip will vary with rotor temperature. The value of Slip Adjustment may be changed through an application task to compensate for temperature changes when not using the constant power feature. A value of 1000 corresponds to a gain of 1.


C.3 Volts per Hertz Voltage Point Gain Variables

The seven gains below represent the seven voltage points of the V/Hz characteristic curve. When the PMI Regulator detects a set of 0 value volts per hertz characteristic gains it will calculate a curve.

When the enable tuning command (register 100/1100, bit 1, PMI_TUN@) is asserted, these gains are reset to their default values. When the reset is complete register 200, bit 1 (PMI_ATC@) is set.

See Appendix E (Figures E.2 and E.3) for more information on the V/Hz characteristic.

P0VT_E3! Point 0 Voltage

This value is set to select the voltage at point 0 in the V/Hz characteristic curve.

This value is entered in times 1000, e.g., 50 volts is entered as 50000.

Units: Volts ∗ 1000Default Value: 0Low Limit: 0High Limit: 1000000Step: 1


















C.4 Volts per Hertz Frequency Point Gain VariablesThese seven gains below represent the seven frequency points of the V/Hz characteristic curve. Output voltage varies with output frequency according to the V/Hz characteristic.

When the enable tuning command (register 100/1100, bit 1, PMI_TUN@) is asserted, these gains are reset to their default values. When the reset is complete register 200, bit 1 (PMI_ATC@) is set

See Appendix E (Figures E.2 and E.3) for more information on the V/Hz characteristic.









P0HZ_E3! Point 0 Frequency

This value is set to select the frequency at point 0 in the V/Hz characteristic curve.

Note that P0HZ_E3 is always 0 (zero) Hz.

Units: Hz ∗ 1000Default Value: 0Low Limit: 0High Limit: 0Step: 0




This value is entered in hertz times 1000, e.g., 60 hertz is entered as 60000.























C.5 DC Bus VariablesThe programmer selects the values in the following variables to determine the drive’s response to changes in the DC bus. Note that the following relationship must be true or a drive warning will occur (register 203/1203, bit 8):

PLT_E0% < UVT_E0% < OVT_E0%

For more information about internal DC bus control, refer to the SA3100 Power Modules instruction manual (S-3058).

OVT_E0% Over Voltage Warning Threshold

A drive warning is generated (203/1203, bit 0) if DC bus voltage exceeds the value stored in this variable. It should be set below the hardware over voltage fault limit and above the normal operating voltage. The value is entered in volts.

Units: VoltsDefault Value: 300Low Limit: 300High Limit: 1000Step: 1

The hardware over voltage fault limit is 400V for 230V Power Modules, 800V for 460V Power Modules, and 975V for 575V Power Modules. The normal operating voltage is displayed in the DC Bus Voltage Feedback register (206/1206).

This value also selects the starting point at which the system begins reducing the regeneration torque limit. Bit 4 of the Drive Warning register (203/1203) is also set to indicate the system is limiting torque.

PLT_E0% Power Loss Fault Threshold

A drive fault is generated (202/1202, bit 6) if DC bus voltage drops below the value stored in this variable.


This value should be set to 100V below the normal operating voltage of the bus. It is entered in volts. The normal operating voltage of the bus is displayed in the DC Bus Voltage Feedback register (206/1206).

When deciding what value to use for PLT_E0%, note that the instantaneous change in voltage on the bus capacitors in the Power Module cannot exceed 100V.

UVT_E0% Undervoltage Warning Threshold

A drive warning is generated (register 203, bit 1) if DC bus voltage is less than the value stored in this variable. This value should be set above the value selected for the Power Loss Fault Threshold variable. It is entered in volts.



C.6 Resolver Balance and Gain VariablesThe resolver gain and balance variable values are used to compensate for varying lengths of resolver wiring. The balance value can be generated automatically by commanding the resolver calibration test in register 101/1101. The gain value will be generated automatically when the RES_GAN% variable is equal to zero., i.e., on power-up. Refer to the SA3100 PMI Regulator instruction manual (S-3057) for more information on the calibration procedures.

Note that Distributed Power Systems are designed to be used with the resolvers described in S-3057. The validity of the results of these calibration procedures are not guaranteed if resolvers other than those described are used.

Figure C.1 – Capacitance Used for Resolver Balancing

VRT_E0% Voltage Ripple Warning Threshold

A drive warning is generated (203/1203, bit 3) if ripple (voltage variation) on the DC bus exceeds the value stored in this variable. The value is entered in volts.


This diagnostic is operational after the bus has reached steady state. It is intended to be used to detect an input phase loss in the rectifier section of a three-phase AC input. However, it can also be used with a common bus supply.

RES_BAL% Resolver Balance

The RES_BAL% local tunable contains the amount of capacitance that is to be added to the sine or cosine channel of the resolver to compensate for stray inductance in the wiring.

Units: pF ∗ 100Default Value: 0Low Limit: 0High Limit: 79Step: 1

This value may range from 0 to 79, with 0 indicating that balance tuning has not been performed. Values from 1 to 39 add capacitance to the cosine channel, while values from 41 to 79 add capacitance to the sine channel. Each integer value represents 100 pF as shown in figure C.1.

Added to Cosine Channel Added to Sine Channel

3900 pF 100 pF 0 pF 100 pF 3900 pF

0 1 39 40 41 79

TuningNot Done


C.7 Diagnostic VariablesThe programmer enters the values in the diagnostic variables to establish thresholds at which drive warnings are generated.

RES_GAN% Resolver Gain

When RES_GA% is equal to zero, the gain tuning procedure is performed automatically by the operating system. Zero is the default value.

The value can range from 0 to 255 counts, with 1 count representing 0.15 volts of gain.

Units: CountsDefault Value: 0Low Limit: 0High Limit: 255Step: 1

This value should be generated using the auto-tuning procedure because the PMI Processor can take into account the entire resolver circuit when setting the proper gain value.

If the gain needs to be re-calibrated, reset the value of RES_GAN% to zero. However, do not reset the value of RES_GAN% to zero while the inner loop is running (i.e., TRQ_ON@ is set). If the value is adjusted too low, a drive fault (register 202/1202, bit 8) will occur.

GIT_E1% Ground Current Warning Threshold

A drive warning is generated (203/1203, bit 4) if ground current exceeds the value stored in this variable. The value is entered in amps times 10, e.g., 10.1 amps is entered as 101.

Units: Amps ∗ 10Default Value: 100Low Limit: 10High Limit: 2000Step: 1

This value should be set above the value in the ground current feedback register (208/1208) after the drive is operational.


APPENDIX DVector with Constant Power

Regulator

SA3100 drives may use either a vector regulator (constant torque or constant power) to control current (torque) to AC motors, or a Volts per Hertz regulation algorithm (see Appendix E). Execution of the vector algorithm is referred to as the minor loop (V/Hz does not use a current minor loop). Power conversion (DC bus to AC variable frequency, variable torque) is performed via pulse width modulation (PWM), which produces a nearly sinusoidal current waveform.

A block diagram of the Vector with Constant Power control algorithm is shown on the following page. Please refer to this figure while reading the following description.

The UDC application control task (the major loop) passes the torque reference command in TRQ_REF% (register 102/1102) to the PMI Regulator, where a value of +/- 4095 corresponds to the motor overload ratio amps specified for the motor in parameter configuration. Drive A and drive B each receive their torque reference from separate speed loops in the UDC module.

The motor currents are separated into two components, Iq and Id. The Iq component produces the torque in the motor while the Id component is the magnetizing current that produces the flux in the motor.

The Id component is normally calculated by the PMI processor based on the no-load stator current configuration parameter entered by the programmer. The programmer can select to calculate Id in the UDC task instead in order to operate the motor at speed ratios up to 2:1 (motor speed versus base speed) or to control the flux directly.

For constant power operation at speed ratios up to 4:1, the programmer can select to have the PMI Regulator calculate the value of Id using integrated motor voltage feedback. The vector algorithm combines the Id and Iq components to produce a vector that is equal to the total current required by the motor to produce the desired torque.

The vector algorithm calculates the electrical phase position of the current reference. This is determined from the Id and Iq reference vector, the motor speed feedback, and the slip calculation. The outputs of the vector algorithm are three current reference signals (Iu, Iw, Iv), one for each phase of the motor.

These current reference signals are compared with the current feedback signals, producing error signals that feed proportional plus integral function blocks. The output of these blocks is a voltage reference. The line-to-neutral voltage signal is further conditioned by injecting a 3rd harmonic signal designed to increase the fundamental voltage of the drive’s output. The conditioned voltage reference is then compared against a triangle wave. The output of the comparator block is a PWM waveform, which drives the power devices in the inverter bridge to pass current to the motor.

Vector with Constant Power Regulator D-1

Figure D.1 – Vector with Constant Power Regulator Block Diagram

UD

C M

OD

ULE

OU

TE

RC

ON

TR

OL

LOO

P(S

)

TR

Q_R

EF

%+

4095

-409

5S

CA

LIN

G

ST

AT

OR

_IZ

_E1%

SLI

P_A

DJ_

E3%

SLI

PG

AIN

CT

T

SU

M

SU

MV

Q_R

EF

Vu

Vv

Vw

P W M

Iu U

PP

ER

Iv U

PP

ER

Iw U

PP

ER

Iu L

OW

ER

Iv L

OW

ER

Iw L

OW

ER

CU

RR

EN

TR

EG

ULA

TIO

N

CM

L_W

CO

%

ST

AT

OR

_R_E

4%S

TA

TO

R_T

_E4%

T

RE

SO

LVE

R P

OS

ITIO

N

IQ_F

B%

ID_F

B%

+ _

+ _

VD

_RE

F

IQ_R

EF

ID_R

EF

CT=

TU

NA

BLE

OR

AF

FE

CT

ED

BY

TU

NA

BLE

= D

ER

IVE

D F

RO

M C

ON

FIG

UR

AT

ION

PA

RA

ME

TE

R

KE

Y

VE

CT

OR

RO

TA

TO

R

CO

NV

ER

SIO

N

3-P

HA

SE

CU

RR

EN

TR

EG

ULA

TIO

N

(AN

GLE

OF

VE

CT

OR

)θ

FLU

X R

EF

/UD

C

FLU

X L

OO

P

ST

AT

OR

_IZ

%

Vu

Vv

Vw

OR

OR

& TO

D-2 SA3100 Drive Configuration and Programming

D.1 Dual Wound Motor

D.1.1 Overview

The dual wound motor is a specially designed motor which has two sets of terminals for connection to two inverters. The outputs of the inverters are connected to the parallel windings of the motor. This type of motor enables an application engineer to use a larger horsepower motor than the horsepower of the largest inverter. To enable the coordination between two SA3100 inverters, both inverters must be connected to the same UDC card (the A-channel inverter is defined as the master unit). Register 700/1700 bit 14 must be asserted in each inverter.

The drives can be commissioned in the normal fashion, however, the resulting IGN table from the A-channel inverter will be copied to the B-channel inverter. After commissioning, both IGN tables are identical for the two drives. The application task in the UDC will copy registers 217 and 218 from the A-channel inverter to registers 1104 and 1107, respectively.

D.1.2 Handshake Registers

After the inverters have been initially tuned, the VOA enable bit (bit 6 of register 1100) must be set while the inverters are running. This bit causes the B-channel inverter to follow the A-channel inverter vector orientation. The B-channel inverter indicates that it is successfully following the A-channel inverter by asserting the VOA_OK@ bit (bit 7 of register 1200).

The configuration data for the drives is also modified. As mentioned above, the Dual Winding bit is set in register 700/1700. The value in register 706 is set to 15. The value in register 1706 is set to 16. The motor nameplate horsepower and current is divided by two and set appropriately in the configuration registers. Note horsepower is in watts divided by 10 units.

Table D.1 – Dual Wound Motor Handshake Registers

Register Number Normal Configuration Dual Wound

217 RPM Feedback ID Reference

218 Slip Frequency Vector Orientation

1104 Auxiliary Reference Id Reference

1107 - Vector Orientation

Vector with Constant Power Regulator D-3

D-4 Drive Configuration and Programming

APPENDIX EVolts per Hertz (V/Hz)

Regulator

The SA3100 volts per hertz regulator (figure E.1) uses an application dependent V/Hz characteristic curve to control the output voltage for a commanded frequency. The drive’s output voltage varies with output frequency according to the V/Hz characteristic curve, when operating in the constant torque region (V/Hz = constant). Constant power and variable torque characteristics are supported.

The volts per hertz regulator supports a frequency range of 0 to 600 Hz. Constant power, constant torque, and variable torque V/Hz characteristics are supported. In the constant torque range (0 Hz to 600 Hz), a constant ratio of voltage/frequency (V/Hz) provides, generally, a constant motor torque. Constant power may be selected from 15 Hz to 600 Hz, enabling constant torque operation from 0 Hz to 15 Hz, and constant power operation from 15 to 600 Hz.

The regulator provides selection of either synchronous carrier operation or fixed carrier frequency, asynchronous carrier operation. It also provides for specification of an adjustable frequency ramp rate to limit the rate of change in the frequency output. The application task in the UDC controls frequency, rate of change of frequency, minimum frequency, avoidance frequencies, and voltage boost1.

At low frequencies, constant torque operation cannot be maintained without an increase in the voltage applied to the motor terminals. Voltage boost is used to modify the linear V/Hz characteristic at low frequencies by specifying the amount of voltage increase at a specific frequency.

To support increased breakaway torque, an offset voltage may be specified at zero hertz. The offset voltage increases the voltage at zero frequency by the amount of the offset voltage specified. This offset voltage function offsets the origin of the V/Hz characteristic curve.

The open loop SA3100 V/Hz inverter may be used in closed loop configurations, such as slip loop control by using the Frequency and Boost Voltage1 command inputs. Slip loop control uses rotor speed feedback to command the base operating frequency of the V/Hz inverter. Speed error is used to control the addition, or subtraction, of a limited frequency to the base operating frequency, as well as providing a boost voltage to the output.

The option of current limit uses monitored phase currents to control the inverter operating frequency as required by the application. A current IET is provided to protect the inverter from destructive currents.

1. The term “voltage boost” refers to a change to the volts per hertz characteristic (i.e., a change on the curve). “Boost Voltage” is an auxiliary voltage command augmenting the regulator output.

Volts per Hertz (V/Hz) Regulator E-1

When required the V/Hz curve is defined by the specification of 7 points of voltage and frequency, as shown in the figure E.2 for constant torque, and figure E.3 for variable torque. The user interface provides a default set of these points based on the parameter entry selected. The user can modify these points to satisfy specific application requirements (see chapter 2).

E-2 SA3100 Drive Configuration and Programming

Figure E.1 – Volts/Hertz Control Regulator Block Diagram

Fre

quen

cy R

efer

ence

6000

00 =

= 6

00H

zIn

tern

al R

amp

Vol

ts p

er H

ertz

Cha

ract

eris

tic

V o l t s

Her

tz

Sca

ling

Vol

tage

per

DC

Bus

vol

tage

Sca

ling

of th

efr

eque

ncy

com

man

d

Vec

tor

Rot

ator

and

Con

vers

ion

to 3

-Pha

se

P W M

Rat

e Li

mite

dF

requ

ency

Ref

eren

ce

Vol

tage

Ref

eren

ce

Fre

quen

cyR

efer

ence

VQ

_RE

F

VD

_RE

F

NU

LL

Vu

Vv

Vw

Iu U

pper

Iv U

pper

Iw U

pper

Iu L

ower

Iv L

ower

Iw L

ower

C

T

CT=

TU

NA

BLE

OR

AF

FE

CT

ED

BY

TU

NA

BLE

= D

ER

IVE

D F

RO

M C

ON

FIG

UR

AT

ION

PA

RA

ME

TE

R

KE

Y

Volts per Hertz (V/Hz) Regulator E-3

Figure E.2 – Constant Torque Volts/Hertz Curve

Figure E.3 – Variable Torque 7-Point Volts/Hertz Curve

F6F4 F5F3F2

Frequency

Output Volts

1 2 3 4 5

6

F0 F1

V5 V6

Constant Voltage Frequency(15, 30, 50, 60, 120, 240, 400, 600 etc.)

ConstantPowerRange

ConstantTorqueRange

MaxFrequency

V4

V3

7

V0V2V1

P0

P2

P3

P1

P5

P4

P6

Nameplate(V/Hz)

F6F4 F5F3F2

Frequency

Output Volts

1 2 3 4 5 6

V6

Constant Voltage Frequency = Max Frequency(15, 30, 50, 60, 120, 240, 400, 600 etc.)

ConstantTorqueRange

V4

V3

7

P0

P2

P3

P1

P5

P4

P6

V5

V1

V0V2

F1F0

Nameplate(V/Hz)

E-4 SA3100 Drive Configuration and Programming

APPENDIX FStatus of Data in the AutoMax

Rack After a STOP_ALLCommand or STOP_ALL Fault

AutoMax Processor UDC Module PMI Processor

LOCAL tunable variables retained retained retained

LOCAL variables retained reset to 0 N/A

COMMON memory variables non-volatile are retained;others are reset to 0

N/A N/A

I/O variables(including UDC dual port memory

inputs retained and updated; outputs are reset to 0

inputs retained and updated; outputs are reset to 0

all I/O is reset to 0

Input values, including:Feedback registersUDC/PMI communication status registersUDC Error Log info

retained retained N/A

Output values, including:Command registersApplication registersISCR registersScan-per-interrupt registerScans-per-interrupt counter

reset to 0 reset to 0 N/A

Parameter configuration variables N/A retained N/A

UDC test switch information N/A retained N/A

D/A setup configuration N/A retained N/A

Operating system retained retained retained

Status of Data in the AutoMax Rack After a STOP_ALL Command or STOP_ALL Fault F-1

F-2 SA3100 Drive Configuration and Programming

APPENDIX GTorque Overload RatioParameter Precautions

The maximum RMS current that will be generated by the Power Module based on the entered Torque Overload Ratio must be within the limits of the selected Power Module or a warning will be generated:

* Power Module Rated Amps for the selected Power Module.

In some cases, however, the internal limit checking rules may be too conservative and generate a warning even when the Power Module Rated Current and Torque Overload Ratio values are consistent. It is not unusual for an application to momentarily exceed the continuous full load current rating of the Power Module, e.g., 150% for one minute.

When the Power Module continuous current rating is exceeded, it is the responsibility of the application programmer to ensure that the maximum Power Module RMS current rating is not exceeded. The above warning provides a flag to the user to check that the proper application programs are in place to protect the Power Module by not exceeding the maximum Power Module ratings.

The data entered by the programmer is checked by multiplying the Motor Full Load Current by the specified Torque Overload Ratio. If the resulting current exceeds the current rating of the Power Module, the warning is displayed. The checking algorithm assumes that motor current and torque are proportional, although this may not be completely accurate.

Internal limit checking for this parameter cannot be performed more accurately because the magnetizing component of the current (Iz) is not available until tuning is enabled in the PMI Regulator. Tuning, in turn, cannot be performed until the parameter object file and UDC task have been loaded to the UDC.

In order to determine if it is permissible to proceed with the application data entry when the warning appears, a more accurate approximation of the maximum RMS current that is required for a specific Torque Overload Ratio level may be obtained by applying the following equation for the current vector magnitudes:

∗

Torque Overload Ratio Parameter Precautions G-1

Maximum RMS Current = Square Root of [(%Torque_Overload_Ratio/100)2 x (Rated_Motor_Current2 - Iz2) + Iz2]

Iz is the magnetizing current component of the Power Module output stored in local tunable variable STATOR_IZ_E1%. The value for this variable can be generated by enabling tuning in register 100/1100, bit 1. Note that you must load a complete parameter object file and UDC task to the UDC module before you can enable tuning.

If the calculation of the Maximum RMS Current is less than or equal to the Power Module Rated Amps at the selected carrier frequency, the programmer may continue entering the application data.

If the calculated Maximum RMS Current exceeds the Power Module Rated Amps, refer to the actual motor data sheets to determine the actual current required by the motor for the required Torque Overload Ratio. If the required current exceeds the Maximum Power Module Current Rating, a higher rated Power Module must be used.

G-2 SA3100 Drive Configuration and Programming

APPENDIX HDefault Carrier Frequency and

Carrier Frequency Limit forDrive Horsepower Ranges

HP Range Default Carrier Frequency Carrier Frequency Limit

1-3 4kHz 1-12kHz

7.5-30 4kHz 1-12kHz

40-60 4kHz 1-12kHz

75-125 2kHz 1-6kHz

150-250 2kHz 1-6kHz

300-500 2kHz 1-4kHz

600-650 1.5kHz 1-4kHz

800 1.5 kHz 1-4 kHz

Default Carrier Frequency and Carrier Frequency Limit for Drive Horsepower Ranges H-1

H-2 SA3100 Drive Configuration and Programming

APPENDIX IVector with Constant Power

Parameter Entry Example

390V

460 V

318 375 700 1100 1200

Base S1 S2 S3 S4

Overload Torque628 ft lb

506 ft lb

Volts

425 ft lb

373 ft lb

220 ft lb

230A

280A

314AAmps

390

460

Rated Motor Voltage

Maximum Motor Voltage

5Total Current Rating Points

BaseS1S2S3S4

318375700

1100

Speed Current

314280270260

Overload

2001901601501502301200

RPM

Rated Torque

260A

314 ft lb

266 ft lb

265 ft lb

248 ft lb

270A

Vector with Constant Power Parameter Entry Example I-1

Commissioning Procedure for Non-Constant Power Algorithim Operation J-1

APPENDIX JCommissioning Procedure

for Non-Constant PowerAlgorithim Operation

Background

The SA3000 and SA3100 AC vector control drives utilize the same control algorithm. This control algorithm contains a constant power algorithm to provide for load changes such as temperature. It is possible to configure both the SA3000 and SA3100 to NOT utilize this constant power algorithm.

Note: If other algorithms are selected, they should be commissioned using the procedure outlined in the manual, as the drive must always be commissioned by a procedure to set the proper magnetizing current for the motor.

The procedure for Constant Power Commissioning is outlined in the readme files of the DPS product, and the present procedure is explained later in this chapter.

Current Procedure - The present procedure is undertaken after the PMI has calculated its gains (PMI Tune - caused by asserting bit 1 of register 100/1100). This procedure entails running the motor at a specific set of speeds. At these speeds, a bit is asserted by the operator, and the drive will sample the magnetizing current for the motor at this time.

New Procedure Explanation - This new procedure expands on the present procedure by adding steps that must be taken at the first speed point. Currently the first speed point is at 40% of the maximum voltage speed of the motor. With the new procedure, at the first point the speed will be altered to cause the drive to go to synchronous speed. The no-load motor voltage will be sampled and used for calculating motor parameters. The speed is then returned to the first point speed value. The procedure continues from that point in the same fashion as the present procedure.

New Procedure Revision 22E - The operations that make up this new revision, are excercised at the first speed point. After the data is aquired at the first point, the remainder of the commissioning procedure is the same.

At the first speed point - 40% of max voltage speed - assert the ‘tune iz’ bit (bit 10 of register 101/1101). During this new procedure, you will monitor the following new status bits: bit 12 of register 201/1201 “Synchronous Speed Reached”, and bit 13 of register 201/1201 “Alter Speed”. Observe the “Alter Speed” bit, when the bit becomes asserted, command the motor to go to synchronous speed (synchronous speed is equal to 120* rated frequency/number of motor poles eg. for a 60Hz, 4 pole motor synchronous speed as 120*60/4 =1800 RPM). When the drive achieves this speed, the “Alter Speed” bit will become zero. The “Syncronous Speed Reached” bit will be asserted. Observe the “Alter Speed” bit. When it is asserted, command the motor to return to the first-point speed.

J-2 SA3100 Drive Configuration and Programming

Note: You must observe the “Alter Speed” bit and modify the motor speed two times: once to accelerate the motor to synchronous speed and once to cause the motor to return to the first-point speed. Observe the “Alter Speed” bit and modify the motor speed two times: Once to accelerate the motor to synchronous speed and once to force the motor to return to the first-point speed. After the motor has returned to the first point speed, observe the “tuned iz” bit (bit 10 of register 201/1201). When this bit is asserted, the first point tuning has been accomplished. Now, the additional points which are required by the application can be aquired in the same fashion as the present procedure.

NOTE: While implementing the new procedure you should monitor the warning register for bit 5 “Tune Aborted”. If this warning appears, start the commissioning procedure over again from the first speed point.

Step by Step Commissioning Procedure

Step 1. With the drive’s motor disconnected, set bits 0 and 1 of register 101/1101. Register 101 is for drive A and register 1101 is for drive B. Drive B can be setup by using the register number for Drive A plus 1000.

The remaining steps use Drive A as the example.

Step 2. Command the speed loop to the appropriate speed reference.

If this is the first speed point, Do the following:

A. When the speed is reached, set bit 10 of register 101 in the UDC.

B. Monitor the “Alter Speed” status bit (bit 13 of register 201). When this bit is set, modify the commanded speed to cause the motor to go to synchronous speed. (Synchronous speed is equal to 120* rated frequency/ number of motor poles eg. for a 60Hz, 4 pole motor synchronous speed as 120*60/4 = 1800 RPM.)

C. When the motor achieves synchronous speed, the “Alter Speed” bit will become reset, and another bit, the “Synchronous Speed Reached” (Bit 12 of register 201) becomes set.

D. Observe the “Alter Speed” status. When this bit becomes asserted, it Commands the motor to return to the first speed point.

E. Monitor register 203. If register 203 contains a hex value of 20, reset the warning, and try step two again.

F. If bit 10 of register 201 was set, reset bit 10 in register 101 and continue with the next speed point as described in step 3. When all the required speed points have been completed, go to Step 8.

Step 3. When the speed is reached, set bit 10 of register 101 in the UDC.

Step 4. Monitor register 203 and bit 10 of register 201.

Step 5. If register 203 is set to hex 20, reset bit 10 of register 101 and go to step 7.

Step 6. If bit 10 of register 201 was set, reset bit 10 in register 101 and continue with the next speed point as described in step 3.

Step 7. If register 203 contains a hex value of 20, verify that the speed scaling of the speed loop is correct and refer to the Notes at the end of this Appendix. Reset the warning, continue with the next point as described in step 3.

Step 8. Reset bits 0 and 1 of register 101.

NOTE: The values saved in the IGNn! variables will be in (amps*100) units.

Note that in Dual Wound Motor Applications (Parallel Inverter Drives) you must use the procedure described above with the following additions:


• After using the reference point data for Drive A (register 101), use the reference point data for Drive B register (1101).

• Ensure that the vector orientation alignment request bit (bit 6, 0040h) is set in register 1100.

• The IGNn! values for the A and B drives should be the same. The acquisition of data should be done with both drives to verify that the magnitudes of the values are similar. After the acquisition is done, the IGNn! values from Drive A should be used for Drive B.

Present Commissioning Procedure - SA3000 AC Vector w/ Constant Power:

Tuning the Magnetizing Current Reference Table - The latest version of the SA3000 Constant Power Operating System has the capability of accomodating temperature changes via modification of the slip value. This modification of the slip value is accomplished through the use of a PMI reference magnetizing current table. It enables the PMI to determine when a load change has occurred. When a load change occurs, the output of the flux loop will increase. This increased output is compared to the value from the reference table. The difference between the two generates a change in slip. The change in slip causes a reduction in flux loop output, which in turn, cause the flux loop output to be the correct value for the magnetizing current value at that point in the speed range.

In order to tune or calibrate this table, a speed loop must be implemented in the UDC module. This speed loop must be set up so that a value of 4095 counts of speed reference corresponds to the maximum speed of the drive (i.e. four times the maximum voltage speed).

Using this speed loop, it is possible to utilize a maximum of 10 points in the speed reference curve. You will need all ten reference points if you are using a four to one range in your application. You do not need to use all ten reference points if your application does not reach the four to one speed range. The following table indicates the speed reference points at which data is obtained.

Ref. Point Speed Reference Counts Value Save Location Units

One 409 Stator_ iZ_e1% (RMS amps * 10)

Two 1023 (equal to max v speed) IGN1! (Note peak amps* 100)

Three 1125 IGN2!

Four 1227 IGN3!

Five 1329 IGN4!

Six 1635 IGN5!

Seven 1941 IGN6!

Eight 2247 IGN7!

Nine 2859 IGN8!

Ten 4095 IGN9!

J-4 Drive Configuration and Programming

For a 2 to 1 range; reference points one, two, three, four, five, six and seven are used.

For a 3 to 1 range; reference points eight and nine are also used.

For a 4 to 1 range; reference point ten is also used.

Note that PMI operating system version requires internal gain tunables IGN1! to IGN9! for retention of the table data.

(IGN ==> Internal Gain)

Use the following procedure to implement each reference point in the speed loop calculation:

Step 1. With the drive’s motor unconnected, set bits 0 and 1 of register 101/1101. Register 101 is for Drive A and register 1101 is for Drive B. Drive B can be setup by using the register number for Drive A plus 1000.

The following steps will use Drive A for this example.

Step 2. Command the speed loop to the appropriate speed reference.

Step 3. When the speed is reached, set bit 10 of register 101 in the UDC.

Step 4. Monitor register 203 and bit 10 of register 201.

Step 5. If register 203 is set to hex 20, reset bit 10 of register 101 and go to step 7.

Step 6. If bit 10 of register 201 was set, reset bit 10 in register 101 and continue with the next speed point as described in step 3. When all the required speed points have been completed, go to step 8.

Step 7. If register 203 contains a hex value of 20, verify that the speed scaling of the speed loop is correct and refer to the Notes at the end of this appendix. Reset the warning, and continue with the next speed point as described in step 3.

Step 8. Reset bits 0 and 1 of register 101.

Note: The values saved in the IGNn! variables will be in (amps*100) units.

Note that in Dual Wound Motor Applications (Parallel Inverter Drives) you must use the procedure described above with the following additions:

• After using the reference point data for Drive A (register 101), use the reference point data for Drive B register (1101).

• Ensure that the vector orientation alignment request bit (bit 6, 0040h) is set in register 1100.

• The IGNn! values for the A and B drives should be the same. The acquisition of data should be done with both drives to verify that the magnitudes of the values are similar. After the acquisition is done, the IGNn! values from Drive A should be used for Drive B.


Reference Material - The following information describes step by step processor functions for the new commissioning procedure.

1. Calculate the necessary motor parameters and variables initially based on the following equations: (This represents the action taken when the PMI tune function is invoked (bit 1 of register 100/1100)).

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

1.

2. Run the algorithm with the closed flux loop using the flux reference (4) directly in the final stator flux reference point. Run the drive at the 40% speed point.

The result of this step is obtaining the first iteration of a rated magnetizing current Iz_rtd_1 by measuring an output of a flux regulator through an averaging procedure (at least a 1000 scan time sampling interval). Recalculate expression (2), (3), and (5) - (9) based on new value of the flux producing current Iz_rtd_1.

3. Disable the flux loop. Set output of a flux regulator. Id_ref = √2⋅Ι z _ rtd _ 1 = Id _ rtd

_ 1. Run drive on a synchronous speed with no load condition and make a measurement of motor voltage through an averaging procedure (at least a 1000 scan time sampling interval). This motor voltage is a rated no load motor voltage VNL _ rtd.

Iz_rtd_start (amps) = 3 . Ist _ rtd746 * HP rtd

V mot _ rtd

(magnetizing current) ( 1 )

Id_rtd_start (amps) = 2 . Iz _ rtd_start (flux producing current) ( 2 )

Iq_rtd_start (amps) = 2 . I2st _ rtd _ I2d _ rtd _ start (torque producing current) ( 3 )

Ψref_start (wb) = 0.97 . 2 . V mot _ rtd

3 . 2 . π . f0

(stator flux reference) ( 4 )

Rr0_start (ohms) = 551 . HPrtd . (RPM synch - RPM rtd)

RPMrtd . I

2q_rtd_start

Rst0_start (ohms) = 1.3 . Rr0_ start

(rotor resistor for therated temperature)

(stator resistor for the rated

( 5 )

temperature) ( 6 )

Ψr_rtd_start (wb) = 227 . HPrtd . V mot_rtd . Ist_rtd

p . RPMrtd . Ι q _ rtd _ start

(rated rotor flux) ( 7 )

Lm0_start(H) = Ψr_rtd_start

Ιd _ rtd _ start

(mutual inductance) ( 8 )

L*σs _ start = 0.05 . Lm0 _ start (modified leakage inductance) ( 9 )

where:HPrtd - Motor rated horsepowerVmot_rtd - Rated motor line - to - line voltage (RMS)

Ist_rtd - Rated motor phase stator current (RMS)

f0 - Rated stator frequency (Hz)p - pole pairs


4. Calculate the remainder of the necessary motor parameters using the following measurements:

5. Run the full algorithm with the parameters calculated above with flux loop and access the table starting with the first point. The first point is the rated d-component current Id_rtd. The value of this current must satisfy the following inequality:

6. If the inequality in #17 is true, then continue to access the table. If the inequality (17) is not true then recalculate all the motor parameters with new Id_rtd and rerun.

System architecture allows only three parameters to be saved.

Ls0 = 2 V NL_rtd

V2 mot _ rtd

(stator inductance) ( 10 )

Id_rtd_1

(q - component voltage) ( 11 )Vq_rtd = OLR . Iq _ rtd _ 1 Rst _1 +

2 . π . f0

( 12 )

Rst_1OLR . I q _ rtd _ 1

Vd_rtd _ 1

( 16 )

=

=

( 14 )

..

. 2

3.V NL _ rtd

q - component voltage has to satisfy the following inequality:

2

3

.

V mot _ rtd V q _ rtd > 2

If the above inequality (12) is true then Vq_rtd can be used for further calculations.

If the expression (12) is not true then the following assumption has to be set:

( 15 )

2

3V mot _ rtd

V mot _ rtd

Vq_rtd =

V NL _ rtd

. ( 13 )2.5

and stator resistance has to be recalculated using the follow equation:

2

3( ) 2

32.5 .

Then d-component voltage and modified leakage inductance can be calculated:

23

. V2q _ rtd _ 1

L*σs 0 =Vd _ rtd _ 1 + Id _ rtd _ 1 . Rst _ 1

2 . π . f0 OLR . I q _ rtd _ 1.

( 17 )Id_rtd - Id _ rtd _ 1

Id _ rtd

. 100% < 2%

( 18 )l stator time constant: Tst =L*σs 0

Rst _ rtdl stator resistor: Rst _ rtd

l magnetizing current: Iz _ rtd


It is necessary to recalculate all algorithm coefficients and variables based on motor nameplate data and the above three parameters.

The equation set which allows this to be accomplished is shown below:

NOTES: In some cases, the approximation from the PMI tune function for the STATOR_IZ_E1% value causes the flux loop to go into saturation. This condition can be recognized if the tune abort warning occurs immediately upon asserting the tune iz bit when at the first speed point. To compensate for this condition, the operator can observe the Flux Reference and Flux Feedback signals via the power module meter ports. The digitized value for the fourth port is available to a register (219 / 1219 - SEL_VAR%). The value of STATOR_IZ_E1% can be modified online until the reference and feedback are approximately equal. When the two signals are approximately equal, the value of “Id current reference counts” (observed via the power module meter ports) should be changing. When this state is acheived, the commissioning procedure may continue.

Id_rtd = 2 Iz_rtd

Iq_rtd = 2

Rst_0 = Rst_rtd

.

. I 2st_rtd

(RPM synch - RPM rtd)551 HP rtd

Lm 0 =

I 2d_rtd

Rr 0 = Rr_rtd =. .

RPM rtd - I 2q _ rtd

Ψr_rtd_start (wb) = 227 HPrtd . V mot_rtd . Ist_rtd

p . RPMrtd . Ι q _ rtd

.

Ψr_rtd

Id_rtd

L*σs 0 = Tst .Rst_rtd

Ls 0 = Lr 0 = Lm 0 + L*σs 0


This Page Intentionally Blank

I-2 SA3100 Drive Configuration and Programming

INDEX

A

Access, 3-3Application programming, 4-1 to 4-10

AutoMax and UDC task coordination, 4-9AutoMax tasks, 4-1calculating local tunable values, 4-7data/time flow for UDC and PMI, 4-10Flex I/O port registers, 3-6local tunable variables, 4-6 to 4-7recommended run permissive logic, 4-9typical structure of a UDC task, 4-3 to 4-6UDC task scan, 4-2UDC tasks, 4-1 to 4-10UDC/PMI task communication, 4-7 to 4-10

Application registers, 3-50 to 3-51AutoMax rack

status of data, F-1

B

Bit Name, Bit Number, 3-3

C

Carrier frequency and HP ranges, H-1Command registers, 3-19 to 3-26

boost voltage (V/Hz), 3-25bridge test code, 3-26DC braking reference, 3-26drive control, 3-19 to 3-22flux reference (vector), 3-25frequency reference (V/Hz), 3-25I/O control, 3-22 to 3-24PMI D/A output, 3-26synchronous transfer volts, 3-26torque reference (vector), 3-25

Configuration views and registers, 3-4Configuring drive parameters, 2-1 to 2-25

configuration data setup (V/Hz), 2-18 to 2-19constant magnetization (vector), 2-7 to 2-8constant power (vector), 2-7, 2-9 to 2-11control data (V/Hz), 2-21 to 2-22entering drive parameters, 2-3 to 2-4feedback (vector), 2-12 to 2-13feedback and control (V/Hz), 2-21 to 2-22

Flex I/O, 2-3, 2-24 to 2-25generating drive parameter files, 2-25manual compensation (vector), 2-7 to 2-8meter port selection (V/Hz), 2-22 to 2-23meter port selection (vector), 2-14 to 2-15motor data (vector), 2-6 to 2-11power module (V/Hz), 2-16 to 2-17power module (vector), 2-5 to 2-6printing drive parameters, 2-25resolver data, 2-12 to 2-13rules for configuring/selecting drives, 2-2UDC module, 2-1 to 2-2V/Hz characteristic, 2-20 to 2-21vector with constant power, 2-5 to 2-15volts per hertz, 2-16 to 2-23

Configuring UDC registers, 3-1 to 3-63

D

Documentation, 1-2Dual port memory register organization, 3-5

F

Faultsdrive faults, 3-32 to 3-36Flex I/O module 0 and module 1, 3-9Flex I/O module 2, 3-10

Feedback registers, 3-27 to 3-49carrier frequency (V/Hz), 3-47current feedback (amps rms), 3-45current feedback normalized (vector), 3-45,

3-46DC bus current (amps), 3-44DC bus voltage (volts), 3-44diagnostic fault code, 3-48 to 3-49drive fault, 3-32 to 3-36drive status, 3-27 to 3-29drive warning, 3-36 to 3-39ground current feedback (amps), 3-45I/O status, 3-30 to 3-32Id feedback normalized (vector), 3-45interlock, 3-42 to 3-44Iq feedback normalized (vector), 3-46output frequency (V/Hz), 3-46power device status, 3-39 to 3-42

Index Index-1

resolver scan position, 3-46resolver strobe position, 3-46revolutions per minute, 3-47selected variabler, 3-47slip feedback (vector), 3-47user analog input, 3-46volt command (V/Hz), 3-45voltage feedback (volts rms), 3-45

Flex I/Oadding to the drive, 2-3analog data formats, 3-8configuring, 2-24 to 2-25digital data formats, 3-7Flex I/O port registers, 3-6 to 3-10module 0 and module 1 faults, 3-9reserved Flex I/O registers, 3-6status and error codes, 3-9 to 3-10

G

Generating drive parameter files, 2-25

H

Hex Value, 3-3

I

Interrupt status and control registers, 3-61 to 3-63interrupt status control, 3-61 to 3-62scans per interrupt, 3-63

Interrupts, 4-3, 4-8Introduction, 1-1 to 1-4

L

LED, 3-3Local tunable variables, 4-6 to 4-7, C-1 to C-10

calculating local tunable values, 4-7current minor loop gain, C-1 to C-2DC bus, C-8 to C-9diagnostic, C-10resolver balance and gain, C-9 to C-10V/Hz frequency point gain, C-6 to C-7V/Hz voltage point gain, C-5 to C-6vector algorithm gain, C-2 to C-4

M

Meter ports, 3-55 to 3-60

configuration, 2-14 to 2-15initiate change in setup register, 3-56meter port 1, 3-57meter port 2, 3-58meter port 3, 3-59meter port 4, 3-60parameters, 2-15, 2-23resolution of meter port data, 3-56 to 3-60

N

Nth scan interrupts, 3-52

O

On-line operation, 5-1 to 5-3deleting UDC tasks, 5-3loading drive parameters, 5-1 to 5-2loading the UDC operating system, 5-1loading UDC tasks, 5-1 to 5-2running UDC tasks, 5-2stopping UDC tasks, 5-2UDC information and error logs, 5-3

P

Printing drive parameters, 2-25

R

Range, 3-3Register Name, 3-3Register Numbers, 3-3Register/bit reference conventions, 3-3 to 3-5Related publications, 1-2 to 1-4Resolver

12-bit resolvers, 2-13balance and gain variables, C-9 to C-10capacitance for resolver balancing, C-9configuration data, 2-12 to 2-13

Run permissive logic, 4-9

S

Screens for parameter entryadding a UDC module, 2-2configuration data setup (V/Hz), 2-18control data (V/Hz), 2-21drive parameter (vector), 2-4feedback and control (V/Hz), 2-21

Index-2 SA3100 Drive Configuration and Programming

feedback data (vector), 2-12Flex I/O, 2-24meter port selection (V/Hz), 2-22meter port selection (vector), 2-14motor data (vector), 2-6, 2-9power module data (V/Hz), 2-16power module data (vector), 2-5V/Hz characteristic, 2-20

Service manual cross reference, 1-2 to 1-4Sug. Var. Name, 3-3

T

Torque overload ratio parameter precautions, G-1

U

UDC Error Code, 3-3UDC module

adding, 2-1 to 2-2initiate change in setup register, 3-56meter port setup registers, 3-55 to 3-60test I/O registers, 3-53 to 3-60test switch inputs register, 3-53 to 3-54

UDC task scan, 3-50, 4-2UDC/PMI communication status registers, 3-11 to

3-18PMI communication status, 3-14 to 3-17PMI CRC error count, 3-17PMI format error count, 3-17PMI receive count, 3-17UDC communication status, 3-11 to 3-13UDC CRC error count, 3-14

UDC fiber-optic link status, 3-18UDC format error count, 3-14UDC receive count, 3-13UDC transmitted message count, 3-18

V

Variable configurator, 3-1Vector with constant power regulator

block diagram, D-2configuring, 2-5 to 2-15control algorithm, D-1 to D-2parameter entry example, I-1register reference, A-1 to A-2

Viewing registers, 3-1 to 3-2application registers, 3-2command registers, 3-2feedback registers, 3-2interrupt status and control registers, 3-2Port 0 Flex I/O, 3-1UDC module test I/O register, 3-2

Volts per hertz regulatorblock diagram, E-3configuring, 2-16 to 2-23constant torque curve, E-4control algorithm, E-1 to E-4register reference, B-1 to B-2variable torque 7-point curve, E-4

W

Warnings, 3-36 to 3-39

Index Index-3

Index-4 SA3100 Drive Configuration and Programming

Rockwell Automation / 24703 Euclid Avenue / Cleveland, Ohio 44117 / (216) 266-7000

Printed in U.S.A. S-3056-1 July 1999

distributed power system sa3100 drive configuration and programming · 2015-10-03 · 1-2 sa3100...

Documents