Skip to content

OMRON Sysmac

On this page

AnyAutomation Studio helps you write programs for OMRON NJ, NX and NY controllers. Describe in the chat what a program should do, and the AI writes it in Structured Text or ladder logic as an IEC 61131-10 XML file, the exchange format that Sysmac Studio imports. Studio checks every such file against the rules of the Sysmac Studio import and against the instructions and system variables of your controller, shows the findings at the matching lines and lists the steps to bring the file into Sysmac Studio. With Sysmac Studio on the same computer, Studio can also import the files, build the controller and show the build results for you, each step after your confirmation. The download to the controller stays in Sysmac Studio, where you are in control of it.

Requirements

  • A Pro+ plan or higher. OMRON Sysmac is available on Pro+ and Enterprise and is unlocked in the free trial. On the free tier and the Basic and Pro plans, its commands and its side bar do not appear.
  • Sysmac Studio, for the import. You import the files into your own Sysmac Studio. Studio works without it on the same computer: you write and check the files and copy them to the computer with Sysmac Studio. With Sysmac Studio installed on the same computer, Studio also checks every file against the import schema of your installation and can control Sysmac Studio for the import and the build. For that, Studio runs without administrator rights (see Administrator Rights).
  • A controller version that supports the import. The IEC 61131-10 XML import needs unit version 1.19 or later on NJ, NX701, NX1P and NY controllers, 1.31 or later on NX102 and 1.60 or later on NX502.

Where OMRON Sysmac Appears

OMRON Sysmac stays out of the way in TIA and CODESYS work. Its side bar is always there, so you can connect to a Sysmac Studio project even in an empty window. Its entry in the status bar and its menu entries appear once your workspace has a reason for them: a controller is selected, an export folder is selected, the workspace contains an IEC 61131-10 XML file, such a file is open in the editor, or a Sysmac Studio project is open. OMRON: Select Sysmac Target, OMRON: Select Sysmac Export Folder and OMRON: Connect are always available in the Command Palette (Ctrl+Shift+P), so you can start in an empty folder.

Selecting the Controller

The controller decides which instructions and system variables a program may use, so select it first:

  1. Open the Command Palette and run OMRON: Select Sysmac Target, or click the OMRON entry in the status bar (bottom left).
  2. Pick the CPU family: NJ, NX701, NX1P, NX102, NX502 or NY. The current family is marked.
  3. Enter the unit version of your controller, for example 1.40.
  4. Optionally enter the controller model, for example NJ501-1500. Leave it empty to set only the family.

Press Escape in any step to keep the previous selection. The status bar then shows the controller, for example OMRON: NJ501-1500 1.40, or OMRON: No Target while none is selected. The selection is saved with the workspace; to change it, select a new one. A file that names its own controller is checked for that controller.

Writing Programs with the AI

Ask the AI in the chat for the program you need, for example "Write a conveyor program for the NJ501 with start, stop and a fault message, the motor output in ladder logic". The AI hands the task to a dedicated Sysmac Structured Text specialist. It writes in the Sysmac dialect for NJ, NX and NY controllers, follows the naming rules of Sysmac Studio and uses only instructions your controller offers.

Before the AI creates or replaces a file, a confirmation card shows the file name and the number of data types, global variables and POUs, and lists the programs, functions and function blocks with their language (with more than 20, the first 20 and the number of the others). After writing, the AI checks the file and corrects its findings until the file has no errors.

Checking a File for the Import

Studio checks an IEC 61131-10 XML file as soon as you open it, while you change it and when you save it. The findings appear in the Problems view under Sysmac Check, each with its rule number, and as wavy lines in the editor. They cover, among others:

  • names that Sysmac Studio rejects, such as names that start with an underscore or that are reserved for an instruction,
  • names that are declared twice and variables that are used but never declared,
  • instructions, function blocks and system variables that your controller or its unit version does not offer, with the version that would offer them,
  • connections in ladder logic that lead nowhere, and Structured Text that does not follow the Sysmac dialect.

To check on demand, right-click the file in the editor or in the Explorer and choose Check for Sysmac Import. A message tells you the number of errors and hints, and Show Problems opens the list. Select several files in the Explorer to check them together. The findings stay in the list even when the file is not open in an editor, until the file is checked without findings or deleted; when the file changes on disk, Studio checks it again.

