Frequently asked questions
We gathered the questions people ask most before installing or buying YTCC, sorted by topic. If yours is not here, write to info@ytcc.io.
General
What is YTCC?
YTCC (YTControl Control Center) is a web-based SCADA/HMI platform from YTControl, with a core written in Rust. It runs on your own server and collects data from field devices. You design screens, alarms and server scripts in the browser and monitor your plant from a computer, tablet or phone on your local network.
Who develops YTCC?
YTControl develops YTCC. YTControl was founded in 2017 by engineers with over 20 years of field experience in safety-critical automation, and is based at Istanbul Teknopark.
How can I try YTCC before buying?
Open the Live Demo in your browser and sign in with your Google account. To try it on your own system, download YTCC and install it on your server. 80 CU or less is free, commercial use included.
What are the demo projects?
Ready-made projects you can open and explore in YTCC. Download a file from the Demo Projects page, then on YTCC's home page drag the file onto the project list.
Does YTCC work with AI tools?
YTCC works with AI tools over the Model Context Protocol (MCP). MCP opens your YTCC project to an AI client. You write the request; the AI builds the screen, symbol or 3D object in YTCC for you.
How do I get technical support?
Business-hours support is included with every license. You can send support requests by email to support@ytcc.io.
Which industries does YTCC focus on?
YTCC's target industries are power transmission and distribution; renewable energy (solar, wind and hydro); water and wastewater; industrial manufacturing; building and facility automation; transportation infrastructure; oil and gas; and agriculture and irrigation.
Installation and access
Where is YTCC installed?
On your own server. The server runs on Windows 10/11 (x64) and Linux (x86-64). There is no macOS package; you connect from your Mac in a browser.
What do I need before installing YTCC?
Your server needs PostgreSQL and Node.js before you install YTCC. YTCC keeps the history of measurements, alarms and events in a PostgreSQL database. Install an LTS release of Node.js: 20 or later on Windows, 22 or later on Linux.
Can I connect from a tablet or phone?
Yes. Runtime screens open in the browser, so you reach them from computers, tablets and phones on your local network. The client side needs nothing but a browser.
Can I move a project to another computer?
Yes. Back up the project to a single file and import it into YTCC on the new computer. Measurement and alarm history and driver certificates stay out of the file.
Protocols and operation
Which protocols does YTCC use to talk to field devices?
YTCC communicates over Modbus TCP, Siemens S7, OPC UA, IEC 60870-5-101, IEC 60870-5-104, IEC 61850 (MMS), DNP3, BACnet/IP, MQTT, SNMP, Beckhoff ADS, and EtherNet/IP.
Do I have to stop the system to make a change?
Not to add or remove a point or change an address: the main drivers keep running. A driver-wide setting does need the driver to restart.
What happens if a driver stops?
YTCC restarts a crashed driver on its own. If a device loses its link, an alarm comes in for that device.
How does YTCC check commands?
The server checks permissions, so a user without the right cannot send a command. A command sent while the link is down is rejected, and a failed command raises an alarm.
Can I set user permissions and password rules?
Yes. You define the roles and decide who can edit screens, acknowledge alarms or send commands. You also set the password rules and account lockout.
Pricing and licensing
What is a CU (Capacity Unit)?
A CU is the unit of a YTCC license. YTCC counts the protocol drivers and power tags in the projects running on a server; a power tag is an active signal point bound to a driver. It does not count user accounts, runtime screens, alarms or features. 80 CU or less is free, commercial use included.
Is YTCC free?
80 CU or less is free, commercial use included. The free tier includes every feature too. If your system goes past 80 CU, you pay $1 per CU.
How much does a SCADA license cost?
In YTCC your total CU sets the license price: 0–80 CU is free, 81–4,999 CU costs $1 per CU, and from 5,000 CU the price is fixed at $5,000. Prices are per server and in US dollars, excluding taxes and maintenance.
How do I see the CU of a running system?
Open the License page from YTCC's home page. Its calculator loads your current usage and shows the breakdown.
Do you sell any features separately?
No. Every plan includes all features, and only your power tags and protocol drivers set the price.
Do users or clients change the price?
No. User accounts, runtime screens and editor sessions are unlimited and add nothing to the price.
Does running several instances of one driver raise the price?
No. How many instances of a driver you run, and how many devices and connections they serve, do not change the price. Modbus TCP is 50 CU with one instance or with five.
Is the license per server?
Yes. Each server has its own license, and the projects running on it share its CU.
How do I buy?
Ask us for a quote. Once you accept it, we send a proforma invoice and you pay by bank transfer.
Features
Real-Time Monitoring
What do I need to install on the client side?
Just a browser. Once the YTCC server is installed, the runtime screen opens in the browser.
What do I see when a device loses its link?
A single alarm comes in for that device, and the objects showing its values turn the "no communication" color.
Are commands sent from the screen logged?
Yes. Every command is logged with the user, value and result. A command sent while the link is down is rejected.
Alarm Management
Can I acknowledge alarms as a group?
"Acknowledge group" acknowledges every alarm in a group. Each acknowledgement is logged under the user's name, and you can add a comment when you acknowledge one or several alarms.
Can I take an alarm off the list for a while?
Yes, by shelving it. You write a reason and pick how long, or keep it shelved until you unshelve it yourself.
Can I export the alarm history?
Yes. Download the alarm history as Excel or CSV and the command log as Excel.
Web Editor
What if I change my mind?
Undo it. The editor also keeps your last ten saves, so you can go back to any of them.
Can I use my existing drawings?
Yes. Import SVG files and bring in images from another project.
Can I add behavior to screens?
Yes. The expression builder calculates values, and event scripts make a click do something. On the server side you write server scripts in TypeScript.
Symbol Library
Which symbols come ready-made?
Gauges, pumps and motors, valves, tanks, flow meters, and electrical, energy and HVAC symbols. For single-line diagrams there are breakers, disconnectors, busbars and transformers too.
Can I use my own symbols?
Yes. Import your drawing as SVG and bind signals to its parts. Parameterized symbols let you reuse one drawing for different equipment.
How do symbols connect to signals?
Place the symbol on the screen and bind its state, level or color to a signal. On the runtime screen the symbol follows the value.
Backup and Migration
What does the backup include?
Settings, screens, images, users and roles. Measurement and alarm history, driver keys and certificates are not included.
How do I back up a project?
You back up the project to one zip file on YTCC's home page while it runs. To restore it, you import the same file on the home page. The import stops only the project you overwrite.
Charts
Can one chart show several signals?
Yes. Bind several signals to a chart and give each series its own label and color. The half gauge draws only the first series.
Which chart types can I use?
Line, area, bar, half gauge, pie and radar. The first three plot history over time; the other three show live values.
Do I have to archive a signal to see its history?
For line, area and bar charts, yes. These types read from the archive and plot averages over time intervals, and you set how often they refresh. Half gauge, pie and radar use live values and need no archive.
3D Environment Support
Which model files can I use?
Binary glTF 2.0 (.glb), up to 25 MB. Prepare the model and its part names in your own modeling tool, without Draco or Meshopt compression. You upload the file from the object's properties, and it stays with the project and its backups.
Can I bind parts of the model to signals?
Yes. Pick a part by name or pattern, then drive its rotation, angle, position, visibility, color and value label from signals, or attach an action to a click. When you replace the file, the bindings stay as long as the part names match.
Can operators rotate the model?
Yes. Dragging rotates the model, the mouse wheel zooms, and one button returns to the starting view. You can turn this off at design time. The browser needs no plugin, only WebGL 2 switched on.
Industries
Power Transmission and Distribution
Which protocols does YTCC use to talk to transmission and distribution field devices?
As master: IEC 60870-5-104, IEC 60870-5-101 over TCP and DNP3. As client: IEC 61850 (MMS), reading by polling. The DNP3 driver runs over TCP, UDP and serial lines and can use TLS and Secure Authentication v5. Other field protocols, such as Modbus TCP and OPC UA, are listed on the Platform page.
Can two operators send commands to the same zone at the same time?
No. With responsibility zones, one user at a time controls a zone, and the server enforces control permission. A user takes, releases or requests control, and can force take it with the right permission.
Are events sorted by the time stamp from the field?
Yes. The IEC 104 driver stores the device's CP56Time2a time tag as the time of the event, and the event list, the alarm history and the historian are sorted by it. The arrival time at the server is shown in its own column. If the device time is missing or invalid, the arrival time is used.
Renewable Energy (Solar / Wind / Hydro)
Which protocols does YTCC use to read inverters and turbines?
As master: Modbus TCP and IEC 60870-5-104. As client: OPC UA, IEC 61850 (MMS) reading by polling, and MQTT. YTCC also works as an OPC UA server. Other field protocols are listed on the Platform page.
Can I monitor several plants in the same interface?
Yes. You keep the plants' signals in one project and watch each plant on its own screen and in its own alarm group. User roles and per-page access lists decide who sees which plant's screens.
Are production values archived?
Yes. In the historian settings you archive each signal on change or periodically, with an absolute or percentage deadband, and set the retention period. The historian is kept on PostgreSQL.
Water and Wastewater
Which protocols does YTCC use with PLCs and stations in water systems?
As master: Modbus TCP and DNP3. As client: Siemens S7 and MQTT. As OPC UA client and server. Modbus is supported over TCP only. Other field protocols are listed on the Platform page.
Can I track pump running hours?
Yes. The internal tags include running hours and counters: you keep a pump's running hours from its run signal and its number of starts from its start signal. These values can be archived too.
How do I set up automatic tasks such as pump rotation?
With server scripts. You write them in TypeScript in the browser and attach them to a value change, periodic, calendar or alarm trigger. A dry run is possible before anything is written, and commands reach the field only with explicit permission, a target pattern and a rate limit.
Industrial Manufacturing
Which PLCs does YTCC talk to?
Over Siemens S7 (S7comm, ISO-on-TCP), EtherNet/IP (Logix symbolic tags, explicit messaging), Beckhoff ADS (TwinCAT 2/3 symbolic names), OPC UA, Modbus TCP and MQTT. On S7-1200/1500, PUT/GET must be enabled and optimized block access turned off.
Do I have to restart the driver to add a signal?
No. Adding and deleting points and changing addresses and scaling take effect without restarting the driver and without dropping the device connection. When a device's connection settings change, only that device reconnects; driver-wide settings need a driver restart.
Can I see who changed the configuration?
Yes. For configuration changes, the audit log keeps who changed which record and when, with the previous and new values.
Building and Facility Automation
Does YTCC talk to BACnet devices?
Yes, as a BACnet/IP client. It discovers devices with Who-Is and scans their objects, subscribes to COV for Present_Value and writes with a priority from 1 to 16. BACnet MS/TP devices are reached through a BACnet/IP router.
Can I monitor network devices too?
Yes. As an SNMP manager you poll devices with v1, v2c and v3, write values and receive traps. SNMP v3 traps are not decoded.
Can I define automatic tasks by working hours?
Yes. You attach server scripts to a calendar (cron) trigger. Scripts run in a sandbox, and commands reach the field only with explicit permission, a target pattern and a rate limit.
Transportation Infrastructure
Which protocols does YTCC use with tunnel equipment?
As master: Modbus TCP. As client: OPC UA and MQTT, and as an OPC UA server too. It monitors network devices as an SNMP manager and receives traps. Other field protocols are listed on the Platform page.
Can I separate alarms by tunnel zone?
Yes. With rule-based, nested alarm groups you gather alarms by tube, zone or system. Group counters show the alarms in each group, and you acknowledge a group at once.
Can I export the alarm and command history?
Yes. You download the alarm and command history as Excel or CSV. Commands include the sending user, the value and the result.
Oil and Gas
Which protocols does YTCC use with devices in oil and gas facilities?
As master: Modbus TCP, DNP3 and IEC 60870-5-104. As client: OPC UA and MQTT, and as an OPC UA server too. Other field protocols are listed on the Platform page.
Can DNP3 communication be secured?
The DNP3 driver can use TLS and Secure Authentication v5. It runs over TCP, UDP and serial lines.
Can I see who sent which command?
Yes. For every command the sending user, signal, value, result and times go into the audit log, and refused commands are logged too. You can download the command history as Excel or CSV.
Agriculture and Irrigation
Which protocols does YTCC use with devices in irrigation systems?
As master: Modbus TCP. As client: MQTT and OPC UA, and as an OPC UA server too. Modbus is supported over TCP only. Other field protocols are listed on the Platform page.
Can I start irrigation automatically at set times?
Yes. You attach server scripts to a calendar (cron) trigger. Scripts run in a sandbox, and commands reach the field only with explicit permission, a target pattern and a rate limit.
YTCC. Your trusted control center for energy and industrial SCADA.
Download YTCC and build your first screen.