Communication Setup for Modbus TCP in Do-more Technical Training

undefined
Do-more Technical Training
Communications
(Modbus TCP)
Communications – Modbus TCP
 
Modbus TCP Server (Slave)
(1) Do-more built-in Ethernet port
(2) Do-more w/ECOM100
Modbus TCP Client (Master)
(3) Do-more built-in Ethernet port
(4) Do-more w/ECOM100
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
 
(
S
l
a
v
e
)
(
1
)
 
D
o
-
m
o
r
e
 
b
u
i
l
t
-
i
n
 
E
t
h
e
r
n
e
t
 
p
o
r
t
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
 
D
e
v
i
c
e
 
e
x
i
s
t
s
 
&
 
i
s
 
e
n
a
b
l
e
d
 
b
y
 
d
e
f
a
u
l
t
 
(
s
e
e
 
C
P
U
C
o
n
f
i
g
u
r
a
t
i
o
n
)
U
s
e
 
C
P
U
 
C
o
n
f
i
g
u
r
a
t
i
o
n
 
 
M
o
d
b
u
s
/
T
C
P
 
S
e
r
v
e
r
 
C
o
n
f
i
g
u
r
a
t
i
o
n
 
t
o
 
c
h
a
n
g
e
p
a
r
a
m
e
t
e
r
s
 
a
s
 
d
e
s
i
r
e
d
M
a
x
i
m
u
m
 
C
o
n
c
u
r
r
e
n
t
 
S
e
s
s
i
o
n
s
:
 
1
-
1
6
 
(
d
e
f
a
u
l
t
 
4
)
U
p
 
t
o
 
1
6
 
C
l
i
e
n
t
s
 
(
M
a
s
t
e
r
s
)
 
c
a
n
 
t
a
l
k
 
t
o
 
t
h
e
 
D
o
-
m
o
r
e
.
T
h
e
 
1
7
t
h
 
o
n
e
 
w
i
l
l
 
b
e
 
u
n
a
b
l
e
 
t
o
 
c
o
n
n
e
c
t
C
l
i
e
n
t
 
I
n
a
c
t
i
v
i
t
y
 
T
i
m
e
o
u
t
:
 
1
-
6
5
,
5
3
5
 
s
e
c
o
n
d
s
I
f
 
D
o
-
m
o
r
e
 
h
a
s
n
t
 
h
e
a
r
d
 
f
r
o
m
 
o
n
e
 
o
f
 
h
i
s
 
C
l
i
e
n
t
s
(
M
a
s
t
e
r
s
)
 
i
n
 
t
h
i
s
 
t
i
m
e
 
p
e
r
i
o
d
,
 
D
o
-
m
o
r
e
 
w
i
l
l
 
d
o
 
a
 
T
C
P
d
i
s
c
o
n
n
e
c
t
T
C
P
 
P
o
r
t
 
N
u
m
b
e
r
:
 
d
e
f
a
u
l
t
 
5
0
2
S
e
r
v
e
s
 
u
p
 
M
-
m
e
m
o
r
y
 
t
o
 
t
h
e
 
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
M
o
d
b
u
s
 
I
n
p
u
t
s
 
0
-
1
0
2
3
 
 
M
I
0
-
1
0
2
3
*
M
o
d
b
u
s
 
C
o
i
l
s
 
0
-
1
0
2
3
 
 
M
C
0
-
1
0
2
3
*
M
o
d
b
u
s
 
I
n
p
u
t
 
R
e
g
i
s
t
e
r
s
 
0
-
2
0
4
7
 
 
M
I
R
0
-
2
0
4
7
*
M
o
d
b
u
s
 
H
o
l
d
i
n
g
 
R
e
g
i
s
t
e
r
s
 
0
-
2
0
4
7
 
 
M
H
R
0
-
2
0
4
7
*
*
R
a
n
g
e
 
i
s
 
e
x
p
a
n
d
a
b
l
e
 
v
i
a
 
M
e
m
o
r
y
 
C
o
n
f
i
g
u
r
a
t
i
o
n
Do-more SLAVE
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
 
(
M
a
s
t
e
r
)
(
3
)
 
D
o
-
m
o
r
e
 
b
u
i
l
t
-
i
n
 
E
t
h
e
r
n
e
t
 
p
o
r
t
O
n
e
 
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
 
D
e
v
i
c
e
 
(
@
I
n
t
M
o
d
T
C
P
C
l
i
e
n
t
)
 
e
x
i
s
t
s
 
b
y
d
e
f
a
u
l
t
U
s
e
 
D
e
v
i
c
e
 
C
o
n
f
i
g
u
r
a
t
i
o
n
 
t
o
 
c
h
a
n
g
e
p
a
r
a
m
e
t
e
r
s
 
a
s
 
d
e
s
i
r
e
d
T
i
m
e
o
u
t
:
 
m
i
l
l
i
s
e
c
o
n
d
s
 
(
m
s
)
 
t
o
 
w
a
i
t
f
o
r
 
S
e
r
v
e
r
 
(
S
l
a
v
e
)
 
t
o
 
r
e
s
p
o
n
d
R
e
t
r
i
e
s
:
 
h
o
w
 
m
a
n
y
 
t
i
m
e
s
 
t
o
 
r
e
t
r
y
 
c
o
m
m
I
n
a
c
t
i
v
i
t
y
 
T
i
m
e
o
u
t
:
 
s
e
c
o
n
d
s
 
t
o
 
k
e
e
p
T
C
P
 
c
o
n
n
e
c
t
i
o
n
 
a
l
i
v
e
 
d
u
e
 
t
o
 
i
n
a
c
t
i
v
i
t
y
(
n
o
 
M
R
X
/
M
W
X
 
b
e
i
n
g
 
e
x
e
c
u
t
e
d
)
 
b
e
f
o
r
e
d
o
i
n
g
 
a
 
T
C
P
 
d
i
s
c
o
n
n
e
c
t
 
f
r
o
m
 
t
h
e
 
S
e
r
v
e
r
(
S
l
a
v
e
)
U
s
e
 
M
R
X
 