Errors block the import and must be fixed; hints are worth a look but do not block it. Ask the AI to fix the findings, or change the file yourself.

Reading a File as Structured Text

Choose Open as ST View in the editor title bar or in the right-click menu of the file. A read-only tab shows the whole file as Structured Text: data types, global variables and every program, function and function block with its declaration and code. Ladder logic appears as equivalent Structured Text, with series contacts as AND, parallel branches as OR and coils as assignments, so you can follow the logic line by line. The findings of the check are marked at the matching lines; hover over a mark for the message.

The view follows every change of the file, also before you save it. To change the program, ask the AI or choose Open as XML to return to the file.

Reading a Sysmac Studio Project

You can read an existing Sysmac Studio project in Studio, without Sysmac Studio and without exporting it first. Click Connect in the OMRON Sysmac view of the OMRON Sysmac side bar, or run OMRON: Connect from the Command Palette. A list shows the projects that Sysmac Studio keeps on this computer, the same ones as on its start page, newest first, each with its name, the date of the last change, the author and the controller. A project that is open in Sysmac Studio at the moment is marked Open in Sysmac Studio. A project protected with a password carries a lock and cannot be opened. Choose a project to open it. For a project file from elsewhere, choose Browse for .smc2 File... at the end of the list and select the .smc2 file; a project that was unpacked into a folder opens through its index file (.oem). Studio only reads the project and never changes it.

The view lists every controller of the project with its model and unit version, and below it the tasks with their programs, the programs, function blocks and functions, the data types and the global variables. Click a program, a function block, a function, Data Types or Global Variables to open it as read-only Structured Text, in the same form as the ST view of a file: the declaration and the code, with ladder logic as equivalent Structured Text. When the project changes on disk, the view and the open tabs read it again; Refresh in the title bar of the view reads it on demand and Close Project closes it. Parts of the project that cannot be shown are listed under Warnings. Type in the tree to jump to a matching entry, or press Ctrl+Alt+F to filter it by name. The checkboxes in front of the programs, function blocks, functions, data types and global variables select them for Export Selected (see Exporting a Sysmac Studio Project).

Parallel branches appear in the order of the drawing, from top to bottom. Where the result of a rung can depend on the order in which its parallel branches run, the Structured Text marks the rung with a note. Check such a rung in Sysmac Studio, because the order shown is not necessarily the order of the controller. Programs that are protected in Sysmac Studio appear without their code. The comments the view adds, such as the titles of sections and rungs, are in English.

Import / Export

The Import / Export view, below the project in the OMRON Sysmac side bar, works with your export folder, the folder that holds the Sysmac files of your machine. Click the title of the view to expand it. It has four buttons: Export Selected and Export All on the left (see Exporting a Sysmac Studio Project), and Import Selected and Import All on the right. Below them, Export Format shows IEC 61131-10 XML (.xml), and Export Folder shows the folder with a button to choose it. You can also choose the folder with OMRON: Select Sysmac Export Folder, or set it in the settings: open the All Settings link below the category list, search for OMRON and enter the full path under Export Folder. The folder applies to all workspaces; the settings of a workspace cannot set it. The AI may read and write the files in this folder as well, each write after your confirmation.

The tree shows the folders and XML files with a checkbox in front of each. Import Selected checks the files you ticked and imports them through Sysmac Studio or shows their import steps, Import All does the same for every XML file of the folder (see Importing into Sysmac Studio). Click a Sysmac file to open it as Structured Text in a preview, double-click to keep the tab open, or drag it into the editor or into the chat. The right-click menu opens a file as Structured Text or XML, with Open XML to the Side also beside the current editor, checks it, shows its import steps, reveals it in File Explorer and offers New Folder..., Rename..., Delete, Cut, Copy, Paste and Copy Path. A check on a folder checks every file below it. In the title bar of the view, Filter Export Folder filters the tree by name, Refresh Export Folder reads the folder again and Reveal in File Explorer shows the folder.

Exporting a Sysmac Studio Project

With a project connected in the OMRON Sysmac view, Studio writes its programs, function blocks, functions, data types and global variables as IEC 61131-10 XML files into the export folder, ready for the import into another Sysmac Studio project.

  1. Tick the elements you want in the project tree and click Export Selected in the Import / Export view, or click Export All for the whole project. Both are also in the right-click menu of the project tree.
  2. If no export folder is selected yet, the folder dialog opens first.
  3. A notification shows Exporting Sysmac elements... while the export runs. Cancel stops the export; the files written up to then stay in the folder.

