14893e62a5
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>
72 lines
2.1 KiB
Markdown
72 lines
2.1 KiB
Markdown
# Critical Structure Differences
|
|
|
|
## Working Mapping Structure (from TestMKS.set)
|
|
|
|
### Mapping Level (ID: "1"):
|
|
```
|
|
1. .SwitchMode (bool): false ← FILTER FLAG - WE'RE MISSING THIS
|
|
2. .VideoInput (bool): true ← FILTER FLAG - WE'RE MISSING THIS
|
|
3. .VideoOutput (bool): false ← FILTER FLAG - WE'RE MISSING THIS
|
|
4. @ (string): "Mapping Name"
|
|
5. @! (int32): 0
|
|
6. @@ (int32): 100
|
|
7. Rules (folder)
|
|
8. SwitchMode (int32): 0 ← ACTUAL VALUE - WE'RE MISSING THIS
|
|
9. VideoInput (int32): 101027 ← ACTUAL VALUE - WE'RE MISSING THIS
|
|
10. VideoOutput (int32): 0 ← ACTUAL VALUE - WE'RE MISSING THIS
|
|
```
|
|
|
|
### Output Action Structure (ID: "1", "2", etc.):
|
|
```
|
|
1. @ (string): "Action Caption"
|
|
2. @! (int32): 0
|
|
3. @@ (int32): 4296, 9392, etc. ← VARIES - WE USE 100
|
|
4. GscAction or GCoreAction (string): "@ ActionName (...)"
|
|
5. GscServer or GCoreServer (string): "server-alias"
|
|
```
|
|
|
|
## What Our C# Code Is Missing
|
|
|
|
### 1. Filter Flags
|
|
At the mapping level, we need to write boolean filter flags BEFORE the @ field:
|
|
- `.SwitchMode` (bool)
|
|
- `.VideoInput` (bool)
|
|
- `.VideoOutput` (bool)
|
|
|
|
These control which fields are visible/filterable in GeViSet.
|
|
|
|
### 2. Actual Field Values
|
|
AFTER the Rules folder, we need to write the actual field values:
|
|
- `SwitchMode` (int32)
|
|
- `VideoInput` (int32) - This is the camera/input ID
|
|
- `VideoOutput` (int32)
|
|
|
|
### 3. Field Order
|
|
The order is CRITICAL:
|
|
1. Filter flags (`.FieldName`)
|
|
2. Metadata (@, @!, @@)
|
|
3. Rules folder
|
|
4. Actual field values (FieldName)
|
|
|
|
### 4. Output Action IDs
|
|
Working file uses "1", "2", etc.
|
|
Need to verify if we're using "0", "1", etc.
|
|
|
|
### 5. Output Action @@ Flag
|
|
Working file uses varying values (4296, 9392), not 100.
|
|
This might be a state/flags field.
|
|
|
|
## Impact
|
|
|
|
Without filter flags and actual field values, GeViSet:
|
|
- Cannot properly identify the mapping type
|
|
- Shows actions as "CrossSwitch" (default)
|
|
- Breaks the configuration display
|
|
|
|
## Fix Required
|
|
|
|
Update `ActionMappingManager.cs` to:
|
|
1. Write filter flags before metadata
|
|
2. Write actual field values after Rules folder
|
|
3. Match the exact field order from working mappings
|