1 / 12

“Excalibur” A flexible KNX/TP1 node

“Excalibur” A flexible KNX/TP1 node. TU Wien Automation Systems Group Fritz Praus 0025854 fritz@praus.at. Outline. Introduction definition of terms requirements Hardware components design Software basic low level routines various stacks. Definition of Terms.

roddy
Download Presentation

“Excalibur” A flexible KNX/TP1 node

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. “Excalibur”A flexible KNX/TP1 node TU Wien Automation Systems Group Fritz Praus0025854 fritz@praus.at

  2. Outline • Introduction • definition of terms • requirements • Hardware • components • design • Software • basic low level routines • various stacks

  3. Definition of Terms • Building Automation / Building Services • lighting, HVAC • security and access control, safety alarm systems, elevators, … • (white goods, brown goods) • Field buses for building automation • exchange of control data • small data amounts • robust

  4. EIB/KNX • open standard • EN 50090 • specification maintained by Konnex Association • well-established in D-A-CH • decentralized design • Twisted pair medium: • CSMA with bitwise arbitration at 9600 bit/s • hierachical 3 layer structure possible • Powerline, radio transmission, …

  5. EIB/KNX Devices and Interfaces • EIB/KNX devices • sensors, actuators • Router (TP/TP vs. IP tunnelling for high-traffic backbones) • gateways • PC-based (management, visualization) • EIB/KNX (TP) interfaces • medium connection • BCU, BIM: Transceiver + Microcontroller (Layer 7) • TP-UART: Transceiver + Layer 2 ASIC • application module/processor • sensor/actuator module: PEI as free digital/analog I/O • µC/PC: RS232 (BCU/TP-UART), USB, IP

  6. Requirements • experimental embedded platform (lab use) • universally applicable • wish list: EIB/KNX, RS232, IP, USB • extensible (i.e. LON, IO pins, ..) • support high-level way of working • But offer powerful features • low cost and compact • design openly available

  7. Hardware - Components • Fujitsu MB90330F 16-bit Microcontroller • 24 MHz, 24Kbyte RAM, 384Kbyte flash memory • 4 UARTS and USB • external bus interface • Crystal CS8900ACQ3 Ethernet Controller • 2 TP-UARTs • SD/MMC card connection

  8. Hardware – Design • Schematic • PCB Layout • Placement • Conductors • Power

  9. Software – Low-Level Drivers • TP-UART protocol • asynchronous serial communication • normal vs. analog mode (transceiver only) • CS8900A protocol • ISA bus • SD card protocol • SPI standard • USB firmware • slave / mini host

  10. Software – IP Stack • IP • ICMP (echo) • UDP • TCP (single) • ARP • DHCP • SLIP

  11. Software – EIB/KNX • EIB/KNX Stack • cEMI • EIBNet/IP • Gateway functionality • Tweety port

  12. Thanks for your attention

More Related