1 / 172

Scientific Computer System Admin and Operator Training

Scientific Computer System Admin and Operator Training. SCS Version 4.5.x for Windows 2003/XP January, 2011 Tom Stepka John Katebini Omar Ayub NOAA OMAO Systems Development Section. Table of Contents. Syllabus 4-7 Introduction 8-29 Networking basics 30-36 Installation 37-58

jun
Télécharger la présentation

Scientific Computer System Admin and Operator Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Scientific Computer System Admin and Operator Training SCS Version 4.5.x for Windows 2003/XP January, 2011 Tom Stepka John Katebini Omar Ayub NOAA OMAO Systems Development Section SCS Training Presentation

  2. Table of Contents • Syllabus 4-7 • Introduction 8-29 • Networking basics 30-36 • Installation 37-58 • Connect a sensor 59-66 • Simulate a sensor 67-68 • Sensor Types 69-81 SCS Training Presentation

  3. Table of Contents (cont.) • SCS Menu Introduction 82-96 • Configuration File Editor 91-123 • SCS Menu Continued 124-148 • SCS 4.0 New Features 149-154 SCS Training Presentation

  4. SCS History Primary Functions Data Flow and End User Products SCS Architecture Windows skills Network skills SCS Config File Switch to Client Serial interfaces Simulating Data Interfacing sensors SCS Configuration Database Design Configuration File Editor (CFE) Scientific Computer System (SCS) Training – Day 1 SCS Training Presentation

  5. Quick Review SCS Menu overview Start and Stop ACQ Real Time Displays Real Time Plots Real Time Gauges Event Logging Intro Holiday Party (Afternoon) Scientific Computer System (SCS) Training – Day 2 SCS Training Presentation

  6. Event Logging Continued Event Logging Labs Beta-Event Builder OEL DataMon Geotrack Scientific Computer System (SCS) Training – Day 3 SCS Training Presentation

  7. Scientific Computer System(SCS) Training - Day 4 • Newspaper Plots (post processing) • Editing/viewing Data Files • Station Builder • Advanced Event Logging • Main Event Lab • CFE Sensor Capabilities To HQ • Importance of Meta-Data • Data Submission Programs • Ship Tracker • NODC + NODC website • SAMOS + SAMOS website • AOML • R2R SCS Training Presentation

  8. Scientific Computer System(SCS) Training - Day 5 • Other SCS Software • SCS Mail Message • Display Sensor Data • Installing SCS – Server and Client • Full Data Base Logging • Database Backups • Database For Configurations Only • Final Test • Test Review SCS Training Presentation

  9. SCS History • SCS first designed in 1986 • First operational system –April 1989 (Command-line/FORTRAN on MicroVAX II) • Graphical User Interface (GUI) front end developed in 1993 (X-Windows/MOTIF on VAXStation 400) • Software re-written for Intel PC and Windows MFC and C/C++ in 1997 (SCS v 3). • Windows 2003/XP (SCS 4) version released Jan 06 • Windows 2008/XP/SQL Server 2008 Express (SCS 4.4) SCS Training Presentation

  10. SCS Background • Current version is 4.4.1, supported by John Katebini , Thomas Stepka of NOAA’s Marine and Aviation Operations (NMAO), Electronics Engineering Branch, Systems Development Group • Contractor Support Phil Zubaly, Omar Ayub SCS Training Presentation

  11. SCS Advantages • Simple to use • Easy to manage • Fast and easy to configure • Stability (in use for > 10 yrs) • Easy user-access to data • Data written to standard media products (i.e. CD-ROM, DVD, etc…) • Can be configured to use on any vessel without the need for new software modules SCS Training Presentation

  12. SCS Primary Functions • Acquire real-time sensor data • Log raw data to disk in several formats • Monitor incoming data for errors • Display real time data in text and graphical formats at any computer on the ship’s LAN. • Collect specific data through the use or user-defined “Events” • QA Post Processing of the ASCII data set • Provide End of Cruise data products SCS Training Presentation

  13. Primary End-User Products • Sensor data collected during the cruise in four formats • Raw files: ASCII sensor messages from the shipboard sensors (*.RAW) • Event Log data files: user configurable (*.ELG) • Compress files: a subset of the Raw files in comma separate format (*.ACO) • Lab files: a subset of Compress files, in a format importable into MATLAB. SCS Training Presentation

  14. Primary End-User Products(continued) • Displays of Sensor Data • Time Series Plots • XY Plots • Gauges • Trackline Plots • Textual Displays • Displays are user defined – saved in “Template Files” SCS Training Presentation

  15. Oceanographic Sensors Meteorological Sensors Time Series Plots Trackline Plots Trawling/ Fish Sensors Data Logging Quality Monitoring Navigation Sensors Data Products SCS Overview INPUT OUTPUT Real-Time Displays SCS Training Presentation

  16. SCS ArchitectureOverview • A SCS server running Windows Server 2003/XP. • Shipboard sensors sending data to the server via serial COM ports or network sockets. • Client computers running Windows 2003/XP connected to the SCS Server via network sockets SCS Training Presentation

  17. SCS ArchitectureClient / Server Primary Applications run on SCS server (Sensor Configuration, ACQ, Data Logger, Event Logger) • User access via remote PCs using LAN to generate displays and run SCS Events • Remotely-run apps use own resources (memory, CPU, etc…) SCS Training Presentation

  18. Real Time Displays Navigation Sensors Meteorological Sensors Real Time Plots Oceanographic Sensors Acquisition Real-time Memory Share RealTime Track Lines Fisheries Sensors Send SCS Data Data Logging/DB Quality Checks Configuration File Event Logging SCS ArchitectureClient-Server Data Flow SCS Training Presentation

  19. Devices, Parents, Children • Device (serial com port or TCP socket on ship network) • Devices own Parents – several Parent messages can arrive on the same device • Messages are divided into fields, each containing one sensor measurement. (Datafields) SCS Training Presentation

  20. SCS ArchitectureOther Shipboard Servers On NOAA ships the SCS Server is paired with a SCS Backup Server and two Active Directory domain controllers. SCS and a multi-port serial adapter is installed on the each system so that either server may acquire data. SCS Training Presentation

  21. SCS ArchitectureData Backup and Distribution • The SCS architecture includes means to backup and distribute collected data • CD-Writers are the primary distribution method • Tape drives and SNAP appliances serve as backup for data. • Dual Data Logging across the Network SCS Training Presentation

  22. SCS ArchitectureSerial Ports • SCS is designed to accept sensor data via serial ports. • Utilize Composite serial interfaces • Utilize USB serial Concentrators SCS Training Presentation

  23. SCS Hardware – Serial Expanders • Digi Acceleport PCI Serial Card • Data collected directly into ACQ workstation • Expandable to 64 RJ45 ports • Simple to set up • No known failures to date • Currently used on the Oregon II and Gordon Gunter • External USB Edgeport 8- port Serial I/O Device • Adds up to 8 additional ports via USB • An economic solutions to vessels needing to interface few physical sensors • Has shown to be reliable based on performance with the FSCS system SCS Training Presentation

  24. SCS Architecture Networking • Shipboard network is currently 100/1000 based Ethernet • The3 -COM 12 Port SuperStack 3300 Ethernet Switch is most commonly used for networking on NOAA vessels • Can use any 100/1000 switches available on the market for new installations • The server(s) and client machines must have a 100/1000 Ethernet card installed for network connectivity SCS Training Presentation

  25. Acceleport Gotcha • Do not unplug Aceleport box if computer is powered on. • If you power on server when Acceleport box is not plugged into PCI card, windows will boot partially and then go back to the beginning over and over and over... SCS Training Presentation

  26. SCS Architecture Minimum Requirements • The minimum requirements for an SCS server are • 2 Ghz Pentium 4 • Windows Server 2003 • 20 GB C drive, 50-100 GB data drive • 1GB of RAM • 100 Mb Ethernet NIC • A serial I/O device capable of handling all required sensors • The minimum requirements for a remote client are • 1GB Mhz Pentium PC • Windows 2003 / Windows XP or higher to avoid DLL conflicts • 40 GB hard drive • 100/1000 Ethernet NIC SCS Training Presentation

  27. SCS ArchitectureDirectory Trees • There are four directory trees on any default SCS server installation: Exe40, Ship40, GIS40 and Datalog40. • All folders are located inside an Installation Directory (defaults to C:\SCS4.0-Server, can be changed during the install) • Recommend changing installation folder to D: drive and naming folder with version for consistency • D:\ SCS4.0.vv-Server • These folder may be separated on different disks if required SCS Training Presentation

  28. SCS ArchitectureAllSCS Directory Tree • EXE • Main repository for all SCS binary and library files. • 3rd party tools • Shared as EXE40 SCS Training Presentation

  29. SCS ArchitectureShip Directory Tree • A root directory called SHIP40 • Under the root, subdirectories for each ship in the fleet • You can add any others you wish • Home of all files created by you and needed by SCS software (templates, sounds…) • Subdirectories of /Ship40/TestShip/ • AcqSimulatorData • Display • EventTemplates • ReportBuilderData • SendSCS • SimulatorRawData • Sounds • Templates • Main ship is shared as SHIP40 SCS Training Presentation

  30. SCS ArchitectureDataLog Directory Tree • The home of all data logged by SCS ACQ and the Event Logger, plus other data. • You may specify a secondary Datalog2 directory, all recorded data will be written to both locations. • Subdirectories: • RAW data files: Messages from sensors. • EventData: Event Logger data files • SavedGISTracklines: Contains older GIS shape files • Station: Stations (used in track line plots) SCS Training Presentation

  31. SCS ArchitectureDataLog Directory Tree • The logging folder is determined by the SCS Configuration file (more later). • By default all raw data is logged to that single folder. This can result in many, many files. • Option to create subdirectories and specify that a sensor’s raw data will be logged there. SCS Training Presentation

  32. Windows NetworkingTCP/IP Address • Each computer has a unique address. • Address is four numbers separated by periods: 140.90.148.33 • First three numbers are called the “domain” • All computers on a ship LAN share these • Fourth number must be unique for each computer. • You need to plan address space to ensure no two computers have the same address. SCS Training Presentation

  33. Windows NetworkingSubnet Mask • On a ship, always use 255.255.255.0 • To grossly oversimplify, “255.255.255” means “everyone on the ship has the same domain numbers”, and “0” means “last number is unique”. SCS Training Presentation

  34. Private LAN vs Public LAN • Organizations can create a LAN where IP addresses start with 10.x.y.z or 168.192.y.z They are private and cannot be seen from the outside of the organization. • NOAA: 10.48.y.z are fleet LANS. “Y” determines which ship. • OMAO Systems Development has 10.49.y.z addresses. SCS Training Presentation

  35. Private vs Public LANS • Systems Development can log into NOAA ships because they are in the same “10 space” • Outside users can log into fleet computers by using a VPN connection. SCS Training Presentation

  36. Windows NetworkingGateway • A Gateway refers to a router, a specialized computer that “knows how to contact any computer not on the ship’s LAN”. • If you try to contact an outside computer, the Ship’s network servers don’t know where it is, so they hand it off to the Gateway. SCS Training Presentation

  37. TCP Sockets • Number from 1-32K • Each network app has its own socket number. • Certain sockets are “well known”, understood by everyone to be reserved • 25 Mail protocol • 80 HTTP • 21 FTP • Use of other sockets must be coordinated among all apps operating on a LAN (Eg SCS ACQ socket 505.) SCS Training Presentation

  38. Windows NetworkingDNS Servers • DNS = “Domain Name Service” • Internet addresses like www.google.com must be translated to an IP address (216.239.39.99) before the Google site can be contacted. • DNS Servers perform this translation • They also allow ship computers to contact each other by name. SCS Training Presentation

  39. Windows NetworkingRudimentary Comms PING command says hello to another computer and asks it to say hello back. Most basic way to test connectivity. At the DOS command prompt: >ping www.google.com >ping 216.239.39.99 SCS Training Presentation

  40. Windows NetworkingRudimentary Comms • NSLOOKUP command: translates an internet URL to an IP address, or vice versa. • At the DOS command prompt: C:>nslookup www.google.com • Response from DNS Server: Address = 216.239.39.99 SCS Training Presentation

  41. Windows NetworkingRudimentary Comms • Q: What is my IP address? • A: at DOS command prompt, • >ipconfig provides basic info • >ipconfig / all provides additional info SCS Training Presentation

  42. Windows NetworkingTwo useful terms • To refer to your machine: • Use hostname “localhost”, or • Use IP address 127.0.0.1 • Either of these refer to this machine, no matter what its host name or IP address may be. • “nslookup localhost” command shows your IP address. SCS Training Presentation

  43. Sharing Folders • SCS Server shares four folders for use by remote clients. • Shares are named GIS40, EXE40, LOG40 and SHIP40. • Shares are created automatically during SCS Server installation. SCS Training Presentation

  44. Managing Shares • GUI and DOS command line varieties • GUI way: Start Button, Run… • Enter FSMGMT.MSC • Shows summary of all shared folders on your machine. • You can stop sharing or start sharing a new folder. SCS Training Presentation

  45. Managing Shares • From the Windows Command Prompt: • “net use” command shows all mapped drives on your machine (ie accessing shared folders on other machines) • “net share” command shows all folders shared by your machine with others. SCS Training Presentation

  46. SHIP40 folder vs SHIP40 share • The SHIP40 folder contains folders for each ship in fleet, eg “Oscar Dyson” • When we refer to the “Ship directory” we mean the “Oscar Dyson” folder not the SHIP40 folder. • The Oscar Dyson folder is shared to remote SCS clients as the SHIP40 share. SCS Training Presentation

  47. SQL Database • SQL = “Structured Query Language • World standard for setting up, reading from and writing to, SQL databases • “Relational” Database is made up of many tables that are connected through relations. SCS Training Presentation

  48. SCS DatabaseSensor Configuration • Created during initial SCS install • Contains all Sensor Configuration (no more “SENSOR.SCF”) • CFE completely rewritten to talk to database. • Sensor configuration now includes sensor metadata and photos of sensors in place. SCS Training Presentation

  49. SCS DatabaseLogged Data • Raw messages written to database. • RAW files still available. • Operation Event Logger writes to database. • Legacy Event Logger still available. SCS Training Presentation

  50. VerifySCS40.CFG Configuration file • Resides in the C: drive’s root directory. • Contains a list of “environmental variables” and their definitions. • Environmental variables originated in the UNIX OS. The idea was copied into DOS and then to windows. • Allows SCS to define “logical directories” • Can redirect software to other directories without modifying the software itself • Use EXE40\ScsConfigurationFileEditor.exe to view and change file • Do not use NotePad !!! SCS Training Presentation

More Related