SINTRAN Il Utilities Manual
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione
Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga -
NORSK DATA AS SINTRAN Iii Reference Manual
SINTRAN Il Reference Manual NORSK DATA AS SINTRAN IiI Reference Manual ND-60.128.03 NOTICE The information in this document is subject to change without notice. Norsk Data A.S assumes no responsibility for any errors that may appear in this document. Norsk Data A.S assumes no responsibility for-the use or reliability of its software on equipment that is not furnished or supported by Norsk Data A.S. The information described in this document is protected by copyright. It may not be photocopied, reproduced or translated without the prior consent of Norsk Data A.S. Copyright © 1983 by Norsk Data A.S This manual is in loose leaf form for ease of updating. Old pages may be removed and new pages easily inserted if the manual is revised. The loose leaf form also allows you to place the manual in a ring binder (A) for greater protection and convenience of use. Ring binders with 4 rings corre- sponding to the holes in the manual may be ordered in two widths, 30 mm and 40 mm. Use the order form below. The manual may also be placed in a plastic cover (B). This cover is more suitable for manuals of less than 100 pages than for large manuals. Plastic covers may also be ordered below. M= | ~ . IB== B 'S NORSK DATA AS NORSK DATA AS Bil=i & e lll\ ® A Ring Binder B Plastic Cover Please send your order to the local ND office or {in Norway) to: Documentation Department Norsk Data A.S P.0O. Box 4, Lindeberg gérd Oslo 10 ORDER FORM | would like to order Ring Binders, 30 mm, at nkr 20,- per binder Ring Binders, 40 mm, at nkr 25,- per binder Plastic Covers at nkr 10,- per cover NAME .. -
The Norwegian State Railway System GTL (1976) Tor Olav Steine
The Norwegian State Railway System GTL (1976) Tor Olav Steine To cite this version: Tor Olav Steine. The Norwegian State Railway System GTL (1976). 4th History of Nordic Com- puting (HiNC4), Aug 2014, Copenhagen, Denmark. pp.290-298, 10.1007/978-3-319-17145-6_30. hal-01301420 HAL Id: hal-01301420 https://hal.inria.fr/hal-01301420 Submitted on 12 Apr 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License The Norwegian State Railway System GTL (1976) Tor Olav Steine, with the help of former colleagues [email protected] Abstract. In 1976 the Norwegian State Railway System (NSB) planned a new system to keep track of all its freight cars. Among the duties were these: arranging trains at the shifting station in Alnabru outside Oslo, following (tracking) the trains as they moved along the tracks inside Norway, optimization of car maintenance and statistics. The system could save millions of Norwegian Crowns by better utilization of the car pool. It was named GTL for Gods Transport Ledelse (there is no Divine link; “Gods” simply means cargo in Norwegian). -
EVOLUTION of Cowtrot SYSTEMS for Aecelsiato&S
- 271 - EVOLUTION OF COWTROt SYSTEMS FOR AeCELSiAtO&S M.C. Crovley-Milling CRM, Geneva 1, HISTORICAL The ««liest accelerator* wer« quite •»*'. 1, and their controls few, as can be seen from fig. 1 which ahow* the 11-inch eye lot ron built by Lawrence and Livingstone in 1932. Control wm by switches sai variable resistors and indication by a variety of Meters, wired directly iota the appropriate circuit, Where the control eleaemt had to be at high vol• tage, a loop of string vat often uted Co operate it. I1* Figur* t : the 11-inch Cyclotron at Berkeley As the si«* and power of the accelerator* increased, they had to be surrounded by heavier and heavier »hielding, and the controls and indications had to be taken away from the accelerator lt»el£ and transferred to a separate control roo». At first this was done by ju»t extending the cables, keeping each control and indication separate, but the increa• sing number* of value» to be indicated led to some manual switching of instruments between different circuit* to save panel apace. In the 1980's, even though the cyclic, accelerators had grown up to 200 » in diameter, the expense of taking cables for every control element to the control too» was not exce««ive. However, in the i960'», project* of auch larger siae were being considered, where this would no longer be true. The first of theae was the "2-mile" electron lime at SLAC. This is composed of 240 alraott identical taodule*, each aodule having very many controls and indications of interest to the operators, The enormous number of cables which would be required to take all these to the control room was reduced considerably by rentóte awl t i- plexing; that is switching one particular control or indication from each «©«Joie in turn onto the s«se set of cables. -
TU-P20 How to Survive the Upgrade Treadmill
HOW TO SURVIVE THE UPGRADE TREADMILL Kirsten Hinsch, Ursula Lauströer, Rüdiger Schmitz, Winfried Schütte - DESY Hamburg, Germany Abstract Lets look a little closer on the impact of changes in Here at DESY we have nine large particle accelerators each part of our environment. and correspondingly a large and complex control system. It consists of subsystems of many generations of hard and 3 IMPACT OF CHANGES software. Until recently we even had to support Norsk Data mini computers so called NORDs. The number of 3.1 Changes in the accelerator applications is considerably more than a thousand. The This is a true place of peace and tranquility. Of course a control team consists of a dozen people aged typically in new accelerator needs a new control system. A closed one the fifties. This large, diverse and understaffed system in- does not need one anymore. Still a major change in the troduces a considerable amount of (healthy) inertia. On accelerator does not necessary have any imp act on the the other hand we have a fast hard- and software upgrade technologies used. It is just a good and most welcome op- cycle in the general computing scene. There is every few portunity to change things now. years a major operating system upgrade. This conflict produces tension and stimulation. 3.2 Network Network upgrades have moderate impact on the other 1 INTRODUCTION areas (fair degree of orthogonality). The major problem we have now is CISCOs mediocre IPX support. We ex- Everybody who works a few years in our field physical- pect this to get worse. -
The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS Tor Steine
The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS Tor Steine To cite this version: Tor Steine. The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS. 3rd History of Nordic Computing (HiNC), Oct 2010, Stockholm, Sweden. pp.249-257, 10.1007/978-3-642-23315- 9_28. hal-01564615 HAL Id: hal-01564615 https://hal.inria.fr/hal-01564615 Submitted on 19 Jul 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS Tor Olav Steine Formerly of Norsk Data AS [email protected] Abstract. Norsk Data was a remarkable company that in just twenty years went from a glimmer in the eyes of some computer enthusiasts to become number two in share value at the Oslo Stock Exchange. Within a few years thereafter, it collapsed, for no obvious reason. How was this tremendous success possible and why did the company collapse? Keywords: Collapse, computer, F16, industry, minicomputer, Norsk Data, Nord, simulator, success, Supermini 1 The Beginning 1.1 FFI A combination of circumstances led to the founding of Norsk Data1 in June 1967. -
Fifty-Year Anniversaries in Norwegian Computing History
EVENTS AND SIGHTINGS Editor: Chigusa Kita Fifty-Year Anniversaries in Norwegian Computing History wo fifty-year anniversaries in computing history were celebrated in Oslo in September 2017: the fifty-year T anniversary of the creation of the Simula program- ming language, and the fifty-year anniversary of the found- ing of the Norsk Data computer company. Simula The Simula 67 programming language, first formally defined in 1967, was a step in a series of developments by Ole-Johan Dahl and Kristen Nygaard that began in the early 1960s.1 Dahl and Nygaard were given the 2001 IEEE John von Neumann Medal and the ACM 2001 A.M. Turing Award for their creation of Simula. A fifty-year anniversary celebration for Simula took place (in the “Simula Auditorium” in the “Ole-Johan Dahl Building”) at the University of Oslo on 27 September 2017. PHOTO 1. Photo credit: Harald Brombach/digi.no. The celebration began with unveiling of a plaque from the IEEE History Committee’s Milestone program. The plaque reads: chaired by Eric Jul (“Whither Programming Languages? Can IEEE Milestone We Still Celebrate Simula 50 Years from Now?”) with partic- Object-oriented Programming, 1961–1967 ipation of the prior three speakers and Ole Lehrmann Mad- Ole-Johan Dahl and Kristen Nygaard created the sen and Olaf Owe.2 Videos from the event are available.3 Simula programming languages in the 1960s at the The previous afternoon, the Association of Simula Norwegian Computer Center, and in so doing intro- Users (ASU) held a several-hour meeting at which there duced a new way of modeling and simulating complex were six presentations and a wrap-up session. -
Embedded Systems - ECE) I -M.TECH I -Semester (AUTONOMOUS-R18
Presentation on Principles of Distributed Embedded Systems (Embedded Systems - ECE) I -M.TECH I -Semester (AUTONOMOUS-R18) Prepared by, Dr. S. Vinoth Associate Professor UNIT - I REAL TIME ENVIRONMENT 2 UNIT - I REAL-TIME ENVIRONMENT .Real-time computer system requirements .classification of real time systems .simplicity, global time .internal and external clock synchronization .real time model. Real time communication .temporal relations, dependability .power and energy awareness .real time communication .event triggered .rate constrained .time triggered. 3 What is an Embedded system? 4 What is a real-time system? . A real-time system is any information processing system which has to respond to externally generated input stimuli within a finite and specified period –the correctness depends not only on the logical result but also the time it was delivered –failure to respond is as bad as the wrong response! . The computer is a component in a larger engineering system => EMBEDDED COMPUTER SYSTEM 99% of all processors are for the embedded systems market 5 Terminology • Hard real-time — systems where it is absolutely imperative that responses occur within the required deadline. E.g. Flight control systems. • Soft real-time — systems where deadlines are important but which will still function correctly if deadlines are occasionally missed. E.g. Data acquisition system. • Real real-time — systems which are hard real-time and which the response times are very short. E.g. Missile guidance system. • Firm real-time — systems which are soft real-time but in which there is no benefit from late delivery of service. A single system may have all hard, soft and real real-time subsystems In reality many systems will have a cost function associated with missing each deadline. -
Cern European Organization for Nuclear Research
S CERN 75-20 J> Laboratory II ^ Control Group §j 22 December 1975 um ORGANISATION EUROPÉENNE POUR LA RECHERCHE NUCLÉAIRE CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH THE DESIGN OF THE CONTROL SYSTEM FOR THE SPS M.C. Crowley-Milling GENEVA 1975 © Copyright CERN, Genève, 1975 Propriété littéraire et scientifique réservée pour Literary and scientific copyrights reserved in tous les pays du monde. Ce document ne peut all countries of the world. This report, or être reproduit ou traduit en tout ou en partie any part of it, may not be reprinted or trans sans l'autorisation écrite du Directeur général lated without written permission of the du CERN, titulaire du droit d'auteur. Dans copyright holder, the Director-General of les cas appropriés, et s'il s'agit d'utiliser le CERN. However, permission will be freely document à des fins non commerciales, cette granted for appropriate non-commercial use. autorisation sera volontiers accordée. If any patentable invention or registrable Le CERN ne revendique pas la propriété des design is described in the report, CERN makes inventions brevetables et dessins ou modèles no claim to property rights in it but offers it susceptibles de dépôt qui pourraient être décrits for the free use of research institutions, manu dans le présent document; ceux-ci peuvent être facturers and others. CERN, however, may librement utilisés par les instituts de recherche, oppose any attempt by a user to claim any les industriels et autres intéressés. Cependant, proprietary or patent rights in such inventions le CERN se réserve le droit de s'opposer à or designs as may be described in the present toute revendication qu'un usager pourrait faire document. -
The Oslo Cyclotron Data Acquisition System
NO9100105 UNIVERSITY OF OSLO DAISY the Oslo Cyclotron Data Acquisition System T. Ramsøy Department of Physics, University of Oslo, Norway £>uf*-- Report91-21 • Received 1991-08-30 ISSN-0332 5571 *__' ,*.a-",' J";"^'^" DEPARTMENT OF PHYSICS REPORT SERIES Hi Ail lill JU ILI mil ..J Ji Jl lll'feiliili' Preface This document is intended for anyone that will use the Oslo cyclotron data acquisition system or wants to get some deeper understanding of the structure of the system. Each chapter is opened with a more general description. The contents should be known to all users. More technical information is found in the last part of the chapter. The source code listing is found in a separate volume, "DAISY - Volume 2, Appendix " available at the cyclotron laboratory. Oslo 30-08-1991 'T&H. (jo Tore Ramsøsøyy // Contents 1. Introduction 3 2. VME front-end system ........— „ 4 2.1 Getting started 4 2.1.1 Preparing for a run 6 2.1.2 Starting the data acquisition 9 2.1.3 Resetting the VME system 9 2.2 Hardware 11 2.2.1 Processor unit 11 2.2.2 Trigger pattern unit 12 2.2.3 NIM interface system 13 2.2.4 CAMAC interface 14 2.2.5 Power supply and crate 14 2.3 Software 15 2.3.1 Event_Builder 15 2.3.2 Memory allocation 17 2.3.3 Data format 18 2.3.4 Pattern bit allocation 19 2.3.5 Compilation and loading 21 3. VME to ND link 22 3.1 Operating the link 22 3.1.1 Restarting the DOMINO controller 22 3.2 Hardware 24 3.2.1 The DOMINO controller 24 3.2.2 Internal VMEbt) - crate 24 3.2.3 VME-VME link 24 3.2.4 Architecture 25 3.3 Software 26 3.3.1 Memory mapping 27 3.3.2 Compilation and loading 28 4. -
SINTRAN III NODAL Systems
THE SIHTIAN III NODAL SYSTEM Oslo University Varsion T.B. Skuli Institute of Physics University of Oslo FOB 1048, Blindern, Oslo 3, Norway Report 80-17 October 1980 The SINTRAN III NODAL System Oslo University Version T.B. Skaali Institute of Physics, University of Oslo POB 1046, Blindern, Oslo 3, Norway October 198O -ooOoo- 1. Introduction , 2. Basic Features of NODAL i 3. The NODILER Preinterpreter 2 4. Implementation under SINTRAN III 4 4.1 Background NODAL 5 4.2 Real Time NODAL Programs o 4.2.1 Interactive RT NODAL Programs 7 4.2.2 File-driven RT NODAL Programs 7 4.3 Oslo University Revisions to the NODAL System ... b 5. NODAL-SINTRAN III Fi...-i.ions 10 b.i RT Program Control 10 5.2 "Escape" Control Functions 11 5.3 General RT Functions 11 5.4 CAMAC Functions 15 5.5 Magnetic Tape and Floppy Disc Handling 16 5.6 Input/Output and I/O Buffer Functions 17 3.7 Functions for Fast Input/Output of Integers Arrays . 1C- 5.8 SINTRAN III Monitor Calls - NODAL Functions . 21 6. Functions for Double Precision Integers 22 7. Display Functions 23 6. TEKPLOT Program Package 24 References 25 Appendix: A Examples on the RT Use of NODAL 26 Throughout the report, replace the characters Æ and Å with [ and ], respectively. October 198O Introduction This report describes the Oalo University implementation of the NODAL system under the operating system 3INTRAN III. At present, the NODAL system has been installed on two NORD-'O.S computers at the Physics Department and on a NORD-'OO at the Chemistry Department, University of Oslo. -
Opensource Software Im Alltag
OpensourceOpensource SoftwareSoftware imim AlltagAlltag -- IstIst dasdas möglich?möglich? Willkommen zum Xing Stammtisch Alexander Demmler – 25.11.2016 © A. Demmler 2016 www.lacunasolutions.com 1 Marktanteile Desktop Systeme 2016 © A. Demmler 2016 www.lacunasolutions.com 2 Webserver Systeme © A. Demmler 2016 www.lacunasolutions.com 3 Einsatz von OSS in US Unternehmen: Northbridge Eine Venture Capital Company. Game changers disrupt existing markets. They also create new multi-billion dollar markets and have the potential to change the way we live and work. http://www.northbridge.com © A. Demmler 2016 www.lacunasolutions.com 4 Was bedeutet OpenSource? • OpenSource Software (OSS) ist professionelle Software unter einer alternativen Entwicklungs- und Vertriebsform • OpenSource ist nicht Linux - aber Linux ist auch OpenSource! • OpenSource bedeutet ein Stück Freiheit: - freie Auswahl - Freiheit ob und wieviel man bezahlt - Freiheit in der Nutzung © A. Demmler 2016 www.lacunasolutions.com 5 Was ist die Community? • Die Community besteht aus - Entwicklern + Beratern + Anwendern + Hobbyisten - grossen Unternehmen (HP, IBM, SUN) - Distributoren wie SUSE, RedHat, Ubuntu u.a. • Die Community entwickelt und pflegt gemeinsam die Software und bietet Unterstützung (Support) • Die Community ist kein Club von Hackern, Freaks und anderen Bösewichten! © A. Demmler 2016 www.lacunasolutions.com 6 Das Geschäftsmodell Freie Software Dienstleistungen (Kosten) Basis Version Erweiterungen Download im WWW Service + Support Online Support Schulungen Zusatzeinkünfte Werbung + Sponsoren © A. Demmler 2016 www.lacunasolutions.com 7 Lizenzrechtliches • Softwarecode (Quellen) sind offen gelegt: - Verbreitung und Nutzung sind ausdrücklich erlaubt - Veränderung (Anpassung, Erweiterung) erlaubt - Quellcode muss offengelegt werden • Es gibt historisch bedingt verschiedene Lizenzmodelle. (GPL, OSL, CPL, EPL u.a) • EU Initiative um Lizenzen vereinen: http://ec.europa.eu ACHTUNG: Auch hier gelten Vorschriften! Computerwoche: http://www.computerwoche.de © A.