Modbus configuration instructions Easergy P3 Application Book

Easergy P3Modbus configuration instructions

Application BookP3APS18025EN04/2019

www.schneider-electric.com

Table of Contents1. About this document..................................................................... 41.1. Purpose............................................................................................................41.2. Abbreviations and terms.................................................................................. 4

2. Modbus overview.......................................................................... 5

3. Modbus configuration....................................................................83.1. Activating Modbus RTU................................................................................... 83.2. Configuring Modbus RTU.................................................................................83.3. Configuring and activating Modbus TCP ........................................................ 93.4. Clock synchronization.................................................................................... 103.5. Events............................................................................................................ 113.6. Scaling........................................................................................................... 12

4. Additional information about some Modbus registers................. 154.1. Protection settings......................................................................................... 15

4.1.1. Modbus registers for protection settings..............................................154.1.2. Reading and writing protection settings...............................................15

4.2. Disturbance recordings.................................................................................. 164.2.1. COMTRADE files.................................................................................164.2.2. Modbus registers for disturbance recordings.......................................164.2.3. Reading disturbance records as COMTRADE files ............................ 17

4.3. Modbus fault current registers....................................................................... 19

5. Testing Modbus with Simple Tester.............................................205.1. Simple Tester................................................................................................. 205.2. Connecting the device to the PC running Simple Tester................................205.3. Connecting the device to Simple Tester with Modbus RTU........................... 215.4. Connecting the device to Simple Tester with Modbus TCP........................... 225.5. Reading data..................................................................................................235.6. Writing data....................................................................................................255.7. Events and clock synchronization in Simple Tester....................................... 25

Table of Contents Modbus configuration instructions

P3APS18025EN 3

1. About this document

1.1. Purpose

The purpose of this document is to describe the configuration and use of theModbus RTU and Modbus TCP in Easergy P3 protection devices.

1.2. Abbreviations and terms

Table 1 - Abbreviations and terms

Term Description

COMTRADE Common format for transient data exchange. File format for storingoscillography and status data related to transient power systemdisturbances.

DHCP Dynamic host configuration protocol

EF Earth fault

HR Holding register

NTP Network time protocol

OC Overcurrent

RTC Real-time clock

RTU Remote terminal unit

SNTP Simple network time protocol

TCP Transmission control protocol

Modbus configuration instructions 1. About this document

4 P3APS18025EN

2. Modbus overviewThe Modbus protocol is a master-slave protocol typically implemented on anRS-232 or RS-485 physical interface. There are two versions of the serial Modbusprotocol: Modbus RTU and Modbus ASCII, of which Modbus RTU is available inEasergy P3 devices. There is also a TCP/IP implementation of the protocol,Modbus TCP.

Modbus TCP is simply the Modbus RTU protocol with a TCP interface that runson Ethernet. TCP/IP refers to the transmission control protocol and InternetProtocol which provide the transmission medium for Modbus TCP messaging. Inpractice, Modbus TCP embeds a standard Modbus data frame into a TCP frame.

Modbus RTU and Modbus TCP can be used to transfer the following types ofdata:

• events• status information• measurements• control commands• clock synchronization• protection settings• disturbance recordings

In the master-slave setup of Modbus, only the master can initiate transactions(queries). The slaves respond by supplying the requested data to the master orby taking the action requested in the query. The master can address individualslaves or initiate a broadcast message to all slaves. The address space for slavesin Modbus RTU ranges from 1-247 on one data link. Address 0 is reserved forbroadcast.

The Modbus protocol defines four different categories of data. The mapping ofdata to these categories is implementation dependent. In Easergy P3 devices, alldata is mapped to the holding registers.

Table 2 - Modbus data organisation

Primary table Object type Access Comments

Discrete input Single bit Read-only This type data can be provided by an I/Osystem.

Coils Single bit Read-write This type of data can be altered by anapplication program.

Input registers 16-bit word Read-only This type of data can be provided by an I/Osystem.

Holdingregisters

16-bit word Read-write This type of data can be altered by anapplication program.

The actual mapping of particular data items to holding registers in Easergy P3devices can be checked with the setting tool by selecting the items under theModbus main configuration setting view.

2. Modbus overview Modbus configuration instructions

P3APS18025EN 5

Figure 1 - Modbus main configuration setting view

NOTE:• The data mappings are visible only when the Modbus protocol is

