DOCSLIB.ORG

Embedded Software Design for a Microcontroller-Based Data Logger for Stepper Motor Fault Diagnosis

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Embedded Software Design for a Microcontroller-Based Data Logger for Stepper Motor Fault Diagnosis EMBEDDED SOFTWARE DESIGN FOR A MICROCONTROLLER-BASED DATA LOGGER FOR STEPPER MOTOR FAULT DIAGNOSIS A Thesis Presented by Michael Thomas Daniel to The Department of Electrical and Computer Engineering in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering in the field of Power Systems Northeastern University Boston, Massachusetts April 2012 ABSTRACT Two independent pieces of embedded software have been developed to operate a data log- ging system based on a PIC18F8722 microcontroller for a stepper motor diagnosis appli- cation. The first piece of embedded software is implemented with several state machines in a foreground/background (superloop) structure, while the second is implemented as an RTOS-enabled software based on the Salvo Lite cooperative real time operating system. The superloop implementation results in data for up to 8 stepper motor channels being logged to an SD card and RS-232 link at a rate of 10 Hz, with approximately 50% processor over- head time reserved for RS-232 communications. The RTOS-enabled implementation results in an improved high priority interrupt service routine execution time, but is overall slower to respond to interrupts compared to the superloop implementation due to the cooperative nature of the chosen operating system. A custom binary-to-ASCII conversion software is also developed for converting the resulting data log file produced by both software imple- mentations to human readable text, as the result of both implementations is a binary data log file containing data of interest for up to 8 stepper motors. This page intentionally left blank as a place holder for the Approval Record. c 2012 Michael Thomas Daniel ALL RIGHTS RESERVED Northeastern University, the faculty adviser, and the author assume no legal and/or financial liability for any statement in this thesis. i Dedicated to my parents. ii ACKNOWLEDGEMENTS While there were countless people who helped me with this work, there are a few who deserve special thanks. Without them, the success of this work would not have been possible. First of all, thank you to Michael Taranowski1 for hiring me to work at LLNL and assigning me to the project that would become the inspiration for this work. I would also like to express my gratitude to Mark Miller1 and Danielle Doane1 who both made my work at LLNL possible. Thanks to Matthew Dayton1 and LeRoy Bennett1 for their help and advice on programming for embedded systems with C. I also extend thanks to Jim McBride1, Eric Imhoff1, and Timm Wulff1 for their help and advice on developing hardware test set-ups for embedded systems. Thank you to Professor Ali Abur2 for his continuous guidance throughout the course of this work, and to Professor Gunar Schirner2 for his practical advice on programming for embedded systems. Thanks to Professor Dionisio Bernal2 for his encouragement to take on this work. Thanks are also extended to Professor Sara Wadia-Fascetti2 for hiring me to my position with the IGERT Intelligent Diagnostics group at Northeastern University, which has made this work possible. The ability to test my designs in the ECE laboratories, which was essential to this work, was made possible by Dr. Amir Farhat2, Edward Tyrance2, and Stephen Keane2. This work has been supported by NSF Grant Number DGE - 0654176. 1Lawrence Livermore National Laboratory 2Northeastern University iii Contents 1 Introduction 1 1.1 Thesis Statement and Objectives . .1 1.2 Significance and Importance of Work . .3 1.3 Background Information Leading to Thesis Formulation . .5 1.4 Summary of the Relevant Literature . .6 1.5 Organizational Summary of Thesis . 10 2 Technical Background 12 2.1 Stepper Motors, Drivers, and Faults . 12 2.2 Signals of Interest and System Technical Requirements . 19 2.3 Early Design Decisions: Laying the Foundation . 23 2.3.1 The Microcontroller and Its Interfaces . 23 2.3.2 Development Hardware and Constraints . 32 2.3.3 Development Software and Constraints . 34 3 Application Software - Superloop Version 38 3.1 Structure and Function . 38 3.1.1 The Background Loop . 42 3.1.2 The Foreground Loop . 57 3.1.3 Overall Superloop Version Software Structure . 63 iv 3.2 Data Log Conversion Software . 65 3.3 Testing Methods . 68 3.4 Results and Evaluation . 71 4 Application Software - RTOS Version 89 4.1 RTOS Fundamentals . 89 4.2 Structure and Function . 93 4.2.1 Initialization Tasks . 99 4.2.2 Get Data Log Task . 103 4.2.3 Put Data Log Task . 106 4.2.4 Handle UART Task . 109 4.2.5 Date/Time Task . 112 4.2.6 RTOS Version Software Structure and Function in Steady State . 115 4.3 Testing Methods . 116 4.4 Results and Evaluation . 118 5 Concluding Remarks 137 5.1 Comparison of the Results and Evaluations . 137 5.2 Opportunities for Future Work . 140 5.3 Broader Impacts . 141 A Hardware Schematics 142 B Application Specific Source Code 148 B.1 Application Source Code - Superloop Version . 149 B.1.1 MainSrcCode.c . 149 B.1.2 AuxSrcCode.c . 158 B.1.3 CustomHeader.h . 171 v B.1.4 18f8722_MDDFS.lkr . 172 B.2 Application Source Code - RTOS Version . 174 B.2.1 main.c . 174 B.2.2 auxiliary.c . 187 B.2.3 main.h . 198 B.2.4 salvocfg.h . 199 B.3 Binary to ASCII Converter Source Code . 200 B.3.1 DataLogBin2ASCIIVer4.c . 200 B.4 MATLAB Files . 204 B.4.1 StepCountingApproximation.m . 204 vi List of Figures 2.1 Basic operation of a two phase permanent magnet stepper motor with four poles ..... 14 2.2 Functional block diagram of TI DRV8811 from the DRV8811 data sheet. ......... 15 2.3 Detailed block diagram of TI DRV8811 output stage from the DRV8811 data sheet. .... 16 2.4 Stepper motor using a linear gear and rails for a linear positioning application. ..... 17 2.5 Functional block diagram of the PIC18F8722 device from the PIC18F8722 data sheet .. 25 2.6 Pin diagram of the PIC18F8722 device from the PIC18F7822 data sheet ........ 26 2.7 Physical interfaces between NIF motor drive board, data logger, SD card, and PC. .... 27 2.8 Pin arrangements for both SD card and RS-232 physical interfaces ........... 28 2.9 Operation of the SPI bus using shift registers. ..................... 29 2.10 Microcontroller internal hardware configuration for this application. ........... 29 2.11 Ideal function of each MCU pin given the data logging application at hand. ....... 31 2.12 Hardware development tools used in this application. Top left is PICkit3 debugger, top right is SD card, bottom left is PICDEM PIC18 board, and bottom right is PICtail Daughter Board for MMC/SD Cards. .............................. 32 2.13 Function of each MCU pin given the data logging application at hand combined with devel- opment tool constraints. ............................... 37 3.1 Visual representations of the superloop program structure used by the embedded application software. ....................................... 39 3.2 Project structure in MPLAB IDE for implementing superloop embedded application software. 40 vii 3.3 State machine used in main() to implement initialization and background loop. ..... 43 3.4 Flow chart showing the possible paths of background loop execution; line numbers refer to MainSrcCode.c which is found in Appendix B.1.1. ................... 44 3.5 Circular buffer represented both as a ring as well as linearly; the circular buffer is first-in first-out or “FIFO”. ................................. 47 3.6 Linear representations of some key circular buffer conditions for this application. .... 48 3.7 Data log structure; note that one “datalog” structure includes an array of eight “channel” structures, which in turn each include a “bitfield” structure. .............. 49 3.8 Structure of the binary data log file. .......................... 51 3.9 Flow chart describing the handling of RS-232 commands received via UART. ...... 56 3.10 State machine used to implement foreground loop in HPISR; note that control is returned to the background upon completion of each state. .................... 58 3.11 Diagram showing the order and manner in which commanded motor steps are counted by the MCU ...................................... 59 3.12 Theoretical motor velocity and position given 200 steps per second squared acceleration for 50 seconds. The MATLAB script used to generate this figure can be found in Appendix B.4.1. 59 3.13 Detail of Figure 3.12 showing motor position from t=49.9s to t=50.0s. ......... 60 3.14 Flow chart describing the execution of foreground state three. .............. 61 3.15 High level overall description of superloop application software structure and function .. 64 3.16 Flow chart describing the execution of the data log binary to ASCII conversion application. 66 3.17 Lab bench set up for testing embedded application software. Note the DC supply limited to 25mA for analog inputs, and signal generator for step inputs. The development tools are on the bench in front of the oscilloscope; the PC to the right is used to control software execution on the PIC18F8722 via the PICkit3 debugger interface and MPLAB IDE. ... 69 3.18 Binary data log file when interpretted directly as ASCII characters by Notepad. ..... 72 viii 3.19 Win32 console displayed by binary-to-ASCII conversion program during execution. Note that the program waits for the user to acknowledge conversion complete before exiting. .. 72 3.20 Final data log correctly converted to ASCII text. .................... 73 3.21 Channels 5 throught 8 of the final text data log file. ................... 74 3.22 Beginning of hyperterminal output for superloop test case. ............... 76 3.23 HyperTerminal output when data logging operations are stopped with both outputs enabled. Terminal output is disabled before data logging is restarted. ............... 78 3.24 HyperTerminal output when data logging is stopped with only SD card output enabled.
Load more