Each program, function block and function gets a file of its own, for example Program_Main.xml or FunctionBlock_FB_Motor.xml; the data types go into DataTypes.xml and the global variables into GlobalVariables.xml. An element in a namespace carries the namespace in its file name, and in a project with several controllers every file name starts with the name of the controller. Files of the same name in the export folder are replaced without asking, other files stay. A file that is open in the editor with unsaved changes is skipped.

Before Studio writes a file, it checks it together with the other files of the export, with the same check as for the import. A file with errors is not written, and neither is any file that uses it. If Sysmac Studio is not installed on this computer, the files are checked against the rules only, and the message says that they were not checked against the schema of Sysmac Studio.

When the export is done, a message tells you how many files were written and how many elements were skipped. Show Report opens the Sysmac Export Report, and Import Steps opens the import steps of the written files in the order of the import. The report lists the import order, every exported element with its file, every skipped element with the reason, and notes for the work in Sysmac Studio: the programs to assign to their tasks, the libraries to add to the target project before the import, the device addresses of variables, and elements that your selection uses but that you did not tick. Studio does not add such elements on its own; tick them, or use Export All. To open the report of the last export again, run OMRON: Show Sysmac Export Report from the Command Palette or choose Show Export Report in the right-click menu of the project tree.

Import the files into a new Sysmac Studio project, in the order of the report. Importing them into the project they came from replaces its elements.

Importing into Sysmac Studio

With Sysmac Studio on this computer, Import Selected and Import All in the Import / Export view import the files through Sysmac Studio (see Controlling Sysmac Studio from Studio). Without it, or to do the import by hand, they show the import steps; you can also right-click a file in the export folder, in the Explorer or in the editor and choose Show Sysmac Import Steps. The import steps open in an editor tab named Sysmac Import Steps: for up to four files one tab per file, for five files or more one tab that lists all of them, each with its result. Each file is checked first. If a file still has errors, the tab lists their number with Show Problems and shows the steps once the errors are fixed. For a file without errors it lists the steps, with the menu names in the display language of the Sysmac Studio installed on this computer (in English when Sysmac Studio is not installed). The menus below are those of the English user interface:

  1. Create the project. Create a standard project in Sysmac Studio for your controller and its version.
  2. Import the file. Choose Tools > IEC 61131-10 XML > Import, select the file and click Execute. The tab shows the path of the file with a button to copy it.
  3. Assign the programs to the task. The file carries no task assignment, so add the listed programs to the PrimaryTask in the task settings of the project.
  4. Build the controller. Choose Project > Build Controller; the Build window should show no errors.
  5. Test in the simulator or download. Start the simulator, or go online with your controller and transfer the project to it. Check the imported code before you use it on the machine.

If the selected unit version is below the version the import needs, the tab tells you so instead. Check Again in the title bar of the tab repeats the check, and the tab updates itself when a file changes. One run shows up to 500 files; tick fewer files to see the others.

Starting Sysmac Studio

Click Open Sysmac Studio in a Sysmac Import Steps tab, or run OMRON: Open Sysmac Studio from the Command Palette, to start the Sysmac Studio installed on this computer. Studio starts it without administrator rights, in the same way as OMRON: Start Sysmac Studio, so that Studio can control it afterwards. If Sysmac Studio is not installed here, the button is disabled and the tab reminds you to copy the file to the computer with Sysmac Studio.

Controlling Sysmac Studio from Studio

With Sysmac Studio installed on the same computer, Studio can do the import work in Sysmac Studio for you: start Sysmac Studio, create or open the project, import the files, save the project, build the controller and bring the build results into the Problems view. You watch every step in the Sysmac Studio window. Studio can also run the project in the simulator of Sysmac Studio (see Testing in the Simulator). Downloading to a controller and going online stay with you.

Starting and Attaching