(
R
e
a
d
)
 
&
 
M
W
X
 
(
W
r
i
t
e
)
i
n
s
t
r
u
c
t
i
o
n
s
M
u
l
t
i
p
l
e
 
M
R
X
/
M
W
X
 
i
n
s
t
r
u
c
t
i
o
n
s
 
c
a
n
 
b
e
 
u
s
e
d
 
t
o
 
s
a
m
e
 
S
e
r
v
e
r
 
(
S
l
a
v
e
)
I
f
 
>
1
 
S
e
r
v
e
r
 
(
S
l
a
v
e
)
,
 
c
r
e
a
t
e
 
a
 
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
 
D
e
v
i
c
e
 
f
o
r
 
e
a
c
h
o
n
e
 
(
e
x
p
l
a
i
n
e
d
 
i
n
 
a
 
f
e
w
 
m
i
n
u
t
e
s
)
Do-more MASTER
Communications – Modbus TCP
 
 
 
 
 
 
 
D
L
 
&
 
E
C
O
M
1
0
0
 
H
i
s
t
o
r
y
 
L
e
s
s
o
n
R
e
m
e
m
b
e
r
 
t
h
e
 
N
e
w
 
A
d
v
a
n
c
e
m
e
n
t
s
?
:
E
C
O
M
1
0
0
 
i
n
v
e
n
t
e
d
 
t
h
a
t
 
r
u
n
s
 
a
t
1
0
0
M
b
p
s
 
&
 
s
u
p
p
o
r
t
s
 
M
o
d
b
u
s
 
T
C
P
(
C
l
i
e
n
t
 
&
 
S
e
r
v
e
r
)
 
r
e
q
u
i
r
i
n
g
 
T
C
P
/
I
P
t
o
 
b
e
 
s
u
p
p
o
r
t
e
d
:
I
P
 
a
d
d
r
e
s
s
,
 
s
u
b
n
e
t
 
m
a
s
k
 
&
 
g
a
t
e
w
a
y
a
d
d
r
e
s
s
A
l
s
o
,
 
p
e
e
r
-
t
o
-
p
e
e
r
 
m
u
s
t
 
b
e
 
u
s
e
d
 
t
o
s
e
l
e
c
t
 
M
o
d
b
u
s
 
T
C
P
N
e
w
 
P
r
o
b
l
e
m
:
 
H
o
w
 
t
o
 
f
u
r
t
h
e
r
 
s
e
l
e
c
t
 
M
o
d
b
u
s
F
u
n
c
t
i
o
n
 
C
o
d
e
 
&
 
r
e
g
i
s
t
e
r
 
a
d
d
r
e
s
s
?
DL-PLC w/ECOM100 MASTER
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
 
 
D
L
 
&
 
E
C
O
M
1
0
0
 
H
i
s
t
o
r
y
 
L
e
s
s
o
n
O
r
i
g
i
n
a
l
 
R
e
q
u
i
r
e
m
e
n
t
s
:
M
o
d
u
l
e
 
I
D
 
(
a
 
n
u
m
b
e
r
 
f
r
o
m
 
0
-
9
0
)
 
i
s
 
t
h
e
 
o
n
l
y
 
m
e
a
n
s
t
o
 
a
d
d
r
e
s
s
 
t
h
e
 
c
o
m
m
u
n
i
c
a
t
i
o
n
 
p
a
r
t
n
e
r
S
o
l
v
e
d
 
w
i
t
h
 
p
e
e
r
-
t
o
-
p
e
e
r
 
t
a
b
l
e
N
e
w
 
R
e
q
u
i
r
e
m
e
n
t
s
:
H
o
w
 
t
o
 
s
e
l
e
c
t
 
M
o
d
b
u
s
 
T
C
P
?
S
O
L
U
T
I
O
N
:
 
A
 
2
n
d
 
p
e
e
r
-
t
o
-
p
e
e
r
 
s
e
l
e
c
t
i
o
n
H
o
w
 
t
o
 
s
e
l
e
c
t
 
M
o
d
b
u
s
 
F
C
?
H
o
w
 
t
o
 
s
e
l
e
c
t
 
r
e
g
i
s
t
e
r
 
a
d
d
r
e
s
s
?
T
h
e
s
e
 
l
a
s
t
 
t
w
o
 
a
r
e
 
s
o
l
v
e
d
 
w
i
t
h
 
m
a
p
p
i
n
g
Converts 
Module ID
(“RX/WX Device Number”) to
an IP Address
Not only converts 
Module ID
(“RX/WX Device Number”)
to an IP Address but also
selects Modbus TCP protocol
DL-PLC w/ECOM100 MASTER
Communications – Modbus TCP
 
 
 
 
D
L
 
&
 
E
C
O
M
1
0
0
 
H
i
s
t
o
r
y
 
L
e
s
s
o
n
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
 
M
a
p
p
i
n
g
:
U
s
e
s
 
R
X
/
W
X
 
o
p
e
r
a
n
d
 
t
o
 
s
e
l
e
c
t
 
b
o
t
h
 
t
h
e
 
M
o
d
b
u
s
 
F
C
 
&
t
h
e
 
r
e
g
i
s
t
e
r
 
a
d
d
r
e
s
s
DL-PLC w/ECOM100 MASTER
Communications –
Modbus TCP
 
 
 
 
 
 
D
L
 
&
 
E
C
O
M
1
0
0
 
H
i
s
t
o
r
y
L
e
s
s
o
n
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
M
a
p
p
i
n
g
:
R
e
s
p
o
n
d
s
 
t
o
 
t
h
e
 
M
o
d
b
u
s
 
F
C
s
a
s
 
s
h
o
w
n
N
o
t
i
c
e
,
 
h
o
w
e
v
e
r
,
 
F
C
0
3
 
&
F
C
0
4
 
b
o
t
h
 
s
e
r
v
e
 
u
p
 
D
L
-
P
L
C
s
V
-
m
e
m
o
r
y
T
h
i
s
 
i
s
 
n
o
t
 
u
s
u
a
l
l
y
 
a
 
p
r
o
b
l
e
m
f
o
r
 
