DOCSLIB.ORG

DX11-8 System 360/370 Channel to PDP-11 Unibus Interface Maintenance Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DX11-8 System 360/370 Channel to PDP-11 Unibus Interface Maintenance Manual EK-DXIIB-MM-002 DX11-8 system 360/370 channel to PDP-11 unibus interface maintenance manual digital equipment corporation • maynard, massachusetts 1st Edition, August 1972 2nd Printing (Rev) March 1973 3rd Printing July 1973 4th Printing May 1974 5th Printing (Rev) January 1976 Copyright © 1972,1973,1974,1976 by Digital Equipment Corporation The material in this manual is for informational purposes and is subject to change without notice. Digital Equipment Corporation assumes no respon­ sibility for any errors which may appear in this manual. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation, Maynard, Massachusetts: DEC PDP FLIP CHIP FOCAL DIGITAL COMPUTER LAB CONTENTS Page CHAPTER 1 GENERAL DESCRIPTION 1.1 Purpose of Manual 1-1 1.2 System Description 1-2 1.3 Mechanical Description 1-5 1.4 Specifications 1-5 1.4.1 Physical 1-6 1.4.2 Environmental 1-6 1.4:3 Electrical 1-6 1.4.4 Performance 1-6 1.5 Engineering Drawaing Drawings 1-7 CHAPTER 2 INSTALLATION AND ACCEPTANCE TEST 2.1 Summary of Installation Functions 2-1 2.2 Installation and Acceptance Test Requirements 2-2 2.2.1 Equipment Required 2-2 2.2.2 Diagnostics Required 2-2 2.2.3 Space Requirements 2-3 2.2.4 Power Requirements 2-3 2.2.5 Information Requirements 2-5 2.2.6 Test Schedule 2-6 2.3 Unpacking and Inspection 2-6 2.3.1 Unpacking 2-6 2.3.2 Inspection 2-7 2.4 Installation 2-7 2.4.1 PDP-II and DX11-B Cable Installation (within PDP-II System) 2-7 2.4.2 IBM Device Address Jumper Installation 2-8 2.4.3 Interrupt Vector Address Jumper Installation 2-12 2.5 Turning Power On for the First Time 2-12 2.6 PDP-II System Test Without DX11-B 2-13 2.6.1 Control and Indicator Panel Lamp Check 2-13 2.7 DX11-B Test Without IBM 360/370 (OffLine) 2-13 2.7.1 M306 NPR Timeout Mono Calibration Procedure 2-14 2.7.2 BLLM Calibration 2-15 2.7.3 Run the DX11-B Maintenance Clock 2 Test 2-15 (MAINDEC-11-DZDXF-[REV] -PB) 2.7.4 Run the DXII-B Off-Line Exerciser (MAINDEC-11-DZDXG-[REV] -PB) 2-15 2.8 DX11-B CABLE TEST 2-15 2.8.1 On Line B Delay Adjustment 2-18 2.8.2 DXTO Calibration Procedure 2-19 2.8.3 IBM 360/370 Cable Test Using DXII-B to Test Cables Without 2-19 IBM 360/370 System iii CONTENTS (Cont) Page 2.9 Filling Out Test Preparation Card 2-20 2.10 I/O Cable Requirements 2-21 2.11 Connecting DX11-B Cables To IBM Channel 2-21 2.12 EPO Cable Connection 2-24 2.13 EPO Panel Check 2-25 2.14 DX11-B System Test Using IBM 360/370 2-26 2.14.1 Introduction 2-26 2.14.2 Test Preparation 2-26 2.14.3 FRIEND Diagnostic Operating Procedure 2-27 2.14.4 Filling Out Test Preparation Card 2-31 2.14.5 Card Deck Preparation Procedure 2-31 2.14.6 DME/2848 Diagnostic Operation Procedures 2-34 2.14.7 Test Preparation 2-34 2.14.8 DME/2848 Diagnostic Operation Procedure 2-34 2.14.9 FRIEND or DME/2848 Diagnostic Operating Procedure for 3270 Console 2-38 2.15 Operating Suggestions 2-40 2.15.1 On-Line Operation Requirements 2-40 2.15.2 Errors with DME/2848 Diagnostic 2-41 2.15.3 Format Consideration and Logic Levels 2-41 2.16 Errors That Occur When FRIEND is Run 2-41 2.17 Maintenance Procedures 2-42 2.18 Hints on Interface Signal Monitoring While Troubleshooting 2-42 CHAPTER 3 OPERA nON 3.1 Scope 3-1 3.2 Controls and Indicators 3-1 3.3 861 Controls and Indicators 3-9 3.3.1 Pilot Lamps 3-9 3.3.2 Circuit Breaker 3-9 3.3.3 LOCAL/OFF/REMOTE Switch 3-9 3.3.4 Remote Switching Control Bus Connectors 3-9 CHAPTER 4 PROGRAMMING 4.1 Scope 4-1 4.2 IBM 360/370 and PDP-II Format Comparison 4-1 4.3 IBM 360/370/DX11-B Communication 4-2 4.4 DX11-B/PDP-ll Communication 4-2 4.5 DX11-B Formats 4-3 4.5.1 Device Status Register (DXDS) 4-4 4.5.2 Command and Address Register (DXCA) 4-6 4.5.3 Control Unit Status Register (DXCS) 4-7 4.5.4 Offset and Status Register (DXOS) 4-9 4.5.5 Bus Address Register (DXBA) 4-10 4.5.6 Byte Count Register (DXBC) 4-11 4.5.7 Maintenance Out Register (DXMO) 4-11 iv CONTENTS (Cont) Page 4.5.8 Maintenance In Register (DXMI) 4-13 4.5.9 Control Bits Register (DXCB) 4-14 4.5.10 Non-Processor Request Data Register (DXND) 4-16 4.5.11 Extra Signals Registers (DXESI and DXES2) 4-17 4.5.12 Maintenance Out Buffered Register (DXMOB) 4-18 4.6 Programming Considerations 4-18 4.6.1 Hardware/Software Interlock 4-18 4.6.2 Boundary Considerations 4-19 4.6.3 Interrupt Request 4-19 4.6.4 Data Transfer 4-20 4.6.5 Status Presentation 4-20 4.6.6 On-Line/Off-Line Control 4-20 CHAPTERS THEORY OF OPERATION 5.1 Scope 5-1 5.2 Functional Description 5-1 5.3 Block Diagram Discussion 5-2 5.3.1 IBM Interface Operation 5-3 5.3.2 IBM Control Operation 5-11 5.3.3 Unibus Interface Operation 5-12 5.3.4 PDP-II Control Operation 5-12 5.3.5 Central Control Operation 5-13 5.3.6 Channel Simulator Operation 5-14 5.4 Sequences of Operation 5-14 5.4.1 IBM Sequences 5-15 5.4.1.1 Selector Channel-Initiated Sequences (CHI) 5-15 5.4.1.2 Control Unit Initiated Sequences (CUI) 5-19 5.4.1.3 Reset Sequences 5-20 5.4.1.4 Multiplexer Channel Differences 5-22 5.4.1.5 IBM Sequence Summary 5-24 5.4.2 DXll-B Sequences 5-27 5.4.2.1 Register Organization 5-27 5.4.2.2 Flow Diagram Conventions 5-29 5.4.2.3 Design Flows 5-30 5.5 Circuit Descriptions 5-40 5.5.1 DXll Device Status Register (DXDS) 540 5.5.2 Control Unit Status Register (DXCS) 5-41 5.5.3 DXll Bus Address Register (DXBA) 541 5.5.4 DXll Byte Counter (DXBC) 542 5.5.5 Control Unit Status Register (CUSR) Part of DXOS 542 5.5.6 NPR Data Register (DXND) 5-43 5.5.7 DXll Control Bits Register (DXCB) 543 5.5.8 Control Lines Out Register (CONO) Part of DXMO 544 v CONTENTS (Cont) Page 5.5.9 Control Lines In Register (CONI) Part of DXMI 5-44 5.5.10 IBM Bus-In Lines (BUS!) Part of DXMI 5-45 5.5.11 Tumble Table Index (TTNDX) 5-45 5.5.l2 Control Unit Address Register (CUAR) Part of DXCA 5-45 5.5.13 Control Unit Command Register (CUCR) Part of DXCA 5-45 5.5.14 Unibus Interface 5-46 5.5.15 NPR and TNT Control 5-46 5.5.16 Data Bus Multiplexer 5-47 5.5.17 Clock, Phase and Time State Generator 5-47 5.5.18 Maintenance Out Buffered Register (DXMOB) 5-47 5.5.19 General Controls 5-48 5.5.20 Signals and Gates 5-48 5.5 .21 Parity and Address Compare 5-49 5.5.22 IBM Interface 5-50 5.5.23 Select Bypass and Power Fail 5-50 5.5.24 "Bit Slice" and "Select" Loop Trace in Off-Line Cable Mode 5-51 5.5.25 EPO Panel Operation 5-51 CHAPTER 6 MAINTENANCE 6.1 Introduction 6-1 6.2 Preventive Maintenance 6-1 6.2.l Mechanical Checks 6-1 6.2.2 Test Equipment Required 6-1 6.3 Corrective Maintenance 6-2 6.3.1 General Corrective Procedures 6-2 6.3.2 Diagnostic Testing 6-2 6.3.3 Vibration Tests 6-3 CHAPTER 7 ENGINEERING DRAWINGS 7.1 General 7-1 APPENDIX A REFERENCE MATERIAL A.l Glossary A-I A.2 HEX/OCTAL/EBCDIC Conversion Chart A-12 A.3 Hexadecimal/Octal Conversion A-13 APPENDIX B ADDRESS ASSIGNMENTS B-1 APPENDIX C INTRODUCTION TO DXI1-B FLOW DIAGRAMS C-l vi ILLUSTRATIONS Figure No. Title Page 1-1 DXll-B, System 360/370 Channel to PDP-II Unibus Interface 1-3 1-2 Typical DXll-B System Block Diagram 1-4 1-3 DXll-B Functional Block Diagram 1-5 2-1 H960 and H957 Cabinet Dimensions 2-4 2-2 DXll-B Cable Connections Configured for User Operation 2-8 (Viewed from Rear) 2-3 DXll - IBM Cable Assembly Configured to Execute Cable Loop 2-9 Around Test DZDXH 2-4 M908 Module Before Wiring 2-10 2-5 I/O Address Format 2-10 2-6 Example of Wiring for Four Devices 2-11 2-7 Example of Wiring for 16 Devices 10 through IF (1x) 2-11 2-8 Example of Wiring for 32 Devices 50 through 6F (5x and 6x) 2-11 2-9 Example of Wiring for One Device (10) 2-11 2-10 Example of Wiring for Two Devices (10 to 11) 2-12 2-11 Example of Wiring for 8 Devices (20-27) 2-12 2-12 NPR Timeout Mono Calibration Waveform 2-14 2-13 BLLM Calibration Signal 2-15 2-14 Test Bus Cable Connections Without IBM 360/370 Cables Supplied 2-16 By Customer 2-15 Test Bus Cable Connections Using IBM 360/370 Cables 2-17 2-16 S.ignal Flow for Test Cable Connections 2-18 2-17 Normal Cable Connections to Channel Bus if on End of Bus 2-22 2-18 Normal Cable Connections to Channel Bus if Not on End of Bus 2-23 2-19 Sample FRIEND 360/370 Console Printout 2-29 2-20 IBM 360/370 Console 2-30 2-21 Sample Prep Card 2-32 2-22 Test Preparation Card 2-33 2-23 Typical Line Printer Copy from the DME/2848 Diagnostic 2-35 2-24 Input/Output Signals 2-43 2-25 Formats for Transmission of Information on the Buses 2-43 3-1 DXll-B Controls and Indicators 3-2 3-2 Type 861-A,-B,-C Power Controller Panels ~-1O 4-1 IBM 360/370/PDP-ll Data Format Comparison 4-1 4-2 360/PDP-ll Transfer Conventions 4-3 4-3 Device Status Register Bit Assignments 4-4 4-4 Command and Address Register Bit Assignments 4-7 4-5 Control Unit Status Register Bit Assignments 4-7 4-6 Offset and Status Register Bit Assignments 4-10 4-7 Bus Address Register Bit Assignments 4-11 4-8 Byte Count Register Bit Assignments 4-11 4-9 Maintenance Out Register Bit Assignments 4-12 4-10 Maintenance In Register Bit Assignments 4-13 4-11 Control Bits Register Bit Assignments 4-14 vii ILLUSTRATIONS (Cont) Figure No.
Load more

