DOCSLIB.ORG

Microchip Wireless Miwi Application Programming Interface

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

AN1284 Microchip Wireless MiWi™ Application Programming Interface – MiApp Authors: Yifeng Yang The MiApp specification defines the programming Pradeep Shamanna interfaces between the application layer and Microchip Derrick Lattibeaudiere proprietary wireless communication protocols. The Vivek Anchalia MiApp programming interface is implemented in two Microchip Technology Inc. ways: as configuration parameters defined in the con- figuration file, and as a set of function calls to the Micro- chip proprietary wireless communication protocols. INTRODUCTION Complying with the MiApp specification defined in this Developing wireless applications can be challenging. application note, applications can use any Microchip Apart from Radio Frequency (RF) circuit designs, the proprietary wireless protocols. With little or no modifica- firmware development process may require the devel- tion in the application layer, software development can opers to understand the details of RF transceivers, as be easily changed between a proprietary P2P/Star well as the different wireless communication protocols. topology connection protocol to a full Mesh proprietary Microchip has developed a way to handle the complex networking protocol for small or big networks, depend- RF hardware or communication protocol stack software ing on the application needs. development, or both, which enables wireless applica- tion developers to focus on their own application devel- opment. This type of wireless communication is achieved through a concise, yet powerful communica- tion programming interface in the application layer called MiApp which is defined in this application note. FIGURE 1: BLOCK DIAGRAM OF MICROCHIP WIRELESS MiWi™ STACK Application User A ppl ic ati on Configuration MiApp MiWi™ P2P/Star MiWi™ Mesh Protocol Configuration Future Microchip Proprietary Wireless Protocols ... Interchangeable Wireless Communication Protocols MiMAC MRF24J40 Transceiver RF Transceiver MRF89XA Transceiver Configuration Future Microchip RF Transceivers ... Interchangeable RF Transceivers 2009-2017 Microchip Technology Inc. DS00001284B-page 1 AN1284 The MiApp specification benefits wireless application CONSIDERATIONS developers in multiple ways: The MiApp specification is designed to support Micro- • Wireless application development focuses on its chip proprietary wireless communication protocols. application. Complex RF or protocol consider- Once a wireless application is implemented by the ations are transparently handled by the MiApp MiApp programming interface, the Microchip RF trans- programming interface. ceivers are also supported through standardization in • The MiApp specification allows maximum flexibil- MiMAC, the module defined in the Media Access Con- ity to choose a wireless protocol at any stage of troller (MAC) layer. application software development with little effort, thus greatly lowering the risk of software develop- MiMAC standardizes the interface between Microchip ment. Application requirement changes in net- wireless protocols and Microchip RF transceivers. working capabilities have little or no impact in MiMAC makes Microchip RF transceivers interchange- application development. able with little or no change in the software application code. For more information on MiMAC, refer to the • MiApp uses the same control interface for Application Note “AN1283 Microchip Wireless MiWi™ Microchip wireless proprietary protocols. Once Media Access Controller - MiMAC” (DS00001283). you are familiar with MiApp, you can apply that knowledge to the development of another applica- MiMAC regulates the lower interface of the Microchip tion even if it has a completely different network- proprietary wireless protocols, while MiApp regulates ing capability requirement. the higher interface of the Microchip proprietary wire- • By communicating to the Microchip proprietary less protocols. Working together, both MiMAC and protocols, MiApp indirectly talks to the Microchip MiApp provide wireless application developers the RF transceivers through the MiMAC interface. As maximum flexibility to choose the RF transceivers and a result, MiApp indirectly enables the wireless wireless communication protocols at any stage of soft- application developers to switch between ware development, thus further minimizing the risk of Microchip RF transceivers through MiMAC. This software development.The block diagram in Figure 1 flexibility, in turn, further reduces the development shows the Microchip Wireless MiWi™ stack offerings. risk of the wireless application project. There are three layers of configurations for application, protocol stacks and RF transceivers. Application con- FEATURES figuration may change between devices in the same application according to their hardware design, role in The MiApp programming interface has the following the application and network. Wireless application features: developers tend to do the majority of the configuration in the application layer. Protocol configurations fine- • Easy to learn and use tune the behavior of the protocol stack. The majority of • Powerful interface to meet most requirements protocol stack configurations define the timing and from wireless applications routing mechanism for the chosen wireless protocol. • Little or no extra effort to migrate the wireless Transceiver configurations define the frequency band, application between Microchip proprietary data rate and other RF related features of the RF trans- wireless protocols ceiver. The default settings for the protocol and RF • Minimum footprint impact transceiver configurations may work with the applica- tion without any modification. The application configu- rations, however, usually need to be changed to fit the needs of different wireless applications. DS00001284B-page 2 2009-2017 Microchip Technology Inc. AN1284 MiApp OVERVIEW MiApp CONFIGURATION FILE As discussed earlier, there are two parts defined in the The hardware definitions depends on the choices of the MiApp specification: Demo/Development boards, the MCUs and the RF • Configuration parameters defined in the transceivers. The hardware definitions can be divided configuration file into the following subcategories: • Signatures of function calls to the Microchip • I/Os on the demo board – these includes the push proprietary wireless protocols buttons, LEDs, serial ports, and so on. The configuration file contains parameters that must be • MCU system resources – these includes the set before compilation. Generally, there are two types timers, interrupts, and so on. of parameters defined in the configuration file: • Interconnections between MCU and RF transceiver • Hardware Definitions – these includes MCU hardware resources, peripherals definition and Hardware definitions are mainly associated with hard- the definition for the RF transceiver control pins. ware selections of the wireless application system The default hardware definitions are defined in design. They depend more on the hardware than the several Microchip standard demo boards that software and vary across different designs. As a result, support Microchip RF transceivers. In these MiApp does not have a set of standards for those cases, the definition of demo boards automatically hardware definitions. introduces all hardware definitions. Selective compilation configurations select the features • Software Definitions – these definitions control among the list of available ones. Using the selective the code sections to be compiled into the firmware compilation, application developers are able to config- hex file. The software definitions include selec- ure Microchip proprietary wireless protocols to perform tions of Microchip proprietary wireless protocol, the desired functionality with the least possible system choice of Microchip RF transceiver, and individual resources. Table 1 describes the possible selective functionalities. Proper definitions in this category compilation configurations and its scope, value, and ensure the minimum firmware footprint with the functionality. intended protocol capabilities. Application Programming Interfaces (APIs) are the function calls between the Microchip proprietary wireless communication protocols with the wireless application. As a rule, the application interface must be clean, concise, easy to understand, and powerful. There are five categories of interfaces for the APIs: • The initialization interface allows wireless applica- tion developers to properly initialize the selected Microchip proprietary wireless protocol in the con- figuration file. • The handshaking interface allows the wireless nodes to discover and get connected with their peers, or to join the network. • Interfaces to send messages which enable appli- cation developers to transmit information from the current node to an intended audience over-the-air. • Interfaces to receive messages which enable application developers to receive information over- the-air from other devices. • Special functionalities which ensure the optimal operating condition for wireless nodes through environment noise control and power saving. 2009-2017 Microchip Technology Inc. DS00001284B-page 3 AN1284 TABLE 1: APPLICATION LAYOUT SOFTWARE DEFINITIONS IN A CONFIGURATION FILE Application Definitions Functionality Comments #define PROTOCOL_P2P Selects the Microchip proprietary Only one protocol can be defined at any #define PROTOCOL_STAR wireless protocol to be used in the one time. #define PROTOCOL_MESH wireless application. #define MRF24J40 Selects the Microchip RF trans-
Recommended publications
  • Acceleration of Applications with FPGA-Based Computing Machines: Code Restructuring

    Acceleration of Applications with FPGA-Based Computing Machines: Code Restructuring

    FACULDADE DE ENGENHARIA DA UNIVERSIDADE DO PORTO Acceleration of Applications with FPGA-Based Computing Machines: Code Restructuring Tiago Lascasas dos Santos Mestrado Integrado em Engenharia Informática e Computação Supervisor: João M. P. Cardoso, PhD Co-supervisor: João Bispo, PhD July 31, 2020 c Tiago Santos, 2020 Acceleration of Applications with FPGA-Based Computing Machines: Code Restructuring Tiago Lascasas dos Santos Mestrado Integrado em Engenharia Informática e Computação Approved in oral examination by the committee: Chair: Prof. João Paulo de Castro Canas Ferreira, PhD External Examiner: Dr. José Gabriel de Figueiredo Coutinho, PhD Supervisor: Prof. João Manuel Paiva Cardoso, PhD July 31, 2020 Abstract Field-programmable gate arrays (FPGAs) can be used to accelerate performance-critical programs from a wide range of fields and still providing energy-efficient solutions. Programs written in high level languages, such as C and C++, can be compiled to FPGAs through High-level Synthesis (HLS). Although FPGAs benefit the most from parallel and data-streaming applications, efficient compilation to FPGAs is a problem for both tools and developers. Most applications do not follow these patterns, and extensive code restructuring and the use of HLS directives need to be applied to a program in order to take advantage of FPGAs. Code restructuring and the use of HLS directives often needs to be manually performed by an experienced developer, and as such there is a need to automate this process. This dissertation proposes a framework that automatically optimizes C code via directives, using a source-to-source compiler on a stage prior to HLS. This optimization is primarily applied by strategies that select, configure and insert directives on the code to be input to an HLS tool, e.g., Vivado HLS, in order to synthesize more efficient hardware accelerators.
  • Concepts General Concepts Wireless Sensor Networks (WSN)

    Concepts General Concepts Wireless Sensor Networks (WSN)

    Wireless Sensor Networks – Concepts General Concepts Wireless Sensor Networks (WSN) are built based on a combination of multiple sensors placed in diverse locations, wireless communication network infrastructure and software data processing to monitor and record multiple parameters. Commonly monitored parameters are temperature, atmospheric pressure, humidity, vibration, illuminance, sound level, power consumption, chemical concentration, body health signals and many others, dependant on the selected available sensors. The WSN are used in multiple fields, ranging from remote environment monitoring, medical health, to home surveillance and industrial machines monitoring. In some cases, WSN can also be additionally used for control functions, apart from monitoring functions. Typically a WSN is made of sensor nodes that are wirelessly connected to a gateway that is then connected to a main computer (Fig. 1). In some WSN the sensor nodes can also be connected to each other, so that is possible to implement multi-hop wireless mesh networks. The gateway connects to the main computer through a cabled or wireless connection. Figure 1 – Wireless sensor network The wireless communications used in WSN depend on the application requirements, taking into consideration the needs in terms of transmission distance, sensor data bandwidth, energy source and power consumption. Common communications include standard protocols such as 2.4 GHz radio based on either IEEE802.15.4 (ZigBee, ISA 100, WirelessHart, MiWi) or IEEE802.11 (WiFi) standards. Each sensor node typically includes an embedded microcontroller system with adequate electronic interface with a sensor (or set of sensors), a radio transceiver with antenna (internal or external) and an energy source, usually a battery, or in some cases an energy harvesting circuit.
  • Linux DVB API Version 4

    Linux DVB API Version 4

    Linux DVB API Version 4 http://www.linuxdvb.org v 0.3 April 15, 2005 Copyright c 2004,2005 The Linux DVB developers Written by Michael Hunold <[email protected]> Parts are based on the Linux DVB API Version 3 documentation, released under the GNU Free Documentation License. Written by Dr. Ralph J.K. Metzler and Dr. Marcus O.C. Metzler. Copyright 2002, 2003 Convergence GmbH. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation. http://www.gnu.org/licenses/fdl.html Contents 1 Introduction 1 1.1 Goals ....................................... 1 1.2 Related technologies ............................... 2 1.3 History ...................................... 2 2 Design 4 2.1 Present situation ................................. 4 2.2 Linux DVB API Version 3 problems ...................... 4 2.3 Linux DVB API Version 3 vs. Version 4 .................... 5 3 Concepts 6 3.1 Control concept .................................. 6 3.2 Capability concept ................................ 6 3.3 Connection concept ................................ 6 3.4 Status concept .................................. 7 4 Frontend API 8 4.1 Device informations ............................... 8 4.2 Satellite equipment control (SEC) commands ................ 9 4.3 DiSEqC commands ............................... 11 4.4 Frontend status ................................. 12 4.5 Configuration and tuning ........................... 12 4.6 Event handling ................................. 14 5 Memory input API 15 5.1 Device informations ............................... 15 5.2 Configuration .................................. 15 5.3 Data input .................................... 16 6 Demux API 17 6.1 Capabilities ................................... 18 6.2 Device input setup ............................... 19 6.3 MPEG-2 TS filters ............................... 19 6.3.1 TS decoder feeds ............................ 20 6.3.2 Pid filters ...............................
  • Internet of Things (Iot): Protocols White Paper

    Internet of Things (Iot): Protocols White Paper

    INTERNET OF THINGS (IOT): PROTOCOLS WHITE PAPER 11 December 2020 Version 1 1 Hospitality Technology Next Generation Internet of Things (IoT) Security White Paper 11 December 2020 Version 1 About HTNG Hospitality Technology Next Generation (HTNG) is a non-profit association with a mission to foster, through collaboration and partnership, the development of next-generation systems and solutions that will enable hoteliers and their technology vendors to do business globally in the 21st century. HTNG is recognized as the leading voice of the global hotel community, articulating the technology requirements of hotel companies of all sizes to the vendor community. HTNG facilitate the development of technology models for hospitality that will foster innovation, improve the guest experience, increase the effectiveness and efficiency of hotels, and create a healthy ecosystem of technology suppliers. Copyright 2020, Hospitality Technology Next Generation All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner. For any software code contained within this specification, permission is hereby granted, free-of-charge, to any person obtaining a copy of this specification (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the above copyright notice and this permission notice being included in all copies or substantial portions of the Software.
  • NANODUST NETWORK for TACTICAL BORDER SURVEILLANCE SYSTEM N.Sivakumar1, T

    NANODUST NETWORK for TACTICAL BORDER SURVEILLANCE SYSTEM N.Sivakumar1, T

    International Journal of Advance Research In Science And Engineering http://www.ijarse.com IJARSE, Vol. No.4, Special Issue (02), February 2015 ISSN-2319-8354(E) NANODUST NETWORK FOR TACTICAL BORDER SURVEILLANCE SYSTEM N.SivaKumar1, T. Sivasankari2 1,2 P.G Student, Raja College of Engineering and Technology, Madurai, Tamilnadu, (India) ABSTRACT The greatest threat to national security is “Terrorism”infiltrating through borders. In critical border areas such as Kashmir and Bangladesh regular forces or even satellites cannot monitor these intruding terrorists as the area monitored is quite large and quite complex. This project provides an innovative and effective solution to this problem. Keywords: IEEE 802.15.4, PIR Sensor, Buzzer, PCB Antenna I. INTRODUCTION The small dust like wireless sensor motes which has multiple onboard sensors and a processor, which has the ability to detect an enemy intrusion across borders and battlefields. Thousands of these smart dust motes can be deployed within a large area in a few hours by one or two men. The motes can form a network on its own among them, are small in size, rapidly deployable, have wireless connection to outside world. They detect the intrusion and classify it into vehicles or individuals and groups. Onboard hardware include a variety of sensors for vibration/seismic, magnetic, acoustic and thermal signature recognition, a microcontroller for processing these sensor values and a radio transceiver for communication over a wireless network. The system process the sensor readings, classify the targets and the tracking history can be viewed in the Graphics LCD display attached in the central monitoring unit.
  • IEEE 802.11 B/G/N Smartconnect Iot Module

    IEEE 802.11 B/G/N Smartconnect Iot Module

    ATWINC15x0-MR210xB IEEE 802.11 b/g/n SmartConnect IoT Module Description The ATWINC15x0-MR210xB is a low-power consumption 802.11 b/g/n IoT (Internet of Things) module, which is specifically optimized for low-power IoT applications. The module integrates Power Amplifier, LNA, Switch, Power Management, and a choice of printed antenna or a micro co-ax (u.FL) connector for an external antenna resulting in a small form factor (21.7x14.7x2.1mm) design. With seamless roaming capabilities and advanced security, it could be interoperable with various vendors’ 802.11 b/g/n access points in wireless LAN. The module provides SPI ports to interface with a host controller. Note that all references to the ATWINC15x0-MR210xB module includes all the module devices listed below unless otherwise noted: • ATWINC1500-MR210PB • ATWINC1500-MR210UB • ATWINC1510-MR210PB • ATWINC1510-MR210UB Features • IEEE® 802.11 b/g/n 20MHz (1x1) solution • Single spatial stream in 2.4GHz ISM band • Integrated Transmit/Receive switch • Integrated PCB antenna or u.FL micro co-ax connector for external antenna • Superior Sensitivity and Range via advanced PHY signal processing • Advanced Equalization and Channel Estimation • Advanced Carrier and Timing Synchronization • Wi-Fi Direct and Soft-AP support • Supports IEEE 802.11 WEP, WPA, WPA2 Security • Superior MAC throughput via hardware accelerated two-level A-MSDU/A-MPDU frame aggregation and block acknowledgment • On-chip memory management engine to reduce host load • SPI host interface • Operating temperature range of -40°C to +85°C. RF performance guaranteed at room temperature of 25oC with a 2-3db change at boundary conditions.
  • Dual Protocol Performance Using Wifi and Zigbee for Industrial WLAN

    Dual Protocol Performance Using Wifi and Zigbee for Industrial WLAN

    American University in Cairo AUC Knowledge Fountain Theses and Dissertations 2-1-2016 Dual protocol performance using WiFi and ZigBee for industrial WLAN Ghada Afifi Follow this and additional works at: https://fount.aucegypt.edu/etds Recommended Citation APA Citation Afifi, G. (2016).Dual protocol performance using WiFi and ZigBee for industrial WLAN [Master’s thesis, the American University in Cairo]. AUC Knowledge Fountain. https://fount.aucegypt.edu/etds/352 MLA Citation Afifi, Ghada. Dual protocol performance using WiFi and ZigBee for industrial WLAN. 2016. American University in Cairo, Master's thesis. AUC Knowledge Fountain. https://fount.aucegypt.edu/etds/352 This Thesis is brought to you for free and open access by AUC Knowledge Fountain. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of AUC Knowledge Fountain. For more information, please contact [email protected]. The American University in Cairo School of Sciences and Engineering DUAL PROTOCOL PERFORMANCE USING WIFI AND ZIGBEE FOR INDUSTRIAL WLAN A Thesis Submitted to Electronics and Communication Engineering Department in partial fulfillment of the requirements for the degree of Master of Science by Ghada Sameh Afifi under the supervision of Prof. Hassanein H. Amer and Dr. Ramez Daoud July 2016 i ii To my Family and Friends iii Abstract The purpose of this thesis is to study the performance of a WNCS based on utilizing IEEE 802.15.4 and IEEE 802.11 in meeting industrial requirements as well as the extent of improvement on the network level in terms of latency and interference tolerance when using the two different protocols, namely WiFi and ZigBee, in parallel.
  • Windows Internals, Sixth Edition, Part 2

    Windows Internals, Sixth Edition, Part 2

    spine = 1.2” Part 2 About the Authors Mark Russinovich is a Technical Fellow in ® the Windows Azure™ group at Microsoft. Windows Internals He is coauthor of Windows Sysinternals SIXTH EDITION Administrator’s Reference, co-creator of the Sysinternals tools available from Microsoft Windows ® The definitive guide—fully updated for Windows 7 TechNet, and coauthor of the Windows Internals and Windows Server 2008 R2 book series. Delve inside Windows architecture and internals—and see how core David A. Solomon is coauthor of the Windows Internals book series and has taught components work behind the scenes. Led by a team of internationally his Windows internals class to thousands of renowned internals experts, this classic guide has been fully updated Windows developers and IT professionals worldwide, SIXTH for Windows 7 and Windows Server® 2008 R2—and now presents its including Microsoft staff. He is a regular speaker 6EDITION coverage in two volumes. at Microsoft conferences, including TechNet As always, you get critical, insider perspectives on how Windows and PDC. operates. And through hands-on experiments, you’ll experience its Alex Ionescu is a chief software architect and internal behavior firsthand—knowledge you can apply to improve consultant expert in low-level system software, application design, debugging, system performance, and support. kernel development, security training, and Internals reverse engineering. He teaches Windows internals courses with David Solomon, and is ® In Part 2, you will: active in the security research community.
  • Microchip Miwi and P2P IEEE 802.15.4 Reference Files Dr

    Microchip Miwi and P2P IEEE 802.15.4 Reference Files Dr

    Microchip MiWi and P2P IEEE 802.15.4 Reference Files Dr. Richard Wall – Professor Department of Electrical and Computer Engineering University of Idaho Moscow, ID 83844-1023 December 19, 2012 [email protected] 1. ZigBee and Wireless Standards - see http://www.stg.com/wireless/ZigBee_comp.html. https://sites.google.com/site/xbeetutorial/ 2. Basic Concepts a. Definition of: ZigBee "A wireless network used for home, building and industrial control. It conforms to the IEEE 802.15.4 wireless standard for low data rate networks. With a maximum speed of 250 Kbps at 2.4 GHz, ZigBee is slower than Wi-Fi and Bluetooth, but is designed for low power so that batteries can last for months and years. The typical ZigBee transmission range is roughly 50 meters, but that can vary greatly depending on temperature, humidity and air quality. b. Zigzag Like a Bee Although ZigBee networks can be configured in star, peer-to-peer and mesh topologies, it is the mesh network from which ZigBee was named. A ZigBee mesh provides multiple pathways from device to device (like the Internet) and eliminates a single point of failure. If nodes go down or are removed, ZigBee devices can "zig" and "zag" through the network to their destination like a bumblebee. 1 Page c. Lots of Bees1 ZigBee networks are simple control networks that periodically send small packets from sensors to regulate lights, motors and other equipment. A large building can have tens of thousands of ZigBee nodes; a home could have a hundred or more. In fact, ZigBee can address more than a thousand quadrillion devices (surely enough for the gadget fanatic's apartment!).
  • Wireless Communication Platform Iqrf – a Case Study

    Wireless Communication Platform Iqrf – a Case Study

    WIRELESS COMMUNICATION PLATFORM IQRF – A CASE STUDY Zdeňka Kuchtová Doctoral Degree Programme (2nd), FEEC BUT E-mail: [email protected] Supervised by: Jaroslav Kadlec E-mail: [email protected] Abstract: This paper describes wireless communication platform IQRF, history of development, available modules and accessories for development and for production use. Very briefly are described communication gateways and cloud services. Part of the article describes DPA communication framework from Microrisc company and summarizes available communication frameworks for different platforms. Keywords: IQRF, DPA, IoT, Communication framework 1. INTRODUCTION Terms like Internet of Things, Smart City, Smart buildings are quite often used in today world. They have at least one common fact, they need communication inside solution and with outside world. For this communication needs wireless or wired solutions are available. Each of them has some advantages and some disadvantages [1, 2, 3]. Within this paper, we will talk about wireless solutions only. There is a wide range of the wireless solutions on the market. Some of them are standardized some of them are proprietary, and of course, some of them are trying to be a standard. From the standardized solutions, we could select WiFi, BlueTooth, RFID or ZigBee. From proprietary world MiWi, Z-Wave, IQRF and the others. Like always, all of them has some pros and some cons and are better or worse for different applications. In the rest of the article, we will stay with IQRF [4]. The article is organized as follows. The second section contains general information about IQRF wireless communication platform, followed by brief description of development tools and gateways to higher systems.
  • Wireless Sensor Network Implementation Using MIWI Wireless Protocol Stack Suman Chhajed Md.Sabir .M.Tech

    Wireless Sensor Network Implementation Using MIWI Wireless Protocol Stack Suman Chhajed Md.Sabir .M.Tech

    Volume 4, No. 11, Nov-Dec 2013 ISSN No. 0976-5697 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info Wireless Sensor Network Implementation using MIWI Wireless Protocol Stack Suman Chhajed Md.Sabir .M.Tech. Student, Department of ECE, GITS-Udaipur Asst. Prof., Department o fECE, GITS-Udaipur [email protected] [email protected] Abstract: This Paper is to design full functional nodes and to deploy wireless sensor network for Industrial parameter monitoring. Sensor nodes acquire the physical variable from field and wirelessly transmit to central master node for acquisition, monitoring, analysis and storage. The resulting designed product could form a reliable support for transferring data between nodes and a computer. A most important stage of this thesis work is to develop sensor nodes for collecting sensor data and acquires data on master node which has MIWI wireless protocol stack. I. INTRODUCTION Wireless Sensor Network (WSN) is a promising data mining solution of industrial wireless data network. Instrumented with wireless sensors, it will become available to monitor the plants in real time, such as air temperature, soil water content, and nutrition stress. The real time information of the fields will provide a solid base to adjust strategies at any time. WSN will revolutionize the data collection in industrial research. However, there have been few researches on the applications of WSN for industrial wireless network. This work was focused on the investigation of wireless sensor networks in industrial Figure.1. Wireless Sensor Network Model applications. The datasets were obtained from experiments. A.
  • Implementing IBM Flashsystem 900 Model AE3

    Implementing IBM Flashsystem 900 Model AE3

    Front cover Implementing IBM FlashSystem 900 Model AE3 Detlef Helmbrecht Jim Cioffi Jon Herd Jeffrey Irving Christian Karpp Volker Kiemes Carsten Larsen Adrian Orben Redbooks International Technical Support Organization Implementing IBM FlashSystem 900 Model AE3 March 2018 SG24-8414-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (March 2018) This edition applies to the IBM FlashSystem 900 Model AE3. © Copyright International Business Machines Corporation 2018. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x Preface . xi Authors. xi Now you can become a published author, too! . xiv Comments welcome. xiv Stay connected to IBM Redbooks . xiv Chapter 1. Introduction to FlashSystem . 1 1.1 FlashSystem storage overview . 3 1.2 IBM FlashCore technology . 4 1.2.1 IBM Piece of Mind Initiative. 5 1.3 Why flash technology matters . 6 1.4 IBM FlashSystem family product differentiation . 7 1.5 Technology and architectural design overview . 8 1.5.1 Hardware-only data path. 9 1.5.2 3DTLC flash memory chips. 10 1.5.3 Flash module capacities . 10 1.5.4 Gateway interface FPGA . 11 1.5.5 Flash controller FPGA. 11 1.5.6 IBM Variable Stripe RAID and 2D Flash RAID overview . 12 1.5.7 Inline hardware data compression . 14 1.5.8 Encryption . 14 1.6 Usability plus reliability, availability, and serviceability enhancements . 16 1.6.1 Automatic battery reconditioning. 16 1.6.2 Remote Support Assistance .