Contents

Contents
- Manual number
- Guidelines
- Further Information Manual List
- Table of Contents
- 1. Introduction
  - 1.1 Abbreviations, Generic Names and Terms Used in This Manual
  - 1.2 Communication Types
  - 1.3 System Configuration
    - 1.3.1 N:N Network
    - 1.3.2 Parallel Link
    - 1.3.3 Computer Link
    - 1.3.4 No Protocol Communication
  - 1.4 Supported Functions and Applicable Versions
- 2. Specifications
  - 2.1 Communication Specification
  - 2.2 Communication Time
    - 2.2.1 N:N network
    - 2.2.2 Parallel link
    - 2.2.3 Computer link
- 3. Wiring
  - 3.1 Caution on cable selection
    - 3.1.1 FX1N-485-BD, FX2N-485-BD, FX2NC-485ADP
    - 3.1.2 FX0N-485ADP
    - 3.1.3 FX2-40AW
  - 3.2 Using RS-232C Interface
    - 3.2.1 Using RS Instruction or Computer Link
    - 3.2.2 Using FX2N-232IF
  - 3.3 Using RS-485 Interface
    - 3.3.1 Wiring Selection
    - 3.3.2 Terminal Resistor
    - 3.3.3 One-pair Wiring
    - 3.3.4 Two-pair Wiring
  - 3.4 Parallel Link
    - 3.4.1 FX2N(1N)-485-BD and FX0N-485ADP
    - 3.4.2 FX0N-485ADP and FX0N-485ADP
    - 3.4.3 FX2N(1N)-485-BD and FX2N(1N)-485-BD
    - 3.4.4 FX2NC-485ADP and FX0N-485ADP
    - 3.4.5 FX2N(1N)-485-BD and FX2NC-485ADP
    - 3.4.6 FX2NC-485ADP and FX2NC-485ADP
    - 3.4.7 FX2-40AW and FX2-40AW
    - 3.4.8 FX2-40AP and FX2-40AP
- 4. N:N Network
  - 4.1 Related Flags and Data Registers
    - 4.1.1 Auxiliary Relays
    - 4.1.2 Data Registers
  - 4.2 Setting
    - 4.2.1 Setting the Station No. (D8176)
    - 4.2.2 Setting the Total Number of Slave Stations (D8177)
    - 4.2.3 Setting the Refresh Range (D8178)
    - 4.2.4 Setting Retry Count (D8179)
    - 4.2.5 Setting Comms Time-out (D8180)
    - 4.2.6 Program Used for Setting
  - 4.3 Example Program
    - 4.3.1 System Configuration
    - 4.3.2 Operations
    - 4.3.3 Example of Setting Program
    - 4.3.4 Example of Error Program
    - 4.3.5 Example of Operation Program
- 5. Parallel link
  - 5.1 Related Flags and Data Registers
  - 5.2 Mode and Link Device
    - 5.2.1 Normal Mode (Special auxiliary relay M8162: OFF)
    - 5.2.2 High Speed Mode (Special auxiliary relay M8162: ON)
  - 5.3 Example Program
    - 5.3.1 Normal Mode
    - 5.3.2 High Speed Mode
- 6. Communication format (D8120)
  - 6.1 What Is Communication Format?
  - 6.2 Related Flags and Data Registers
    - 6.2.1 Special Auxiliary Relays
    - 6.2.2 Special Data Registers
  - 6.3 Communication Format (D8120)
  - 6.4 Example of setting program
- 7. Computer Link
  - 7.1 Data Flow by Link
  - 7.2 Information Needed Before Programming
    - 7.2.1 Programmable Controller Operation
    - 7.2.2 Computer Notes
  - 7.3 How to Read a Control Protocol Diagram
  - 7.4 Basic Formats of Dedicated Protocol
    - 7.4.1 Control Protocol Format 1
    - 7.4.2 Control Protocol Format 4
    - 7.4.3 Control Protocol Parts Explained
    - 7.4.4 Time-out Check Time
  - 7.5 Communication Timing Chart
    - 7.5.1 Reading Data from Programmable controller
    - 7.5.2 Writing Data to Programmable Controller
    - 7.5.3 Communication Time
  - 7.6 Character Area Data Transmission
    - 7.6.1 Bit Device Memory
    - 7.6.2 Word Device Memory
  - 7.7 Commands and Device Ranges
    - 7.7.1 Commands
    - 7.7.2 Device specification ranges
  - 7.8 Example Computer Program for Loopback Test
