Porovnávané verzie

Kľúč

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

...

  • Communication line category: TCP/IP-UDP, LonWorks, Serial, SerialOverUDP Device Redundant.
  • TCP/IP-UDP parameters:
    • Host: IP address or of network interface that is used for communication by KOM process. A symbolic name that can be translated to an IP address can be entered too.
      Note: a symbolic name ALL can be entered - in which case all available interfaces are used.
    • Port: UDP port number that is used for communication by KOM process (according to standard 0xBAC0, i.e. 47808).

Note: The parameters of backup server (Host and Port) are not used in this protocol.


Line protocol parameters

KeywordFull nameMeaningUnitDefault value
Kotva
dbgi
dbgi
DBGI
Debug InputDebug information about the input data. Meaning of the bits:
  • 1. bit - debugging of  ASN message parsing
  • 2. bit - debugging of the I/O tag names that received a new value
  • next bits - not used
-0
Kotva
dtq
dtq
DTQ
Debug Timeout QueueDebug information about messages in time queue.-False
Kotva
di
di
DI
Device InstanceNon-zero value causes that KOM process answers to Who-Is request by I-Am message. It contains a defined Device Instance. Zero value causes that Who-Is request is ignored.-0
Kotva
rb
rb
RB
Receive Buffer(only for for TCP/IP-UDP line line) Size of received buffer which is set on UDP socket. Zero value means the buffer size remains unchanged. 8192 bytes is a normal size in Windows. If there are more stations or more intensive communication, the buffer should be enlarged.bytes0
Kotva
ro
ro
RO
Receive OnlyIf value is True, any messages are not sent to any station on the line. This parameter may be used when listening the communication LonTalk: Configure the address, which is the same as the address of existing LonTalk device, on the line. Also configure the station with the device address which communication you need to listen to. The communication between devices is recorded to the log file of line. RO=True ensures that KOM process does not influence the communication by its commands and responds.-False
Kotva
sc
sc
SC
Send Count(only for LonWorks line line) The retry count of one packet - default value is 1. However, in some situations when using iLON(tm)10 Ethernet Adapter, the first message did not pass and the communication started to work correctly when SC=2.
Note: Later we found out that this was caused because Free topology bus had not been ended by a terminator. However, this parameter had been already implemented.
-1
Kotva
sd
sd
SD
Send Delay(only for LonWorks line line) A complement to SC parameter that defines a delay (v ms) after each sending of packet.ms0
Kotva
vi
vi
VI
Vendor IDParameter Vendor ID of I-Am message (see the parameter Device Instance).-1

...

    • Station type: BACnet/IP station must be configured on TCP/IP-UDP line. LonWorks station must be configured on LonWorks line line. MS/TP station must be configured on SerialOverUDP Device Redundant or Serial line.
    • Kotva
      adresa
      adresa
      Address:
      • BACnet/IP station: IP address of station (in the form A.B.C.D, e.g. 172.16.0.99)
      • LonWorks station: address of LON subnet and LON node (in the form subnet.node, a subnet is 8-bit number and a node is 7-bit number)
      • MS/TP station: number of node on the line (0-254, address 255 is a broadcast)
    • Port: (only for BACnet/IP): UDP port number on station (according to standard 0xBAC0, i.e. 47808)
    • Domain: (only for LonWorks): 0 or 1, it relates with the line configuration. On LonWorks line  line you can configure a membership to one or two domains. On BACnet station, if you choose some domain, it means that the device belongs to this domain (it influences 'domain' bit in LON address).
    • Source network: source network number (i.e. a network with KOM process). This parameter may not be set for LonWorks line line. For TCP/IP-UDP line line, it is 16-bit number (or it is not set, see Note 2).
    • Kotva
      destionation_network
      destionation_network
      Destination network: 16-bit number of a destination network (i.e. a network including the device which communicates with KOM process).
      Set this for LonWorks line  line if KOM process communicates with the device that is placed after BACnet router. In that case, Address of station is the address of BACnet router and Destination address is the address of destination device.
      For TCP/IP-UDP line line, use Destination network if there is a communication between different BACnet networks.

      Note 1: This configuration was tested as follows:
      • Line: TCP/IP-UDP
      • Station type: BACnet/IP
      • Address: 172.16.99.1 (address of BACnet router PXG80-N)
      • Destination network: 1
      • Destination address: 1.1 (address PXC22 on LON network after BACnet router)
      KOM process communicated with the device PXC22 which was connected to LON network by BACnet router PXG80-N. KOM process communicates with BACnet router over Ethernet, so the line is TCP/IP-UDP. The communication between BACnet router and station PXC22 was done over LON network.

      Kotva
      pozn2
      pozn2
      Note 2: We tested the similar configuration. We used Delta Controls DSM-RTR (connected over Ethernet network) and Klimasoft MBG device (gateway on M-Bus) after it connected over MS/TP interface. The communication started if only Destination network (value 50020) and Destination address (value 96) were configured and not Source network. However, in other configuration, the communication proceeded also with the parameter Source network. We recommend you to try various settings of network parameters for the devices.

