FabyaVisionUser Manual
/

Device configuration

7 min readProjects

The name of the station on which the project will run, the computer name and the operating mode (single station or redundant server pair); the server names, addresses, port and times of the redundant server pair.

Device configuration is the section that defines the SCADA computer (station) on which the project runs. It is the first section under the station node in the Project tree. It has two cards: Station and Redundant server pair.

Device configuration: the Station card on the left, the Redundant server pair card on the right.123
Device configuration: the Station card on the left, the Redundant server pair card on the right.
  1. Station name
  2. Computer name
  3. Operating mode

Station card

FieldValueDefaultWhat it is used for
Station nameRequired; starts with a letter, contains only letters, digits and _Istasyon_1The name you give to the station. In Studio it appears as the name of the station node in the project tree, in the path bar, in the station box in the Overview and in the Project information window.
Computer nameWindows computer name; no spaces or characters such as \ / : * ? " < > | . , ;, at most 63 charactersemptyOn a single station, Live warns if it is started on a computer with a different name (see below). Not used in a redundant pair; the server names are taken from the Redundant server pair card.
Operating modeSingle station or Redundant server pair (redundancy)Single stationSingle station: Live runs on one computer. Redundant server pair: the same project runs on two computers; one is master, the other standby (Redundant server pair).
DescriptionTextemptyFree note.

When the station name is changed, the project tree, the path bar and the Overview are updated immediately. An invalid name (one that starts with a digit or contains a space) is not accepted; a warning window states the reason: “The station name must start with a letter; it may contain only letters, digits and "_".” For a name left blank, the message “The station name cannot be left blank.” appears. The station name does not change the name of the file uploaded to Live: the file name is the name of the project file (Uploading the project to Live).

The Server (with browser clients) type found in older versions was never implemented; when such a project is opened, its type becomes Single station. Monitoring from a browser is enabled in a separate section (Remote monitoring) (Remote monitoring).

Computer name warning

On a single station, if Computer name is filled in and Live is started on a computer with a different name, a warning window appears at startup and the same text is written to the event log: This project is configured for the computer KONTROL-PC; this computer is OFIS-PC. Live still runs; the warning helps you notice a project uploaded to the wrong computer. The Windows name is shown under Settings›System›About.

Redundant server pair card

The card applies only when Operating mode is Redundant server pair (redundancy); on a single station the fields are not used even if they are filled in. How it works, the setup steps and the limits: Redundant server pair.

A station with Redundant server pair selected: name and address of the two servers, default master, port and times (sample names).1234567
A station with Redundant server pair selected: name and address of the two servers, default master, port and times (sample names).
  1. Operating mode — when “Redundant server pair” is selected, the settings below apply.
  2. Server 1 computer name — the Windows name; Live uses this name to determine which server it is.
  3. Server 1 address — the IP address or name to which the other Live and the browsers connect.
  4. Default master — becomes master when both start together.
  5. Redundancy port — TCP port between the two Live instances.
  6. Timeout (s) — if the other server does not respond within this time, it is considered failed.
  7. Pairing key — the two Live instances recognize each other by this key; Studio generates it.
FieldValueDefaultWhat it is used for
Server 1 computer name, Server 2 computer nameWindows computer name (rules as on the Station card)emptyWhen Live starts, it compares its own Windows name with these two names (not case-sensitive) and determines which server it is. On a computer whose name matches neither, redundancy remains off, Live runs as a single server and shows a warning.
Server 1 address, Server 2 addressIP address or network nameempty (= computer name)The address at which the other Live and the browsers connect to this server. If the network name cannot be resolved, enter the IP address.
Default masterServer 1 or Server 2Server 1The server that becomes master when both start together. A failed master that comes back becomes standby; it does not take the master role back on its own.
Redundancy port1024 – 655358091The TCP port of the connection between the two Live instances; it is the same on both computers. It must be different from the Remote monitoring port. Allow this port in Windows Firewall on both computers.
Timeout (s)2 – 605If the other server does not respond for this time, it is considered failed. A short time speeds up the switchover; a very short time also causes a switchover on a brief network interruption.
History to synchronize (days)0 – 302How many days of the alarm, event, data log and report logs are fetched from the master when the standby server (re)connects. 0 = only those arriving while connected.
Browser / TV failoverOn / OffOnWhen on, browser and TV viewers switch to the other server if their server does not respond for 10 s.
Pairing key32 hexadecimal characters; cannot be changedGenerated by StudioThe two Live instances recognize each other by this key. It is stored in the project file; it is not sent to browser viewers.

Summary and buttons

The summary below the card is refreshed with every change: the state (Not in use, Incomplete or On), the name and address of the two servers, which connections have an arbiter address, and what to do on the two computers.

Summary on the Redundant server pair card: the two servers, connections with an arbiter and reminders.
Summary on the Redundant server pair card: the two servers, connections with an arbiter and reminders.
  • Open the Connections section: switches to Connections to enter the arbiter addresses (PLC arbiter).
  • Generate new key: asks for confirmation and generates a new pairing key. Until the project is uploaded again to both servers, the two Live instances do not pair. It can be undone once with Ctrl+Z.

Check project rules

When the operating mode is redundant, F7 writes the following to the Problems list (location: General › Redundant server pair):

  • Error: the server computer name has not been entered; the address is invalid; the same name or the same address has been entered for both servers; the port is out of range or the same as the Remote monitoring port.
  • Warning: no PLC connection has a valid arbiter address.

The specific rules for the arbiter address are checked in the connection's row (Arbiter card).

What is used in Live

Live reads Operating mode, Computer name (only for a warning) and all fields of the Redundant server pair card. Station name and Description are visible only in Studio: use them to identify and document the project. The startup, appearance, session and window behavior of Live is set in Live settings (Live settings).

Related topics

FabyaVision 1.2.1 User Manual · 2 November 2026© Fabyatek Yazılım Bilişim Teknolojileri Ltd. Şti.