Fronius prints on elemental chlorine free paper (ECF) sourced from certified sustainable forests (FSC).
/ Perfect Charging / Perfect Welding / Solar Energy
RI FB/i Yaskawa WeldCom 2.0
RI MOD/i CC Modbus TCP-2P
Operating instructions
EN-US
42,0426,0218,EA 029-11012022
Table of contents
General5
Safety5
Device Concept5
Block Diagram6
Scope of Supply6
Required Tools and Materials6
Installation Requirements6
Connections and Indicators7
Connections on the Robot Interface7
Pin Assignment of M12 Connection7
LEDs on Robot Interface PCB8
LEDs for Power Supply Diagnosis9
LEDs for Network Connection Diagnosis9
Connections and indicators on RJ 45 module10
Examples of How the M12 Connection Is Used12
Examples of How the M12 Connection Is Used12
Technical data13
Environmental Conditions13
Robot Interface Technical Data13
Data Transfer Properties13
Configuration Parameters14
Configuration of robot interface15
General15
Configuring the Process Image15
Setting the IP Address15
Configuring the Robot Interface16
Installing the Robot Interface17
Safety17
Preparation17
Fitting the M12 Connection18
Routing the Data Cable19
Installing the Robot Interface20
Final Tasks20
Installing the Bus Module21
Safety21
Installing the Bus Module21
Input and output signals22
Data types22
Input Signals22
Value range Process line selection25
Value Range for TWIN Mode25
Value Range for Documentation mode26
Value range Working mode26
Value Range for Command value selection26
Output signals27
Value Range for Welding Process and Process Image30
Assignment of Sensor Statuses 1–330
Value range Safety status30
TAG Table31
Retrofit Image Input and Output Signals34
Input signals34
Value Range for Operating Mode35
Output Signals37
TAG Table38
Modbus – General Information40
Protocol Description40
Data Coding40
Application Data Unit (ADU)41
Danger from incorrect operation and work that is not carried out properly.
This can result in serious personal injury and damage to property.
All the work and functions described in this document must only be carried out by
▶
technically trained and qualified personnel.
Read and understand this document in full.
▶
Read and understand all safety rules and user documentation for this equipment
▶
and all system components.
WARNING!
Danger from electrical current.
This can result in serious personal injury and damage to property.
Before starting work, switch off all devices and components involved, and discon-
▶
nect them from the grid.
Secure all devices and components involved so they cannot be switched back on.
▶
WARNING!
Danger from unplanned signal transmission.
This can result in serious personal injury and damage to property.
Do not transfer safety signals via the interface.
▶
Device ConceptThe robot interface serves as an interface between the power source and standardized
bus modules supporting a wide range of communication protocols.
Fronius may factory-fit the robot interface in the power source but it can also be retrofitted by appropriately trained and qualified personnel.
(1)Robot control system
(2)SpeedNet data cable
(3)Robot interface
(4)Power source
5
Block Diagram
SpiderNT241
RI FB/i Yaskawa
WeldCom 2.0
Data
24 V
Module
(1)
(2)
(4)
(5)
(3)
(5)Cooling unit
(6)Interconnecting hosepack
(7)Wirefeeder
(8)Robot
Scope of Supply
Required Tools
and Materials
(1)RI FB/i Yaskawa WeldCom 2.0
(2)Data cable
4-pin
(3)M12 connection (5-pin)
with connection cable
(4)Cable ties
(5)2 screws for M12 connection
(6)These Operating Instructions
(not pictured)
-Screwdriver TX8
-Screwdriver TX20
-Screwdriver TX25
-Diagonal cutting pliers
Installation Requirements
The robot interface may only be installed in the designated opening on the rear of the
power source.
6
Connections and Indicators
(2)(3)
(1)
(1)(2)
(3)(4)
(5)
EN-US
Connections on
the Robot Interface
Pin Assignment
of M12 Connection
(1)Power supply connection
2-pin
(2)SpeedNet data cableconnection
4-pin
(3)Bus module connection
WeldCom 2.0Retrofit
(1)CAT signalCAT signal
(2)TouchedArc stable
(3)CAT signal GNDCAT signal GND
(4)Touched GNDArc stable GND
(5)n.c (not connected)
7
LEDs on Robot
(14)
(13)
(12)
(11)
(2)
(1)
(9)
(10)
(8)
(7)
(3) (4)
(5) (6)
Interface PCB
(1)ETH1 LEDGreenFor diagnosing the network connection.
For details, see section below titled "LEDs
(2)ETH2 LEDOrange
for Network Connection Diagnosis"
(3)LED 3Green
No function
(4)LED 4Green
-Flashes at 4 Hz = No SpeedNet connection
(5)LED 5Green
-Flashes at 20 Hz = Establishing
SpeedNet connection
-Flashes at 1 Hz = SpeedNet connection established
Lights up when an internal error occurs.
(6)LED 6Red
Remedy: Restart the robot interface. If this
does not resolve the issue, inform the service team.
(7)+3V3 LEDGreenFor diagnosing the power supply.
For details, see section below titled "LEDs
(8)+24V LEDGreen
for Power Supply Diagnosis"
(9)DIG OUT 2 LEDGreenDigital output 2. LED lights up when active
(10)DIG OUT 1 LEDGreenDigital output 1. LED lights up when active
8
(11)LED 11Green
LEDs for Power
Supply Diagnosis
(12)LED 12Green
(13)LED 13Green
(14)LED 14Green
LEDIndicatorMeaningCause
Off
+24V
Lights up
Off
+3V3
Lights up
No supply voltage available for
interface
24 VDC supply voltage
present on robot interface
No operating voltage present
on robot interface
3 VDC operating voltage
present on robot interface
No function
-Robot interface power
supply not established
-Power supply cable faulty
-24 VDC supply voltage
not present
-Robot interface power
supply unit is faulty
EN-US
LEDs for Network
Connection Diagnosis
LEDIndicatorMeaningCause
-No network connection
ETH1
ETH2
OffNo network connection
Lights up
FlashesData transfer in progress
OffTransmission speed 10 Mbit/s
Lights up
Network connection established
Transmission speed
100 Mbit/s
established for interface
-Network cable faulty
9
Connections and
(12)(11)(10)
(14)(13)
(9)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
indicators on RJ
45 module
(11)RJ-45 Ethernet connection 2
(12)RJ-45 Ethernet connection 1
(13)Link/Activity LED 1
(14)Network status LED
(1)TX+
(2)TX-
(3)RX+
(6)RX-
(4)Not normally used; to ensure
(5)
(7)
(8)
signal completeness, these pins
must be interconnected and,
after passing through a filter circuit, must terminate at the
ground conductor (PE).
(9)Link/Activity LED 2
(10)Module status LED
Network Status LED:
StatusMeaning
OffNo IP address or exception state
Lights up greenAt least one Modbus message received
Flashes greenWaiting for first Modbus message
Lights up redIP address conflict, serious error
Flashes redConnection timeout. No Modbus message was received
within the period defined for the "Process active timeout"
Module Status LED:
StatusMeaning
OffNo supply voltage
Lights up greenNormal operation
Lights up redMajor error (exception state, serious fault, etc.)
Flashes redMinor error
Alternates between red
Firmware update in progress
and green
10
Link/Activity LED:
StatusMeaning
OffNo connection, no activity
Lights up greenConnection established (100 Mbit/s)
Flickers greenActivity (100 Mbit/s)
Lights up yellowConnection established (10 Mbit/s)
A risk is posed by prohibited environmental conditions.
This can result in severe damage to equipment.
Only store and operate the device under the following environmental conditions.
▶
Temperature range of ambient air:
-During operation: -10 °C to +40 °C (14 °F to 104 °F)
-During transport and storage: -20 °C to +55 °C (-4 °F to 131 °F)
Relative humidity:
-Up to 50% at 40 °C (104 °F)
-Up to 90% at 20 °C (68 °F)
Ambient air: free of dust, acids, corrosive gases or substances, etc.
Altitude above sea level: up to 2000 m (6500 ft).
Power supplyInternal (24 V)
Degree of protectionIP 23
Data Transfer
Properties
RJ-45 Connection
Transmission technology:
Ethernet
Medium (4 x 2 twisted-pair copper cable):
Category 5 (100 Mbit/s) or higher
Transmission speed:
10 Mbit/s or 100 Mbit/s
Bus connection:
Ethernet RJ-45
M12 Connection
Voltage:
24 V
Current load per output:
Max. 20 mA
13
Configuration
Parameters
In some robot control systems, it may be necessary to state the configuration
parameters described here so that the bus module can communicate with the
robot.
ParameterValue
Vendor NameFronius International GmbH
Product Code0340
hex
(832
dec
)
Major / Minor RevisionV1.00
Vendor URLwww.fronius.com
Product Nameyaskawa-weldcom2-0-modbus-tcp
Model Nameyaskawa-weldcom2-0
User Application NameFronius welding controller for the series TPS/i WeldCom2.0
(ModbusTCP)
14
Configuration of robot interface
(1)
(2)
EN-US
General
Configuring the
Process Image
The DIP switch on the robot interface is
used to configure:
-The process image (standard image,
retrofit image)
-The IP address
Default setting for process image:
Positions 7 and 8 of DIP switch set to OFF
(1) = standard image = Weldcom V2.0
Default setting for IP address =
192.168.255.210:
-Positions 6, 5, 3, and 1 of DIP switch
set to OFF (1)
-Positions 2 and 4 of DIP switch set to
ON (2)
DIP Switch
87654321Configuration
OFFOFF
OFFON
------
------
Standard image
(Weldcom V2.0)
Not used
Setting the IP Address
ONOFF
ONON
------
------
Retrofit image
(Weldcom TPS series)
Not used
The process image defines the volume of data transferred and the system compatibility.
You can set the IP address as follows:
-Via the DIP switch within the range defined by 192.168.255.2xx
(xx = DIP switch setting = 01 to 55)
Setting the Address via the DIP Switch:
DIP Switch
IP Address
87654321
--
--
OFFOFFOFFOFFOFFON
OFFOFFOFFOFFONOFF
192.168.255.201
192.168.255.202
:
--
--
ONONOFFONONOFF
ONONOFFONONON
192.168.255.254
192.168.255.255
The IP address can be set via positions 1 to 6 of the DIP switch.
The configuration is carried out in binary format. In decimal format, the setting range is
01 through 55.
15
The following IP address is set via the DIP switch on delivery:
-IP address: 192.168.255.210
-Subnet mask: 255.255.255.0
-Default gateway: 0.0.0.0
Configuring the
Robot Interface
Set the DIP switch in accordance with the desired configuration
1
NOTE!
Risk due to invalid DIP switch settings.
This may result in malfunctions.
Whenever changes are made to the DIP switch settings, the interface must be re-
▶
started. This is the only way for the changes to take effect.
Restart the interface = interrupting and restoring the power supply or executing the
▶
relevant function on the website of the power source (SmartManager).
16
Installing the Robot Interface
EN-US
Safety
Preparation
WARNING!
Electrical current hazard.
This can result in serious injuries or death.
Before starting work, switch off all the devices and components involved and discon-
▶
nect them from the grid.
Secure all the devices and components involved to prevent unintentional restarting.
▶
After opening the device, use a suitable measuring instrument to check that electric-
▶
ally charged components (such as capacitors) have been discharged.
WARNING!
Electrical current hazard caused by an inadequate ground conductor connection.
This can result in severe personal injury and damage to property.
Always use the original housing screws in the original quantity.
▶
12
34
17
5
Fitting the M12
Connection
12
34
18
56
EN-US
Routing the Data
Cable
12
3
19
Installing the Robot Interface
12
Final Tasks
12
20
Installing the Bus Module
EN-US
Safety
Installing the Bus
Module
WARNING!
Danger from electrical current.
Serious injuries or death may result.
Before starting work, switch off all devices and components involved, and discon-
▶
nect them from the grid.
Secure all devices and components involved so that they cannot be switched back
▶
on.
WARNING!
Danger from electrical current due to inadequate ground conductor connection.
Serious personal injury and property damage may result.
Always use the original housing screws in the quantity initially supplied.
▶
12
3
21
Input and output signals
Data typesThe following data types are used:
-UINT16 (Unsigned Integer)
Whole number in the range from 0 to 65535
-SINT16 (Signed Integer)
Whole number in the range from -32768 to 32767
Conversion examples:
-for a positive value (SINT16)
e.g. desired wire speed x factor
12.3 m/min x 100 = 1230
-for a negative value (SINT16)
e.g. arc correction x factor
-6.4 x 10 = -64
Input SignalsFrom robot to power source
Applicable to firmware V2.3.0 and higher
= FFC0
dec
= 04CE
dec
hex
hex
HEX
Ad-
ressSignalType
F000 Control Flag Group 1
Bits 0 to 7Process active timeoutBytems10
F001
Bits 8 to
15
Control Flag Group 2
Bit 0Welding startBoolean
Bit 1Robot readyBoolean
Bit 2Source error resetBoolean
Bit 3Gas onBoolean
Bit 4Wire inchingBoolean
Bit 5Wire retractBoolean
Bit 6Torch blow outBoolean
Bit 7Welding simulationBoolean
Bit 8Touch sensingBoolean
Bit 9Reserved
Bit 10SFI ONBoolean
Reserved
Range /
Unit
Factor
22
Bit 11Synchro pulse onBoolean
Bit 12WireBrakeBoolean
Bit 13Torch XChangeBoolean
Bit 14TeachModeBoolean
Bit 15Reserved
HEX
Ad-
ressSignalType
F002Control Flag Group 3
Range /
Unit
Factor
EN-US
Bit 0Process line selection Bit
0
Bit 1Process line selection Bit
1
Bit 2TWIN mode Bit 0Boolean
Bit 3TWIN mode Bit 1
Bits 4 to 9Reserved
Bit 10Active heat controlBoolean
Bit 11Wire sense startBoolean
Bit 12Wire sense breakBoolean
Bits 13 to15ReservedBoolean
Boolean
See section
Value
range Pro-
Boolean
Boolean
cess line
selection on
page 25
See section
Value
Range for
TWIN Mode
on page 25
F003Control Flag Group 4
Bit 0Documentation modeBooleanSee section
Value
Range for
Documenta-
tion mode
on page 26
Bits 1 to
15
F004Control Flag Group 5
Bits 0 to
15
F005Control Flag Group 6
Bits 0 to
15
F006Control Flag Group 7
Bits 0 to
15
Reserved
Reserved
Reserved
Reserved
23
HEX
Ad-
ressSignalType
F007Control Flag Group 8
Range /
Unit
Factor
F008
Bit 0ExtInput1 => OPT_Out-
put 1
Bit 1ExtInput2 => OPT_Out-
put 2
Bit 2ExtInput3 => OPT_Out-
put 3
Bit 3ExtInput4 => OPT_Out-
put 4
Bit 4ExtInput5 => OPT_Out-
put 5
Bit 5ExtInput6 => OPT_Out-
put 6
Bit 6ExtInput7 => OPT_Out-
put 7
Bit 7ExtInput8 => OPT_Out-
put 8
Bits 8 to
15
Working mode
Bit 0Working Mode Bit 0
Bit 1Working Mode Bit 1
Bit 2Working Mode Bit 2
Bit 3Working Mode Bit 3
Bit 4Working Mode Bit 4
Bits 5 to
13
Reserved
Reserved
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
See section
Value
range
Working
mode on
page 26
Bit 14Command value selec-
tion
Bit 15Reserved
F009Job numberUINT160 to 1000
F00AProgram number (xml-file)UINT160 to 65,535
F00BFeeder command ValueSINT16-327.68 to
F00CArc length correctionSINT16-10 to +1010
F00DPuls/Dynamik correctionSINT16-10 to +1010
F00EWire retractSINT160 to +1010
BooleanSee section
Value
Range for
Command
value selection on page
26
100
327.67
[m/min]
24
HEX
Ad-
ressSignalType
Range /
Unit
F00FWelding speedUINT160 to 65,535
(0 to 6553.5
10
m/min)
F010Penetration stabilizerSINT160 to +1010
F011Arc length stabilizerUINT160 to +1010
F012Reserved
F013Reserved
F014Reserved
F015Reserved
F016Reserved
F017Reserved
F018Reserved
F019Reserved
Factor
EN-US
Value range Process line selection
F01AWire forward / backward lengthUINT16OFF / 1 to
65,535 mm
F01BWire sense edge detectionUINT16OFF / 0.5 to
20.0 mm
F01CReserved
F01DSeam numberUINT160 to 65,5351
Bit 1Bit 0Description
00Process line 1 (default)
01Process line 2
10Process line 3
11Reserved
Value range for process line selection
1
10
Value Range for
TWIN Mode
Bit 1Bit 0Description
00TWIN Single mode
01TWIN Lead mode
10TWIN Trail mode
11Reserved
Value range for TWIN mode
25
Value Range for
Documentation
mode
Bit 0Description
0Seam number of power source (internal)
1Seam number of robot
Value range for documentation mode
Value range
Working mode
Value Range for
Command value
selection
Bit 4Bit 3Bit 2Bit 1Bit 0Description
00000Internal parameter selection
00001Special 2-step mode characteristics
00010Job mode
010002-step mode characteristics
Value range for operating mode
Bit 14Description
0Wirefeeder set value
1Welding current set value
Value range for set value
26
Output signalsFrom Power Source to Robot
Applicable to firmware V2.3.0 and higher
HEX
Ad-
ressSignalType
F100Status Flag Group 1
Bit 0 = 15Reserved
Range /
Unit
EN-US
Factor
F101
Status Flag Group 2
Bit 0Heartbeat PowersourceBoolean1
Hz
Bit 1Power source readyBoolean
Bit 2Arc stableBoolean
Bit 3Current flowBoolean
Bit 4Main current signalBoolean
Bit 5Torch collision protectionBoolean
Bit 6Reserved
Bit 7Reserved
Bit 8TouchedBoolean
Bit 9Torchbody connectedBoolean
Bit 10Command value out of
range
Bit 11Correction out of rangeBoolean
Bit 12Process activeBoolean
Bit 13RobotMotionReleaseBoolean
Boolean
F102
Bit 14Wire stick workpieceBoolean
Bit 15Reserved
Status Flag Group 3
Bit 0Welding Mode Bit 0BooleanSee section
Bit 1Welding Mode Bit 1Boolean
Bit 2Welding Mode Bit 2Boolean
Bit 3Welding Mode Bit 3Boolean
Bit 4Welding Mode Bit 4Boolean
Bit 5 = 7Reserved
Bit 8Parameter selection in-
ternally
Bit 9Characteristic number
valid
Bit 10 =
13
Bit 14Process image Bit 0Boolean
Bit 15Process image Bit 1Boolean
Reserved
Boolean
Boolean
Value
Range for
Welding
Process
and Pro-
cess Image
on page 30
27
HEX
Ad-
ressSignalType
F103Status Flag Group 4
Bit 0Penetration stabilizierBoolean
Bit 1Arclength stabilizierBoolean
Bit 2 = 15Reserved
F104Status Flag Group 5
Range /
Unit
Factor
Bit 0Sensor status 1 HighBooleanSee section
Bit 1Sensor status 2 HighBoolean
Bit 2Sensor status 3 HighBoolean
Bit 3 = 10Reserved
Bit 11Safety status Bit 0BooleanSee section
Bit 12Safety status Bit 1Boolean
Bit 13Reserved
Bit 14NotificationBoolean
Bit 15System not readyBoolean
F105Status Flag Group 6
Bit 0Limit SignalBoolean
Bit 1 = 7Reserved
Assign-
ment of
Sensor
Statuses 1–
3 on page
30
Value
range
Safety
status on
page 30
Bit 8Reserved
Bit 9TWIN synchronization
active
Bit 10Line supply statusBoolean
Bit 11 =
13
Bit 14WarningBoolean
Bit 15Reserved
F106Status Flag Group 7
Bit 0 = 15ReservedBoolean
Reserved
Boolean
28
HEX
Ad-
ressSignalType
F107Status Flag Group 8
Range /
Unit
Factor
EN-US
Bit 0ExtOutput1 <= OPT_In-
put1
Bit 1ExtOutput2 <= OPT_In-
put2
Bit 2ExtOutput3 <= OPT_In-
put3
Bit 3ExtOutput4 <= OPT_In-
put4
Bit 4ExtOutput5 <= OPT_In-
put5
Bit 5ExtOutput6 <= OPT_In-
put6
Bit 6ExtOutput7 <= OPT_In-
put7
Bit 7ExtOutput8 <= OPT_In-
put8
Bit 8 = 15ReservedBoolean
F108Main error numberUINT160 to 65,535
F109Warning numberUINT160 to 65,5351
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
F10AWelding voltage actual valueUINT160.0 to
327.67 volts
F10BWelding current actual valueUINT160.0 to
3276.7
amperes
F10CMotor current actual value M1SINT16-327.68 to
327.67
amperes
F10DMotor current actual value M2SINT16-327.68 to
327.67
amperes
F10EMotor current actual value M3SINT16-327.68 to
327.67
amperes
F10FReserved
F110Wire speed actual valueSINT16-327.68 to
327.67
m/min
F111Seam tracking actual valueUINT160 to 6.553510000
F112Real energy actual valueUINT160 to 6553.5
kilojoules
100
10
100
100
100
100
10
F113Wire positionSINT16-327.68 to
327.67 mm
F114Reserved
F115Reserved
100
29
HEX
Ad-
ressSignalType
Range /
Unit
F116Reserved
F117Reserved
F118Reserved
F119Reserved
F11AReserved
F11BReserved
F11CReserved
F11DReserved
Factor
Value Range for
Welding Process
and Process Image
Bit 4Bit 3Bit 2Bit 1Bit 0Description
00000Internal mode selection
00001MIG/MAG pulsed synergic
00010MIG/MAG standard synergic
00011MIG/MAG PMC
00100MIG/MAG LSC
00101MIG/MAG standard manual
00110Electrode
00111TIG
01000CMT
Value range for welding process
Bit 15Bit 14Bit 0-13Description
00-Standard image (Weldcom V2.0)
10-Retrofit image (Weldcom TPS series)
Value range for process image
Assignment of
Sensor Statuses
1–3
Value range
Safety status
30
Bit 2Bit 1Bit 0Description
001OPT/i WF R wire end
010OPT/i WF R DE wire drum
100OPT/i WF R DE ring sensor
Bit 1Bit 0Description
00Reserve
01Hold
TAG Table
Bit 1Bit 0Description
10Stop
11Not installed / active
EN-US
-To read the following TAGs, use the mode function 03dec (03hex) - see section 03
dec
(03
hex
) Read
Holding Register from page 42
-To edit the following TAGs, use the mode function 06dec (06hex) - see section 06
The MODBUS ADU is constructed by the client that initiates the MODBUS transaction.
The function tells the server which action is to be performed. The MODBUS application
protocol defines the format of a client-initiated request.
The function code field of a MODBUS data unit is coded in one byte. Valid codes are in
the range of 1 ... 255 decimal (the range 128-255 is reserved for exception responses).
When the server receives a message from a client, the function code field tells the server
which action to perform.
If several actions are to be performed, subfunction codes are added to some function
codes. When messages are sent to servers by a client, the data field in the message
contains additional information that the server uses to perform the action defined by the
function code. This can include elements such as discrete addresses, register addresses, the quantity to be handled, or the number of actual data bytes contained within
the field.
With certain types of request, there might not be a data field (length: zero). In this case,
the server does not require any additional information because the action is specified by
the function code alone.
If a MODBUS ADU is correctly received without any errors occurring in connection with
the requested MODBUS function, the requested data will be included in the data field
when a server responds to a client. If an error does occur in connection with the requested MODBUS function, the field will contain an exception code that the server application
can use to determine what action to perform next.
For instance, a client can read the ON/OFF statuses of a group of discrete inputs or outputs, or it can read/write the data contents of a group of registers.
When sending a response to the client, the server uses the function code field either to
indicate that the response is normal (free of errors) or that an error has occurred (this
kind of response is called an "exception response"). In the case of a normal response,
the server simply echoes the original function code.
Data CodingFor addresses and data elements, MODBUS uses a big-endian format. When a number
larger than a single byte is transmitted, this means that the most significant byte is sent
first.
Register SizeValue
16 bits, 1234
hex
12
is sent as the first byte and then 34
hex
hex
40
Application Data
Unit (ADU)
This section describes the encapsulation method used for a MODBUS request or response when it is transmitted over a MODBUS TCP network.
MPAP headerFunction codeData
Description of MPAP header:
Transaction Identifier
Used to allocate the transaction. The MODBUS server copies the Transaction Identifier of the request into the response.
Transaction Identifier
This is used for transaction pairing. The MODBUS server copies the transaction identifier from the request into the response.
Length:2 bytes
Description:For identifying a MODBUS request/response transaction
Client:Initialized by the client
Server:Copied back by the server from the request received
Protocol Identifier
This is used for multiplexing within the system. The MODBUS protocol is identified by
the value 0.
Length:2 bytes
EN-US
Description:0 = Modbus protocol
Client:Initialized by the client
Server:Copied back by the server from the request received
Length
This field is used to specify the number of bytes in the field to follow, including the unit
identifier, function code, and data field.
Length:2 bytes
Description:Number of bytes to follow
Client:Initialized by the client
Server:-
Unit Identifier
This field is used for routing within the system. It is usually used for communication
with a serially connected MODBUS- or MODBUS+ slave where communication takes
place via a gateway between an Ethernet network and a serial MODBUS line. The
field value is set in the request by the MODBUS client and must be replicated exactly
in the response from the server.
Length:1 byte
Description:For identifying a remote slave that is connected via a serial
line or other type of bus.
Client:Initialized by the client
All MODBUS/TCP ADUs are sent via TCP on registered port 502.
41
Modbus Functions
03
(03
dec
Holding Register
hex
) Read
This code is used to read the contents of a contiguous block of holding registers in a remote device. The request PDU determines the starting register address and the number
of registers.
The registers are addressed in the PDU starting at zero. This means registers numbered
1-16 will be addressed using 0-15.
The register data in the response message is packed as two bytes per register, with the
binary contents precisely aligned/justified within each byte. Within the individual registers, the first byte contains the high-order bits and the second byte the low-order bits.
Request
Function code1 byte03
Start address2 bytes0000
Number of registers2 bytes1 to 125 (7D
hex
to FFFF
hex
hex
hex
)
Response
Function code1 byte03
hex
Number of bytes2 bytes2 x N*
Register valueN* x 2 bytes-
N* = Number of registers
Errors
Error code1 byte83
hex
Exception code1 byte01 or 02 or 03 or 04
Example
Example of a read request for register F009 (job number).
The contents of register F009 (job number) are displayed in the form of the two-byte values 237
hex
or 567
dec
.
This function code is used to write a single holding register in a remote device. The request PDU specifies the address of the register to be written. Registers are addressed
starting at zero. This means that the register that has been numbered as 1 will be addressed using 0.
The normal response is an echo of the request, which is returned after the register contents are written.
This function code is used to write a block of contiguous registers in a remote device.
The requested written values are specified in the request data field. Data is packed as
two bytes per register. The normal response returns the function code, the starting address, and the number of registers written.
Request
Function code1 byte10
Starting address2 bytes0000
Number of registers2 bytes0001
hex
to FFFF
hex
or 0078
hex
hex
hex
Number of bytes1 byte2 x N*
Register valuesN* x 2 bytesValue
N* = number of registers to be written
Response
Function code1 byte10
Starting address2 bytes0000
Number of registers2 bytes1 to 123 (7B
hex
to FFFF
hex
hex
hex
)
Errors
Error code1 byte90
hex
Exception code1 byte01 or 02 or 03 or 04
Example
Example request for writing two registers (F00B
Quantity of Registers Hi00Quantity of Registers Hi00
Quantity of Registers Lo02Quantity of Registers Lo02
Byte Count04
Register Value Hi04
Register Value LoCE
44
Example
Example request for writing two registers (F00B
– F00C
hex
hex
).
RequestResponse
Field nameHexField nameHex
Register Value HiFF
Register Value LoC0
EN-US
45
23
dec
(17
hex
)
Read/Write Multiple Register
This function code performs a combination of one read operation and one write operation
in a single MODBUS transaction. The write operation is performed before the read operation.
Holding registers are addressed starting at zero. This means that holding registers 1-16
will be addressed in the PDU using 0-15.
The request PDU specifies:
-The starting address and number of holding registers to be read
-The starting address, number of holding registers, and data for the write operation.
The byte count field specifies the number of bytes to follow in the write data field.
The normal response contains the data from the group of registers read. The byte count
field specifies the number of bytes to follow in the read data field.
Request
Function code1 byte17
hex
Read starting address2 bytes0000
Number of registers to
2 bytes0001
read
Write starting address2 bytes0000
Number of registers to
2 bytes0001
write
Write number of bytes1 byte2 x N*
Write register valuesN* x 2 bytes
N* = number of registers to be written
Response
Function code1 byte17
hex
Number of bytes1 byte2 x N*
Write register valuesN* x 2 bytes
N* = number of registers to be read
Errors
to FFFF
hex
to approx. 0076
hex
to FFFF
hex
to approx. 0076
hex
hex
hex
hex
hex
46
Error code1 byte97
hex
Exception code1 byte01 or 02 or 03 or 04
Example
Example request for reading 2 registers and writing 2 registers.
Example
Example request for reading 2 registers and writing 2 registers.
RequestResponse
Field nameHexField nameHex
Length Lo11Length Lo7
Unit Identifier00Unit Identifier00
Function code17Function code17
Read Starting Address HiF1Byte Count2
Read Starting Address Lo0ARead Registers Value Hi04
Quantity to Read Hi00Read Registers Value Lo08
Quantity to Read Lo2Read Registers Value Hi0A
Write Starting Address HiF0Read Registers Value LoC8
Write Starting Address Lo0B
Quantity to Write Hi00
Quantity to Write Lo04
Write Byte Count2
Write Registers Value Hi04
Write Registers Value LoCE
Write Registers Value HiFF
EN-US
103
dec
(67
hex
)
Read Holding Register Float
Write Registers Value LoC0
Transaction Identifier Hi00
This function is used to read the contents of a contiguous block of registers in the TAG
tables contained in this document. The register uses floating-point format (32 bits). The
request PDU determines the starting register address and the number of registers.
The registers are addressed in the PDU starting at zero. This means registers numbered
1-16 will be addressed using 0-15.
The register data in the response message is packed as two bytes per register, with the
binary contents precisely aligned/justified within each byte. Within the individual registers, the first byte contains the high-order bits and the second byte the low-order bits.
The contents of register E064
values 3FC00000 or 1.5
dec
(gas pre-flow) are displayed in the form of the two-byte
hex
.
This function is used to edit registers in the TAG tables contained in this document. The
register uses floating-point format (32 bits). The request PDU specifies the address of
the register to be written. Registers are addressed starting at zero. This means that the
register that has been numbered as 1 will be addressed using 0.
The normal response is an echo of the request, which is returned after the register contents are written.
Requirement
Function code1 byte68
Register address2 bytesE000
Register value2 bytes0000
hex
to Exxx
hex
or FFFFFFFF
hex
hex
hex
48
Response
Function code1 byte68
hex
Register address2 bytesE000
Register value2 bytes0000
to Exxx
hex
or FFFFFFFF
hex
hex
hex
Error
Error code1 bytesE8
hex
Exception code1 byte01 or 02 or 03
Example
Example request for writing the value 3FC00000