• Home
• com.github.calimero
• calimero-server
• 2.6-rc1
• source code

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

limero.calimero-server.2.6-rc1.source-code.server-config.xml Maven / Gradle / Ivy

<?xml version="1.0" encoding="UTF-8"?>
<!-- Calimero server settings (required for startup) -->
<knxServer name="knx-server" friendlyName="Calimero KNX IP Server">
	<!-- KNXnet/IP search & discovery -->
	<discovery listenNetIf="all" outgoingNetIf="all" activate="true" />

	<!-- Provides the KNXnet/IP-side configuration for access to one KNX subnet -->
	<serviceContainer activate="true" routing="true" networkMonitoring="true"
		udpPort="3671" listenNetIf="any">
		<knxAddress type="individual">7.1.0</knxAddress>
		<routing/>
		<!-- latencyTolerance specifies the time window for accepting secure multicasts,
			depends on max. end-to-end network latency (usually [500 .. 8000] ms) -->
		<!-- <routing latencyTolerance="1000">224.0.23.12</routing> -->

		<!-- Enabling the disruption buffer will replay missed frames after reconnecting a KNXnet/IP client link
			using the specific client UDP port range (if caused by a disrupted connection). -->
		<!-- <disruptionBuffer expirationTimeout="30" udpPort="5555-5559" /> -->

		<!-- Specify one KNX subnet type, connecting the KNX network. The subnet connection type is one of
			{ "udp", "tcp", "knxip", "ft12", "usb", "tpuart", "user", "virtual", "emulate" }.
			The KNX communication medium is one of { "tp1" (default), "pl110", "knxip", "rf" }.
			In the following are some examples: -->

		<!-- <knxSubnet type="udp">192.168.10.10:3671</knxSubnet> -->
		<!-- two optional attributes are supported for tunneling:
			* netif: specifies the server network interface to the knx subnet
			* useNat="true"|"false": use network address translation (NAT) -->
		<!-- <knxSubnet type="udp" netif="eth0" useNat="true">192.168.10.10:3671</knxSubnet> -->

		<!-- <knxSubnet type="knxip" listenNetIf="en0">224.0.23.12</knxSubnet> -->

		<!-- <knxSubnet type="tcp">192.168.10.80:3671</knxSubnet> -->
		<!-- <knxSubnet type="tcp" host="1.2.0" user="4">192.168.10.80:3671</knxSubnet> -->

		<!-- <knxSubnet type="ft12" medium="pl110" domainAddress="6f">/dev/ttyS0</knxSubnet> -->
		<!-- <knxSubnet type="ft12" medium="tp1" format="cemi">/dev/ttyS0</knxSubnet> -->

		<!-- KNX USB: specify the vendorId:productId or vendor name, e.g., siemens -->
		<!-- <knxSubnet  type="usb" medium="tp1">siemens</knxSubnet> -->
		<!-- if USB device identifier is left empty, the first found KNX USB device is used -->
		<knxSubnet type="usb" medium="tp1"></knxSubnet>

		<!-- <knxSubnet type="tpuart" medium="tp1">/dev/ttyACM0</knxSubnet> -->
		<!-- <knxSubnet type="virtual">virtual-subnet</knxSubnet> -->
		<!-- <knxSubnet type="emulate">emulate-subnet</knxSubnet> -->
		<!-- <knxSubnet type="user" class="my.knx.NetworkLink">o1,i2|i4</knxSubnet> -->

		<!-- Datapoints are only useful if an emulated KNX subnet is used -->
		<!-- <datapoints ref="datapointMap.xml" /> -->

		<!-- KNX group address filter applied by the server for this service container (optional).
		     This filter is used both for server->subnet and vice versa. -->
		<groupAddressFilter>
			<!-- <knxAddress type="group">2/1/1</knxAddress> -->
			<!-- <knxAddress type="group">2/1/0</knxAddress> -->
			<!-- <knxAddress type="group">2/1/20</knxAddress> -->
		</groupAddressFilter>

		<!-- Additional KNX individual addresses assigned to client KNXnet/IP connections (optional) -->
		<additionalAddresses>
			<knxAddress type="individual">7.1.10</knxAddress>
			<knxAddress type="individual">7.1.11</knxAddress>
			<knxAddress type="individual">7.1.12</knxAddress>
			<knxAddress type="individual">7.1.13</knxAddress>
		</additionalAddresses>

		<!-- Cyclically transmit date (11.001), time (10.001), or date+time (19.001) information on the subnetwork
			 and server side, using the default time zone and the specified datapoint(s).
			 Expiration timeout specifies tx cycle in seconds, e.g., 1 min = 60, 1 hour = 3600, 12 hours = 43200. -->
		<!--
		<timeServer>
			<datapoint stateBased="true" name="current time" dptID="10.001" priority="low">
				<knxAddress type="group">3/4/5</knxAddress>
				<expiration timeout="600" />
			</datapoint>
		</timeServer>
		-->
	</serviceContainer>

	<!-- Add next service container (optional) -->
</knxServer>