- 8. Commands
  - 8.1 Batch Read of Bit Device (BR command)
  - 8.2 Batch Read of Word Device (WR command)
  - 8.3 Batch Write of Bit Device (BW command)
  - 8.4 Batch Write of Word Device (WW command)
  - 8.5 Test of Bit Device (BT command)
  - 8.6 Test of Word Device (WT command)
  - 8.7 Remote RUN/STOP (RR, RS commands)
    - 8.7.1 Operation of Remote RUN/STOP
    - 8.7.2 Conditions for Valid Execution of Remote RUN/STOP
    - 8.7.3 Control Specification and Examples of Remote RUN/STOP
  - 8.8 Reading The Programmable Controller Type (PC command)
    - 8.8.1 Type Codes
    - 8.8.2 Control Specification and Example
  - 8.9 Global Function (GW command)
    - 8.9.1 Control Specification and Example of Global Function
  - 8.10 On-demand Function
    - 8.10.1 Special Devices Used in On-demand Function
    - 8.10.2 On-demand Control Protocol
    - 8.10.3 Specification and Example of On-demand
  - 8.11 Loopback Test
- 9. RS instruction
  - 9.1 Function and Operation
    - 9.1.1 Send and Receive Program
    - 9.1.2 Operation of RS Instruction
    - 9.1.3 Related Flags and Data Registers
  - 9.2 Hardware Hand Shake Operation
    - 9.2.1 FX, FX2C, FX0N, FX1S, FX1N and FX2N (earlier than V 2.00)
    - 9.2.2 FX2N, FX2NC (V 2.00 or later)
  - 9.3 Number of Communication Data
    - 9.3.1 Deal with 16 bits Data
    - 9.3.2 Deal with 8 bits Data
  - 9.4 Example Program
    - 9.4.1 Personal Computer
    - 9.4.2 Printer
- 10. FX2N-232IF
  - 10.1 Introduction
    - 10.1.1 Outline of Product
  - 10.2 Allocation of Buffer Memories (BFMs)
    - 10.2.1 BFM List
    - 10.2.2 Communication Format <BFM#0>
    - 10.2.3 Command BFM #1
    - 10.2.4 Receive Upper Limit Byte Count BFM #2
    - 10.2.5 Receive Time-out Time <BFM #3>
    - 10.2.6 Send Header <BFM #5 (upper), BFM #4 (lower)>
    - 10.2.7 Send Terminator <BFM #7 (upper), BFM #6 (lower)>
    - 10.2.8 Receive Header <BFM #9 (upper), BFM #8 (lower)>
    - 10.2.9 Receive Terminator <BFM #11 (upper), BFM #10 (lower)>
    - 10.2.10 Receive Suspension Waiting Time <BFM #12>
    - 10.2.11 Number of Remaining Send Data <BFM #13>
    - 10.2.12 Number of Receive Buffers <BFM #14>
    - 10.2.13 Send Sum Result <BFM #15>
    - 10.2.14 Receive Sum Result <BFM #16>
    - 10.2.15 Time from CS ON to Send Start <BFM #20>
    - 10.2.16 Time from Completion of Actual Send to RS OFF (completion flag ON) <BFM #21>
    - 10.2.17 Status <BFM #28>
    - 10.2.18 Error Code <BFM #29>
    - 10.2.19 Model Code <BFM #30>
    - 10.2.20 Send Byte Count <BFM #1000>
    - 10.2.21 Send Buffers <BFMs #1001 to #1256>
    - 10.2.22 Receive Byte Count <BFM #2000>
    - 10.2.23 Receive Buffers <BFM #2001 to #2256>
    - 10.2.24 Spare Receive Buffers for Interlink Connection Mode <BFM #2257 to #2271>
  - 10.3 Hardware Hand Shake Operation
    - 10.3.1 No Hardware Hand Shake
    - 10.3.2 Standard RS-232C Mode
    - 10.3.3 Interlink Mode
  - 10.4 Example Program
    - 10.4.1 Example of 16 Bits Data Communication
    - 10.4.2 Example of 8 Bits Data Communication
- 11. Optional Programming Port
  - 11.1 FX2N-422-BD, FX1N-422-BD
  - 11.2 FX2N-232-BD FX1N-232-BD FX0N-232ADP and FX2NC-232ADP
    - 11.2.1 Connection cables
  - 11.3 Cautions on Use
    - 11.3.1 Cautions on Setting
    - 11.3.2 Cautions on use
- 12. Diagnostics
  - 12.1 Common Items
  - 12.2 N:N Network
    - 12.2.1 Error Code
    - 12.2.2 Diagnostics
  - 12.3 Parallel Link
    - 12.3.1 Diagnostics
  - 12.4 Computer Link
    - 12.4.1 NAK Error Code
    - 12.4.2 Programmable Controller Error Code
    - 12.4.3 Diagnostics
  - 12.5 RS Instruction
    - 12.5.1 Diagnostics
  - 12.6 FX2N-232IF
    - 12.6.1 Error code
    - 12.6.2 Diagnostics
  - 12.7 Using Optional Programming Port
    - 12.7.1 FX1S, FX1N and FX2N(C) earlier V2.00
    - 12.7.2 FX2N, FX2NC whose version is V 2.00 or later
  - Appendix A: ASCII code Lists
