MTN639 Series Gateway and Communication Modules - System Integration

The MTN639 series provides protocol translation and connectivity solutions, enabling KNX systems to integrate with building management systems, cloud platforms, and third-party automation networks.

Building Management System Integration:

The MTN639126 bridges KNX lighting and room automation with BACnet building management systems:

BACnet Specifications:

• Protocol: ANSI/ASHRAE 135 (BACnet/IP)
• Device profile: BACnet Building Controller (B-BC)
• Object types: Analog Input, Analog Output, Binary Input, Binary Output, Multi-state
• Data link layer: BACnet/IP (UDP port 47808)
• Network layer: IP routing supported

KNX to BACnet Mapping:

Configuration Process:

1. Export KNX group addresses from ETS
2. Import into MTN639126 configuration tool
3. Map to BACnet object instances
4. Define COV (Change of Value) notifications
5. Set polling intervals for critical points
6. Generate BACnet device profile
7. Commission on BACnet network

Typical Integration - Office Building:

BACnet Network (BMS)
        │
        ├── VAV controllers
        ├── Chillers
        ├── Boilers
        └── MTN639126 Gateway
                │
                └── KNX Network
                        ├── Lighting (MTN620619)
                        ├── Sun protection (MTN626714)
                        ├── Room sensors (MTN630614)
                        └── Energy meters

BACnet Objects Exposed:
├── BO 300001: Floor 1 Lighting Enable
├── BO 300002: Floor 1 Dimming Level
├── BI 300003: Floor 1 Occupancy Status
├── AI 300004: Floor 1 Temperature
└── AI 300005: Floor 1 Power Consumption

Industrial System Integration:

The MTN639150 connects KNX building automation with Modbus RTU/TCP industrial networks:

Modbus Specifications:

• Protocol: Modbus RTU (serial) and Modbus TCP (Ethernet)
• Modes: Master (query devices) and Slave (respond to queries)
• Data formats: Coils, Discrete Inputs, Input Registers, Holding Registers
• Baud rates: 9600-115200 (RTU)
• TCP port: 502 (standard)

Modbus Master Mode:

• Polls external Modbus devices
• Maps registers to KNX group addresses
• Update rates: 100ms to 60s configurable
• Error handling: Timeout, retry, fallback values

Modbus Slave Mode:

• Responds to external Modbus master queries
• Exports KNX data points as Modbus registers
• Supports multiple simultaneous connections (TCP)
• Register mapping: Flexible, user-defined

Application Example - Factory Integration:

Scenario: Office building attached to production facility

Modbus Network (Production)
├── PLC 1: Machine status
├── PLC 2: Energy meters
├── HVAC: Air handling units
└── MTN639150 (Modbus Master mode)
        │
        └── KNX Network (Office)
                ├── Lighting control
                ├── Room booking system
                └── Energy dashboard

Integration Points:
├── Production energy → KNX energy monitoring
├── Machine status → KNX occupancy (disable lights)
├── Shift schedule → KNX scene control
└── Emergency stop → KNX emergency lighting

IoT and Remote Access:

The MTN639180 enables KNX systems to connect to cloud platforms for remote monitoring, analytics, and mobile app integration:

Cloud Architecture:

[KNX Devices] ←→ [MTN639180] ←→ [Internet] ←→ [Cloud Platform] ←→ [Mobile Apps]
     │                │              │               │                │
   Sensors         Gateway       Secure TLS      AWS/Azure/       User
   Actuators       Local         Connection      Custom           Interface
                   Processing                    Platform

Supported Cloud Platforms:

• Schneider Electric EcoStruxure
• Amazon Web Services (AWS IoT Core)
• Microsoft Azure (IoT Hub)
• Google Cloud IoT
• Custom MQTT brokers

Security Features:

• TLS 1.3 encryption for all communications
• X.509 certificate authentication
• Secure boot and firmware signing
• Local firewall rules
• VPN tunnel support (optional)

Data Transmission:

Local Intelligence:

The MTN639180 performs local processing to reduce cloud dependency:

Edge Functions:

• Scene execution (local, no cloud required)
• Time schedules (internal RTC with battery backup)
• Logic operations (AND, OR, comparisons)
• Alarm generation (local notification)
• Data buffering (store-and-forward during outages)

Offline Operation:

• Normal operation continues without internet
• Data buffered locally (up to 30 days)
• Automatic sync when connection restored
• SMS/email alerts on connection loss

Mobile App Integration:

Network Requirements:

Security Best Practices:

• Use VLAN segmentation for KNX network
• Enable TLS encryption for all connections
• Regular firmware updates
• Strong passwords for configuration access
• Network monitoring and logging

• BACnet Testing Laboratories (BTL) certified (MTN639126)
• IEC 60669-2-1
• EN 62386
• FCC Part 15 (for radio versions)
• CE marked, RoHS compliant