Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Home
  • Knowledge base
  • Contact Us
  • Home
  • Connectors
  • Mitsubishi MELSEC

MELSEC - Troubleshooting

Troubleshooting of Mitsubishi MELSEC instances and items

Written by Mads Mikkelsen

Updated at August 16th, 2021

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Installation & Technical information
    Introduction SIA Connect Standalone SIA Connect ANY-Ware Cellular & WiFi connectivity
  • Configuration in the Web UI
    Getting started with the UI Connectors Instances Items Mapping Data System Network Tools & Add-ons DigiCert IoT Trust Manager
  • Connectors
    Siemens S7 Azure IoT Ethernet/IP Mitsubishi MELSEC OPC-UA Server SQL MQTT Omron Host Link REST API Omron FINS Keyence Beckhoff TwinCAT BACnet Virtual OPC-UA Client MS SQL File M-Bus Modbus
  • Scripting & Variables
    Data formatting
  • Developers
    API documentation Shadow API
  • Tutorials & Guides
    InfluxDB AWS IoT Core - Amazon Web Services Microsoft Power BI KaaIoT Siemens S7 AVEVA Insight SIA Connect Demo Rack Grafana Azure
  • General
+ More

Articles in this section:

  • Mitsubishi MELSEC - Instance & item setup
  • MELSEC - Troubleshooting
  • Enabling communication in Mitsubishi MELSEC controller

Table of Contents

Error messagesInstanceNotes

You most likely encountered some problems with connecting to your Mitsubishi MELSEC device and you ended up here.

This article will describe some of the most common faults encountered when trying to connect and exchange data with your MELSEC device. All the various error messages is also explained here.

Error messages

Both instance and items can have errors. The following sections describes the error and how to solve them.


Instance

The instance errors are related to the connectivity status of the connector to the PLC. These errors are shown in SIA's web interface.

Error message Solution
The request cannot be executed to the CPU module.
  • Correct the network number, PC number, request destination module I/O number, or request destination module station number.
  • Correct the read/write request data
Not connected to Melsec PLC
  • Correct port
  • Correct IP
  •  Check cable connection
  • Check if the model selected is in the same series with the PLC
  • Check if ASCII mode is enabled on the PLC or select Binary
Invalid port or IP
  • Correct port
  • Correct IP
Mode mismatch. Select binary
  • Check if ASCII mode is enabled on the PLC or select binary
Mode mismatch. Select ASCII
  • Check if binary mode is enabled on the PLC or select ASCII
Select A or FX or 1E model
  • Select A, FX or 1E model
ASCII code data that cannot be converted to binary code was received from an external device
  • Select Binary in the "Mode" field
  • Enable ASCII mode communication on the PLC



Notes

  • Writing anything else than a integer value to a bit device (not a dot notated memory address.) is the same as writing the value 0
  • Writing any integer value to a bit device is the same as writing the value 1
  • Writing any value that is not in-between the boundaries of the valid values will not be written to the PLC.
  • Creating a bit type item that points to a non-existing bit in the word (i.e. memory address  D100.567) will not be written to the PLC.

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Mitsubishi MELSEC - Instance & item setup

0
0
Expand