- Appendix A: ASCII code Lists

Mitsubishi Electric FX Communication User's Manual

Mitsubishi Electric FX Communication manual cover

Pages 162

Year 2003

Language(s)

of 162

Mitsubishi Electric FX Communication Specification

The Mitsubishi Electric FX Communication module is designed to enhance the connectivity and integration capabilities of the FX series programmable logic controllers (PLCs). This module facilitates seamless data exchange between PLCs and various industrial devices, ensuring efficient and reliable communication across multiple platforms. It supports a range of communication protocols, including Ethernet, RS-232C, RS-485, and Modbus, allowing for versatile integration with existing industrial systems. The FX Communication module is equipped with advanced diagnostics and configuration tools, enabling easy setup and maintenance.

With high data transfer rates, it ensures timely and accurate data processing, crucial for real-time applications. The module is engineered to withstand harsh industrial environments, featuring robust construction and compliance with international standards for electromagnetic compatibility and safety. It integrates seamlessly with Mitsubishi Electric's comprehensive suite of automation solutions, offering scalable options for small to medium-sized systems.

The module supports remote monitoring and control, providing enhanced operational efficiency and reduced downtime. Its compact design allows for easy installation and space-saving in control panels. The FX Communication module is also equipped with comprehensive security features to protect data integrity and prevent unauthorized access. It is compatible with Mitsubishi Electric's programming software, allowing for simplified programming and system integration.

Overall, the Mitsubishi Electric FX Communication module offers a powerful and flexible solution for industrial communication needs, ensuring optimal performance and reliability in various automation applications.

Mitsubishi Electric FX Communication F.A.Q.

How do I connect the Mitsubishi FX PLC to a computer for programming?

To connect the Mitsubishi FX PLC to a computer, use a programming cable compatible with the FX series, such as SC-09. Connect one end to the PLC's programming port and the other to the computer's USB or serial port. Ensure that the appropriate driver and programming software (GX Developer or GX Works2) are installed on your computer.

What is the procedure for troubleshooting communication errors in FX PLCs?

First, check all physical connections and ensure cables are securely attached. Verify that the correct communication settings (baud rate, parity, data bits) are configured in both the PLC and the connected device. Use diagnostic tools within the programming software to identify error codes and refer to the manual for troubleshooting steps based on those codes.

How can I perform a firmware update on a Mitsubishi FX PLC?

Firmware updates for Mitsubishi FX PLCs are conducted via the programming software. First, download the latest firmware from the Mitsubishi Electric website. Connect the PLC to your computer, open the programming software, and navigate to the firmware update utility. Follow the on-screen instructions to complete the update process.

What should I do if the FX PLC does not respond to commands from the HMI?

Ensure that the communication settings between the HMI and PLC match. Check that the correct communication protocol is selected and that all cables and connections are intact. Use the HMI's diagnostic tools to verify the communication status and check for any error messages.

How do I back up and restore programs on a Mitsubishi FX PLC?

To back up a program, connect the PLC to your computer and use the programming software to download the program to your PC. Save the file in a secure location. To restore, connect the PLC, open the backup file in the programming software, and upload it to the PLC.

What is the best practice for maintaining the communication between FX PLC and other devices?

Regularly check and tighten connections to prevent loosening due to vibrations. Use high-quality shielded cables to reduce electromagnetic interference. Periodically inspect cables for wear and damage, and replace them as necessary. Keeping the firmware and software updated can also ensure optimal communication.

How do I configure the Ethernet communication module for a Mitsubishi FX PLC?

Install the Ethernet module according to the manufacturer's instructions. Use the programming software to set the IP address, subnet mask, and gateway for the module. Ensure that these settings are compatible with the network it will be connected to. Test the connection using a ping command or network diagnostic tool.

Can I use third-party software for programming Mitsubishi FX PLCs?

While Mitsubishi recommends using their own GX Developer or GX Works2 software for programming, some third-party software might offer compatibility. However, using non-proprietary software may not provide full access to all features and could lead to compatibility issues.

What steps should I take if an FX PLC is not powering on?

Check the power supply to ensure it is correctly connected and providing the necessary voltage. Inspect the PLC for any visible damage or signs of overheating. If the PLC has a fuse, verify that it is intact. Consult the manual for any specific error indicators and troubleshoot accordingly.

How can I ensure data integrity during communication between FX PLC and SCADA systems?

Implement error-checking protocols such as checksums or CRCs in your communication setup. Use redundant communication paths if possible. Regularly audit and monitor data logs to detect and resolve discrepancies promptly. Ensure that both PLC and SCADA software are updated to the latest versions.