Run OMRON: Start Sysmac Studio from the Command Palette, or click its play button in the title of the OMRON Sysmac side bar, to start Sysmac Studio in a way Studio can control. As soon as you use Sysmac Studio from Studio, or it runs while the OMRON Sysmac side bar is open, the status bar shows Sysmac Studio on the right; click it for the actions. While you do not use Sysmac Studio, the entry stays hidden. If Sysmac Studio is already running, run OMRON: Attach to Sysmac Studio and choose the window from the list. Windows that Studio cannot control are listed with the reason, for example a Sysmac Studio that runs with administrator rights. Once attached, the status bar shows the project and the controller; hover over it for the version and language of Sysmac Studio. OMRON: Detach from Sysmac Studio ends the control and leaves Sysmac Studio running as it is.

Studio checks the signature of Sysmac Studio before it starts it. Studio controls only a Sysmac Studio that runs in your Windows session, for your user and without administrator rights. A version of Sysmac Studio that has not been checked with Studio yet still works when Studio finds what it needs; the status, the confirmation and every AI answer then say so.

Administrator Rights

Studio starts Sysmac Studio without administrator rights, so that it can control it, and Sysmac Studio does not ask for them at the start. Studio cannot control a Sysmac Studio that runs with administrator rights. If you started Sysmac Studio as administrator yourself, close it and start it from Studio. If Studio itself runs with administrator rights, it does not start Sysmac Studio at all; start Studio as a normal user. If Sysmac Studio asks for administrator rights during a step, Studio stops and tells you so.

Choosing the Target and the Backup

Click Import Selected or Import All in the Import / Export view, or run OMRON: Import into Sysmac Studio.... Studio first checks every file. If some files have errors, a dialog lists them with their errors; tick the line Also import the files with errors (it names their number) when you want Sysmac Studio itself to show what it does not accept when it builds the controller. Without the tick Studio imports only the files without errors and names the others in the confirmation. If no file can be imported, the import steps open so you can fix the files. Then choose where the files go:

  • New Project (recommended): Studio creates a new project for the controller of your Sysmac target. Enter the name of the project; a controller model must be selected in the target.
  • Project Open in Sysmac Studio: the project that is open in the attached Sysmac Studio.
  • Project from the Sysmac Studio Project List...: one of the projects Sysmac Studio keeps on this computer.

Before anything goes into an existing project, Sysmac Studio saves it and Studio copies the whole project to a backup folder in your user profile. Studio checks the copy file by file; if the copy cannot be made or checked, nothing is imported. A new project created by the same import needs no backup. OMRON: Open Backup Folder shows the backup of the last import.

The Confirmation

Before Studio changes anything, a dialog lists what will happen: the files, the project and controller, the backup line for an existing project, and the programs, function blocks and functions that are replaced. Sysmac Studio replaces such elements without asking, so check this list. Global variables and data types that differ from the project stop the import, and nothing of them is overwritten. To overwrite them, tick Overwrite differences in global variables and data types (not yet verified); it is off every time. The dialog also says that Sysmac Studio saves the project before each file, that Studio builds the controller afterwards, and which programs you add to their tasks by hand.

Progress and Cancel

While Studio works, the status bar on the left shows the step with a counter, and the Sysmac Import Steps tab shows each step and each file with its result. Do not click or type in Sysmac Studio until the operation ends. If Sysmac Studio shows a dialog Studio does not know, Studio stops, leaves the dialog open and tells you its title and text; answer it in Sysmac Studio and run the step again.

Click Cancel in the notification or in the tab, or click the entry in the status bar, to stop. Sysmac Studio cannot stop a file once its import has started, so Studio finishes that file and stops after it. A rebuild cannot be stopped once it has started, and neither can a program check; Studio waits for its result. If a message about a finished import or a compare window from an earlier run is still open in Sysmac Studio, Studio closes it before the next step; closing the compare window overwrites nothing. After a cancel Studio saves nothing; the project may then hold part of the files, and for an existing project the backup from before the import is in the backup folder. The OMRON Sysmac output channel lists every step with its time and result.

Build Results in Problems

After the import Studio saves the project, builds the controller and shows the result, for example "Sysmac Studio build: 4 errors, 0 warnings.", with Show Problems. The rows appear in the Problems view under Sysmac Build, at the matching file and line in the export folder where Studio can tell, otherwise at the file. OMRON: Build Sysmac Controller, OMRON: Rebuild Sysmac Controller and OMRON: Check All Programs run on demand; the program check reports more warnings than a build and appears under Sysmac Program Check. OMRON: Read Build Results reads the rows again. Where Sysmac Studio does not show whether a row is an error or a warning, it appears as a warning marked "Severity unknown"; the counts of Sysmac Studio stay the numbers that count.

