Release notes

The docs describe the development build e17990ef of 5 November 2026, which follows version 1.5.0. Its product version is shown under Settings › About; see Which version you are reading.

Development build after 1.5.0

New

Projects and administration

• Licensing uses Capacity Units: 3 CU per power tag, 50 CU per protocol family. Up to 80 CU is free and commercial use is included; above that 1 USD per CU; unlimited at 5,000 CU. See Licence and Capacity Unit.
• The Licence tab shows the status, a calculator and the usage of the server. It downloads the request file, loads the licence without a restart, releases the licence and downloads the usage report.
• Uninstall offers three choices: remove the program only, full clean-up, or back up selected projects and then clean up. See Uninstall YTCC.
• scada-manager db-password changes the database password in one step, and scada-manager migrate --all upgrades the registry and every project. See scada-manager commands.
• config\ui-web.toml opens the interface to other computers on the network. See Ports and network.
• The interface is available in 13 languages. The Help window follows the interface language and says when it falls back to another one. See Application settings.
• Several YTCC versions can be installed side by side, each in its own folder such as v13. A project is taken over into a new version, can be taken back, and the old version is deleted when it is no longer needed. See Upgrade to a new version and roll back.
• A project runs in one version at a time; starting it in a second version is refused. See Start, stop and restart a project.
• A whole project, with its database, files and users, is backed up to one zip file and restored from it. See Backup and restore.
• Projects can be renamed and copied on the home page, and the home page shows which version saved each project.
• Settings › About shows the contract versions of the installation. See Compatibility and contract versions.
• Projects are backed up from the home page with Back up… or the Back up toolbar button, also several at a time, to a download or to a folder on the server; Import… on a project restores its backup. Backups, downloads and imports are written to the audit log of the server account. See Back up a project from the home page.
• The project list marks projects whose database needs a schema upgrade, and Upgrade… upgrades one after a backup. See Upgrade a project from the home page.
• The setup program shows the YTCC installations on the computer, can stop them, upgrades the databases after a backup, and removes old installations: the program only, everything without a backup, or everything after a backup of the projects you pick. See Install with the setup program.
• Settings lists the YTCC installations on this computer and which one runs the project. One About window, with Copy information, opens from the home page, the editors and the runtime screen. See Application settings.
• The live data server can accept only listed client addresses or networks. See Security hardening checklist.
• The Processes tab shows the PostgreSQL connections in use, and every YTCC connection carries the name of its process. See Databases and schema upgrade.
• The state of the licence is shown in the strip of the home page and in About. See Licence and Capacity Unit.
• The Help window on the home page opens the documents in the interface language. YTCC includes them in Turkish, English and Azerbaijani; for other languages they open in English. See The home page.
• The project list has an AI (MCP) column that turns the AI access of a project on or off. See The home page.
• The packages and the installation folder of the setup program contain Read Me.txt (English) and Beni Oku.txt (Turkish). See Install with the setup program.

Signals and communication

• The DNP3 driver reports the average and maximum poll response time. See DNP3.
• The configuration editor: tables for drivers, devices, signals, alarms, history, areas and zones, with validation before changes are applied. See A tour of the configuration editor.
• Signal types and instances, a type library, internal signals with expressions, and value processing (scaling, deadband, smoothing). See Signal types and instances and Internal signals.
• Renaming a signal keeps its old name working for screens and scripts until the old name is removed.
• New drivers: DNP3, BACnet/IP, ADS and EtherNet/IP. See How drivers work.
• Device time and arrival time are kept separately for every value. See Time stamps and time zones.
• One communication alarm per device and per driver. See Communication state and communication alarms.
• Instances created from a signal type can get their device and address parameters in the same step, with a start value and a step per parameter. See Signal types and instances.
• Set mode… on a folder or a signal type in the explorer simulates or returns to Auto all its signals at once. See Set the run mode of signals.
• A totalizer internal signal adds up a rate over time, for example a flow to a volume. See Internal signals.
• MQTT client: a signal can read the device time from its JSON message and its value from a list of values; values the device buffered during an outage are stored with their original time. See MQTT client.
• MQTT client: with Seq pointer the driver counts lost messages per device from a sequence number in the message, and with Clamp future ts a value whose device time is too far ahead is kept with the arrival time instead of being dropped. See Lost messages.
• The BACnet/IP and DNP3 drivers count timeouts and retries in the Communication diagnostics panel and the system signals of a device. See Check the communication of a device.

