.png)
ProSight by Coolmay for Mitsubishi Control Upgrades with GX Works2 and GX Developer Support
Older Mitsubishi control systems often sit at the centre of reliable machines. The challenge starts when the hardware becomes hard to source, the screen is fading, or small changes take too long because the original setup no longer matches the plant’s needs.
That is where selected ProSight by Coolmay PLC and touchscreen HMI options can fit. For some Mitsubishi control upgrade projects, documented Coolmay models support programming through GX Works2 and GX Developer, which can make the upgrade path more familiar for technicians already working with Mitsubishi automation tools.
This does not mean every Mitsubishi PLC can be replaced like-for-like without engineering checks. It does mean there may be a practical path for machines where the aim is to refresh the controller and operator interface while keeping the programming workflow recognisable.
Why Mitsubishi control upgrades need a careful path
Mitsubishi PLCs have been used for decades in packaging, process, pumping, food production, machine tending, materials handling, and general factory automation. Many systems still run well, but the surrounding conditions change.
Common reasons for an upgrade include:
the original PLC or HMI is no longer easy to buy
the screen has become dim, cracked, or unresponsive
spare parts lead times are too long
the machine needs extra inputs, outputs, alarms, or recipes
maintenance staff want better visibility of faults
the existing software tools or backups are incomplete
the plant wants to reduce downtime risk before a failure occurs
A control upgrade is not only a hardware swap. The program, wiring, field devices, communication links, operator screens, safety circuits, and commissioning process all matter.
For this reason, a good upgrade starts with a simple question: what must remain familiar, and what can change?
If the maintenance team already uses GX Works2 or GX Developer, keeping those tools in the project can lower the learning curve. It can also make software review and future support more straightforward, provided the selected hardware and project files are properly documented.
Where ProSight by Coolmay can fit
ProSight by Coolmay offers PLC and touchscreen HMI options that may suit selected Mitsubishi upgrade projects. The key point is the word selected. Compatibility needs to be assessed by model, software support, I/O requirements, communications, and the way the existing program is written.
Some documented Coolmay PLC models support Mitsubishi-style programming environments such as GX Works2 and GX Developer. That can be helpful where a project team wants to work within tools they already know, rather than moving the machine to a completely different programming platform.
A ProSight by Coolmay approach may suit projects such as:
replacing ageing compact PLC hardware on smaller machines
combining updated PLC control with a modern touchscreen HMI
refreshing a machine where the logic is well understood
improving operator screens without redesigning the whole process
preparing a spare or replacement controller for a known machine type
supporting maintenance teams that already use Mitsubishi programming tools
It is less suitable when the machine has highly specialised motion control, undocumented communication links, unusual expansion hardware, or safety functions that need certified safety PLC architecture. Those projects need more detailed engineering review and, in many cases, a different hardware strategy.
GX Works2 and GX Developer support matters because it reduces friction
Software familiarity is a practical advantage. Many electricians, controls technicians, and system integrators in Australia have experience with Mitsubishi programming environments. GX Developer is common on older projects, while GX Works2 is widely used for more recent systems.
When a documented controller model supports these tools, the project may avoid some of the rework that comes with changing platforms. Logic review, program editing, and commissioning can feel more familiar.
That said, support for a programming tool is not the same as full project interchangeability.
A careful project still needs to confirm:
whether the selected Coolmay PLC model is documented for GX Works2 or GX Developer
which PLC series settings are required in the software
whether all instructions used in the existing program are supported
how timers, counters, special relays, data registers, and memory areas map
whether analogue modules, high-speed counters, pulse outputs, or communications need changes
how the HMI connects to the PLC and reads device addresses
whether the final program has been tested on the actual machine
Software support can reduce the learning curve, but it does not replace engineering checks, bench testing, and commissioning on site.
This is the practical centre of ProSight by Coolmay for Mitsubishi Control Upgrades with GX Works2 and GX Developer Support. The value is not only in the hardware. It is in creating a path that respects the existing machine, the existing maintenance knowledge, and the realities of industrial downtime.
What to check before choosing a PLC option
Before selecting a replacement PLC, gather the facts from the current machine. A rushed hardware choice can create avoidable rework later.
The first step is to document the existing control system. Record the PLC model, expansion modules, power supply, HMI model, communication cables, field devices, and cabinet space. If a program backup exists, save a clean copy before changing anything.
Then check the following areas.
Area to check | Why it matters | What to confirm |
Digital I/O | Machine wiring must match the replacement design | Input and output count, voltage type, sink or source wiring, spare points |
Analogue I/O | Scaling errors can affect process control | Signal type, range, resolution, scaling, shielding |
Communications | HMIs, drives, meters, and remote devices may need specific protocols | Serial, Ethernet, Modbus, Mitsubishi protocol, device addresses |
Special functions | Not every compact PLC handles every machine function the same way | High-speed counters, pulse outputs, positioning, interrupts |
Program instructions | Existing logic may use instructions that need review | Timers, counters, data movement, comparison, maths, special relays |
HMI addressing | Screens rely on correct device mapping | Bit addresses, data registers, numeric formats, alarm bits |
Safety circuits | Safety must not be weakened during an upgrade | E-stops, guards, interlocks, safety relays, risk controls |
This table is not a replacement for a design review. It is a practical filter. If the machine uses basic digital I/O and straightforward logic, the path may be simple. If it uses motion, mixed networks, or old undocumented serial devices, allow more time for testing.
How a touchscreen HMI upgrade changes the operator experience
A PLC upgrade often gets most of the attention, but the HMI is usually what operators notice first. A better touchscreen can make faults easier to read, settings easier to adjust, and manual controls easier to use.
A useful HMI upgrade is not just a prettier version of the old screen. It should help people run the machine with fewer mistakes.
Good HMI work includes:
clear start-up and shutdown steps
alarm messages written in plain language
separate screens for manual control, settings, alarms, and diagnostics
visible machine status, such as running, stopped, faulted, or waiting
protected settings where unauthorised changes could cause downtime
simple recipe or parameter management where needed
maintenance screens for I/O status and sensor checks
Touchscreen upgrades also provide a chance to remove clutter. Older HMIs often grew over time, with extra buttons and messages added wherever space was available. A replacement screen can group functions more clearly.
The HMI should still respect the way the machine is used. If operators rely on a particular manual sequence or alarm wording, changing it without consultation can create confusion. Keep what works. Improve what slows people down.
A practical upgrade workflow
A clean upgrade process reduces downtime and makes the final system easier to support. The exact steps vary by machine, but the workflow below suits many Mitsubishi control replacement projects.
Start with a control audit
Record the existing PLC, HMI, I/O modules, networks, drives, sensors, power supplies, and safety circuits. Photograph the cabinet before touching wiring. Save the current program and HMI project if available.
This audit should also note any known faults. If a sensor is unreliable or a cable is damaged, replacing the PLC will not fix that root cause.
Review the original program
Open the program in the correct software where possible. Check comments, device usage, special modules, and instructions. If comments are missing, trace the logic against the machine operation.
For GX Developer projects, confirm whether the program can be reviewed, cleaned up, or migrated as part of the wider job. For GX Works2 projects, check the target PLC settings and instruction usage against the intended Coolmay model documentation.
Match the hardware to the machine
Select the PLC and HMI based on real requirements, not only the current part number. Allow for spare I/O where useful, but avoid unnecessary complexity.
Check power supply capacity, panel space, terminal layout, cable access, and environmental conditions. Heat, dust, vibration, and washdown areas all affect hardware life.
Build and test off the machine
Bench testing saves time during a shutdown. Load the program, set up the HMI, simulate inputs, check outputs, test alarm screens, and verify data registers.
Where practical, create a small test rig with switches, indicator lamps, analogue simulation, and communication devices. This catches many errors before site work begins.
Plan the changeover
A changeover plan should include wiring drawings, terminal references, backup files, labelled parts, rollback options, and commissioning checks. Arrange the shutdown window around machine availability, not just labour availability.
For sites that run long shifts or weekend production, this planning can be the difference between a controlled upgrade and a stressful restart.
Commission with operators and maintenance staff
Commissioning should test the machine in real operating conditions. Check manual mode, auto mode, alarms, interlocks, limits, recipes, and recovery after power loss.
Include the people who run and maintain the machine. They often spot practical issues that do not appear in a program review.
Risks to manage during a Mitsubishi control upgrade
Control upgrades carry risk because they sit close to production. The goal is not to remove every risk on paper. The goal is to find the real ones early.
The most common risks include:
Missing program backups
Unsupported instructions
I/O wiring mismatch
HMI address errors
Unclear safety boundaries
No rollback plan
Create backups before work starts and store the final files safely after commissioning.
Review the logic against the selected controller documentation before installation.
Confirm voltage, sink-source wiring, common terminals, and load type.
Test key buttons, indicators, numeric displays, alarms, and recipes before production use.
Keep safety circuits under proper engineering control and verify them after changes.
Keep the old system, program files, and wiring notes available until the new system is proven.
Safety deserves special attention. A PLC or HMI refresh must not bypass guarding, emergency stops, interlocks, or other protective functions. If the machine safety system needs changes, involve a competent person and follow the relevant Australian standards and site procedures.
Documentation is part of the upgrade, not an afterthought
A control system that works today but cannot be supported later is only half finished. Documentation should be produced or updated during the project, not guessed after the cabinet door is closed.
At minimum, keep:
PLC program backup files
HMI project backup files
final software versions used
PLC and HMI model details
wiring changes and terminal references
I/O list
network settings and communication parameters
password and access control records where site policy allows
commissioning checklist
notes on any program changes made during testing
Clear documentation helps future troubleshooting. It also protects the project team. If a fault appears months later, good records make it easier to see what changed and what did not.
When this path makes sense
ProSight by Coolmay may be a good fit when the machine needs a practical Mitsubishi-style refresh rather than a full controls redesign. It can be especially appealing where documented models support GX Works2 or GX Developer and the existing machine logic is within the capability of the selected hardware.
The best candidates are machines with known operation, available program files, manageable I/O, and clear upgrade goals. The hardest candidates are machines with missing documentation, complex networks, safety uncertainty, or specialised motion.
A sensible approach is to treat the upgrade as an engineering project, not a parts swap. Confirm compatibility, test before installation, protect safety functions, and leave the site with clean backups and clear records.
Done well, the result is a machine that keeps the strengths of the Mitsubishi control approach while gaining fresher PLC and touchscreen HMI hardware for the next stage of its working life.