Adding the Programs to Their Tasks

The import files carry no task assignment, and Studio does not change task settings in Sysmac Studio. After the import, the Tasks section of the Sysmac Import Steps tab lists each program with its task:

  1. In Sysmac Studio, open Task Settings in the Multiview Explorer, then Program Assignment Settings.
  2. Add each listed program to its task with Add Program. Copy Task List copies the list as text.
  3. Save the project in Sysmac Studio.
  4. Click Check Tasks Again. Studio reads the saved project and marks each row Assigned, To do or In task with the other task, and says for example "20 of 20 programs are assigned."

Right after the import every row says To do; that is expected. Programs that are not assigned to a task are still built, so the build result does not depend on this step.

Fixing and Importing Again

Fix the findings in the XML files, yourself or through the AI, and import the changed files again into the same project. Studio takes a new backup first, lists the elements that are replaced, imports, builds and shows the new results. Repeat until the build has no errors.

Restoring a Backup

Studio never writes into the project folders of Sysmac Studio, so it does not restore a backup itself. To go back to the state before an import:

  1. In Sysmac Studio, close the project, or close Sysmac Studio.
  2. Run OMRON: Open Backup Folder, or open the backup folder of that import. Its name starts with the project name and the time of the backup. The file backup.json in it names the original project folder.
  3. Replace the content of the original project folder with the files of the backup.
  4. Open the project in Sysmac Studio again.

What Studio Never Does in Sysmac Studio

Studio does not download to a controller, go online with a controller, change the operating mode of a controller, create, change or move tasks, change options or security settings, delete projects, or close a project or Sysmac Studio. It does not send keystrokes or mouse clicks to Sysmac Studio and never answers a dialog it does not know. It never writes into the project folders of Sysmac Studio; it only reads them, for the backup, the task check and the read-back after the import. In the simulator it uses only the commands of the Simulation menu of Sysmac Studio.

Testing in the Simulator

With a project open in the attached Sysmac Studio, Studio can run it in the simulator of Sysmac Studio, so you can test a program right after the import without a controller. Studio works only with the simulator. If Sysmac Studio is online with a real controller, Studio refuses every simulator step and says so.

Starting, Pausing and Stopping

  1. Build the controller without errors first, for example with the import or with OMRON: Build Sysmac Controller.
  2. Run OMRON: Start Simulation from the Command Palette, or click Start Simulation in the Sysmac Import Steps tab after the import. To start with the controller in PROGRAM mode, run OMRON: Start Simulation in PROGRAM Mode.
  3. Confirm the dialog. It names the project and the controller and the command Studio chooses in Sysmac Studio.

The status bar then shows Simulator running next to Sysmac Studio. OMRON: Pause Simulation pauses the simulator and the status bar shows Simulator paused; OMRON: Start Simulation continues it. OMRON: Stop Simulation stops it. OMRON: Show Simulator State reads the current state from Sysmac Studio, for example after you started or stopped the simulator in Sysmac Studio yourself. You find the same commands in the ... menu of the OMRON Sysmac and Import / Export views and in the menu that opens when you click Sysmac Studio in the status bar.

You can cancel a start only until Sysmac Studio starts the simulator; after that the start runs to its end and Studio reports the state it finds. Pausing and stopping always run to their end. Studio never stops or restarts the simulator on its own. If Sysmac Studio closes while the simulator runs, Studio says so and names the two log files of Sysmac Studio that help to find the reason.

If Sysmac Studio shows a dialog while the simulator starts, Studio leaves it open and stops; answer it in Sysmac Studio.

While the Simulator Runs

Sysmac Studio does not build a controller while its simulator runs, so Studio does not import, build, rebuild or check the programs then. It tells you right away to stop the simulator with Stop Simulation and changes nothing. Start the simulator again after the import.

Watching and Writing Values over OPC UA