3
r
d
-
p
a
r
t
y
 
M
o
d
b
u
s
 
T
C
P
C
l
i
e
n
t
s
,
 
b
u
t
DL-PLC w/ECOM100 SLAVE
Communications – Modbus TCP
 
 
 
 
 
 
D
L
 
&
 
E
C
O
M
1
0
0
 
H
i
s
t
o
r
y
 
L
e
s
s
o
n
N
e
w
 
P
r
o
b
l
e
m
:
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
 
m
a
p
p
i
n
g
 
d
o
e
s
n
t
 
a
l
l
o
w
 
t
h
e
a
b
i
l
i
t
y
 
t
o
 
a
d
d
r
e
s
s
 
M
o
d
b
u
s
 
I
n
p
u
t
 
R
e
g
i
s
t
e
r
s
!
S
O
L
U
T
I
O
N
:
 
U
s
e
 
a
n
 
o
d
d
 
l
e
n
g
t
h
 
d
e
s
i
g
n
a
t
i
o
n
 
t
o
c
h
a
n
g
e
 
f
r
o
m
 
u
s
i
n
g
 
H
o
l
d
i
n
g
 
R
e
g
i
s
t
e
r
s
 
t
o
 
u
s
i
n
g
 
I
n
p
u
t
R
e
g
i
s
t
e
r
s
W
h
y
 
t
h
i
s
 
w
o
r
k
s
:
 
t
h
e
 
l
e
n
g
t
h
 
p
a
r
a
m
e
t
e
r
 
i
s
 
a
l
w
a
y
s
 
a
n
 
e
v
e
n
n
u
m
b
e
r
 
b
e
c
a
u
s
e
 
i
t
 
d
e
s
i
g
n
a
t
e
s
 
b
y
t
e
s
 
a
n
d
 
a
l
l
 
M
o
d
b
u
s
r
e
g
i
s
t
e
r
s
 
a
r
e
 
w
o
r
d
s
 
(
2
 
b
y
t
e
s
)
 
IR?
IR?
DL-PLC w/ECOM100 MASTER
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
 
 
 
D
L
 
&
 
E
C
O
M
1
0
0
 
H
i
s
t
o
r
y
 
L
e
s
s
o
n
A
l
l
 
p
r
e
v
i
o
u
s
 
m
a
p
s
 
w
e
r
e
 
f
o
r
 
D
L
 
P
L
C
s
 
u
s
i
n
g
 
E
C
O
M
1
0
0
s
C
a
n
 
E
C
O
M
1
0
0
 
b
e
 
u
s
e
d
 
t
o
 
d
o
 
M
o
d
b
u
s
 
T
C
P
 
w
h
i
l
e
 
i
n
 
a
 
D
o
-
m
o
r
e
 
P
L
C
 
b
a
s
e
?
.
.
.
 
Y
e
s
 
h
o
w
e
v
e
r
T
o
 
a
n
 
E
C
O
M
1
0
0
 
a
s
 
a
n
y
 
k
i
n
d
 
o
f
 
s
e
r
v
e
r
 
i
n
 
a
 
D
o
-
m
o
r
e
 
P
L
C
,
 
o
n
l
y
D
L
-
m
e
m
o
r
y
 
i
s
 
a
v
a
i
l
a
b
l
e
S
o
 
t
h
e
 
s
e
r
v
e
r
 
m
a
p
p
i
n
g
 
c
h
a
r
t
 
i
s
 
f
u
r
t
h
e
r
 
r
e
s
t
r
i
c
t
e
d
A
s
 
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
:
F
C
0
1
 
R
e
a
d
 
C
o
i
l
s
,
 
F
C
0
5
 
F
o
r
c
e
 
S
i
n
g
l
e
 
C
o
i
l
 
&
 
F
C
1
5
 
F
o
r
c
e
 
M
u
l
t
i
p
l
e
C
o
i
l
s
 
o
n
l
y
 
a
c
c
e
s
s
 
D
L
Y
0
-
1
7
7
7
 
&
 
D
L
C
0
-
3
7
7
7
F
C
0
2
 
R
e
a
d
 
I
n
p
u
t
s
 
o
n
l
y
 
a
c
c
e
s
s
e
s
 
D
L
X
0
-
1
7
7
7
F
C
0
3
 
R
e
a
d
 
H
o
l
d
i
n
g
 
R
e
g
i
s
t
e
r
s
,
 
F
C
0
6
 
P
r
e
s
e
t
 
S
i
n
g
l
e
 
R
e
g
i
s
t
e
r
 
&
F
C
1
6
 
P
r
e
s
e
t
 
M
u
l
t
i
p
l
e
 
R
e
g
i
s
t
e
r
s
 
o
n
l
y
 
a
c
c
e
s
s
 
D
L
V
0
-
7
7
7
7
F
C
0
4
 
R
e
a
d
 
I
n
p
u
t
 
R
e
g
i
s
t
e
r
s
 
a
l
s
o
 
o
n
l
y
 
a
c
c
e
s
s
e
s
 
D
L
V
0
-
7
7
7
7
A
s
 
M
o
d
b
u
s
 
T
C
P
 
C
l
i
e
n
t
:
M
u
s
t
 
u
s
e
 
D
L
R
X
/
D
L
W
X
 
(
n
o
t
 
M
R
X
/
M
W
X
!
)
 
w
i
t
h
p
r
o
p
e
r
 
p
a
r
a
m
e
t
e
r
DL-PLC w/ECOM100 SLAVE/MASTER
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
 
(
S
l
a
v
e
)
(
2
)
 
D
o
-
m
o
r
e
 
w
i
t
h
 
E
C
O
M
1
0
0
D
o
-
m
o
r
e
s
 
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
 
i
s
 
n
o
t
 
u
t
i
l
i
z
e
d
A
 
M
o
d
b
u
s
 
T
C
P
 
S
e
r
v
e
r
 
e
x
i
s
t
s
 
&
 
i
s
 
e
n
a
b
l
e
d
 
i
n
 
t
h
e
 
E
C
O
M
1
0
0
M
o
d
b
u
s
 