Recommended publications
  • AMD Athlon™ Processor X86 Code Optimization Guide
    AMD AthlonTM Processor x86 Code Optimization Guide © 2000 Advanced Micro Devices, Inc. All rights reserved. The contents of this document are provided in connection with Advanced Micro Devices, Inc. (“AMD”) products. AMD makes no representations or warranties with respect to the accuracy or completeness of the contents of this publication and reserves the right to make changes to specifications and product descriptions at any time without notice. No license, whether express, implied, arising by estoppel or otherwise, to any intellectual property rights is granted by this publication. Except as set forth in AMD’s Standard Terms and Conditions of Sale, AMD assumes no liability whatsoever, and disclaims any express or implied warranty, relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particular purpose, or infringement of any intellectual property right. AMD’s products are not designed, intended, authorized or warranted for use as components in systems intended for surgical implant into the body, or in other applications intended to support or sustain life, or in any other applica- tion in which the failure of AMD’s product could create a situation where per- sonal injury, death, or severe property or environmental damage may occur. AMD reserves the right to discontinue or make changes to its products at any time without notice. Trademarks AMD, the AMD logo, AMD Athlon, K6, 3DNow!, and combinations thereof, AMD-751, K86, and Super7 are trademarks, and AMD-K6 is a registered trademark of Advanced Micro Devices, Inc. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.
    [Show full text]
  • A PROGRAMMABLE COMPUTER INTERFACE for CAMAC F by Robert W
    NASA TECHNICAL NOTE NASA TN D-7148 A PROGRAMMABLE COMPUTER INTERFACE FOR CAMAC f by Robert W. Bercaw, Theodore E. Fessler, \ and Jeffrey M. Arnold Lewis Research Center Cleveland, Ohio 44135 NATIONAL AERONAUTICS AND SPACE ADMINISTRATION • WASHINGTON, D. C. • MARCH 1973 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. NASA TN D-7148 4. Title and Subtitle 5. Report Date March 1973 A PROGRAMMABLE COMPUTER INTERFACE FOR CAMAC 6. Performing Organization Code 7. Author(s) 8. Performing Organization Report No. Robert W. Bercaw, Theodore E. Fessler, and Jeffrey M. Arnold E-6957 10. Work Unit No. 9. Performing Organization Name and Address 503-10 Lewis Research Center 11. Contract or Grant No. National Aeronautics and Space Administration Cleveland, Ohio 44135 13. Type of Report and Period Covered 12. Sponsoring Agency Name and Address Technical Note National Aeronautics and Space Administration 14. Sponsoring Agency Code Washington, B.C. 20546 15. Supplementary Notes 16. Abstract An interface has been developed for CAMAC instrumentation systems that implements data transfers controlled either by the computer CPU or by an autonomous (data-channel) processor in the interface unit. The data channel processor executes programs stored in the computer memory. These programs consist of standard CAMAC module commands plus special control characters and commands for the processor itself. The interface was built for the PDP-15 computer, which has an 18-bit word structure, but both 18- and 24-bit data transfers can be made. A software system has been written that exploits the many features of the processor. 17. Key Words (Suggested by Author(s)) 18.
    [Show full text]
  • Application Note Saving Data During a Power Failure Using the Dataflash® E-Series Family
    Saving Data During a Power Failure Using the DataFlash® E-Series Family Application Note Saving Data During a Power Failure Using the DataFlash® E-Series Family Abstract This application note is intended to provide readers with information on how to save critical data to the Flash memory of DataFlash E-Series devices in the event of a power failure. The power failure is simulated by removing power to the devices. This document does not discuss how the power failure is detected, how the microcontroller may respond to the failure, or how the power rail is controlled for both the DataFlash device and the microcontroller. Product Highlights • Single 3V Read/Write Operation (1.65V - 3.6V Supply Range) • SPI Mode 0 and Mode 3 Compatible • Fast Read Access Times: 85 MHz Maximum Clock Frequency • Individual Hardware and Software Sector Protection • Security: 128-byte Register • JEDEC Standard Manufacturer and Device ID Read • Endurance: 100,000 Program/Erase Cycles per Page Minimum • Data Retention: 20 Years • Packaging Options: SOIC, DFN, WLCSP, Die/Wafer • Green (Pb/Halide-free) Packaging Options Application Note 114 11-Dec-2020 AN114 1 of 13 © 2020 Dialog Semiconductor Saving Data During a Power Failure Using the DataFlash® E-Series Family Revision History Revision Date Description A0 11-Dec-2020 Initial Release Application Note 114 11-Dec-2020 AN114 2 of 13 © 2020 Dialog Semiconductor Saving Data During a Power Failure Using the DataFlash® E-Series Family 1 Introduction The DataFlash E-series family of Flash memory devices are often used in applications such as server configuration, data logging, event counters and failure/error/status loggers.
    [Show full text]
  • 14-/12-Bit, 250MSPS, Ultralow-Power ADC with Analog Buffers Check for Samples: ADS41B29, ADS41B49
    ADS41B29 ADS41B49 www.ti.com SBAS486E – NOVEMBER 2009–REVISED JULY 2012 14-/12-Bit, 250MSPS, Ultralow-Power ADC with Analog Buffers Check for Samples: ADS41B29, ADS41B49 1FEATURES DESCRIPTION The ADS41B29/B49 are members of the ultralow- 23• ADS41B49: 14-Bit, 250MSPS ADS41B29: 12-Bit, 250MSPS power ADS4xxx analog-to-digital converter (ADC) family, featuring integrated analog input buffers. • Integrated High-Impedance These devices use innovative design techniques to Analog Input Buffer: achieve high dynamic performance, while consuming – Input Capacitance: 2pF extremely low power. The analog input pins have – 200MHz Input Resistance: 3kΩ buffers, with benefits of constant performance and input impedance across a wide frequency range. The • Maximum Sample Rate: 250MSPS devices are well-suited for multi-carrier, wide • Ultralow Power: bandwidth communications applications such as PA – 1.8V Analog Power: 180mW linearization. – 3.3V Buffer Power: 96mW The ADS41B49/29 have features such as digital gain – I/O Power: 135mW (DDR LVDS) and offset correction. The gain option can be used to improve SFDR performance at lower full-scale input • High Dynamic Performance: ranges, especially at high input frequencies. The – SNR: 69dBFS at 170MHz integrated dc offset correction loop can be used to – SFDR: 82.5dBc at 170MHz estimate and cancel the ADC offset. At lower sampling rates, the ADC automatically operates at • Output Interface: scaled-down power with no loss in performance. – Double Data Rate (DDR) LVDS with Programmable Swing and Strength: The devices support both double data rate (DDR) low-voltage differential signaling (LVDS) and parallel – Standard Swing: 350mV CMOS digital output interfaces. The low data rate of – Low Swing: 200mV the DDR LVDS interface (maximum 500MBPS) – Default Strength: 100Ω Termination makes it possible to use low-cost field-programmable gate array (FPGA)-based receivers.
    [Show full text]
  • Real-Time Operating System (RTOS)
    Real-Time Operating System ELC 4438 – Spring 2016 Liang Dong Baylor University RTOS – Basic Kernel Services Task Management • Scheduling is the method by which threads, processes or data flows are given access to system resources (e.g. processor time, communication bandwidth). • The need for a scheduling algorithm arises from the requirement for most modern systems to perform multitasking (executing more than one process at a time) and multiplexing (transmit multiple data streams simultaneously across a single physical channel). Task Management • Polled loops; Synchronized polled loops • Cyclic Executives (round-robin) • State-driven and co-routines • Interrupt-driven systems – Interrupt service routines – Context switching void main(void) { init(); Interrupt-driven while(true); } Systems void int1(void) { save(context); task1(); restore(context); } void int2(void) { save(context); task2(); restore(context); } Task scheduling • Most RTOSs do their scheduling of tasks using a scheme called "priority-based preemptive scheduling." • Each task in a software application must be assigned a priority, with higher priority values representing the need for quicker responsiveness. • Very quick responsiveness is made possible by the "preemptive" nature of the task scheduling. "Preemptive" means that the scheduler is allowed to stop any task at any point in its execution, if it determines that another task needs to run immediately. Hybrid Systems • A hybrid system is a combination of round- robin and preemptive-priority systems. – Tasks of higher priority can preempt those of lower priority. – If two or more tasks of the same priority are ready to run simultaneously, they run in round-robin fashion. Thread Scheduling ThreadPriority.Highest ThreadPriority.AboveNormal A B ThreadPriority.Normal C ThreadPriority.BelowNormal D E F ThreadPriority.Lowest Default priority is Normal.
    [Show full text]
  • Parallelization Hardware Architecture Type to Enter Text
    Parallelization Hardware architecture Type to enter text Delft University of Technology Challenge the future Contents • Introduction • Classification of systems • Topology • Clusters and Grid • Fun Hardware 2 hybrid parallel vector superscalar scalar 3 Why Parallel Computing Primary reasons: • Save time • Solve larger problems • Provide concurrency (do multiple things at the same time) Classification of HPC hardware • Architecture • Memory organization 5 1st Classification: Architecture • There are several different methods used to classify computers • No single taxonomy fits all designs • Flynn's taxonomy uses the relationship of program instructions to program data • SISD - Single Instruction, Single Data Stream • SIMD - Single Instruction, Multiple Data Stream • MISD - Multiple Instruction, Single Data Stream • MIMD - Multiple Instruction, Multiple Data Stream 6 Flynn’s Taxonomy • SISD: single instruction and single data stream: uniprocessor • SIMD: vector architectures: lower flexibility • MISD: no commercial multiprocessor: imagine data going through a pipeline of execution engines • MIMD: most multiprocessors today: easy to construct with off-the-shelf computers, most flexibility 7 SISD • One instruction stream • One data stream • One instruction issued on each clock cycle • One instruction executed on single element(s) of data (scalar) at a time • Traditional ‘von Neumann’ architecture (remember from introduction) 8 SIMD • Also von Neumann architectures but more powerful instructions • Each instruction may operate on more than one data element • Usually intermediate host executes program logic and broadcasts instructions to other processors • Synchronous (lockstep) • Rating how fast these machines can issue instructions is not a good measure of their performance • Two major types: • Vector SIMD • Parallel SIMD 9 Vector SIMD • Single instruction results in multiple operands being updated • Scalar processing operates on single data elements.
    [Show full text]
  • The 8255A Is Generally Seen As 8-Bit Bidirectional Data Buffer, Which Is
    PROGRAMMABLE PERIPHERAL INTERFACE 8255 The 8255A is generally seen as 8-bit bidirectional data buffer, which is specially designed to transfer the data with the execution of input output instructions requested by the CPU. It has the ability to use with almost any microprocessor. It consists of three 8-bit bidirectional I/O ports (24I/O lines) which can be configured with their different functional characteristics, each possessing unique features to upgrade the flexibility of 8255. Ports of 8255A 8255A consists of three ports, i.e., PORT A, PORT B, and PORT C. Port A contains one 8-bit output latch/buffer and one 8-bit input buffer possessing both pull- up and pull-down devices present in Port A. Port B is similar to PORT A. Port C can be split into two parts, i.e. PORT C lower (PC0-PC3) and PORT C upper (PC7- PC4) with the help of control word. These three ports are further classified into two groups, i.e. Group A includes PORT A and upper PORT C. Group B includes PORT B and lower PORT C. These two groups can be programmed in three different modes, i.e. the first mode is named as mode 0, the second mode is named as Mode 1 and the third mode is named as Mode 2. Data Bus Buffer : It is a tri-state 8-bit bidirectional data buffer, which helps in interfacing the microprocessor to the system data bus. Data is transmitted or received by the buffer with the input output instructions given by the CPU.
    [Show full text]
  • COS 318: Operating Systems I/O Device Interactions and Drivers
    Topics COS 318: Operating Systems u So far: l Management of CPU and concurrency l Management of main memory and virtual memory I/O Device Interactions and u Next: Management of the I/O system Drivers l Interacting with I/O devices l Device drivers Jaswinder Pal Singh l Storage Devices Computer Science Department Princeton University u Then, File Systems l File System Structure (http://www.cs.princeton.edu/courses/cos318/) l Naming and Directories l Efficiency/Performance l Reliability and Protection 2 Input and Output Revisit Hardware u A computer u Compute hardware CPU l CPU cores and caches CPU l Computation (CPU, memory hierarchy) CPUCPU CPU l Memory $ l Move data into and out of a system (locketween I/O devices Chip l I/O and memory hierarchy) l Controllers and logic Memory I/O bridge u Challenges with I/O devices I/O bus l Different categories with different characteristics: storage, u I/O Hardware networking, displays, keyboard, mouse ... l I/O bus or interconnect l Large number of device drivers to support l I/O device l I/O controller or adapter l Device drivers run in kernel mode and can crash systems • Often on parent board Network u Goals of the OS • Cable connects it to device • Often using standard interfaces: IDE, l Provide a generic, consistent, convenient and reliable way to SATA, SCSI, USB, FireWire… access I/O devices • Has registers for control, data signals • Processor gives commands and/or l Achieve potential I/O performance in a system data to controller to do I/O • Special I/O instructions (w.
    [Show full text]
  • Ans: the Buffer Register Prevents the High Speed Processor from Being
    1. a) What is use of buffers? Ans: The Buffer Register prevents the high speed processor from being locked to a slow I/O device during a sequence of data transfer or reduces speed mismatch between faster and slower devices. b) Write basic performance equation. Ans: T=(N*S)/R Where, TPerformance Parameter RClock Rate in cycles/sec NActual number of instruction execution SAverage number of basic steps needed to execute one machine instruction. c) What is an interrupt? Ans: An interrupt is a signal to processor generated by hardware or software indicating an event that needs immediate attention. d) How control memory works? Ans: Control Memory is the storage in the microprogrammed control unit to store the microprogram(sequence of micro instructions). e) What is role of micro programmed control? Ans: A microprogrammed control unit is a relatively simple logic circuit that is capable of sequencing through microinstructions and (2) generating control signals to execute each microinstruction. f) Explain indirect register addressing modes. Ans: Register indirect addressing means that the location of an operand is held in a register. It is also called indexed addressing or base addressing. g) State the meaning of locality of reference. Ans: Many instructions in localized areas of the program are executed repeatedly during some time period. This behaviour manifests itself in two ways: temporal and spatial. h) Define virtual memory. Ans: virtual memory is a memory management technique creates the illusion to users of a very large main memory. Also a Technique that automatically move program and data blocks into the physical main memory when they are required for execution is called the Virtual Memory.
    [Show full text]
  • 8-Bit Microcontroller with 12 Kbyte Flash AT89S8253
    Features • Compatible with MCS®51 Products • 12K Bytes of In-System Programmable (ISP) Flash Program Memory – SPI Serial Interface for Program Downloading – Endurance: 10,000 Write/Erase Cycles • 2K Bytes EEPROM Data Memory – Endurance: 100,000 Write/Erase Cycles • 64-byte User Signature Array • 2.7V to 5.5V Operating Range • Fully Static Operation: 0 Hz to 24 MHz (in x1 and x2 Modes) 8-bit • Three-level Program Memory Lock • 256 x 8-bit Internal RAM Microcontroller • 32 Programmable I/O Lines • Three 16-bit Timer/Counters with 12 Kbyte • Nine Interrupt Sources Flash • Enhanced UART Serial Port with Framing Error Detection and Automatic Address Recognition • Enhanced SPI (Double Write/Read Buffered) Serial Interface • Low-power Idle and Power-down Modes AT89S8253 • Interrupt Recovery from Power-down Mode • Programmable Watchdog Timer • Dual Data Pointer • Power-off Flag • Flexible ISP Programming (Byte and Page Modes) – Page Mode: 64 Bytes/Page for Code Memory, 32 Bytes/Page for Data Memory • Four-level Enhanced Interrupt Controller • Programmable and Fuseable x2 Clock Option • Internal Power-on Reset • 42-pin PDIP Package Option for Reduced EMC Emission • Green (Pb/Halide-free) Packaging Option 1. Description The AT89S8253 is a low-power, high-performance CMOS 8-bit microcontroller with 12K bytes of In-System Programmable (ISP) Flash program memory and 2K bytes of EEPROM data memory. The device is manufactured using Atmel’s high-density non- volatile memory technology and is compatible with the industry-standard MCS-51 instruction set and pinout. The on-chip downloadable Flash allows the program mem- ory to be reprogrammed in-system through an SPI serial interface or by a conventional nonvolatile memory programmer.
    [Show full text]
  • D: Serial Driver
    CHAPTER 7 Serial Driver 7 This chapter describes how you can use the Serial Driver to transfer data to a device connected to a Macintosh modem or printer port. The Serial Driver supports 7 asynchronous serial data communication between applications and serial devices Serial Driver through these ports. The Serial Driver provides low-level support for communicating with serial devices that cannot be accessed through the Communications Toolbox or Printing Manager. For example, a scientific instrument or a printer that does not support QuickDraw. Before you decide to use the Serial Driver, you should determine whether it is the appropriate solution for your communication needs. The Communications Toolbox is the recommended method for integrating modems and other telecommunications devices into the Macintosh environment. The Communications Toolbox provides hardware-independent services and a standard interface that offers compatibility with all Macintosh models. To find out more about the Communications Toolbox, see Inside the Macintosh Communications Toolbox. Likewise, the Printing Manager is the recommended interface for printers and similar output devices. Using the Printing Manager makes your hardware or software product compatible with every other device or application that supports this standard interface. Refer to Inside Macintosh: Imaging With QuickDraw for more information. To use the Serial Driver, you should understand how to open, close, and communicate with device drivers using the Device Manager. You can find this information in
    [Show full text]
  • A New Approach to Making I2C Bus Buffers
    A New Approach to Making I2C Bus Buffers SCOPE: The information in this paper helps electronic engineers and engineering managers stay informed of developments with the I2C (Inter-Integrated-Circuit) bus system. All existing I2C bus buffers use the signal amplitude to set the signal flow direction, and use voltage offset techniques to avoid bus buffer latching. The no-offset buffer is different and unique in that it uses the signal timing as the direction flow control, thus eliminating many prior design headaches. The I2C Bus – From Humble Beginnings The I2C Bus – From Humble Beginnings to to New Uses 1 I2C Signal Flows 2 New Uses I2C-bus Buffer Basics 2 The simplicity and low cost of the I2C bus has enticed electronic engineers Making I2C-bus Buffers that Work 2 to find more uses for the two-wire Inter-Integrated-Circuit protocol, and its Innovation in I2C-bus Buffer many derivatives. Techniques — The No-offset Type 3 Key Features of No-offset Bus Buffers 3 While the technology has been around for decades, and is still a viable Introducing the Industry’s First solution for many maintenance and control applications, additional No-offset Bus Buffers 5 components have been invented to make it better and more useful. In Summary 8 particular, to overcome some of the basic limitations due to adding more devices to the bus or extending the bus length beyond its original maximum of just a few meters. The most popular addition to the family has been the bus buffer, which relays the signals, but there have also been a variety of other devices invented that can switch the I2C-bus to different branches and greatly enhance its usefulness.
    [Show full text]