MNZB-DKC-900 MeshNetics, MNZB-DKC-900 Datasheet
MNZB-DKC-900
Specifications of MNZB-DKC-900
Related parts for MNZB-DKC-900
MNZB-DKC-900 Summary of contents
Page 1
... ZigBit™ 900 Development Kit 1.3 Doc. S-ZDK-451~03 v.1.3 User’s Guide © 2008 MeshNetics October 2008 ...
Page 2
... Please visit MeshNetics website for the latest available version. MeshNetics does not assume any responsibility for the use of the described product or convey any license under its patent rights. MeshNetics warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with MeshNetics standard warranty ...
Page 3
... Running WSNDemo................................................ 36 4.6.1. Starting WSNDemo on MeshBean2 nodes36 4.6.2. Setting up node timeouts ............................ 36 4.6.3. Node Reset.................................................. 37 4.6.4. Changing Frequency Channels.................. 37 4.6.5. Visualization of the Sensor Data................. 39 5. SerialNet ......................................................... 40 © 2008 MeshNetics 6. Serial Bootloader...........................................41 7. Programming with BitCloud API.................42 7.1. API Overview............................................................42 7.2. Using AVR Programming Tools ..............................42 7 ...
Page 4
... Figure 9. Example of file containing the node titles............. 36 Figure 10. WSN Monitor Tools/Settings menu ................... 37 Figure 11. Resetting the node ............................................. 37 Figure 12. Setting channel mask dialog box ....................... 38 Figure 13. Setting the channel mask using checkboxes .... 38 Figure 14. AVR Studio dialog box for firmware upload using JTAG .................................................................... 49 © 2008 MeshNetics ’ Page 4/56 ...
Page 5
... Table 10. System requirements........................................... 23 Table 11. COM port settings for hardware testing .............. 26 Table 12. Fuse bits setting................................................... 31 Table 13. DIP switch configurations used in WSNDemo ... 33 Table 14. LED indication used in WSNDemo..................... 34 Table 15. Typical problems and solutions........................... 45 Table 16. The ZDK file structure.......................................... 47 © 2008 MeshNetics ’ Page 5/56 ...
Page 6
... Safety and Precautions The product contains electronics, which are electrically sensitive. Please take necessary precautions when using such devices. MeshNetics does its best to protect the product components from electrostatic discharge phenomena, but we encourage our users to follow common guidelines to avoid electrostatics by using proper grounding etc. ...
Page 7
... API Channel Mask Coordinator DIP EEPROM End device © 2008 MeshNetics Alternating Current / Direct Current converter Analog-to-Digital Converter Application Programming Interface Channel mask is a number that defines the set of working channels Within ZigBee networks, the ZigBee coordinator is responsible for starting the network and for choosing certain key network parameters ...
Page 8
... RAM RF RISC Router RP-SMA RS-232 RSSI RTS/CTS RX © 2008 MeshNetics Electrostatic Discharge General Purpose Input/Output Graphical User Interface Hardware Abstraction Layer Inter-Integrated Circuit Integrated Development Environment Institute of Electrical and Electronics Engineers Interrupt Request Digital interface for debugging of embedded devices, also known as IEEE 1149 ...
Page 9
... UART UID USART USB VCP WSN ZDK ZigBee, ZigBee PRO 802.15.4 © 2008 MeshNetics Surface Mount Assembly Serial Peripheral Interface bus Time To Market Transmitter Universal Asynchronous Receiver/Transmitter Unique Identifier Universal Synchronous/Asynchronous Receiver/Transmitter Universal Serial Bus Virtual Com Port Wireless Sensor Network ...
Page 10
... RF design assistance. It's ideal for customers engaged in a full cycle of developing, prototyping, and launching innovative products made possible by MeshNetics ZigBit wireless platform. It also features early software release access, © 2008 MeshNetics ’ ...
Page 11
... API use, which may be used as application "building blocks", (3) sample applications featuring integration of ZigBit w/ 3-rd party sensors. © 2008 MeshNetics Lite MNZB-DKL-900 45 days + + + 1 – 2 – – – E-mail ’ Complete MNZB-DKC-900 1 year + + + + + + + E-mail Page 11/56 ...
Page 12
... Flash Memory EEPROM Performance Power Power Supply Over-Voltage Protection Reverse Polarity Protection © 2008 MeshNetics Value AT86RF212 IEEE 802.15.4-2003 [12] 868 – 868.6 MHz, 902 – 928 MHz from -20 dBm to +11 dBm from -110 dBm to -100 dBm Pulse W1063 (868–928 MHz external antenna) ...
Page 13
... MeshBean2 Featured Components 2.2.1. ZigBit 900 Module ZigBit 900 module is an ultra-compact, low-power, high sensitivity 900 MHz 802.15.4/ZigBee OEM module from MeshNetics. ZigBit 900 module is based on Atmel’s Z-Link platform. It includes ATmega1281V Microcontroller and AT86RF212 RF Transceiver. In ZDK, every ZigBit 900 module is delivered installed on a MeshBean2 board. ...
Page 14
... See Figure 2 for the layout of MeshBean2 with external antenna. See also Figure 3 for the board’s functional diagram. 5 8MHz requires changes in the BitCloud Software that normally runs at 4 MHz in order to extend the voltage range and decrease power consumption. © 2008 MeshNetics 2 C interface with ESD protection and voltage level translation ’ ...
Page 15
... ™ Figure 2. MeshBean2 and UID Silicon Serial © 2008 MeshNetics ’ Page 15/56 ...
Page 16
... ™ Figure 3. MeshBean2 functional diagram 2.3.1. Connectors and Jumpers The board connector pinouts and jumper settings are presented in Table 3 through Table 8. IMPORTANT NOTE: All manipulations with connectors or jumpers should be done when the board is not powered! © 2008 MeshNetics ’ Page 16/56 ...
Page 17
... RESET 12 USART_TXD 13 USART_RXD 14 USART_CLK 15 GND 16 ADC_INPUT1 © 2008 MeshNetics I/O Description Input Request to Send Pin. RS-232 level. Input Transmit Data Pin (meaning that the host device will transmit data to this line). RS-232 level. Output Clear To Send signal from the module. Active low. RS-232 level. ...
Page 18
... NOTE: JTAG connector pinout is compatible with ATmega JTAGICE mkII in-circuit emulator connector. Table 5. J1 jumper settings: current measurement Jumper position J1 is mounted © 2008 MeshNetics I/O Description Input ADC input. This pin is connected directly to the ADC_INPUT_2 pin of the module. For details, refer to ZigBit 900 datasheet [1] ...
Page 19
... LEDs (green, yellow and red) and a LED indicating powering the board from the USB. Any of onboard buttons, DIP switches and LEDs can be controlled by an embedded application running on a ZigBit 900. © 2008 MeshNetics Description In this position, the ZigBit 900 module is not powered while remaining parts of the board are powered ...
Page 20
... BitCloud Software BitCloud is a full-featured, next generation embedded software stack from MeshNetics. The stack provides a software development platform for reliable, scalable, and secure wireless applications running on MeshNetics ZigBit modules. BitCloud is designed to support a broad ecosystem of user-designed applications addressing diverse requirements and enabling a full spectrum of software customization ...
Page 21
... Peer-To-Peer Data Exchange (Peer2peer) • Blink minimal sample application (Blink) The WSNDemo application is a featured ZDK application demonstrating the WSN performance presented in details in Section 4. The source code for WSNDemo is available with Complete Support Package only. © 2008 MeshNetics ’ Page 21/56 ...
Page 22
... ™ The rest of programs are sample implementations triggering common BitCloud APIs. Blink is a minimal application (see Section 7.3). Low Power Ping-Pong, and Peer-To-Peer applications are introduced in Section 7.4. © 2008 MeshNetics ’ Page 22/56 ...
Page 23
... Hard disk free space JTAG emulator Software Operating system USB driver IDE Serial Bootloader utility Java virtual machine Microsoft .NET framework © 2008 MeshNetics Value Note Intel Pentium III or higher, 800 MHz 128 JTAGICE mkII emulator Necessary to upload and debug with cable ...
Page 24
... Make sure that the driver is installed successfully and the new COM port is present in the device list. Open the Device Manager window shown in Figure 5: Start/Control Panel/System/Hardware/Device Manager. Figure 5. COM port drivers in the Windows Device Manager window To resolve possible problems see Section 3.4. © 2008 MeshNetics ’ Page 24/56 ...
Page 25
... ZDK). Serial port pinout is presented in Table 8. IMPORTANT NOTE: USB and serial port (RS-232) share the same physical port on the board. They cannot be used at the same time. Keep in mind that the connection mode is controlled by setting of jumper J3 (see Table 7). © 2008 MeshNetics ’ Page 25/56 ...
Page 26
... Stop Bits Flow Control Type the “AT” command and press Enter key. The board responds to Hyper Terminal with “OK“. Now, a user can play various networking scenarios by sending AT commands fully described in [3]. © 2008 MeshNetics ’ Value 38 400 bps 8 None ...
Page 27
... Apparently, Hyper Terminal does not recognize such changes. If this happens, you have to reconnect Hyper Terminal to a proper port. Simply select File/New Connection menu item and repeat the connection procedure. Figure 6. Hyper Terminal Hardware Test report © 2008 MeshNetics ’ Page 27/56 ...
Page 28
... Contrarily, at distances of several centimeters the pattern is more complex. Approximate field patterns are given in the ZigBit 900 datasheet [1]. Handle the external antenna with care to avoid mechanical damage. © 2008 MeshNetics ’ Page 28/56 ...
Page 29
... The application is delivered with source code included (see Appendix A implemented on top of the BitCloud API and it can be modified as described in Section 7. With WSNDemo, the number of routers and/or end devices used is limited only by the network parameters described in Section 7.4. © 2008 MeshNetics ’ Page 29/56 ...
Page 30
... EEPROM, BitCloud attempts to load MAC address from UID chip. If there is no UID, the node will not be able to join the network 6 Another JTAG programmer may be also used but it should be compatible with the Atmel 1281 MCU. © 2008 MeshNetics 6 (see Section 4.2.2) is recommended. [7] ) ...
Page 31
... Set the following options on the Fuses tab before uploading the image through JTAG: Table 12. Fuse bits setting Option BODLEVEL OCDEN JTAGEN SPIEN WDTON EESAVE BOOTSZ © 2008 MeshNetics Value Brown-out detection disabled Disabled Enabled Enabled Disabled Disabled Boot Flash size=1024 words start address=$FC00 ’ ...
Page 32
... By default, each of the boards (MCU) is preprogrammed with this fuse setting. In addition, JTAG can be used to restore the device's ability to respond to Serial Bootloader commands. Serial Bootloader firmware can be reprogrammed with JTAG by selecting bootloader.hex image contained in your ZDK 900 Distribution CD and uploading it to the device. © 2008 MeshNetics Value Disabled Enabled Disabled Int. RC Osc. ...
Page 33
... At that moment, LED1, LED2 and LED3 are flashing once on router, they are flashing twice on end device and they are flashing three times on coordinator. After joining the network, a node starts sending data to the coordinator, which is indicated by LEDs. © 2008 MeshNetics Description 3 OFF Board is configured coordinator. ...
Page 34
... In case the board is powered via USB port, the heating voltage regulator, which is located next to the temperature sensor, can distort the sensor readings. Use battery-powered boards for more accurate measurements. © 2008 MeshNetics LED state LED1 (Red) LED2(Yellow) ...
Page 35
... Node Data Pane includes a Sensor Selection combo-box used to switch between sensor types. Node titles are defined in the NodeNames.txt file. By default located in the following subdirectory: "./Evaluation Tools/WSNDemo (WSN Monitor)/resources/ configuration/”. © 2008 MeshNetics ’ Page 35/56 ...
Page 36
... Topology tree. To get smooth topology visualization, setting timeouts to 3 sec is recommended for coordinator and router and 30 sec is recommended for end device. Those timeouts cover 3 periods between packet sending. © 2008 MeshNetics ’ Page 36/56 ...
Page 37
... Changing Frequency Channels The network operation is supported on 11 channels (one in 868 MHz band and 10 in 906-928 MHz band), which are numbered from 0(0x00) through 10(0x0A). Use Tools/Send Command dialog box to set channel mask. By default, current channel © 2008 MeshNetics ’ Page 37/56 ...
Page 38
... LED3 turns ON. LED1 flashes shortly to indicate sending a packet, LED1 flashes shortly to indicate having received acknowledgement. Next, all LEDs get turned OFF when end device is falling to sleep. © 2008 MeshNetics ) of channel mask should be set to 0. The rest 27 least significant bits 31 ...
Page 39
... Sensor Data Graph Pane. You can easily check how they evolve over time. The Sensor Data Graph Pane includes a Sensor Selection combo-box. Use the button on the Sensor Control Toolbar to display the desired types of sensor data. © 2008 MeshNetics ’ Page 39/56 ...
Page 40
... Examples section of the document [3]. NOTE: The +IFC and +IPR commands both change the rate and flow control parameters of Serial/USB port. If any of these commands is used, the COM port settings on the terminal program running on the PC should be changed accordingly. © 2008 MeshNetics ’ Page 40/56 ...
Page 41
... Development Kit, each MeshBean2 board is delivered with fuse bits set up and the bootstrap preloaded to ZigBit MCU. Bootstrap itself can be recovered using JTAG when necessary supplied in form of bootloader.hex image file (see Appendix A). Exhaustive information on using Serial Bootloader is contained in [7]. © 2008 MeshNetics ’ Page 41/56 ...
Page 42
... In AVR Studio, the development of an application is organized under particular project. All the necessary information about a project is kept in project file. Such files assigned to the AVR Studio have an *.aps extension, so they open in AVR Studio automatically when double-clicked. © 2008 MeshNetics ’ Page 42/56 ...
Page 43
... WSNDemo is presented in details in Section 4. The source codes for WSNDemo application can be found inside the “./Sample Applications/WSNDemo“ subdirectory (see Appendix A), once the Development Kit is installed to user’s PC (see Section 3.3). © 2008 MeshNetics ’ Page 43/56 ...
Page 44
... Applications/WSNDemo/“ subdirectory with AVR Studio and just execute Build/Rebuild All item from the main menu. The WSNDemoApp.hex and WSNDemoApp.srec image files will be then generated. Low-Power, Peer-to-peer and Ping-Pong applications are described in details in [4]. © 2008 MeshNetics ’ Page 44/56 ...
Page 45
... DATA in the Sensor Data Graph Pane. Node titles displayed on the Topology Pane do not show node destinations. © 2008 MeshNetics Solution Make sure that either WSNDemo image or Hardware Test image is loaded. For SerialNet, the LED status is controlled by AT-commands. Make sure the external antenna is not broken and it is properly connected to the board ...
Page 46
... Neither Serial Bootloader nor other application work with a node, except for the Hardware Test. © 2008 MeshNetics Solution The WSNDemo application was not uploaded into the node. Upload this application to the node. Make sure that J3 is set on the board properly to correspond to the actual connection type (either Serial or USB) ...
Page 47
... Test/HardwareTest.hex ./Evaluation Tools/Range Measurement Tool/range_tool.vi ./Evaluation Tools/Range Measurement Tool/RangeTestRF212.hex ./Evaluation Tools/Range Measurement Tool/RangeTestRF212.srec ./Evaluation Tools/SerialNet/BPSK ./Evaluation Tools/SerialNet/O-QPSK © 2008 MeshNetics ’ Description Introductory document containing the links to the documentation files The ZDK release notes End User License Agreement Documentation on hardware and ...
Page 48
... Using AVR Studio both flash memory and EEPROM of a board can be separately programmed with images having Intel HEX format. EEPROM image has .eep extension while flash image has .hex extension. To upload firmware, follow the instructions from © 2008 MeshNetics ’ Description ...
Page 49
... IMPORTANT NOTES: To avoid corruption of the bootstrap code required for serial booting, do not erase device when using JTAG. For JTAG programming, the Boot Reset vector fuse bit should be disabled. To enable serial booting this fuse bit should be enabled. © 2008 MeshNetics ’ Page 49/56 ...
Page 50
... MIN_BLINK_PERIOD 100 #endif #ifndef MAX_BLINK_PERIOD #define MAX_BLINK_PERIOD 10000 // Maximum blink period, ms. #endif #define BLINK_INTERVAL // Blink interval. #define MIN_BLINK_INTERVAL // Minimum blink interval. #define MAX_BLINK_INTERVAL // Maximum blink interval. #ifndef _BUTTONS_ © 2008 MeshNetics ’ Minimum blink period, ms. (BLINK_PERIOD / 2) (MIN_BLINK_PERIOD / 2) (MAX_BLINK_PERIOD / 2) Page 50/56 ...
Page 51
... BSP_OpenButtons(NULL, buttonsReleased); Register button event handlers #else // Configure blink timer changeBlinkTimer.interval = 10000; interval changeBlinkTimer.mode Repeating mode (TIMER_REPEAT_MODE or TIMER_ONE_SHOT_MODE) changeBlinkTimer.callback = changeTimerFired; Callback function for timer fire event © 2008 MeshNetics 0 1 BSP_KEY0 BSP_KEY1 // // Timer = TIMER_REPEAT_MODE ’ Page 51/56 ...
Page 52
... Description: blinking timer fire event handler. Parameters: none. Returns: nothing. ***********************************************************/ static void blinkTimerFired() { BSP_ToggleLed(LED_RED); BSP_ToggleLed(LED_YELLOW); BSP_ToggleLed(LED_GREEN); } /*********************************************************** Description: button release event handler. Parameters: buttonNumber - released button number. Returns: nothing. ***********************************************************/ © 2008 MeshNetics = TIMER_REPEAT_MODE ’ Start // Timer // // // Start Page 52/56 ...
Page 53
... HAL_StartAppTimer(&blinkTimer); // Start updated blink timer. } /*********************************************************** Description: just a stub. Parameters: are not used. Returns: nothing. ***********************************************************/ void ZDO_MgmtNwkUpdateNotf(ZDO_MgmtNwkUpdateNotf_t *nwkParams) { nwkParams = nwkParams; prevention } /*********************************************************** Description: just a stub. Parameters: none. Returns: nothing. ***********************************************************/ void ZDO_WakeUpInd(void © 2008 MeshNetics // Update LED status // Unused parameter warning ’ Page 53/56 ...
Page 54
... Output debug port for ARM platforms only ------------ ifeq ($(HAL), AT91SAM7X256) CFLAGS += -D_DBG_ endif # Stack libraries paths ------------------------------ LIB_PATH = -L$(COMPONENTS_PATH)/../lib \ -L$(CS_PATH)/lib -L$(BSP_PATH)/lib ## Stack include paths -------------------------------- INCLUDES = -I$(SE_PATH)/include -I$(APS_PATH)/include -I$(NWK_PATH)/include © 2008 MeshNetics -L$(PDS_PATH)/lib \ \ \ \ ’ Page 54/56 ...
Page 55
... Server library creation------- make all -C $(CS_PATH) $(PRJ_NAME).o: %.o: %.c @echo @echo -------Application executable creation------------- $(CC) -c $(CFLAGS) $(INCLUDES $(PRJ_NAME).elf: $(PRJ_NAME).o $(CC) $(CFLAGS) $(LIB_PATH) $(LINK_OBJECTS) -l$(STACK_LIB) -l$(CS_LIB) - l$(PDS_LIB) -l$(BSP_LIB) -l$(STACK_LIB) $(LDSCRIPT) $(LINKER_FLAGS) © 2008 MeshNetics \ \ \ \ \ \ $(INCLUDES) $(PRJ_NAME). ’ Page 55/56 ...
Page 56
... Server library cleaning------- make clean -C $(CS_PATH) @echo # eof Makefile © 2008 MeshNetics %.elf %.elf ’ $< binary $< $@ Page 56/56 ...