a92b909539
- Add GeViScope Bridge (C# .NET 8.0) on port 7720 - Full SDK wrapper for camera control, PTZ, actions/events - 17 REST API endpoints for GeViScope server interaction - Support for MCS (Media Channel Simulator) with 16 test channels - Real-time action/event streaming via PLC callbacks - Add GeViServer Bridge (C# .NET 8.0) on port 7710 - Integration with GeViSoft orchestration layer - Input/output control and event management - Update Python API with new routers - /api/geviscope/* - Proxy to GeViScope Bridge - /api/geviserver/* - Proxy to GeViServer Bridge - /api/excel/* - Excel import functionality - Add Flutter app GeViScope integration - GeViScopeRemoteDataSource with 17 API methods - GeViScopeBloc for state management - GeViScopeScreen with PTZ controls - App drawer navigation to GeViScope - Add SDK documentation (extracted from PDFs) - GeViScope SDK docs (7 parts + action reference) - GeViSoft SDK docs (12 chunks) - Add .mcp.json for Claude Code MCP server config Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
86 lines
3.1 KiB
Plaintext
86 lines
3.1 KiB
Plaintext
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.
|
|
|
|
G u t z u w i s s e n | G o o d t o k n o w | B o n à s a v o i r | C o n v i e n e s a b e r
|
|
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:
|
|
|
|
ADVICE
|
|
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
|
|
connection
|
|
If set tot true you will receive an echo of your
|
|
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.
|
|
|
|
|
|
|
|
|