Mitsubishi GOT2000 Utility Troubleshooting and System Maintenance Complete Guide

Mitsubishi GOT2000 Utility Troubleshooting and System Maintenance Complete Guide

The Mitsubishi GOT2000 series graphic operation terminal is a core device for human-machine interaction in industrial automation, widely used in production line monitoring, data acquisition, and equipment control. Its built-in Utility provides a complete set of functions from communication settings, system maintenance to data backup and fault diagnosis. However, on-site engineers often face issues such as communication interruptions, touch offset, system alarms, or data backup failures. This article is based on the GOT2000 series user manual (Utility section), combined with practical engineering experience, to systematically review the various functions of the Utility and provide troubleshooting steps for common faults, helping engineers quickly locate and solve on-site problems.

Overview of GOT2000 Utility Features

Utility is the built-in management program of GOT2000, which can complete the following tasks without connecting to a computer:

GOT basic settings: display, language, IP address, time synchronization, controller communication parameters, etc.

Extended feature settings: wireless LAN, VNC server, backup/restore, trigger backup, license management, etc.

Maintenance: Batch self check, USB device management, screen cleaning, touch calibration, system alarm display, drawing/font/touch screen inspection, I/O inspection, Ethernet status inspection, etc.

Monitoring: equipment monitoring, PLC program monitoring, network monitoring, servo amplifier monitoring, etc.

Data management: conversion, deletion, copying, and movement of alarm logs, recipe files, log files, image files, and operation logs; File manager, SD card formatting, memory check, packet management, etc.

Mastering these functions can significantly improve the efficiency of on-site fault handling.

Key Settings and Common Problems

2.1 Display and Operation Settings

Function description: It can set the display time of the startup screen, screen saver time, battery alarm display, human body sensor (some models), brightness adjustment, etc.

Common problem: The screen darkens after a long period of inactivity, but cannot be awakened by touch.

Troubleshooting steps:

Go to Utility → [GOT Setup] → [Display] and check if the "Screen save time" is set to a non-zero value.

If using a human sensor, confirm that it has been set to "Valid" and the sensor detection level is appropriate (default 10, highest sensitivity).

Check if forced screen saver (system signal) is enabled. It can be disabled through the system information function in GT Designer 3.

2.2 Language switching issues

Utility supports Japanese, English, Simplified Chinese, Traditional Chinese, Korean, etc., but requires the installation of corresponding fonts.

Fault phenomenon: After switching the system language, some menus still display the old language or garbled characters.

Solution:

Ensure that the corresponding font package is installed (written through GT Modeler 3).

Click the [Language] button on the Utility main interface, select the desired language, and restart GOT.

2.3 IP address setting and Ethernet communication failure

The Ethernet interface of GOT2000 requires correct configuration of IP address, subnet mask, and default gateway. The factory default IP addresses are 192.168.3.18 (standard port) and 192.168.5.22 (expansion port).

Common error: Communication interruption caused by IP address conflict.

Troubleshooting steps:

Go to [GOT Setup] → [IP Address] and confirm that "Ethernet comm. unit" is set to "Effective".

Check if the IP address is duplicated with other devices in the network. If repeated, GOT will display the system alarm "G01-425" and may automatically disconnect the network.

You can select 'Maintain a network connection (rec)' or 'Do not maintain' in the 'Behavior of duplicate IPs'. It is recommended to maintain the former and manually modify the IP address in case of conflicts.

Use the [Ethernet status check] in the Utility to send ping packets to test the connectivity with the controller or server.

2.4 Controller Communication Setting Issues

GOT2000 communicates with PLC or other devices through multiple channels (CH1-CH4). The communication driver needs to be installed in advance.

Common faults: GOT displays "Communication timeout" (error code 402) or "SIO status error" (403).

Solution:

Check cable connections and communication unit installation.

Go to [GOT Setup] → [Controller] → [Channel Driver assignment] and confirm that the channel number has been correctly assigned to the communication driver (such as "MELSEC-FX").

Click on the driver display box to enter the "Communication detail setting", and verify that the parameters such as baud rate, data bits, stop bits, parity check, etc. are consistent with the PLC.

If using multiple channels, confirm that the Transparent mode channel number (usually CH1) is set correctly.

2.5 Clock synchronization (time setting)

GOT2000 can synchronize time from PLC or SNTP servers, and can also broadcast its own clock to the PLC.

Common problem: Time synchronization or low battery voltage causing clock data loss.

Solution steps:

Install the built-in battery of GOT (GT11-50BAT or GT15-BAT), otherwise the time will not be maintained after power failure.

