Video

Live at work

The Demo Project running in FabyaVision Live: overview, process screens, alarms and trends, 3D scene. 51 seconds, no sound.

Operator

Operator screens

Pages and navigation

Operators move around with menus and toolbars, pop-up windows and fixed top and bottom areas. User, pages (favorites and all pages), connection states, language and station preferences are in the system menu.

Object, page and menu access by permission
A full-height system panel on the right: session, pages and system actions
The theme comes from the project: Light, Dark or Automatic

Two reactors, condensers, pre-mix tanks and batch status.

Alarm and trend views

The alarm view and alarm bar show the incoming, outgoing, acknowledged and suppressed states. The location button in a row, or a double-click, opens the page of the object the alarm comes from and zooms in on it; red and yellow rings spread around a faulted object. Trends are drawn from the archive or straight from live tags.

Acknowledge, suppress and comment; audible warning (siren or beep)
Many curves, multiple Y axes, scrolling back in time
Digital and analog alarms; color, acknowledgment requirement and priority by class

An alarm list with class colors, the detail of the selected alarm and an alarm summary by area.

Recipe transfer

An approved recipe record is transferred to the PLC directly or with a handshake and verified by reading it back.

Draft and approved records; approval requirement
Restriction by permission group
A script before and after the transfer

Recipe records, values and download to the PLC.

Report records

Reports are recorded on a tag event or manually and come out as Excel, CSV and PDF.

Records are append-only and cannot be edited afterwards
Daily, shift, weekly, monthly and batch summaries; approval and signature block
PDF output with a print preview

Batch records with deviation, energy and duration.

Operator action log

Which user changed which tag and when, the old and new values and the outcome are recorded. The Event View object shows the log on screen.

On by default
Written to monthly files

An event log filterable by type and a separate log of operator actions with users.

On-screen keyboard for touch screens

Touching a field opens the on-screen keyboard; if the field would end up under the keyboard, the page scrolls up. Number fields get a numeric keypad. Only the Turkish Q layout is available, and it works only in the local Live window, not in the browser or on TVs.

The F1–F12 keys on the top row work like those of a physical keyboard, so action keys and screen or object key events fire from them too. A pressed key flashes in the theme color.

Keyboard themes

Standard
Midnight Blue
Carbon
Industrial Steel
Neon
Terminal
Ceramic
Sunset

The theme is set for the project in Studio and for each station from the Live system menu.

The on-screen keyboard open while typing in the recipe search, with the F1–F12 keys on the top row. — On-screen keyboard

The Live on-screen keyboard in eight themes: Standard, Midnight Blue, Carbon, Industrial Steel, Neon, Terminal, Ceramic and Sunset. — On-screen keyboard themes

Screens and TVs

Multiple monitors and TV display

Monitor layouts

In full screen Live spans 1, 2, 3, 4, 6 or 8 monitors: side by side, stacked or in a grid. A separate page can also open on each monitor.

1 monitors
2 monitors
3 monitors
4 monitors
6 monitors
8 monitors

Pages rotating full screen on a production TV, with a clock on top and an alarm banner below. — TV display

Local TV display

A second screen (automatic, or screen 1–4) cycles through a display sequence: one page and a duration per row. Transitions: Fade, Slide left, Slide up, Blur, Zoom, Curtain or Random.

Network TVs

Up to eight TVs open their own address in their browser. A display sequence has up to 40 rows, and durations run from 5 to 3600 seconds. An alarm banner can be shown.

Remote monitoring and control

Monitoring and control from a browser

The Live computer opens a small web server. You watch the project from a computer, tablet or smart-TV browser. If remote control is on, users given a permission group operate the plant as in Live; the others monitor only.

What you can do in the browser

Watch pages, alarm and trend views live
With a permission group: write tags, acknowledge alarms, handle recipes and reports
See pages according to the user’s permissions, read the logs
See camera images and PDFs once logged in

Only on the Live computer

Closing the program and the operator session in Live
Station settings and the time machine
Scheduled tasks, alarm detection, archives and drivers
Database, file and program access from scripts

The syrup preparation page in a desktop browser, with the page list and viewer options on the right. — Desktop browser monitoring

A portrait page in a phone browser showing efficiency, tank levels and pump states.

User name and password

Browser users are defined separately and passwords are stored as hashes. The session cookie is HttpOnly and SameSite=Strict. A user can be connected from only one computer at a time.

Network access rule

By default only private / local network and VPN addresses are accepted. It can be limited to a list of addresses or opened to everyone (not recommended).

Failed-login protection

An address with 5 failed logins within 10 minutes is locked out for 60 seconds; the request origin (Origin) is checked.

Firewall

The Windows Firewall rule is added with a button; it asks for administrator approval.