activated. For instructions on how to activate the protocol, see Chapter 3.Modbus configuration.

• The values in the Address column (for example 40xxxx) consist of twoparts: “40” and “xxxx”, where the prefix “40” denotes a reference to Read/Write Output or Holding Registers and “xxxx” denotes the address of aparticular register.

• The holding register address sent via Modbus is one less than thatindicated by a device. For example, if the Alive Indicator, holding registeraddress 2001, is sent over a Modbus data link, the frame indicates thatthe address of the holding register is 2000.

The bit rate of Modbus RTU is typically 9600 bps and for the transmission offrames, a parity check mode must be selected (even, odd or none paritychecking).

Modbus configuration instructions 2. Modbus overview

6 P3APS18025EN

Figure 2 - Modbus data mappings

Related tasksActivating Modbus RTU on page 8Configuring and activating Modbus TCP on page 9

2. Modbus overview Modbus configuration instructions

P3APS18025EN 7

3. Modbus configuration

3.1. Activating Modbus RTU

1. In Easergy Pro, go to Communication > Protocol configuration.

2. Under Remote port, select “ModBusSlv” from the Remote port protocoldrop-down menu.

Figure 3 - Selecting the remote port protocol

• After changing the communication protocol, for the changes to take effect,reboot the device.

• The protocol can also be enabled via the local panel of the device. You mustenter the password for the configurator access level via the local panel beforethis is possible. See the manual for the device at hand for more instructions.

3.2. Configuring Modbus RTU

Before configuring Modbus, you must activate it.

Configure the Modbus protocol using Easergy Pro.

1. Go to Protocol configuration > Modbus main configuration.

2. Set the Modbus slave numer, bit rate and parity.

Modbus configuration instructions 3. Modbus configuration

8 P3APS18025EN

Figure 4 - Modbus main configuration setting view

NOTE: The parity and bit rate must be set to the same value on alldevices connected to the same data link.

Related tasksActivating Modbus RTU on page 8

3.3. Configuring and activating Modbus TCP

Configure the Ethernet port settings with Easergy Pro.

1. Go to Protocol configuration > Ethernet port.

2. Set the IP address, subnet mask (NetMask) and gateway.

Figure 5 - Ethernet port setting view

3. Modbus configuration Modbus configuration instructions

P3APS18025EN 9

NOTE: Easergy P3 devices support dynamic host configuration protocol(DHCP) but usually a static IP address is used. Consider this beforeconnecting a device to an existing network, so that no conflicts emerge.

3. Reboot the device for the changes to take effect.

4. To activate Modbus TPC, set Ethernet port protocol to “ModbusTCPs”(Modbus TCP, slave).

Figure 6 - Ethernet protocol setting view

NOTE:◦ There are two different Ethernet protocols, Ethernet protocol 1 and 2.

Modbus TCP can be selected to only one of them. The other protocolcan be for example IEC 61850.

◦ Two Modbus TCP masters can communicate with the devicesimultaneously.

◦ Serial Modbus RTU can be used at the same time with Modbus TCPmasters.

3.4. Clock synchronization

The device’s internal clock can be synchronised via the Modbus protocol.However, this is not a native feature of the Modbus protocol, but an Easergy-specific system. The accuracy of the clock synchronisation is in the scale of a fewhundred milliseconds.

The clock can be synchronized either completely (all fields: seconds, minutes,hours, days, month and year) or by synchronizing only the minutes, which in turnsets the seconds and milliseconds to zero.


10 P3APS18025EN

An example of how minute synchronisation can be done: when the referenceclock (the clock which is assumed to be correct) is exactly seven minutes past(any hour), a minute synchronisation is performed. The result is that the internalclock of the device is set to HH:07:00.000(“Hours:Minutes:Seconds.Milliseconds”) “HH” is not changed.

These two ways of synchronizing the clock are denoted “Set RTC”, where “RTC”stands for real-time clock and “Synchronise Minutes” in the data map. The holdingregister address of the minute synchronisation is 2502.

Table 3 - Description of holding registers allocated to “Set RTC”synchronization

Holding register Content

2504 Lower byte: seconds. Milliseconds are zero.

2505 Upper byte: minutes.

Lower byte: hours.

2506 Upper byte: day.

Lower byte: month.

2507 Year

Time synchronization is recommended to be performed hourly.