In [GOT Setup] → [Time], enable "Adjust" or "Broadcast" as needed.

Adjust: GOT retrieves time from PLC or SNTP server. Reference channel number or SNTP server IP needs to be set.

Broadcast: GOT writes its own time to the PLC. Broadcast channels and triggering conditions (rising edge/falling edge/timed sampling) need to be set.

If you need to display the local time zone, set "Local time" and select the time zone (such as GMT+8:00).

System maintenance and self inspection

3.1 Batch Self Check

Batch self-test can collect GOT startup information, system status, communication settings, operation history, screen switching history, clock change history, system alarm history, CPU error history, etc., and can export system status logs to SD card.

Operation: Go to [Maintenance] → [Batch self check], select the export destination drive (A: SD card), and click [Start]. After completion, detailed results can be viewed.

Application scenario: Export logs for Mitsubishi technical support analysis when GOT frequently restarts or encounters anomalies.

3.2 Touch Panel Calibration

Due to long-term use or temperature changes, the touch position may shift.

Calibration steps:

[Maintenance] → [Touch panel calibration].

Touch the center of the four "+" symbols (top left, top right, bottom left, bottom right) displayed on the screen in order.

Automatically return after calibration is completed.

Troubleshooting: If the calibration is still inaccurate, the calibration can be repeated. If a 'Touch panel calibration error' occurs, the touch panel may have a hardware malfunction and needs to be replaced.

3.3 System Alarm Viewing and Clearing

System Alarm displays error messages such as GOT, controller, network, etc.

Viewing method:

View the current alarm list in [Maintenance] → [System alarm].

The error code format is "G01-402" (G is GOT error, 01 is classification, 402 is specific error).

Controller errors (such as PLC) will display "M0128-1000" and so on.

Clearing method:

GOT self error: After eliminating the cause, click the [Reset] button on the system alarm screen.

CPU error or network error: Automatically reset after eliminating the cause.

If it cannot be cleared, restart GOT.

3.4 Touch Panel Check

Used to detect whether there is a dead zone in the touch area.

Operation:

[Maintenance] → [Touch panel check], the screen turns completely black.

Touch various areas of the screen with your fingers, and the touched points will turn yellow (or white/gray depending on the model).

If there is no color change after touching a certain area, the touch screen may be damaged.

3.5 I/O check and Ethernet check

I/O check: Used to test RS-232 interface hardware. Self loop connectors (short circuits 2-3, 4-6, 7-8) need to be made, and then Self loop back testing should be performed.

Ethernet status check: Enter the destination IP address and click [Ping transmission] to test network connectivity.

Data Management and Backup

4.1 Alarm Log Management (Alarm Information)

The alarm log is stored in G2A format on an SD card, USB, or network drive.

Common operations:

Convert format: Select G2A file, click [G2A → CSV] or [G2A → TXT], and export as a readable file.

Delete/Copy: Select the file and click [Del] or [Copy].

Troubleshooting: If the alarm log cannot be read, it may be due to a format mismatch caused by a change in project data (error code 525). At this point, old logs need to be deleted or recreated.

4.2 Recipe Information Management

The recipe file (G2P) can read and write device values from the controller, and can also be converted to CSV or Unicode text for editing.

Common problem: Recipe writing failed (error code 583/584).

Solution:

Check if the SD card is write protected.

Confirm that the recipe file is not damaged and regenerate it if necessary.

If the SRAM user area space is insufficient, initialize or backup data through [Data Management] → [SRAM Management].

4.3 Backup/Restoration

GOT2000 can backup the sequence program, parameters, file registers, etc. of PLC to SD card, and supports triggering backup (automatic backup according to conditions).

Backup settings:

[Extended function setting] → [Backup/reset] Set the backup destination drive (A: SD card).

The maximum backup data quantity can be set (0-50, 0 is unlimited).

Trigger backup: The trigger type (Rise/Time) and corresponding device or time can be set in [Trigger backup].

Recovery precautions:

The target PLC must be in STOP state before recovery (FX series needs to be manually stopped).

If a backup/recovery password is set, you need to enter the password first.

Common error: Backup data not found (error code 634) - Check if the SD card is inserted or if the drive in the backup settings is correct.

4.4 SD Card Format and Memory Check

SD Card Format: In [Data Management] → [Memory Card Format], enter the password "1111" and format the SD card. Note: GOT cannot format an unformatted SD card, it needs to be formatted as FAT16/FAT32 on a PC first.

Memory Check: Conduct read and write tests on built-in flash memory, SD cards, and USB drives to check for any faulty blocks.

