- #DRAGONFRAME 3.6.1 UPLOADED MANUAL#
- #DRAGONFRAME 3.6.1 UPLOADED SOFTWARE#
- #DRAGONFRAME 3.6.1 UPLOADED WINDOWS#
#DRAGONFRAME 3.6.1 UPLOADED MANUAL#
2.5 Design and Implementation Constraints 2.6 User Documentation The following documentation will be made available on completion of the work: A user manual describing the installation and operation of the application will be provided.
#DRAGONFRAME 3.6.1 UPLOADED WINDOWS#
The web-application will be hosted on a Windows machine, and will communicate with the LMC using an RPC-based mechanism like protobuf. The web-client will communicate with the server over the web through http and ftp protocols. 2.4 Operating Environment In the first instance the operating environment will be Firefox. The login determines whether the user is an administrator or viewer.
#DRAGONFRAME 3.6.1 UPLOADED SOFTWARE#
Figure 1: System description of the LFAA Local Monitoring and Control 2.2 Product Functions The main function of the software product is to allow a user to: communicate with the TPM monitor, control and manage the TPM log data from the sensors on the TPM plot data from the sensors on the TPM store archival data from the sensors on the TPM 2.3 User Classes and Characteristics There will be two kinds of user classes: Viewers with the capability of plotting sensor data available from the TPMĥ Administrators, who in addition to the above will have the capability of writing/editing register values on the TPM Authentication occurs through connecting to the LMC server, which is the first screen that the user is presented with. The UI will run on a cross-platform web browser, in the first instance being Firefox. This is shown in Figure 1.Ĥ The communication between the web-based UI and the LMC will occur through Remote Call Procedures (RPC). Overall Description 2.1 Product Perspective The software product described here is a web-based User Interface (UI) which communicates with the Local Monitoring and Control (LMC) layer in the LFAA, which is situated on the LMC server. 1.3 Product Scope The top-level requirements of the product are as follows (with further details in the subsequent sections): Communication with the Tile-Processing Modules Monitoring and Management of the Tile-Processing Modules Control of the firmware functionality of the Tile-Processing Modules Visualisation of control/sensor data from the Tile-Processing Modules (excluding the datastream) Data Logging/Historical archiving of control/sensor data from the Tile-Processing Modules (excluding the data-stream) 2. It is also (recommended) that this document is circulated to the wider SKA community such that other consortia developing Monitoring, Control and Management systems could use it as a reference. It is also meant for the LFAA Local Monitoring and Control Work Package leader, Signal Processing Work Package Leader, Project Engineer and Consortium Leader. 1.2 Intended Audience and Reading Suggestions This document is meant as a reference document for the developers at the supplier as well as the project managers of the software product. It lays out a plan of how the software environment is to be implemented including the platforms on which the software will run as well as the main functionality of the software. It is intended to act as a reference document between the Supplier and the AADC consortium regarding the software infrastructure for managing the TPM(s) and the telescope as a whole. The scope of the prototype is to communicate with and control the tile-processing modules (TPM) which will be used to carry out the digital signal processing (DSP) tasks for the LFAA. Introduction 1.1 Purpose This document specifies the requirements for the development of a prototype Monitoring and Control system for the Low-Frequency aperture array (LFAA). 3 Hardware Interfaces Software Interfaces Communications Interfaces Functional Requirements User Class 1: Administrator User Class 2: Viewer Other Requirements Scenarios Delivery Milestones Acceptance Testing Criteria Service Level Requirements Key Performance Indicators Contract Duration.10 Appendix A: Screen shots.11 A.1: Dashboard screen A.2: TPM Signal Display A.3: Antenna Signal Display A.4 RF and Firmware Settings A.5: TPM Settings Appendix B: Use Cases.13 Appendix C: Remote Procedure Calls.15ģ 1. 3 Assumptions and Dependencies External Interface Requirements User Interfaces. 2 Operating Environment Design and Implementation Constraints User Documentation. 1 Intended Audience and Reading Suggestions Product Scope Overall Description Product Perspective Product Functions User Classes and Characteristics. 1 Specification of Requirements Software for Low-Frequency Aperture Array Management System PrototypeĢ Table of Contents Table of Contents.