For Modbus TCP, clock synchronisation can also be done by using simplenetwork time protocol (SNTP). This requires a NTP server, the address of whichis set in the Protocol configuration > Ethernet port setting view in Easergy Pro.

3.5. Events

The device’s event buffer can be read via the Modbus RTU protocol by readingone event at a time, from holding registers 2101…2105. The event registerscontain the latest event, and are cleared when they are read. The registers arethen updated to contain the following event from the event buffer.

Table 4 - Description of Events in holding registers


2101 Event code

2102 Event timestamp

Bits 15-6 = milliseconds

Bits 5-0 = seconds


Upper byte = minute

Lower byte = hour


P3APS18025EN 11



Upper byte = day

Lower byte = month

2105 Event timestamp, year

If an error occurs when reading an event from registers 2101…2105, thepreviously read event is available in registers 2490…2494 for re-reading.

NOTE: Events can also be read from holding registers 1996…2000.

Events are coded with a numbering starting from 0. To obtain the meaning ofthese event codes, run the GETSET-command “get eventcodes” in the terminalsoftware (for example PuTTY).

3.6. Scaling

Holding registers are 16 bits in size, so they can directly represent 216 = 65535different values, which might not be enough to describe the values of somephysical quantity such as voltage or power. Thus, values transmitted over aModbus data link must be scaled to account for this.

Figure 7 - Line defined by two points in a two-dimensional space

The scaling is determined by the equation of the line connecting two points in atwo-dimensional space, (x1, y1) and (x2, y2). That is, the trajectory of the line andthe offset from origin. Note that there is no offset in the example if the point (x1,y1) is assumed to lie at the origin.

It is common to use scaling factors with base ten (10, 100, 1000…) since, in suchcases, the original measurements only lose decimals and such values are easy toread and re-scale to actual values on the client side after transmission. Note thatthe scaled measurements get rounded.

Different settings for scaling can be used for the power, power factor, tan phi,voltage and frequency scaling. These can be set in the Communication >Modbus & Profibus scalings setting view item in Easergy Pro.

A short example: The frequency is internally (in the device) stored as a integervalue which also holds three decimal places, that is, 50.000 Hz is represented as


12 P3APS18025EN

50000. This is a value too large to be represented with 16 bits (signed integer),however, frequency is by default scaled with the points: (x1, y1) = (0, 0) and (x2,y2) = (10, 1), enabling it to be sent over Modbus.

The slope is 0.1 and there is no offset.

𝑘𝑦 2 1

2 1

− 𝑦𝑥 −𝑥

==1 − 0

10 − 0= 0.1

Thus, the value on the receiving side (the Modbus value) is:

𝑣 𝑎 𝑙 𝑢 𝑒 = 𝑘 𝑣 𝑎 𝑙 𝑢 𝑒 = 0.1 ** 50000 = 5000 modbus internal

Figure 8 - Default frequency scaling

To make sure that a scaling has been set as intended, you can check it inEasergy Pro by viewing the Scaling column for each holding register in theModbus data mapping lists, for example in Communication > Modbus slave401491.

For an example of scaling change, see Figure 9 - Voltage scaling changed fromdefault (x2 changed to 10 from 1) on page 14, Figure 10 - Result of the changein voltage scaling on page 14 and Figure 11 - Default scaling for some holdingregisters on page 14.


P3APS18025EN 13

Figure 9 - Voltage scaling changed from default (x2 changed to 10 from 1)

Figure 10 - Result of the change in voltage scaling

Compare the scalings in Figure 10 - Result of the change in voltage scaling onpage 14 and Figure 11 - Default scaling for some holding registers on page 14.

Figure 11 - Default scaling for some holding registers

NOTE: To avoid overflow, scale values so that they are kept in the interval 0–32768 .


14 P3APS18025EN

4. Additional information about some Modbusregisters

4.1. Protection settings

4.1.1. Modbus registers for protection settings

The most important protection settings can be read and written using Modbusregisters starting from address 5001.

Figure 12 - Modbus register 5001

4.1.2. Reading and writing protection settings

Modbus holding registers are 16 bits wide. However, some of the parameterswhich have been mapped to these registers in the device have 32-bit values.These parameters are mapped to two consecutive 16-bit holding registers, so thatthe register with the smaller address represents the LSB 16-bit word for theparameter and the second register represents the MSB 16-bit word for theparameter.

