Manual Modbus Info
Manual Modbus Info
4.1 Description
0RGEXV0DVWHU
1RWH8VHWZLVWHGSDLUZLULQJLIVKLHOGHGFRQQHFWRQO\DWRQHHQG
A
1RWH7KHJURXQGLVORFDWHGRQ3LQRIHDFKGULYH
B A B A B A
0D[FRQQHFWLRQV
1;*&RQWUROV0RGEXVVODYHV
= 7HUPLQDWLRQ 1RWH$%GHILQLWLRQVDUHQRWVWDQGDUG,IWKHXQLWGRHVQRWZRUN
\RXPD\QHHGWRVZDS$DQG%
Description
The Siemens Modbus™ module supports Modbus™ communication. The module plugs into
the Anybus 1 (ABUS1) connector or the Anybus 2 (ABUS2) connector on the fiber optic board,
as shown in Figure NXGpro Control in the Introduction Chapter.
The following figure shows the connector and status indicators on the Siemens Modbus™
module.
NXGpro Communication
32 Function Manual, AD, A5E33486415A
Modbus Communication
4.1 Description
Connector
The module has fixed pin assignments for Data A and Data B. The following figure shows the
output pin configuration for RS485.
1 Pin 2: Data A
2 Pin 3: Data B
3 Pin 5: Ground
Figure 4-3 RS485 Pin Assignments
NXGpro Communication
Function Manual, AD, A5E33486415A 33
Modbus Communication
4.2 Software Programming
Status Indicators
The following table explains the status indicators as shown in Figure Siemens Modbus Module.
Note
The green LED does not indicate that network traffic is present for this specific device; it only
means that network traffic is present.
Termination Resistor
The module incorporates a jumper (JP5), which can be used to terminate the network line as
listed in the following table.
Jumper Setting
JP5 = 1-2 Termination resistor disabled
JP5 = 2-3 Termination resistor enabled
NXGpro Communication
34 Function Manual, AD, A5E33486415A
Modbus Communication
4.2 Software Programming
The following table shows how the fixed register bits correspond with programmable bits
available for use in the SOP (drctry.pro bits).
Pick list variable in 'Data to Drive Reg nn' menus Corresponding Drctry.pro bits Modbus Address
Fixed Reg Bits (network 1) Network1FixedRegBit0_I ~ Network1FixedReg‐ 40065
Bit15_I
Fixed Reg Bits (network 2) Network2FixedRegBit0_I ~ Network2FixedReg‐ 40065
Bit15_I
Description
There are 64 input bits available for user programming through the SOP file. These bits can be
programmed to set or reset any other bits used within the SOP.
Programming Procedure
1. Locate the first data to drive register that is programmable using Table Correspondence
between Drive Parameter ID and Communication Protocol Address in Section Parameter
Assignment/Addressing.
You will see that the first programmable data to drive register for network 1 is register 'Data
to Drive 03', which corresponds to parameter ID (9603).
2. Enter parameter ID (9603).
3. The pick list of data to drive variables will appear. Refer to Table Data to Drive Pick List
Variables and Scaling in Section Parameter Assignment/Addressing for a list of data to drive
pick list variables.
4. Scroll through the pick list until you come to 'Net Input Flag 1' and press [ENTER]. This
setting uses the first 16 bits of the possible 64 bits.
Now the corresponding bits from the drctry.pro file can be used in the SOP, as shown below:
;Network1Flag0_I Use bit 0 for Stop bit
;Network1Flag1_I Use bit 1 for Run Forward bit
RunRequest_O = /Network1Flag0_I * Network1Flag1_I;Run drive using
bit 1,stop using bit 0
5. Select 'Net Input Flag 2' to use the second set of 16 bits, and so on.
Note
By choosing 'Data to Drive 03' as the write register, the PLC must now send 0x02 in register
'Data to Drive 03' to run the drive.
To stop the drive, the PLC must send 0x01 in register 'Data to Drive 03'.
NXGpro Communication
Function Manual, AD, A5E33486415A 35
Modbus Communication
4.2 Software Programming
The pick list variables and the corresponding programmable input bits are found in the following
tables for network 1 and 2, respectively.
Pick list variable in 'Data to Drive Reg nn' menus Related Drctry.pro bits
Net Input Flag 1 Network1Flag0_I ~ Network1Flag15_I
Net Input Flag 2 Network1Flag16_I ~ Network1Flag31_I
Net Input Flag 3 Network1Flag32_I ~ Network1Flag47_I
Net Input Flag 4 Network1Flag48_I ~ Network1Flag63_I
Pick list variable in 'Data to Drive Reg nn' menus Related Drctry.pro bits
Net Input Flag 1 Network2Flag0_I ~ Network2Flag15_I
Net Input Flag 2 Network2Flag16_I ~ Network2Flag31_I
Net Input Flag 3 Network2Flag32_I ~ Network2Flag47_I
Net Input Flag 4 Network2Flag48_I ~ Network2Flag63_I
Example
The following example shows how the network can be programmed to trip the input medium
voltage:
● The PLC writes to register 'Data to Drive 03' which is programmed to 'Net Input Flag 1' using
the procedure above.
● The SOP sets a flag bit that uses a digital output to trip input medium voltage, using the
following SOP source code:
● The PLC writes the contents of 'Net Input Flag 1', bit 9 (Network1Flag9_I) to create an input
medium voltage trip.
Description
There are 64 output bits available for user programming through the SOP file. These bits can
be programmed to set or reset any other bits used within the SOP.
NXGpro Communication
36 Function Manual, AD, A5E33486415A
Modbus Communication
4.2 Software Programming
Programming Procedure
1. Locate the first data from drive register that is programmable using Table Correspondence
between Drive Parameter ID and Communication Protocol Address in Section Parameter
Assignment/Addressing.
You will see that the first programmable data from drive register for network 1 is register
'Data from Drive 03', which corresponds to parameter ID (9403).
2. Enter parameter ID (9403).
3. The pick list of data from drive variables will appear. Refer to Table Data from Drive Pick List
Variables in Section Parameter Assignment/Addressing for a list of data from drive pick list
variables.
4. Scroll through the pick list until you come to 'Net1 Out Reg 1' and press [ENTER]. This
setting uses the first 16 bits of the possible 64 bits.
5. Select 'Net1 Out Reg 2' to use the second set of 16 bits, and so on.
The pick list variables and the corresponding programmable output bits are found in the
following tables for network 1 and 2, respectively.
Pick list variable in 'Data from Drive Reg nn' menus Related Drctry.pro bits
Net1 Out Reg 1 Network1Flag0_O ~ Network1Flag15_O
Net1 Out Reg 2 Network1Flag16_O ~ Network1Flag31_O
Net1 Out Reg 3 Network1Flag32_O ~ Network1Flag47_O
Net1 Out Reg 4 Network1Flag48_O ~ Network1Flag63_O
Pick list variable in 'Data from Drive Reg nn' menus Related Drctry.pro bits
Net2 Out Reg 1 Network2Flag0_O ~ Network2Flag15_O
Net2 Out Reg 2 Network2Flag16_O ~ Network2Flag31_O
Net2 Out Reg 3 Network2Flag32_O ~ Network2Flag47_O
Net2 Out Reg 4 Network2Flag48_O ~ Network2Flag63_O
Example
The following example shows how the network can be programmed to detect a trip on the input
medium voltage:
● The PLC reads register 'Data from Drive 03', which is programmed to 'Net1 Out Reg 1' using
the procedure above.
● The SOP sets a flag bit that corresponds to a medium voltage low fault, using the following
SOP source code:
NXGpro Communication
Function Manual, AD, A5E33486415A 37
Modbus Communication
4.3 Parameter Assignment/Addressing
● This example uses bit 9 of 'Net1 Out Reg 1', which is Network1Flag9_O, to set the network
flag true if the medium voltage low fault is active.
● The PLC reads the contents of 'Net1 Out Reg 1', bit 9 (Network1Flag9_O) to determine if a
medium voltage fault occured.
NXGpro Communication
38 Function Manual, AD, A5E33486415A
Modbus Communication
4.3 Parameter Assignment/Addressing
Network Parameters
NXGpro Communication
Function Manual, AD, A5E33486415A 39
Modbus Communication
4.3 Parameter Assignment/Addressing
Network 1 Parameters
NXGpro Communication
40 Function Manual, AD, A5E33486415A
Modbus Communication
4.3 Parameter Assignment/Addressing
Network 2 Parameters
NXGpro Communication
Function Manual, AD, A5E33486415A 41
Modbus Communication
4.3 Parameter Assignment/Addressing
NXGpro Communication
42 Function Manual, AD, A5E33486415A
Modbus Communication
4.3 Parameter Assignment/Addressing
NXGpro Communication
Function Manual, AD, A5E33486415A 43
Modbus Communication
4.3 Parameter Assignment/Addressing
NXGpro Communication
44 Function Manual, AD, A5E33486415A
Modbus Communication
4.3 Parameter Assignment/Addressing
NXGpro Communication
Function Manual, AD, A5E33486415A 45
Modbus Communication
4.3 Parameter Assignment/Addressing
Wago Inputs 17-32 2651 None None Bit Field ExternalDigitalInput03a_I - ExternalDigita‐
lInput03h_I
ExternalDigitalInput04a_I - ExternalDigita‐
lInput04h_I
Wago Inputs 33-48 2652 None None Bit Field ExternalDigitalInput05a_I - ExternalDigita‐
lInput05h_I
ExternalDigitalInput06a_I - ExternalDigita‐
lInput06h_I
Wago Inputs 49-64 2653 None None Bit Field ExternalDigitalInput07a_I - ExternalDigita‐
lInput07h_I
ExternalDigitalInput08a_I - ExternalDigita‐
lInput08h_I
Wago Inputs 65-80 2654 None None Bit Field ExternalDigitalInput09a_I - ExternalDigita‐
lInput09h_I
ExternalDigitalInput10a_I - ExternalDigita‐
lInput10h_I
Wago Inputs 81-96 2655 None None Bit Field ExternalDigitalInput11a_I - ExternalDigita‐
lInput11h_I
ExternalDigitalInput12a_I - ExternalDigita‐
lInput12h_I
Wago Outputs 1-16 2656 None None Bit Field ExternalDigitalOutput01a_O - ExternalDigi‐
talOutput01h_O
ExternalDigitalOutput02a_O - ExternalDigi‐
talOutput02h_O
Wago Outputs 17-32 2657 None None Bit Field ExternalDigitalOutput03a_O - ExternalDigi‐
talOutput03h_O
ExternalDigitalOutput04a_O - ExternalDigi‐
talOutput04h_O
Wago Outputs 33-48 2658 None None Bit Field ExternalDigitalOutput05a_O - ExternalDigi‐
talOutput05h_O
ExternalDigitalOutput06a_O - ExternalDigi‐
talOutput06h_O
Wago Outputs 49-64 2659 None None Bit Field ExternalDigitalOutput07a_O - ExternalDigi‐
talOutput07h_O
ExternalDigitalOutput08a_O - ExternalDigi‐
talOutput08h_O
PFD1 None None None None Refer to Appendix Parameter Read/Write
PFD2
PFD3
PFD4
Drive Losses 2161 % /100 Unsigned
Excessive Reactive 2162 % /100 Unsigned
Current
Speed Droop Percent 2163 % /100 Unsigned
Sync Motor Field Ref 2164 % /100 Unsigned
Avail Reactive Current 3653 % /100 Unsigned
NXGpro Communication
46 Function Manual, AD, A5E33486415A
Modbus Communication
4.3 Parameter Assignment/Addressing
NXGpro Communication
Function Manual, AD, A5E33486415A 47
Modbus Communication
4.3 Parameter Assignment/Addressing
Net Input Flag 4 None None Bit Field Network 1 SOP flags:
Network1Flag48_I ~ Network1Flag63_I
Network 2 SOP flags:
Network2Flag48_I ~ Network2Flag63_I
Ratio % % / 100 Signed
Forward Max Lim % / 10000 or Unsigned
% / 100
Reverse Max Lim % / 10000 or Unsigned
% / 100
Forward Acc Time Seconds / 10 Unsigned
Forward Dec Time Seconds / 10 Unsigned
Reverse Acc Time Seconds / 10 Unsigned
Reverse Dec Time Seconds / 10 Unsigned
Net Input Pulse None None Unsigned
Forward Min Lim % / 10000 or Unsigned
% / 100
Reverse Min Lim % / 10000 or Unsigned
% / 100
Torque Limit % / 10000 or Unsigned
% / 100
MUX1 Id None None None Refer to Appendix Multiplexer (MUX) Data Reg‐
MUX2 Id isters
MUX3 Id
MUX4 Id
MUX5 Id
MUX6 Id
MUX7 Id
MUX8 Id
PTD1 None None None Refer to Appendix Parameter Read/Write
PTD2
PTD3
PTD4
Parallel Cmd 1 None None Unsigned
Torque Demand % / 1000 Unsigned
PVCL Demand % / 100 Unsigned
Flux Demand % / 100 Unsigned
Node Count None None Unsigned
Node Index None None Unsigned
Torque Acc Time Seconds / 100 Unsigned
Torque Dec Time Seconds / 100 Unsigned
Torque Offset None / 1000 Unsigned
Torque Scalar None / 1000 Unsigned
Vars Command % / 1000 Unsigned
NXGpro Communication
48 Function Manual, AD, A5E33486415A
Modbus Communication
4.4 Planning/Configuring
4.4 Planning/Configuring
This section describes the setup methods available for communication. The following topics
are explained:
● Fast setup procedures
● Network setup procedure
● Network status detection
● An example to illustrate the setup procedure.
Note
Fast setup procedures allow setup of a Network 1 interface with a minimum of detail.
4.4.1 Fast Setup: Control the drive using the default configuration
To control the drive using the default configuration, you must send commands to the drive's
'fixed reg bits' location. This location is register 'Data to Drive 01' as provided in
Table Correspondence between Drive Parameter ID and Communication Protocol Address in
Section Parameter Assignment/Addressing.
To control the drive from a PLC using the default configuration, complete the following steps.
1. Set parameter 'Network 1 Type' (9901) to "Modbus".
2. Set parameter 'Modbus Baud Rate' (9060); this must match the baud rate of the PLC
controller.
3. Set parameter 'Modbus Address' (9070) to the desired network address for the drive.
4. Set parameter 'Net Control Type' (9944) to "Fixed". This sets the bits at register 'Data to
Drive 01' where the fixed register bits are located. The fixed register bits are interpreted as
shown in the following table.
5. Add the following line to the SOP:
Network1RunEnable_O = TRUE;
NXGpro Communication
Function Manual, AD, A5E33486415A 49
Modbus Communication
4.4 Planning/Configuring
Note
To run the drive, the PLC must send 0x21 to register 'Data to Drive 01'. This hexadecimal value
sets bit 0 (run) and bit 5 (start/stop control from network).
To stop the drive, the PLC must send 0x08 or 0x00 to register 'Data to Drive 01'.
NXGpro Communication
50 Function Manual, AD, A5E33486415A
Modbus Communication
4.4 Planning/Configuring
The general drive status bits found in register 'Data from Drive 01' are defined in the following
table.
Note
You cannot reprogram the drive's default interpretation of output bits.
Refer to Network Setup Procedure for details on how to read other drive data.
See also
Network Setup Procedure (Page 53)
NXGpro Communication
Function Manual, AD, A5E33486415A 51
Modbus Communication
4.4 Planning/Configuring
4.4.4 Fast Setup: Control the drive using user-defined bits controlled by the SOP
To control the drive using non-default configuration, you must redefine the fixed register bits at
register 'Data to Drive 01'.
Note
The 'fixed reg bits' location is fixed at register 'Data to Drive 01', whether the default
configuration is used or not.
You cannot reprogram the 'fixed reg bits' location.
You can reprogram the definition of the bits at this address.
See also
Software Programming (Page 34)
NXGpro Communication
52 Function Manual, AD, A5E33486415A
Modbus Communication
4.4 Planning/Configuring
Note
Setup functions are contained in the Configure Parameters Menu (9902), which is a submenu
of the Communications Menu (9).
Access is security-controlled at level 7; you must enter the security code to access these
parameters.
Refer to the NXGpro Control Operating Manual for further information on security access levels
and codes.
Use the following procedure to complete network setup. Refer to Table Configure Parameters
Menu (9902) in Section Parameter Assignment/Addressing for the menus needed to complete
setup.
Procedure
1. Select a protocol using parameter 'Network 1 Type' (9901). Scroll to "Modbus" and press
[ENTER]. The Modbus™ configuration parameters are viewable.
2. Set parameter 'Modbus Baud Rate' (9060); this must match the baud rate of the PLC
controller.
3. Set parameter 'Modbus Parity' (9047) to match the parity of the PLC controller.
4. Set parameter 'Modbus Address' (9070) to the desired network address for the drive.
5. Set parameter 'Velocity Units' (9080) to the desired motor speed units for motor
commanded speed and motor feedback speed scaling.
6. Where necessary, set parameter 'Demand Scalar' (9912) to:
n x commanded speed where –125 % to 125 %
7. Set parameter 'Aux Demand Scalar' (9913) if used.
8. Use Table Correspondence between Drive Parameter ID and Communication Protocol
Address in Section Parameter Assignment/Addressing to program the drive to send data to
and receive commands from the network. The table provides all available addresses with
corresponding parameter ID as well as pre-programmed addresses, which provide basic
drive send and receive functionality and are not changeable.
9. Define the bits in the available addresses using one of the following methods:
NXGpro Communication
Function Manual, AD, A5E33486415A 53
Modbus Communication
4.4 Planning/Configuring
● Enter from a choice of variables in the pick lists. The pick lists in the menus contain the most
commonly used data variables. Refer to Section Parameter Assignment/Addressing for the
pick lists.
Note
A pick list item can only be used once for each 'Data to Drive' register.
● For 'Data from Drive' registers, choose pick list option "Man Id" (manual ID) to manually
enter a variable that is not included in the pick lists, using the output data ID number. Use
the list of data IDs available in Appendix Output Data IDs to locate the variable and use the
corresponding ID number to enter the variable into the 'Data from Drive' register.
Note
The output data ID number is not the same as a parameter ID number.
● Custom program using the drive's SOP. Refer to Section Software Programming for details.
Note
The PLC can receive data from the drive without any changes to the SOP.
Only if you need to control the drive through the network will you need to set any flags in the
SOP.
See also
Software Programming (Page 34)
Correspondence between Drive Parameter ID and Communication Protocol Address (Page 38)
Parameter Tables (Page 39)
Pick List Variable Tables (Page 44)
NXGpro Communication
54 Function Manual, AD, A5E33486415A
Modbus Communication
4.4 Planning/Configuring
The SOP flag is set to "1" (true) when the network connection is operating normally, and "0"
(false) when it is not operating normally.
The network status cannot be automatically detected. Instead, a "Pulse Timeout" method is
used to set the network status flags.
The "Pulse Timeout" status detection must be set up in the menu system, and has to be
“strobed” by a network device that is communicating with the drive.
Task
Set up network to indicate the following drive outputs on the PLC:
● general status
● motor speed
● output power
● number of active faults.
Procedure
Refer to Table Correspondence between Drive Parameter ID and Communication Protocol
Address in Section Parameter Assignment/Addressing to establish whether an address or
register is changeable.
To indicate general status and motor speed:
1. The table shows that:
NXGpro Communication
Function Manual, AD, A5E33486415A 55
Modbus Communication
4.4 Planning/Configuring
● 'Data from Drive 01' is not changeable; it is set to indicate general status. No action is
required.
● 'Data from Drive 02' is not changeable; it is set to indicate motor speed. No action is required.
To indicate output power:
1. The table shows that 'Data from Drive 03' is changeable, this can be set to indicate output
power.
2. Refer to Table Correspondence between Drive Parameter ID and Communication Protocol
Address to determine that the corresponding parameter ID is 9403.
3. Enter parameter ID 9403.
4. Choose "output power" from the pick list.
The output power will be sent to the PLC using register 'Data from Drive 03'.
To indicate the number of active faults:
1. The table shows that 'Data from Drive 04' is changeable, this can be set to indicate the
number of active faults.
2. Refer to Table Correspondence between Drive Parameter ID and Communication Protocol
Address to determine that the corresponding parameter ID is 9404.
3. Enter parameter ID 9404.
4. The pick list of data from drive variables appears. As "number of active faults" is not an
option in the pick list, you must specify it manually.
5. Refer to Table Data From Drive Pick List Variables in Section Parameter Assignment/
Addressing for a list of 'data from drive' pick list variables.
Since "number of active faults" is not a choice in the pick list, instead choose "Man Id"
(manual ID). The display shows "ManId-0000".
6. Refer to Appendix Output Data IDs and locate "number of active faults" in the tables to
determine its data ID number (3000).
7. Use arrow or number keys to enter 3000, and press [ENTER]. The display now shows
"ManId-3000".
The number of active faults will be sent to the PLC using register 'Data from Drive 04'.
● If the data ID number is not found, the error message "Invalid Id Entered" is displayed.
Ensure that the data ID is correct.
See also
Correspondence between Drive Parameter ID and Communication Protocol Address (Page 38)
NXGpro Communication
56 Function Manual, AD, A5E33486415A
Modbus Communication
4.5 Functions
4.5 Functions
Description
The "read coil" command allows you to obtain the ON or OFF status of logic coils used to control
discrete outputs from the addressed slave.
Coils are numbered beginning from 0 (coil number 1 = 0, coil number 2 = 1, and so on).
Example
A sample of a "read coil" request to read coils 0020 to 0056 from a slave device number 3 and
the associated response is given below.
The meaning of the sample request and associated response is detailed in the following tables.
Request Details
NXGpro Communication
Function Manual, AD, A5E33486415A 57
Modbus Communication
4.5 Functions
Response Details
Description
The "read holding registers" command allows the Modbus master to read up to 64 consecutive
memory registers from the drive.
NXGpro Communication
58 Function Manual, AD, A5E33486415A
Modbus Communication
4.5 Functions
Example
A sample of a "read holding registers" request to read 2 registers (40005 and 40006) and the
associated response, in hexadecimal, is given below.
The meaning of the sample request and associated response is detailed in the following tables.
Request Details
Response Details
Field Name Value (in Hex) Actual Result Scaled Value Description
Slave Address 0x01 N/A N/A 0x01 = 1 decimal
Function 0x03 N/A N/A Read holding registers
command
Byte Count 0x04 N/A N/A 4 bytes in response
Data Value 1 (MSB) 0x04 0x04A5 This register is user program‐ High byte of item 1
Data Value 1 (LSB) 0xA5 mable. See Table Register Da‐ Low byte of item 1
ta from Drive Menu (9400).
Data Value 2 (MSB) 0x90 0x90B1 High byte of item 2
Data Value 2 (LSB) 0xB1 Low byte of item 2
CRC byte 1 --- N/A N/A Byte 1 for this mes‐
sage
CRC byte 2 --- N/A N/A Byte 2 for this mes‐
sage
NXGpro Communication
Function Manual, AD, A5E33486415A 59
Modbus Communication
4.5 Functions
Note
Parameter names and their corresponding data ID numbers are listed in Appendix Output Data
IDs.
Note
For responses received from the drive such as in Table Read Holding Registers Response
(RX) from Drive , the keypad parameter 'Velocity Units' (9080) is set to "Percent" by default.
Scaled values differ depending on how this parameter is configured. This is described in
Table Configure Parameters Menu (9902) in Section Parameter assignment/addressing.
Refer to Table General Data Register Assignments in Appendix Output Data IDs for data
scaling.
Description
The "write multiple coils" command forces multiple coils in a consecutive block to a desired ON
or OFF state. Any coil that exists within the controller can be forced to either state. The
controller can also alter the state of the coil.
Coils are numbered beginning from 0 (coil number 1 = 0, coil number 2 = 1, and so on).
Example
A sample of a "write multiple coils" request to force a slave device number 1 to write 10 coils
starting at address 20 (13 HEX), and the associated response is given below.
The 2 data fields, CD = 1100 and 00 = 000 0000, indicate that coils 27, 26, 23, 22, and 20 are
to be forced on.
The meaning of the sample request and associated response is detailed in the following tables.
Request Details
NXGpro Communication
60 Function Manual, AD, A5E33486415A
Modbus Communication
4.5 Functions
Response Details
Description
The "write input register" command allows the Modbus master to write a value to a specified
input register in the drive.
Example
A sample of a "write input register" request to write a value to register 40067 and the associated
response, in hexadecimal, is given below.
The meaning of the sample request and associated response is detailed in the following table.
NXGpro Communication
Function Manual, AD, A5E33486415A 61
Modbus Communication
4.5 Functions
Request Details
Response Details
The write input register response (RX) from the drive is an echo of the request and therefore is
identical; refer to table above.
Note
Parameter names and their corresponding data ID numbers are listed in Appendix Output Data
IDs.
Description
The "loop back test" command allows the Modbus master to test the communication link to the
drive.
Example
A sample of a "loop back test" request and the associated response, in hexadecimal, is given
below.
The loop back test response (RX) from the drive is an echo of the request and therefore is
identical.
NXGpro Communication
62 Function Manual, AD, A5E33486415A
Modbus Communication
4.5 Functions
Description
The "write multiple input registers" command allows the Modbus master to write up to 64 values
(in a single command) to multiple input registers in the drive.
Example
A sample of a "write multiple input registers" command to write to 2 registers and the
associated response, in hexadecimal, is given below.
The meaning of the sample request and associated response is detailed in the following tables.
Request Details
Table 4-31 Write Multiple Input Registers Request (TX) from Master
Response Details
Table 4-32 Write Multiple Input Registers Response (RX) from Drive
NXGpro Communication
Function Manual, AD, A5E33486415A 63
Modbus Communication
4.5 Functions
Note
Parameter names and their corresponding data ID numbers are listed in Appendix Output Data
IDs.
NXGpro Communication
64 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication 5
This chapter contains instructions for controlling the drive using a PLC over an Modbus™
Ethernet network. It addresses the following topics:
● Description of the interface
● User Programming
● Parameter assignment and addressing
● Configuration and setup options
● Available functions
5.1 Description
The Modbus™ Ethernet communication interface is based on the TCP/IP protocol. All
addressing is based on IP addresses.
The drive always acts as a Modbus™ slave. This means that the drive does not initiate dialog
on the Modbus™ Ethernet network. Rather, it listens to and then responds to the Modbus™
Ethernet master.
Note
Only register-based read and write functions of the Modbus™ protocol are supported. These
functions are used to monitor and control analog and digital inputs and outputs of the drive.
Only the Remote Terminal Unit (RTU) format of the Modbus™ protocol is supported by the
NXGpro Control. All requests are sent via register port 502.
Refer to Section Functions for function codes supported by the NXGpro Control.
To enable dual network functionality, this protocol requires an additional Anybus™ module.
See also
Functions (Page 93)
NXGpro Communication
Function Manual, AD, A5E33486415A 65
Modbus Ethernet Communication 5
This chapter contains instructions for controlling the drive using a PLC over an Modbus™
Ethernet network. It addresses the following topics:
● Description of the interface
● User Programming
● Parameter assignment and addressing
● Configuration and setup options
● Available functions
5.1 Description
The Modbus™ Ethernet communication interface is based on the TCP/IP protocol. All
addressing is based on IP addresses.
The drive always acts as a Modbus™ slave. This means that the drive does not initiate dialog
on the Modbus™ Ethernet network. Rather, it listens to and then responds to the Modbus™
Ethernet master.
Note
Only register-based read and write functions of the Modbus™ protocol are supported. These
functions are used to monitor and control analog and digital inputs and outputs of the drive.
Only the Remote Terminal Unit (RTU) format of the Modbus™ protocol is supported by the
NXGpro Control. All requests are sent via register port 502.
Refer to Section Functions for function codes supported by the NXGpro Control.
To enable dual network functionality, this protocol requires an additional Anybus™ module.
See also
Functions (Page 93)
NXGpro Communication
Function Manual, AD, A5E33486415A 65
Modbus Ethernet Communication
5.1 Description
Description
Note
Network Usage
The Anybus™ Ethernet module is the only hardware that can be used for Network 2 .
The following figure shows the connector and status indicators on the Anybus™ Modbus™
Ethernet module. The DIP switches are not used for the NXGpro application.
NXGpro Communication
66 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.1 Description
1 RJ-45 connector
2 DIP switches (not used)
3 Status indicators
Figure 5-1 Anybus Ethernet Module
Status Indicators
The following figure shows the status indicators.
.Refer to Table Status Indicator Table to view explanation of the various status indicators
NXGpro Communication
Function Manual, AD, A5E33486415A 67
Modbus Ethernet Communication
5.2 Software Programming
Pick list variable in 'Data to Drive Reg nn' menus Corresponding Drctry.pro bits Modbus Address
Fixed Reg Bits (network 1) CPU Network1FixedRegBit0_I ~ Network1FixedReg‐ 40065 or 41025
(only valid on NXGpro software version 6.1 and Bit15_I
earlier)
Fixed Reg Bits (network 1) Anybus Network1FixedRegBit0_I ~ Network1FixedReg‐ 41025
Bit15_I
Fixed Reg Bits (network 2) Network2FixedRegBit0_I ~ Network2FixedReg‐ 41025
Bit15_I
Description
There are 64 input bits available for user programming through the SOP file. These bits can be
programmed to set or reset any other bits used within the SOP.
NXGpro Communication
68 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.2 Software Programming
Programming Procedure
1. Locate the first data to drive register that is programmable using Table Correspondence
between Drive Parameter ID and Communication Protocol Address in Section Parameter
Assignment/Addressing.
You will see that the first programmable data to drive register for network 1 is register 'Data
to Drive 03', which corresponds to parameter ID (9603).
2. Enter parameter ID (9603).
3. The pick list of data to drive variables will appear. Refer to Table Data to Drive Pick List
Variables and Scaling in Section Parameter Assignment/Addressing for a list of data to drive
pick list variables.
4. Scroll through the pick list until you come to 'Net Input Flag 1' and press [ENTER]. This
setting uses the first 16 bits of the possible 64 bits.
Now the corresponding bits from the drctry.pro file can be used in the SOP, as shown below:
;Network1Flag0_I Use bit 0 for Stop bit
;Network1Flag1_I Use bit 1 for Run Forward bit
RunRequest_O = /Network1Flag0_I * Network1Flag1_I;Run drive using
bit 1,stop using bit 0
5. Select 'Net Input Flag 2' to use the second set of 16 bits, and so on.
Note
By choosing 'Data to Drive 03' as the write register, the PLC must now send 0x02 in register
'Data to Drive 03' to run the drive.
To stop the drive, the PLC must send 0x01 in register 'Data to Drive 03'.
The pick list variables and the corresponding programmable input bits are found in the following
tables for network 1 and 2, respectively.
Pick list variable in 'Data to Drive Reg nn' menus Related Drctry.pro bits
Net Input Flag 1 Network1Flag0_I ~ Network1Flag15_I
Net Input Flag 2 Network1Flag16_I ~ Network1Flag31_I
Net Input Flag 3 Network1Flag32_I ~ Network1Flag47_I
Net Input Flag 4 Network1Flag48_I ~ Network1Flag63_I
Pick list variable in 'Data to Drive Reg nn' menus Related Drctry.pro bits
Net Input Flag 1 Network2Flag0_I ~ Network2Flag15_I
Net Input Flag 2 Network2Flag16_I ~ Network2Flag31_I
Net Input Flag 3 Network2Flag32_I ~ Network2Flag47_I
Net Input Flag 4 Network2Flag48_I ~ Network2Flag63_I
NXGpro Communication
Function Manual, AD, A5E33486415A 69
Modbus Ethernet Communication
5.2 Software Programming
Example
The following example shows how the network can be programmed to trip the input medium
voltage:
● The PLC writes to register 'Data to Drive 03' which is programmed to 'Net Input Flag 1' using
the procedure above.
● The SOP sets a flag bit that uses a digital output to trip input medium voltage, using the
following SOP source code:
● The PLC writes the contents of 'Net Input Flag 1', bit 9 (Network1Flag9_I) to create an input
medium voltage trip.
Description
There are 64 output bits available for user programming through the SOP file. These bits can
be programmed to set or reset any other bits used within the SOP.
Programming Procedure
1. Locate the first data from drive register that is programmable using Table Correspondence
between Drive Parameter ID and Communication Protocol Address in Section Parameter
Assignment/Addressing.
You will see that the first programmable data from drive register for network 1 is register
'Data from Drive 03', which corresponds to parameter ID (9403).
2. Enter parameter ID (9403).
3. The pick list of data from drive variables will appear. Refer to Table Data from Drive Pick List
Variables in Section Parameter Assignment/Addressing for a list of data from drive pick list
variables.
4. Scroll through the pick list until you come to 'Net1 Out Reg 1' and press [ENTER]. This
setting uses the first 16 bits of the possible 64 bits.
5. Select 'Net1 Out Reg 2' to use the second set of 16 bits, and so on.
The pick list variables and the corresponding programmable output bits are found in the
following tables for network 1 and 2, respectively.
Pick list variable in 'Data from Drive Reg nn' menus Related Drctry.pro bits
Net1 Out Reg 1 Network1Flag0_O ~ Network1Flag15_O
Net1 Out Reg 2 Network1Flag16_O ~ Network1Flag31_O
NXGpro Communication
70 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Pick list variable in 'Data from Drive Reg nn' menus Related Drctry.pro bits
Net1 Out Reg 3 Network1Flag32_O ~ Network1Flag47_O
Net1 Out Reg 4 Network1Flag48_O ~ Network1Flag63_O
Pick list variable in 'Data from Drive Reg nn' menus Related Drctry.pro bits
Net2 Out Reg 1 Network2Flag0_O ~ Network2Flag15_O
Net2 Out Reg 2 Network2Flag16_O ~ Network2Flag31_O
Net2 Out Reg 3 Network2Flag32_O ~ Network2Flag47_O
Net2 Out Reg 4 Network2Flag48_O ~ Network2Flag63_O
Example
The following example shows how the network can be programmed to detect a trip on the input
medium voltage:
● The PLC reads register 'Data from Drive 03', which is programmed to 'Net1 Out Reg 1' using
the procedure above.
● The SOP sets a flag bit that corresponds to a medium voltage low fault, using the following
SOP source code:
● This example uses bit 9 of 'Net1 Out Reg 1', which is Network1Flag9_O, to set the network
flag true if the medium voltage low fault is active.
● The PLC reads the contents of 'Net1 Out Reg 1', bit 9 (Network1Flag9_O) to determine if a
medium voltage fault occured.
NXGpro Communication
Function Manual, AD, A5E33486415A 71
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
NXGpro Communication
72 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Network Parameters
NXGpro Communication
Function Manual, AD, A5E33486415A 73
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Network 1 Parameters
NXGpro Communication
74 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Table 5-12 Network 1: TCP/IP Setup Menu (9300) when "Ethernet Modbus Type" (9906) is set to "Internal CPU" 1
Table 5-13 Network 1: TCP/IP Setup Menu (9902) when "Ethernet Modbus Type" (9906) is set to "Anybus Module"1,2
NXGpro Communication
Function Manual, AD, A5E33486415A 75
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Network 2 Parameters
NXGpro Communication
76 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
NXGpro Communication
Function Manual, AD, A5E33486415A 77
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
NXGpro Communication
78 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Mux1 Echo None None None None Refer to Appendix Multiplexer (MUX) Data
Mux1 Data Registers
Mux2 Echo
Mux2 Data
Mux3 Echo
Mux3 Data
Mux4 Echo
Mux4 Data
Mux5 Echo
Mux5 Data
Mux6 Echo
Mux6 Data
Mux7 Echo
Mux7 Data
Mux8 Echo
Mux8 Data
Wago Inputs 1-16 2650 None None Bit Field ExternalDigitalInput01a_I - ExternalDigita‐
lInput01h_I
ExternalDigitalInput02a_I - ExternalDigita‐
lInput02h_I
Wago Inputs 17-32 2651 None None Bit Field ExternalDigitalInput03a_I - ExternalDigita‐
lInput03h_I
ExternalDigitalInput04a_I - ExternalDigita‐
lInput04h_I
Wago Inputs 33-48 2652 None None Bit Field ExternalDigitalInput05a_I - ExternalDigita‐
lInput05h_I
ExternalDigitalInput06a_I - ExternalDigita‐
lInput06h_I
Wago Inputs 49-64 2653 None None Bit Field ExternalDigitalInput07a_I - ExternalDigita‐
lInput07h_I
ExternalDigitalInput08a_I - ExternalDigita‐
lInput08h_I
Wago Inputs 65-80 2654 None None Bit Field ExternalDigitalInput09a_I - ExternalDigita‐
lInput09h_I
ExternalDigitalInput10a_I - ExternalDigita‐
lInput10h_I
Wago Inputs 81-96 2655 None None Bit Field ExternalDigitalInput11a_I - ExternalDigita‐
lInput11h_I
ExternalDigitalInput12a_I - ExternalDigita‐
lInput12h_I
Wago Outputs 1-16 2656 None None Bit Field ExternalDigitalOutput01a_O - ExternalDigi‐
talOutput01h_O
ExternalDigitalOutput02a_O - ExternalDigi‐
talOutput02h_O
NXGpro Communication
Function Manual, AD, A5E33486415A 79
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
Wago Outputs 17-32 2657 None None Bit Field ExternalDigitalOutput03a_O - ExternalDigi‐
talOutput03h_O
ExternalDigitalOutput04a_O - ExternalDigi‐
talOutput04h_O
Wago Outputs 33-48 2658 None None Bit Field ExternalDigitalOutput05a_O - ExternalDigi‐
talOutput05h_O
ExternalDigitalOutput06a_O - ExternalDigi‐
talOutput06h_O
Wago Outputs 49-64 2659 None None Bit Field ExternalDigitalOutput07a_O - ExternalDigi‐
talOutput07h_O
ExternalDigitalOutput08a_O - ExternalDigi‐
talOutput08h_O
PFD1 None None None None Refer to Appendix Parameter Read/Write
PFD2
PFD3
PFD4
Drive Losses 2161 % /100 Unsigned
Excessive Reactive 2162 % /100 Unsigned
Current
Speed Droop Percent 2163 % /100 Unsigned
Sync Motor Field Ref 2164 % /100 Unsigned
Avail Reactive Current 3653 % /100 Unsigned
Drive Efficiency 2168 % /100 Unsigned
Ids Ref Current 2276 % /100 Unsigned
NXGpro Communication
80 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
NXGpro Communication
Function Manual, AD, A5E33486415A 81
Modbus Ethernet Communication
5.3 Parameter Assignment/Addressing
NXGpro Communication
82 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.4 Planning/Configuring
5.4 Planning/Configuring
This section describes the setup methods available for communication. The following topics
are explained:
● Fast setup procedures
● Network interfaces
● Network setup procedure
● Network status detection
● An example to illustrate the setup procedure.
Note
Fast setup procedures allow setup of a Network 1 interface with a minimum of detail.
5.4.1 Fast Setup: Control the drive using the default configuration
To control the drive using the default configuration, you must send commands to the drive's
'fixed reg bits' location. This location is register 'Data to Drive 01' as provided in
Table Correspondence between Drive Parameter ID and Communication Protocol Address in
Section Parameter Assignment/Addressing.
To control the drive from a PLC using the default configuration, complete the following steps.
1. Set parameter 'Network 1 Type' (9901) to "Ethernet Modbus". This setup assumes that an
existing working TCP/IP network is established.
2. Verify the network settings for the parameters 'Subnet Mask' and 'Gateway Address' . Refer
to Tables titled Network 1: TCP/IP Setup Menu. and Network 1: TCIP/IP Setup Menu
located in the previous section of this chapter to find the parameter numbers for the
'Gateway Address' and the 'Subnet Mask' based on the NXGpro software version and
hardware configuration.
3. Set parameter 'IP Address'. The IP address must be unique to the drive. Refer to Tables
titled Network 1: TCP/IP Setup Menu. and Network 1 : TCIP/IP Setup Menu located in the
previous section of this chapter to find the parameter number for the 'IP Address' based on
the NXGpro software version and hardware configuation.
4. Set parameter 'Net Control Type' (9944) to "Fixed". This sets the bits at register 'Data to
Drive 01' where the fixed register bits are located. The fixed register bits are interpreted as
shown in the following table.
5. Add the following line to the SOP:
Network1RunEnable_O = TRUE;
NXGpro Communication
Function Manual, AD, A5E33486415A 83
Modbus Ethernet Communication
5.4 Planning/Configuring
Note
To run the drive, the PLC must send 0x21 to register 'Data to Drive 01'. This hexadecimal value
sets bit 0 (run) and bit 5 (start/stop control from network).
To stop the drive, the PLC must send 0x08 or 0x00 to register 'Data to Drive 01'.
NXGpro Communication
84 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.4 Planning/Configuring
4. Set parameter 'Velocity Units' (9080) to the desired motor speed units.
5. Refer to the Table Correspondence between Drive Parameter ID and Communication
Protocol Address in Section Parameter Assignment/Addressing to obtain the addresses for
general status (Data from Drive 01) and motor speed feedback (Data from Drive 02) from
the drive.
– 'Data from Drive 01' (9401) is read by sending the read register request in address
40001.
– 'Data from Drive 02' (9402) is read by sending the read register request in address
40002, and so on.
The general drive status bits found in register 'Data from Drive 01' are defined in the following
table.
Note
You cannot reprogram the drive's default interpretation of output bits.
Refer to Network Setup Procedure for details on how to read other drive data.
NXGpro Communication
Function Manual, AD, A5E33486415A 85
Modbus Ethernet Communication
5.4 Planning/Configuring
5.4.4 Fast Setup: Control the drive using user-defined bits controlled by the SOP
To control the drive using non-default configuration, you must redefine the fixed register bits at
register 'Data to Drive 01'.
Note
The 'fixed reg bits' location is fixed at register 'Data to Drive 01', whether the default
configuration is used or not.
You cannot reprogram the 'fixed reg bits' location.
You can reprogram the definition of the bits at this address.
NXGpro Communication
86 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.4 Planning/Configuring
5. Next, set up the drive to correspond with the bits you want to use in the SOP. Refer to
Section Software Programming to find the bits and locate the associated keypad pick list
variable, and use the procedures detailed in this section to complete set up.
6. To enable speed settings from the network, add the following line to the SOP file:
RawDemandNetwork1_O = true;
See also
Software Programming (Page 68)
(WKHUQHW0RGEXV'HYLFH 1;*SUR&RQWURO
&URVVRYHUFDEOH
DQGFRXSOHU
NXGpro Communication
Function Manual, AD, A5E33486415A 87
Modbus Ethernet Communication
5.4 Planning/Configuring
1;*SUR&RQWURO
(WKHUQHW,3'HYLFH +XE
1;*SUR&RQWURO
NXGpro Communication
88 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.4 Planning/Configuring
Note
Setup functions are contained in the Configure Parameters Menu (9902), which is a submenu
of the Communications Menu (9).
Access is security-controlled at level 7; you must enter the security code to access these
parameters.
Refer to the NXGpro Control Operating Manual for further information on security access levels
and codes.
Use the following procedure to complete network setup. Refer to Table Configure Parameters
Menu (9902) in Section Parameter Assignment/Addressing for the menus needed to complete
setup.
Procedure
1. Select a protocol using parameter 'Network 1 Type' (9901). Scroll to "Ethernet/IP" and press
[ENTER]. The configuration parameters are viewable.
2. Set parameter 'Velocity Units' (9080) to the desired motor speed units for motor
commanded speed and motor feedback speed scaling.
3. Where necessary, set parameter 'Demand Scalar' (9912) to:
n x command speed where –125 % to 125 %
4. Set parameter 'Aux Demand Scalar' (9913) if used.
5. Use Table Correspondence between Drive Parameter ID and Communication Protocol
Address in Section Parameter Assignment/Addressing to program the drive to send data to
and receive commands from the network. The table provides all available addresses with
corresponding parameter ID as well as pre-programmed addresses, which provide basic
drive send and receive functionality and are not changeable.
6. Define the bits in the available addresses using one of the following methods:
NXGpro Communication
Function Manual, AD, A5E33486415A 89
Modbus Ethernet Communication
5.4 Planning/Configuring
● Enter from a choice of variables in the pick lists. The pick lists in the menus contain the most
commonly used data variables. Refer to Section Parameter Assignment/Addressing for the
pick lists.
Note
A pick list item can only be used once for each 'Data to Drive' register.
● For 'Data from Drive' registers, choose pick list option "Man Id" (manual ID) to manually
enter a variable that is not included in the pick lists, using the output data ID number. Use
the list of data IDs available in Appendix Output Data IDs to locate the variable and use the
corresponding ID number to enter the variable into the 'Data from Drive' register.
Note
The output data ID number is not the same as a parameter ID number.
● Custom program using the drive's SOP. Refer to Section Software Programming for details.
Note
The PLC can receive data from the drive without any changes to the SOP.
Only if you need to control the drive through the network will you need to set any flags in the
SOP.
See also
Output Data IDs (Page 263)
Software Programming (Page 103)
NXGpro Communication
90 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.4 Planning/Configuring
The network status cannot be automatically detected. Instead, a "Pulse Timeout" method is
used to set the network status flags.
The "Pulse Timeout" status detection must be set up in the menu system, and has to be
“strobed” by a network device that is communicating with the drive.
Task
Set up network to indicate the following drive outputs on the PLC:
● general status
● motor speed
● output power
● number of active faults.
Procedure
Refer to Table Correspondence between Drive Parameter ID and Communication Protocol
Address in Section Parameter Assignment/Addressing to establish whether an address or
register is changeable.
To indicate general status and motor speed:
1. The table shows that:
● 'Data from Drive 01' is not changeable; it is set to indicate general status. No action is
required.
● 'Data from Drive 02' is not changeable; it is set to indicate motor speed. No action is required.
NXGpro Communication
Function Manual, AD, A5E33486415A 91
Modbus Ethernet Communication
5.4 Planning/Configuring
See also
Correspondence between Drive Parameter ID and Communication Protocol Address (Page 72)
NXGpro Communication
92 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.5 Functions
5.5 Functions
Description
The "read holding registers" command allows the Modbus master to read up to 64 consecutive
memory registers from the drive.
Example
A sample of a "read holding registers" request to read 2 registers (40005 and 40006) and the
associated response, in hexadecimal, is given below.
The meaning of the sample request and associated response is detailed in the following tables.
NXGpro Communication
Function Manual, AD, A5E33486415A 93
Modbus Ethernet Communication
5.5 Functions
Request Details
Response Details
Field Name Value (in Hex) Actual Result Scaled Value Description
Transaction identifier 0
Transaction identifier 0
Protocol identifier 0
Protocol identifier 0
Length field (upper 0
byte)
Length field (lower Number of bytes to
byte) follow
Slave Address 0x01 N/A N/A 0x01 = 1 decimal
Function 0x03 N/A N/A Read holding registers
command
Byte Count 0x04 N/A N/A 4 bytes in response
Data Value 1 (MSB) 0x04 0x04A5 This register is user program‐ High byte of item 1
Data Value 1 (LSB) 0xA5 mable. See Table Register Da‐ Low byte of item 1
ta from Drive Menu (9400).
Data Value 2 (MSB) 0x90 0x90B1 High byte of item 2
Data Value 2 (LSB) 0xB1 Low byte of item 2
Note
Parameter names and their corresponding data ID numbers are listed in Appendix Output Data
IDs.
NXGpro Communication
94 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.5 Functions
Note
For responses received from the drive such as in Table Read Holding Registers Response
(RX) from Drive , the keypad parameter 'Velocity Units' (9080) is set to "Percent" by default.
Scaled values differ depending on how this parameter is configured. This is described in
Table Configure Parameters Menu (9902) in Section Parameter assignment/addressing.
Refer to Table General Data Register Assignments in Appendix Output Data IDs for data
scaling.
Description
The "write input register" command allows the Modbus master to write a value to a specified
input register in the drive.
Example
A sample of a "write input register" request to write a value to register 40067 and the associated
response, in hexadecimal, is given below.
The meaning of the sample request and associated response is detailed in the following table.
Request Details
NXGpro Communication
Function Manual, AD, A5E33486415A 95
Modbus Ethernet Communication
5.5 Functions
Response Details
The write input register response (RX) from the drive is an echo of the request and therefore is
identical; refer to table above.
Note
Parameter names and their corresponding data ID numbers are listed in Appendix Output Data
IDs.
Description
The "write multiple input registers" command allows the Modbus master to write up to 64 values
(in a single command) to multiple input registers in the drive.
Example
A sample of a "write multiple input registers" command to write to 2 registers and the
associated response, in hexadecimal, is given below.
The meaning of the sample request and associated response is detailed in the following tables.
Request Details
Table 5-28 Write Multiple Input Registers Request (TX) from Master
NXGpro Communication
96 Function Manual, AD, A5E33486415A
Modbus Ethernet Communication
5.5 Functions
Response Details
Table 5-29 Write Multiple Input Registers Response (RX) from Drive
Note
Parameter names and their corresponding data ID numbers are listed in Appendix Output Data
IDs.
NXGpro Communication
Function Manual, AD, A5E33486415A 97
Modbus Ethernet Communication
5.5 Functions
NXGpro Communication
98 Function Manual, AD, A5E33486415A
Ethernet / IP Communication
6.5 Planning/Configuring
NXGpro Communication
Function Manual, AD, A5E33486415A 125