Versions Compared

Old Version 6

changes.mady.by.user dominik.kurfner (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Reinhard Mayr (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Parameter
NameDescriptionScopeUnitDefaultNotes
OPC.GroupAddressType

Description

It defines

Specifies the format that is used to map KNX group addresses to server item IDs. 2Level - uses the two-level KNX group address format 3Level - uses the three-level KNX group address format

Scope

2level, 3level

Unit

None

Default value

3level

 

 

Parameter

OPC

.

PrefixedItemID

Description

It defines whether the leading "0"-characters shall be added to server item IDs. ON - defines that leading "0"characters are added to the item IDs of KNX group addresses OFF - defines that the item IDs of KNX group addresses do not contain leading "0"-characters

Scope

ON, OFF

Unit

None

Default value

ON

 

...

Warning

In contrast to defined parameter within the studio, this has a crucial influence on the structure of all server item IDs.

The following examples represent the same KNX datapoint:

  • OPC.GroupAddressType: 2Level -> ITEM ID = "NETx\XIO\KNX\192.168.1.1\00/0513"
  • OPC.GroupAddressType: 3Level -> ITEM ID = "NETx\XIO\KNX\192.168.1.1\00/2/001"
2level, 3levelNone3level
OPC.PrefixedItemID

Specifies whether the leading "0"

...

 

...

Parameter

-characters shall be added to server item IDs.

  • ON: leading "0"characters are added to the item IDs of KNX group addresses
  • OFF: the item IDs of KNX group addresses do not contain leading "0"-characters
Warning

This parameter has crucial influence on the structure of all server item IDs.

The following examples represent the same KNX datapoint:

  • OPC.PrefixedItemID: ON -> ITEM ID = "NETx\XIO\KNX\192.168.1.1\00/2/001"
  • OPC.PrefixedItemID: OFF -> ITEM ID = "NETx\XIO\KNX\192.168.1.1\0/2/1"

 

It defines
ON, OFFNoneON
OPC.AsyncTimeout

Description

Specifies the timeout value for asynchronous OPC queries. If no answer to an OPC query is received within this time interval, the quality of all queried datapoints will be set to UNCERTAIN.

Scope

1 -
1 – 60
Unit

Default value

s

seconds

5

 

...

Parameter

It specifies

OPC.AsyncReadFromDevice

Description

Specifies whether the response data of the asynchronous OPC value read queries ("READ") shall be read from the server's data base

,

or

whether it shall

directly be retrieved from the field device.

  • ON - the field devices are queried
  • OFF - the values are read from the server's data base

Scope

ON, OFF
Unit
None

Default value

OFF

 

 

ParameterIt specifies

OPC.AsyncRefreshFromDevice

Description

Specifies whether the response data of the asynchronous OPC value refresh queries ("REFRESH") shall be read from the server's data base

,

or

whether it shall

directly be retrieved from the field device.

  • ON - the field devices are queried
  • OFF - the values are read from the server's data base

Scope

ON, OFF

Unit

None

Default value

Parameter

OFF

 

 


It specifies
OPC.ShowETSStructure

Description

Specifies whether to show an ETS like structure within the server item tree.

  • ON - shows the ETS-like structure
  • OFF - shows the NXA-like structure
Scope
ON, OFF

Unit

None

Default value

OFF

 

...

Parameter

It specifies

OPC.QualityForValueNotSet

Description

Specifies which OPC Quality value shall be used for item values that are not yet set.

Scope

UNCERTAIN, BAD, NOT_CONNECTED

Unit

None

Default value

UNCERTAIN

...

Parameter

 


It specifies
OPC.Delimiter

Description

Specifies which delimiter shall be used for the item IDs within the server item tree.

Scope

String (" not allowed)

Unit

 

!Attention: If the parameter is set on "ON", each OPC "WRITE" command will result in sending up telegrams to the field network. In the case of KNX, up to three KNX telegrams are sent.

 

Parameter

OPC.RefreshOnEqualValue

Description

It specifies
None

Default value

\

! Following OPC parameters are available only for compatibility reasons. In future versions they may vanish.

...

Parameter

...

OPC.AsyncWriteConfirmation

...

Description

...

It specifies whether the response data of the asynchronous OPC value write queries ("WRITE") shall be read from the server's data base, or whether it shall directly be retrieved from the field device. ON - the field devices are queried OFF - the values are read from the server's data base

...

Scope

...

ON, OFF

...

Unit

...

None

...

Default value

...

OFF

\
DEPRECATED PARAMETERS – Will be removed in future releases.
OPC.RefreshOnEqualValue

Specifies whether OPC "OnDataChange" events are generated by incoming values from the field level even if the values are unchanged.

  • ON - the "OnDataChange" of events will be generated
  • OFF - the "OnDataChange" of events will be generated only with changes of
value

Scope

ON, OFF

Unit

None

Default
  • value

ON

 

!Attention: Use the following option only with caution!

 

Parameter

Example:
If the server receives two KNX telegrams with same value and same address (IP + KNX group address) and the option "OPC.RefreshOnEqualValue" is set to "OFF", the OPC "OnDataChange" event is generated only for the first telegram, since the second telegram does not cause a change of value of the datapoint. If this option is set on "ON", then two OPC "OnDataChange" events are generated.

...

ON, OFFNoneON
OPC.AllValuesValid
Description
If set to "
'
ON"
'
, server items always have the quality "
'
GOOD"
'
, even if their quality is "
'
BAD"
'
or "
'
UNCERTAIN"
'
. This option can be used for limited OPC clients that are not aware of OPC qualities other than "
'
GOOD"
'
.

Scope

ON, OFF

Unit

None

Default value

OFF
NoneOFF

Article applies to the following products:

  • NETx BMS Platform
  • NETx Multi Protocol Server