In the current firmware version, all parameters (and only the parameters) whichoccupy two consecutive holding registers have 32-bit values.

When the value of such parameter is updated through Modbus, the client mustperform two write operations: one for the LSB word and another for the MSBword. Each write operation updates the value of the parameter, so that only theword being written to is modified. The intermediate state for the parameter—where only one word has been updated—may represent an invalid value for theparameter. For example, the value may be out of allowed range. In such case thefirst write operation gives an error message, indicating that the value of theparameter was not updated. The client can nevertheless continue with the secondwrite operation. This second write operation modifies the incomplete intermediatestate of the parameter. If the intermediate state then reaches a valid 32-bit valuefor the parameter, the second write operation should indicate a success.

4. Additional information about some Modbus registers Modbus configuration instructions

P3APS18025EN 15

The client can, for example, first write the LSB 16-bit word for the parameter andthen write the MSB 16-bit word for the parameter, and the parameter should havethe new 32-bit value after the second write operation. The two 16-bit words canbe written in any order. These two write operations should occur within twoseconds of each other.

4.2. Disturbance recordings

4.2.1. COMTRADE files

COMTRADE is a standard file format for exchanging disturbance recordings.These are (oscillographic) measurements of power system variables, such as(instantaneous) currents and voltages, over an event like a transient fault.

One recording consists of two files: a CFG file describes what was recorded in therecording, and a DAT file contains the recorded values.

4.2.2. Modbus registers for disturbance recordings

In P3 devices, one register is used to issue commands to the COMTRADEreading mechanism.

Table 5 - Modbus registers for disturbance recordings

Register Content

5400

(Commandregister)

• MSB byte: Number of the recording to be downloaded, so thatvalue zero means the oldest record, value one means the secondoldest record, and so on.

• LSB byte: A set of flags◦ b5: Trigger to remove oldest record.◦ b4: Trigger to request the next chunk.◦ b3: Flag for auto-increment the chunk.◦ b2: Flag for load DAT file.◦ b1: Flag for load CFG file.

• (LSB) b0: Trigger start of download when value 1 is written to thisbit.

5401

(Status register1)

• MSB byte: Number of recordings available.• LSB byte: A set of flags.

◦ b5: Flag for error in download.◦ b4: Flag for last chunk of data for this file.◦ b3: Flag for chunk auto-increment in use.◦ b2: Flag for DAT file now being loaded.◦ b1: Flag for CFG file now being loaded.

• (LSB) b0: Flag for valid data in data registers. Implies that adownload is in progress.

Modbus configuration instructions 4. Additional information about some Modbus registers

16 P3APS18025EN

Register Content

5402

(Status register2)

• MSB byte: Number of bytes of data available in data registers.• LSB byte: Approximate progress downloading current file in

percentage.

5403 to 5498

(96 Dataregisters)

Content (fragment) for the file being downloaded.

NOTE: The maximum length of a Modbus message is 253 bytes. It is thuspossible to read the two status registers and all of the data registers in asingle command.

4.2.3. Reading disturbance records as COMTRADE files

Disturbance recordings (COMTRADE files) can be read via registers starting from5400.

1. Open Modbus connection to the device.

2. Read status register 1 (5401), and check that there is at least one recordingavailable.

3. Construct a value for the command which starts the download process.

For example, value 271 (0x0x10F) starts download of the second oldestrecord.

MSB byte: 0x01

Number of the recording to be downloaded

LSB byte: 0x0F

◦ b5: (0) Trigger to remove the oldest record.◦ b4: (0) Trigger to request the next chunk.◦ b3: (1) Flag to auto-increment the chunk.◦ b2: (1) Flag to load the DAT file.◦ b1: (1) Flag to load the CFG file.◦ (LSB) b0: (1) Trigger start of download when value 1 is written to this bit.

Write this value to the command register (5400). This command indicateswhich recording you want to read and whether you want to download bothCFG file and DAT file, or only either one at a time. This enables “chunk auto-incrementing”, which means that whenever we read the value of statusregister 1, the contents of the data registers are updated to contain the nextfragments of data for the file which is currently downloading.

4. Make a read request that starts from status register 1 (5401) and continuesuntil the end of the data registers (registers 5403...5498).This is a total of 96 + 2 = 98 registers.

5. Inspect the value of status register 1.


P3APS18025EN 17

