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>
118 lines
6.0 KiB
HTML
118 lines
6.0 KiB
HTML
<!DOCTYPE html>
|
|
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" lang="en" xml:lang="en" data-mc-search-type="Stem" data-mc-help-system-file-name="index.xml" data-mc-path-to-help-system="../" data-mc-target-type="WebHelp2" data-mc-runtime-file-type="Topic" data-mc-preload-images="false" data-mc-in-preview-mode="false" data-mc-toc-path="">
|
|
<!-- saved from url=(0014)about:internet -->
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>The media data loop
|
|
</title>
|
|
<link href="Resources/TableStyles/Rows.css" rel="stylesheet" />
|
|
<link href="../Skins/Default/Stylesheets/TextEffects.css" rel="stylesheet" />
|
|
<link href="../Skins/Default/Stylesheets/Topic.css" rel="stylesheet" />
|
|
<link href="Resources/Stylesheets/Styles.css" rel="stylesheet" />
|
|
<script src="../Resources/Scripts/jquery.min.js">
|
|
</script>
|
|
<script src="../Resources/Scripts/plugins.min.js">
|
|
</script>
|
|
<script src="../Resources/Scripts/require.min.js">
|
|
</script>
|
|
<script src="../Resources/Scripts/require.config.js">
|
|
</script>
|
|
<script src="../Resources/Scripts/MadCapAll.js">
|
|
</script>
|
|
</head>
|
|
<body>
|
|
<h2>The media data loop
|
|
</h2>
|
|
<p>Each device that is registered gets its own
|
|
thread in which the media data loop (function MediaDataLoop) is running. The
|
|
media data loop is an endless loop that handles server requests and fulfills the
|
|
purpose of the plugin. The server calls the media data loop after startup for
|
|
each device instance.
|
|
</p>
|
|
<p> </p>
|
|
<p>The first thing that a media data loop
|
|
should do is waiting for valid plugin device settings. The following example
|
|
(in pseudo code) should demonstrate this:
|
|
</p>
|
|
<p> </p>
|
|
<p class="CODEetc" style="margin-left: 25px;"><span style="color: #008000;">// wait until the settings for the plugin device are
|
|
available</span> <![CDATA[ ]]></p>
|
|
<p class="CODEetc" style="margin-left: 25px;"><span style="color: #4169e1;">if </span>(WaitForNewSettingsOrAbort() == peStop) <span style="color: #4169e1;">return</span>; <span style="color: #008000;">// Leave loop on
|
|
stop request</span> <![CDATA[ ]]></p>
|
|
<p class="CODEetc" style="margin-left: 25px;">ReadNewSettings(); <span style="color: #008000;">// Read initial device settings</span> <![CDATA[ ]]></p>
|
|
<p> </p>
|
|
<p>After doing internal device instance
|
|
creation or device instance initialization the endless loop should follow. The
|
|
endless loop waits for events, that the server fires. The events are defined by
|
|
the help of a filter definition. Here is an example (in pseudo code) for this:
|
|
</p>
|
|
<p> </p>
|
|
<p class="CODEetc" style="margin-left: 25px;">PluginNextEventFilter filter =
|
|
</p>
|
|
<p class="CODEetc" style="margin-left: 25px;"><span style="color: #4169e1;">static_cast</span><PluginNextEventFilter>(pefNewSettings
|
|
| pefCreateNewVideoData);
|
|
</p>
|
|
<p class="CODEetc" style="margin-left: 25px;"> </p>
|
|
<p class="CODEetc" style="margin-left: 25px;"><span style="color: #008000;">// here the media data loop starts</span> <![CDATA[ ]]></p>
|
|
<p class="CODEetc" style="margin-left: 25px;"><span style="color: #4169e1;">for </span>(;;)
|
|
</p>
|
|
<p class="CODEetc" style="margin-left: 25px;">{
|
|
</p>
|
|
<p class="CODEetc" style="margin-left: 50px;"><span style="color: #008000;">// wait until the server fires the next event for this
|
|
plugin</span> <![CDATA[ ]]></p>
|
|
<p class="CODEetc" style="margin-left: 50px;">PluginNextEvent pluginEvent = simpleDevice->WaitForNextEvent(filter);
|
|
</p>
|
|
<p class="CODEetc" style="margin-left: 50px;"><span style="color: #4169e1;">switch </span>(pluginEvent)
|
|
</p>
|
|
<p class="CODEetc" style="margin-left: 50px;">{
|
|
</p>
|
|
<p> </p>
|
|
<p>The following types of server events are
|
|
actually supported (not a complete list):
|
|
</p>
|
|
<p> </p>
|
|
<table style="caption-side: top;mc-table-style: url('Resources/TableStyles/Rows.css');" class="TableStyle_Rows" cellspacing="0">
|
|
<col style="width: 140px;" />
|
|
<col style="width: 439px;" />
|
|
<thead>
|
|
<tr>
|
|
<th class="TableStyle_Rows_Head_0_0_RowSep_ColSep">Method
|
|
</th>
|
|
<th class="TableStyle_Rows_Head_0_0_RowSep_ColEnd">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td class="TableStyle_Rows_Body_0_0_RowSep_ColSep">peCreateNewVideoData
|
|
</td>
|
|
<td class="TableStyle_Rows_Body_0_0_RowSep_ColEnd">The server requests a new image from the
|
|
plugin
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td class="TableStyle_Rows_Body_1_0_RowSep_ColSep">peNewSettings
|
|
</td>
|
|
<td class="TableStyle_Rows_Body_1_0_RowSep_ColEnd">The server notifies the plugin about new
|
|
settings, that are available
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td class="TableStyle_Rows_Body_0_0_RowSep_ColSep">peNewDeviceTask
|
|
</td>
|
|
<td class="TableStyle_Rows_Body_0_0_RowSep_ColEnd">The server notifies the plugin about new
|
|
task settings especially for this device
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td class="TableStyle_Rows_Body_1_0_RowEnd_ColSep">peStop
|
|
</td>
|
|
<td class="TableStyle_Rows_Body_1_0_RowEnd_ColEnd">The server notifies the plugin, that the
|
|
plugin should stop its media data loop
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p> </p>
|
|
</body>
|
|
</html> |