...

  • Kotva
    resubscribe
    resubscribe
    Resubscribe interval: Time in seconds. After it elapses, a station again gets a request to send changes of I/O tags. This parameter relates to the I/O tags with Request type that is equal to SubscribeCOV or SubscribeCOVProperty.
  • Max APDU: Maximum size of message (APDU = Application Protocol Data Unit) that is sent by KOM process. A default value is:
    The changing of default value is important for testing and adjusting to the stations which are able to process only smaller messages. For example, the reducing of Max APDU influences only the size and amount of messages ReadPropertyMultiple-Request. These messages are intended for a periodic reading of I/O tag value (see I/O tag configuration).

    Note: The setting of Max APDU does not affect the size of max-APDU-length-accepted in APDU BACnet-Confirmed-Request-PDU, with the help of which KOM process informs a partner what big message is capable to process. This parameter is configured by the station protocol parameter Segment-Response.

  • Priority: A priority of message in BACnet protocol. There are 4 priorities: Normal (default), Urgent, CriticalEquipment and LifeSafety.
  • Rpt_timer & reply: (only for LonWorks) The parameters Repeat timer (default value = 1) and Retry (default value =1 ) of LonTalk protocol.
  • Tx_timer: (only for LonWorks) Parameter Tx_timer in LonTalk protocol. Default value = 3.
  • Timeout and retry: A timeout in milliseconds to confirm the message. Default value according to BACnet protocol is 3000 ms. After the timeout elapses, the message is sent retry-times. If any confirmation is not received, an error count will increase on station.

    Note: When testing Siemens PXC64-U device (the communication over LonTalk), we had to set Retry=8, Timeout=300 (more retries with shorter timeout). Due to that, we had to increase the values COM_ERR=10, HARD_ERR=20 so that the station did not switch to error state at retrying to send message.
  • COM_ERR: The value of error counter on station when the station switches to COM_ERR status. The situation when station does not reply on call for reading or writing of value could be consider as error. A negative confirmation of a command (refusal of recording) is not the error. Default value = 5. See the parameters Timeout and retry.
  • HARD_ERR: The value of error counter on station when the station switches to HARD_ERR status. Default value = 10. See the parameters Timeout and retry.
  • Register-Foreign-Device, R-F-D Time to live: In this example the station is placed on LONTalk network after BACnet router which communicates with KOM process over Ethernet (e.g. Desigo PXG80-N). BACnet router sends the broadcasts from LONTalk to Ethernet as UDP broadcasts. If distributing of UDP broadcasts is disabled or KOM process is placed in other segment of network than BACnet router (it does not receive any UDP broadcasts), you should mark off the option Register-Foreign-Device on the station. This will cause, KOM process will send the message Register-Foreign-Device to BVLC router (BACnet Virtual Link Control) after start. The message calls for the registration to FDT table (Foreign Device Table) in router. The router sends the broadcasts in the form of UDP unicast (whose distribution is not limited to one segment) to the devices that are registered in FDT table. TTL - time in seconds (1-65535) is the parameter of message Register-Foreign-Device. It defines the expiration of registration that stops sending of UDP unicasts. That is why KOM process must ask BACNet router to register it before TTL expires. If there are more stations after BACnet router, just mark off Register-Foreign-Device on one of them.

    Note 1: If router does not support BBMD functionality (BACnet/IP Broadcast Management Device), it replies to the message Register-Foreign-Device with the error code and does not send LonTalk broadcasts to KOM process in the form of UDP unicasts. In that case you must use other solution (the communication over iLon Ethernet Adapter, the placing of KOM process on the same segment in network on which is BACnet router, etc.).
    Note 2: Router Desigo PXG80-N supports this functionality (tested). The control station Desigo PXC22-E.D does not support it probably (not tested yet).
    Note 3:In case of Desigo devices, if the D2000 KOM process is on a different network segment than the Desigo device, this parameter must be checked at the station. Otherwie Who-Is and Who-Has queries won't work (and thus addressing by object's name), as responses to these queries are sent as UDP broadcasts which will not go through a router.

  • Master: (only for MS/TP): The station is Master type. KOM process transmits a token to Master station which has the next larger address than is the address of KOM process (the parameter of line MS/TP address). If the addresses of all Master station are lower than addresses of KOM process, token is given to Master station with the lowest address. If any Master station has not been configured, KOM process supposes to be the only master and does not give any token. You should get the information about the type of station from a producer or device documentation.

    Note: The current version of protocol does not contain the automatic search of Master station. You can find more information in the section Comment on BACnet MS/TP implementation.