Table 6 - Register 5401 (status register 1)

Byte / bit Meaning Explanation

MSB byte Number of recordingsavailable

If this value changes in themiddle of a download, anew recording has beenmade. It is recommendedthat in this case thedownload is aborted andrestarted, by returning tostep 3 (or to step 1).

LSB byte Set of flags

b5 Flag for error in download. If this flag is set, there wasan internal error in thedevice, and the downloadis automatically aborted bythe device. Contents of allother registers are invalid.

b4 Flag for last chunk of datafor this file

If this flag is set, the dataregisters contain the lastpieces of data for the filewhich we are currentlydownloading. When nextchunk is triggered, we getthe first pieces of data foranother file. (With auto-increment, this triggeringhappens when the statusregister 1 is read.)

b3 Flag for chunk auto-increment in use

Indicates whether auto-increment is in use for thisdownload. If this is notused, a separate write isneeded to the commandregister, with correct flags,to get the next pieces ofdata in the data registers.

b2 Flag for DAT file now beingloaded

If set, indicates that we arenow downloading the DATfile.

b1 Flag for CFG file nowbeing loaded

If set, indicates that we arenow downloading the CFGfile.

(LSB) b0 Flag for valid data in dataregisters

If this flag is set, the dataregisters DO contain validdata for the files beingdownloaded. Absence ofthis flag indicates either anerror or that the downloadis complete.

Modbus configuration instructions 4. Additional information about some Modbus registers

18 P3APS18025EN

6. Assuming that you now have valid data for the download, inspect the value ofstatus register 2 (4602).

MSB byte Number of bytes of data available in data registers

LSB byte Approximate progress downloading current file in percentage

NOTE: The data registers hold 16-bit values (two bytes), while the amountof data is reported in bytes. The data registers should be filled with data(giving value 192 here), unless the last pieces of content for the file arenow in the data registers.

You can always read all data registers, and then ignore those which do notcontain valid data, or first read the two status registers, and then, with aseparate read command, read only those data registers which actually containdata. Also, you may choose to read only at most M registers at a time, so thatM is smaller than the total number of data registers (96). These options maybe useful if the used communication link is slow or expensive.

If the link is prone to transfer errors, you can choose to read a given dataregister several times, and use the value which occurs most commonly. In thisuse case, it is recommended not to use the auto-increment feature.

7. Copy data from the data registers to the file which is currently beingdownloaded.Note the actual amount of (valid) data in the registers that was discovered instep 5. If this is the last chunk of data for this file, then after the data has beenwritten to the file, close the file. When the next pieces of data are received,you can open a new file. Flags on status register 1 indicate which file is thenbeing downloaded.

8. Start to read the next chunk by returning to step 4.

4.3. Modbus fault current registers

Here you can find explanations for some additional Modbus registers.

Table 7 - Modbus fault current registers

Register Explanation

2110 Last fault current from any dir/undir OC stage (can be cleared)

2111 Fault current from I> stage

2112 Fault current from I>> stage

2113 Fault current from I>>> stage

2130 Last fault Io current from any undirectional EF stage

2131 Fault current from Io> stage

2132 Fault current from Io>> stage

2133 Fault current from Io>>> stage

2134 Fault current from Io>>>> stage


P3APS18025EN 19

5. Testing Modbus with Simple Tester

5.1. Simple Tester

Simple Tester is a basic protocol testing tool (for PC) that supports severaldifferent protocols, including Modbus RTU and TCP. Simple Tester can be used totest reading data from holding registers, writing to holding registers, viewingevents and performing clock synchronization from the PC.

Figure 13 - Simple Tester user interface with Modbus selected as protocol

A

B

C

D

E

F

G

A. Communication parameters: protocol selection and device connectionconfiguration

B. Modbus Slave ID selectorC. Selections for data readingD. Selections for data writingE. Time controlsF. Event view windowG. Connection status

5.2. Connecting the device to the PC running Simple Tester

Before starting testing, connect the P3 device to the PC running Simple Tester.

You can create the connection either via RS-232 or Ethernet.• To connect the device to the PC via RS-232 interface:

a. Connect an RS-232 cable to the device.

b. Connect an USB-to-RS-232 cable to the PC’s USB port.

Modbus configuration instructions 5. Testing Modbus with Simple Tester

20 P3APS18025EN

c. Connect a cable adapter between the two cables.

