Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Kotva
kom_di
kom_di
DI ON/OFF HOBJ/mask

Debug Info for values - enables/disables displaying information about the evaluation of:
  • I/O tag with specified HOBJ,
  • all I/O tags on the station with specified HOBJ,
  • I/O tags with the name matching the given mask,
  • all I/O tags on the stations with the names matching the given mask.
DP ON/OFFDebug Pipe - shows/hides the course of communication with D2000 KOM (only if the process window is displayed on the desktop).
GETKOMARCDEPTHGets the timestamp of the oldest data stored in the KOM Archive.
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.
Time format ("BeginTime", "EndTime") is "dd-mm-yyyy hh:mi:ss".

This feature is supported only by some communication protocols (Datalogger ESC8800, ESC8816, UNIP_TS ...).
Warning: This is not a function of KOM Archiv but it is the reading values directly from a device!

NORECALC parameter causes the archive to not execute the calculation of calculated archive objects, the values of which are calculated from the values acquired by this calling of a TELL command. For some protocols (OPC DA, OPC HDA, and IEC 870-5-104), a parameter mask "M:" can be used, which is used to read the archive values only for selected I/O tags which match the mask, from the StationName station.

Kotva
lnalterpath
lnalterpath
LNALTERPATH LineName ON|OFF OFF|PRIMARY|BACKUP|QUERY [1|2|3|4]

The command allows switching between the primary (OFF or PRIMARY) and backup (ON or BACKUP) devices for the lines of categories "SerialOverUDP Device Redundant", "SerialOverUDP Line Redundant", and "SerialOverUDP System&Line Redundant" line categories, 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.

The third parameter (numbers 1-4) specifies the subline. For a line of category "SerialOverUDP Device Redundant", it need not be specified or can must be equal to 1. For a line of 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" 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).

Example Examples of use:
LNALTERPATH L.MyLine ON 3
LNALTERPATH L.MyLine BACKUP 3
LNALTERPATH L.MyLine QUERY

Kotva
lnstat
lnstat
LNSTAT OPEN/CLOSE LineName

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/HEXEnables the decimal/hexadecimal format of line listening. The default format is hexadecimal.
READKOMARC ["BeginTime"] ["EndTime"]Reads the values from KOM Archiv. There are transferred all old values from the specified interval. The parameter BeginTime is optional and if it is not entered, the data from all 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, there will be sent just the values, which have not been sent. If at least the parameter BeginTime is defined, there will be sent all values within the specified interval.

Return codes:

  • SUCCESS - transaction successful, data transfer to the system finished,
  • IGNORED - the process D2000 KOM is not running in the mode of KOM Archiv,
  • ERROR - invalid parameters (time format: dd-mm-yyyy hh:mi:ss), wrong sequence of entered times - BeginTime > EndTime.

Kotva
reload
reload
RELOAD StationName | StationHOBJ | LineName | LineHOBJ

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:

Kotva
resetperf
resetperf
RESETPERF LineName/StationName

Resets the statistics of 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).

Kotva
setptaddr
setptaddr
SETPTADDR name "address1" "address2"

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 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:

  • SUCCESS - changed address (the value of the I/O tag is invalid until it is read from the new address).
  • IGNORED - D2000 KOM process does not support dynamic address change for the specified protocol.
  • ERROR
    1. duplicate address
    2. point not found
    3. bad address format

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 defines its new address. Change of station address will be performed only in 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:

  • SUCCESS - changed address,
  • IGNORED - D2000 KOM does not support a dynamic change of address for the specified protocol,
  • ERROR
    1. object not found
    2. invalid number of parameters

Dynamic change of address is implemented only for a limited group of communication protocols:

SHOW TAG TagName/TagHOBJ
SHOW NAN
Enables debug information for the specified I/O tag. The command requires either the name or HOBJ of the I/O tag. 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 WINNTRestarts the computer with the D2000 KOM process (the process must be running).

Kotva
stalterpath
stalterpath
STALTERPATH StationName ON|OFF

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").

Kotva
start_record
start_record
START_RECORD dir_name_only [begin_time] end_time

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:
Data files, recorded by the TELL command:
START_RECORD DirName "01-12-2008 08:22:27" "01-12-2008 11:02:07"

These four data files (it relates to four hourly intervals) are the result of recording:
KOM-SELF_2008_12_01_08.dat < 01-12-2008 08:22:27 ; 01-12-2008 09:00:00 >
KOM-SELF_2008_12_01_09.dat < 01-12-2008 09:00:00 ; 01-12-2008 10:00:00 >
KOM-SELF_2008_12_01_10.dat < 01-12-2008 10:00:00 ; 01-12-2008 11:00:00 >
KOM-SELF_2008_12_01_11.dat < 01-12-2008 11:00:00 ; 01-12-2008 11:02:07 >

Note: The TELL command uses "dd-mm-rrrr hh:mm:ss" format for the parameters of DateTime type.
It is possible to initialize this TELL command from the D2000 Server, as well as directly from the clients (currently only from the D2000 KOM and Gateway Client processes).
Data are recorded into the specified subdirectory in the application directory, where a separate data file is created for every hourly time period.

Kotva
stop_record
stop_record
STOP_RECORD

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).

Kotva
start_replay
start_replay
START_REPLAY dir_name_only [begin_time [/NOW]]
or
START_REPLAY dir_name_only /LOOP

Starts a data replaying from a subdirectory (of application directory) with the 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 data represents a particular time from the recorded time period. The time of data replaying must be from the range of the recorded time period.

Example of data replaying:
Time Stamp (TS) - blue color, current time (CT) - red color

begin_time/NOWDescription
nono
  • data are replayed immediately
  • if CT = 02-12-2008 14:11:02, data are replayed from TS >= 01-12-2008 09:11:02
  • if CT = 02-12-2008 14:33:55, data are replayed from TS >= 01-12-2008 08:33:55
yesno
  • if begin_time = 01-12-2008 08:27:27, data are replayed from time so that this time corresponds with a shift from hour
  • if CT = 02-12-2008 14:11:02, data are replayed from TS >= 01-12-2008 08:27:27, when CT = 02-12-2008 14:27:27
  • if CT = 02-12-2008 14:33:55, data are replayed from TS >= 01-12-2008 08:27:27, when CT = 02-12-2008 15:27:27
yesyes
  • if begin_time = 01-12-2008 08:27:27, the command finds the nearest time (time stamp) so that data could be replayed immediately
  • if CT = 02-12-2008 14:11:02, data are replayed from TS >= 01-12-2008 09:11:02
  • if CT = 02-12-2008 14:33:55, data are replayed from TS >= 01-12-2008 08:33:55
In this situation, also data, recorded before TS, are replayed. This data are replayed at the beginning.


If /LOOP is used, data replaying will be again started automatically. 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 DateTime type.
It is possible to start this TELL command from the D2000 Server, as well as directly from the clients (currently only from KOM client).
Process D2000 KOM can be started up in replay mode only with the start parameter /Replay. It causes, the process D2000KOM does not communicate with devices.

Kotva
stop_replay
stop_replay
STOP_REPLAY

Stops a data replaying immediately. If the replaying does not work, the error will occur.

Note: There is possible to start up this TELL command from the D2000 Server, as well as directly from the clients (currently only from KOM client).

STDOUT outputThe command redirects the standard output to a new one.

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 STDOUT command for D2000 Archiv.

STOPStops the D2000 KOM process.

Kotva
ststat
ststat
STSTAT START/STOP StationName

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.

Kotva
stwatch
stwatch
STWATCH StationName ["Number"]

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 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)

...