Quick search and handling of system alarm codes

According to Chapter 8 of the manual, the following are the most common GOT system alarms and countermeasures encountered by engineers:

Typical causes and solutions for error codes and messages

301 Project data contains unsupported functions. GOT firmware or GT Designer 3 version is too low. Install the latest version of GT Designer 3 and rewrite project data.

306 No project data. Download screen data. Project data not downloaded. Download project data.

402 Communication timeout. Communication cable disconnected, PLC not powered on, communication parameter error. Check the cables, power supply, and communication settings.

403 SIO status error. Serial communication overload, parity check error. Check if the baud rate and data format are consistent.

425 A duplicate IP address has been detected. IP address conflict. Change the IP address of GOT or conflicting devices.

500 Warning! Built in battery voltage is low. The internal battery voltage of GOT is low. Replace the battery (model GT11-50BAT).

511 Detected a decrease in brightness or a failure of the liquid crystal backlight.  Backlight aging or malfunction. If it repeatedly occurs, the display screen needs to be repaired or replaced.

571 Capacity shortage of user memory (RAM). Insufficient user memory. Format the D drive (with built-in SRAM) or delete unnecessary files.

651 Cannot access the operator management information file. The operator information file cannot be accessed. Check if the SD card is inserted and not write protected.

For errors on the controller side (such as CPU running errors), the error code is usually 100-299, and it is necessary to refer to the corresponding PLC manual.

Key points for advanced feature settings

6.1 Wireless LAN Connection (Some Models)

It can be set to Access point (hotspot) or Station (client) mode in [Extended function setting] → [Wireless LAN function].

Common malfunction: Unable to connect to wireless network (error codes 431/432/433).

Inspection items:

Confirm that the wireless LAN communication unit has been installed correctly.

In Station mode, check if the SSID and authentication method match the AP.

Confirm that the wireless channel is not interfered with in Access point mode.

6.2 VNC Server Functionality

VNC server allows remote desktop access to GOT. Authorization guarantee time (0-3600 seconds) needs to be set in [Extended function setting] → [VNC server function]. At the same time, a license for VNC server functionality needs to be registered (registered in License Management).

6.3 SoftGOT-GOT Link Function

Used for sharing operation authorization with GT SoftGOT2000 software. Set exclusive authorization acquisition time and operation priority guarantee time. When GOT obtains exclusive authorization, SoftGOT cannot operate.

6.4 System Launcher

Allow system applications to be launched on GOT and enable Online module change. Please note that this feature is only supported on specific models.

6.5 Ethernet Printer Settings

Enter the printer IP address in [Extended function setting] → [Ethernet printer] to directly print the report file to the network printer.

Firmware and System Application Installation

When is it necessary to install BootOS or system applications?

The new GOT is being used for the first time (BootOS is pre installed, but basic system applications need to be installed).

Function upgrade or repair of faults.

Automatically compare versions when downloading project data from GT Designer 3, and prompt installation if there is no match.

7.2 Installation Method

Through SD card: Insert system applications (. g2p files) into the SD card, insert GOT, and press and hold the S.MODE switch (or touch the bottom right corner of the screen) when powering on to enter installation mode.

Through USB: For models that support USB, similar to SD card method.

Through GT Designer 3: Write directly using USB or Ethernet.

Notes:

Installing BootOS will clear all existing data (including project data).

During the installation process, do not turn off the power or remove the storage card.

Sharing of Engineering Site Cases

Case 1: GOT cannot communicate with FX5U in a certain factory

Phenomenon: GOT displays' Communication timeout '. Check that the cable connection is normal and the PLC running light is on.

Troubleshooting: Go to Utility → [GOT Setup] → [Controller] → check if the CH1 driver displays "MELSEC-FX", but in the detailed settings, the baud rate is 19200, while the FX5U is actually set to 9600. Change to 9600 and restart GOT to restore communication.

Case 2: Touch Screen Mistriggering

Phenomenon: The operator does not touch the screen, but automatically executes button actions.

Solution: Go to [Maintenance] → [Touch panel calibration] to recalibrate. At the same time, check if the "Key sensitivity" in [GOT Setup] → [Operation] is set too low (causing over sensitivity). Suggest adjusting from default 6 onwards.

Case 3: Alarm history cannot be converted to CSV

Phenomenon: When performing G2A → CSV conversion in [Data Management] → [Alarm Information], it prompts "File conversion failed".

Reason: The target folder already contains a file with the same name and is read-only, or it is write protected on an SD card.

Solution: Check the SD card write protection switch, or delete or move old files first.