Files and folders of Live

6 min readLive

The Live program folder, the project folder, the project's .veri folder (persistent values, event and alarm logs, archive, report and recipe records), the settings file and backup.

General layout

By default, the setup program installs Live under C:\Program Files\Fabyatek\FabyaVision\Live\ (Studio is in the sibling folder: …\Studio\). The locations that Live writes to are opened so that users can modify them; the program files cannot be modified.

Location	Content
`Live\FabyaVision_Live.exe`, `Live\wwwroot\`	Program and interface files. Do not modify.
`Live\logs\`	The Live program log: `Live_yyyyMMdd.log` (Log files).
`Live\Projeler\`	The default project folder. If it is not writable, `%LOCALAPPDATA%\FabyaVision\Projeler` is used.
`Live\live_ayarlar.json`	Live's own settings (below).
`%LOCALAPPDATA%\FabyaVision_Live\WebView2\`	User data of the WebView2 component that renders the interface. Not edited by hand.
`Belgeler\FabyaVision_Live\Ekran Görüntüleri\`	The PNG files of the screenshot key (the folder name is the name of the running program).

Settings file: live_ayarlar.json

The file is located in the program folder and is independent of the project file. If the file is missing or damaged, safe defaults are used; it is read field by field, and a damaged field alone reverts to its default.

SonProje: Full path of the most recently opened project file.
ProjeKlasoru: The folder scanned by the project selection screen. If empty, the default folder is used. Change folder… on the project selection screen writes this field.
OtomatikBasla: If true and no project is given on the command line, the last project is opened without showing the project selection screen. On a new installation it is false. In a file carried over from a previous version in which SonProje is filled in, a missing field is treated as true.
EkranGoruntuKlasoru: The folder to which the screenshot key writes its PNGs. If empty, Belgeler\<program adı>\Ekran Görüntüleri.

Project folder

The Upload project to Live… command in Studio writes the project in the following structure; the project selection screen of Live also scans this structure.

Projeler\
  Tanitim_Tesisi\
    Tanitim_Tesisi.fvs          proje dosyası
    Tanitim_Tesisi.veri\        Live'ın yazdığı veriler (ilk yazmada oluşur)
    Yedek\                      yüklemede eski sürümler: Tanitim_Tesisi_2026-10-17_0930.fvs …

The scan covers the project folder and one sub-level; *.fvs files and the old *.fyscada files are listed. Folders such as *.veri, Yedek and .git are skipped. If the same name exists with both extensions, .fvs takes precedence. A file that is not JSON or is corrupt is shown as a red Unreadable card.
Yedek: if the project is uploaded again while the target file exists, the old version is saved here as <Ad>_<yyyy-MM-dd_HHmm>.fvs (at most 10).
Uploading never copies, deletes or changes the .veri folder.

Project data: the .veri folder

<Ad>.veri is located next to the project file (<Ad> is the name of the project file without extension; this also applies to the old .fyscada). It has two subfolders.

depo\ — persistent values

Each key is a .json file. Writing is first done to a temporary file, which then replaces the actual file; even if the power fails, no half-written file remains.

File	Content
`istasyon.json`	The preferences of this computer: on-screen keyboard, interface language, font size.
`tag_kalici.json`	The last values of persistent internal tags (written when Live closes, read when it opens).
`gorev_durum.json`	Last run and result information of the scheduled tasks (Tasks… window).
`recete_<kimlik>.json` and related files (`recete_etkin_…`, `recete_gecmis_…`)	Recipe records, the active record and the PLC transfer history.
`rapor_<kimlik>_sayac.json`	Report record number counter.
`trend_<kimlik>.json`	The selections the operator makes in the trend object (on this station).
`baglanti_sifreleri.json`	The passwords of connections that require a user name / password (those entered with Enter password).

gunluk\ — monthly log files

A separate monthly file is kept for each log name: <ad>_yyyyMM.log (the month is the local month at the moment the line is added). Each line is a single-line JSON and contains a "z" (Unix milliseconds) timestamp. Only English letters, digits, _ and - may be used in log and store names (1 – 80 characters).

File	Content	Deletion
`olay_yyyyMM.log`	Event log: session, settings, recipe, report, system, script, operator and connection records (Log files).	Not deleted automatically.
`alarm_yyyyMM.log`	Alarm records (unless the Logged option of the alarm class is switched off).	Not deleted automatically.
`arsiv_<kimlik>_yyyyMM.log`	Data archive records; the trend and history are read from this file.	According to the archive's retention setting; only months at least two months old are deleted.
`arsiv_<ad>_yyyyMM.csv`	Archive CSV mirror (with UTF-8 BOM, `;` delimiter, decimal point, with header row); when CSV is selected in the archive.	The same rule.
`arsivsql_<kimlik>.bekleyen`	The disk buffer for archive rows that could not yet be written to SQL Server.	It is emptied once written.
`rapor_<kimlik>_yyyyMM.log`	Report records and their approval and deletion marks.	According to the report retention setting; the current month and the previous month are never deleted.
`recete_aktarim_yyyyMM.log`	The recipe's PLC transfer records.	Not deleted automatically.

For where the retention settings are made and what effect they have, see Historical data and Generating the report in Live. If the clock is invalid (before 2020), no file is deleted.

Backup and transfer

When moving the project to another computer, copying the .veri folder together with the .fvs file also transfers the persistent values, the recipe records and the historical data. If only the .fvs file is copied, the project opens, but this data is empty on the new computer.
For a regular backup, copy the .veri folder and the live_ayarlar.json file. Copying files while Live is running is possible; for a consistent backup, do it after closing Live.
The Yedek folder holds only older versions of the project file; it does not contain Live data.

Limitations and points to note

The event, alarm and recipe transfer logs are not deleted automatically; monitor the disk for filling up and, if necessary, back up and delete old monthly files.
The program log in the logs folder and the project records in the .veri\gunluk folder are different things: the first holds Live's own messages, the second the event, alarm, archive and report data of the project.
The folder layout may vary depending on the installation (custom installation folder, the ProjeKlasoru setting). Verify the exact path on the Select project page (the Project folder row).