Home

K-NET01

1. B t P21 ADC Input Um E am W VUA POO Output pin It is connected to a LED to demonstrate the light control P01 Digital input pin P21 8 bit ADC input pin 5 2 GPI O Control Functions U Messenger provides the other operation mode for GPI O Control function When users enter this mode the coordinator can access the GPIO pins of every Network Brick There are three functions One is to turn on off GPIO POO The second is to detect the logic 0 or 1 of GPIO PO1 The third is to read 8 bit ADC value from ADC pin P21 through UART interface 1 Execute U Messenger 03 exe AN KN01 01 Rev 0 1 page 25 35 K NETOI e U Messenger U Messenger Ver 0 3 Detect Infa com vi Loop 100Mb 121 msec Bute delay 0 1 msec MCU NEC 0602 Clean Send U Messenger Ver 0 3 Detect Info Hefresh Loop 1O0MB 192 msec Byte delay 01 msec MEL NEC 0602 Clean Send 3 If users want to return to normal mode Click right button of the mouse at Text Input Region and press Ctrl Alt G to switch the mode 4 Fill the network address of the target node 5 Click Refresh button to acquire the status of the target node including LED pin PO0 output Logic value of P01 pin input and ADC value of pin P21 input 6 Click the text of LED on or off to change the status of remote LED 7 Connect P01 of the target node to Ground with the appended wire and clic
2. ec I rj C on ot LE 8 A 1 d i w XE HEADER 20 AN KN01 01 Rev 0 1 page 29 35 P21 q D2 a lt POO a D3 P ud 7 pol D 4 am wy P120 TNTPO 2 P lt P61 spAo 2P d P60 SCLO K NETOI R182KR R192KR R202KR R212KR R222KR R232KR R242KR AN KN01 01 lt Rev 0 1 gt page 30 35 Wubec K NETO1 A 2 Interface Board Layout 0000000000000000000 0000000000000000000 0000000000000000000 ELLIS OOO T HT TTE vr fy a t3 BU S i d i i G a r4 g ia TE seu lt A eu a Far FM T p23 pom 5a MCU RESET SELE O NO ON C Em m 0 xe O O Lu 00 um uU C m a Cu E m 5 o O LS al X O Iv re 00 x a al 3 C I z VCC xL too TEN des D AN KN01 01 Rev 0 1 page 31 35 Wubec x K NETOI Appendix B U NETO1 DK MCU Board Board Size 39 5mm x 25mm Board Thickness 1mm Board Material FR4 Multi layer B 1 MCU Board Schematics ANIL PZI AKIZP22 ANIG P20 ANIA P23 POL TIL0 TODO AVss POO TTOO AVREF PL20 TNTPO EXL YT PlO SCEIO TxXDO gt RESET PHU SIMVEXIXI 1 FLMDO 7 P12 SO10 UART TX Sebas o PI2LXYEXCLK OCDOB P13 TxDS ART EX 10 P121 X1 OCD0A PIVRxXDS SEN ao VSS GND P16TOHLTNTP5 a PSUSDAO M DU UU I P l WAKE HA PRL RHA P3LINTPYOCDIA
3. EN RD EE dE 10 GE 19 Enca EE e Ue 11 SL SE EEE EE EEE 11 NTE TIC oscila 12 3 2 1 Hardware setup using the K NET01 DK Network Bricks rr 12 3 2 2 Installing K NETO1 DK Design Environment ss ese eee Y e e e K meme 12 3 2 3 K NET01 DK Firmware res 13 3 3 Using UBEC Messenger to verify Peer to Peer Communication with K NETO1 DK 14 3 3 1 Set up a Pair of Network Bricks eeseeeeeen mmm emn nn 14 3 3 2 Messenger communication for Peer to Peer with K NETOL DK eee ee rrr Y YY Y y A 15 3 4 Using UBEC Messenger to verify Linear Tree Communication with K NETO1 DK 17 3 5 Using UBEC Messenger to verify Device Communication with K NETO1 DK Y RYN 17 A Using the KNETOL Development avveie 18 P VINO GU CUO a ca EEE 18 4 2 Modifying the Network Addresses of Routers and Coordinator sss es es ee eee eee 18 4 3 Modifying the Network Addresses of D VICES cccccecscsueeseecueueerseaueusseauaueerseauauecreeaueuteeeuauenterans 22 4 4 Modifying the Topology of Network rarvarararnrvarannrraransrnrversrsrneversrnrrerersrneversrneneversrnererersrneversenn 23 5 ENE 25 5 1 GPIO Hardware Introduction ee Kee 25 NNN 25 Appendix A U NETO1 DK Interface Board aravarvararnrnvvararnrnerarsrsrverersrsrverersrvererersrnerersnsrverererssverersrnevernenn 28 A Interface Board STEM AUG vanene ayaqa qaqaq 28 FN 31 Appendix
4. Em Os 02 178 Depth Lm Ox 03 177 PAN D Ox 0000 e g 1234 T Device Huk Og Foo FOO FEFF Power s oo M ax gt MAC Ox End Dev OxFPFFF Detect com E gt CON 5 connected Save Load Exit Read Setv DevNwk 4 If devices are successfully set up the device information will be shown on the screen Nwk F001 Parent FFFF Scope Child Cr Ox 2 178 Depth Lm 0 320 177 PAN4D Ox 0000 eg 1234 CH ri Device Huk Og FOO F00 FEFF Power Ox oo IM ax MAC Dx depth 0 Mac 0000000000000000 End Dev OxFFFF Read Detect com 5 gt Oxo COM 5 003 connected Ox0000 1 th Save Nwk 0xF007 Parent OxF FFF Load O00 EET A000000000000000 Setv DevNwk 4 4 Modifying the Topology of Network If users want to change the topology of network type the values into the blanks of Child and Layer One should also fill in PAN ID and CH RF freq channels to complete the network parameters The PAN ID and CH are the identification of the network Different networks should have different PAN ID s They can co exist in the same RF channel If the RF channel is too noisy it can change the RF channel K NETO1 following 802 15 4 specification provides 14 RF channels Click New icon and the tool will generate a brand new topology of the network addresses Follow the sequences given in Section 3 2 to modify all the Network Bricks including the
5. NETO1 DK Firmware Inside the K NETO1 Design Kit box there are four Network Bricks including one coordinator two routers and one device The coordinator s job is to initiate a wireless network Without this initiator no Network Brick can join the network Only one coordinator is allowed in a given network The NWK address of the coordinator is 0x0000 for all the applications The routers transfer the data from one Network Brick to the other according to the routing table The routing table of K NETO1 is shown in Figure 6 The communication path for each transferring is controlled by each network engine in this case the NEC uPD78F0502 microcontroller according to the address data 2Child 3 Layer Coordinator 008 Routers N 009 UD Sed TN DW Is 0034 0044 006 0070 004 ODB ODD ODE Figure 6 Routing Table of K NETO1 DK The devices choose one and only one of the nearby routers or the coordinator to transfer the data when it starts to work without obeying the parent child super frame rule This neighborhood communication allows the device to move around throughout the network region and thus extends the mobility of network When a brand new device shows up for the first time for the network it should trigger the signal to the network first If the new device fails to send the trigger signal the whole network will not recognize this device The functions of the Network Bricks are decided by the address value
6. P3VHSI TOSVINTPA PYININTPYVOGCDIN UPD7SFOSOX P23 ANREDE SCLK 50 SI PIA TNTPC MCU RESET FLMDO i OCDOBX2 i pes RS Lok GPICH GPIOH R A N GPIO2 RESETN WAKE 8 INT 9 30 Ti _ l J sC LE 12 D D 1 Ch C hw L 12 E 14 SEN 13 CLROUT 14 AIAL32 HM 15 L XTAL32 P 16 16 L CONN PCB 31 13 100nF 10nF o OO AN KN01 01 lt Rev 0 1 gt page 32 35 K NETOI MCU RESET m a PI20 INTPO OCDOB X2 FLMDO OCDOA X1 P6O SCLO P33 B 2 MCU Board Layout 0019 I U 024 B HON 66 6 o i 4 AO OOOOTI c3 a c2 NEC uPD78FO5OX LZ J LI E ul 0 VA VE B 7 n ufo O O O on Be b gt 000009009 NN WIND OND 5 v a 4 o OO AN KN01 01 lt Rev 0 1 gt page 33 35 K NETOI Revision History Revision Date Description of Change 2009 9 1 Original 2008 10 9 Add K NET Application Topology RF characteristics and Network Binding A AN KN01 01 Rev 0 1 page 34 35 Wubec K NETO1 Contact UBEG Headquarters Address 7F 1 No 192 Dongguang Rd Hsinchu 300 Taiwan Tel 886 3 5729898 Fax 886 3 5718599 Website http www ubec com tw Sales Services FAE Services Tel 886 3 5729898 Tel 886 3 5729898 Fax 886 3 5718599 Fax 886 3 5718599 E mail sales ubec com tw E mail fae Qubec com tw DI SCLAI MER TO THE BEST KNOWLEDGE OF THE UNIBAND ELECTRO
7. icon and choose KNETDK dat AN KNO1 01 lt Rev 0 1 gt Bank Detect COM 5 connected Save Load Exit EE page 19 35 Wubec K NETO1 U Addressor Com5 s P Loop 100Mb 190 msec Byte delay 0 06 msec MCU NEC 0502 BEID Ube AP i I Doc Scope Read L gt E Ol version E ea j ERNA E Copyright bet Child Cm Ox 178 Detect com 5 3 me COM 5 Sync DO 10 ini Be me A connected RE Sync ini PAN ID Dy e g 1234 WY U Addressor_O3a exe 1 mE Save L e nU COM_03b ese Es F os U MACwriter 13 exe Device Nwk Ox E ZR U Messenger O3b0910 exe a FDD1 FEFF cl EG TT Messenger 3c exe i HEN Power Ox 00 IM ax gt Exit MAC Ox m dr MM KNETDEdM BRAUD r TIERRA 5 Move to 01 and press left button Drag 01 to upper layer Power Ox m Max 00 min 28 Exit Power Ox po Max 00 7 min 28 iLoad XI MAC Ox MAC Ox HE d 0 C KS 00 d 1 01 01 02 Users can utilize this tool by drag the number up and down to verify the address map is the same as that shown in Figure 8 6 To Set 08 address into the connected module users push right button of the mouse on the 08 number It will pop out the set up menu Choose Set and the process will be started and the number color will change After the process is completed the color of 08 should change to blue col
8. layer through the UART interface Accessories The power supply of the Network Brick supports both AC DC adaptor and battery powered schemes The selected AC DC adaptor should be capable of supplying a DC supply of 3 0V Two USB RS232 adaptor cables and the driver CD are bundled together These cables help facilitate the control of the Network Brick by PC A AN KN01 01 Rev 0 1 page 7 35 Wubec u K NETO1 through the RS 232 ports Software and Other Resources The content of the K NETO1 DK CD ROM includes U Messenger application software U Addressor application software U MACwriter application software user manual and AT command manual 2 4 Interface Board of the Network Brick Figure 1 shows the layout of the interface board for the Network Brick The interface board has the following features DMCU module connector 2 RS232 DB9F connector DC power jack 4 User defined I O connector Along with the Network Brick the interface board has the features necessary for developing a 2 4GHz tree networking solution Detailed setup procedures are described in Chapter 2 Please refer to Appendix A K NETO1 DK Interface Board for the Network Brick for further information 299900000900000000000 6000000000000000000 RR RRR RRR ERE RE RE SE 6060606000000000000000 600 0000000000000000 LAA AAA ERE RES ES ES OE E ROR RRR RR ER ERE LAL v06006000600800080080000020 8 6060060600000000000000 09900000 0000000000G mOo
9. pre configured network ID and node ID as described in Sections 1 6 and 1 7 Due to these parameter pre settings the air traffic and the memory size requirement will be dramatically reduced and one can achieve the cost saving 1 9 Network Components There are three types of components used in constructing the K NET network namely the Coordinator the Router and the Device Using these components one can easily extend the size and flexibly change the configuration of the network Q Coordinator The coordinator s function is to initiate a wireless network Without this initiator no Network Brick can join the network Only one coordinator is allowed in a given network The NWK address of the coordinator is 0x0000 for all applications 0O Router The routers transfer the data from one node to the other according to the routing table The routing table and the communication path are pre determined through the parameter setting such as the node ID OU Device The devices choose one and only one of the nearby routers or the coordinator to transfer the data when it starts to work without the need to obey the parent child super frame rule This neighborhood communication allows the device to move around throughout the network region and thus extends the mobility of network When a brand new device shows up for the first time in the network it should trigger the signal to the network first If the new device did not send the trigger signal the who
10. virtually extend the communication range by placing the Network Bricks at still longer distance away Without being connected to the PC the Network Bricks still can execute the network functions 3 5 Using UBEC Messenger to verify Device Communication with K NETO1 DK As mentioned in Section 2 3 3 the devices choose one and only one of the nearby routers or the coordinator to transfer the data Note that it should send the signal to the network first if the device is new to the network Otherwise it will not be recognized by the whole network After setting up the linear tree network users can power on Device F001 and connect it to the PC through the COM port If users try to look for FOO1 from the network first the information line will display Sending Fail If users send the message from Device F001 to the network Coordinator 0000 will be able to recognize users after all Next users can power down Router 0002 and then Router 0001 Users will find that the communication between Device F001 and Coordinator 0000 can remain active all the time MEM OOO AN KN01 01 Rev 0 1 page 17 35 Bubec K NETOI 4 Using the K NETO1 Development Kit 4 1 Introduction This chapter describes the following topics UO Modifying the network addresses of routers and coordinator LY Modifying the network address of devices UO Modifying the network topology 4 2 Modifying the Network Addresses of Routers and Coordinator To build up the wh
11. B U NETOL DK MCU Board x sss sse seene 32 NIIS BO a o OD EEN e 32 B 2 MCU Board La OU EDN EF a as 33 AN KN01 01 Rev 0 1 page 2 35 K NETOI K NETOI Development Kit User Manual 1 K NET Overview 1 1 Introduction UBEC s K NET is an easily installed proprietary network platform It builds on the established IEEE 802 15 4 standard for packet based wireless communications with enhanced features such as tree routing intelligence and listen before talk scheme It can co exist with other wireless technologies such as Bluetooth and Wi Fi within the same operating environment 1 2 K NET Applications K NET along with the IEEE 802 15 4 protocols is specifically designed for battery powered applications The platform comes with the needed hardware firmware and software design resources to enable a guick and cost effective networking solution Due to its inherent flexibility users will be able to develop with a minimum effort a peer to peer a star or a tree topology network to suit the desired application K NET adopts a fixed address tree topology to both save the system cost and increase the network robustness It is suitable for a wide range of applications such as Peer to peer communication Lighting control Automatic meter reading AMR Industrial automation Long distance network cable replacement U U U U 1 3 Radio Frequency Range K NET provides a wireless radio based network connectivity oper
12. Coordinator 0000 o OO AN KN01 01 lt Rev 0 1 gt page 23 35 K NETOI U Addressor Com Loop 100Mb 213 msec Byte delay 0 06 msec MCU NEC 0502 Count Child Cm Depth Lm FANM D Ox 0000 e g 1234 CH Scope We 17 nE lx 5 177 NE Read Detect com 5 COM 5 connected m Device Nuvk Ox Info F001 FEFF Power Ox OQ Max gt To communicate with every module Mac 0 you need holding the same i Cm Lm CH PAN ID I d If users forget to fill the Cm and Lm before clicking Scope button it will show the warning message for reminding to set the correct values Nwk FFFF Parent FFFF depth 255 Mac FFFFFFFFFFFFFFFF Cm FF Lm FF PanlD 0000 CH 20U Set Device Nwk n Child Cm Os 00 1 Warning Depth Lm 0 80 17 In this module PANAD Ox FFF Cm OxFF cH Jo mn Emz0xPF gt re i COM 3 connected Power Ox FF Ma In your setting MAC Ox Ferrer Cm Ox0 L Lm 0x0 Exit NS OO AN KN01 01 lt Rev 0 1 gt page 24 35 WJ ubec K NETO1 5 Entering Remote GPI O Control Mode 5 1 GPIO Hardware I ntroduction K NET01 provides the other mode which can control GPIO pins on the Network Brick 100006000000 110000000000 NE POO Light Control Output Z 6 C B le w w w w w w w w Jsleoceeeoeoo T
13. K NETOI K NETOI Development Kit User Manual Application Note Preliminary AN KNO1 01 The content of this technical document is subject to change without Version 0 1 notice Please contact UBEC for further information Released Date 2008 10 9 All rights are strictly reserved Any portion of this document shall not be reproduced copied or transformed to any other forms without permission from Uniband Electronic Corp AA AN KN01 01 Rev 0 1 page 1 35 Uubec K NETO1 Table of Content 1 K NET VG 3 1 p H Y AP A pe o oo 5 3 1 2 NET UNN 3 loo a RIO uu uuu o O oo E peer etait R NETUS RUFI DERE 3 1 4 R eli able Radio COMMUNICATION re 4 1 5 Topologies and Routing sss esse eee e e ee eee d Lo NWO Taenu nc PERYF EEE EE EE 5 L7 Network Address NOT EN EE lel aerei PU sax Uu peti ers GRUG NOD DU NOE SS UN CREE OO ES 5 1 8 Automatic Binding and Joining danse ere ghi E dria 6 L9 NeDWOFK COMPONEN Sesa aman Ita eu oru SII RE Drm 6 2 S zi 7 E N aun OC TO CN E E PEN A et 7 2 2 K NETOL DK Components see mm mmmmmmememememememe eme enne messes sensns 7 2 3 Overview of the K NET01 DR v re riene 7 2 4 Interface Board or the Network BIICK versa ear 8 2 5 MCU Board of the Network Brick eset mmm mmm nennen nnns 9 2 0 RF Board of me NetWork BiCK aa GN UNO CNEUEN GRO UD
14. NIC CORPORATION UBEC THIS DOCUMENT IS ADEQUATE FOR ITS INTENDED PURPOSES UBEC MAKES NO WARRANTY OF ANY KIND WITH REGARD TO ITS COMPLETENESS AND ACCURACY UBEC EXPRESSLY DISCLAIMS ANY AND ALL OTHER WARRANTIES WHETHER EXPRESSED IMPLIED OR STATUTORY INCLUDING WITHOUT LIMITATION WARRANTIES OF TITLE MERCHANTABILITY NON INFRINGENT AND FITNESS FOR PARTICULAR PURPOSE WHETHER ARISING IN LAW CUSTOM CONDUCT OR OTHERWISE A AN KN01 01 Rev 0 1 page 35 35
15. The definition of function vs address value is shown below Functions Address value 0x0000 0x0001 0xF000 0xF001 0xFEFF 2o 0 00 0 O AN KN01 01 Rev 0 1 page 13 35 Wubec K NETO1 3 3 Using UBEC Messenger to verify Peer to Peer Communication with K NETO1 DK There are two ways to accomplish the peer to peer communication with the K NETO1 DK One is to deploy Coordinator 0000 to Router 0001 and the other is Coordinator 0000 to Device F001 3 3 1 Set up a Pair of Network Bricks Figure 7 Network Bricks setup and P16 P17 LEDs When the Coordinator is powered on the LED of P17 will be on after it has build up the network Subsequently the Router is powered on The LED of P16 will blink firstly It means the Router is sending receiving the RF Signal to from the air These RF signals are transmitted received for searching binding and joining the network After joining successfully the LED of P17 of the Router will be on a AN KNO1 01 lt Rev 0 1 gt page 14 35 Wubec x K NETOI 3 3 2 Messenger communication for Peer to Peer with K NETO1 DK The set up procedure is given as follows Coordinator Network Brick Address 0x0000 1 Executing U Message 0x exe U Messenger Ver 0 3 com vi nak vi Loop 100Mb 121 msec Bute delay 0 1 msec MEU NEC 0502 en 2 Select COM port or click Detect icon to detect available COM ports If the selection is successf
16. al knowledge to link with a wireless network with a minimum effort using simple AT command sets through the UART interface To reduce the system cost and increase the network robustness UBEC s K NET platform adopts a fixed address tree topology This topology will request for every K NET component Network Brick a fixed address These addresses follow the rule of routing table of ZigBee specification Section 3 7 3 ZigBee Specification Document 053474r13 and are predetermined before starting the network buildup According to that rule different layers and children have different addressing schemes as shown in Figure 4 below 1 Child 1 Layer 2 Child 3 Layer 3 Child 1 Layer Figure 4 Address Assignments for Different K NET Layers and Children The DK contains the addressing tool U Addressor U Addressor_0x exe to calculate the routing table address assignment and program the addresses into the Network Bricks AN KN01 01 Rev 0 1 page 11 35 Wubec I K NETOI 3 2 Using K NETOL DK for the First Time 3 2 1 Hardware setup using the K NETO1 DK Network Bricks The K NETO1 DK consists of four Network Bricks Each Network Brick consists of one RF module one MCU Board and one interface board Users have to assemble each Network Brick before applying the power Please follow the setup steps below to prepare for each Network Brick 1 Unbox and unwrap each board and place it on a non conductive surface 2 The RF
17. ating in the 2 4GHz radio frequency RF band This band is available for unlicensed usage The frequency characteristics are shown as follows Frequency Rangel Channel numbers CH16 2430MHz CH17 2435MHz CH18 2440MHz CH19 2445MHz NN AN KN01 01 Rev 0 1 page 3 35 Wubec K NETO1 CH21 2455MHz CH25 2475MHz Specification IEEE 802 15 4 Standard 1 4 Reliable Radio Communication K NET inherits the techniques widely used fort he IEEE 802 15 4 protocol to ensure reliable communications between the sender and the receiver To minimize the potential data corruptions due to interferences or poor transmit receive conditions K NET adopts the following three techniques 1 Modulation K NET follows the IEEE 802 15 4 protocol for the coding mechanism for the radio transmissions The coding method uses the OQPSK Offset Quadrature Phase shift Keying modulation scheme where there Is a high probability that a message will get through to its destination even if there are conflicting transmissions more than one device transmitting in the same frequency channel at the same time Collision Avoidance The transmission scheme is also such that no data will be transmitted when there Is an activity detected in the chosen channel generally known as the Carrier Sense Multiple Access with Collision Avoidance CSMA CA This means that before beginning a transmission a node will listen on the channel to check whether it is
18. clear If an activity is detected on the channel the node will delay the transmission for a random amount of time and listen again If the channel is now clear the transmission can begin Otherwise the delay and listen cycle is repeated Acknowledgements They are very useful to make sure that data properly reach their destinations When a message arrives at its destination the receiving node will send an acknowledgement back to the sender to tell it that the message has been received If the sending node does not receive an acknowledgement within a certain time interval it needs to resend the original message Together these techniques will ensure a reliable K NET network even if there are other nearby networks operating in the same frequency band In particular the K NET networks can operate interference free in the neighborhood of networks based on other standards such as Wi Fi and Bluetooth NO CJ 1 5 Topologies and Routing K NET provides an improved tree topology which will enable more communication nodes and cover longer distances via intermediate nodes The network has a top node with a branch leaf structure as shown below To reach its destination a message travels up the tree as far as necessary and then down the tree A AN KN01 01 Rev 0 1 page 4 35 K NETOI Coordinator 9 Router O Device 1 6 Network Identification In K NET every network has its RF channel and PAN Personal Area Network ID Bef
19. e of the nearby routers or the coordinator to transfer the data it does not obey the parent child super frame rule Therefore it is not necessary to code the device address by the network protocol However it still needs to inform the network about its layers and children K NET defines the addresses 0xF001 to OxFEFF as the devices To set up the device addresses the procedure is shown below 1 Select Set Device Nwk Before setting the device address please make sure Cm and Lm are the same as this network T Addressor Com Loop 100Mb 265 msec Byte delay 0 06 msec MCU NEC 0502 End Dey OxFFFF Scope HEB Child Cm Ox 02 178 Detect com 5 Depth Lm Ox 08 177 COM 5 connected PAN ID Ox 0000 e g 1234 Setv DevNwk 2 One should fill in the address whose range is from 0xF001 to OxFEFF Again one should check the blanks of Child Depth PAN ID and CH to make sure these values are the same as other Network Bricks M SetDevice NWR UMFFFF IFODI FEFF End Dev DERO Depth Lm Ox 5 177 a PAN ID Ox 1234 eg 1234 Scope CH Hh 1th 16th Power Ox nm Mas UU 7 min 28 EI MAC Ox FFFFF i Read COM 3 connec E Save E f Load 3 After completing the data click SetDev to start the process AN KN01 01 lt Rev 0 1 gt page 22 35 T Addressor Com K NETOI Loop 100Mb 265 msec Byte delay 0 06 msec MCU NEC 0502 Scope Child
20. eooooooooonooo ooo Se IO oOx los FTO EU Figure 1 Interface Board Layout AN KNO1 01 Rev 0 1 page 8 35 Bubec K NETOI 2 5 MCU Board of the Network Brick The MCU Board Is designed to support UBEC s U Force module with a stamp interface NEC uPD78F0502 microcontroller is adopted as the network engine for the Network Brick This network engine handles the wireless network communication between the Network Bricks through the RF modules and provides the AT commands through the UART interface for the users Also the MCU board through the two row 16pins header can be connected to the interface board which in turn provides the electric power the RS 232 interface and all the I O pin connections gt a LO e m a lt N A a 3 dl Lu Z Figure 2 MCU Board Layout Figure 2 shows the MCU board layout The MCU board has the following features NEC uPD78F0502 microcontroller 2 Stamp interface 9 Pin Headers Please refer to Appendix B K NETO1 DK MCU Board for the Network Brick for further information A AN KNO1 01 lt Rev 0 1 gt page 9 35 Bubec K NETOI 2 6 RF Board of the Network Brick 23 31 23 EE OI fa gt T RT TT a De L Sh h L G kb ok Figure 3 U Force Layout Figure 3 shows the board layout of the U force The U force has the following features DUBEC s UZ2400 2 Stamp interface 3 PCB antenna Please refer to AN 2400 12 U force Module User Man
21. iu bas L Depth Max 5 Depth Max 5 Current Depth Current Depth U ml I mo Ao rm oaa L wes l 1 f Dad 8 Type the message in the lower screen and click Send icon or users can press Alt E or Alt Enter vi Loop 100Mb 120 msec Byte delay 0 1 msec MEL NEC 0502 Send Hi How are von J Clean 9 If the transmission is successful the upper screen of sender and receiver will show the message Message Com 1 U Messenger Ver 0 3 Info Detect om y wk il COM 3 gt Parent FFFF Power 0x00 Myself How are you Myself Send 10 If the transmission failed the information line will show Sending Fail A AN KN01 01 Rev 0 1 page 16 35 K NETOI Tz 00 Send Sending F aill 3 4 Using UBEC Messenger to verify Linear Tree Communication with K NETO1 DK After power on and connecting the Coordinator 0000 and the Router 0001 continue connecting the Router 0002 Users can connect all three Network Bricks with the COM port or choose two of the three to connect to the PC Following the step 7 of the last section Section 2 4 users can type in the Network Brick s address that users want to communicate with and start sending the message If turn off the Router 0001 users will find that the Coordinator 0000 and Router 002 will not communicate with each other Also users can
22. k the Refresh button of the A AN KN01 01 Rev 0 1 gt page 26 35 Bubec x K NETO1 coordinator The GPIO High will turn to be Low V v A8 2006 08 33 8 Also users can connect P21 of the target node to Ground or VCC with the appended wire and click the Refresh button of the coordinator The result will show the ADC values on the screen 9 If pin P21 does not connect to any voltage source the result will be random values 1 a Info M 1 vi wk 000 lt Bie Detect Info COM T y T y Hwk 0001 Loop 1T00Mb 120 msec Byte delay 0 7 meec MEL HEC 0602 APIO ADC Send Refresh Send Detect mo LED GPIO m Detect Info Loop 100Mb 120 msec Bute delay 0 1 msec MCU NEC 0502 Send LED GPO Om High 241 247 Refresh AN KN01 01 Rev 0 1 page 27 35 Wubec x K NETO1 Appendix A U NETO1 DK Interface Board Board Size 95mm x 53mm Board Thickness 1mm Board Material FR4 Multi layer A 1 Interface Board Schematics JP R4 OCDOA XI ik JPl_2 MCU RESET R vel FE6USDAO Ew A xm L LA Sm A AN KNO1 01 lt Rev 0 1 gt page 28 35 K NETO1 VOC U6 CIALE ea 28 orl vr LM epom DCD DB9R25 C191 00nF 3 Ivy veo 20 J EDO DSR DBOR26 CIS DBU 5 nr wv RTS DB9 R27 DSR DB9 6 E CTS DB9 R28 DTR DBUR29 RI DB9 R30 VCC2 Je GP VCCI on n cy 3 rj qJ 2
23. le network will not recognize this device K NET provides a simpler way to identify the components by setting the network address The component function is determined by the associated address value As given in the table below Function Address value 0x0000 0x0001 0xF000 0xF001 OxFEFF I AN KN01 01 lt Rev 0 1 gt page 6 35 Bubec K NETOI 2 K NETOL 2 1 Introduction This chapter presents an overview of the features and requirements of the K NETO1 Development Kit DK Topics covered in this chapter include K NETO1 DK components Overview of the K NETO1 DK K NETO1 DK Network Bricks K NETO1 DK CD ROM U 2 2 K NET01 DK Components The K NET01 DK contains the following items Hardware U Network Brick coordinator x1 O Network Brick router x2 U Network Brick device x1 Q Battery stage x4 O USB RS232 adaptor cables Software Uu U Messenger U U Addressor LY U MACwriter 2 3 Overview of the K NETO1 DK Hardware The K NETO1 DK is designed to demonstrate UBEC s K NET network protocol solution for tree topologies over UBEC s IEEE 802 15 4 compatible solution UZ2400 K NET01 DK includes four Network Bricks comprising of three hardware boards one RF module U Force one MCU Board and one interface board Each Network Brick has been programmed by predetermined codes as a coordinator a router or a device By using AT command the Network Bricks can communicate with the application
24. module is soldered onto the MCU board Carefully plug the MCU board into the connector on the Interface Board Note that the polarization of the MCU Board RF module Care should be taken during the plugging to avoid any damages 3 Connect the 3 0 3 3V AC DC power adaptor to the 2 5mm adaptor jack or connect the battery stage as the case may be Observe the POWER_ LED on the interface board and see if it is turned on properly This confirms that the board works properly 4 Repeat step 1 to 3 for other Network Bricks Figure 5 K NETO1 DK Network Brick 3 2 2 Installing K NETO1 DK Design Environment Follow the steps below to install all necessary components into the PC and properly set up the development environment 1 Insert the K NETO1 DK CD ROM into system s CD ROM drive 2 Using Microsoft Windowse Explorer to read the CD and start the installation process by double clicking the Setup Ubec AP Ox exe icon 3 After the installation is completed all necessary files will be copied to the lt Program Files Ubec API gt directory on the root drive of the computer There will be three exe files one dat file and one ini file in the folder U MACwriter Ox exe gt MAC address Setting U Addressor Ox exe gt Parameter Address Setting U Messenger Ox exe gt UBEC Messenger Tool Sync ini Parameter File KNETDK dat gt Network data file jl wes AN KN01 01 Rev 0 1 page 12 35 Wubec K NETO1 3 2 3 K
25. ole network every Network Brick should be programmed with a dedicated address The value of the address is determined by predetermined layers and children For K NETO1 DK the default network is 2 children and 3 layers The address map is previously shown in Figure 6 One can change the linear tree topology to the star tree topology by changing the address of the Router Figure 8 shows the demonstration of such a network topology change 2Child 3 Layer 008 Routers A 005 009 00C ER TNS Routers 002 005 009 00C IM DIN DW TNS 003 004 006 007 00A 006 00D DOE Figure 8 Change of the Router Address for Network Topology 2o 7 U8EpEYs E C l l l l d i ds lli AN KN01 01 lt Rev 0 1 gt page 18 35 Wubec 1 Execute U Addressor 03 exe T Addressor K NETOI Loop 100Mb 190 msec Byte delay 0 06 msec MCU NEC 0502 Child Em O 178 Deph Lm k F PANID Oxf eg 1224 Device Mk x FOO FEFF Power Ox 00 Mas MAC Dx 2 Click Detect icon to look for available COM ports Count Save Load Exit 3 There will be three changes after users select the COM port U Addressor Com Loop 100Mb 190 msec Byte delay 0 06 msec MCU NEC 0502 Child Ern Dx 178 Depth Lm Og 177 PAN lx eg 1234 Device Nik Ox FOO FEFF Power Os OD Max MAC Dy T 4 Click Load
26. or ramma sam Peo v m PAPP SA q AT al u mid u MAE l i d E ME East Gay eee _ Load Exit d 0 00 d 0 00 d 0 00 01 01 08 01 08 K Le a Remek k 7 Users should change the color of address 08 to complete the process Otherwise the mapping data will not be changed after users save the whole map even though the content of Network Brick has been changed To complete the process click right button of the mouse again and choose Select and it will pop out the color matrix Choose the color you like except the grey color located at the right top corner When the change of mapping is successful count number on the left top corner will increase A AN KN01 01 Rev 0 1 page 20 35 Bubec K NETOI Fewer AM IMN WT pan ZH Powe Ua pH mn Poser x Max UC ma 25 MAC Ox T MAC Dx paai Detect COM 4 v zh og a SU 00 d 0 00 Read COM 4 connected 01 m 01 01 DE Save i k e ad Exit 8 To complete the set up process one also needs to eliminate the address 02 in the map because Router 0002 has been changed to Router 0008 What one needs to do is to move the layer to the one that shows 02 Again press the right button of the mouse on the 02 and choose Select It pops out the color matrix Choose the color of grey on the right top corner to de select 02 When the change of mapping is successful count number on the lef
27. ore starting the network buildup it should select a specific radio channel Then the network should select PAN ID a 32 bit value These two parameters should be pre determined by the system developer 1 7 Network Address Node Identification In K NET to reduce the system cost and increase the network robustness UBEC s K NET platform adopts a fixed address tree topology This topology will request a fixed address for every K NET device Network Address These addresses follow the rule of routing table of ZigBee specification Sec 3 7 3 ZigBee Specification Document 053474r13 and are predetermined before starting the network buildup According to that rule different layers and children have different addressing schemes as shown in the figure below Child 1 1 Layer 2 Child 3 Layer Therefore before starting the network the numbers of the layers and children of the network topology have to be decided After confirming the layers and children the network addresses can be assigned correspondingly In summary for the K NET three parameters should be decided for the node identification layer number and children number of the network and network address UBEC provides users the Graphic Unit Interface software GUI to code these parameters easily A AN KN01 01 Rev 0 1 page 5 35 Bubec K NETOI 1 8 Automatic Binding and J oining After power on a K NET node will search and join the network according to the
28. t top corner will decrease d 4 01 d 1 01 ld 1 01 i 02 e bel gt l Exit 9 To verify the content of Network Brick users can click Read icon The top of the display will show the information of the connected Network Brick The information includes Q NWK Network address Parent Upper one layer address parent s address Depth the position of layers of Network Brick Mac MAC address used in the production The MAC address can be changed by U MACwriter Cm Lm Child Layer Panl D This ID is for Network ID CH RF channels Channel 1 2405MHz Channel 2 2410MHz Channel 3 2415MHz Channel 4 2420MHz Channel 5 2425MHz Channel 6 2430MHz Channel 7 2435 MHz Channel 8 2440 MHz Channel 9 2445 MHz Channel 10 2450 MHz Channel 11 2455 MHz Channel 12 2460 MHz Channel 13 2465 MHz Channel 14 2470 MHz Channel 15 2475 MHz Channel 16 2480 MHz U U U U U U U Addressor Com5 E ml EJ Nwk 0001 Parent 0000 depth 1 Mac FFFFFFFFFFFFFFFF Count 8 SEDES Read Child Em Ox 02 178 D 02 Detect com 5 C Depth Lm Ox 03 177 0 03 OM 5 connected PAN ID Ox 0000 e g 1234 00000 CH 1 th Save r Device Nwk Ox Mw 0 0001 sd F001 FEFF Parent 0x0000 n Power Ox a i Max v O00 Exit MAC Dx FFFFFFFFFFFFFFFF AN KN01 01 Rev 0 1 page 21 35 Wubec x K NETO1 4 3 Modifying the Network Addresses of Devices Because the device chooses one and only on
29. ual for more detailed information A AN KN01 01 Rev 0 1 page 10 35 Wubec x K NETO1 3 Getting Started This section describes the following topics DU What is K NET LJ Using K NETO1 DK for the first time O Assembling K NETO1 DK Network Bricks and installing K NETO1 DK software files LJ Using UBEC Messenger to verify peer to peer communication with K NETO1 DK LJ Using UBEC Messenger to verify linear tree communication with K NETO1 DK LJ Using UBEC Messenger to verify device communication with K NETO1 DK 3 1 What is K NET Due to very diverse wireless network applications different network sizes and functions will be required to achieve optimal solutions It is very difficult to define a network protocol to suit all applications where parameters such as cost dimension data rate communication distance and programming complexity must be traded off Designers often encountered obstacles when developing modern wireless network because they may not be familiar with the network protocol or the radio frequency characteristics or even the overall cost structure As a rule of thumb if one is to start developing a product containing a wireless network from the scratch one probably will need to spend about several months to learn the basics of the RF IC the RF board design and the network protocol To reduce such a long development time UBEC has developed a low cost K NET platform to help the designers quickly gain the essenti
30. ul the caption will be changed to U Message Com x L qm ru IU Messenger Com 1 U Messenger Ver 0 3 Info U Messenger Ver 0 3 Infa 3 Click Info icon to show the predetermined parameters of the Network Brick and the location of the network U Messenger 0 3c Com 5 SEE U Messenger Ver 0 3c Detect nto COM 5 Nwk lt Info Child Max 2 Depth Max 3 Current Depth Channel Ch_1 0x08 PAN ID 0x1234 Mac 0000000000000000 wk 0000 Parent FFFF Power 0x00 E v Loop 100Mb 213 msec Byte delay 0 06 msec M Send Detect Clean COM Send Hex of Send AN KNO1 01 lt Rev 0 1 gt page 15 35 Wubec K NETO1 Router Network Brick Address 0x0001 4 Executing U Message Ox exe again in the same system or in another system 5 Select another COM port or click Detect icon to detect available COM ports If the selection is successful the caption will be changed to U Message Com Xx 6 Click Info icon to show the predetermined parameters of the Network Brick Starting to communicate 7 Fill Nwk with the address of the Network Brick users want to communicate For example if the port is Network Brick 0000 users should fill 0001 in this demonstration and vice versa Detect Info Detect Info com vi ae COM gt Wwk L I IILI 1 PM U L

K-NET01

Contents

Download Pdf Manuals

Related Search

Related Contents