Mitsubishi GOT screen design: tags, scripts, and recipes

For Mitsubishi Electric GX Works3 V1.080+.

GOT2000 panels are programmed in GT Designer3. Screen design, tag binding to a GX Works3 project, scripts, and the recipe system. This page is the working engineer's read — what the menu paths actually are in GX Works3 V1.080+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program iQ-R / iQ-F ourselves, daily; we are not a Mitsubishi Electric sales channel.

What this is and when you need it

GOT2000 panels are programmed in GT Designer3. Screen design, tag binding to a GX Works3 project, scripts, and the recipe system. The walkthrough below is the same sequence we use when teaching this on the simulator. Every step names the exact menu path or keystroke; if a name has changed in your version of GX Works3 V1.080+, it is called out. The simulator runs the same logic flow without the licence cost — ladder, FBD, and ST in a browser, with a virtual CPU you can download to.

Walkthrough

1. Create the GOT2000 project

Open GT Designer3 V1.275+ > File > New. Pick GOT type — GT2107 (7"), GT2110 (10"), GT2112 (12"), GT2115 (15"). Set the orientation, the colour depth, and the connection type (Ethernet, CC-Link, serial). Connection > Ethernet > add the controller (iQ-R, iQ-F, Q-series). The Project Tree on the left shows Screens, Scripts, Recipes, Alarms, Comment Group, Tags.

2. Build the device list and tag list

Common Setting > Connection > select 'Mitsubishi PLC' driver and target the iQ-R or iQ-F by IP. Common Setting > Tag > Add. Each GOT tag has a name, a device address (D100, M50, X10), a datatype (Word, Bit, Real, String), and a comment. For a Sysmac-style symbolic workflow, import the GX Works3 label file via Tag > Import — labels become GOT tags with their declared types preserved.

3. Drop a numeric display on a screen

Open Screen 1. Toolbar > Numeric Display. Click on the screen. Properties dialog: Device > pick a tag (e.g. Tank1_Level) or address (D100). Format > pick decimal point position, signed/unsigned, colour-by-range. Repeat for status lamps, button switches, alphanumeric displays. The simulator (Tools > Simulator) renders the screen against a virtual PLC for visual checks before download.

4. Add a script for derived values

Common > Script > New. Pick Project Script (runs on a timer) or Screen Script (runs while a screen is active). The script language is a BASIC-like dialect — IF/THEN, FOR/NEXT, GOTO, plus device-access functions. Use scripts for derived values the PLC doesn't compute (averaging, unit conversion, simple alarm latching).

// GOT script example: convert raw m to mm with rounding
// IF [w:Tank1_Level_Raw] > 0 THEN
//   [w:Tank1_Level_mm] = [w:Tank1_Level_Raw] * 1000
// ELSE
//   [w:Tank1_Level_mm] = 0
// ENDIF

5. Build the recipe system

Common > Recipe > New Recipe. Each recipe maps a list of devices (D100..D109) to a recipe name. The operator selects a recipe at runtime > the GOT writes the recipe values to the PLC devices in one shot. Recipes store on the GOT's internal flash or a CF card. Compile (Build > Compile) and download via Communication > Write to GOT (over Ethernet typically). The runtime starts on completion.

Common mistakes

• Hard-coding raw devices (D100, M50.0) instead of importing GX Works3 labels — every PLC tag rename forces a manual GOT find-and-replace
• Putting too much logic in GOT scripts — the script engine is single-threaded and a slow script blocks screen updates, making the panel feel frozen
• Setting the recipe write to a single transaction across 200 devices — the PLC scan stalls during the write and any safety logic on the same scan window is delayed
• Forgetting to reserve sufficient internal flash for recipe and alarm history — at default settings the GOT runs out of space at around 1000 alarm entries and silently overwrites the oldest

Each of these mistakes shows up in real projects every week. The simulator catches the first three at compile time; the fourth one only surfaces on hardware, which is why we recommend running the cert packs against a real CPU once you have completed the curriculum modules.

How this fits the broader curriculum

Mitsubishi GOT screen design: tags, scripts, and recipes is one of the building blocks. The full Mitsubishi Electric curriculum on the simulator covers: programming-language fundamentals (ladder, FBD, ST), tag and variable scope, HMI tag binding, comms setup (Profinet / EtherNet/IP / Modbus depending on the platform), and the brownfield troubleshooting pathway. Each is its own module with worked examples and a portfolio piece. The cert packs at the Pro tier align to the ISA CCST exam content outline. Reference: isa.org.

For the platform-pick decision — when Mitsubishi Electric is the right call versus a different brand — see the brand hub. For region-specific context on where Mitsubishi Electric dominates the SA install base, see the relevant city pages under /brands/mitsubishi/training-in-* and the sector pages under /industries.

Where this sits in a working week

A technician who has finished this module typically spends the next three to four working days running the same logic flow on hardware. The simulator's value is the dry run — getting the keystrokes and the IDE conventions into muscle memory before you sit down with a live CPU. The first time you build this on hardware, expect the IO mapping and the addressing conventions to slow you down for a session or two; the simulator's project tree mirrors the same shape so the transition is short.

The full Mitsubishi Electric curriculum runs roughly 60 to 100 hours of focused practice. That breaks into bit logic and timers in the first 20 hours, FBs and structured data in the next 20, comms and HMI in the next 20, and a portfolio piece in the last block. Pace yourself — three or four hours per session, four sessions a week, and you finish in eight weeks. Most of our learners report that the bottleneck is not understanding the IDE, it is building reflex around the conventions: where Mitsubishi Electric expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Mitsubishi Electric's own documentation is the canonical reference once you are working on real hardware: Mitsubishi Electric Factory Automation Support. The simulator covers the basics; the vendor docs cover everything specific to a hardware revision, a firmware update, or a CPU-specific quirk. Bookmark both. The IEC 61131-3 standard that governs all the Mitsubishi Electric programming languages is at iec.ch.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The walkthrough above is brand-specific because Mitsubishi Electric's tooling has its own conventions; do not assume the same menu paths exist in another brand's IDE.

How to start

You can be running mitsubishi got screen design: tags, scripts, and recipes in the simulator in 5 minutes. Free tier covers the basics, no card, no install. Once you are 20 minutes in you will know whether the platform fits how you learn. The full Mitsubishi Electric curriculum is the Basic tier (USD 12 / month). The cert packs and portfolio export sit in the Pro tier (USD 29 / month). For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.

Honest expectations on the local job market

Petrochem, mining, FMCG, automotive, and water-utility sectors all carry Mitsubishi Electric install bases somewhere in their stack. Knowing the IDE conventions on this page does not get you a job by itself; it gets you past the first technical screen. The portfolio piece — a working program you built yourself, with a wiring track, a tag list, an HMI screen, and a short README explaining the design choices — is what lands the second interview. The simulator's portfolio export bundles all of that into a single folder you can hand a hiring engineer. Recruiters in this space skim the README first; if your design choices are coherent, they read the code.

Load-shedding has reshaped what gets built first in Mitsubishi Electric programs across SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — now belong in the same module as the basics. Mitsubishi GOT screen design: tags, scripts, and recipes fits into that shape: every line of code you write needs to consider what state the controller is in when it powers up after a 2.5-hour cut, not just what state it is in when running. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware.