Mitsubishi Electric MELSEC iQ-F Series User Manual page 124

Error code Error name
CB03H MQTT communication
error
CB04H MQTT communication
error
CB07H MQTT communication
error
CB10H MQTT communication
error
CB11H MQTT communication
error
CB12H MQTT communication
error
CB13H MQTT communication
error
CB14H MQTT communication
error
CB15H MQTT communication
error
CB16H MQTT communication
error
CB17H MQTT communication
error
CB20H MQTT communication
error
CB21H MQTT communication
error
CB22H MQTT communication
error
CB23H MQTT communication
error
CB24H MQTT communication
error
CB25H MQTT communication
error
10 TROUBLESHOOTING
122
10.6 List of Error Codes
Error details and causes
Host name resolution has failed.
An SSL connection error has occurred.
An SNI extended setting error has occurred.
An MQTT connection error (CONNACK is not
received) has occurred.
An MQTT connection error (MQTT protocol
version invalid) has occurred.
An MQTT connection error (identifier invalid)
has occurred.
An MQTT connection error (the server cannot
be used) has occurred.
An MQTT connection error (invalid user name
or password) has occurred.
An MQTT connection error (connection is
prohibited) has occurred.
An MQTT connection error (a code not
specified in the MQTT protocol has been
received) has occurred.
An MQTT connection error (network error
during connection) has occurred.
A subscribe execution error (SUBACK is not
received) has occurred.
A subscribe execution error (SUBACK is
received, but the server returns an error) has
occurred.
The subscribe ID overlaps.
The topic overlaps.
The number of registrations for subscribe ID0
has exceeded the maximum value.
A network error during execution of
SUBSCRIBE command has occurred.
Action
• Check the DNS server address.
• Run a PING command to check whether the DNS server can be
communicated.
• Check that the own station IP address and the DNS server IP
address are in the same class. (If the class differs, check the
router settings.)
• Retry the operation after a while.
• Check the network environment.
• Check the host name of the server to be connected.
• Check the connection settings of the external device. (Such as
TLS/TCP or port address)
• If TLS is specified, check if the certificate is appropriate. (Check
for problems such as an appropriate certificate not being set
and the common name in the server certificate not matching
with the settings of the destination host.)
• Retry the operation after a while.
• Reset the CPU module, and then switch it to RUN mode. If the
error occurs again even after the above action is taken, the
possible cause is a hardware failure of the CPU module. Please
consult your local Mitsubishi representative.
Check the following points and retry the processing from FB:
MQTT_Connect.
• Is there any problem with network cables or other
environmental factors?
• Is the server operating normally?
Check that the MQTTVersion of the server is 3.1.1.
Check that the string used is permitted for the server.
Check whether the server can use MQTT.
Check that the user name and password are valid.
Check that connection of the client concerned is permitted by the
server.
Check if there is a problem with the server.
Check if the QoS specification is correct when specifying the Will
status. (This error occurs if the server does not support the
specified QoS.) If there is no problem with the specification, check
the network environment, such as the connection cable.
Retry the operation from FB: MQTT_Subscribe or FB:
MQTT_Connect. If the error persists, check if there is a problem
with the server.
Check if there is a problem with the server.
A subscribe ID that is already set is specified again with another
topic.
Change the subscribe ID.
A topic that is already set is specified again with another
subscribe ID.
Change it without performing the other subscribe process.
The maximum number (256) that can be specified for the
subscribe ID0 has been exceeded.
Keep the number of subscriptions with subscribe ID0 to 256 or
less.
This error also occurs if the specified topic filter is invalid or the
server does not support the specified QoS. Check that there is no
error with the specification of the topic filter/QoS.
If there is no problem with the specification, check the network
environment, such as the connection cable.