Screens

• Junction opens a menu with five ready cards: Straight, Elbow, Tee, Wye and Intersect. See Process objects.
• Five new conveyors: Cleated belt, Chain, Slat, Bucket and Vibrating, each in the ISA-101 and Mimic styles. See Process objects.
• Toggle Button: a Switch drawn as a button, with its own on and off text. See The widget palette and Send commands.
• A signal picker with tabs, tree, search, properties and pinned signals. See Signal picker.
• Trend and Trend Table objects: pens, reference lines, fixed values, limits, chart, table and stacked views, vertical pan and zoom, axis menu, a movable configuration window, and export to xlsx, csv, html and png. See Trend and Trend Table objects.
• Period Chart (energy, uptime, monthly targets) and Analysis Chart (histogram, duration curve, state timeline, heatmap, time comparison, SPC, box plot, XY). See Period and analysis charts.
• Chart object: Y minimum and maximum, start at 0, X format, step line, markers and a last update label. See Chart object.
• Alarm band object with counters, unacknowledged alarms, a trip cause per unit, acknowledge and horn. Trip causes object listing the signals before a breaker opening. See Put alarm objects on a screen.
• Popups: title and frame colors, corner radius, shadow and placement. See Popups.
• Input boxes: prefill, select on focus, and Enter clicks a popup button. See Input boxes in a popup.
• Write Tag can skip the confirmation when the popup is itself the confirmation. See Action types.
• Object theme of a page. See Page and project settings.
• More equipment variants, with command, travel time, interlock, maintenance, simulation and alarm marks. Bar gauges can show the value at the marker. See Process objects.
• 3D Model: left, right or no click for signal details, Click bindings, label styles and | patterns. See 3D Model object.
• Saving per item, Save All, a save conflict window, and live updates when another user saves the same project. See Undo, save and restore.
• Images are kept as separate files of the project.
• New drawing tools (line, trim, shape operations), the command box, the format painter, project colors, gradients, shadows, and objects for gauges, equipment, pipes, maps, clocks and documents.
• Screenshots of the editor and the runtime screen as PNG or PDF. See Screenshot and PDF.
• Screen packages, including packages prepared with an AI assistant. See Screens prepared with AI.
• Text roles from the project's design standard keep titles, labels and values alike, with Apply roles after the table changes. See Object appearance.
• The screen expression functions MAP (linear scaling) and LERP. See Screen expression functions.
• The Menu bar object gives a screen a desktop application menu with submenus. See Menu bar.
• A symbol can resize in layout mode: its objects are placed by constraints and text and lines are not stretched. See Symbols.
• An assistant with AI access can see the objects selected in the editor. See What the assistant can do.
• Claude Desktop connects to the AI access through an extension downloaded from the AI access (MCP) view. See Connect an AI assistant.
• An assistant with AI access can also edit the Global Layout and the display settings of the runtime screen. See What the assistant can do.
• An assistant with AI access can define signals, internal tags, drivers, devices, protocol addresses, alarms and history assignments in a project in the Engineering phase, and upload files of up to 25 MB through a one-time address. See Define signals, drivers and devices.
• The 3D Model object shows a glTF model whose named parts turn, move, appear, change color and show values from signals. See 3D Model object.
• The Vehicle telltale object draws one of 120 dashboard lamps of buses, trolleybuses and trams. See Process objects.
• The Chart object picks its series from the project signals, draws a gap where there is no data instead of 0, and its Show Legend setting shows or hides the legend. See Chart object.

Operation

• Charts on the run screen: click objects, draw curve, XY and other chart types, save templates. See Draw charts from the screen.
• The signal menu shows only the signals under the pointer, and a project setting controls Open in editor. See Look at the details of a signal.
• Enum commands accept only the defined values, and the confirmation window has a new text. See Send commands.
• Every write to the field asks for confirmation; critical commands can require a reason and a second user. See Commands and confirmation.
• Manual values with a reason, and the operating modes Manual [Field], Manual [SCADA] and Simulated. See Operating mode.
• The signal details panel, the trend with any signal chosen at runtime, communication control and system stop from the runtime screen. See Look at the details of a signal and Use the trend.
• A runtime screen receives live values only for the signals it shows. See Page cache and screen subscription.
• An open runtime screen takes changes saved in the editor or by the AI access without reloading the page. See Undo, save and restore.
• The control rail of the runtime screen can be dragged up and down; the position is kept for each user. See A tour of the runtime screen.
• The trend has a pen table with scales, zooming and panning, a min / max band, quality marks, alarm limits, an energy view per hour, day or month, and personal and shared trend profiles. Signals selected in a signal list open in the trend with Plot in trend, and the Open Trend action can open a profile. See Use the trend.

