Porovnávané verzie

Stará verzia 31

changes.mady.by.user D2000 Dev Team

Uložené

porovnané s

Nová verzia Aktuálny

changes.mady.by.user D2000 Dev Team

Uložené

Kľúč

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

...

The next message sent by the client is "OpenSecureChannel message". It is used to establish a communication channel to exchange data. In this message, the client and server agree on what type of encrypting and signing mode will be used (either "sign and encrypt" or "encrypt" only). OPCUA client in the D2000 System supports only unencrypted mode.

...

After activating the session, all types of messages that are intended for object management in the address space of the OPC UA server can be swapped. In this step, the client creates a subscription with the parameters set on the communication station level for all stations within the communication line.

The monitored items should be then inserted into these subscriptions. They correspond with the instances of I/O tags, which contain the parameters defined in the address dialog window.

From this moment, the server informs the client about the changes in the monitored objects by

Kotva
publish_message
publish_message
"Publish message" in the periodic intervals (that have been set in the parameters of the subscription). If the monitored objects have not been changed, the server will send a "Publish message" once in (Max KeepAlive Count * Publishing Interval) seconds. The message informs the client that the subscription is is still active. A similar check mechanism is also on the client - side - it will send a "Publish request" once every (Max KeepAlive Count * Publishing Interval). If the client does not send the acknowledgment "Publish message" within (LifeTime Count * Publishing Interval), the subscription will expire on the side of the server.

...

  • Simatic S-7 OPC UA Server
  • Bernecker PLC embedded OPC UA Server
  • Zenon OPC UA Server

...

Forced disconnection: If all stations on the line are in the simulation mode or the communication is stopped for them, the line will be disconnected (the communication socket will be closed). If the simulation is disabled for at least one station and the communication is not stopped for it (the Parameters tab of the Station type object), the line will be connected again.

Kotva
komunikacna_linka
komunikacna_linka
Communication line configuration

...


Communication line category: OPC UA Client
Host address: OPC UA server address. You may set the name

...

