Omron NS vs NA HMIs: legacy vs current Sysmac integration

For Omron Sysmac Studio V1.50+.

NS is the legacy Omron HMI line driven by NS-Designer; NA is the current Sysmac-integrated HMI. The bind workflow and the migration path. This page is the working engineer's read — what the menu paths actually are in Sysmac Studio V1.50+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program NX / NJ series ourselves, daily; we are not a Omron sales channel.

What this is and when you need it

NS is the legacy Omron HMI line driven by NS-Designer; NA is the current Sysmac-integrated HMI. The bind workflow and the migration path. 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 Sysmac Studio V1.50+, 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. Understand which line you have

NS5/NS8/NS10/NS12/NS15 are Omron's legacy HMI line, programmed in NS-Designer (a standalone tool, not part of Sysmac Studio). They communicate to CJ/CS/CP1 controllers via Host Link, FINS, or Ethernet/IP. NA5-7W/9W/12W/15W are the current Sysmac-integrated HMIs — programmed inside Sysmac Studio as part of the same project as the NJ/NX controller. NA panels run a webkit-style HTML-rendered runtime.

2. NS workflow: tag bind via NS-Designer

Open NS-Designer > new project > target NS panel model. Add a Communication Setting > select FINS Ethernet > target controller IP. Create a Symbol Table — manually import or hand-type each PLC tag with its address (DM100, W50.0, CIO 100). Drop a numeric display on a screen > Set Address > pick the symbol. Compile (F7) > Transfer (over USB or Ethernet).

3. NA workflow: tag bind inside Sysmac

In Sysmac Studio, the project tree has a section for the NJ/NX controller and a section for the NA HMI. Add Device > NA HMI > pick model. The HMI's Variables list shares the same global variable scope as the controller — no manual symbol table, no explicit Communication Setting. Drop a Numeric Display on an HMI screen > Variable Mapping > pick from the global variable list. Build > Transfer to NA panel.

// Sysmac variable mapping (NA HMI)
// HMI Variable: hmi_Tank1_Level
// PLC Variable: Tank1.Level (REAL, global)
// Update rate: 100 ms
// Direction: Read

4. Decide on migration NS to NA

NS panels are still supported but in mature lifecycle. New SA panel builds rarely spec NS unless replicating an existing fleet. NA migration: there is no automated NS-Designer to Sysmac Studio converter — the project is rebuilt by hand. The screen designs port via screenshot reference, the variable bindings change from manual symbols to Sysmac global variables. Plan two to four engineering days per medium NS project.

5. Test the runtime

Sysmac Studio NA Simulator: HMI > Simulator > Start. The NA runtime opens in a window on the engineering PC, against the simulated controller. Screens render exactly as on the panel, variables update from the simulated controller. Catch screen-layout issues, tag-binding errors, and update-rate stutters here. NS-Designer has no equivalent simulator — NS testing requires hardware on the bench.

Common mistakes

• Speccing an NS panel for a new project to save 20% on hardware cost — the toolchain divergence forces NS-Designer alongside Sysmac Studio and engineering effort doubles
• Migrating an NS to an NA assuming the screens auto-port — there is no migration tool, the rebuild is manual and screen layouts often need rework for the higher NA resolution
• Setting the NA update rate to 50 ms across hundreds of variables — the NA runtime CPU runs hot and screen response degrades on heavy screens
• Using FINS Ethernet for the NS to NJ link without realising NJ uses EtherCAT/Sysmac native, not FINS — the bind requires a FINS gateway that adds 20 ms latency

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

Omron NS vs NA HMIs: legacy vs current Sysmac integration is one of the building blocks. The full Omron 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 Omron is the right call versus a different brand — see the brand hub. For region-specific context on where Omron dominates the SA install base, see the relevant city pages under /brands/omron/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 Omron 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 Omron expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Omron's own documentation is the canonical reference once you are working on real hardware: Omron Industrial 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 Omron 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 Omron'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 omron ns vs na hmis: legacy vs current sysmac integration 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 Omron 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 Omron 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 Omron 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. Omron NS vs NA HMIs: legacy vs current Sysmac integration 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.