Example of station configuration on TCP/IP-UDP line line:

  • Station type: BACnet/IP
  • Adresa: 10.0.0.1
  • Port: 47808
  • Source network: 1

Example of station configuration on LonWorks line:

  • Station type: LonWorks
  • Address: 1.15
  • Domain: 0

...

Key wordFull nameMeaningUnitDefault value
Kotva
rsd
rsd
RSD
Receive-send DelayDelay between the receiving of the reply from station and sending next packet.ms0
Kotva
sr
sr
SR
Segment-ResponseA byte that contains Max Segs and Max Resp parameter (see the specification of BACnet protocol). Only some values from the 0-127 are permitted, which are specified by BACnet standard. KOM process considers the value 128 as default:
  • LonWorks line: set the value to 0x70 (more than 64 segments are accepted, maximum length of message is 50 bytes)
  • TCP/IP-UDP line line: set the value to 0x75 (more than 64 segments are accepted, maximum length of message is 1476 bytes)
  • Serial and SerialOverUDP Device Redundant line: set the value to 0x73 (more than 64 segments are accepted, maximum length of message is 480 bytes)
-128
Kotva
tsu
tsu
TSU
Time-Synchronization UTCThe parameter is important only if the synchronization is enabled on the tab "Time parameters" in the configuration of station.
If the parameter is True (default), the time synchronization is executed by the message UTCTimeSynchronization-Request (the synchronization in UTC). If the parameter is False, the time synchronization is executed by the message TimeSynchronization-Request (the synchronization in the local time).
Notes:
  • We recommend you to use the synchronization in UTC, if it is supported in the device - you can avoid the problems when advancing the time.
  • The requirements for the time synchronization are the unacknowledged messages, i.e. the device will not send the answer neither if it supports the time synchronization nor if it does not support.
  • The time synchronization has been tested on Siemens PXC36-E.D (HW=V3.02). This device supports the synchronization in both UTC and local time. You can find out the current time and date as "property local-date(56)" and "local-time(57)" of the object of Device(8) type.
    From this object, you can find out also "property utc-offset(119)" which defines the offset of local time from UTC (in minutes, i.e. -60 is Central European Time) as well as "property daylight-savings-status(24)", which defines whether the device works in the summer time (when testing in September 2012, the value on the device was True).
    After the time synchronization, the values "local-date(56)" and "local-time(57)" have been changed.
-True

...