Manager Tool
The Manager Tool is the central configuration interface for GroundControl VGRS. It launches in onboarding mode on first startup to guide you through the initial setup. After completing the onboarding process, you can view and modify all system configuration settings.
Access: The Manager Tool can be launched via desktop shortcut or Start Menu entry (if configured during installation).
System Tray Behavior: Clicking the close button minimizes the application to the system tray rather than terminating it. To fully exit the application, right-click the tray icon and select Quit.
Onboarding Mode
The onboarding mode guides you through the initial configuration of GroundControl VGRS. During this process, you will configure essential components including database connections, message broker settings, logging, scheduling, TETRA integration, and web access parameters. All settings configured during onboarding can be modified later in normal mode.
Database
GroundControl VGRS requires a default database to store application data and a separate database to store event logs and high-volume data. These databases must be created prior to establishing a connection. See 'Database Setup' for detailed instructions.
| Field | Description |
|---|---|
| Server | Format: <host>\<SQL-Server>. For local installations, use .\<SQL-Server>. IP addresses are also supported. |
| Database | Database name. Recommended: GC for the Default Connection and GC.EventLogging for the EventLog Connection. |
| User Id | Username of the SQL Server credential. |
| Password | Password of the SQL Server credential. |
| Use Windows-Authentication | Enable or disable Windows Authentication. When disabled, SQL Server Authentication will be used with the provided credentials. |
Windows Authentication Context
When using Windows Authentication, the Manager Tool operates under the security context of the currently logged-in Windows user, while GroundControl VGRS services run under the GroundControl VGRS service account (if configured during installation). Ensure that database access permissions have been properly configured for the service account as described in the database setup guide.
RabbitMQ
RabbitMQ serves as the primary message broker for inter-service communication within GroundControl VGRS.
| Field | Description |
|---|---|
| Host | For local installations, use localhost. Remote installations require an IP address or resolvable hostname. |
| Port | Default port is 5671. This can be configured during RabbitMQ setup. |
| Username | Optional. Required only when authentication is enabled. Leave blank for unauthenticated local connections. |
| Password | Optional. Required only when authentication is enabled. Leave blank for unauthenticated local connections. |
Remote Authentication Required
Remote RabbitMQ installations require authentication credentials. Unauthenticated connections are only permitted for local installations. For additional details, refer to the RabbitMQ setup guide.
Logging
| Field | Description |
|---|---|
| Minimum Log-Level | The log level determines which events are written to the log files. Available log levels: Verbose, Debug, Information, Warning, Error. |
| Log Path | Directory path for log file storage. |
Log Rotation & Service Restart
Log files rotate daily by default. To modify the rotation interval, refer to the manual configuration guide. Changes to these settings require a restart of the logging service to take effect.
Schedules
Schedules define jobs executed periodically by the Event Scheduling service based on the configured global execution interval (in milliseconds). The default interval is 1000ms. A recommended value is 10000ms (10 seconds) or higher, depending on your schedule configuration, to reduce service load. Currently available jobs are limited to database maintenance tasks for high-volume tables.
| Field | Description |
|---|---|
| Name | Custom name for the schedule. |
| Type/Job | Job to be executed. Available options: Clear Event-Log, Clear SDS-Log. |
| Schedule Hours, Minutes, Seconds | Execution interval. For example: 1 hour = hourly execution, 24 hours = daily execution. The same logic applies to minutes and seconds. |
| MaxAgeInDays | Retention threshold in days. Records older than this value will be deleted when the job executes. |
Tetra
Configure the connection settings and paths for the TETRA subscriber components.
DAMM Subscriber
| Field | Description |
|---|---|
| Path | Path to the DAMM Subscriber executable. Defaults to the installer's extraction location. Recommended to keep the default path. |
Terminal Gateway
| Field | Description |
|---|---|
| Path | Path to the Terminal Gateway Subscriber executable. Defaults to the installer's extraction location. Recommended to keep the default path. |
| TCP Reconnect Initial Delay (ms) | Initial delay before the first reconnection attempt. Default: 1000. |
| TCP Reconnect Max Delay (ms) | Maximum delay threshold. Reconnection attempts will cease after this value is reached. Default: 120000 (2 minutes). |
Gateways
Configure multiple gateways that can be selected and activated later. Refer to the Tetra Gateway section in the Configuration documentation for details.
| Field | Description |
|---|---|
| Name | Custom name for the gateway. Only alphanumeric characters are allowed (no whitespace or special characters). |
| IP | IP address of the gateway. |
| Type | Gateway type. Available options: DAMM-API (DAMM Subscriber), DAMM-TERMINAL (Terminal Gateway). |
| Port | Port number according to your gateway configuration. Default: 42380 for DAMM-API, 42381 for DAMM-TERMINAL. |
DAMM Subscriber
To use the DAMM Subscriber/DAMM API for connecting to your TETRA network, you must provide the required API DLLs. Use this interface to upload the necessary files and view currently installed DLLs in the directory.
Web
Configure the web access settings for GroundControl VGRS.
| Field | Description |
|---|---|
| Endpoint | HTTP endpoint for the web interface. Default: http://*:80 (port 80). If port 80 is unavailable, use an alternative port such as 8080. |
| Allowed Origins | Specifies which origins can access the API. Default: local origin only. |
| Token Signing Key | API authentication signing key. Must be at least 32 characters. Recommended to keep the auto-generated value. |
Multiple Instances & Remote Access
Multiple GroundControl VGRS instances can be deployed simultaneously. Refer to the System Redundancy guide for deployment scenarios, or consult the network access guide for remote access configuration.
Normal Mode
Normal mode provides access to the same configuration options described in the onboarding mode section, plus additional advanced settings.
The following pages mirror the onboarding mode configuration:
Click the links in the image captions to navigate to the detailed sections on this page.
Additional pages available exclusively in normal mode:
Services
Displays the status of installed GroundControl VGRS services. Possible states: STOPPED, START_PENDING, RUNNING. Use the buttons to start or stop individual services.
General
Provides an option to reset all custom configuration settings to their default values.
Sessions
Displays active session count and licensed session limit.
License Limitation
Without a license, the interface shows 0 of Infinite sessions in use, but only one concurrent user login is permitted.
Available actions: - Refresh session count - Clear all sessions (logs out all users)
Other
Contains miscellaneous configuration options that do not belong to a specific category.
Currently available:
Weather Warning
| Field | Description |
|---|---|
| File Location | Path to the .xml file containing weather alert data. |
| Interval in which to check the file (m) | File polling interval in minutes to detect new weather alerts. |
| Embargo duration (m) | Notification embargo period in minutes when no weather changes are detected. |
| Notification interval (s) | Delay in seconds between notifications sent to GroundControl VGRS for processing. |
Weather Warning Documentation
For detailed information on the Weather Warning feature and default values, refer to the Weather Warning documentation.