Wireless Control with ZigBee Final Presentation Students Yossi Lempert Natan Keren Instructor Konstantin Sinyuk

Introduction Smart House topic continue Latest projects: Home Wireless Control, Remote Controller for Smart House New technology – ZigBee Reminder: fresh new Microchip kit, late start…

Project Goals Learn the ZigBee protocol and it’s constrains Learn the PicdemZ kit Implement an Access Point – End Point communication via ZigBee Add simple Hyper Terminal based control

ZigBee Simpler and cheaper than existing wireless protocols and hardware

ZigBee cont. Four layers: Physical, Mac, Application + sub-level Three predefined unit types:  RFD – simplest node, system interaction only  FFD – can transfer other units’ data  Coordinator – can serve as a network root and hold data about it, can be a bridge between networks

ZigBee vs. Bluetooth Cost: 3$ for Bt node, 1.1$ for ZigBee But, microcontroller support needed for ZigBee for now Code size: 10% of BT code size in most capable node, 2% in the simplest one But, 50% in actual node

ZigBee vs. Bluetooth New developing protocol vs. finalized product Next generation or commercial alternative? Low power consumption, small size – both Simple protocol model vs. complicated multi- layered one Networking design in ZigBee

PicdemZ Hardware 2.4 GHz RF transceiver 64 KB flash memory PIC18LF4620 microcontroller 2 * 9v battery

PicdemZ Software ZigBee Stack support Microchip MPLAB ICD2 Microchip MPLAB IDE available on Microchip site

Block Diagram End point Access Point Access Point Controller

Access Point Holds internal devices binding tables Holds neighbors tables Performs all the logic Access Point RF Transmitter Coordinator Module PIC18LF4620 UART

End Point Simple unit Responds AP messages and commands End Point RF Transmitter RFD Module PIC18LF4620 UART

Hyper Terminal Controller Simple Remote Controller via serial port Built into the Coordinator code

Functionality Set ID Create binding Clear binding table Clear neighbors table Perform action

Communication algorithm Bluetooth: AP inquires for EP and initiates connection ZigBee: EP scans for available APs and initiates connection Further logic is performed by AP in both cases

Difficulties New technology Very basic stack, almost no networking Hard to debug Resets and burnings after every change Lose of connection – possibly RF or stack problem

Debug No ICD2 NO LEDs Lots of prints and messages to Hyper Term Burn and test

Summary Easier system – easier life “It’s a brick in the wall” The system and technology do stand expectations Future: large network, integration into larger system ZigBee develops – new kits and stacks

Thanks to everyone…