Yaskawa MP3200 Troubleshooting Manual - Manual (Page 104)

5.2 Troubleshooting Message Communications
Message Communications Errors
5-29
T
roubleshooting Programming and Debugging
 Checking the Input Items to the Message Function
If message communications with a PLC, touch panel, or PC from another manufacturer do not start, the
message function may not have been executed properly due to incorrect input items to the message func-
tion.
Use the following procedure to check the input items to the message function.
 Dev-Typ (Communications Device Type)
Specify the type code of the communications device.
 Pro-Typ (Communications Protocol)
Specify the type code of the communications protocol.
Connection Parameter Tab Page in Module’s Detail Definition Dialog Box
Device Type Code (Decimal)
218IFD 16
Type Code Communications Protocol Remarks
1 MEMOBUS
• If the protocol type is set to Extended MEMOBUS, MEMO-
BUS, MELSEC, or MODBUS/TCP on the Connection Parame-
ter Tab Page in the Module’s Detail Definition Dialog Box, set 1
for the type code.
• The communications protocol that is set here is used between the
CPU Unit/CPU Module and the 218IFD.
The Communications Function Module converts the data to the
protocol that is set in the connection parameters
2
No-protocol communica-
tions 1 (unit: words) Receives data in word units in no-protocol communications.
A response is not sent to the remote station.
3
No-protocol communica-
tions 2 (unit: bytes) Receives data in byte units in no-protocol communications.
A response is not sent to the remote station.
C
D
E
F