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>
77 lines
3.4 KiB
Markdown
77 lines
3.4 KiB
Markdown
# TACI - Telnet Action Command Interface
|
||
|
||
> Converted from `GeViScope/Additional documentation/TACI - Telnet Action Command Interface.pdf` using `pdftotext -layout`.
|
||
|
||
Plugin: TACI - Telnet Action Command
|
||
Interface
|
||
Konzept | Concept | Projet | Concepto
|
||
|
||
GeViScope provides an internal optional to send and receive actions system-wide. The normal method
|
||
of externally sending and receiving actions is provided by the GeViScope SDK. However, in a number
|
||
of situations it is not possible to use the Win32-based SDK. TACI (Telnet Action Command Interface)
|
||
thus provides an option for sending and receiving actions in ASCII format. TACI converts these ASCII
|
||
actions into normal GeViScope actions, or conversely converts GeViScope actions into ASCII format
|
||
for transmission over a Telnet port.
|
||
|
||
Gut zu wissen | Good to know | Bon à savoir | Conviene saber
|
||
|
||
Your software must be capable of sending and receiving text in ASCII format.
|
||
|
||
|
||
Use the description of the actions in the SDK to become familiar with the actions and their parameters.
|
||
The GSCPLC Simulator helps you to find the GeViScope directory.
|
||
|
||
|
||
Prozedur | Procedur | Procédure | Procedimiento
|
||
|
||
How to configure TACI
|
||
Ensure that the file GscTelnetActionCommandInterface.dll has been copied to the directory
|
||
GeViScope/Mediaplugins. Copy the file to this location if it is not already there.
|
||
|
||
In GSCSetup, open the Hardware Selection menu.
|
||
|
||
|
||
|
||
|
||
Click with the right mouse button in the list view and select Add in the popup menu.
|
||
Select the plugin GscTelnetActionCommandPlugin (in our example, Plugin 004) by marking it and
|
||
clicking on Add.
|
||
|
||
The TACI plugin is now entered as a hardware resource in the hardware module list. If you click on it,
|
||
you can set the required parameters.
|
||
|
||
|
||
|
||
|
||
The following describes the parameters:
|
||
|
||
ADVI CE
|
||
UDP is not currently implemented.
|
||
|
||
ActionFilterIn/ ActionFilterOut Regular Expression to filter incoming or outgoing
|
||
messages. * means pass all.
|
||
CommandTerminationChars Chars defining the end of a command
|
||
FormatASCIIReply Format string of the reply from TACI {0}: Return value
|
||
3: Error(No action 4: OK) {1}: Position of echo {2}:
|
||
Send termination signal at the end (CR/ LF)
|
||
FormatBinaryReply Obsolete
|
||
FormatReceivedActions {0} Position of Action in the received string
|
||
MaxTCPVonnections Maximum number of allowed TACI connections for one
|
||
server
|
||
SendAllActions Forward all actions from GeviScope to Telnet
|
||
TCPBinaryIntelByteOrder Obsolete
|
||
TCPBinaryRepyDownwardsCompatible Obsolete
|
||
TCPEnabled Obsolete
|
||
TCPPort Number of TCP Port for the telnet connection
|
||
Number of TCP Port for the telnet If set tot true you will receive an echo of your
|
||
connection command
|
||
|
||
Hello World!
|
||
After you have configured TACI as described above, simply open a Telnet connection using the
|
||
Windows Telnet program. To do this, open the CMD, tip in telnet and press enter.
|
||
Then type o [hostname] 12007 .
|
||
|
||
You can now send a simple user action, for instance CustomAction (1,"HelloWorld"). In the
|
||
PLCSimulator, you see the actions that you have sent and you can send actions from the
|
||
PLCSimulator to the Telnet clients.
|
||
|