I
/
O
 
m
a
p
p
i
n
g
 
f
r
o
m
 
E
C
O
M
1
0
0
 
w
i
l
l
 
g
o
 
t
o
 
D
L
-
m
e
m
o
r
y
M
o
d
b
u
s
 
I
n
p
u
t
s
:
2
0
4
9
-
3
0
7
2
 
 
D
L
Y
0
-
1
7
7
7
*
3
0
7
3
-
5
1
2
0
 
 
D
L
C
0
-
3
7
7
7
*
M
o
d
b
u
s
 
C
o
i
l
s
:
2
0
4
9
-
3
0
7
2
 
 
D
L
X
0
-
1
7
7
7
*
M
o
d
b
u
s
 
I
n
p
u
t
 
R
e
g
i
s
t
e
r
s
:
*
*
1
-
4
0
9
6
 
 
 
D
L
V
0
-
7
7
7
7
*
1
7
,
5
0
1
-
1
7
,
5
0
6
 
 
I
n
t
e
r
n
a
l
 
E
C
O
M
1
0
0
 
V
e
r
s
i
o
n
 
I
n
f
o
 
(
E
C
O
M
 
m
a
n
u
a
l
)
1
7
,
5
1
1
-
1
7
,
6
0
0
 
 
I
n
t
e
r
n
a
l
 
E
C
O
M
1
0
0
 
D
e
v
i
c
e
 
D
a
t
a
 
(
E
C
O
M
 
m
a
n
u
a
l
)
M
o
d
b
u
s
 
H
o
l
d
i
n
g
 
R
e
g
i
s
t
e
r
s
:
*
*
1
-
4
0
9
6
 
 
D
L
V
0
-
7
7
7
7
*
1
8
,
0
0
1
-
1
8
0
2
0
 
 
I
n
t
e
r
n
a
l
 
E
C
O
M
1
0
0
 
D
y
n
a
m
i
c
 
M
o
d
 
D
a
t
a
 
(
E
C
O
M
 
m
a
n
u
a
l
)
*
 
T
h
e
s
e
 
r
a
n
g
e
s
 
a
r
e
 
l
a
r
g
e
r
 
t
h
a
n
 
t
h
e
 
d
e
f
a
u
l
t
.
 
 
U
s
e
 
M
e
m
o
r
y
 
C
o
n
f
i
g
u
r
a
t
i
o
n
 
t
o
 
e
n
l
a
r
g
e
 
t
h
e
m
 
i
f
 
n
e
e
d
e
d
*
*
 
N
o
t
i
c
e
 
b
o
t
h
 
I
n
p
u
t
 
&
 
O
u
t
p
u
t
 
R
e
g
i
s
t
e
r
s
 
a
d
d
r
e
s
s
 
D
L
V
Do-more w/ECOM100 SLAVE
Communications – Modbus TCP
 
Modbus TCP Client (Master)
(4) Do-more with 
ECOM100
Do-more’s Modbus TCP Client is 
not
 
utilized
A Modbus TCP Client exists & is enabled in the ECOM100
Must configure a Peer-to-peer table and select Modbus TCP
Must use 
DLRX
/
DLWX
 instructions with the proper 
From DL/To DL
 parameters
DLRX
 with 
From DL
 parameter will select the following:
FC01 “Read Coils” (Coils 1-6656)
:
GY0-3777 
 1-2048
Y0-1777 
 2049-3072
C0-3777 
 3073-5120
S0-1777 
 5121-6144
T0-377 
 6145-6400
CT0-377 
 6401-6656
FC02 “Read Inputs” (Inputs 1-3584)
:
GX0-3777 
 1-2048
X0-1777 
 2049-3072
SP0-777 
 3073-3584
FC03 “Read Holding Registers” (HRs 1-17056)
:
V0-41237  
 1-17056
FC04 “Read Input Registers” (IRs 1-17056)
:
V0-41237 
 1-17056
*
DLWX
 with 
To DL
 parameter will select the following:
FC15 “Force Multiple Coils”: Same mapping as FC01 “Read Coils” above
FC16 “Preset Multiple Registers”: Same mapping as FC03 “Read Holding Registers” above
*
To select this one requires the use of an odd number for the 
Number of Bytes
 parameter
Do-more w/ECOM100 MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
 
SYN
 
SYN, ACK
 
ACK
 
Modbus Request
 
ACK
 
Modbus Response
 
ACK
 
Establish TCP
Connection #1
over Port #502
 
Modbus
Protocol
Exchange
 
MRX/MWX #1
MRX/MWX #1
TCP
Connection #1
Established
TCP
Connection #1
Established
 
If Server does not
respond in 15 seconds
(not configurable) the
MRX/MWX
instruction errors out
If Server does not respond
in 
Timeout
 period it 
Retries
the number of times
specified before
MRX/MWX instruction
errors out
Do-more MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
 
Modbus Request
 
ACK
 
Modbus Response
 
ACK
 
Modbus
Protocol
Exchange
 
MRX/MWX #1
MRX/MWX #1
TCP
Connection #1
Established
TCP
Connection #1
Established
After TCP
Connection is
established, if an
MRX/MWX is not
executed within
Inactivity Timeout
setting, the TCP
Connection is
closed
Do-more MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
 
Modbus Request
 
ACK
 
Modbus Response
 
ACK
 
Modbus
Protocol
Exchange
 
MRX/MWX #1
MRX/MWX #1
TCP
Connection #1
Established
TCP
Connection #1
Established
Do-more MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
Modbus TCP Server
(Slave) #2
 
FIN, ACK
 
FIN, ACK
 
ACK
 
Establish TCP
Connection #2
over Port #502
TCP
Connection #1
Established
TCP
Connection #1
Established
 
MRX/MWX #2
MRX/MWX #2
 
Close TCP
Connection #1
 
SYN
 
SYN, ACK
 
ACK
TCP
Connection #2
Established
TCP
Connection #2
Established
2
nd
 Server (Slave) is
added, but still using just
one Modbus TCP Client in
Do-more
TCP Connection to
Server (Slave) #1 is still
established
Do-more MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
Modbus TCP Server
(Slave) #2
 