There is no HTTPS. Connections use plain HTTP, so commands also travel unencrypted. Do not expose the server directly to the internet; use it inside the plant network or over a VPN. Give control rights only to users you trust. TV addresses (/tv1 … /tv8) always monitor only and have no password by default; that setting can be changed.

Remote monitoring settings for port, addresses, browser users and TV playlists. — Remote monitoring

A playlist for each TV, with screen, duration and transition effect. — Network TVs

Live Settings

Five settings tabs

Settings are kept in the project file and edited in Studio. The on-screen keyboard, its theme and the interface language are chosen at each station from the system menu.

General

Start page, full screen, Live language, multiple screens, default theme, on-screen keyboard and keyboard theme, alarm bar, fault wave, 2D and 3D display quality, session timeout, operator action log and script permissions.

Window

Full screen or window; title bar, border, maximize and minimize buttons, always on top, cursor hiding and preventing the screen from sleeping.

Startup sequence

The task, report, alarm, data logging and recipe services can be switched on or off at startup, one by one.

Additional applications

Programs that start and close together with Live. They depend on the run-programs permission.

Keyboard

Key assignments for ten actions: log in and out, screenshot, acknowledge alarm, switch window, forward and back, store and recall page, start screen. Windows keys can be blocked; Ctrl+Shift+Esc and Ctrl+Alt+Del are not.

Live settings for startup screen, multi-monitor, theme, session and script permissions. — Live settings

Start to shutdown

Startup, running and shutdown

Startup
Settings and the project are loaded. The services in the startup sequence and the additional applications start, “on Live start” tasks run and the start page opens.
Running
Drivers connect to the PLCs; if a connection drops, Live retries by itself. Alarms, archiving, tasks and scripts keep running. If the interface process crashes, the page is reloaded.
Shutdown
“On Live shutdown” tasks run, additional applications set to “close with Live” are closed and persistent tags are written.

Live opens the Live file (.fvl) that Studio produces from the project. If no file is specified, a project selection screen appears at startup. There is an option to start automatically with the last project (off on a fresh install).

What is kept where

The program log and settings file sit in the Live folder. Project data and logs sit in the data folder next to the project; optionally they are also written to the project database on SQL Server. Event and alarm logs are not deleted automatically.

File layout

Live\
  logs\Live_yyyyMMdd.log        # program log
  live_ayarlar.json             # Live settings
  Projeler\

Proje.fvl                       # Live file (made by Studio)
Proje.veri\
  depo\*.json                   # tags, recipes, connection passwords
  gunluk\*_yyyyMM.log           # event, alarm, archive, report logs

Data and connections

Connections, archive and tasks

All of this runs inside Live; no separate service is installed.

Driver connections

10 protocols and a simulator. Writes are queued and verified by reading back. S7 switches to a backup PLC by itself.

Connectivity page

History archive

A local monthly file is always written; CSV and SQL Server mirroring are optional. A disk buffer is kept if the connection drops. Old data is cleaned up automatically by retention time and maximum size.

Tasks

Scheduled or event-driven jobs with 10 trigger types; a missed task can run at startup.

Scripts

VBScript, JavaScript, C and Python scripts run in Live; database, program and file permissions are off by default.

Task triggers

Cyclic
Daily at a set time
Days of the week
Day of the month
Day of the year
One-time
Tag change
Tag condition
On Live start
On Live shutdown

Outside connections

OPC UA server, notifications and performance reports

Live opens tags to outside systems, sends important alarms to people and e-mails scheduled reports.

OPC UA server

Tags selected in Studio are opened to external OPC UA clients. Each tag gets read-only or read and write permission.

Learn more

Notification Center

Selected alarms reach people by SMS and e-mail according to rules. On sites with no internet, a GSM / LTE modem with a SIM card is used.

Learn more

Performance reports

You assign tags to ready-made templates; the report goes by e-mail as PDF and Excel to the defined people at the planned time.

Learn more

Scope and limits

What Live does not include

Not a Windows service

If it closes, it does not restart by itself. The “start Live when Windows starts” option in the installer (off by default) only adds a startup shortcut.

No server / client architecture

Each Live runs its own screens and opens one project at a time; there are no separate client stations. To switch projects, use “Change project” in the system menu. Two Live instances can back each other up as a redundant server pair.

OPC UA server scope

Live’s OPC UA server offers tag reads, writes and subscriptions. There are no history, alarm or method services, and there is no OPC DA server.

Not a cloud or mobile app

It is Windows software installed on premises, with no mobile app.

Live

Open the sample project in Live

Open the sample project with the trial. The simulator connection works without a PLC, so alarms, trends and 3D scenes run live.

Try it free Write to us

Live at work

Operator screens

Pages and navigation