feat: Geutebruck GeViScope/GeViSoft Action Mapping System - MVP
This MVP release provides a complete full-stack solution for managing action mappings in Geutebruck's GeViScope and GeViSoft video surveillance systems. ## Features ### Flutter Web Application (Port 8081) - Modern, responsive UI for managing action mappings - Action picker dialog with full parameter configuration - Support for both GSC (GeViScope) and G-Core server actions - Consistent UI for input and output actions with edit/delete capabilities - Real-time action mapping creation, editing, and deletion - Server categorization (GSC: prefix for GeViScope, G-Core: prefix for G-Core servers) ### FastAPI REST Backend (Port 8000) - RESTful API for action mapping CRUD operations - Action template service with comprehensive action catalog (247 actions) - Server management (G-Core and GeViScope servers) - Configuration tree reading and writing - JWT authentication with role-based access control - PostgreSQL database integration ### C# SDK Bridge (gRPC, Port 50051) - Native integration with GeViSoft SDK (GeViProcAPINET_4_0.dll) - Action mapping creation with correct binary format - Support for GSC and G-Core action types - Proper Camera parameter inclusion in action strings (fixes CrossSwitch bug) - Action ID lookup table with server-specific action IDs - Configuration reading/writing via SetupClient ## Bug Fixes - **CrossSwitch Bug**: GSC and G-Core actions now correctly display camera/PTZ head parameters in GeViSet - Action strings now include Camera parameter: `@ PanLeft (Comment: "", Camera: 101028)` - Proper filter flags and VideoInput=0 for action mappings - Correct action ID assignment (4198 for GSC, 9294 for G-Core PanLeft) ## Technical Stack - **Frontend**: Flutter Web, Dart, Dio HTTP client - **Backend**: Python FastAPI, PostgreSQL, Redis - **SDK Bridge**: C# .NET 8.0, gRPC, GeViSoft SDK - **Authentication**: JWT tokens - **Configuration**: GeViSoft .set files (binary format) ## Credentials - GeViSoft/GeViScope: username=sysadmin, password=masterkey - Default admin: username=admin, password=admin123 ## Deployment All services run on localhost: - Flutter Web: http://localhost:8081 - FastAPI: http://localhost:8000 - SDK Bridge gRPC: localhost:50051 - GeViServer: localhost (default port) Generated with Claude Code (https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
105
geutebruck-api/docs/GEVISCOPE_VS_GCORE_SERVERS.md
Normal file
105
geutebruck-api/docs/GEVISCOPE_VS_GCORE_SERVERS.md
Normal file
@@ -0,0 +1,105 @@
|
||||
# GeViScope vs G-Core Server Configuration
|
||||
|
||||
## Storage Locations in TestMKS.set
|
||||
|
||||
- **G-Core Servers**: `GeViGCoreServer` folder
|
||||
- **GeViScope Servers**: `GeViGscServer` folder
|
||||
|
||||
## Field Comparison
|
||||
|
||||
### Common Fields (Both Server Types)
|
||||
|
||||
| Field | Type | Description |
|
||||
|-------|------|-------------|
|
||||
| Alias | string | Server display name |
|
||||
| Host | string | Server hostname or IP address |
|
||||
| User | string | Username for authentication |
|
||||
| Password | string | Password (appears to be hashed) |
|
||||
| Enabled | bool | Whether server is enabled |
|
||||
| DeactivateEcho | bool | Disable echo functionality |
|
||||
| DeactivateLiveCheck | bool | Disable live connection checking |
|
||||
|
||||
### GeViScope-Only Fields
|
||||
|
||||
| Field | Type | Description |
|
||||
|-------|------|-------------|
|
||||
| DialUpBroadcastAware | bool | Dial-up broadcast awareness |
|
||||
| DialUpConnection | bool | Use dial-up connection |
|
||||
| DialUpCPAConnection | bool | CPA connection via dial-up |
|
||||
| DialUpCPAConnectionInterval | int32 | CPA connection interval (seconds) |
|
||||
| DialUpCPATimeSettings | int32 | CPA time settings bitmap |
|
||||
| DialUpKeepAlive | bool | Keep dial-up connection alive |
|
||||
| DialUpKeepAliveRetrigger | bool | Retrigger keep-alive |
|
||||
| DialUpKeepAliveTime | int32 | Keep-alive time (seconds) |
|
||||
|
||||
### G-Core-Only Fields
|
||||
|
||||
None - G-Core servers only have the common fields.
|
||||
|
||||
## Example Configurations
|
||||
|
||||
### GeViScope Server (from test config)
|
||||
|
||||
```json
|
||||
{
|
||||
"id": "1",
|
||||
"alias": "GEVISCOPE_01",
|
||||
"host": "localhost",
|
||||
"user": "sysadmin",
|
||||
"password": "f5296f4dfae3f1c137e146b11e2480d8",
|
||||
"enabled": false,
|
||||
"deactivate_echo": false,
|
||||
"deactivate_live_check": false,
|
||||
"dialup_broadcast_aware": false,
|
||||
"dialup_connection": false,
|
||||
"dialup_cpa_connection": false,
|
||||
"dialup_cpa_connection_interval": 3600,
|
||||
"dialup_cpa_time_settings": 16777215,
|
||||
"dialup_keep_alive": false,
|
||||
"dialup_keep_alive_retrigger": false,
|
||||
"dialup_keep_alive_time": 10
|
||||
}
|
||||
```
|
||||
|
||||
### G-Core Server (for comparison)
|
||||
|
||||
```json
|
||||
{
|
||||
"id": "1",
|
||||
"alias": "gscope-cdu-3",
|
||||
"host": "10.240.130.81",
|
||||
"user": "sysadmin",
|
||||
"password": "hashed_password",
|
||||
"enabled": false,
|
||||
"deactivate_echo": false,
|
||||
"deactivate_live_check": false
|
||||
}
|
||||
```
|
||||
|
||||
## Global Settings in GeViGscServer Folder
|
||||
|
||||
The `GeViGscServer` folder also contains global dial-up settings (not per-server):
|
||||
|
||||
- `DialUpCPADay0` through `DialUpCPADay6` (int32): CPA settings for each day of week
|
||||
- `DialUpCPAResponseWindow` (int32): CPA response window in milliseconds
|
||||
- `DialUpCPAThreshold` (int32): CPA threshold percentage
|
||||
- `DialUpLimitActionCount` (int32): Maximum action count
|
||||
- `DialUpLimitTimeDepth` (int32): Time depth limit in seconds
|
||||
- `DialUpWorkerThreads` (int32): Number of worker threads
|
||||
- `FailoverActive` (bool): Whether failover is active
|
||||
|
||||
## REST API Implementation Plan
|
||||
|
||||
Need to implement similar CRUD endpoints for GeViScope servers:
|
||||
|
||||
- `GET /api/v1/configuration/geviscope-servers` - List all GeViScope servers
|
||||
- `GET /api/v1/configuration/geviscope-servers/{id}` - Get specific server
|
||||
- `POST /api/v1/configuration/geviscope-servers` - Create new server
|
||||
- `PUT /api/v1/configuration/geviscope-servers/{id}` - Update server
|
||||
- `DELETE /api/v1/configuration/geviscope-servers/{id}` - Delete server
|
||||
|
||||
Implementation will reuse the same patterns as G-Core servers but work with the `GeViGscServer` folder and additional dial-up fields.
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: 2025-12-17
|
||||
Reference in New Issue
Block a user