/ Battery Charging Systems / Welding Technology / Solar Electronics
Implementation Guide
Gateway Modbus UDP extended
Operating Instructions
Roboter Interface
EN
42,0410,1536010-05022013
Dear Reader
Introduction
Thank you for choosing Fronius - and congratulations on your new, technically highgrade Fronius product! This instruction manual will help you get to know your new
machine. Read the manual carefully and you will soon be familiar with all the many
great features of your new Fronius product. This really is the best way to get the most
out of all the advantages that your machine has to offer.
Please also take special note of the safety rules - and observe them! In this way, you
will help to ensure more safety at your product location. And of course, if you treat your
product carefully, this definitely helps to prolong its enduring quality and reliability - things
which are both essential prerequisites for getting outstanding results.
Data encoding .......................................................................................................................................... 3
Application Data Unit (ADU) ..................................................................................................................... 4
General .................................................................................................................................................. 14
Server .................................................................................................................................................... 14
Modbus UDP - Process image for MIG/MAG standard synergic, MIG/MAG pulse synergic and CMT ....... 15
Process data from controller to power source (0xF000 - 0xF0FF)......................................................... 15
Process data from power source to controller (0xF100 - 0xF1FF)......................................................... 16
Modbus UDP - Process image for TIG........................................................................................................ 18
Process data from controller to power source (0xF000 - 0xF0FF)......................................................... 18
Process data from power source to controller (0xF100 – 0xF1FF) ........................................................ 19
Modbus UDP - Process image for CC/CV .................................................................................................. 21
Process data from controller to power source (0xF000 – 0xF0FF) ....................................................... 21
Process data from power source to controller (0xF100 – 0xF1FF) ........................................................ 22
Modbus UDP - Process image for MIG/MAG standard manual .................................................................. 23
Process data from controller to power source (0xF000 – 0xF0FF) ....................................................... 23
Process data from power source to controller (0xF100 – 0xF1FF) ........................................................ 24
Special data ................................................................................................................................................. 26
Real Values ............................................................................................................................................ 31
Special process: MIG/MAG manual standard ........................................................................................32
Special process: MIG/MAG manual pulse.............................................................................................. 32
Pilot Plasma ........................................................................................................................................... 33
TAG Table ................................................................................................................................................... 34
The MODBUS application data unit is built by the client that initiates a MODBUS transaction. The function indicates to the server what kind of action to perform. The MODBUS
application protocol establishes the format of a request initiated by a client.
The function code field of a MODBUS data unit is coded in one byte. Valid codes are in
the range of 1 ... 255 decimal (128 – 255 reserved for exception responses). When a
message is sent from a Client to a Server device the function code field tells the server
what kind of action to perform.
Sub-function codes are added to some function codes to define multiple actions.
The data field of messages sent from a client to server devices contains additional
information that the server uses to take the action defined by the function code. This can
include items like discrete and register addresses, the quantity of items to be handled,
and the count of actual data bytes in the field.
The data field may be nonexistent (of zero length) in certain kinds request, in this case
the server does not require any additional information. The function code alone specifies
the action.
If no error occurs related to the MODBUS function requested in a properly received
MODBUS ADU the data field of a response from a server to a client contains the data
requested. If an error related to the MODBUS function requested occurs, the field
contains an exception code that the server application can use to determine the next
action to be taken.
For example a client can read the ON / OFF states of a group of discrete outputs or
inputs or it can read/write the data contents of a group of registers.
When the server responds to the client, it uses the function code field to indicate either a
normal (error-free) response or that some kind of error occurred (called an exception
response). For a normal response, the server simply echoes the original function code.
Data encodingMODBUS uses a ‘big-Endian’ representation for addresses and data items. This means
that when a numerical quantity larger than a single byte is transmitted, the most significant byte is sent first.
Register sizeValue
16 Bit 0x1234the first byte sent is0x12 then 0x34
3
Application Data
Unit (ADU)
This section describes the encapsulation of a MODBUS request or response when it is
carried on a MODBUS UDP network.
MPAP HeaderFunction codeData
MPAP Header description:
Transactions Identifier
It is used for transaction pairing, the MODBUS server copies in the response the transaction identifier of the request.
Length:2 Byte
Description:Identification of a MODBUS Request / Response transaction
Client:Initialized by the client
Server:Recopied by the server from the received request
Protocol Identifier
It is used for intra-system multiplexing. The MODBUS protocol is identified by the value
0.
Length:2 Byte
Description:0 = Modbus protocol
Client:Initialized by the client
Server:Recopied by the server from the received request
Length
The length field is a byte count of the following field, including the Unit Identifier, Function
code and the data field.
Length:2 Byte
Description:Number of following bytes
Client:Initialized by the client
Server:-
Unit Identifier
This field is used for intra-system routing purpose. It is typically used to communicate to
a MODBUS or MODBUS+ serial line slave through a gateway between an Ethernet
network and a MODBUS serial line. This field is set by the MODBUS Client in the request and must be returned with the same value in the response by the server.
Length:1Byte
Description:Identification of a remote slave connected on a serial line or on other
buses
Client:Initialized by the client
Server:Recopied by the server from the received request
Important! All MODBUS/UDP ADU are sent via UDP on registered port 502.
4
Modbus Functions
03 (0x03) Read
Holding Registers
This function code is used to read the contents of a contiguous block of holding registers
in a remote device. In the Special Data area this contiguous block is limited from 1-4
registers. The request PDU specifies the starting register address and the number of
registers. In the PDU registers are addressed starting at zero. Therefore registers
numbered 1-16 are addressed as 0-15.
The register data in the response message are packed as two bytes per register, with
the binary contents right justified within each byte. For each register, the first byte contains the high order bits and the second contains the low order bits.
Request
Function code1 Byte0x03
Starting Address2 Bytes0x0000 to 0xFFFF
Quantity of Registers2 Bytes1 to 125 (0x7D)
Response
Function code1 Byte0x03
Byte count1 Byte2 x N*
Register valueN* x 2 Bytes-
N* = Quantity of Register
Error
Error code1 Byte0x83
Exception code1 Byte01 or 02 or 03 or 04
Example
Here is an example of a request to read registers 0xE011 (Gas preflow).
Request
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo06
Unit Identifier00
Function code03
Starting Address HiE0
Starting Address Lo11
No. of Registers Hi00
No. of Registers Lo01
Response
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo05
Unit Identifier00
Function code03
Byte Count02
Register value Hi (108)08
Register value Lo (108)98
The contents of register 0xE011 (Gas preflow) are shown as the two byte values of 08
98 hex, or 2200 decimal.
5
06 (0x06) Write
Single Registers
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. Therefore register numbered 1 is addressed as 0.
The normal response is an echo of the request, returned after the register contents have
been written.
Request
Function code1 Byte0x06
Register Address2 Bytes0x0000 to 0xFFFF
Register Value2 Bytes0x0000 or 0xFFFF
Response
Function code1 Byte0x06
Register Address2 Bytes0x0000 to 0xFFFF
Register Value2 Bytes0x0000 or 0xFFFF
Error
Error code1 Byte0x86
Exception code1 Byte01 or 02 or 03 or 04
Example
Here is an example of a request to write register 0xE011 (Gas preflow) with the value
0x898 (decimal 2200):
Request
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo06
Unit Identifier00
Function code06
Register Address HiE0
Register Address Lo11
Register Value Hi08
Register Value Lo98
Response
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo06
Unit Identifier00
Function code06
Register Address HiE0
Register Address Lo11
Register Value Hi08
Register Value Lo98
6
16 (0x10) Write
Multiple Registers
This function code is used to write a block of contiguous registers (1 to 20 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,
starting address and quantity of registers written.
Request
Function code1 Byte0x10
Starting Address2 Bytes0x0000 to 0xFFFF
Quantity of Registers2 Bytes0x0001 or 0x0078
Byte Count1 Byte2 x N*
Register ValuesN* x 2 BytesValue
N* = Quantity to Write
Response
Function code1 Byte0x10
Starting Address2 Bytes0x0000 to 0xFFFF
Quantity of Registers2 Bytes1 to 123 (0x7B)
Error
Error code1 Byte0x90
Exception code1 Byte01 or 02 or 03 or 04
Example
Here is an example of a request to write two registers (0xF00B – 0xF00C)
Request
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo??
Unit Identifier00
Function code10
Starting Address HiF0
Starting Address Lo0B
Quantity of Registers Hi00
Quantity of Registers Lo02
Response
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo06
Unit Identifier00
Function code10
Starting Address HiF0
Starting Address Lo0B
Quantity of Registers Hi00
Quantity of Registers Lo02
Byte Count04
Register Value Hi7F
Register Value LoFF
Register Value Hi7F
Register Value LoFF
7
23 (0x17) Read/
Write Multiple
registers
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.
Holding registers are addressed starting at zero. Therefore holding registers 1-16 are
addressed in the PDU as 0-15.
The request PDU specifies the starting address and number of holding registers to be
read as well as the starting address, number of holding registers, and the data to be
written. The byte count specifies the number of bytes to follow in the write data field.
The normal response contains the data from the group of registers that were read. The
byte count field specifies the quantity of bytes to follow in the read data field.
Request
Function code1 Byte0x17
Read Starting Address2 Bytes0x0000 to 0xFFFF
Quantity to Read2 Bytes0x0001 to approx.0x0076
Write Starting Address2 Bytes0x0000 to 0xFFFF
Quantity to Write2 Bytes0x0001 to approx. 0X0076
Write Byte Count1 Byte2 x N*
Write Registers ValueN* x 2 Bytes
N* = Quantity to Write
Response
Function code1 Byte0x17
Byte Count1 Byte2 x N'*
Read Registers valueN'* x 2 Bytes
N* = Quantity to Read
Error
Error code1 Byte0x97
Exception code1 Byte01 or 02 or 03 or 04
Example
Here is an example of a request to read six registers and to write three registers:
Request
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo11
Unit Identifier00
Function code17
Read Starting Address HiF1
Read Starting Address Lo00
Quantity to Read Hi00
Field Name(Hex)
Write Starting Address HiF0
Write Starting address Lo00
Quantity to Write Hi00
Quantity to Write Lo03
Write Byte Count06
Write Registers Value Hi01
Write Registers Value LoFA
Write Registers Value Hi02
Write Registers Value LoFB
Write Registers Value Hi03
Write Registers Value LoFC
Quantity to Read Lo06
8
Write Multiple
registers
(continued)
Response23 (0x17) Read/
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo0F
Unit Identifier00
Function code17
Byte Count0C
Read Registers value Hi00
Read Registers value LoFE
Field Name(Hex)
Read Registers value Hi0A
Read Registers value LoCD
Read Registers value Hi00
Read Registers value Lo01
Read Registers value Hi00
Read Registers value Lo03
Read Registers value Hi00
Read Registers value Lo0D
Read Registers value Hi00
Read Registers value LoFF
100 (0x64) Configure Streaming
Data
This function code is used to configure the data in the streaming frame. This frame will
be sent without a request from the client (or master).
The request PDU specifies the IP-address and the port number of the client, the streaming frequency and the addresses of the register. The port number 15000 and 15001
are reserved for Fronius Applications.
The normal response is an echo of the request.
Request
Function code1 Byte0x64
IP Address Hi Word2 Bytes0x0000 to 0xFFFF
IP Address Lo Word2 Bytes0x0000 to 0xFFFF
Port number2 Byte0x0000 to 0xFFFF
Frequency2 Byte0x0000 to 0xFFFF
Number of register1 Byte0x00 to 0xFF
Register AddressN* x 2 Bytes
N* = Quantity of Register
Response
Function code1 Byte0x64
IP Address Hi Word2 Bytes0x0000 to 0xFFFF
IP Address Lo Word2 Bytes0x0000 to 0xFFFF
Port number2 Byte0x0000 to 0xFFFF
Frequency2 Byte0x0000 to 0xFFFF
Number of register1 Byte0x00 to 0xFF
Register AddressN* x 2 Bytes
N* = Quantity of Register
Error
Error code1 Byte0xE5
Exception code1 Byte01 or 02 or 03 or 04
9
100 (0x64) Configure Streaming
Data
(continued)
Example
Here is an example of a request to configure the streaming data.
IP-Address:192.168.0.2
Port number:500
Frequency:20 Hz
Address 1:0xE070
Address 2:0xE071
Address 3:0xE068
Request
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo0F
Unit Identifier00
Function code64
IP Address Hi Word HiC0
IP Address Hi Word LoA8
IP Address Lo Word Hi00
IP Address Lo Word Lo02
Port number Hi01
Port number LoE4
Frequency Hi00
Frequency Lo14
Number of register03
Registers Value HiE0
Registers Value Lo70
Registers Value HiE0
Registers Value Lo71
Registers Value HiE0
Registers Value Lo68
Response
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo0F
Unit Identifier00
Function code64
IP Address Hi Word HiC0
IP Address Hi Word LoA8
IP Address Lo Word Hi00
IP Address Lo Word Lo02
Port number Hi01
Port number LoE4
Frequency Hi00
Frequency Lo14
Number of register03
Registers Value HiE0
Registers Value Lo70
Registers Value HiE0
Registers Value Lo71
Registers Value HiE0
Registers Value Lo68
101 (0x65) Action
Streaming Data
This function code is used to start and stop the streaming frame without a request from
the client (or master).
The request PDU specifies the start (0x01) or stop (0x00) of the streaming frame.
The normal response is an echo of the request.
Request
Function code1 Byte0x65
Action1 BytesBit 0…0 (Stop streaming)
Bit 0…1 (Start streaming)
10
101 (0x65) Action
Streaming Data
(continued)
Response
Function code1 Byte0x65
Action1 BytesBit 0…0 (Stop streaming)
Bit 0…1 (Start streaming)
Error
Error code1 Byte0xE5
Exception code1 Byte01 or 04 or 10
Example
Here is an example of a request to start the streaming data.
102 (0x66) Streaming Data
Request
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo03
Unit Identifier00
Function code65
Action streaming data01
Response
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo00
Length Hi00
Length Lo03
Unit Identifier00
Function code65
Action streaming data01
This function will be send from the server without a request from the client.
The Transaction Identifier will be incremented every cycle by the server. The Protocol
Identifier is the Protocol Identifier from the function 100 (0x64) Configure Streaming
Data.
The Unit Identifier is the Unit Identifier from the function 100 (0x64) Configure Streaming
Data.
Response
Function code1 Byte0x66
Frequency2 Byte0x0000 to 0xFFFF
Timestamp in ms2 Byte0x0000 to 0xFFFF
Number of registers1 Byte0x00 to 0xFF
Register address 12 Byte0x0000 to 0xFFFF
Register value 12 Byte0x0000 to 0xFFFF
Register address n2 Byte0x0000 to 0xFFFF
Register value n2 Byte0x0000 to 0xFFFF
11
102 (0x66) Streaming Data
(continued)
Example
Here is an example of a response of the streaming data.
Frequency:20 Hz
Timestamp:1613 ms
Nr. of register: 0x03
Address 1:0xE070
Address 2:0xE071
Address 3:0xE068
Response
Field Name(Hex)
Transaction Identifier Hi00
Transaction Identifier Lo01
Protocol Identifier Hi00
Protocol Identifier Lo01
Length Hi00
Length Lo13
Unit Identifier00
Function code66
Frequency Hi00
Frequency Lo14
Timestamp Hi06
Timestamp Lo4D
Number of register03
Field Name(Hex)
Register address 1 HiE0
Register address 1 Lo70
Register value 1 Hi01
Register value 1 LoFF
Register address 2 HiE0
Register address 2 Lo71
Register value 2 Hi02
Register value 2 LoFF
Register address 3 HiE0
Register address 3 Lo68
Register value 3 Hi03
Register value 3 LoFF
12
Exception codes
Code 0x01 Illegal Function
Code 0x02 Illegal Data
Address
Code 0x03 Illegal Data V alue
The function code received in the query is not an allowable action for the server (or
slave). This may be because the function code is only applicable to newer devices, and
was not implemented in the unit selected. It could also indicate that the server (or slave)
is in the wrong state to process a request of this type, for example because it is unconfigured and is being asked to return register values.
The data address received in the query is not an allowable address for the server (or
slave). More specifically, the
combination of reference number and transfer length is invalid. For a controller with 100
registers, a request with offset 96 and length 4 would succeed, a request with offset 96
and length 5 will generate exception 02.
A value contained in the query data field is not an allowable value for server (or slave).
This indicates a fault in the
structure of the remainder of a complex request, such as that the implied length is
incorrect. It specifically does NOT mean that a data item submitted for storage in a
register has a value outside the expectation of the application program, since the
MODBUS protocol is unaware of the significance of any particular value of any particular
register.
Code 0x04 Slave Device
Failure
Code 0x06 Slave Device
Busy
An unrecoverable error occurred while the server was attempting to perform the requested action.
What is the reason for this error:
-License Gateway Level 1 (4,061,115) not installed in the power source
-Modbus protocol not activated (UniveralBusSteuerung -> Config)
-Wrong Firewall IP address Modbus
The server (or slave) is engaged in processing a long-duration command. The client (or
master) should retransmit the message later when the server (or slave) is free.
13
Timeout Lifecycle
General
Client
Server
Modbus UDP is a connectionless transport protocol. It provides no control mechanism
when exchanging data between client and server. This results in a higher processing
speed than, for example, TCP. Therefore the connection must be controlled by the client
and the server.
In the process image 0xF000 (Bit 0-7) Control Flag Group 1 contents the signal Timeout
Lifecycle.
If the value is zero, there is no control of the communication active.
A value between 1-255 means a timeout from 10ms - 2550ms.
Every request of a Modbus function 23 (0x17) reset the lifecycle timer in the server.
After a overrun of this lifecycle timer the power source stops immediately.
If the lifecycle time run over, in the process image 0xF100 Bit 1 Status Flag Group 1 the
signal Modbus Timeout will be set.
After a restart of the Modbus communication this flag is set as long, till the signal Source
Error Reset will be set.
14
Modbus UDP - Process image for MIG/MAG standard
synergic, MIG/MAG pulse synergic and CMT
Process data
from controller to
power source
(0xF000 - 0xF0FF)
Address DescriptionUnitTypeFactor R / W
0xF000Control Flag Group 1
Bit 0 - 7 Timeout LifecyclemsByte10r/w
Bit 8 - 15 Reserved----
0xF001Control Flag Group 2
Bit 0Welding start-Boolean-r/w
Bit 1Robot ready-Boolean-r/w
Bit 2Source error reset-Boolean-r/w
Bit 3Gas test-Boolean-r/w
Bit 4Wire inching-Boolean-r/w
Bit 5Wire retract-Boolean-r/w
Bit 6Torch blow out-Boolean-r/w
Bit 7Welding simulation-Boolean-r/w
Bit 8Touch sensing-Boolean-r/w
Bit 9Master selectioin Twin-Boolean-r/w
Bit 10SFI disable-Boolean-r/w
Bit 11SynchroPuls disable-Boolean-r/w
Bit 12Pulse/Dynamik correction disable-Boolean-r/w
Bit 13Burn back correction disable-Boolean-r/w
Bit 14Power full range-Boolean-r/w
Bit 15Reserved-Boolean--
Process data
from controller to
power source
(0xF000 - 0xF0FF)
(continued)
Address DescriptionUnitTypeFactor R / W
0xF00FReserved----
0xF010External wirefeeder
Wirefeed speed actual valuem/minWord-r/w
0xF011External wirefeeder
Main error-Byte-r/w
0xF012External wirefeeder
Sub error-Byte-r/w
0xF013External wirefeeder
Bit 0External wirefeeder enable-Boolean-r/w
Bit 1 - 15 Reserved----
Process data from
power source to
controller (0xF100
- 0xF1FF)
Address DescriptionUnitTypeFactor R / W
0xF100Status Flag Group 1
Bit 0Modbus timeoutmsBoolean-r
Bit 2 - 15 Reserved-Boolean--
0xF101Status Flag Group 2
Bit 0Communication ready-Boolean-r
Bit 1Power source ready-Boolean-r
Bit 2Arc stable-Boolean-r
Bit 3Process active-Boolean-r
Bit 4Main current signal-Boolean-r
Bit 5Torch collision protection-Boolean-r
Bit 6Wire stick control-Boolean-r
Bit 7Wire available-Boolean-r
Bit 8Shortcircuit timeout-Boolean-r
Bit 9Power out of range-Boolean-r
Bit 10Robot access-Boolean-r
Bit 11Data documentation ready-Boolean-r
Bit 12Limit signal-Boolean-r
Bit 13-15 Reserved-Boolean-r
0xF102Status Flag Group 3
Bit 0 - 15 Reserved----
0xF103Status Flag Group 4
Bit 0 - 15 Reserved----
0xF104Status Flag Group 5
Bit 0 - 15 Reserved----
0xF105Status Flag Group 6
Bit 0 - 15 Reserved----
0xF106Status Flag Group 7
Bit 0 - 15 Reserved----
0xF107Device SubError-Byte-r
0xF108Main error number-Word-r
0xF109Reserved----
0xF10AWelding voltage actual valueVWord-r
0xF10BWelding current actual valueAWord-r
0xF10CMotor current actual valueAWord-r
0xF10DReserved----
0xF10EReserved----
16
Process data from
power source to
controller (0xF100
- 0xF1FF)
(continued)
Address DescriptionUnitTypeFactor R / W
0xF10FReserved----
0xF110Wire speed actual valuem/minWord--
0xF111External wirefeeder
Wirefeed speed command valuem/minWord-r
0xF112External wirefeeder
Wirefeed speed ramp value15m/min/s Wordr
17
Modbus UDP - Process image for TIG
Process data
from controller to
power source
(0xF000 - 0xF0FF)
Address DescriptionUnitTypeFactor R / W
0xF000Control Flag Group 1
Bit 0 - 7 Timeout LifecyclemsByte10Bit 8 - 15 Reserved----
Bit 1DC- / DC+-Boolean-Bit 2Cap shaping-Boolean-Bit 3Pulse disable-Boolean-Bit 4Pulse range Bit 0-Boolean-Bit 5Pulse range Bit 1-Boolean-Bit 6Pulse range Bit 2-Boolean-Bit 7Reserved----
0xF00BMain currentAWord--
18
Process data
from controller to
power source
(0xF000 - 0xF0FF)
(continued)
Address DescriptionUnitTypeFactor R / W
0xF00CExternal parameter-Word--
0xF00DBase current%Byte--
0xF00EDuty cycle%Byte--
0xF00FWire speed cold wirem/min10 Bit--
0xF010External wirefeeder
Wirefeed speed actual valuem/minWord--
0xF011External wirefeeder
Main error-Byte--
0xF012External wirefeeder
Sub error-Byte--
0xF013External wirefeeder
Bit 0External wirefeeder enable-Boolean-Bit 1-15 Reserved----
Pulse range selectionBit 6Bit 5Bit 4
Set pulse range on power source000
Pulse setting range deactivated001
0,2 - 2 Hz010
2 - 20 Hz011
20 - 200 Hz100
200 - 2000 Hz101
Process data
from power
source to controller (0xF100 –
0xF1FF)
Address DescriptionUnitTypeFactor R / W
0xF100Status Flag Group 1
Bit 0Modbus timeoutmsBoolean-Bit 2-15 Reserved-Boolean--
0xF101Status Flag Group 2
Bit 0Communication ready-Boolean-Bit 1Power source ready-Boolean-Bit 2Arc stable-Boolean-Bit 3Process active-Boolean-Bit 4Main current signal-Boolean-Bit 5Torch collision protection-Boolean-Bit 6Reserved---Bit 7Wire available (cold wire)-Boolean-Bit 8Reserved---Bit 9Reserved---Bit 10Reserved---Bit 11Reserved---Bit 12Reserved---Bit 13High frequency active-Boolean-Bit 14Pulse high-Boolean-Bit 15Reserved----
0xF102Status Flag Group 3
Bit 0 - 15 Reserved-Boolean--
0xF103Status Flag Group 4
Bit 0 - 15 Reserved----
0xF104Status Flag Group 5
Bit 0 - 15 Reserved----
0xF105Status Flag Group 6
Bit 0 - 15 Reserved----
19
Process data
from power
source to controller (0xF100 –
0xF1FF)
(continued)
Address DescriptionUnitTypeFactor R / W
0xF106Status Flag Group 7
Bit 0 - 15 Reserved----
0xF107Device SubError-Byte-r
0xF108Main error number-Word--
0xF109Reserved----
0xF10AWelding voltageVWord--
0xF10BWelding currentAWord--
0xF10CMotor current (cold wire)AWord--
0xF10DReserved
0xF10EArc length actual value (AVC)VByte--
0xF10FReserved----
0xF110Wire speed (cold wire)m/minWord--
0xF111External wirefeeder
Wirefeed speed command valuem/minWord--
0xF112External wirefeeder
Wirefeed speed ramp value15m/min/s Word--
20
Modbus UDP - Process image for CC/CV
Process data
from controller to
power source
(0xF000 –
0xF0FF)
Address DescriptionUnitTypeFactor R / W
0xF000Control Flag Group 1
Bit 0 - 7 Timeout LifecyclemsByte10Bit 8 - 15 Reserved----
E06DCurrent at end of ground-phaseTRUEFALSEAInteger0,1
E06EVoltage at end of ground-phaseTRUEFALSEVInteger0,01
E06FReal value arc lengthTRUEFALSEVInteger0,01
E070Real value voltageTRUEFALSEVInteger0,01
E071Real value currentTRUEFALSEAInteger0,1
E079Current mean value of neg. wave TRUEFALSEAInteger0,1
E07AVoltage mean value of neg. wave TRUEFALSEVInteger0,01
E0BFReal value gasTRUEFALSEmlInteger1
Address DescriptionReadWriteUnitType Factor
E072Min. feeder-valueTRUEFALSE m/minInteger0,01
E073Max. feeder-valueTRUEFALSE m/minInteger0,01
E074Min. voltage command valueTRUEFALSEVInteger0,01
31
Limits
(continued)
Address DescriptionReadWriteUnitType Factor
E075Max. voltage command valueTRUEFALSEVInteger0,01
E076Min. current command valueTRUEFALSEAInteger0,1
E077Max. current command valueTRUEFALSEAInteger0,1
E0A9Min. Eld valueTRUEFALSEmmWord0,1
E0AAMax. Eld-valueTRUEFALSEmmWord0,1
Special process:
MIG/MAG manual
standard
Special process:
MIG/MAG manual
pulse
Address DescriptionReadWriteUnitType Factor
E07BFeeder creep speedTRUETRUEm/minInteger0,01
E07CIgnition currentTRUETRUEAInteger0,1
E07DIgnition current timeTRUETRUEmsWord0,01
E07EWirefeed speedTRUETRUEm/minInteger0,01
E07FBackground currentTRUETRUEAInteger0,1
E080Voltage command valueTRUETRUEVInteger0,01
E081Characteristic slopeTRUETRUEμOhmWord1
E082Special dynamicTRUETRUE-Word1
E083Current decreaseTRUETRUE-Word1
E084Current riseTRUETRUE-Word1
E085Burn back timeTRUETRUEsWord0,01
E086Burn back pulse timeTRUETRUEmsWord0,01
E087Burn back pulsing currentTRUETRUEAInteger0,1
Address DescriptionReadWriteUnitType Factor
E088Feeder creep speedTRUETRUEm/minInteger0,01
E089Ignition currentTRUETRUEAInteger0,1
E08AIgnition current timeTRUETRUEmsWord0,01
E08BBase currentTRUETRUEAInteger0,1
E08CCurrent riseTRUETRUEA/msWord0,1
E08DCurrent rise tauTRUETRUEmsWord0,01
E08EPulsing currentTRUETRUEAInteger0,1
E08FPulsing current timeTRUETRUEmsWord0,01
E090Current decreaseTRUETRUEA/msWord0,1
E091Current drop tauTRUETRUEmsWord0,01
E092Droplet detachment currentTRUETRUEAInteger0,1
E093Droplet detachment timeTRUETRUEmsWord0,01
E094Pulsing frequencyTRUETRUEHzWord0,1
E095Wirefeed speedTRUETRUEm/minInteger0,01
E096Voltage command valueTRUETRUEVInteger0,01
E097Fact I_b_control_piTRUETRUE%Word0,01
E098Fact I_p1_control_piTRUETRUE%Word0,01
E099Fact f_control_pTRUETRUE%Word0,01
E09AFact I_b_correctionTRUETRUE%Word0,01
E09BFact I_p1_correctionTRUETRUE%Word0,01
E09CFact f_correctionTRUETRUE%Word0,01
32
Special process:
MIG/MAG manual
pulse
(continued)
Address DescriptionReadWriteUnitType Factor
E09DCurrent rise scTRUETRUEA/msWord0,1
E09EBurn back timeTRUETRUEsWord0,01
E0A1Regulator outputTRUEFALSE-Integer1
Pilot Plasma
Address DescriptionReadWriteUnitType Factor
E0A3Gas preflow [GPr]TRUETRUEsWord0,001
E0A4Gas postflow [GPo]TRUETRUEsWord0,001
E0A5Gas command value [GAS]TRUETRUElInteger0,01
E0A6Gas factor [Cor]TRUETRUE-Word0,1
E0A7Pre-/Post Gas command valueTRUETRUElInteger0,01
[GPA]
E0A8Pilot currentTRUETRUEAInteger0,1
33
TAG Table
Adress DescriptionReadWriteGroupUnitTypeFactor
E000Main errorTrueFalseGenericWord1
E001Sub errorTrueFalseGenericWord1
E002Status FlagTrueFalseGenericWord1
Bit 0maincurrent
Bit 1cooler
Bit 2fan1
Bit 3gas1
Bit 4coolersensor
Bit 5processrun
Bit 6processact
Bit 7wf started
Bit 8weldstart
Bit 9inching
Bit 10 gastest
Bit 11 keylock
Bit 12 UST-fan
Bit 13 currentflow
Bit 14 started up
Bit 15 hold
E003Status FlagTrueFalseGenericWord1
Bit 01=DC+ enable
Bit 11=Needle OVL
Bit 21=3 phase machine
Bit 31=Magic Wave
Bit 41=TIG
Bit 51=I-RV-display
Bit 61=U-RV-display
Bit 71=Fd-RV-display
Bit 81=enable jobchange
Bit 91=par.-select.-int.
Bit 10 1=Touchsensing active
E004ReservedTrueFalseGenericWord1
E005JobnumberTrueTrueGenericWord1
E007Push pull unit [PPU]TrueTrueGenericWord1
E008Opterating modeTrueTrueGenericWord1
0MIG Standard
1MIG Pulse
2Stick
3TIG
4Job mode
5Manual mode
6CC/CV
7CMT special mode
8Unused
9Manual standard
10Manual puls
255Invalid