BY NXGEN

Geutebrück

Device Configuration & Integration Guide

2026

GCXONE Security Management Platform  |  NXGEN Technology AG

© 2026 NXGEN Technology AG. All rights reserved.

Overview

Geutebrück is a professional Video Management System (VMS) that provides recording, live viewing, video playback, and event/alarm management for connected cameras and security hardware. GCXONE integrates directly with Geutebrück, allowing streams and events from G-Core servers to appear alongside other devices in the GCXONE platform.

Ports

Applications

•  G-Set: system configuration client — used to add hardware, configure media channels, and set up event and behaviour rules.

•  G-View: operator client for live viewing, playback, and event monitoring.

•  GPLC Simulator: PLC test simulator for I/O and manual event workflows, used during testing.

Part 1 — G-Set Configuration

1.1  Starting G-Core

G-Core is the server component of Geutebrück. It must be running before G-Set or G-View can connect. Start it from the Command Prompt as Administrator:

1.  Open Command Prompt as Administrator.

2.  Navigate to the G-Core installation folder:  cd %gngpath%

3.  Stop any running instance:  GCoreServer.exe stop

4.  Start G-Core — use Demo mode for testing (GCoreServer.exe demo) or Licensed mode for production (GCoreServer.exe start).

Figure 1: G-Core running in Demo mode — server started and connected to the SQL database.

1.2  Connecting G-Set to the Server

Once G-Core is running, launch the G-Set client and connect to the server using the Connection Wizard.

1.  Open G-Set. Click Connection Wizard on the main screen.

Figure 2: G-Set main screen — click Connection Wizard to begin.

2.  Enter the Connection name, Host name (G-Core server IP), Username, and Password. Default credentials: username = sysadmin, password = masterkey. Click Ping Host and Check Connection to verify, then click OK.

Figure 3: Connection Wizard form — enter host details and verify connectivity before saving.

3.  In the Connections panel, right-click the connection and select Connect.

Figure 4: Right-click the connection name and select Connect to establish the session.

1.3  Adding Hardware (IP Camera)

Hardware in G-Set represents the physical camera device. Each camera is added as an IP-Camera plugin module.

1.  In the left panel, expand Media channels / Hardware and click Hardware.

2.  In the Hardware module list, right-click and select Add.

Figure 5: Hardware module list — right-click and select Add.

3.  In the Add hardware module dialog, select IP-Camera Plugin <ONVIF IPC> and click Add.

Figure 6: Select IP-Camera Plugin <ONVIF IPC> and click Add.

4.  Configure the hardware module and click Save:

Figure 7: Hardware configuration panel — enter camera name, hostname, and credentials.

1.4  Adding a Sensor (Media Channel)

A media channel in G-Set is what GCXONE recognises as a sensor. It links a video stream from a hardware module to the GCXONE device.

1.  In the left panel, click Media channels under Media channels / Hardware.

2.  Right-click in the list and select Add.

Figure 8: Media channel list — right-click and select Add.

3.  In the Module channels dialog, select the hardware module you just created and click Add.

Figure 9: Module channels dialog — select the hardware module (e.g., Module channel 1 on <SCT-Entrance>) and click Add.

4.  Enter the channel details and click Save:

Figure 10: Media channel settings — enter the channel name and description.

5.  Select the channel in the tree, open Permanent recording, enable it, and click Save. The sensor is now added and linked.

Figure 11: Permanent recording enabled for the media channel.

Part 2 — G-View Application

G-View is the operator client used to watch live feeds, review recorded footage, and monitor events.

1.  Launch G-View. In the Video servers panel, right-click the server name and select Connect.

Figure 12: G-View — right-click the server and select Connect.

2.  Expand the server tree. Double-click a media channel to open its live stream.

3.  Use the playback controls and the Event / MOS timeline tabs to review recorded footage and jump to event markers.

Figure 13: G-View live feed — SCT-Entrance channel streaming with timeline visible.

Part 3 — Geutebrück Integration in GCXONE

3.1  Add a Geutebrück Device

With the custom property in place, register the Geutebrück G-Core server as a device under the target site.

1.  Navigate to the target site in the Configuration app and open the Devices tab. Click Add.

Figure 16: Site Devices tab — click Add to register a new Geutebrück device.

2.  Fill in the new device form:

Figure 17: New Device form — select Geutebrueck as the device type and fill in the server connection details.

3.  Click Save & Verify to confirm GCXONE can reach the device and receive stream data.

3.2  Verify the Live Stream in GCXONE

Once saved, sensors from G-Set appear under the device in GCXONE. Open any sensor in the Video Viewer to confirm the live stream is active.

Figure 18: GCXONE Video Viewer — live stream from the Geutebrück-connected camera confirmed.

Part 4 — Event Rule Configuration in G-Set

Event rules define what triggers an alarm, how the system responds, what is recorded, and how the alarm appears in G-View and GCXONE. The Event/Alarm Wizard guides you through five steps.

To open the wizard: in G-Set navigate to Events / Behaviour Rules → Events, right-click in the event list and select Add.

Step 1 — Event Settings

Enter the event name, configure timing, and set database storage options.

•  Event name: enter a descriptive name (e.g., VMD event).

•  Retrigger mode: set to Retrigger to allow the event to restart while already active.

•  Store to database: ensure On start and On stop are enabled so events appear in logs.

Figure 19: Step 1 — Event Settings. Configure the event name, ring buffer, retrigger mode, and database logging.

Step 2 — Action Settings

Define which alarm actions start and stop the event by dragging items from the Action list into the Start by and Stop by zones.

•  Start by: G-Tect/VMD alarm — triggers the event when motion is detected.

•  Stop by: G-Tect/VMD alarm finished — ends the event when motion stops.

Figure 20: Step 2 — Action Settings. G-Tect/VMD alarm assigned as the Start action. The Action list shows all available triggers.

Step 3 — Recording Settings

Assign the media channels to record when the event fires by dragging them from the channel list into the Recording channels drop zone.

Figure 21: Step 3 — Recording Settings. SCT-Entrance is available in the media channels list.

Step 4 — Alarm Settings

Configure the alarm that appears in G-View and GCXONE when the event fires.

•  Alarm name: e.g., test or VMD alarm.

•  Alarm priority: High, Medium, or Low.

•  Media channels: drag the camera channel so the alarm opens its feed automatically.

•  Default alarm scene: enable to display the camera when the alarm is acknowledged.

Figure 22: Step 4 — Alarm Settings. Alarm name, priority, and associated media channel are configured.

Step 5 — Summary

Review the complete configuration in one table, then click Save & Finish to commit the event rule.

Figure 23: Step 5 — Configuration Summary. VMD event with G-Tect/VMD alarm trigger, SCT-Entrance recording, and test alarm confirmed.

4.1  Reviewing the Event Configuration

After saving, clicking an event in the G-Set Events tree opens its full configuration — including the event tree, recording task, media channels, and playback profile.

Figure 24: Event configuration detail — VMD event tree showing Recording tasks, StartBy, StopBy, and recording profile at 25 fps on SCT-Entrance.

Part 5 — Viewing Event Logs in G-View

All triggered events are logged in the G-View Event list. A populated log confirms the device is online and events are being captured correctly.

1.  Open G-View and connect to the server.

2.  In the top menu bar, click View then select Event list.

Figure 25: G-View — View menu with Event list highlighted.

3.  The Event list opens. Each entry shows:

Figure 26: G-View Event list — VMD events logged with start time, stop time, event name, and description. A populated log confirms end-to-end integration.

A populated event log confirms that events configured in G-Set are successfully captured, stored, and visible in G-View — validating the complete Geutebrück integration from device to GCXONE.

For technical support or integration assistance, contact NXGEN Technology AG through the GCXONE support portal.