IMDTouchKnowledge BaseShop main store

Explainer

Which SoMachine version configures an HMISCU controller and HMI

HMI and touchscreens Published 6 min read

Short answer

Configure the HMISCU8B5 with full SoMachine. SoMachine Basic is the free package for the Modicon M221 alone and cannot open an HMISCU combo project. Inside SoMachine, the screens are built in the embedded Vijeo Designer editor and the control program uses the CODESYS-based IEC 61131-3 languages, with no import path from Unity Pro.

On this page
  1. Full SoMachine is the package that opens the HMISCU8B5
  2. The control program is CODESYS-based, not Unity Pro
  3. The screens are Vijeo Designer inside the SoMachine project
  4. One project, two downloads — and the USB pitfall
  5. From HMI entry to analog output: a worked valve example
  6. The decision, case by case
  7. Questions asked

Use full SoMachine, not SoMachine Basic, for the HMISCU8B5. SoMachine Basic is Schneider's free package for the Modicon M221 alone; it has no device support for the HMISCU combo family, so it can neither program the controller nor draw the screens. Full SoMachine answers both halves of the question: the graphics look like Vijeo Designer because the Vijeo Designer editor runs inside it, and the control program is CODESYS-based, with no relation to Unity Pro. Below is the decision for each package, how the two sides of the project fit together, and how a valve command travels from an operator entry to the analog output.

Full SoMachine is the package that opens the HMISCU8B5 #

The two packages share the first word of their names and nothing else. Schneider's FAQ on the difference states the split: SoMachine Basic is free and was created specifically to program the M221 logic controller. There is no HMISCU target in it, so neither the control program nor the screens of the combo can be built there — installing the free package gets you an editor for a controller this machine does not use.

Full SoMachine is the engineering environment for this machine. You create the project, select the HMISCU hardware, and the control application and the HMI application both live in that project. Confirm the installed product name and version before you start — the same software-first discipline as checking HMI engineering software before a panel replacement.

The control program is CODESYS-based, not Unity Pro #

SoMachine is built on CODESYS 3, so the control side of the project has no relation to Unity Pro beyond the shared language names. The languages are the IEC 61131-3 set — the international standard that defines the PLC programming languages and their execution rules — and through the CODESYS-based editor you get ladder diagram, function block diagram, structured text and sequential function chart.

For a Unity Pro user the practical consequence is blunt: no Unity Pro project, data type or function block opens in SoMachine. You rebuild the application with CODESYS objects and carry the logic, the I/O list and the control narrative across. Budget the move as a rewrite, not a conversion.

The screens are Vijeo Designer inside the SoMachine project #

The graphics side resembles Vijeo Designer because it is Vijeo Designer: the full package embeds the graphics editor, and when you add the HMI application to the project you draw the screens in that editor. The integration is the part to respect. Variables are declared in the control application and the screen objects bind to them, so the tag list comes from the controller side of the project rather than from a separate import. A standalone Vijeo Designer project will not open in this integrated editor — the reasons are laid out in why a standalone HMI project will not open in your integrated editor.

The embedded editor also sets the update rule: the base software installs before the service pack, as install the HMI base software before the service pack documents.

One project, two downloads — and the USB pitfall #

The controller application and the HMI application are built in one project but arrive on the target as separate downloads. Schneider's FAQ on the HMISCU and XBTGC combos documents the classic symptom: after a Vijeo Designer project is downloaded to the panel from a USB memory stick, the PLC does not start in RUN. The screens arrived; the control program did not. Download the controller application as well, then confirm both are on the target before you expect the machine to run. A panel that shows its screens while the controller sits idle is a transfer problem first, not a hardware fault.

From HMI entry to analog output: a worked valve example #

The command path has four stages: the operator entry on the screen, the controller variable, the scaling logic, and the physical output channel. Test them in that order so a graphics problem is never mistaken for an analog fault. One safety note: put the channel in the installation's specified safe state and use an approved manual mode before forcing or measuring anything on a live valve.

The example is illustrative: a regulating valve commanded 0–100% of span over a 4–20 mA output. The variables below are declared with their types and initial values the way the CODESYS-based editor expects:

VAR
    OperatorCommand : REAL := 62.5;  // percent, entered on the HMI screen
    LimitedCommand  : REAL := 0.0;
    ValvePercent    : REAL := 0.0;
END_VAR

LimitedCommand := LIMIT(0.0, OperatorCommand, 100.0);
ValvePercent := LimitedCommand;

The scaling from percent to current, with the arithmetic:

4 mA + (62.5 - 0) / (100 - 0) × (20 - 4) mA = 4 mA + 0.625 × 16 mA = 14.0 mA

The test that proves the whole path: enter 62.5% on the screen and read 14.0 mA at the output terminal, within meter tolerance. The step from current to the channel's internal raw value uses the endpoints shown by the channel definition in your project — read them there, because they belong to the configured channel, not to the model number.

Where the path stops tells you where the fault is:

Where it stops What that means Next check
Screen value changes, controller variable does not the screen object is not writing the intended variable variable binding, data type, write access
Controller variable changes, scaled value does not a limit, mode selection or interlock holds the command enable conditions and calculation inputs
Scaled value changes, terminal current does not output mapping or channel configuration mapped object against the configured channel, then measure at the terminal
Terminal current is right, valve does not move the actuator side supply, wiring, signal-type match at the valve input

If the channel is selected in the project but the terminal refuses to move, work the mapping next — see resolving SoMachine HMISCU output I/O mapping issues. When the valve or its position feedback sits on a serial network instead of local I/O, the controller application does the polling with READ_VAR, covered in configuring Modbus RTU on HMISCU8B5 with SoMachine READ_VAR.

The decision, case by case #

What you have Package to use Why
An HMISCU8B5 or another HMISCU or XBTGC combo full SoMachine control program and embedded Vijeo Designer screens in one project
A Modicon M221 (TM221) on its own SoMachine Basic, listed today as Machine Expert Basic the free package dedicated to that one controller family
A Magelis panel with no combo controller standalone Vijeo Designer at the version matching the panel family the panel is the whole target
Unity Pro logic to carry over full SoMachine, rewritten a CODESYS-based project with no Unity Pro import path

For the machine in hand — an HMISCU8B5 driving a regulating valve on an analog output — open full SoMachine, write the control application in the IEC 61131-3 languages, draw the screens in the embedded Vijeo Designer editor, download both applications, and only then command the valve.

Questions asked

SoMachine Basic no longer appears on the download page — was it withdrawn?

It was renamed, not replaced. The same TM221 software line is listed as Machine Expert Basic on current Schneider pages, and it remains the package dedicated to the M221 family. That rename does not change the decision here: Machine Expert Basic, like SoMachine Basic before it, cannot open an HMISCU combo project.

Can I verify the valve command path without stroking the valve?

Yes. Build both applications, put the output in the specified safe state, and watch the path online in the engineering tool: the operator entry updates the controller variable, and the limit and scaling logic produce the scaled value. Those three stages verify with no actuator connected. The final current check, 14.0 mA for the example entry, needs the channel configured and a meter at the terminal.

Does the XBTGC combo use the same SoMachine workflow?

Yes. The HMISCU and XBTGC HMI combo families share the SoMachine workflow: a CODESYS-based control application and an embedded Vijeo Designer HMI, both built in one project. The documented USB pitfall, screens transferred while the controller is left out of RUN, is common to both families, so always download the controller application and the screens together.

Our plant standard is Unity Pro — do I need it on this machine?

No. Nothing on the HMISCU8B5 opens in Unity Pro. Program changes and maintenance happen in full SoMachine, using the CODESYS-based IEC 61131-3 languages. Unity Pro experience helps you read ladder and structured text quickly, but treat this machine as a CODESYS project: no project files, data types or function blocks move between the two environments.

Keep reading

  • Troubleshooting

    Which Vijeo Designer version edits an XBTG5230 project

    Edit an XBTG5230 application with a licensed Vijeo Designer release from 4.5 through V5.0 SP2 — V5.0, all service packs included, is the last line supporting the XBTG series (Schneider Electric FAQ FA280491). Version 4.2.2 cannot load a 4.5 project and releases after V5.0 cannot select the target, so the fix is the release window, not a cable or terminal fault.

    HMI and touchscreens

  • Troubleshooting

    Why Vijeo Designer Basic Router Fields Stay Greyed Out

    Greyed Router IP and Control & Data TCP Port fields in Vijeo Designer Basic 1.1 mean the download-through-a-router function is not exposed for that edition and target pair — the GXU 3512 keeps downloading on the local network. Confirm the edition first: the demo cannot connect to a device at all, and the trial modes run 21 days or 42 days from install.

    HMI and touchscreens

  • How-to

    Open a legacy Vijeo Designer project in version 6.2

    Open the project in the release the error names — Vijeo Designer 4.7 in this case — compile and save it there, then climb release by release until 6.2 opens and builds it. Only then change the target to HMIGTO6310, configure Unitelway, and choose one documented transfer route.

    HMI and touchscreens