1 1999/Ph 514: Lab #5 : Course Projects EPICS Lab #5 Course Projects.

Slides:

Advertisements

Similar presentations

Chapter 11 user support. Issues –different types of support at different times –implementation and presentation both important –all need careful design.

Advertisements

CS0004: Introduction to Programming Visual Studio 2010 and Controls.

ATM User Interface Design. Requirements A bank customer is able to access his or her account using an automatic teller machine. To be able to use an ATM.

Maintenance Modifying the data –Add records –Delete records –Update records Modifying the design –Add fields into tables –Remove fields from a table –Change.

Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface.

Well-behaved objects Debugging. 2 Objects First with Java - A Practical Introduction using BlueJ, © David J. Barnes, Michael Kölling Prevention vs Detection.

Software Requirements

PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.

Self-Contained Particulate Filter Filter 3 Presenters: Ian Gray, Kyhia Bostic Demo Given by: Nathan Sullivan.

1 A Student Guide to Object- Orientated Development Chapter 9 Design.

The chapter will address the following questions:

Input/Output Design User Interface Design

Programming Logic Program Design. Objectives Steps in program development Algorithms and Pseudocode Data Activity: Alice program.

1 Shawlands Academy Higher Computing Software Development Unit.

EPICS Insertion Device Control System Pete Owens EPICS Collaboration Meeting June 2003 Control System for a Helical Undulator Pete Owens Daresbury Laboratory.

COE4OI5 Engineering Design. Copyright S. Shirani 2 Course Outline Design process, design of digital hardware Programmable logic technology Altera’s UP2.

Summary Data Modeling SDLC What is Data Modeling Application Audience and Services Entities Attributes Relationships Entity Relationship Diagrams Conceptual,Logical.

Developing a Solution How to create the computer-based solution for a real-world problem. 1.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.

ASIC/FPGA design flow. FPGA Design Flow Detailed (RTL) Design Detailed (RTL) Design Ideas (Specifications) Design Ideas (Specifications) Device Programming.

Database Queries. Queries Queries are questions used to retrieve information from a database. Contain criteria to specify the records and fields to be.

ECE482 Final Project Spring 03. Specification Design a digital thermometer to report the temperature in the room in degrees Fahrenheit. The PC should.

1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.

BTEC Unit 06 – Lesson 08 Principals of Software Design Mr C Johnston ICT Teacher

Activating Clarity  Activating Clarity  Activation  Online Activation  Fax Activation  Review and Verify Activation and License Terms  Updating.

Software Life Cycle Requirements and problem analysis. –What exactly is this system supposed to do? Design –How will the system solve the problem? Coding.

Software Development Process.  You should already know that any computer system is made up of hardware and software.  The term hardware is fairly easy.

C++ Programming Language Lecture 2 Problem Analysis and Solution Representation By Ghada Al-Mashaqbeh The Hashemite University Computer Engineering Department.

User Support Chapter 8. Overview Assumption/IDEALLY: If a system is properly design, it should be completely of ease to use, thus user will require little.

IPortal Bringing your company and your business partners together through customized WEB-based portal software. SanSueB Software Presents iPortal.

4. The process specification （プロセス仕様） You will learn: （次の内容を学び） The concept of process specification （プロセス仕様の概念） Notations for process specification （プロセス.

Definition of Terms Software/Programs Programs that directs the operation of a computer system Set of instructions Codes Programming Process of planning,

Requirements Engineering Overview Senior Design Don Evans.

Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.

1 User Interface Design Components Chapter Key Definitions The navigation mechanism provides the way for users to tell the system what to do The.

TAC SRs Initiation Best Practices A non-exhaustive list to serve as a Best Practices reference for Cisco customers before/while opening TAC Cases 3 I’s.

Chap#11 What is User Support?

L To identify the services that the customer requires from a system and the constraints under which it operates and is developed.

The Software Development Process

Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.

FPGA Calculator Core Final Presentation Chen Zukerman Liran Moskovitch Advisor : Moshe Porian Duration: semesterial December 2012.

 Accessible informal format.  Graphical notation is trivial. But writing good use cases is a skillful process.

Intermediate 2 Computing Unit 2 - Software Development.

Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved Object-Oriented Design.

The Hashemite University Computer Engineering Department

1 1999/Ph 514: Lab #1 : CA Clients EPICS Lab #1 CA Clients.

1 Week 6 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.

1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.

CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.

Chapter 2: Advanced programming concepts Part 3: The user interface Lecture 5 1.

1 Digital processing applications for DE2 card High Speed Digital Systems Lab Winter 2008/09  Instructor: Mony Orbach  Students : Avner Reisz, Natty.

Final Fantasy ½: IOC Overview Team Q CSE 403 Winter ‘03 I’ve got something special for you.

 Profiles are the basic building blocks of the Opera database for your hotel.  They can be simple, with a first and last name only, or complex with preferences,

1 1999/Ph 514: Lab #2 : IOC Database EPICS Lab #2 IOC Database.

Selection Using IF THEN ELSE CASE Introducing Loops.

1 Software Requirements Descriptions and specifications of a system.

Databases and Database Users

CS240: Advanced Programming Concepts

Chapter 2: System Structures

Procedural Abstraction Object-Oriented Code

Lesson 5: Epic Past Appointment Scheduling

SAP transaction RSA3 Enter the Data source Name

“Would I have to do this all by myself …….?”

Lesson 5: Epic Past Appointment Scheduling

Database Actors.

Summary Data Modeling SDLC What is Data Modeling

Lesson 5: Epic Past Appointment Scheduling

Presentation transcript:

1 1999/Ph 514: Lab #5 : Course Projects EPICS Lab #5 Course Projects

2 1999/Ph 514: Lab #5 : Course Projects EPICS Bipolar Power Supply u Develop an EPICS control system for a unipolar power supply and a relay to implement a bipolar supply. Requirements : Operator enters a value from -50 amps to +50 amps Rate of change of current must not exceed 10 amps/sec The relay must only be changed when the current = 0 amps Readback should indicate actual ramping current and range from -50 to 50 amps Provide a warning when actual current does not equal setpoint Amp Power Supply Magnet Current : -50 to +50 Amps + -

3 1999/Ph 514: Lab #5 : Course Projects EPICS Elevator Control System u Develop an EPICS control system for a building elevator u Simple or complex model of an elevator u Choose the EPICS building blocks to implement intelligence u Database, State Notation Language, C subroutines u Choose how to present model u I/O Bugs, Digital I/O cards, MEDM screens etc. u Concentrate on areas most interesting and useful to you

4 1999/Ph 514: Lab #5 : Course Projects EPICS Grading u Credit will be given for: u Logical design (documented?) u Appropriate use of EPICS facilities u i.e. Use records where appropriate rather than workstation-based clients u Intuitive interface for the operator/user u Maintenance Information u More detailed displays u Debugging messages u Working model, implements normal expected behavior u Artistic merit