Alarms and history

• The event list has a desktop layout, acknowledge all matching, SOE columns, and built-in and saved views. See Use the event list.
• The alarm list has an icon toolbar and a time bar, and its Download menu offers Excel, CSV, HTML and image. See Read the alarm list and the alarm bar.
• An alarm service per project: alarm levels, acknowledge modes, shelving, alarm areas, classes and groups, the alarm horn and the alarm history. See How alarms work.
• History is recorded in a PostgreSQL database per project, with archive tables, retention by days and by size, and disk protection. See How history is recorded.
• The event list shows signal changes, alarms, commands and operator actions in one list, with Excel export. See What the event list records.
• An Alarm List can hide its top bar and show at most a given number of rows. See Put alarm objects on a screen.
• The alarm history and the signal list can be filtered by the value source and by the quality on the server. See Search and export the alarm history and Work with lists.

Security

• Users, profiles and permissions per project, password and lockout policy, idle sign-out and a system use notice. See Permission model.
• Responsibility zones with exclusive control. See Responsibility zones.
• Audit logs of sign-ins, configuration changes and commands. See Audit logs.

Electrical diagrams

• Single-line diagrams colored live from the network topology, topological interlocking checked on the screen and on the server, the control panel with select and confirm, diagrams across several pages, user-defined symbols, import from IEC 61850 SCL files and switching programs. See Topological interlocking.
• A detail page can show the live color of a device drawn on another page (color source). See Diagrams across several pages.

Scripts

• Server scripts that run on the server without a screen, on signal changes or on a schedule. See Which script runs where.
• scada-manager script export prepares the folder for VS Code, and scada-manager script sync uploads changed scripts when you save them without overwriting changes made in the editor. See Import and export server scripts.

Changed behavior

• Bind to tag on a property that is not bound opens the Signal picker at once, and the property is bound with the Direct mapping. Edit mapping then opens the Tag Binding window. See Bind objects to signals.
• A pipe drawn on from the end of another pipe no longer takes its inline fittings, and a pipe with inline fittings no longer joins its extension: the extension stays a separate pipe, so the fittings stay in place. See Process objects.
• The Compute Unit licence model is replaced by Capacity Units, with .ytreq, .ytlic and .ytrel files. Overrun, unlicensed and unverified states show in the strip of the home page and as a line on the runtime screen. Nothing stops. After 90 days of unlicensed use above 80 CU, design changes cannot be saved. See Licence and Capacity Unit.
• A lost connection is detected within about 3.5 seconds, and a large flashing band says No server connection — data is not up to date. See When the connection is lost.
• Colors and states with no value draw grey, not as 0. See Appearance without a value or communication.
• Show acknowledged in the alarm list is off by default. See Read the alarm list and the alarm bar.
• A driver alarm says that there is no communication, and open system alarms left from another project are closed when the alarm service starts. See Communication, command and system alarms.
• Motor and Conveyor take their state like the pump: Running, Speed (rpm) and Speed are in the State group and are bound to signals. The former Run Tag, RPM Tag and Speed Tag of saved projects and screen packages are taken over when they are opened. See Process objects.
• In a project with user login on, commands need a signed-in user.
• A database is never upgraded by connecting to it; it is upgraded by the setup program, by Upgrade… on the home page or by scada-manager migrate, each with a backup first.
• Popups and dialogs no longer darken the page behind them; darkening can be turned on in Settings on the home page.
• The interface opens in English the first time.
• A new server opens the first-run setup, which creates a server administrator account separate from the projects; creating, copying and importing projects need a sign-in with it. See First start.
• Only one project runs on a computer, across all installed versions. This is no longer a setting: Concurrent projects was removed. Starting a project on the home page stops the running project of the same installation first; a project in another version line still blocks the start. Opening a project in the editor no longer starts its drivers and asks no confirmation. See Run lock and side-by-side versions.
• YTCC can be installed with a Windows setup program, one version line (for example v15) at a time, and then runs as a Windows service. The setup program opens in English and refuses to install into the folder of an old installation from before version lines. To restore a backup, import it on the home page. Removing an installation removes the program only, or everything, with or without a backup of the projects you pick. See Install with the setup program.
• The PostgreSQL password of a setup program installation is kept in config\secrets.toml, readable only by administrators; commands that connect to the database need an administrator window. See Security hardening checklist.
• scada-manager start, stop and restart without a version line ask which line to use, and status shows the process table of every running line. See scada-manager commands.
• A project stop always reports a result, and the home page gives up waiting after 90 seconds with a message. See Start, stop and restart a project.
• The message bus of a version line uses the port of its port block in config\ports.toml. See Port table.
• A value that arrives late with an older device time is stored in the history but no longer moves the current value back, raises a live alarm or runs onChange; after 60 seconds without a newer value it is applied anyway. See Time stamps and time zones.
• The interface uses the corporate blue #2468B8 and the new YTCC logo; a saved accent color of the old default blue changes to it, and new layers are #2468B8.
• The runtime screen opens a page faster: the visible part is drawn first.
• Starting a project whose database is older opens the upgrade window on the home page. The schema messages are in the interface language and no longer ask for a command. See Upgrade a project from the home page.
• The runtime screen no longer shows a label at the top left when communication is lost: a dot on the handle of the control rail and a button on the rail show the view, and only while an object has lost communication. See Read values and states.
• The home page no longer has the What's new in this version card; the release notes are in the Help window.