Modbus Request
 
ACK
 
Modbus Response
 
ACK
MRX/MWX #2
MRX/MWX #2
TCP
Connection #2
Established
TCP
Connection #2
Established
Do-more MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
@MyModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
Modbus TCP Server
(Slave) #2
 
Modbus Request
 
ACK
 
Modbus Response
 
ACK
TCP
Connection #1
Established
TCP
Connection #1
Established
 
MRX/MWX #1
MRX/MWX #1
 
SYN
 
SYN, ACK
 
ACK
 
Establish TCP
Connection #1
over Port #502
2
nd
 Modbus TCP Client
is created to service the
2
nd
 Server (Slave) #2
Do-more MASTER
Communications – Modbus TCP
@IntModTCPClient
(Master)
@MyModTCPClient
(Master)
DO-MORE PLC
Modbus TCP Server
(Slave) #1
Modbus TCP Server
(Slave) #2
 
Modbus Request
 
ACK
 
Modbus Response
 
ACK
 
Establish TCP
Connection #2
over Port #502
TCP
Connection #1
Established
TCP
Connection #1
Established
 
MRX/MWX #2
MRX/MWX #2
 
SYN
 
SYN, ACK
 
ACK
TCP
Connection #2
Established
TCP
Connection #2
Established
MRX/MWX #1
MRX/MWX #1
MRX/MWX #1
MRX/MWX #2
MRX/MWX #2
MRX/MWX #2
Do-more MASTER
Communications – Modbus TCP
 
MRX “Modbus Network Read”
Reads data from a Modbus (TCP or RTU) Server
Fully asynchronous instruction (red triangle)
Parameters:
Device
 – Modbus TCP Client Device name
Modbus/TCP addressing
IP Address
Fixed Address
Variable Address
TCP Port Number
 – default 502
Unit ID
 – default 255 (most Slaves ignore)
