Leica Flexline TS02/TS06/TS09 User Manual

Total Page:16

File Type:pdf, Size:1020Kb

Leica Flexline TS02/TS06/TS09 User Manual Leica FlexLine TS02/TS06/TS09 User Manual Version 1.0 English Introduction FlexLine, 2 Introduction Purchase Congratulations on the purchase of a FlexLine instrument. This manual contains important safety directions as well as instructions for setting up and operating the product. Refer to "13 Safety Directions" for further information. Read carefully through the User Manual before you switch on the product. Product The model and serial number of your product are indicated on the type plate. identification Enter the model and serial number in your manual and always refer to this information when you need to contact your agency or Leica Geosystems authorised service workshop. Model: _________________________________________________________ Serial No.: _________________________________________________________ Symbols The symbols used in this manual have the following meanings: Type Description ƽ Danger Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. ƽ Warning Indicates a potentially hazardous situation or an unintended use which, if not avoided, could result in death or serious injury. ƽ Caution Indicates a potentially hazardous situation or an unintended use which, if not avoided, may result in minor or moderate injury and/or appreciable material, financial and environmental damage. Important paragraphs which must be adhered to in practice as ) they enable the product to be used in a technically correct and efficient manner. Trademarks • Windows is a registered trademark of Microsoft Corporation. • Bluetooth is a registered trademark of Bluetooth SIG, Inc. All other trademarks are the property of their respective owners. Introduction FlexLine, 3 Introduction FlexLine, 4 Validity of this Description manual General This manual applies to TS02, TS06, and TS09 instruments. Where there are differences between the various instruments they are clearly described. The following symbols will identify in each section where the instruments differ: • for TS02. • for TS06. • for TS09. Telescope • Measuring with Prism mode: When measuring distances to a reflector with Electronic Distance Measurement (EDM) mode "Prism", the telescope uses a wide visible red laser beam, which emerges coaxially from the telescope's objective. • Measuring with Non-Prism modes: Instruments that are equipped with a reflectorless EDM additionally offer the EDM mode "Non-Prism". When meauring distances with this EDM mode, the telescope uses a narrow visible red laser beam, which emerges coaxially from the telescope's objective. Table of Contents In this manual Chapter Page 1 Description of the System 12 1.1 System Components 12 1.2 Container Contents 14 1.3 Instrument Components 16 2 User Interface 19 2.1 Keyboard 19 2.2 Screen 21 2.3 Status Icons 22 2.4 Softkeys 24 2.5 Operating Principles 25 2.6 Pointsearch 27 3 Operation 29 3.1 Instrument Setup 29 3.2 Working with the Battery 35 3.3 Data Storage 37 3.4 Main Menu 37 3.5 Q-Survey Application 39 3.6 Distance Measurements - Guidelines for Correct Results 40 Table of Contents FlexLine, 5 Table of Contents FlexLine, 6 4 Setting 42 4.1 General Settings 42 4.2 EDM Settings 54 4.3 Communication Parameters 60 5 Tools 63 5.1 Adjust 63 5.2 Start Up Sequence 64 5.3 System Information 65 5.4 Licence Keys 67 5.5 Instrument Protection with PIN 68 5.6 Loading Software 70 6Functions 72 6.1 Overview 72 6.2 Target Offset 74 6.2.1 Overview 74 6.2.2 Cylinder Offset Subapplication 76 6.3 Height Transfer 80 6.4 Hidden Point 81 6.5 Check Tie 84 6.6 EDM Tracking 86 7Coding 87 7.1 Standard Coding 87 7.2 Quick Coding 89 8 Applications - Getting Started 91 8.1 Overview 91 8.2 Starting an Application 92 8.3 Setting the Job 94 8.4 Setting the Station 95 8.5 Setting the Orientation 97 8.5.1 Overview 97 8.5.2 Manual Orientation 98 8.5.3 Orientation with Coordinates 99 9 Applications 103 9.1 Common Fields 103 9.2 Surveying 104 9.3 Stakeout 105 9.4 Free Station 111 9.4.1 Starting Free Station 111 9.4.2 Measuring Information 113 9.4.3 Computation Procedure 114 9.4.4 Free Station Results 115 9.5 Reference Element - Reference Line 118 9.5.1 Overview 118 9.5.2 Defining the Base Line 119 9.5.3 Defining the Reference Line 120 9.5.4 Subapplication Measure Line & Offset 123 Table of Contents FlexLine, 7 Table of Contents FlexLine, 8 9.5.5 Subapplication Stakeout 125 9.5.6 Subapplication Grid Stakeout 127 9.5.7 Subapplication Line Segmentation 131 9.6 Reference Element - Reference Arc 136 9.6.1 Overview 136 9.6.2 Defining the Reference Arc 137 9.6.3 Subapplication Measure Line & Offset 139 9.6.4 Subapplication Stakeout 141 9.7 Tie Distance 146 9.8 Area & Volume 149 9.9 Remote Height 153 9.10 Construction 154 9.10.1 Starting Construction 154 9.10.2 Layout 155 9.10.3 As Built Check 157 9.11 COGO 159 9.11.1 Starting COGO 159 9.11.2 Inverse and Traverse 159 9.11.3 Intersections 161 9.11.4 Offsets 163 9.11.5 Extension 165 9.12 Road 2D 166 9.13 Roadworks 3D 171 9.13.1 Starting Roadworks 3D 171 9.13.2 Basic Terms 173 9.13.3 Creating or Uploading Alignment Files 181 9.13.4 Subapplication Stake 184 9.13.5 Subapplication Check 187 9.13.6 Subapplication Stake Slope 189 9.13.7 Subapplication Check Slope 195 9.14 TraversePRO 197 9.14.1 Overview 197 9.14.2 Starting and Configuring TraversePRO 199 9.14.3 Measuring Traverse 202 9.14.4 Moving ahead 205 9.14.5 Closing a Traverse 208 9.15 Reference Plane 214 10 Data Management 218 10.1 File Management 218 10.2 Exporting Data 220 10.3 Importing Data 224 10.4 Working with a USB Memory Stick 226 10.5 Working with Bluetooth 228 10.6 Working with Leica FlexOffice 230 11 Check & Adjust 231 11.1 Overview 231 11.2 Preparation 232 11.3 Adjusting Line-of-Sight and Vertical Index Error 233 11.4 Adjusting the Tilting Axis Error 237 Table of Contents FlexLine, 9 Table of Contents FlexLine, 10 11.5 Adjusting the Circular Level of the Instrument and Tribrach 240 11.6 Inspecting the Laser Plummet of the Instrument 241 11.7 Servicing the Tripod 243 12 Care and Transport 244 12.1 Transport 244 12.2 Storage 245 12.3 Cleaning and Drying 246 13 Safety Directions 247 13.1 General 247 13.2 Intended Use 247 13.3 Limits of Use 249 13.4 Responsibilities 249 13.5 Hazards of Use 250 13.6 Laser Classification 255 13.6.1 General 255 13.6.2 Distancer, Measurements with Reflectors 256 13.6.3 Distancer, Measurements without Reflectors (Non-Prism mode) 258 13.6.4 Electronic Guide Light EGL 262 13.6.5 Laser Plummet 263 13.7 Electromagnetic Compatibility EMC 266 13.8 FCC Statement, Applicable in U.S. 268 14 Technical Data 271 14.1 Angle Measurement 271 14.2 Distance Measurement with Reflectors 272 14.3 Distance Measurement without Reflectors (Non-Prism mode) 274 14.4 Distance Measurement Reflector (>3.5 km) 276 14.5 Conformity to National Regulations 277 14.5.1 Products without Communication side cover 277 14.5.2 Products with Communication side cover 278 14.6 General Technical Data of the Instrument 279 14.7 Scale Correction 285 14.8 Reduction Formulas 288 15 International Limited Warranty, Software License Agreement 290 16 Glossary 292 Appendix A Menu Tree 296 Appendix B Directory Structure 299 Index 300 Table of Contents FlexLine, 11 Description of the System FlexLine, 12 1 Description of the System 1.1 System Components Main Components Flex c Office a) FlexLine instrument with FlexField firmware b) Computer with FlexOffice software TSOX_001 a b c) Data transfer Component Description FlexLine An instrument for measuring, calculating and capturing data. Ideally instrument suited for tasks from simple surveys to complex applications. Equipped with a FlexField firmware package to complete these tasks. The various lines have a range of accuracy classes and support different features. All lines can be connected with FlexOffice to view, exchange and manage data. FlexField The firmware package installed on the instrument. Consists of a firmware standard base operating system with optional additional features. Component Description FlexOffice An office software consisting of a suite of standard and extended software programs for the viewing, exchanging, managing and post processing of data. Data transfer Data can be always transferred between a FlexLine instrument and a computer via a data transfer cable. For instruments equipped with a Communication side cover data can also be transferred via USB memory stick, USB cable, or Bluetooth. Description of the System FlexLine, 13 Description of the System FlexLine, 14 1.2 Container Contents Container contents a b c d e f g h part 1 of 2 a) Instrument with supplied tribrach b) GEV189 data cable (USB-RS232)* c) GLI115 clip-on bubble* d) GHT196 holder for height meter* e) CPR105 flat prism* f) GHM007 height meter* g) Protective cover / Lens hood* h) GEV223 data cable (USB-mini USB) - for instruments with a Communica- tion side cover i) GMP111 mini prism* TS0X_069a i * Optional Container contents jk part 2 of 2 j) Adjustment tools k) GFZ3 diagonal eyepiece* l) GEB211 batteries* m) GKL211 battery charger* n) GAD105 flat or mini prism adapter* o) MS1 Leica industrial grade USB memory stick - for instruments with a Communication side cover p) GEB221 battery* q) Tip for mini prism pole* r) Counterweight for diagonal eyepiece* s) User manual t) GLS115 mini prism pole* l m n op q r s t TS0X_069b * Optional Description of the System FlexLine, 15 Description of the System FlexLine, 16 1.3 Instrument Components Instrument abc dfeg components part 1 of 2 a) Compartment for USB memory stick and USB cable ports* b) Bluetooth antenna* c) Optical sight d) Detachable carrying handle with mounting screw e) Electronic Guide Light (EGL)* f) Objective with integrated Electronic Distance Measurement (EDM).
Recommended publications
  • The Von Neumann Computer Model 5/30/17, 10:03 PM
    The von Neumann Computer Model 5/30/17, 10:03 PM CIS-77 Home http://www.c-jump.com/CIS77/CIS77syllabus.htm The von Neumann Computer Model 1. The von Neumann Computer Model 2. Components of the Von Neumann Model 3. Communication Between Memory and Processing Unit 4. CPU data-path 5. Memory Operations 6. Understanding the MAR and the MDR 7. Understanding the MAR and the MDR, Cont. 8. ALU, the Processing Unit 9. ALU and the Word Length 10. Control Unit 11. Control Unit, Cont. 12. Input/Output 13. Input/Output Ports 14. Input/Output Address Space 15. Console Input/Output in Protected Memory Mode 16. Instruction Processing 17. Instruction Components 18. Why Learn Intel x86 ISA ? 19. Design of the x86 CPU Instruction Set 20. CPU Instruction Set 21. History of IBM PC 22. Early x86 Processor Family 23. 8086 and 8088 CPU 24. 80186 CPU 25. 80286 CPU 26. 80386 CPU 27. 80386 CPU, Cont. 28. 80486 CPU 29. Pentium (Intel 80586) 30. Pentium Pro 31. Pentium II 32. Itanium processor 1. The von Neumann Computer Model Von Neumann computer systems contain three main building blocks: The following block diagram shows major relationship between CPU components: the central processing unit (CPU), memory, and input/output devices (I/O). These three components are connected together using the system bus. The most prominent items within the CPU are the registers: they can be manipulated directly by a computer program. http://www.c-jump.com/CIS77/CPU/VonNeumann/lecture.html Page 1 of 15 IPR2017-01532 FanDuel, et al.
    [Show full text]
  • Demystifying Internet of Things Security Successful Iot Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M
    Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security: Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Chandler, AZ, USA Chandler, AZ, USA Ned Smith David M. Wheeler Beaverton, OR, USA Gilbert, AZ, USA ISBN-13 (pbk): 978-1-4842-2895-1 ISBN-13 (electronic): 978-1-4842-2896-8 https://doi.org/10.1007/978-1-4842-2896-8 Copyright © 2020 by The Editor(s) (if applicable) and The Author(s) This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this book are included in the book’s Creative Commons license, unless indicated otherwise in a credit line to the material.
    [Show full text]
  • Reverse Engineering X86 Processor Microcode
    Reverse Engineering x86 Processor Microcode Philipp Koppe, Benjamin Kollenda, Marc Fyrbiak, Christian Kison, Robert Gawlik, Christof Paar, and Thorsten Holz, Ruhr-University Bochum https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/koppe This paper is included in the Proceedings of the 26th USENIX Security Symposium August 16–18, 2017 • Vancouver, BC, Canada ISBN 978-1-931971-40-9 Open access to the Proceedings of the 26th USENIX Security Symposium is sponsored by USENIX Reverse Engineering x86 Processor Microcode Philipp Koppe, Benjamin Kollenda, Marc Fyrbiak, Christian Kison, Robert Gawlik, Christof Paar, and Thorsten Holz Ruhr-Universitat¨ Bochum Abstract hardware modifications [48]. Dedicated hardware units to counter bugs are imperfect [36, 49] and involve non- Microcode is an abstraction layer on top of the phys- negligible hardware costs [8]. The infamous Pentium fdiv ical components of a CPU and present in most general- bug [62] illustrated a clear economic need for field up- purpose CPUs today. In addition to facilitate complex and dates after deployment in order to turn off defective parts vast instruction sets, it also provides an update mechanism and patch erroneous behavior. Note that the implementa- that allows CPUs to be patched in-place without requiring tion of a modern processor involves millions of lines of any special hardware. While it is well-known that CPUs HDL code [55] and verification of functional correctness are regularly updated with this mechanism, very little is for such processors is still an unsolved problem [4, 29]. known about its inner workings given that microcode and the update mechanism are proprietary and have not been Since the 1970s, x86 processor manufacturers have throughly analyzed yet.
    [Show full text]
  • Control Unit Operation
    PART SIX: THE CONTROL UNIT CHAPTER 19 CONTROL UNIT OPERATION 19.1 MICRO-OPERATIONS ............................................................... 3 The Fetch Cycle ...................................................................... 5 The Indirect Cycle................................................................... 8 The Interrupt Cycle ................................................................. 9 The Execute Cycle................................................................... 9 The Instruction Cycle............................................................. 12 19.2 CONTROL OF THE PROCESSOR ............................................... 13 Functional Requirements........................................................ 13 Control Signals ..................................................................... 16 A Control Signals Example ..................................................... 19 Internal Processor Organization .............................................. 23 The Intel 8085...................................................................... 24 19.3 HARDWIRED IMPLEMENTATION .............................................. 30 Control Unit Inputs ............................................................... 30 Control Unit Logic ................................................................. 33 19.4 RECOMMENDED READING ...................................................... 35 19.5 KEY TERMS, REVIEW QUESTIONS, AND PROBLEMS ................... 35 Key Terms ..........................................................................
    [Show full text]
  • IBM Z Connectivity Handbook
    Front cover IBM Z Connectivity Handbook Octavian Lascu John Troy Anna Shugol Frank Packheiser Kazuhiro Nakajima Paul Schouten Hervey Kamga Jannie Houlbjerg Bo XU Redbooks IBM Redbooks IBM Z Connectivity Handbook August 2020 SG24-5444-20 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Twentyfirst Edition (August 2020) This edition applies to connectivity options available on the IBM z15 (M/T 8561), IBM z15 (M/T 8562), IBM z14 (M/T 3906), IBM z14 Model ZR1 (M/T 3907), IBM z13, and IBM z13s. © Copyright International Business Machines Corporation 2020. 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 . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . xi Comments welcome. xi Stay connected to IBM Redbooks . xi Chapter 1. Introduction. 1 1.1 I/O channel overview. 2 1.1.1 I/O hardware infrastructure . 2 1.1.2 I/O connectivity features . 3 1.2 FICON Express . 4 1.3 zHyperLink Express . 5 1.4 Open Systems Adapter-Express. 6 1.5 HiperSockets. 7 1.6 Parallel Sysplex and coupling links . 8 1.7 Shared Memory Communications. 9 1.8 I/O feature support . 10 1.9 Special-purpose feature support . 12 1.9.1 Crypto Express features . 12 1.9.2 Flash Express feature . 12 1.9.3 zEDC Express feature . 13 Chapter 2. Channel subsystem overview . 15 2.1 CSS description . 16 2.1.1 CSS elements .
    [Show full text]
  • The Microprogrammed Control Unit
    The Microprogrammed Control Unit Up to this point, we have studied: 1. The microoperation sequence associated with each assembly language instruction 2. The control signals associated with those microoperations. 3. The use of combinational logic in the form of a signal generation tree to generate these control signals. We now consider another option for generating the control signals. This is the microprogramming option, in which representations of the control signals are stored in a micro–memory and read into a MBR (micro–memory buffer register) from whence they are issued. Consider the control signal PC B1. When this is asserted, the contents of the Program Counter are copied onto bus B1. The method of generating this signal has no effect on the action it takes. We have two options for generating each control signal: Hardwired: The signal is output from an AND gate Microprogrammed: The signal is output from a D flip–flop. Survey of Bus Usage and Other Control Signals In order to structure the micro–memory properly, we must tabulate the control signals used and arrange them by use: bus transfer, ALU operation, memory operation, etc. Option Bus 1 Bus 2 Bus 3 ALU Other 0 1 PC B1 1 B2 B3 PC tra1 L / R’ 2 MAR B1 – 1 B2 B3 MAR tra2 A 3 R B1 R B2 B3 R shift C 4 IR B1 MBR B2 B3 IR not READ 5 SP B1 IOD B2 B3 SP add WRITE 6 B3 MBR sub extend 7 B3 IOD and 0 RUN 8 B3 IOA or 9 xor Note the important option 0.
    [Show full text]
  • Microprogramming: Basic Idea
    5-45 Chapter 5—Processor Design—Advanced Topics Microprogramming: Basic Idea • Recall control sequence for 1-bus SRC Step Concrete RTN Control Sequence T0 MA ← PC: C ← PC + 4; PCout, MAin, INC4, Cin, Read ← ← T1 MD M[MA]: PC C; Cout, PCin, Wait T2 IR ← MD; MDout, IRin ← T3 A R[rb]; Grb, Rout, Ain ← T4 C A + R[rc]; Grc, Rout, ADD, Cin ← T5 R[ra] C; Cout, Gra, Rin, End • Control unit job is to generate the sequence of control signals • How about building a computer to do this? Computer Systems Design and Architecture by V. Heuring and H. Jordan © 1997 V. Heuring and H. Jordan 5-46 Chapter 5—Processor Design—Advanced Topics The Microcode Engine • A computer to generate control signals is much simpler than an ordinary computer • At the simplest, it just reads the control signals in order from a read-only memory • The memory is called the control store • A control store word, or microinstruction, contains a bit pattern telling which control signals are true in a specific step • The major issue is determining the order in which microinstructions are read Computer Systems Design and Architecture by V. Heuring and H. Jordan © 1997 V. Heuring and H. Jordan 5-47 Chapter 5—Processor Design—Advanced Topics Fig 5.16 Block Diagram of Microcoded Control Unit Ck CCs Other IR Opcode PLA • Microinstruction has Sequencer (computes branch control, 2 start addr) External source n branch address, and control signal fields Increment 4–1 Mux n • Microprogram µPC counter can be set n from several sources to do the required Control sequencing store k n m µBranch µIR control Branch Control signals address PCout, etc.
    [Show full text]
  • CHAPTER 4 MARIE: an Introduction to a Simple Computer
    CHAPTER 4 MARIE: An Introduction to a Simple Computer 4.1 Introduction 219 4.2 CPU Basics and Organization 219 4.2.1 The Registers 220 4.2.2 The ALU 221 4.2.3 The Control Unit 221 4.3 The Bus 221 4.4 Clocks 225 4.5 The Input/Output Subsystem 227 4.6 Memory Organization and Addressing 227 4.7 Interrupts 235 4.8 MARIE 236 4.8.1 The Architecture 236 4.8.2 Registers and Buses 236 4.8.3 Instruction Set Architecture 238 4.8.4 Register Transfer Notation 242 4.9 Instruction Processing 244 4.9.1 The Fetch–Decode–Execute Cycle 244 4.9.2 Interrupts and the Instruction Cycle 246 4.9.3 MARIE’s I/O 249 4.10 A Simple Program 249 4.11 A Discussion on Assemblers 252 4.11.1 What Do Assemblers Do? 252 4.11.2 Why Use Assembly Language? 254 4.12 Extending Our Instruction Set 255 4.13 A Discussion on Decoding: Hardwired Versus Microprogrammed Control 262 4.13.1 Machine Control 262 4.13.2 Hardwired Control 265 4.13.3 Microprogrammed Control 270 4.14 Real-World Examples of Computer Architectures 274 4.14.1 Intel Architectures 275 4.14.2 MIPS Architectures 282 Chapter Summary 284 CMPS375 Class Notes (Chap04) Page 1 / 27 Dr. Kuo-pao Yang 4.1 Introduction 219 • In this chapter, we first look at a very simple computer called MARIE: A Machine Architecture that is Really Intuitive and Easy. • We then provide brief overviews of Intel and MIPS machines, two popular architectures reflecting the CISC (Complex Instruction Set Computer) and RISC (Reduced Instruction Set Computer) design philosophies.
    [Show full text]
  • 5 Computer Organization
    5 Computer Organization Source: Foundations of Computer Science Cengage Learning 5.1 Objectives After studying this chapter, students should be able to: List the three subsystems of a computer. Describe the role of the central processing unit (CPU). Describe the fetch-decode-execute phases of a cycle. Describe the main memory and its addressing space. Define the input/output subsystem. Understand the interconnection of subsystems. Describe different methods of input/output addressing. Distinguish the two major trends in the design of computers. Understand how computer throughput can be improved using pipelining and parallel processing. 5.2 1 A computer can be divided into three broad categories or subsystem: the central processing unit (CPU), the main memory and the input/output subsystem. 5.3 5-1 CENTRAL PROCESSING UNIT The central processing unit (CPU) performs operations on data. In most architectures it has three parts: an arithmetic logic unit (ALU), a control unit and a set of registers, fast storage locations. 5.4 2 The arithmetic logic unit (ALU) The arithmetic logic unit (ALU) performs logic, shift, and arithmetic operations on data. Logic operations: NOT, AND, OR, and XOR. Shift operations: logic shift operations and arithmetic shift operations Arithmetic operations: arithmetic operations on integers and reals. 5.5 Registers Registers are fast stand-alone storage locations that hold data temporarily. Multiple registers are needed to facilitate the operation of the CPU. Data registers Instruction register Program counter The control unit The control unit controls the operation of each subsystem. Controlling is achieved through signals sent from the control unit to other subsystems.
    [Show full text]
  • The Central Processing Unit (CPU)
    The Central Processing Unit (CPU) Crash Course Computer Science #7 The Central Processing Unit https://www.youtube.com/watch?v=FZGugFqdr60 Internals ● Arithmetic Logic Unit (ALU) ● Control Unit (CU) ● Registers ● Cache Memory ● The Fetch-Execute Cycle Arithmetic Logic Unit An arithmetic logic unit (ALU) is a digital circuit used to perform arithmetic and logic ​ operations. It represents the fundamental building block of the central processing unit ​ (CPU) of a computer. Modern CPUs contain very powerful and complex ALUs. In addition to ALUs, modern CPUs contain a control unit (CU). Most of the operations of a CPU are performed by one or more ALUs, which load data from ​ input registers. A register is a small amount of storage available as part of a CPU. The ​ control unit tells the ALU what operation to perform on that data and the ALU stores the result in an output register. The control unit moves the data between these registers, the ALU, and memory. Control Unit A control unit coordinates how data moves around a cpu. The control unit (CU) is a ​ ​ component of a computer's central processing unit (CPU) that directs operation of the processor. It tells the computer's memory, arithmetic/logic unit and input and output devices how to respond to a program's instructions. ● The control unit obtains data / instructions from memory ● Interprets / decodes the instructions into commands / signals ● Controls transfer of instructions and data in the CPU ● Coordinates the parts of the CPU Registers In computer architecture, a processor register is a quickly accessible location available ​ to a digital processor's central processing unit (CPU).
    [Show full text]
  • ARM Processor Architecture Embedded Systems with ARM Cortext-M Updated: Monday, February 5, 2018 a Little About ARM – the Company
    Chapters 1 and 3 ARM Processor Architecture Embedded Systems with ARM Cortext-M Updated: Monday, February 5, 2018 A Little about ARM – The company • Originally Acorn RISC Machine (ARM) • Later Advanced RISC Machine • Then it became ARM Ltd owned by ARM Holdings (parent company) • In 2016 SoftBank bought ARM for $31 billion • ARM: • Develops the architecture and licenses it to other companies • Other companies design their own products that implement one of those architectures— including systems- on-chips (SoC) and systems-on-modules (SoM) that incorporate memory, interfaces, radios, etc. • It also designs cores that implement this instruction set and licenses these designs to a number of companies that incorporate those core designs into their own products. • ARM Processors • RISC based processors • In 2010 alone, 6.1 billion ARM-based processor, representing 95% of smartphones, 35% of digital televisions and set-top boxes and 10% of mobile computers • over 100 billion ARM processors produced as of 2017 • The most widely used instruction set architecture in terms of quantity produced https://en.wikipedia.org/wiki/ARM_architecture M R https://en.wikipedia.org/wiki/ARM_architecture ARM Family and Architecture CPU ARM FAMILY TREE CORTEX- CORTEX- CORTEX- ARM Cortex Processors • ARM Cortex-A family: • Applications processors • Support OS and high- performance applications • Such as Smartphones, Smart TV • ARM Cortex-R family: • Real-time processors with high performance and high reliability • Support real-time processing and mission-critical control • ARM Cortex-M family: • Microcontroller • Cost-sensitive, support SoC 6 CORTEX- • Cortex-M is a great trade-off between performance, cost, efficiency; used for IoT, various applications.
    [Show full text]
  • NX-Series Safety Control Unit Instructions Reference Manual (Z931) 1 CONTENTS
    Machine Automation Controller NX-series Safety Control Unit Instructions Reference Manual NX-SL Z931-E1-05 NOTE 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, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of OMRON. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice. Every precaution has been taken in the preparation of this manual. Neverthe- less, OMRON assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in this publication. Trademarks • Sysmac and SYSMAC are trademarks or registered trademarks of OMRON Corporation in Japan and other countries for OMRON factory automation products. • Microsoft, Windows, Excel, and Visual Basic are either registered trademarks or trademarks of Microsoft Corpora- tion in the United States and other countries. • EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany. • Safety over EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany. • ODVA, CIP, CompoNet, DeviceNet, and EtherNet/IP are trademarks of ODVA. • The SD and SDHC logos are trademarks of SD-3C, LLC. Other company names and product names in this document are the trademarks or registered trademarks of their respective companies. Copyrights Microsoft product screen shots reprinted with permission from Microsoft Corporation. Introduction Introduction Thank you for purchasing Machine Automation Controller NX-series Safety Control Units.
    [Show full text]