Upgrade from 1.5.0

1. Back up all project databases and the data folder. After the upgrade, version 1.5.0 can no longer use the upgraded databases; the backup is the only way back.
2. Install the new version, in place or in its own version folder next to the old one.
3. The setup program upgrades the databases itself. For a package installation, with the YTCC processes stopped, run scada-manager migrate --all, or scada-manager migrate --registry and then scada-manager migrate <project> for each project, or take the projects over into the new version.
4. In projects with user login on, create user accounts for the operators before you start: automatic sign-ins can no longer send commands.
5. Start YTCC and check each project.

The steps in detail: Upgrade to a new version and roll back.

1.5.0 (15 August 2026)

The code is the same as 1.4.0. The release marks the version put into service on site and adds documentation.

1.4.0 (28 June 2026)

• One daily log file shows the start-up, the services, the drivers and the communication of each device.
• The reconnect timing of devices can be set; logs rotate daily.
• The last project starts again when the server starts.
• A write is refused while the device is not connected.
• Screen editor: one explorer tree with folders, movable windows, a visibility property.
• Upgrade: the control port of scada-manager moved from 4999 to 5000.

1.3.0 (22 June 2026)

• When a driver stops, its signals get bad quality.
• Scripts are organised in modules, with a diagnostics panel.
• A backup of the project is taken before each save and can be restored.
• Dark theme and interface language selection.
• The alarm bar at the bottom of the runtime screen was removed.

1.2.1 (17 June 2026)

• Popups with parameters, opened next to the clicked object.
• Scripts can write to devices, keep values and change page properties.
• Objects and their event handlers are named automatically.

1.2.0 (15 June 2026)

• New drivers: IEC 60870-5-104 and -101, SNMP, MQTT client with its own broker, and IEC 61850.
• A driver marks the quality of its signals instead of stopping when a device does not answer.

1.1.2 (15 June 2026)

• OPC UA client and OPC UA server.
• A test mode to set values in the editor as if they came from the field.

1.1.1 (14 June 2026)

• Opening a project starts its drivers.
• Scripts can read the quality, unit and time stamps of a signal.
• Screen editor: design and code views, grid and snapping, image upload.

1.1.0 (14 June 2026)

• S7 driver.
• One signal model for all drivers: scaling, range check, quality and alarm definitions.
• Signals can be chosen by name in the screen editor.
• Ports are managed in one place; processes can be started and stopped from the interface.

1.0.1 (13 June 2026)

• Windows: no console windows when YTCC starts in the background.

1.0.0 (13 June 2026)

• First version under the name YTCC.
• The project configuration is kept in a PostgreSQL database and changes apply without a restart.
• scada-manager starts, stops and watches all services and restarts a service that stops.
• Creating or deleting a project creates or deletes its database.