História stránky

...

• I/O tag address is mapped on Information object address, i.e. it has 3 bytes and must within the range of 0..16777215.
• Input tags must be particular types (Ai, Ci, Di, Qi) for received ASDU, see the table 1 and also the table 2 in the balanced mode.
• For particular type of output tag (Ao, Dout, Co) it is necessary to set a ASDU type, that has to be used, see the table 2.
• Archive for providing historical values: if client asks for historical values through ASDU 250, the server sends:
  1. the values of the historical value specified by this input entry field,
  2. if the input entry field is not filled, then the values of the historical value that archives the I/O tag,
  3. if given historical value does not exist, then the values of the I/O tag that archives the control object of given I/O tag,
  4. if the control object does not exist (or the archive is not available), the server returns an error.
  Specification of a historical value allows user to set e.g. sending 10-minutes averages instead of sending all changes of given I/O tag.

Browse

For the I/O tags, it is possible to discover the list of objects, as long as the KOM process is running and communication with a station is established.
Clicking the Browse button opens the IEC870-5-104 Item Browser window and displays a list of objects that have been read so far. The object list is created dynamically as a result of received messages.

The list of objects is dynamic, i.e. when a new value arrives in the KOM process, it is updated. Filtering in individual columns is also supported, asterisks can be used in the mask (e.g. *Short*).

Double-clicking on a particular line will cause the Address parameter to be inserted into the configuration of I/O tag from which the IEC870-5-104 Item Browser window was opened.

The Refresh button clears the list of values in both the CNF and the KOM process.

The Value column contains the received value.

Kotva
literatura literatura

Literature

...

Kotva
revizie revizie

Document revisions

...

• Ver. 1.0 – July 30th, 2003
• Ver. 1.1 – November 19th, 2003: extension of supported ASDU, new parameters
• Ver. 1.2 – March 20th 2004: added ASDU for reading archive data
• Ver. 1.3 – June 20th, 2004: extension - redundancy support
• Ver. 1.4 – December 1st, 2004: extension - support of balanced mode
• Ver. 1.5 - December 12th, 2012 - updating, tell commands
• Ver. 1.6 – June 15th, 2020: browsing support

...