d. The cable adapter connects the pins 2,3, and 7 of the device’s RS-232cable’s D-connector to pins 2,3, and 5 of the D-connector of the PC’scable.

• To connect the device to the PC via Ethernet interface:

– Connect an Ethernet cable or Ethernet switch between the PC and thedevice.

5.3. Connecting the device to Simple Tester with Modbus RTU

Before connecting a device with Modbus RTU:• Configure the device.• Connect the device to the PC running Simple Tester.

1. Open Simple Tester.

2. Under Communication parameters, select ModBus from the Protocol drop-down menu.

3. Under Communication parameters and Modbus, select the settings asfollows:

Parameter Value

Protocol Modbus

Connection type Serial line

Serial port The serial port of the PC

Modbus slave ID The slave ID configured on the device

4. Click the Go button.

5. Testing Modbus with Simple Tester Modbus configuration instructions

P3APS18025EN 21

Figure 14 - Simple Tester when connected with Modbus RTU

A successful connection is indicated by an “OK” in the rightmost connectionstatus indicator furthest down in the Simple Tester window.

Related tasksConfiguring Modbus RTU on page 8Connecting the device to the PC running Simple Tester on page 20

5.4. Connecting the device to Simple Tester with Modbus TCP

Before connecting a device with Modbus TCP:• Configure the device Ethernet port and TCP port instances.• Establish a physical Ethernet connection from the PC running Simple Tester

to the device.


2. Under Communication parameters, select Modbus from the Protocol drop-down menu.

3. Under Communication parameters and Modbus, select the settings asfollows:

Parameter Value

Protocol Modbus

Connection type TCP connection

Host The IP address configured on the device

Port 502

Modbus slave ID The slave ID configured on the device


22 P3APS18025EN

4. Click the Go button.

Figure 15 - Simple Tester when connected with Modbus TCP

A successful connection is indicated by an “OK” in the right-most connectionstatus indicator furthest down in the Simple Tester window.

Related tasksConfiguring and activating Modbus TCP on page 9Connecting the device to the PC running Simple Tester on page 20

5.5. Reading data

Before reading data, connect the device to the PC running Simple Tester.


2. Under Communication parameters, select ModBus from the Protocol drop-down menu.


P3APS18025EN 23

Figure 16 - Performing a cyclic read on the Alive Counter with Simple Tester

3. Set the right values for Type, Index and Count.

Parameter Description

Type Type of data: select HR (holding register).

Index Select which data item to read from the device. See the data mappingprovided by Easergy Pro.

Count Indicates how many consecutive indices are to be read. For example,setting Index to 2001 and Count to 2 displays the values of Index 2001and Index 2002 in the Values box.

4. Click the Read button to manually initiate a read.Reads can also be done cyclically, by selecting the Cyclic read checkbox.The length of one cycle can be changed by setting a value (seconds) in theCycles field.

Related tasksConnecting the device to the PC running Simple Tester on page 20


24 P3APS18025EN

5.6. Writing data

Figure 17 - Simple Tester after write to Virtual Input 1

1. Set the right values for Type, Index and Value.

2. Click the Write button.

If the operation is successful, the Status field indicates OK.

NOTE: The event view of Simple Tester now contains an event,corresponding to “Virtual Input 1 ON”.

5.7. Events and clock synchronization in Simple Tester

If there are events in the event buffer when connecting to Simple Tester, they arelisted in the event view. New events triggered by writes done with Simple Testeralso show up there.

Clock synchronisation can also be performed with Simple Tester by setting thedesired behavior in the time controls settings. The two leftmost fields are used forsetting the time manually, but the time can also be taken from the PC, byselecting the PC Time checkbox.

Clock synchronisation can also be set to be cyclic by selecting the Cyclictimesync checkbox. The length of a cycle (minutes) is set in the rightmost field.

Related conceptsSimple Tester on page 20


P3APS18025EN 25

Schneider Electric35 rue Joseph Monier92500 Rueil Malmaison - FrancePhone: +33 (0) 1 41 29 70 00www.schneider-electric.com

As standards, specifications, and designs change from time to time,please ask for confirmation of the information given in this publication.

© 2019 Schneider Electric All Rights Reserved.

P3APS18025EN — 04/2019

Modbus configuration instructions Easergy P3 Application Book

Documents

Transcript of Modbus configuration instructions Easergy P3 Application Book