Recommended publications
  • PDP-11 Bus Handbook (1979)
    The material in this document is for informational purposes only and is subject to change without notice. Digital Equipment Corpo­ ration assumes no liability or responsibility for any errors which appear in, this document or for any use made as a result thereof. By publication of this document, no licenses or other rights are granted by Digital Equipment Corporation by implication, estoppel or otherwise, under any patent, trademark or copyright. Copyright © 1979, Digital Equipment Corporation The following are trademarks of Digital Equipment Corporation: DIGITAL PDP UNIBUS DEC DECUS MASSBUS DECtape DDT FLIP CHIP DECdataway ii CONTENTS PART 1, UNIBUS SPECIFICATION INTRODUCTION ...................................... 1 Scope ............................................. 1 Content ............................................ 1 UNIBUS DESCRIPTION ................................................................ 1 Architecture ........................................ 2 Unibus Transmission Medium ........................ 2 Bus Terminator ..................................... 2 Bus Segment ....................................... 3 Bus Repeater ....................................... 3 Bus Master ........................................ 3 Bus Slave .......................................... 3 Bus Arbitrator ...................................... 3 Bus Request ....................................... 3 Bus Grant ......................................... 3 Processor .......................................... 4 Interrupt Fielding Processor .........................
    [Show full text]
  • What We Learned from the PDP-11
    ABSTRACT Gordon Bell, William Il. Strecker November 8, 1975 COMPUTER STRUCTURES: WHAT HAVE WE LEARNED FROM THE PDP-ll? Over the FDP-11’S six year life behave in a particular way? about 20,000 specimens have been Where does it get inputs? HOW built based on 10 species (models). does it formulate and solve Al though range was a design goal, problems? it was unquantified; the actual range has exceeded expectations 3. The rest of the DEC (5OO:l in memory size and system organization--this includes price]. The range has stressed the applications groups assoc ia ted baa ic mini (mall computer with market groups # sales, architecture along all dimensions. service and manufacturing. The marn PM.5 structure, i.e. the UNIBUS, has been adopted as a de 4. The user, who receives the facto standard of interconnection final OUtQUt. for many micro and minicomputer systems. The architectural Note, that if we assume that a experience gained in the design and QrOduc t is done sequentially, and use of the PDP-11 will be described each stage has a gestation time of in terms Of its environment about two years, it takes roughly (initial goals and constraints, eight years for an idea from basic technology, and the organization research to finally appear at the that designs, builds and user’s site. Other organizations distributes the machine). ala0 affect the design : competitors (they establish a deaign level and determine the product life): and government IsI 1.0 TNTRODUCTTON and standards. There are an ever increasing number Although one might think that of groups who feel compel led to computer architecture is the sole control all products bringing them determinant of a machine, it is all common norm : the merely the focal point for a government (“5) , testing groups such specification.
    [Show full text]
  • DHQ11 User Guide
    EK -DHQ 11-UG.002 DHQ11 User Guide Prepared by Educational Services of Digital Equipment Corporation Second Edition, July 1987 Copyright © 1987 by Digital Equipment Corporation All Rights Reserved Printed in U.S.A. The information in this document is subject to change without notice. Digital Equipment Corporation assumes no responsibility for any errors herein. The following are trademarks of Digital Equipment Corporation: mmDDmrM DEC MASSBUS RT-l1 DECmate PDP UNIBUS DECsystem-IO PIOS VAX DECSYSTEM-20 Professional VAXBI DECUS Rainbow VMS DECwriter RSTS VT DIBOL RSX Work Processor FALCON CONTENTS PREFACE CHAPTER 1 INTRODUCTION 1.1 SCOPE................................................................. 1-1 1.2 OVERVIEW ........................................................... 1-1 1.2.1 General Description ................................................ 1-1 1.2.1.1 Modem Control Facility ....................................... 1-2 1.2.1.2 Self-Test Facility .............................................. 1-2 1.2.1.3 Diagnostic Programs .......................................... 1-2 1.2.1.4 Preventing Data Loss ......................................... 1-2 1.2.2 Physical Description ............................................... 1-2 1.2.2.1 On-Board Switchpacks ........................................ 1-3 1.2.2.2 Communications Standard ..................................... 1-3 1.2.3 Versions Of The DHQl1 ........................................... 1-4 1.2.4 Configurations ...... Ie. • • •• •• • • • • • • • • • • • • • • • • • • • • • •
    [Show full text]
  • Integriti Access Controller (IAC)
    Integriti Access Controller (IAC) An IP based master controller The Integriti Access Controller (IAC) is an IP based master controller for the Integriti modular hardware system. The Integriti Access Controller can be used to control and monitor up to 8 Doors or Lift cars on the Integriti RS-485 LAN). The IAC supports two doors/four wiegand and 16 RS485 SIFER readers and is expandable up to eight doors/ eight wiegand readers with the simple addition of 2 Door expander boards via the UniBus in-cabinet expansion interface. Equipped with an Ethernet Port, the IAC can be used both stand alone or expanded further via its UniBus and RS-485 Sub-LAN ports. The flexible, modular design of the IAC’s system parameters and Sub-LAN architecture allows a single standalone controller to be expanded to form a network of RS-485 expansion modules of up to 100,000 Users, 512 Zone Inputs, 250 Areas/ Zone Partitions and up to 80 card readers and 40 Doors. Integriti’s multi-controller architecture allows any number of IAC’s and or ISCs to be combined within the Integriti software package to form a globally managed small, medium or enterprise sized system where the entire network of controllers is managed as a whole. This architecture allows for an infinite number of Readers, Doors, Areas, Zone Inputs and Outputs. Doors Terminals Users LAN Modules Review Events No Smart Card 12 24 10,000 2 60,000 Expanded 40 80 100,000 16 100,000 Key Features Uni-Bus In-Cabinet Expansion ISC On board Features UniBus is an innovative in-cabinet bus which allows the • RJ45 - 10/100 Ethernet Port Ethernet Connected Services • RS-485 Sub-LAN • Connectivity to Integriti Software connection of Expansion devices, Communications devices and • USB Master & Slave Ports • SkyTunnel® Cloud Services & Door & Reader expansion devices on a common Plug & Play • UniBus In-Cabinet Expansion Interface Smart Phone connectivity • Multipath-IP / GSM STU Port (Port bus.
    [Show full text]
  • Unibus: a Universal Hardware Architecture for Serial Bus Interfaces with Real-Time Support
    UNIBUS: A UNIVERSAL HARDWARE ARCHITECTURE FOR SERIAL BUS INTERFACES WITH REAL-TIME SUPPORT A THESIS SUBMITTED TO THE GRADUATE SCHOOL OF NATURAL AND APPLIED SCIENCES OF MIDDLE EAST TECHNICAL UNIVERSITY BY MEHDI DUMAN IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN ELECTRICAL AND ELECTRONICS ENGINEERING JANUARY 2015 Approval of the thesis: UNIBUS: A UNIVERSAL HARDWARE ARCHITECTURE FOR SERIAL BUS INTERFACES WITH REAL-TIME SUPPORT submitted by MEHDI DUMAN in partial fulfillment of the requirements for the de- gree of Master of Science in Electrical and Electronics Engineering Department, Middle East Technical University by, Prof. Dr. Gülbin Dural Ünver Dean, Graduate School of Natural and Applied Sciences Prof. Dr. Gönül Turhan Sayan Head of Department, Electrical and Electronics Engineering Assoc. Prof. Dr. ¸SenanEce Güran Schmidt Supervisor, Electrical and Electronics Eng. Dept., METU Examining Committee Members: Prof. Dr. Gözde Bozdagı˘ Akar Electrical and Electronics Engineering Dept., METU Assoc. Prof. Dr. ¸SenanEce Güran Schmidt Electrical and Electronics Engineering Dept., METU Assoc. Prof. Dr. Cüneyt F. Bazlamaçcı Electrical and Electronics Engineering Dept., METU Dr. Nizam Ayyıldız ASELSAN,REHIS˙ Dr. Salih Zengin TÜBITAK˙ SAGE Date: I hereby declare that all information in this document has been obtained and presented in accordance with academic rules and ethical conduct. I also declare that, as required by these rules and conduct, I have fully cited and referenced all material and results that are not original to this work. Name, Last Name: MEHDI DUMAN Signature : iv ABSTRACT UNIBUS: A UNIVERSAL HARDWARE ARCHITECTURE FOR SERIAL BUS INTERFACES WITH REAL-TIME SUPPORT Duman, Mehdi M.S., Department of Electrical and Electronics Engineering Supervisor : Assoc.
    [Show full text]
  • I/O Műveletek PCI, PCI Express, SCSI Buszok Előadó
    PANNON EGYETEM, Veszprém Villamosmérnöki és Információs Rendszerek Tanszék Digitális Rendszerek és Számítógép Architektúrák 7. el őadás: I/O műveletek PCI, PCI Express, SCSI buszok El őadó: Dr. Vörösházi Zsolt [email protected] Jegyzetek, segédanyagok: Könyvfejezetek: http://www.virt.uni-pannon.hu Oktatás Tantárgyak Digitális Rendszerek és Számítógép Architektúrák (Nappali) (chapter06.pdf + további részek, amik a könyvben nem szerepelnek: PCI_bus.pdf, SCSI_bus.pdf ) Fóliák, óravázlatok .ppt (.pdf) Feltöltésük folyamatosan 2 I/O műveletek Aszinkron protokoll Szinkron protokoll Arbitráció (döntési mechanizmus) Megszakítás – kezelés (operációs rendszerek) Buszok – Buszrendszerek: PCI, PCI-Express, SCSI buszok 3 I/O egységek A számítógép a külvilággal, perifériákkal az I/O egységeken keresztül tartja a kapcsolatot. Az információ továbbítását az egységek között buszok végzik, amelyek interfészekkel kapcsolódnak egymáshoz. Interface: azon szabályok összessége, amelyek mind a fizikai megjelenést, kapcsolatot, mind pedig a kommunikációs folyamatokat leírják. Egy busz általában 3 fő kommunikációs vonalból állhat: vezérl őbusz, adatbusz, és címbusz . 4 I/O kommunikációs protokollok: Kommunikáció során megkülönböztetünk egy eszközpárt: a Master -t és Slave -t. A Master (pl. CPU) általában, mint kezdeményez ő, birtokolja és ellen őrzi a buszt, és átadja (ír / olvas) az adatokat a Slave-nek (pl. Memória). A kommunikációhoz el őredefiniált protokollokra (szabályok és konvenciók gy űjteménye) van szükség, amelyek meghatározzák az események sorrendjét és id őzítését. A kommunikáció feltétele a másik egység állapotának pontos ismerete. Lehetséges több M-S modul (pl. multi-master rendszer több kezdeményez ővel) is egy rendszerben. Két alapvet ő protokoll különböztethet ő meg: 1.) Aszinkron kommunikációs (pl. SCSI busz), és 2.) Szinkron kommunikációs (pl. PCI busz) protokoll. 5 Busz rendszer Master-Slave moduljainak szervezése Modul-szervezés Busz-Master (busz- vezérl ő) kommunikál Master Slave a Busz-Slave-el M M M S S (responder).
    [Show full text]
  • Unibus Troubleshooting User's Manual
    Unibus Troubleshooting user's manual ( Unibus Troubleshooting user's manual " ( E K-FS002-0P-001 ( ( COMPANY CONFIDENTIAL ( \ digital equipment corporation • maynard, massachusetts 1st Edition, February 1977 ( Copyright © 1977 by Digital Equipment Corporation ( The material in this manual is for informational purposes and is subject to change without notice. This manual is intended for use by authorized DIGITAL personnel only. The information contained in this manual is intended to be used for analyzing product performance. Printed in U.S.A. This document was set on DIGITAL's DECset-8000 computerized typesetting system. c The following are trademarks of Digital Equipment Corporation, Maynard, Massachusetts: DEC DECtape PDP DECCOMM DECUS RSTS DEC system-l 0 DIGITAL TYPESET-8 DECSYSTEM-20 MASSBUS TYPESET-II UNIBUS CONTENTS ( Page CHAPTER 1 INTRODUCTION 1.1 SYSTEM OVERVIEW . 1-1 1.2 UNIBUS TROUBLESHOOTING TECHNIQUES 1-2 1.3 HI/LO TERMINATOR MARGIN CARDS 1-2 1.4 UNIBUS VOLTAGE MARGIN TESTER BOX 1-2 1.5 SINGLE-ENDED MARGINING TECHNIQUE 1-2 CHAPTER 2 UNIBUS CONFIGURATION 2.1 GENERAL ..... 2-1 2.2 UNIBUS DEFINITIONS 2-1 ( 2.2.1 Bus Segment 2-1 2.2.2 Bus Cable 2-2 2.2.3 Bus Element 2-2 2.2.4 Lumped Load 2-2 2.2.5 Bus Jumper 2-2 2.2.6 Bus Terminator 2-4 2.2.7 Semi-Lumped Load 2-4 2.2.8 AC Unit Load 2-5 2.2.9 DC Unit Load 2-6 ( 2.2.10 Unibus Length and Loading 2-6 2.3 UNIBUS CONFIGURATION RULES 2-7 2.3.1 Maximum Cable Length (Rule No.1) 2-8 2.3.2 Maximum dc Loading (Rule No.2) 2-8 2.3.3 Maximum Lumped Loading (Rule No.3) 2-8 2.3.4 Skewed Cable Lengths (Rule No.4) 2-11 2.3.5 Skewed Cable Lengths, Supplement (Rule No.5) 2-13 2.3.6 Rule Violations (Rule No.6) .
    [Show full text]
  • PDP-11 Unibus Replacement Systems
    PDP-11 Unibus Replacement Systems PDP-11 Unibus Replacement System Model NuPDPU 4200 Eliminate Your PDP-11 has been a dependable workhorse for decades, but, Obsolete disks and tapes What do you do if it stops running? High maintenance costs Can you obtain spare parts? Aging, unreliable equipment Do you have knowledgeable staff to troubleshoot Preserve the old system? Existing applications Specialized Unibus I/O interfaces You want to get rid of the high maintenance overhead, but how do you connect a new system to your expensive, hard- Packaging and cables to-replace externally connected equipment? Improve You might be able to replace it all – Speeds 25 times faster than a PDP-11 system, software and external equipment – New equipment, new warranty for a significant capital investment; High performance disk Or, save time and money and choose NuPDP 4200: Unibus Support Retain your investment in software. Support for multiple Unibus devices Preserve your investment in external equipment. Follows all Unibus rules and specifications Migrate to a brand new system with a new Both Unibus PIO and DMA data transers are warranty. supported as well as all three Unibus interrupts Unibus PIO and DMA data transfers occur at NuPDP 4200 is a modern, industry-standard system that replaces the PDP-11 chassis, CPU, memory, and mass maximum Unibus speeds; throughput is limited only storage. Your current PDP-11 disk images can be by the Unibus device(s) transferred onto a NuPDP system running your existing operating system and applications. PDP-11 Compatibility Software compatible with existing applications You can select from a variety of new technology controllers such as the DR11-W, DR11-C, and DHU to replace popular Hardware compatible legacy Unibus interfaces.
    [Show full text]
  • VAX 7000/10000 DEC 7000/10000 Chapter of Datadoc
    Datadoc - DEC/VAX 7xx0/10xx0 This section by Dave Bazley..... Revision: Written July 1993, updated January 1994, August 1994, April 1995. 1 Introduction This section contains information on the following systems: DEC7xx0, DEC10xx0, VAX7xx0 and VAX10xx0. The basic 7000 and 10000 boxes, or platforms, can be configured to support either VAX architecture (the 32 bit, CISC based one, you know about, that made us great in the ’80s) or Alpha AXP architecture (the 64 bit, RISC based one, you’ve heard about, that’s going to make us great again!) The DECxxxx(x) systems are AXP based, the VAXxxxx(x) systems are VAX based. The 7000s are single cabinet systems and were designed as a replacement for VAX 6000s. For this reason they are described as "departmental" and sometimes termed "VAX 6000 style". However, read on to discover how different they actually are. The 10000s are multi-cabinet systems designed as a replacement for VAX 9000s. They are described as "datacentre" systems. The fact that all these systems can start off as VAXes and be simply upgraded to AXPs later, makes migrating from one architecture to the other easier for customers. As additional models and options appear, I expect this section to evolve and expand. Any suggestions for improvement would be welcome. 1.1 Codenames System Code name Architecture DEC 7xx0 Laser (Ruby) Alpha AXP DEC 10xx0 Blaser (Ruby) Alpha AXP VAX 7xx0 Laser (Neon) VAX/VMS VAX 10xx0 Blaser (Neon) VAX/VMS LASER: Light Amplified by Stimulated Emission of Radiation BLASER: Sounds like a jacket, first worn by sailors on HMS Blazer, but actually stands for Big laser.
    [Show full text]
  • 03 Top Level View of Computer Function and Interconnection
    William Stallings Computer Organization and Architecture 8th Edition Chapter 3 Elements of Bus Design What is a Bus? • A communication pathway connecting two or more devices • Usually broadcast • Often grouped —A number of channels in one bus —32 bit data bus is 32 separate single bit channels • What do buses look like? —Parallel lines on circuit boards —Ribbon cables —Strip connectors on mother boards (e.g. PCI) —Sets of wires Buses • There are a # of possible interconnection systems • Single and multiple BUS structures are most common • e.g. Control/Address/Data bus (PC) • e.g. Unibus (DEC-PDP) Connecting • All the units must be connected • Different type of connection for different type of units —Memory —Input/Output —CPU Bus Interconnection Scheme Definition of a Bus Bus lines - Digital interconnection mechanism • Transfer of data - A set of parallel wires with rules for putting • Address information and retrieving information on the wires. • Control of the bus - A digital communication mechanism that – Memory fetch or store allows two or more functional units to transfer – Ready control signals or data. – Bus Request and Bus Grant - The connection medium allowing the CPU, – Interrupt and Interrupt Acknowledge memory and I/O controllers to communicate – Clock Memory Connection • Receives and sends data • Receives addresses (of locations) • Receives control signals —Read —Write —Timing N words of = length. Each word is assigned a unique numerical address. A word can be read from or written into memory. The nature of operation is indicated by read and write control signals. The location for the operation is specified by an address Input/Output Connection • Output - Receive data from computer - Send data to peripheral • Input - Receive data from peripheral or send data to computer • Receive control signals from computer • Send control signals to peripherals (spin disk) • Receive addresses from computer —e.g.
    [Show full text]
  • DMF32 Multi-Function Communications . Interface
    , \ EK-OMF32-TO-OO 1 DMF32 Multi-Function Communications . Interface . Technical Description \ . " ~ , EK DMF32 TD 2 EK-DMF32-TD-OO 1 DMF32 Multi-Function Communications Interface Technical Description Prepared by Educational Services of Digital Equipment Corporation Copyright © 1983 by Digital Equipment Corporation All Rights Reserved The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Printed in U.S.A. The manuscript for this book was created on a DIGITAL Word Processing System and, via a translation program, was automatically typeset on DIGITAL's DECset Integrated Publishing System. Book production was done by Educational Services Development and Publishing in South Lawrence, MA. The following are trademarks of Digital Equipment Corporation: ~DmDD~D DECtape Rainbow DATATRIEVE DECUS RSTS DEC DECwriter RSX DEC mate DIBOL UNIBUS DECnet MASSBUS VAX DECset PDP VMS DECsystem-lO PjOS VT DECSYSTEM-20 Professional Work Processor CONTENTS CHAPTER 1 INTRODUCTION Page 1.1 SCOPE ................................................................................................................ 1-1 1.2 DMF32 DOCUMENTATION .............................................................................. 1-1 1.3 PHYSICAL DESCRIPTION ................................................................................ 1-2 1.4 FUNCTIONAL DESCRIPTION ........................................................................
    [Show full text]
  • Brookhaven Fastbus/Unibus Interface 3 Nl 33165 G
    Oo/OF - " - 7 SuLniiitted to tHe Third Biennial Conference on Real-Time Computer Applications in Nuclear & Particle Physics, Berkeley,:CA "" Kay 16-19, 1983 BROOKHAVEN FASTBUS/UNIBUS INTERFACE 3 NL 33165 G. Benenson, J. Bauecnfeind, R.C. Larsen, L.8. Lelpuner, and W.H.Morse* BNL--3 316 5 Brookhaven National laboratory Associated Universities, Inc. Upton, New York 11973 DB83 014434 R.K. Adair, J.K. Black, S.R. Campbell, H. Kasha, and H.P. Schmidt Tale University New Haven, Connecticut 06511 I. Summary CONTROL signals are needed to determine which of many A typical high energy physics experiment re- potential masters will actually assume mastership quires both a high speed data acquisiton and proces- during a particular time slot on the bus. ADDRESS sing system, for data collection and reduction; and a Information is used to select which of many potential general purpose computer to handle further reduction, slaves will actually respond io the current master. bookkeeping and mass storage. Broad differences in architecture, format or technology, will often exist between these two systems, and Interface design can become a formidable task. A. ONE-TO-ONE The PDP-11 series minicomputer is widely used in physics research, and the Brookhaven FASTBUS is the only standard high speed data acquisition system which Is fully Implemented in a current high energy physics experiment, this paper will describe the design and operation of an interface between these two-systems. The major issues are elucidated by a preliminary discussion on the basic principles of Bus Systems, and their application to Brookhaven FASTBUS and UMIBUS.
    [Show full text]