Function Code
1 (Read Coil)
2 (Read Discrete Inputs)
3 (Read Holding Registers)
4 (Read Input Registers)
7 (Read Exception Status
From Modbus Offset Address
Number of Modbus…
 “Coils”, “Discrete Inputs”, “Registers”
To Do-more Memory Address
 – where received data is stored
Do-more MASTER
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
M
R
X
 
M
o
d
b
u
s
 
N
e
t
w
o
r
k
 
R
e
a
d
P
a
r
a
m
e
t
e
r
s
:
E
n
a
b
l
e
O
n
c
e
 
o
n
 
L
e
a
d
i
n
g
 
E
d
g
e
C
o
n
t
i
n
u
o
u
s
 
o
n
 
P
o
w
e
r
 
F
l
o
w
a
t
 
I
n
t
e
r
v
a
l
 
 
e
x
e
c
u
t
e
s
m
u
l
t
i
p
l
e
 
t
i
m
e
s
 
b
a
s
e
d
 
o
n
 
t
h
e
I
n
t
e
r
v
a
l
 
c
o
n
f
i
g
u
r
e
d
C
o
n
s
t
a
n
t
V
a
r
i
a
b
l
e
O
n
 
S
u
c
c
e
s
s
:
 
S
e
t
 
b
i
t
 
o
r
 
J
M
P
 
t
o
S
t
a
g
e
O
n
 
E
r
r
o
r
:
 
S
e
t
 
b
i
t
 
o
r
 
J
M
P
 
t
o
S
t
a
g
e
E
x
c
e
p
t
i
o
n
 
R
e
s
p
o
n
s
e
 
(
o
p
t
i
o
n
a
l
)
Do-more MASTER
Communications – Modbus TCP
 
MWX “Modbus Network Write”
Writes data to a Modbus (TCP or RTU) Server
Fully asynchronous instruction (red triangle)
Parameters:
Device
 – Modbus TCP Client Device name
Modbus/TCP addressing
IP Address
Fixed Address
Variable Address
TCP Port Number
 – default 502
Unit ID
 – default 255 (most Slaves ignore)
Function Code
5 (Write Single Coil)
6 (Write Single Register)
15 (Write Multiple Coils)
16 (Write Multiple Registers)
To Modbus Offset Address
Number of Modbus…
 “Coils”, “Registers”
From Do-more Memory Address
 – where data to be written is stored
Do-more MASTER
Communications – Modbus TCP
 
 
 
 
 
 
 
 
 
 
 
M
W
X
 
M
o
d
b
u
s
 
N
e
t
w
o
r
k
 
W
r
i
t
e
P
a
r
a
m
e
t
e
r
s
:
E
n
a
b
l
e
O
n
c
e
 
o
n
 
L
e
a
d
i
n
g
 
E
d
g
e
C
o
n
t
i
n
u
o
u
s
 
o
n
 
P
o
w
e
r
 
F
l
o
w
a
t
 
I
n
t
e
r
v
a
l
 
 
e
x
e
c
u
t
e
s
m
u
l
t
i
p
l
e
 
t
i
m
e
s
 
b
a
s
e
d
 
o
n
 
t
h
e
I
n
t
e
r
v
a
l
 
c
o
n
f
i
g
u
r
e
d
C
o
n
s
t
a
n
t
V
a
r
i
a
b
l
e
O
n
 
S
u
c
c
e
s
s
:
 
S
e
t
 
b
i
t
 
o
r
 
J
M
P
 
t
o
S
t
a
g
e
O
n
 
E
r
r
o
r
:
 
S
e
t
 
b
i
t
 
o
r
 
J
M
P
 
t
o
S
t
a
g
e
E
x
c
e
p
t
i
o
n
 
R
e
s
p
o
n
s
e
 
(
o
p
t
i
o
n
a
l
)
Do-more MASTER
Communications – Modbus TCP
Do-more CPU
MRX
MWX
E
C
O
M
1
0
0
@IntModTCPClient
Do-more CPU
MC
MI
MIR
MHR
@ModbusTCPServer
 
Modbus TCP Client (Master)
 
Modbus TCP Server (Slave)
Do-more CPU
MRX
MWX
@IntModTCPClient
 
Modbus TCP Client (Master)
Do-more CPU
DLC
DLX
DLY
DLV
DL Server
 
Modbus TCP Server (Slave)
Communications – Modbus TCP
Do-more CPU
DLRX
DLWX
E
C
O
M
1
0
0
@ECOM_001
Do-more CPU
MC
MI
MIR
MHR
@ModbusTCPServer
 
Modbus TCP Client (Master)
 
Modbus TCP Server (Slave)
Do-more CPU
DLC
DLX
DLY
DLV
DL Server
 
Modbus TCP Server (Slave)
E
C
O
M
1
0
0
Modbus
Peer
to
peer
Do-more CPU
DLRX
DLWX
@ECOM_001
 
Modbus TCP Client (Master)
E
C
O
M
1
0
0
Modbus
Peer
to
peer
Communications – Modbus TCP
1
 Must use Client table in 
“ECOM100 Server Client Mapping (Do-more).PDF”
 file
     to choose correct Function Code & Modbus memory address
2
 Must use Client table in 
“ECOM100 Server Client Mapping.PDF”
 file to choose
     correct Function Code & Modbus memory address
Communications – Modbus TCP
1
 Must use Server table in 
“ECOM100 Server Client Mapping (Do-more).PDF”
 file
     to see where a Function Code & Modbus memory address maps into DL-memory
2
 Must use Server table in 
“ECOM100 Server Client Mapping.PDF”
 file to see where
     a Function Code & Modbus memory address maps into DL-PLC memory
Communications – Modbus TCP
 
 
 
 
 
T
h
e
r
e
 
a
r
e
 
a
c
t
u
a
l
l
y
 
3
 
M
o
d
b
u
s
 
p
r
o
t
o
c
o
l
s
(
1
)
 
M
o
d
b
u
s
 
R
T
U
(
2
)
 
M
o
d
b
u
s
 
T
C
P
(
3
)
 
M
o
d
b
u
s
 
O
v
e
r
 
T
C
P
Address
Function
Code
Data
Checksum
 
Modbus RTU Telegram
 
Modbus TCP Telegram
Transaction
Identifier
Protocol
Identifier
Length
Field
Unit ID
 
TCP/IP Frame
Do-more & ECOM100s 
do not natively
support 
Modbus Over TCP
Modbus 
Over
 TCP 
is just a
Modbus RTU Telegram
encapsulated in a TCP/IP Frame
However, it can be accomplished in Do-more using a 
Custom
TCP
 Device & using the 
CHECKSUM
 instruction to calculate
the “Checksum” portion of the telegram
Slide Note
Embed
Share

Explore the configuration and setup of Modbus TCP communication in Do-more devices, including the use of built-in Ethernet ports and ECOM100 modules for both server and client roles. Understand the parameters, limitations, and expandable ranges for communication with Modbus TCP devices as slaves and masters. Delve into the advancements with DL-PLC incorporating ECOM100 for enhanced Modbus TCP communication speeds and functionalities.


Uploaded on Sep 12, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Do-more Technical Training Communications (Modbus TCP)

  2. Communications Modbus TCP Modbus TCP Server (Slave) (1) Do-more built-in Ethernet port (2) Do-more w/ECOM100 Modbus TCP Client (Master) (3) Do-more built-in Ethernet port (4) Do-more w/ECOM100

  3. Do-more SLAVE Communications Modbus TCP Modbus TCP Server (Slave) (1) Do-more built-in Ethernet port Modbus TCP Server Device exists & is enabled by default (see CPU Configuration) Use CPU Configuration Modbus/TCP Server Configuration to change parameters as desired Maximum Concurrent Sessions: 1-16 (default 4) Up to 16 Clients (Masters) can talk to the Do-more. The 17thone will be unable to connect Client Inactivity Timeout: 1-65,535 seconds If Do-more hasn t heard from one of his Clients (Masters) in this time period, Do-more will do a TCP disconnect TCP Port Number: default 502 Serves up M-memory to the Modbus TCP Client Modbus Inputs 0-1023 MI0-1023* Modbus Coils 0-1023 MC0-1023* Modbus Input Registers 0-2047 MIR0-2047* Modbus Holding Registers 0-2047 MHR0-2047* *Range is expandable via Memory Configuration

  4. Do-more MASTER Communications Modbus TCP Modbus TCP Client (Master) (3) Do-more built-in Ethernet port One Modbus TCP Client Device (@IntModTCPClient) exists by default Use Device Configuration to change parameters as desired Timeout: milliseconds (ms) to wait for Server (Slave) to respond Retries: how many times to retry comm Inactivity Timeout: seconds to keep TCP connection alive due to inactivity (no MRX/MWX being executed) before doing a TCP disconnect from the Server (Slave) Use MRX (Read) & MWX (Write) instructions Multiple MRX/MWX instructions can be used to same Server (Slave) If >1 Server (Slave), create a Modbus TCP Client Device for each one (explained in a few minutes)

  5. DL-PLC w/ECOM100 MASTER Communications Modbus TCP DL & ECOM100 History Lesson Remember the New Advancements?: ECOM100 invented that runs at 100Mbps & supports Modbus TCP (Client & Server) requiring TCP/IP to be supported: IP address, subnet mask & gateway address Also, peer-to-peer must be used to select Modbus TCP New Problem: How to further select Modbus Function Code & register address?

  6. DL-PLC w/ECOM100 MASTER Communications Modbus TCP DL & ECOM100 History Lesson Original Requirements: Module ID (a number from 0-90) is the only means to address the communication partner Solved with peer-to-peer table New Requirements: How to select Modbus TCP? SOLUTION: A 2nd peer-to-peer selection How to select Modbus FC? How to select register address? ( RX/WX Device Number ) to an IP Address but also selects Modbus TCP protocol Converts Module ID ( RX/WX Device Number ) to an IP Address Not only converts Module ID These last two are solved with mapping

  7. DL-PLC w/ECOM100 MASTER Communications Modbus TCP DL & ECOM100 History Lesson Modbus TCP Client Mapping: Uses RX/WX operand to select both the Modbus FC & the register address

  8. DL-PLC w/ECOM100 SLAVE Communications Modbus TCP DL & ECOM100 History Lesson Modbus TCP Server Mapping: Responds to the Modbus FCs as shown Notice, however, FC03 & FC04 both serve up DL-PLC s V-memory This is not usually a problem for 3rd-party Modbus TCP Clients, but

  9. DL-PLC w/ECOM100 MASTER Communications Modbus TCP DL & ECOM100 History Lesson New Problem: Modbus TCP Client mapping doesn t allow the ability to address Modbus Input Registers! SOLUTION: Use an odd length designation to change from using Holding Registers to using Input Registers Why this works: the length parameter is always an even number because it designates bytes and all Modbus registers are words (2 bytes) IR?

  10. DL-PLC w/ECOM100 SLAVE/MASTER Communications Modbus TCP DL & ECOM100 History Lesson All previous maps were for DL PLCs using ECOM100s Can ECOM100 be used to do Modbus TCP while in a Do- more PLC base?... Yes however To an ECOM100 as any kind of server in a Do-more PLC, only DL-memory is available So the server mapping chart is further restricted As Modbus TCP Server: FC01 Read Coils , FC05 Force Single Coil & FC15 Force Multiple Coils only access DLY0-1777 & DLC0-3777 FC02 Read Inputs only accesses DLX0-1777 FC03 Read Holding Registers , FC06 Preset Single Register & FC16 Preset Multiple Registers only access DLV0-7777 FC04 Read Input Registers also only accesses DLV0-7777 As Modbus TCP Client: Must use DLRX/DLWX (notMRX/MWX!) with proper parameter

  11. Do-more w/ECOM100 SLAVE Communications Modbus TCP Modbus TCP Server (Slave) (2) Do-more with ECOM100 Do-more s Modbus TCP Server is not utilized A Modbus TCP Server exists & is enabled in the ECOM100 Modbus I/O mapping from ECOM100 will go to DL-memory Modbus Inputs: 2049-3072 DLY0-1777* 3073-5120 DLC0-3777* Modbus Coils: 2049-3072 DLX0-1777* Modbus Input Registers:** 1-4096 DLV0-7777* 17,501-17,506 Internal ECOM100 Version Info (ECOM manual) 17,511-17,600 Internal ECOM100 Device Data (ECOM manual) Modbus Holding Registers:** 1-4096 DLV0-7777* 18,001-18020 Internal ECOM100 Dynamic Mod Data (ECOM manual) * These ranges are larger than the default. Use Memory Configuration to enlarge them if needed ** Notice both Input & Output Registers address DLV

  12. Do-more w/ECOM100 MASTER Communications Modbus TCP Modbus TCP Client (Master) (4) Do-more with ECOM100 Do-more s Modbus TCP Client is not utilized A Modbus TCP Client exists & is enabled in the ECOM100 Must configure a Peer-to-peer table and select Modbus TCP Must use DLRX/DLWX instructions with the proper From DL/To DL parameters DLRX with From DL parameter will select the following: FC01 Read Coils (Coils 1-6656): GY0-3777 1-2048 Y0-1777 2049-3072 C0-3777 3073-5120 S0-1777 5121-6144 T0-377 6145-6400 CT0-377 6401-6656 FC02 Read Inputs (Inputs 1-3584): GX0-3777 1-2048 X0-1777 2049-3072 SP0-777 3073-3584 FC03 Read Holding Registers (HRs 1-17056): V0-41237 1-17056 FC04 Read Input Registers (IRs 1-17056): V0-41237 1-17056* DLWX with To DL parameter will select the following: FC15 Force Multiple Coils : Same mapping as FC01 Read Coils above FC16 Preset Multiple Registers : Same mapping as FC03 Read Holding Registers above *To select this one requires the use of an odd number for the Number of Bytes parameter

  13. Do-more MASTER Communications Modbus TCP @IntModTCPClient (Master) Modbus TCP Server (Slave) #1 MRX/MWX #1 SYN Establish TCP Connection #1 over Port #502 Established TCP TCP SYN, ACK Connection #1 Connection #1 Established ACK If Server does not respond in 15 seconds (not configurable) the MRX/MWX instruction errors out If Server does not respond in Timeout period it Retries the number of times specified before MRX/MWX instruction Modbus Request ACK Modbus Protocol Exchange Modbus Response ACK DO-MORE PLC errors out

  14. Do-more MASTER Communications Modbus TCP @IntModTCPClient (Master) Modbus TCP Server (Slave) #1 After TCP Connection is established, if an MRX/MWX is not executed within TCP TCP Connection #1 Established Connection #1 Established MRX/MWX #1 Inactivity Timeout setting, the TCP Modbus Request Connection is closed ACK Modbus Protocol Exchange Modbus Response ACK DO-MORE PLC

  15. Do-more MASTER Communications Modbus TCP @IntModTCPClient (Master) Modbus TCP Server (Slave) #1 TCP TCP Connection #1 Established Connection #1 Established MRX/MWX #1 Modbus Request ACK Modbus Protocol Exchange Modbus Response ACK DO-MORE PLC

  16. Do-more MASTER Communications Modbus TCP @IntModTCPClient (Master) MRX/MWX #2 Modbus TCP Server (Slave) #1 FIN, ACK TCP TCP Close TCP Connection #1 FIN, ACK Connection #1 Established Connection #1 Established ACK TCP Connection to Server (Slave) #1 is still established 2nd Server (Slave) is added, but still using just one Modbus TCP Client in Do-more Modbus TCP Server (Slave) #2 SYN Establish TCP Connection #2 over Port #502 Established TCP TCP SYN, ACK Connection #2 Connection #2 Established ACK DO-MORE PLC

  17. Do-more MASTER Communications Modbus TCP @IntModTCPClient (Master) MRX/MWX #2 Modbus TCP Server (Slave) #1 Modbus TCP Server (Slave) #2 Modbus Request ACK TCP TCP Connection #2 Established Connection #2 Established Modbus Response ACK DO-MORE PLC

  18. Do-more MASTER Communications Modbus TCP @IntModTCPClient (Master) MRX/MWX #1 Modbus TCP Server (Slave) #1 Modbus Request SYN ACK Establish TCP Connection #1 TCP TCP SYN, ACK Connection #1 Established over Port #502 Connection #1 Established Modbus Response ACK ACK @MyModTCPClient (Master) Modbus TCP Server (Slave) #2 2nd Modbus TCP Client is created to service the 2nd Server (Slave) #2 DO-MORE PLC

  19. Do-more MASTER Communications Modbus TCP Multiple MRXs & MWXs possible @IntModTCPClient (Master) Modbus TCP Server (Slave) #1 TCP TCP MRX/MWX #1 MRX/MWX #1 MRX/MWX #1 Connection #1 Established Connection #1 Established No disconnect & reconnect (management) of the TCP MRX/MWX #2 Connections is necessary @MyModTCPClient (Master) Modbus TCP Server (Slave) #2 Modbus Request SYN MRX/MWX #2 MRX/MWX #2 MRX/MWX #2 Establish TCP Connection #2 over Port #502 Connection #2 Established ACK TCP TCP SYN, ACK Connection #2 Established Modbus Response ACK ACK DO-MORE PLC

  20. Do-more MASTER Communications Modbus TCP MRX Modbus Network Read Reads data from a Modbus (TCP or RTU) Server Fully asynchronous instruction (red triangle) Parameters: Device Modbus TCP Client Device name Modbus/TCP addressing IP Address Fixed Address Variable Address TCP Port Number default 502 Unit ID default 255 (most Slaves ignore) Function Code 1 (Read Coil) 2 (Read Discrete Inputs) 3 (Read Holding Registers) 4 (Read Input Registers) 7 (Read Exception Status From Modbus Offset Address Number of Modbus Coils , Discrete Inputs , Registers To Do-more Memory Address where received data is stored

  21. Do-more MASTER Communications Modbus TCP MRX Modbus Network Read Parameters: Enable Once on Leading Edge Continuous on Power Flow at Interval executes multiple times based on the Interval configured Constant Variable On Success: Set bit or JMP to Stage On Error: Set bit or JMP to Stage Exception Response (optional)

  22. Do-more MASTER Communications Modbus TCP MWX Modbus Network Write Writes data to a Modbus (TCP or RTU) Server Fully asynchronous instruction (red triangle) Parameters: Device Modbus TCP Client Device name Modbus/TCP addressing IP Address Fixed Address Variable Address TCP Port Number default 502 Unit ID default 255 (most Slaves ignore) Function Code 5 (Write Single Coil) 6 (Write Single Register) 15 (Write Multiple Coils) 16 (Write Multiple Registers) To Modbus Offset Address Number of Modbus Coils , Registers From Do-more Memory Address where data to be written is stored

  23. Do-more MASTER Communications Modbus TCP MWX Modbus Network Write Parameters: Enable Once on Leading Edge Continuous on Power Flow at Interval executes multiple times based on the Interval configured Constant Variable On Success: Set bit or JMP to Stage On Error: Set bit or JMP to Stage Exception Response (optional)

  24. Communications Modbus TCP Modbus TCP Server (Slave) Modbus TCP Client (Master) Do-more CPU Do-more CPU MC MI MIR MHR MRX MWX @IntModTCPClient @ModbusTCPServer Modbus TCP Server (Slave) Modbus TCP Client (Master) E C O M 1 0 0 Do-more CPU Do-more CPU DLC DLX DLY DLV MRX MWX DL Server @IntModTCPClient

  25. Communications Modbus TCP Modbus TCP Server (Slave) Modbus TCP Client (Master) E C O M Do-more CPU Do-more CPU MC MI MIR MHR Modbus Peer to peer DLRX DLWX @ECOM_001 @ModbusTCPServer 1 0 0 Modbus TCP Client (Master) Modbus TCP Server (Slave) E C O M Do-more CPU E C O M 1 0 0 Do-more CPU DLC DLX DLY DLV Modbus Peer to peer DLRX DLWX @ECOM_001 1 0 0 DL Server

  26. Communications Modbus TCP # Master CPU Ethernet Port Function Codes Instruction Device 1 Do-more Internal MRX/MWX @IntModTCPClient 1-7, 15, 16 2 ECOM100 (Modbus TCP Peer-to-Peer) 1-4, 15, 16 DLRX/DLWX1 @ECOM_001 3 DL-PLC ECRX/ECWX2 n/a 1 Must use Client table in ECOM100 Server Client Mapping (Do-more).PDF file to choose correct Function Code & Modbus memory address 2 Must use Client table in ECOM100 Server Client Mapping.PDF file to choose correct Function Code & Modbus memory address

  27. Communications Modbus TCP # Slave CPU Ethernet Port Function Codes Device Memory 1 Do-more Internal @ModbusTCPServer 1-7, 15, 16, 22 M-memory 2 ECOM100 @ECOM_001 1-6, 15, 16 DL-memory1 C, CT, GX, GY, S, SP, T, V, X, Y & Internal ECOM100 memory2 3 DL-PLC n/a 1 Must use Server table in ECOM100 Server Client Mapping (Do-more).PDF file to see where a Function Code & Modbus memory address maps into DL-memory 2 Must use Server table in ECOM100 Server Client Mapping.PDF file to see where a Function Code & Modbus memory address maps into DL-PLC memory

  28. Communications Modbus TCP There are actually 3 Modbus protocols (1) Modbus RTU (2) Modbus TCP (3) Modbus Over TCP Modbus Over TCP is just a Modbus RTU Telegram encapsulated in a TCP/IP Frame TCP/IP Frame TCP/IP Frame Modbus RTU Telegram Modbus TCP Telegram Length Function Modbus RTU Telegram Protocol Address Function Code Field Code Transaction Identifier Data Unit ID Data Address Identifier Checksum Checksum Do-more & ECOM100s do not natively support Modbus Over TCP However, it can be accomplished in Do-more using a Custom TCP Device & using the CHECKSUM instruction to calculate the Checksum portion of the telegram

More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#