Smart Digital Valve Control Simulator May 01-11 April 25, 2001 Client: Client: Fisher Controls Intl....
-
Upload
tracey-gibson -
Category
Documents
-
view
215 -
download
0
Transcript of Smart Digital Valve Control Simulator May 01-11 April 25, 2001 Client: Client: Fisher Controls Intl....
Smart Digital Valve Control Smart Digital Valve Control SimulatorSimulator
May 01-11May 01-11
April 25, 2001April 25, 2001Client:Client: Fisher Controls Intl. Inc.
Contacts:Contacts: Patrick Ryan and Jeff Seyller
Faculty Advisor:Faculty Advisor: Dr. Jacobson
Team MembersTeam MembersChad JanovickTy HartwickMike Ziller
Brian Kierzek
Presentation OutlinePresentation Outline Problem Statement Design Objectives Functional Requirements End-Product Description Assumptions and Limitations Project Risks and Concerns Technical Approach Evaluation of Project Success Recommendations for Further Work Human and Financial Budgets Lessons/Skills Learned Summary Demonstration Questions
Problem Statement and Problem Statement and SolutionSolution
Fisher Controls needs the ability to simulate Digital Valve Controllers (DVCs) due to the physical and financial impossibility of testing Valvelink® software with large networks of DVCs.
Problem Statement and Problem Statement and Solution ( cont )Solution ( cont )
The goal of this project is to develop, HARTSim, a Windows based application capable of simulating communication between Valvelink® and a network of virtual devices.
Users and UsesUsers and Uses UsersUsers
– Software Development EngineersSoftware Development Engineers– Software Test EngineersSoftware Test Engineers– Technical Support StaffTechnical Support Staff– Sales RepresentativesSales Representatives
UsesUses– Development and testing of ValvelinkDevelopment and testing of Valvelink®®
– TroubleshootingTroubleshooting– Showing capabilities of ValvelinkShowing capabilities of Valvelink®® to customers to customers
Design ObjectivesDesign Objectives
Communicate with Valvelink® via a serial port through the use of industry standard Highway Addressable Remote Transducer (HART) protocol.
Build a set of virtual devices capable of understanding and creating HART messages.
Allow user configuration of device characteristics. Provide a intuitive graphical user interface.
Design ConstraintsDesign Constraints
Windows 9X/NT restraintsWindows 9X/NT restraintsVisual C++ restraintsVisual C++ restraintsSerial communication restraintsSerial communication restraintsExpandable/Open-ended formatExpandable/Open-ended formatNeed for intuitive interfaceNeed for intuitive interface
Functional RequirementsFunctional Requirements
• Network Tree PaneNetwork Tree Pane• Device Properties Pop-Up PaneDevice Properties Pop-Up Pane• Communication Log PaneCommunication Log Pane• Status PaneStatus Pane• Communication Module (Router Logic)Communication Module (Router Logic)• Virtual DeviceVirtual Device
Network Tree PaneNetwork Tree PaneThis pane allows the user to configure, start, and stop a simulation; drag, drop, and delete devices; and open a device properties page.
Device Properties DialogDevice Properties DialogThis pane will allow the user to view and configure variables and their values for a specific devices.
Communication Log Pane and Status PaneCommunication Log Pane and Status Pane
The Communication Log Pane will list all HART commands that go over the line. The Status Pane will display the number of messages sent and received, and an LED will light if there is activity on the line.
User InterfaceUser Interface
Communication ModuleCommunication Module(Router Logic)(Router Logic)
Receives packets from ValvelinkReceives packets from Valvelink®®
Creates application friendly HART packetsCreates application friendly HART packets Routes packets to correct virtual deviceRoutes packets to correct virtual device Packages responsePackages response Sends packets to ValvelinkSends packets to Valvelink®®
Incoming FSM Routing
LogicOutgoing
FSM
Virtual
Device
Serial
Port
Virtual DevicesVirtual Devices
Interprets HART packetsInterprets HART packets– Looks in packet for command number and any dataLooks in packet for command number and any data
Creates response for Communication ModuleCreates response for Communication Module– Uses command number and data to create a response packetUses command number and data to create a response packet
Preamble Start Ch. Address Command Byte Count [Status] [Data] Checksum
Virtual Device InheritanceVirtual Device Inheritance
Virtual Device
Virtual MUX Virtual DVC
Virtual DVC5000
Virtual DVC6000
Virtual MUX A
Virtual MUX B
Device Archive Device Archive (Not Implemented)(Not Implemented)
Object serialization system– Uses Microsoft Foundation Classes’ (MFC) object serialization
methods Saves
– Network configuration– Device properties
End Product DescriptionEnd Product Description
Windows based software packageWindows based software package Intuitive user interfaceIntuitive user interface Capable of emulating DVC 5 & 6000sCapable of emulating DVC 5 & 6000s Communication through the serial port Communication through the serial port
using HART protocolusing HART protocol
Assumptions and LimitationsAssumptions and Limitations
Assumptions:Assumptions: Users are familiar with ValveLink® and HART protocolUsers are familiar with ValveLink® and HART protocol Accurate DVC models can be constructedAccurate DVC models can be constructed Open-ended design will allow for future expansionOpen-ended design will allow for future expansion Software will be easy to set up and useSoftware will be easy to set up and use
Limitations:Limitations: Serial port timing constraintsSerial port timing constraints Software can only be run on Windows based PCsSoftware can only be run on Windows based PCs Semester is not long enough to implement all featuresSemester is not long enough to implement all features
Risks and Risk ManagementRisks and Risk Management
• Loss or damage of master codeLoss or damage of master code-Source Control-Source Control
• Staying within the scope of the projectStaying within the scope of the project-Constant contact with Fisher Controls-Constant contact with Fisher Controls
• Time ManagementTime Management-Weekly team meetings-Weekly team meetings
-Multi-tasking ( split project into sections )-Multi-tasking ( split project into sections )
Technical ApproachTechnical Approach
Visual C++ vs. Visual Basic vs. Java Multi-Threaded Application vs. Single Threaded
Application Use of object inheritance for modular design User interface parallels ValveLink ®®
Evaluation of Project SuccessEvaluation of Project Success(Milestones)(Milestones)
Intuitive user interface (100%)Intuitive user interface (100%)– Easy for user to set up a simulationEasy for user to set up a simulation– User is able to configure devicesUser is able to configure devices
Communications enabled (100%)Communications enabled (100%)– ValveLinkValveLink®® thinks physical devices are attached thinks physical devices are attached
Accurate virtual device simulation (*100%)Accurate virtual device simulation (*100%)– Devices provide correct resultsDevices provide correct results
Application meets the needs of Fisher Application meets the needs of Fisher ControlsControls (100%)
Recommendations for Further Recommendations for Further WorkWork
Serialization for saving configured Serialization for saving configured devices/simulationsdevices/simulations
Multiplexer network capabilitiesMultiplexer network capabilities More detailed device logicMore detailed device logic
-Virtual diagnostic capabilities-Virtual diagnostic capabilities-Mux scanning-Mux scanning
Future device typesFuture device types
Human BudgetHuman Budget
0
100
200
300
400
500
600
Pro
ject
Pla
n
Res
earc
h
Pos
ter
Des
ign
Rep
ort:
Impl
emen
t Pro
ject
Des
ign:
Fin
al R
epor
t:
Tota
l
Hours
Estimated Actual
Financial BudgetFinancial Budget
Item Estimated ActualValve Link Software* $3,000 $0
Laptop* $1,000 $0Poster $50 $55
Programming Books $100 $0Visual C++ $99 $0
Totals $4,249 $55
Costs
Lessons LearnedLessons Learned
Start research as early as possibleStart research as early as possibleTry to inflate time estimatesTry to inflate time estimatesPrioritize tasksPrioritize tasksMaintain contact with the clientMaintain contact with the clientTake more time to familiarize ourselves Take more time to familiarize ourselves
with Visual C++with Visual C++
Developed SkillsDeveloped Skills
Technical SkillsTechnical Skills-Visual C++ (coding skills improved immensely) -Visual C++ (coding skills improved immensely)
-HART protocol -HART protocol
-Serialization techniques-Serialization techniques
-Working with technical documentation-Working with technical documentation
Non-Technical SkillsNon-Technical Skills-Interaction with professional clients-Interaction with professional clients
-Team meeting utilization-Team meeting utilization
-Documentation techniques-Documentation techniques
SummarySummary
HART COMMUNICATION
ValveLink® Software HARTSim Software
QuestionsQuestions