The simulator of Sysmac Studio offers an OPC UA server for the values of the running program. You start it in Sysmac Studio and connect to it in Studio like to any OPC UA controller:

  1. With the simulator running, choose Simulation > Use the OPC UA Server for the simulator in Sysmac Studio.
  2. Tick the variables you want to watch, then go on to the endpoint settings.
  3. Set the endpoint to 127.0.0.1 with a free port, for example 127.0.0.1:4841, and click Start using the OPC UA Server. The proposed port 4840 is often taken by another OPC UA program on the computer; if Sysmac Studio says that the port is used by another application, choose another port such as 4841.
  4. In Studio, open the PLC / OPC UA editor and connect to the endpoint, for example opc.tcp://127.0.0.1:4841 (see OPC UA). The server of the simulator accepts only the security modes Sign and SignAndEncrypt with a user name, so choose such an endpoint and sign in with Username/Password. On the first connect Studio asks whether to trust the certificate of the server; choose Trust Server Certificate.

In the PLC / OPC UA editor you browse the variables you ticked, watch them in a watch table and write new values, like on any OPC UA controller. Only the variables you ticked in step 2 are visible; to add more, change the selection in Sysmac Studio. You can close the window of the OPC UA server in Sysmac Studio, the server keeps running.

While the OPC UA server runs, Sysmac Studio does not offer Run, Pause and Stop in its Simulation menu, so Studio cannot pause or stop the simulator either and tells you so. Stop the OPC UA server in Sysmac Studio first.

Comparing a Project with a Folder

Studio compares the connected Sysmac Studio project with a folder of IEC 61131-10 XML files, or two such files with each other. Both sides are shown as Structured Text, ladder logic included, so you see what changed in the program and not in the XML. Layout changes in a ladder diagram do not count as a change. Sysmac Studio does not have to be installed for this, and the comparison changes nothing.

Project and Folder

  1. Connect to a project in the OMRON Sysmac side bar.
  2. Click Compare with Export Folder in the title bar of the Import / Export view, or run it from the Command Palette or the right-click menu of the project tree. Studio compares with the export folder; without an export folder it asks for the folder to compare with.
  3. The Compare view opens in the OMRON Sysmac side bar. Its first line sums up the result, for example how many elements changed, and the elements are grouped as Changed, Only in Project, Only in Folder, Not Compared and Equal.

Double-click an element to open the project and the folder side by side as Structured Text; both sides are read-only. Elements under Not Compared carry the reason, for example a part that the Structured Text view does not show. Compare Again repeats the comparison, for example after you changed a file, and Close Comparison closes the view. A comparison you start can be cancelled in its notification.

To take the folder state into the project, import the changed files with Import Selected as usual, with the backup of the project first.

Two Files

Select two Sysmac XML files in the Explorer, right-click one of them and choose Compare as ST. Both files open side by side as Structured Text, and the comparison follows later changes of either file. You find Compare as ST also in the right-click menu of a file in the Import / Export view and in the Command Palette, where Studio asks for the two files.

Working with the AI

Besides writing programs, you can ask the AI to:

  • Show the status: the selected controller and whether Sysmac Studio is installed on this computer, with its version.
  • Select the controller: from a model name such as NJ501-1500 or from a family, together with the unit version.
  • Look up an instruction: its variants, parameters and the unit versions in which it is available on your controller.
  • Check a file: the AI reads the findings and corrects the file it has written.
  • Read a file as Structured Text: to explain a ladder program or to answer questions about it.
  • List the Sysmac Studio projects: the projects that Sysmac Studio keeps on this computer, the same list as Connect.
  • Open a Sysmac Studio project: one of these projects by its name, or a project file you name, in the OMRON Sysmac view.
  • Read a Sysmac Studio project: first its structure, then single programs, the data types or the global variables as Structured Text, from the project open in the OMRON Sysmac view or from a project file you name.
  • Export the project: the whole connected project or the elements you name, into the export folder, after you confirm it. The confirmation names the project, the folder and the elements. If you connect another project or choose another export folder before you confirm, nothing is written and the AI asks again. While the export runs, a notification shows its progress, and Cancel stops it. The AI then shows the import steps of the written files and tells you what was skipped.
  • List the export folder: the AI tells you which files it holds and which of them are Sysmac files.
  • Select the export folder: the folder dialog opens and you choose the folder yourself.
  • Manage files in the export folder: create a folder, rename, copy, move or delete, always inside this folder. A delete asks once more, as in the right-click menu.
  • Show the import steps: for one or several files, the same steps as the Sysmac Import Steps tabs, and on request in these tabs.
  • Start Sysmac Studio: after you confirm it, without administrator rights so that Studio can control it.
  • Attach to Sysmac Studio: list the running Sysmac Studio windows and attach to one of them, after you confirm it.
  • Create or open a project in Sysmac Studio and save it: each after you confirm it.
  • Import into Sysmac Studio: the files you name or all files of the export folder, into a new project or an existing one. The confirmation is the same as in the import dialog, with the backup and the list of replaced elements. If global variables or data types differ, the AI stops and asks you before it tries again with overwriting, which needs a confirmation of its own.
  • Build the controller and read the results: build and rebuild after you confirm them, the program check and the results without a prompt. The AI reads the rows with their file and line and can fix the files and import them again.
  • List the task assignment and check it: the AI shows which program goes into which task and checks the saved project after you added them. It never changes task settings itself.
  • Run the simulator: start it, also in PROGRAM mode, pause it and stop it, each after you confirm it, and read its state without a prompt.
  • Watch and write values in the simulator: after you started the OPC UA server in Sysmac Studio and connected to it in the PLC / OPC UA editor, the AI uses that connection, reads and browses the variables and writes new values. Before each write it shows the variable, the value and the connection it writes to, and waits for your confirmation. If you are not connected yet, the AI asks you to connect first.
  • Compare: the connected project with the export folder, or two XML files as Structured Text, and report what differs.

