| Debug Info for values - enables/disables displaying information about the evaluation of:
| ||||||||||||||||||||||
| DP ON/OFF | Debug Pipe - shows/hides the course of communication with the D2000 KOM (only if the process window is displayed on the desktop). | ||||||||||||||||||||||
| GETKOMARCDEPTH | Gets the timestamp of the oldest data stored in the KOM Archive. | ||||||||||||||||||||||
| Configuration check. The CHECK CERTS variant verifies the existence of certificates used in the configuration of lines (TCP/IP-TCP and TCP/IP-TCP Redundant) - it loads them from disk and lists the parameters:
This way, it is possible to verify the availability and up-to-dateness of certificates of all D2000 KOM processes in redundant systems or in systems with multiple instance D2000 KOM processes. The CHECK DIRTY variant lists those lines that operate with an outdated configuration. These are the following cases:
The mask parameter allows you to narrow the list of checked lines to those whose names match the specified mask. | ||||||||||||||||||||||
| Debug Info for values - enables/disables displaying information about the evaluation of:
Note: The /KDI<mask> startup parameter can be used to enable Debug Info at the start of the process. | ||||||||||||||||||||||
| DP ON/OFF | Debug Pipe - shows/hides the course of communication with the D2000 KOM (only if the process window is displayed on the desktop). | ||||||||||||||||||||||
| GETKOMARCDEPTH | Gets the timestamp of the oldest data stored in the KOM Archive. | ||||||||||||||||||||||
| Reads historical values from a device - StationName station. The values from the specified interval will be read. The parameter EndTime is optional, and if it is not entered, the current time will be used. Kotva | | getoldval | getoldval | GETOLDVAL StationName [M:PointMask] [NORECALC] "BeginTime" ["EndTime"]Reads historical values from a device - StationName station. The values from the specified interval will be read. The parameter EndTime is optional and if is not entered, the current time will be used.|||||||||||||||||||
| The command allows switching between the primary (OFF or PRIMARY) and backup (ON or BACKUP) devices for lines of categories "SerialOverUDP Device Redundant", "SerialOverUDP Line Redundant", and "SerialOverUDP System&Line Redundant", or discovering the active device (QUERY). The active device is used to write UDP packets, and packets received from it are processed. Data received from the inactive device is ignored. Similar functionality is also supported for lines of the "TCP/IP-TCP System Redundant" category - the TCP connection is connected to a primary or backup device. The third parameter (numbers 1-4) specifies the subline. For a line of the category "SerialOverUDP Device Redundant", it need not be specified or must be equal to 1. For a line of the category "SerialOverUDP Line Redundant", it can be equal to 1 (the device on the Primary line is set) or 2 (the device on the Secondary line is set). For a "SerialOverUDP System&Line Redundant" or "TCP/IP-TCP System Redundant" category line, it can be equal to 1 - 4 (the device on the Primary/Secondary line of the system A/B is set). If an active device is detected (QUERY) and the third parameter is not entered, all active devices are listed (1, 2, or 4, depending on the line type). The command is also applicable | on to the OPC UA Client line in the OPC Unified Architecture Data Access Client protocol for Client Type=Default. Using the command, it is possible to find out which of several specified hosts the D2000 KOM process is connected to (QUERY) or to force a connection to a specific one (ON, third parameter set to 1 .. N). The command is also applicable | on to RFC2217 Client, TCP/IP-TCP, and TCP/IP-TCP Redundant lines. With the help of the command, it is possible to find out which of several specified hosts the D2000 KOM process is connected to (QUERY, or QUERY PRIMARY/BACKUP) or to force a connection to a specific one (PRIMARY/BACKUP, third parameter set to 1 .. N). Examples of use: | ||||||||||||||||||||
| The command can be used only for the lines of Serial (asynchronous serial lines) and RFC2217 Client categories. The command stops the communication (CLOSE) and disconnects the communication port. Then the port can be used by other programs, e.g., diagnostic or configuration tools. Stations on the line are to be in the Communication error state. The communication will be recovered either using the command LNSTAT OPEN or after restarting the whole communication process. | ||||||||||||||||||||||
| LNTRACE DEC/HEX | Enables the decimal/hexadecimal format of line listening. The default format is hexadecimal. | ||||||||||||||||||||||
| Reads the values from KOM Archiv. There are transferred all All old values from the specified interval are transferred. The parameter parameter BeginTime is optional, and if it is not entered, the data from the whole history depth of KOM Archiv will be read there. The parameter EndTime is optional, and if it is not entered, the current time will be used. If the parameters BeginTime and EndTime are not defined, only the unsent values will be sent. If at least the parameter BeginTime is defined, all values within the specified interval will be sent. Return codes:
| ||||||||||||||||||||||
| The command de-configures the object (line or station) and its descendants (stations, I/O tags) and reloads them. The command can be used to apply configuration changes that would otherwise require restarting the KOM process. The command is currently implemented for protocols:
| ||||||||||||||||||||||
| Resets the statistics of a given line/station - the system structured variable SV._System_LinePerformance / SV._System_LinePerformance. It is executed immediately, but it will be visible after the process D2000 KOM sends new statistics to the process D2000 Server (periodically every 10 seconds). | ||||||||||||||||||||||
| Dynamic change of the I/O tag address. The parameter name specifies the I/O tag. It can be entered as the object name (e.g., "M.CoolantTemperature") or the object HOBJ (the syntax requires the character '$' before HOBJ, e.g., "$278"). The parameters address1 and address2 define the new I/O tag address. Change of address will be performed only in the internal data structures of the KOM process. It is not sent, in a centralized way, to the server, i.e. changed address is valid until the restart of the KOM process. After this, the value from the initial configuration will be used again. Return codes:
Dynamic change of the I/O tag address is implemented only for a limited group of communication protocols: | ||||||||||||||||||||||
| SETSTADDR StationName|StationHOBJ "address" | Dynamic change of station address. The first parameter specifies the station. It can be entered as the object name StationName (e.g., "B.Station") or station ID StationHOBJ. The "address" parameter parameter defines its new address. Change of station address will be performed only in the internal data structures of the KOM process. It is not sent, in a centralized way, to the server, i.e. changed address is valid until the restart of the KOM process. After this, the value from the initial configuration will be used again. Return codes:
Dynamic change of station address is implemented only for a limited group of communication protocols: | ||||||||||||||||||||||
| SHOW TAG TagName/TagHOBJ SHOW STATION StationName|StationHOBJ SHOW NAN | Enables debug information for the specified I/O tag/station. The command requires either the name or the HOBJ of the I/O tag/station. The debug information is usable for D2000 System developers. The SHOW NAN command displays all I/O tags whose value (current, last telemetry, or last valid) is NaN (unspecified type). | ||||||||||||||||||||||
| SHUTDOWN WINNT | Restarts the computer with the D2000 KOM process (the process must be running). | ||||||||||||||||||||||
| For the Microtel 700 protocol, it explicitly activates (ON) or deactivates (OFF) an alternative communication route for a station named StationName (e.g., "B.Station"). | ||||||||||||||||||||||
| Starts a data recording into a subdirectory (application directory) with the name dir_name_only. If the directory does not exist, it will be created. If this TELL command is run from the D2000 Server, firstly, the file dodm_values.dat containing the initialization values of DODM objects is recorded, and then the D2000 Server will send this command to clients. Data are recorded within the time period <begin_time, end_time>. If <begin_time> is not set, data are recorded immediately. Example: These four data files (it relates to the time interval spans four hourly intervals) are the result of recording: Note: The TELL command uses "dd-mm-rrrr hh:mm:ss" format for the parameters of the DateTime type. | ||||||||||||||||||||||
| Stops a data recording immediately, ; it is not necessary to wait for end_time. If the recording is not in progress, an error will be returned. Note: It is possible to start up this TELL command from the D2000 Server, as well as directly from the clients (currently only from the D2000 KOM and Gateway Client processes). | ||||||||||||||||||||||
| Starts a data replaying replay from a subdirectory (of the application directory) with the name name dir_name_only. If the directory does not exist, an error will be returned. If the command is run from the D2000 Server - at first, the dodm_values.dat file containing the initialization values of DODM objects will be recorded by the D2000 Server, and then the D2000 Server will send this command to the clients with /NOW parameter. It replays all data (in data files) with the time stamp >= begin_time. The timestamp of the data represents a particular time from the recorded time period. The time of data replaying replay must be from the range of the recorded time period. Example of data replaying:
Note: This TELL command uses the "dd-mm-rrrr hh:mm:ss" format for the parameters of DateTime type. Kotva | | stop_replay | stop_replay | STOP_REPLAYStops a data replaying immediately. If the replaying does not work, the error will occur.
|
If /LOOP is used, data replay will start automatically again. It can be stopped by the STOP_REPLAY command.
Note: This TELL command uses the "dd-mm-rrrr hh:mm:ss" format for the parameters of the DateTime type.
It is possible to start this TELL command from the D2000 Server, as well as directly from the clients (currently only from the KOM client).
The D2000 KOM process can be started up in replay mode only with the start parameter /Replay. It causes the process D2000KOM not to communicate with devices.
STOP_REPLAYKotva stop_replay stop_replay
Note: It is possible to start up this TELL command from the D2000 Server, as well as directly from the clients (currently only from the KOM client).
STCOMMANDKotva stcommand stcommand
Special, protocol-dependent commands. Currently supported are the following
IEC 870-5-104 protocol:
- STCOMMAND StationName DISCONNECT - force disconnection from server
MQTT Client protocol:
- STCOMMAND StationName PUTOLDVAL BeginTime EndTime - send old values (in Sparkplug B Edge Node mode)
OPC Data Access 2.05 & 3.0 Client protocol:
- STCOMMAND StationName DISCONNECT - force disconnection from the OPC server
- STCOMMAND StationName CONNECT_PS - force disconnection from the OPC server and connect to the primary OPC server
- STCOMMAND StationName CONNECT_BS - force disconnection from the OPC server andconnect to the secondary OPC server
Example:
D2000 on OpenVMS platform: STDOUT "_TNA2:" (output is redirected to the terminal _TNA2:)
D2000 on Windows platform: STDOUT C:\output.txt (output is redirected to the file output.txt)
Note: See a note for the STDOUT command for D2000 Archiv.
| Kotva | ||||
|---|---|---|---|---|
|
STSTAT COMERR/HARDERR StationName
The first form of the command enables the communication (the parameter START) or disables the communication (parameter STOP) with the StationName station. The station will get the StON (START) or StOFF (STOP) value.
The second form of the command sets the station's value to a communication error (StComErr or StHardErr). This form can be used for some communication protocols (e.g., KNX protocol, MQTT Client) if there is an external way to detect the outage (e.g., the value of an I/O tag serving as a watchdog doesn't come in time).
STWATCH StationName ["Number"]Kotva stwatch stwatch
For protocols based on periodic polling of I/O tags (request-response protocols): the command generates one or several requests for priority reading of all I/O tags on a specified station. The Number parameter defines the number of requests, possible value is within 1...5. If the parameter is not specified, a single request will be generated.
For protocols based on sending of changes (change-based protocols): the command generates one or several requests for the reading of all data. The command is implemented for a selected set of communication protocols:
- BACnet (sends ReadProperty, ReadPropertyMultiple, and Subscribe messages depending on the configuration of I/O tags)
- DNP3 (sends requests for reading of all configured Poll Classes specified in the configuration of station parameters and for reading of values of all objects with "Explicit read" enabled)
- IEC 60870-6 ICCP/TASE.2 (sends requests for reading values of all I/O tags)
- IEC 61850 (sends requests for reading values of all I/O tags)
- IEC 870-5-101 (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
- IEC 870-5-104 (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
- IEC 870-5-104 Server (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
- IEC 870-5-104 Sinaut (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
- OPC Data Access (sends requests for synchronous reading values of all I/O tags)
- OPC UA (sends requests for reading values of all I/O tags)