Communication line category: OPC UA Client
Host address: OPC UA server address. You may set the name according to UNC convention (e.g. "\\server" or "server", DNS names (e.g. "domain.com", "example.company.com") or IP address ("196.54.23.113").  In the case of redundant systems, multiple names/addresses separated by commas or semicolons can be entered.
The usage of the alternative path (the second or following name/address) is signalized by the FLB flag and a combination of FLN, FLO, FLP flags in the station value.
TCP port: TCP port of OPC UA server (e.g. 4840).
EndpointUrl: Endpoint address (e.g. opc.tcp://localhost:4840)
Encoding type: Type of encoding that is used for data exchange (currently only Binary encoding is supported).

...

Debug Threads
Parameter nameMeaningUnitDefault value

Kotva
ct
ct
Client Type

Type of used client (driver for OPC UA communication):

  • Default - an original implementation of OPC UA client. Supports authentication (parameter Authentication Type) of Anonymous/Username types only. It does not support message encryption or signing.
  • Secure - a new implementation of OPC UA client with security support. Supports advanced authentication, encryption, and message signing capabilities.

Default

Secure

Default

Kotva
sn
sn
Session Name

Session text identifier. Session identifier should be unique within the client instance, making it possible to search problems faster in the client or server logs.StringKom process
Kotva
cl
cl
Requested Channel Lifetime
The channel must be reopened before this time limit elapses. If the time is exceeded, the channel will be closed and unable to change data.hh:mm:ss01:00:00
Kotva
st
st
Requested Session Timeout
Any message should be changed between client and server before this time limit elapses. If it is not sent, the sources within the session that are kept on the server are released. The primary work of this parameter is to remove the sessions that became inactive because of some unexpected reason.mm:ss01:00
Kotva
at
at
Authentication Type
Type of authentication used with the OPC UA server. Supported types are:
  • Anonymous: logon is anonymous
  • Username: logon uses user name and password
  • Certificate: logon uses x509 certificate (only for Client Type = Secure)
Anonymous / UsernameAnonymous
Kotva
tun
tun
Token User Name
If Authentication type = Username, then user name used in the authentication.
If Authentication type = Certificate, then path to user certificate (e.g. D:\user_cert.der).

Kotva
pwd
pwd
Token Password
If Authentication type = Username, then password used in the authentication.
If Authentication type = Certificate, then path to user private key (e.g. D:\user_private_key.pem).

Kotva
sp
sp
Security Policy

Security policy (only for Client Type = Secure; for Client Type = Default a security policy None is used):

  • None - security policy None
  • Basic128Rsa15 - security policy Basic128Rsa15 (considered to be obsolete due to using a weak SHA-1 hashing algorithm)
  • Basic256 - security policy Basic256 (considered to be obsolete due to using a weak SHA-1 hashing algorithm)
  • Basic256Sha256 - security policy Basic256Sha256
  • Aes128Sha256RsaOaep - security policy Aes128Sha256RsaOaep
  • Aes256Sha256RsaPss - security policy Aes256Sha256RsaPss
None
Basic128Rsa15
Basic256
Basic256Sha256
Aes128Sha256RsaOaep
Aes256Sha256RsaPss		None

Kotva
sm
sm
SecurityMode

A mode of message security in OPC UA communication (only for Client Type = Secure; for Client Type = Default a mode of message security None is used):

  • None - messages are not secured 
  • Sign - messages are signed (protected against modification, but not against eavesdropping)
  • Sign & Encrypt- messages are signed and encrypted (protected both against modification and eavesdropping)
None
Sign
Sign & Encrypt		None

Kotva
ppi
ppi
Preferred Policy Id

Identifier of preferred Security Policy (only for Client Type = Default for password encryption). If the OPC UA offers several security policies, it is possible to select a specific one according to the identifier sent by the OPC server (the identifier can be found from the logs). Examples of an identifier (text form is in parentheses):
PolicyId: 30 (0)
PolicyId: 31 (1)
PolicyId: 75 73 65 72 6E 61 6D 65 5F 62 61 73 69 63 31 32 38 52 73 61 31 35 (username_basic128Rsa15)
PolicyId: 75 73 65 72 6E 61 6D 65 5F 62 61 73 69 63 32 35 36 53 68 61 32 35 36 (username_basic256Sha256)		--

Kotva
rcd
rcd
Reconnect Delay

Waiting after the connection is broken before the connection is re-established.mm:ss.mss00:10.000

Kotva
ecd
ecd
Error Connect Delay

Waiting after an unsuccessful connection attempt.mm:ss.mss00:02.000

Kotva
dmorddm
Debug Mode

It changes the number of information about communication. We recommend enabling the Extended/Full modes only when detecting the problems and debugging the communication. The "Full + Trace (Secure only)" mode is valid only for Client Type = Secure.Normal/Extended/Full/
Full + Trace (Secure only)		Normal
Kotva
dtdtThe parameter defines the thread(s) that will send the debug info about the communication.Receiving/Sending/Others treads/All threadsAll threads

Note: all X509 certificates used in OPC UA communication can be found in the following subdirectories of the kom-opcua directory in the application directory:

  • own - a directory with KOM process's own certificate (file cert.der). If this file does not exist, it is generated
    Warning - this automatically generated certificate will only be valid for 1 year, so we recommend replacing it with a certificate valid for a longer period!
  • private - a directory with a private key for the KOM process own certificate (file private.pem)
  • rejected - a directory with rejected certificates
  • trusted - a directory with trusted certificates (the first time a connection is established to an OPC UA server, its certificate is stored in this directory)

...

ord
Object Reinit Delay

Waiting after an unsuccessful attempt to create monitored items. If it is zero, the attempt is not repeated. If it is non-zero, the attempt is repeated after the defined wait.
Note: in the case of a specific OPC UA server (Simatic S-7), it could happen that after restarting the PLC the creation of monitored items failed, but after some time (after the complete initialization of the PLC?) the creation was already successful.

sec0

Kotva
dsf
dsf
Disconnect On ServiceFault

Terminating the connection after receiving a ServiceFault.YES/NONO

Kotva
dm
dm
Debug Mode

It changes the number of information about communication. We recommend enabling the Extended/Full modes only when detecting the problems and debugging the communication. The "Full + Trace (Secure only)" mode is valid only for Client Type = Secure.Normal/Extended/Full/
Full + Trace (Secure only)		Normal
Kotva
dt
dt
Debug Threads
The parameter defines the thread(s) that will send the debug info about the communication.Receiving/Sending/Others treads/All threadsAll threads

Note: all X509 certificates used in OPC UA communication can be found in the following subdirectories of the kom-opcua directory in the application directory:

  • own - a directory with KOM process's own certificate (file cert.der). If this file does not exist, it is generated
    Warning - this automatically generated certificate will only be valid for 1 year, so we recommend replacing it with a certificate valid for a longer period!
  • private - a directory with a private key for the KOM process own certificate (file private.pem)
  • rejected - a directory with rejected certificates
  • trusted - a directory with trusted certificates (the first time a connection is established to an OPC UA server, its certificate is stored in this directory)

Kotva
protokol_komunikacna_stanica
protokol_komunikacna_stanica
Protocol configuration on the communication station

...


The parameters on the level of the communication station correspond with the setting of one subscription. It means the one communication station is equivalent to one instance of a subscription within the session.


Full nameDescriptionUnitDefault value
Kotva
subrpi
subrpi
Requested Publishing Interval

Defines the time interval for the server to send the information about the change of monitored items within the instance subscription by "Publish message".
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer always returned a value of "Publishing Interval" at least 50 ms, although the requested interval was smaller.

mi:ss.mss00:05.000
Kotva
subrlc
subrlc
Requested LifeTime Count

If the client does not send the request for data till the time defined by (LifeTime Count * Publishing Interval), the subscription expires. The value should be minimally 3 times higher than the "Requested Max KeepAlive Count

...

The parameters on the level of the communication station correspond with the setting of one subscription. It means the one communication station is equivalent to one instance of a subscription within the session.

Requested Publishing Interval

Defines the time interval for the server to send the information about the change of monitored items within the instance subscription by "Publish message".
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer always returned as a value of "Publishing Interval" at least 50 msLifeTime Count" a maximum of 600, although the requested interval was smaller.

Max Notifications Per PublishPublishing EnabledPrioritySamples Queue SizeRead TimestampWrite Timestamp

Timestamps used to write a value:

  • None - no timestamp is set
  • Source - SourceTimestamp is set (equal to the timestamp of written value)
  • Server - ServerTimestamp is set (equal to current time)
  • Both - both SourceTimestamp and ServerTimestamp are set
Note: If the OPC server does not support the writing of timestamps, according to the standard .Write Status CodeStatusCode item will be used when writing According to the standard, the OPC UA Wrapper returns the Bad_WriteNotSupported (2155020288) error code if the StatusCode entry is used when writing to the OPC DA Server version 2.05a.YESwwaWrite Whole ArrayNO
Full nameDescriptionUnitDefault value
Kotva
subrpisubrpimi:ss.mss

value was greater.

Number100000:05.000
Kotva
subrlcsubrmkcsubrlc
subrmkc
Requested LifeTime Max KeepAlive Count

If the client does not send the request for data till the time defined by (LifeTime Count objects of subscription are not changed, the server will send a keep-alive message after elapsing the time (Max Notifications Per Publish * Publishing Interval), the subscription expires. The value should be minimally 3 times higher than the "Requested Max KeepAlive Count". The client will confirm this message when it sends a new request for data.
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer has always returned as a value of "LifeTime Max KeepAlive Count" a maximum of 600200, although the requested value was greater.

Number10005
Kotva
subrmkcmnppsubrmkc
mnpp
Requested Max KeepAlive Count

If the objects of subscription are not changed, the server will send a keep-alive message after elapsing the time (Max Notifications Per Publish * Publishing Interval). The client will confirm this message when it sends a new request for data.
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer has always returned as a value of "Max KeepAlive Count" a maximum of 200, although the requested value was greater.

Number5
Kotva
mnppmnppThe parameter defines the maximum number of notifications about the object change, which the server can send in one "Publish message". Zero indicates that the number of notifications is unlimited.Number0
Kotva
pepeThe parameter enables/disables the publishing within the subscription.YES/NOYES
Kotva
ppIt defines a relative priority of a subscription. If the server should send more notifications, the subscription with higher priority is preferred.0-2550
Kotva
mqsmqsThis parameter enables creating an object queue with the defined length on the OPC UA server's side for each monitored item in a subscription.Number0
Notifications Per Publish
The parameter defines the maximum number of notifications about the object change, which the server can send in one "Publish message". Zero indicates that the number of notifications is unlimited.Number0
Kotva
pe
pe
Publishing Enabled
The parameter enables/disables the publishing within the subscription.YES/NOYES
Kotva
p
p
Priority
It defines a relative priority of a subscription. If the server should send more notifications, the subscription with higher priority is preferred.0-2550

Kotva
mqs
mqs
Samples Queue Size

This parameter enables creating an object queue with the defined length on the OPC UA server's side for each monitored item in a subscription.Number0

Kotva
rt
rt
Read Timestamp

Timestamps used while reading a value:

  • None - timestamp received from OPC server is not used (value will be timestamped by the current time)
  • Source - SourceTimestamp is used
  • Server - ServerTimestamp is used (default)
  • Newer - newer timestamp is used (SourceTimestamp or ServerTimestamp)
-Server

Kotva
wt
wt
Write Timestamp

Timestamps used to write a value:

  • None - no timestamp is set
  • Source - SourceTimestamp is set (equal to the timestamp of written value)
  • Server - ServerTimestamp is set (equal to current time)
  • Both - both SourceTimestamp and ServerTimestamp are set

Note: If the OPC server does not support the writing of timestamps, according to the standard it should return the Bad_WriteNotSupported (2155020288) error code.

-None

Kotva
wsc
wsc
Write Status Code

StatusCode item will be used when writing.
Note: According to the standard, the OPC UA Wrapper returns the Bad_WriteNotSupported (2155020288) error code if the StatusCode entry is used when writing to the OPC DA Server version 2.05a.		YES/NOYES

Kotva
wwa
wwa
Write Whole Array

When an item of an array is written, the entire array is read first and then written. If this parameter is set to NO, only a specific array item is written,
Note: According to the standard, if the OPC server does not support writing a specific array item,
Kotva
rtrt

Timestamps used while reading a value:

  • None - timestamp received from OPC server is not used (value will be timestamped by the current time)
  • Source - SourceTimestamp is used
  • Server - ServerTimestamp is used (default)
-Server
Kotva
wtwt it should return the Bad_WriteNotSupported (2155020288) error code-None
Kotva
wscwsc.
Note: 		If this parameter is active, the "Write only" parameter must not be set at the I/O tag which addresses an item of the array.YES/NONO

Kotva

aot

wwaWhen an item of an array is written, the entire array is read first and then written. If this parameter is set to NO, only a specific array item is written,
Note: According to the standard, if the OPC server does not support writing a specific array item, it should return the Bad_WriteNotSupported (2155020288) error code.
Note: If this parameter is active, the "Write only" parameter must not be set at the I/O tag which addresses an item of the array.		YES/NO

aot
Accept Older Time

Values that are not older than the specified time interval (compared to the timestamp of the current value of the I/O tag) will be accepted. After writing, it may happen that the value read back is older (usually by several ms) compared to the time of writing unless the communication computer and the OPC UA server have exact time synchronization. Error messages may appear in the line log:
Ignoring value for I/O tag <name>, current timestamp=<current_time> is newer than received <old_time>
Increasing the value of the Accept Older Time parameter will cause such older values to be processed and the error message to be suppressed.

hh:mi:ss00:00:00

Kotva
rm
rm
Read Mode

A way of reading values:

  • Subscribe: communication via subscriptions and notifications (standard)
  • Subscribe + Read: like Subscribe, in addition, periodic Read requests are sent (according to the time parameters of the station)
  • Read: send Read requests only

Note: The Subscribe+Read and Read modes should only be used if there is a problem with standard communication, as they are less efficient and have a higher overhead.

Subscribe
Subscribe+Read
Read		Subscribe

Kotva
nf
nf
No Filter

Ignoring filter parameters in the I/O tag configuration (Sampling type, DeadBand type, Trigger type).
In the specific case, the OPC UA server did not work correctly if monitored items with the specified filter parameters were inserted into the subscription.

YES/NONO

Kotva
mpp
mpp
Max Pending Publish Requests

The maximum number of consecutive unconfirmed Publish requests (to which OPC UA server does not reply with a Publish Message), after which the connection will be closed. A value of 0 causes the connection to not be closed.
Note: This parameter can be used to speed up the detection of a broken connection to the OPC UA server.		-0


Kotva
protokol_merany_bod
protokol_merany_bod
I/O tag configuration

...

Note: In versions from 17th December 2018 and newer, the recycling of browser dialog has been implemented. If the dialog is closed by the Close button or after selecting a tag, it is actually only hidden and it is available for browsing by another I/O tag within the same station so that the tree structure of the browsed objects is preserved. Clicking on the close icon at the top right corner will cause the dialog to be really closed.

Image Added

"Copy tags" button or a keyboard shortcut Ctrl+C copies the names of the browsed objects is preserved. Clicking on the close icon at the top right corner will cause the dialog to be really closed.

Image Removed

tags in a selected branch into the Windows clipboard. All tags will be copied unless a specific tag is selected.

"Copy tree" button or a keyboard shortcut Ctrl+Shift+C copies the names of tags and their addresses in all browsed branches into the Windows clipboard.

Checking the "Structured tags" option causes the variables (tags) to appear in the tree structure in addition to the objects, and the KOM process also attempts to read their descendants. This is useful for browsing OPC UA servers that support structured tags. You can also insert a tag into the address dialog window of the I/O tag by double-clicking the tag name in the tree structure.

Image RemovedImage Added

Kotva
tell_cmd
tell_cmd
Tell commands

...


Tell
CommandSyntaxMeaning
STWATCHSTWATCH StationNameThe command sends commands for the reading of values of all configured I/O tag
LNALTERPATH

LNALTERPATH LineName QUERY

LNALTERPATH LineName 1|2|3|4

The command finds out which of the IP addresses configured on the line (1..4) the D2000 KOM process is connected to.

The command breaks the current connection and connects to the IP address whose order is in the command (1..4).



Kotva
literatura
literatura
Literature

...