Telnet Action Command Interface (TACI)
Subject to license
G-Core provides an internal optional to send and receive actions system-wide. The normal method of externally sending and receiving actions is provided by the G-Core 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 G-Core actions, or conversely converts G-Core actions into ASCII format for transmission over a Telnet port.
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.
Add the Plugin
-
Ensure that the files TelnetActionCommandInterface.dll, TelnetActionCommandInterface.dlg.dlland MediaPluginLoaderNet.dll has been copied to the directory GCore/Mediaplugins. Copy the files to this location if they are not already there.
After copying these files to the G-Core directory you must restart the server.
-
In G-Set, open the Hardware Selection menu.
-
Click with the right mouse button in the list view and select Add in the pop-up menu.
-
Select the Plugin <Telnet Action Command Interface> 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.
Configuration
The TACI plugin has two TCP action servers. They can be configured on the two tabs G-Core TACI and G-Core GeViScope TACI.
G-Core TACI dialog after installing:
G-Core GeViScope TACI dialog after installing:
The TCP Action Server, which can be configured in the G-Core TACI register, expects actions in G-Core format and also responds with G-Core actions.
At the same time, actions in GeViScope format can also be processed. For this purpose a second Action Server is instantiated, which is configured in the G-Core GeViScope TACI register.
|
Action server |
TCP/UDP default port |
Characteristics |
|---|---|---|
|
G-Core TACI |
13007 |
Responds with actions in the G-Core format |
|
G-Core GeViScope TACI |
12007 |
Responds with actions in the GeViScope format |
UDP is not supported yet.
The following table describes the parameters:
|
Name |
Description |
|---|---|
|
Action in filter in |
Regular expression to filter incoming commands |
|
Action in filter out |
Regular expression to filter outgoing commands |
|
Command termination chars |
Characters that define the end of the command |
|
Format ASCII reply |
Format string of the reply from TACIIn {0} the return value is entered. Value 3 is for an error (no action) and a value of 4 means OK.In {1} the received text is entered.In {2} characters are added that define an end. |
|
Format binary reply |
Outdated |
|
Format received actions |
Defines the format of the received action within the text. {0} contains the action. |
|
MaxTCPConnections |
Defines the maximum number of allowed TCP client connections |
|
SendAllActions |
Actions are sent to the G-Core server |
|
TCP binary Intel byte order |
Outdated |
|
TCP binary reply downwards compatible |
Outdated |
|
TCP enabled |
Enables or disables the TCP action server |
|
TCP port |
Number of TCP port for the telnet connection |
Example
Examples for regular expressions (regex) to filter outgoing commands:
Example 1
Action out filter regex:(CustomAction)(.*)
Filter to the following Custom Action:
CustomAction (<any kind of content>)
CustomActionEx (<any kind of content>)
Example 2
Action out filter regex:(CustomAction)(.)(1234)(.)("abcd")(.*)
Filter to the following Custom Action:
CustomAction (Int: 1234, String: "abcd")
To test the settings, the Windows console can be used. In the Run window, telnet, followed by the IP address and the port of the destination, is entered.
Actions can then be sent. For this purpose, the entire action must be entered and confirmed with the Enter key: CustomAction (Int: 0, String: "Sent from telnet client").
The TACI client receives the transmitted action as response with a status value (line 2) and then receives the action distributed by the server (line 3).
In the G-PLC simulator you can also seen whether the action has arrived:
Similarly, actions can be sent by the G-PLC simulator:
If you connect with telnet to the port of the G-Core GeViScope TACI (Port 12007), actions can be received in GeViScope format.
Actions in GeViScope format can be sent to both TACIs!
|
Action |
Format |
Action String |
|---|---|---|
| CustomAction | G-Core | CustomAction (Int: 0, String: "Sent from telnet client") |
| CustomAction | GeViScope | CustomAction (0, "Sent from telnet client") |