Writing a file, exporting the project, selecting and managing the export folder, and every step that starts or changes something in Sysmac Studio ask for your confirmation. If Sysmac Studio, its project or its controller changes after you confirmed, nothing happens and the AI asks again. Stopping the AI also stops the running step where Sysmac Studio allows it. Reading or opening a project file that lies outside your workspace and the export folder asks as well. Other reading, checking, looking up and setting the controller run without a prompt. Allow an action once, for the session, or for good, or switch its tool off in the chat tool picker.

What Is Not Supported Yet

  • Downloading and going online with a real controller from Studio. These steps stay in Sysmac Studio. The simulator is supported (see Testing in the Simulator).
  • Debugging in the simulator and setting values in Sysmac Studio. Step execution, breakpoints, the simulation speed and setting values in the watch window of Sysmac Studio stay in Sysmac Studio; in Studio you watch and write values over OPC UA. Choosing the variables of the OPC UA server and starting it is a step you do in Sysmac Studio, and you connect to it yourself in the PLC / OPC UA editor.
  • Taking a folder over from the comparison. The Compare view only shows differences; bring changed files into the project with the import.
  • Several controllers in one project and checking selected programs. The import and the build work on a project with one controller; Sysmac Studio's check of selected programs is not offered.
  • Exporting libraries, device addresses and task assignments. The export writes the programs, function blocks, functions, data types and global variables of the project. Add the libraries to the target project, set the device addresses and assign the programs to their tasks in Sysmac Studio; the export report lists all of them.
  • Exporting every kind of element. Protected code, function block diagrams and some forms of ladder logic are not exported yet, among them forms that Sysmac Studio refuses when it builds the project. They are skipped, and the export report names each of them with the reason. A rung without an instruction, such as a rung with only a comment, is left out, and the report names it. Debug programs are exported as debug programs; the export report lists them with the programs of their task, as in the source project.
  • Changing a Sysmac Studio project directly. Studio never writes into project files. A change goes through an IEC 61131-10 XML file and its import in Sysmac Studio, by hand or by Studio.
  • Older and other project formats. Ladder logic in an older format (before version 1.13) and function block diagrams are not shown; the view names such parts under Warnings. Projects in the older .smc format and projects protected with a password do not open.
  • Taking over changes from Sysmac Studio. After the import the project in Sysmac Studio is the master; changes made there do not come back into the file.
  • Editing in the Structured Text view. The view is read-only; change the program in the XML file or through the AI.
  • Task assignment by Studio. Assign the programs to their tasks in Sysmac Studio after the import; Studio lists them and checks the result (see Adding the Programs to Their Tasks).

Notes

  • Emergency stop and motor protection belong in a safety controller or a hard-wired circuit, never only in standard code.
  • The check runs on your computer and needs no connection to a controller and no running Sysmac Studio.
  • The import steps name the menus in the display language of the installed Sysmac Studio. Without Sysmac Studio on this computer they name the menus of its English user interface; in another display language look for the same commands at the same place.