Parker Variable Speed Drive AC30 series. User’s Manual (2017)

A-5

Fieldbuses

USER-DEFINED PARAMETER MAPPING

The inverter parameters may be mapped to the user-defined register area (00001 – 00256). This allows parameters to be grouped together so
that they may be accessed through a single Modbus request.

To map parameters add the required parameter numbers to the user mapping table using parameter

1567 Modbus Mapping

. The following

applies:

•

The mapping starts at register 00001.

•

Any valid fixed or application parameter may be added excluding password parameters and parameter arrays - individual elements of the
array may be added however.

•

Parameter strings may be added.

•

The mapping ends on the first mapping entry of zero or when the mapping table is full.

Note:

The mapping may be modified at any time. However no Modbus requests should be made when the mapping is being modified to avoid

indeterminate response data.

Unlike the fixed mapping, the user-defined parameter mapping will only use as many registers as necessary to accommodate the parameter. An
example is given below:

Mapping Table

Parameter Name

Data Type

No. of Registers

Start Register

End Register

0627 Comms Control Word

WORD

00001

0681 Comms Reference

REAL

00002

00003

0696 First Trip

USINT

00004

0661 Status Word

WORD

00005

0395 Actual Speed Percent

REAL

00006

00007

0961 Drive Name

23-character STRING

00008

00019

0000

The mapping table is continually checked for valid entries. The diagnostic parameter

1632 Mapping Valid

will be TRUE if all entries in the table

are valid parameters. If the diagnostic parameter is FALSE, meaning there are invalid entries, then Modbus requests are still accepted but the
invalid entries will be skipped over and will occupy no registers in the mapping.

Fieldbuses

A-6

The following applies to user-mapped parameters:

•

If the parameter has a data type that uses one byte then it will occupy the low byte of the Modbus register and the high byte will be zero,
i.e. the register will not be sign extended.

•

The word order of 32-bit parameters is determined by the inverter parameter

0940 High Word First

•

Writable 32-bit parameters will only accept a change in value if

both

registers mapped to the parameter are written to in the same

request.

•

String parameters are packed into the registers

low byte first

•

Writable string parameters will only accept a change if the first register is included in the request. If the string is not null terminated, then
a null termination will be added automatically.

PASSWORD PROTECTION

Write access to parameters via the fixed mapping registers may be restricted by setting the parameter

1659 Modbus TCP Password

Note that there is no restriction to parameters via the user-defined mapping registers.

When this password is set to a value other than zero, writing to parameters will only be possible when the password is unlocked. If the password
is not unlocked then writes will be ignored.

To unlock the password write to the Modbus register

00518

the value set in the parameter 1659 Modbus TCP Password. Write access

will be available until a subsequent write to the Modbus register 00518 of value 0000.

Note the following:

•

A read of Modbus register 00518 will always respond with a value of 0000 regardless of the password being locked or unlocked.

•

Locking and unlocking the password will apply to all Modbus connections.

•

When all Modbus connections are closed, write access will returned back to the locked state if a password is set.

A-7

Fieldbuses

SUPPORTED MODBUS FUNCTIONS

Four Modbus functions are supported:

Read Holding Registers (#3)

This function allows multiple Input registers to be read. Up to 125 registers may be read. As the Holding registers and Input registers map to the
same inverter parameters this will return the same values as the Read Input Registers function.

Read Input Registers (#4)

This function allows multiple Holding registers to be read. Up to 125 registers may be read. As the Holding registers and Input registers map to
the same inverter parameters this will return the same values as the Read Holding Registers function.

Write Single Register (#6)

This function allows a single Holding register to be written to. Note that this function may only be used on registers that map to 1-byte or 2-byte
inverter parameters. An attempt to write to a register that maps to a 4-byte parameter will have no effect on the parameter.

Write Multiple Registers (#16)

This function allows a contiguous block of Holding registers to be written to. Up to 120 registers may be written. Note that when writing to
registers that map to 4-byte inverter parameters both registers must be written to. Writing to one-half of a 4-byte parameter will have no effect on
the parameter.

Fieldbuses

A-8

MODBUS EXCEPTION CODES

Three Modbus exception codes are supported:

Illegal Function (01)

The Modbus function is not supported by the slave.

Illegal Data Address (02)

If the register data address contained in the Modbus request maps to an inverter parameter that is outside the range of parameter numbers then
this exception will occur.

Illegal Data Value (03)

If the number of bytes or words contained in the Modbus request field is out of range then this exception will occur.

PROCESS ACTIVE AND LOST COMMUNICATIONS TRIP

Process Active Flag

The Process Active flag is represented by the inverter parameter

0943 Process Active

. This parameter changes to TRUE on the first valid

Modbus request.

If the parameter

0941 Modbus Timeout

is set to a non-zero value then the

Process Active

parameter will subsequently change to FALSE if a

Modbus request is not received within the timeout period.

Trip

If enabled, a break in the Modbus communications can be used to generate a trip. The

0943 Process Active

parameter is used to generate the

trip. If this parameter transitions from TRUE to FALSE then a trip will event will be generated.

To enable the base communications Modbus trip, the parameter

0942 Modbus Trip Enable

must be set to TRUE

and

the

BASE MODBUS

BREAK

bit set in the parameter

0697 Enable 1-32

. The parameter

0941 Modbus Timeout

must be set to a value other than zero.

For information on enabling trips see Chapter 10 Trips & Fault Finding.

Connection Timeout

The parameter

1241 Open Connections

indicates the number of open connections to the inverter Modbus TCP server.

A connection receive timeout may be set using the parameter

1458 Modbus Conn Timeout

. If this is set to a value other than zero, then the

connection will be closed by the server if no data has been received within the timeout period. This is useful, for example, if the link between the
server and client is lost, otherwise the connection may remain open indefinitely.

A-9

Fieldbuses

PARAMETER SUMMARY

The following parameters are relevant to the Modbus TCP.

Parameter Name

No.

Path

Default

Range

Writable

Maximum Connections

0939

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

0 - 3

ALWAYS

Modbus TCP parameter.

Sets the maximum number of Modbus clients allowed. If set to zero, then no connections will be allowed.

High Word First

0940

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

FALSE

TRUE

ALWAYS

Modbus TCP parameter.

If set to TRUE, the most significant word of a 32-bit parameter will be mapped to the first register, and the least significant word to
the next register.

Modbus Timeout

0941

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

3.0 seconds

0.0 – 65.0 seconds

ALWAYS

Modbus TCP parameter.

Sets the process active timeout.

Modbus Trip Enable

0942

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

TRUE

FALSE

TRUE

ALWAYS

Modbus TCP parameter.

Set TRUE to enable the Modbus Trip. The parameter Modbus Timeout must be set to a value other than zero

Open Connections

1241

Monitor::Communications::Base Modbus

Parameters::Base Comms::Modbus

0 - 3

NEVER

Modbus TCP parameter.

Indicates the number of open connections to the inverter Modbus TCP server.

Process Active

0943

Monitor::Communications::Base Modbus

Parameters::Base Comms::Modbus

FALSE

TRUE

NEVER

Modbus TCP parameter.

Indicates that a Modbus request addressed to this node has been received within the period set by the parameter Modbus Timeout,
or if no timeout is specified, this parameter will stay active after the first received Modbus request.

Fieldbuses

A-10

Parameter Name

No.

Path

Default

Range

Writable

Modbus Conn Timeout

1458

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

66 seconds

0 – 100,000 seconds

ALWAYS

Modbus TCP parameter.

Sets the Modbus connection timeout. If this parameter is set to zero then the connection will not timeout.

Modbus Mapping

1567

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

none

Last parameter number

ALWAYS

Modbus TCP parameter.

User-defined Modbus parameter mapping table. Each entry in the table represents the required parameter number.

Mapping Valid

1632

Monitor::Communications::Base Modbus

Parameters::Base Comms::Modbus

TRUE

FALSE

TRUE

NEVER

Modbus TCP parameter.

Status of the user defined mapping area. This will be set to TRUE if all entries in the mapping table are valid.

Modbus TCP Password

1659

Setup::Communications::Base Modbus

Parameters::Base Comms::Modbus

0000

FFFF

ALWAYS

Modbus TCP parameter.

Modbus password. When set to a value other than zero, write access to parameters via the fixed mapping registers will be
restricted. To unlock the password, write to the Modbus register 00518 the value set in this password. A subsequent write of value
0000 to Modbus register 00518 will lock the password.

A-11

Fieldbuses

EtherNet/IP Adapter

INTRODUCTION

The built-in EtherNet/IP adapter (slave/server) is implemented in the AC30P and AC30D inverters.

Features

The following EtherNet/IP features are implemented:

•

Class 1 and Class 3 connections

•

One input assembly instance of up to 500 bytes

•

One output assembly instance of up to 496 bytes

•

Input mapping of up to 32 inverter parameters

•

Output mapping of up to 32 inverter parameters

•

Unicast or multicast communications

•

Requested Packet Interval (RPI) down to 2ms

•

Explicit access of inverter parameters (read and write)

Identity

The EtherNet/IP adapter has the following identity:
Vendor ID

(Parker-Hannifin)

Product Code

306

(Parker AC30 Drive)

To make use of this feature, firmware version V3.x.x needs to be installed in the inverter. The firmware may be updated by downloading the
firmware file from the Parker website (see section

Firmware Update

in Chapter 4) or installed from the latest version of PDQ. With version

V3.x.x firmware installed, the

AC30EIPS

CoDeSys (PDQ/PDD) device is required.

Note: V3.x.x firmware has no AFE support and an application size of 128Kbytes (rather than 192Kbytes).

Fieldbuses

A-12

INVERTER CONFIGURATION

Enabling

To enable the EtherNet/IP adapter set the parameter

3128 EtherNet IP Enable

to TRUE.

The current state of the EtherNet/IP adapter is given by the parameter

3130 EtherNet IP State

Note the EtherNet/IP adapter is only active when the inverter is in the Operational state.

IP Settings

The IP settings are set up from the inverter using the Ethernet parameters described in Chapter 12. The IP settings of the inverter cannot be set
via the PLC.

The current IP settings are monitored using the parameters:

0926 IP Address
0927 Subnet Mask
0928 Gateway Address

If parameter

0929 DHCP

is set to TRUE, then the IP address will be set from the DHCP server on the network, if one is available.

If parameter

0930 Auto IP

is set to TRUE, then the IP address will be automatically be assigned a link-local address.

If both parameters

0929 DHCP

and

0930 Auto IP

are FALSE, then the IP address, subnet mask and gateway address will be set from the values

in the parameters:

0933 User IP Address
0934 User Subnet Mask
0935 User Gateway Address

A-13

Fieldbuses

Parameter Mapping

The input and output assembly mappings of the inverter parameters are set in the parameters

3000 Input Mapping

(PLC->inverter) and

3064

Output Mapping

(inverter->PLC). Parameters created in the application may be added into the mapping. The mapping of each table ends on

the first zero entry.

The total number of input and output bytes mapped depends on the type of parameters
added to the mapping tables. The number of bytes used by each data type is summarized
in the table.

For the

input mapping

each parameter must be read-writable. Parameter

arrays are permitted. Configuration type parameters, string parameters,
password parameters and reserved parameters are not permitted. The
default input mapping is given in the table.

For the

output mapping

each parameter may be read-only or read-

writable. Parameter arrays are permitted. String parameters and
password parameters are not permitted. The default input mapping is
given in the table.

If the input and output mappings have invalid entries then the parameter

3130 EtherNet IP State

will report

ERROR

and the inverter will not go

into the Operational state.

AC30 Data Type

Bytes

BOOL

SINT

INT

DINT

USINT (incl enumerated)

UINT

UDINT

REAL

TIME

DATE

TIME_OF_DAY

DATE_AND_TIME

BYTE

WORD

DWORD

Input Mapping Table

Data Type

Bytes

000

0627 Comms Control Word

WORD

001

0681 Comms Reference

REAL

002

0000

Output Mapping Table

Data Type

Bytes

000

0661 Status Word

WORD

001

0395 Actual Speed Percent

REAL

002

0000

Fieldbuses

A-14

Assembly Instances

The assembly instance numbers are:

Electronic Data Sheet (EDS) File

The latest EtherNet/IP EDS file for the inverter may be downloaded from

www.parker.com

The EDS file may also be downloaded directly from the drive via a web browser. To access this make sure the parameter

0944 Web Access

set to LIMITED or FULL. Type the following into the browser address bar (replacing

ip_address

with the inverter’s IP address):

ip_address/eds/eips.zip

Assembly Instance

Number

Input (T2O)

100

Output (O2T)

150

Input only

198

Listen Only

199

A-15

Fieldbuses

EXAMPLE PLC CONFIGURATIONS

Using RSLogix 5000

The example in this section uses the default parameter mapping of the inverter described under Parameter Mapping in the Inverter Configuration
section above:

A CompactLogic L32E controller is used.

1. Start a new project from within RSLogix 5000 and select the required controller.

Input Mapping Table

Data Type

Bytes

000

0627 Comms Control Word

WORD

001

0681 Comms Reference

REAL

002

0000

Output Mapping Table

Data Type

Bytes

000

0661 Status Word

WORD

001

0395 Actual Speed Percent

REAL

002

0000

Fieldbuses

A-16

Open the

Ethernet Port

properties and enter the IP address of the Controller.

3. Right-click on the

Ethernet Port

and select

New Module

. Under

Communications

select the

Generic Ethernet Module

A-17

Fieldbuses

4. Enter the Name and IP address of the inverter. Set the

Comm Format

Data – SINT

. The

Input Assembly Instance

100

and in this example the

data size is a total of 6 bytes. The

Output Assembly Instance

150

and in this example the data size is a total of 6 bytes. The mapping sizes on the

inverter MUST match that on the PLC. Set the Configuration Assembly Instance to 128 size 0.

5. Within the

Controller Tags

the communications data arrays are automatically created:

A-19

Fieldbuses

Using a CoDeSys Based PLC

The example in this section uses the default parameter mapping of the inverter described under Parameter Mapping in the Inverter Configuration
section above:

A CoDeSys (V3.5 SP10) soft PLC running on a PC is used.

1. Start a new project from CoDeSys using a

CODESYS Control Win V3

device.

2. From the CoDeSys menu select

Tools->Device Repository…

and install the AC30 EDS file. The device will appear under Fieldbuses as

shown.

Input Mapping Table

Data Type

Bytes

000

0627 Comms Control Word

WORD

001

0681 Comms Reference

REAL

002

0000

Output Mapping Table

Data Type

Bytes

000

0661 Status Word

WORD

001

0395 Actual Speed Percent

REAL

002

0000

Fieldbuses

A-20

3. Under Devices, select the

CODESYS Control Win 3

device, right click and select

Add Device…

, then add an

Ethernet Adapter

. Under the

Ethernet device add an

EtherNet/IP Scanner

. Under the EtherNet/IP Scanner add a

Parker AC30 Drive

4. Double-click on

CODESYS Control Win 3

and under

Communications Settings

tab select

Scan Network...

and select the required PC

(note the softPLC on the PC must be started).

Parker Variable Speed Drive AC30 series. User’s Manual (2017) - page 14