all | frequencies |
|
|
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|---|---|
manuals | photos | labels |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 3 |
|
programmers manual | Users Manual | 453.74 KiB | ||||
1 2 3 |
|
users and installation guide | Users Manual | 3.20 MiB | ||||
1 2 3 |
|
photos | Internal Photos | 450.00 KiB | ||||
1 2 3 |
|
photos | External Photos | 211.54 KiB | ||||
1 2 3 |
|
label artwork and placement photos | ID Label/Location Info | 264.07 KiB | February 06 2000 | |||
1 2 3 |
|
table of contents and label | ID Label/Location Info | 9.45 KiB | ||||
1 2 3 | Test Setup Photos | May 01 2002 | ||||||
1 2 3 |
|
covering letter including new part numbers for the certificate | Cover Letter(s) | 24.47 KiB | ||||
1 2 3 | Test Report | |||||||
1 2 3 |
|
schematics adn block diagrams | Schematics | 2.98 MiB | ||||
1 2 3 | Test Report | May 01 2002 | ||||||
1 2 3 | Test Report | May 01 2002 | ||||||
1 2 3 |
|
PN Change request | Cover Letter(s) | 6.86 KiB | March 10 2000 | |||
1 2 3 |
|
attestation statement | Attestation Statements | 5.70 KiB | ||||
1 2 3 |
|
circuit descriptions | Block Diagram | 12.22 KiB | ||||
1 2 3 |
|
cover letter | Cover Letter(s) | 30.82 KiB | ||||
1 2 3 |
|
model and fcc id change request | Cover Letter(s) | 6.18 KiB | February 06 2000 | |||
1 2 3 |
|
operational data | Operational Description | 9.39 KiB | ||||
1 2 3 | Test Report | |||||||
1 2 3 | Attestation Statements | |||||||
1 2 3 |
|
schematics | Schematics | 124.30 KiB | ||||
1 2 3 | Test Report | |||||||
1 2 3 | Test Report | |||||||
1 2 3 | Test Report | |||||||
1 2 3 |
|
tuneup info | Parts List/Tune Up Info | 51.52 KiB |
1 2 3 | programmers manual | Users Manual | 453.74 KiB |
ToolBox for MOSCAD RTUs For Programming ToolBox Version 7.51 Motorola Inc.1999 All rights reserved System Overview 68P02956C45-A COMMERCIAL WARRANTY (STANDARD) Motorola radio communications products are warranted to be free from defects in material and workmanship for a period of ONE (1) YEAR, (except for crystals and channel elements which are warranted for a period of ten (10) years), from the date of shipment. Parts, including crystals and channel elements, will be replaced free of charge for the full warranty period but the labor to replace defective parts will only be provided for one Hundred-Twenty (120) days from the date of shipment. Thereafter purchaser must pay for the labor involved in repairing the product or replacing the parts at the prevailing rates together with any transportation charges to or from the place where warranty service is provided. This express warranty is extended by Motorola Communications and Electronics Inc., 1301 E. Algonquin Road, Schaumburg, Illinois 60196, to the original purchaser only, and only to those purchasing for purpose of leasing or solely for commercial, industrial, or governmental use. THIS WARRANTY IS GIVEN IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED WHICH ARE SPECIFICALLY EXCLUDED, INCLUDING WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MOTOROLA BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES TO THE FULL EXTENT SUCH MAY BE DISCLAIMED BY LAW. In the event of a defect, malfunction or failure to conform to specifications established by seller, or if appropriate, to specifications accepted by Seller in writing, during the period shown, Motorola, at its option, will either repair or replace the product or refund the purchase price thereof, and such action on the part of Motorola shall be the full extent of Motorolas liability hereunder. This warranty is void if:
a. b. c. This warranty extends only to individual products, batteries are excluded, but carry their own separate limited warranty. Because each radio system is unique, Motorola disclaims liability for range, coverage, or operation of the system as a whole under this warranty except by a separate written agreement signed by an officer of Motorola. Non-Motorola manufactured products are excluded from this warranty, but subject to the warranty provided by their manufacturers, a copy of which will be supplied to you on specific written request. In order to obtain performance of this warranty, purchaser must contact its Motorola salesperson or Motorola at the address first above shown, attention Quality Assurance Department. This warranty applies only within the United States. the product is used in other than its normal and customary manner;
the product has been subject to misuse, accident neglect or damage;
unauthorized alterations or repairs have been made, or unapproved parts used in the equipment. COMPUTER SOFTWARE COPYRIGHTS The Motorola products described in this instruction manual may include copyrighted Motorola computer programs stored in semi conductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer programs including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described in this instruction manual may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. Table of Contents GENERAL ..............................................................................................................................................................III Glossary ...........................................................................................................................................................iii Terms and Conventions....................................................................................................................................vi MOSCAD RTU And ToolBox Software Version Policy ...................................................................................vii Applicable Documentation...............................................................................................................................viii Model Complements.........................................................................................................................................ix Options.............................................................................................................................................................x Accessories.......................................................................................................................................................xi THE MOSCAD SYSTEM - OVERVIEW...................................................................................................................1 The MOSCAD System ......................................................................................................................................1 Control Center .............................................................................................................................................................. 1 Remote Terminal Unit (RTU)....................................................................................................................................... 2 Communication Processor/MODBUS (MCP-M) ......................................................................................................... 2 Communication Processor/TCP/IP (MCP-T)................................................................................................................ 2 ToolBox for MOSCAD RTUs ...........................................................................................................................3 Features and Functions ................................................................................................................................................. 3 The RTU Programming Concept .................................................................................................................................. 3 Programming Sequence ................................................................................................................................................ 4 RTU Definition............................................................................................................................................................. 4 Communication Network..................................................................................................................................6 The RTUs and the Network .......................................................................................................................................... 7 Communication Links................................................................................................................................................... 7 Communication Types .................................................................................................................................................. 7 Network Configurations ............................................................................................................................................... 8 Starting a ToolBox Application........................................................................................................................15 Entering the Password .................................................................................................................................................. 15 Changing the Session Password.................................................................................................................................... 15 THE TOOLBOX FOR MOSCAD RTUS...................................................................................................................16 Hardware and Software Requirements ............................................................................................................16 Installing ToolBox............................................................................................................................................16 Connecting ToolBox to RTU ............................................................................................................................16 A Brief Tour .....................................................................................................................................................16 The RTU ....................................................................................................................................................................... 16 Database Principles....................................................................................................................................................... 18 Programming Philosophy.............................................................................................................................................. 20 The Tools..........................................................................................................................................................22 Site Configuration (MOSCAD-L)................................................................................................................................. 23 Network Configuration ................................................................................................................................................. 25 Application Programmer .................................................................................................................................26 Database Builder........................................................................................................................................................... 28 Process Programming ................................................................................................................................................... 28 I/O Link ........................................................................................................................................................................ 29 Compiler ....................................................................................................................................................................... 30 Downloading and Monitoring....................................................................................................................................... 31 REMOTE TERMINAL UNIT......................................................................................................................................32 The RTU Hardware..........................................................................................................................................32 i CPU Module ................................................................................................................................................................. 32 I/O Modules.................................................................................................................................................................. 38 RTU Software...................................................................................................................................................38 MDLC COMMUNICATION PROTOCOL ...................................................................................................................40 Physical Layer..................................................................................................................................................41 Link Layer ........................................................................................................................................................41 Network Layer..................................................................................................................................................42 Transportation Layer .......................................................................................................................................42 Session Layer ...................................................................................................................................................42 Presentation Layer...........................................................................................................................................43 Application Layer.............................................................................................................................................43 ii General Glossary This list of terms consists of abbreviations, acronyms and specialized words used in this manual. Acronyms and Abbreviations ACK AGA ASL ASR BCD BIN CD COS CPU CPY CRC CTD CTS CTU DBB DCE DFM DOF DON DPL DPSK DSP DSR DTE DTR EGU FEP FIU FSK GND GPS HDLC HW I/O IGC/M IMP INTRAC Acknowledge American Gas Association Arithmetical Shift to Left Arithmetical Shift to Right Convert to BCD Format Convert to Binary Format Carrier Detect Change of State Central Processing Unit Copy Cyclic Redundancy Check Count Down Clear to Send Count Up Data Base Builder Data Communication Equipment Direct Frequency Modulation Delay Off Delay On Digital Private Line Differential Phase Shift Keying Digital Signal Processing Data Set Ready Data Terminal Equipment Data Ready Engineering Units Front End Processor (MCP-M, MCP-T, or FIU) Field Interface Unit Frequency Shift Keying Ground Global Positioning System High -level Data Link Communication Hardware Input/Output IBM Graphic Center for MOSCAD (old) Integrated Multiprotocol Processor Two-layer (32 bits) protocol iii JMP JSP LED LSL LSR MCP-M MCP-T MDLC MEIC MMI MODBUS MOSCAD MOSCAD-L MOVE MOVH MTE NACK N.C. N.O. NEMA OSI OVF PC PID PL PLC PPH PPS PSTN PTT RAM RET RF ROM ROR RNR RR RST RTS RTU RUNP RX SCADA SW TDPSK General Jump Jump To Subprocess Light Emitting Diode Shift to Left Shift to Right Motorola Communication Processor MODBUS Motorola Communication Processor TCP/IP MDLC Motorola Data Link Communication (Seven-layer OSI protocol) Previous generation RTU type Man Machine Interface MODICON BUS Protocol Motorola SCADA Motorola SCADA-Light Move Value Move High Multi Task Environment Negative Acknowledge Normally Closed Normally Open National Electrical Manufacturers Association (issues enclosure standards) Open System Interconnection Overflow Personal Computer Proportional Integral Derivative Private Line Programmable Logic Controller Pulse per Hour Pulse per Second Public Switching Telephone Network Push to Talk (button on radio) Random Access Memory Return Radio Frequency Read Only Memory Rotate to Right Receive, Not Ready Receive, Ready Reset Request to Send Remote Terminal Unit (can be MOSCAD or MOSCAD-L) Run Process Receive Supervisory Control and Data Acquisition Software Trunked Differential Phase Shift Keying iv General TRT TX UART UCL UDF XTAL Definitions Retentive Timer Transmit Universal Asynchronous Receiver Transmitter User Call Function Underflow Crystal Upload Load a block of data or code, from the RTU to the ToolBox Download Load a block of data or code, from the ToolBox to the RTU. v General Terms and Conventions The MOSCAD RTU is shipped in two versions, MOSCAD RTU and MOSCAD-L RTU. Most of the features described in the MOSCAD documentation are common to MOSCAD and MOSCAD-L. Throughout the documentation the terms RTU and MOSCAD refer to the generic system. Differences are indicated by specific references to MOSCAD and MOSCAD-L. RTUs and MCP/Ms are sites. In the MOSCAD documentation, references to site generally mean RTU and vice-versa. The MCP/M is a central adapter between SCADA and the field. The MOSCAD ToolBox package consists of several Windows 95/NT applications, such as Site Configuration and Application Programmer. Throughout the MOSCAD documentation the application names are printed in initial capitals. Some features are valid from a certain version of Programming ToolBox. as specified using the Va.b notation. See MOSCAD RTU And ToolBox Software Version Policy. vi General MOSCAD RTU And ToolBox Software Version Policy The version numbers of the Programming ToolBox and MOSCAD RTU system software are updated according to additional features and improvements. Compatibility (at source level) between the Programming ToolBox and the MOSCAD RTU is assured only if the version number of the Programming ToolBox Software is later than the version number of the MOSCAD RTU system software. A version number is composed of two numbers, as in the following example: V1.61. The one-digit number to the left of the decimal point describes a major modification of the software, while the two-digit number to the right of the decimal point describes a minor modification. In this manual, some headings of major subjects are marked by the following annotation:
Va.b. For example, V1.61 indicates that the marked subject is supported by an RTU whose MOSCAD software version number is at least 1.61. This numbering convention applies to MOSCAD-L as well, except for the versions below:
If no version number is specified, then that feature is supported by all versions of MOSCAD and MOSCAD-L. MOSCAD-L Version Supported by ToolBox Version 1.0x 2.0x 2.40 5.01 6.00 6.50 vii Applicable Documentation General The MOSCAD system includes the following manuals:
ToolBox for MOSCAD RTUs, MOSCAD Programming ToolBox - Overview, Motorola publication no. 68P02956C45 ToolBox for MOSCAD RTUs, MOSCAD Programming ToolBox - System Setup &
Diagnostic Tools, Motorola publication no. 68P02956C50 ToolBox for MOSCAD RTUs, MOSCAD Programming ToolBox - Application Programmer, Motorola publication no. 68P02956C55 ToolBox for MOSCAD RTUs, MOSCAD Programming ToolBox - Third Party Protocols Support, Modbus and Allen Bradley, Motorola publication no. 68P02956C70 ToolBox for MOSCAD RTUs, MOSCAD Programming ToolBox C Toolkit, Motorola publication no. 68P02956C75 ToolBox for MOSCAD RTUs, MOSCAD Programming ToolBox - AGA8 Gas Flow Calculations, Motorola publication no. 68P02957C10 MOSCAD RTU Service manual, Motorola publication no. 68P02991G90 MOSCAD RTU Owner's manual, Motorola publication no. 68P02994G10 MCP/M Users Manual, Motorola publication no. 68P02945C05-0. viii General Model Complements F2316 MOSCAD Programming ToolBox FVN4126 Program Software Package on CD-ROM + Manuals FLN6457 RS232 Terminal Adapter Cable + Adapters ix General Options V377 Third Party Protocols FVN4119 Third Party Protocols V378 AC Analyzer Toolkit FVN 4335 AC Analyzer Toolkit V284 AGA8 Gas Flow Calculations FVN 4334 AGA8 Gas Flow Calculations V212 Master Key Diskette FVN 4396 Master Key Diskette V385 X.25 option for ToolBox FVN 4730 X.25 option for ToolBox V204 MDLC over IP option for ToolBox FVN 4782 MDLC over IP option for ToolBox x General Accessories FVN1710 Upgrade ToolBox FVN4126 Program Software Package on CD-ROM + Manuals FVN4334 AGA8 Gas Flow Calculations + Manual FVN4119 Third Party Protocols FVN4335 AC Analyzer Toolkit FVN4396 Master Key Diskette FLN2391 C Toolkit Package + Manual xi The MOSCAD System - Overview MOSCAD Programming ToolBox is a package of computer programs that builds sophisticated distributed SCADA (Supervisory Control and Data Acquisition) systems for a wide range of applications. The MOSCAD (Motorola SCADA) system consists of remote terminal units (RTU) and one or more computerized control centers, connected to a communication network via the Communication Processor/TCP/IP (MCP-T) or the Communication Processor/MODBUS (MCP-M). The Programming ToolBox software package runs on a Pentium 100 (or more powerful) computer. The main function of the Programming ToolBox is to define and maintain the MOSCAD system according to user needs and requirements. The Programming ToolBox also enables the engineer to program/download the application program to be executed in the RTU and to perform debugging in each RTU, using a symbolic (graphic) debugging tool. The Programming ToolBox may be operated either locally by direct connection to the selected units computer port, or remotely, by connection to a computer port of any other RTU in the system (MCP-M, MCP-T, or RTU) via the system communication network. By connecting the Programming ToolBox to a computer port of one of the RTUs, MCP-Ms, or MCP-Ts in the system, you can program or service that specific RTU or any other RTU in the system. The MOSCAD System The entire control system is comprised of the SCADA central computer as a master station, communicating with RTUs over various communication links, such as conventional radio, trunked radio, microwave, wireline, or dial system (telephone). The communication system is used for transmitting alarms, status information, telemetric readings, calculated data, diagnostics, and error logging information from the RTUs to the central facility computer and vice versa. It is also used for downloading, monitoring, and debugging the application program at the site. The system can be relatively simple, comprising several RTUs and a control center, or a more complicated hierarchical system, where several sub-centrals communicate with lower, parallel and higher hierarchies. The RTUs may also communicate with each other and/or with any other hierarchy in the system. Control Center The control center computer, with the user interface, provides the user with full graphic control of the RTUs operation, including database and parameter changes, and on-line application monitoring for the system engineer. The central computer and MCP-M communicate using the MODBUS protocol; MCP-T uses the TCP/IP protocol. 1 The MOSCAD System - Overview One of the functions of the control center is to exchange data with the RTUs. It may interrogate the RTUs for any portion of their database. Multiple interrogation
(polling) cycles operate with different priorities and by different trigger mechanisms
(time or events). Remote Terminal Unit (RTU) The RTU is a smart modular unit designed to operate as a stand-alone controller or as part of a system having any number of RTUs, control centers, and sub-centrals connected through a communication network with any number of links and nodes. The RTU is configured and loaded with the appropriate application using the Programming ToolBox. The RTU is a microprocessor-based unit, which consists of a CPU module and various I/O and communication modules. The very wide range of I/O and communication modules makes the MOSCAD system flexible to satisfy any application requirements. MOSCAD-L, on the other hand, is a lighter version with a limited number of I/O modules and fewer features. The MCP-M and the RTUs communicate using the MDLC protocol, based on the seven layers of the OSI (Open Systems Interconnection) model published by ISO, and adapted for SCADA communications. The protocol provides network support and multiple logical channels per physical port, enabling simultaneous central-to-RTU and RTU-to-RTU sessions. It also enables each RTU to simultaneously run several communication sessions, such as data exchange, on-line monitoring, diagnostics, etc. The RTU is discussed in more detail later in this manual. For technical information, consult the Owners manual and the Service manual. Note that throughout the ToolBox documentation, the terms RTU and unit are used interchangeably. Communication Processor/MODBUS (MCP-M) The MCP-M is an intelligent, intermediary unit that ensures communications between the control center and the RTUs. Its pre-loaded application and database allow it to perform tasks independently, at times when the control center is not active. The MCP-
M application and database are dedicated to collecting data from the field and performing scheduling tasks. The MCP-M is installed in the control center and does not require any further programming: the user only customizes the unit by setting parameters. It can be configured using a ToolBox of its own, which differs from the ToolBox for RTUs covered in this manual. The communication processor does not have independent I/O capabilities. Any data collection and assessment needs that may arise in the control center premises are met by an additional RTU that is connected to the network like any remote terminal on the field. 2 The MOSCAD System - Overview Communication Processor/TCP/IP (MCP-T) The MCP-T replaces the MCP-M where only a router that converts TCP/IP (over Ethernet) to MDLC and vice versa, is needed. Unlike MCP-M, it does not have a database or any control capabilities. ToolBox for MOSCAD RTUs This section is a brief review of Programming ToolBox, the software package used to configure an RTU system and to build an application. Features and Functions The following are the main features of the Programming ToolBox:
Configuring the RTU sites, configuring the network, building and maintaining the application database and flow Preparing project documentation for the user Automatically creating a central file to be used later during RTU database creation in the MCP-M. Performing the following functions on any RTU either via local connection or via the communication network:
Downloading and uploading the site configuration and related data Downloading the application and the network configuration Downloading and uploading the compressed source Downloading C blocks which are run by the application Downloading the phone book Downloading the third-party protocol Real-time symbolic (graphic) monitoring and debugging of the application (both database and process) Updating the time and the date in RTU sites Testing all hardware modules, including software calibration of analog inputs and outputs Testing radio channels Retrieving time-tagged events (of very high resolution) logged in the RTUs Synchronizing the system clock according to MCP-Ms or FIUs time Retrieving errors logged in the RTUs (hardware or software malfunctions) Capturing the data packets on the communication links and analyzing the seven layers of the MDLC protocol System software diagnostics by object entity names The RTU Programming Concept The various circles illustrated below describe the RTU in layers. The first layer is the RTU hardware that is the base for the system software and application (including configuration) software. When the application software runs, the RTU database is updated. 3 The MOSCAD System - Overview The following figure shows different ways of accessing and modifying each of the RTU layers, using the Programming ToolBox:
Locally by direct connection to the RTU Remotely via the communication network Remote Programming RTU or MCP/M Download/Upload/Monitor Download/Monitor Diagnostics/Debugging Diagnostics Remote Programming CONTROL CENTER PROGRAMMING TOOL BOX Local Programming PROGRAMMING TOOL BOX Programming Sequence APPLICATION DATA BASE APPLICATION SOFTWARE SYSTEM SOFTWARE RTU HARDWARE
(CPU, COMM, I/O MODULES) The definition of the RTU application allows the system engineer to build a database as a set of tables. The tables used for the RTU database definition are the basis for process programming, I/O link definition, automatic central database definition, real-
time monitoring of the RTUs operation, etc. Once the database is built, the RTU application is created using the symbolic Motorola Advanced Ladder Diagram Language. These symbolic definitions are later used for monitoring and debugging. The necessary RTU application documentation is automatically produced, including automatic insertion of notes into the produced documents. After downloading the application to the RTU, the control program of the terminal controls the RTU run-time operations. The Programming ToolBox terminal then allows the system engineer to perform any required operation. RTU Definition The RTU definition is carried out in three stages, stored as corresponding sections in the RTU:
Site configuration - defining the I/O modules mounted on the RTU, the units ports, and the site address. Network configuration - for defining the communications network structure. Application program - building the application database and flow. 4 The MOSCAD System - Overview Site Configuration The MOSCAD system operates with a very wide range of I/O modules and interface communication boards which satisfy any application requirements. The site configuration includes the definition of:
The I/O modules mounted on the RTU and their location in the various racks The ports of the RTU and their parameters Site ID (logical address) and system address. Since several RTUs in the system usually have the same configuration (except for the logical address), you save the configuration to a file. Then, you can download the same configuration to different RTUs, adding only their logical address and system address. Once the configuration is downloaded to the site, it is ready to receive the user application program. The site configuration must be defined and downloaded to the RTU before downloading the application. The file created by Site Configuration is later used by Application Programmer during I/O Link definition function (I/O assignment). Full details can be found in the Application Programmer manual. Network Configuration The Network Configuration application is designed to define the communication nodes in the network. The program determines the network structure - there is no need to define all RTUs, only the nodes in the network. The MDLC protocol uses these definitions for the automatic routing of the packets through the network. Network configuration is needed only in MOSCAD systems that use more than one communication link. A simple network, such as one MCP-M connected to one communication link, does not require network configuration. Like site configuration, the network configuration parameters can be saved to a file. These parameters can be downloaded using Network Configuration or can be automatically loaded into the RTUs with the application. During application loading, the user is asked to provide the network configuration name, the site ID, and one link ID of the destination RTU. The same network configuration file is used for all the sites in the system and may also be used in other systems (with the same structure). Note: The network configuration must be loaded to all sites in the system (including site nodes) to enable each site to route the packets through the network. 5 The MOSCAD System - Overview RTU Application The RTU application is the control process to be executed by the remote terminal. The application definition consists of the following:
RTU database The process to be performed by the RTU (in the form of rungs, using the Motorola Ladder Diagram Language and C functions) The connections between the database and the various inputs and outputs of the I/O modules (I/O link). The I/O link portion of the RTU application is based on the definition of the RTU I/O modules as determined in the site configuration. The RTU database is divided into reserved variables or constants, retrieved from a wide bank of system information (such as functional variables, reserved flags or temporary buffers), and user variables or constants, arranged according to various data types (such as discrete inputs/outputs, value inputs/outputs, timers, parameters, integer/real values, etc.). User variables, in most cases, represent the actual inputs/outputs from/to the outside world. They are designed to monitor and control the user devices connected to the appropriate RTUs. They may also be used to represent internal inputs/outputs for intermediate results and time elements, or to perform various calculations. The application database is built as a set of tables, where tables define a group of devices. Each row defines a separate device, and each column contains device-
specific data. The table entries are assigned user-significant names, such as PUMP1. During program execution, the process continuously updates the database according to the following:
RTU physical inputs/outputs incoming information Internal data stored in the RTU memory Data received via the communication channel and the communication ports. Downloading The downloading to the RTU is performed in the following order:
RTU application (and/or network configuration) according to the configuration Site configuration definition. Additional optional blocks, such as: Phone book, C blocks, special drivers
(MODBUS, AGA8, DNP3, etc.) Communication Network The MOSCAD system network consists of RTUs communicating with one or more computerized control centers and/or with other RTUs. Each control center is connected to the communication network via the MCP-M or MCP-T. The system can be relatively simple, comprising several RTUs and one control center. It can be modularly expanded to a more hierarchical system, where several sub-
6 The MOSCAD System - Overview systems (comprising intelligent RTUs and/or sub-centrals controlling their peripheral RTUs) communicate with a central computer. The communication network is flexible, enabling each RTU to communicate with hierarchies above it (RTU-to-central), parallel to it (RTU-to-RTU), under it (another RTU), and also relaying messages through it (when the RTU serves as a communication node). While the communication protocol allows for a complex hierarchical system structure, it does not make it complicated. This is because most of the communication interactions are transparent to the user, except in those cases where the communication is to be defined by the ladder application. In such cases, you should perform simple programming operations to configure the required application. The RTUs and the Network Each RTU may be configured to serve as a far-end terminal or as a regional center. The RTU may function as a regional center either by definition or only after loss of communication with the central. It also can act as a communication node (an interconnection point between two or more different links) while performing its other tasks. The RTU network uses the MDLC protocol, which incorporates all seven layers of the OSI model adapted for SCADA. It supports multiple logical channels per physical port, enabling simultaneous central-to-RTU and RTU-to-RTU sessions. It also enables each RTU to simultaneously run several kinds of communication applications, such as reporting alarms by contention, on-line monitoring, performing diagnostics checks, etc. The MDLC protocol is discussed later in this manual. The Programming ToolBox may perform monitoring, modification, diagnostics, error logging, etc., on any RTU in the system from any RS232 port in the system, configured as either RS232 Local Computer port or RTU-to-RTU RS232 (RS-link1 RS-link19). Communication Links The system may support a network comprised of a nearly unlimited number of links. The RTU supports a variety of communication media and baud rates, as detailed below:
Through the radio/wireline communication port:
Direct FM (DFM) modem on conventional radio, up to 4800 bps FSK modem on conventional radio, up to 2400 bps FSK modem on trunked radio, up to 2400 bps Wireline, up to 19200 bps, using external modems Wireline, up to 2400 bps, using built-in modems Dial-up, up to 2400 bps, using built-in modems External Dial-up modem Through the RS-232-C and RS-485 communication ports, up to 19200 bps. The communication via the various ports may be simultaneous. 7 The MOSCAD System - Overview The RTU operates on all radio frequencies: VHF 136-174 MHz, UHF 403-430 and 450-470 MHz, 900 MHz band, 800/900 MHz trunking and microwave. The RTU contains a circuit for monitoring activity on the radio or line communications channel. Channel access software prevents the RTU from transmitting over a busy channel. Transmission is inhibited until the channel is free. There are also several priority levels for getting to the channel when it becomes available. Communication Types The RTUs in the system are linked to a radio or wireline network as defined by the system engineer, according to user requirements. Each RTU executes its application and, simultaneously, supports the communications link (or links) defined for it, and serves as a network node, if so defined. The MOSCAD system supports up to 29 wireline links (LINE 1 to LINE 29), up to nine radio links (RADIO 1 to RADIO 9), and up to 19 local RTU-to-RTU links (RS-
link 1 to RS-link 19) that use RS232. Any of the radios may be either conventional or trunked. Computers may be connected to the ports configured as RS232 Local Computer or as local RTU-to-RTU link. For conventional radios, up to nine zones can be defined on every frequency (of the nine supported frequencies). A radio link for conventional radios is divided into zones when not all sites can communicate with each other and F1/F2 repeaters (using two frequencies) are not to be used. In this case, some RTUs will serve as Store &
Forward repeaters and the link is divided into zones. A zone is defined as a group of one or more sites that can directly communicate with each other without a Store & Forward repeater. The name of a zone is composed of the link name and the zone number. For example, for RADIO 3 zone number 1 is named RADIO 3/1, zone number 2 - RADIO 3/2 and so on. After defining the communications network, the user must define the various links used in the system as well as the RTUs that serve as nodes between the links. A network node is an RTU that functions as an interconnection point between two or more different links. A Store & Forward node, on the other hand, is a network node, which relays messages using the same physical port. Network Configurations The MOSCAD system supports both simple and complex communication networks. The following sections describe various configurations from different aspects. Simple System A simple system, comprised of a central computer, MCP-M, and RTUs connected over one communication link, is shown in the following figure:
8 The MOSCAD System - Overview Central Computer RS-232C Programming Toolbox Radio link (RADIO1) MCP/M 1 U T R 2 U T R 3 U T R Programming Toolbox The Programming ToolBox may be connected to any port of the RTU or MCP-M configured as a computer port. The radio link, named RADIO 1 in the above figure, can be a conventional radio using DFM (Direct Frequency Modulation) or FSK (Frequency Shift Keying) radio modems, or a trunked radio using FSK radio modem. The ports of the RTUs and MCP-M should be defined via Site Configuration. The logical name (in this case, RADIO 1) of the communication link is also defined. As networks involve at least two types of links, simple systems do not need to be configured as networks. Two-Link and Multiple Link Systems A two-link system utilizing a communications network, comprised of two communication links, is described in the following figure:
Central Computer RS-232C MCP/M RADIO1 2 U T R LINE1 5 U T R 1 U T R 4 U T R 3 U T R 6 U T R The MCP-M in the system illustrated above serves as a network node between link RADIO 1 and link LINE 1. Configuring the MCP-M to have access to two different links enables the MCP-M to serve as a node between these links. The MDLC protocol permits RTU-to-RTU communications without the intervention of the central computer. RTUs that are not on the same link communicate with each other via the network node (in this case, the MCP-M). 9 The MOSCAD System - Overview A multi-link system is a network that uses several link types. The following figure illustrates a system where a third link type, RADIO 3, connects an RTU to another terminal that communicates over RADIO 2. RTUs connected to the RADIO 1 link can reach RTU 7 via MCP-M and then RADIO 2. Central Computer RS-232C MCP/M RADIO1 2 U T R RADIO2 5 U T R 1 U T R 4 U T R 3 U T R 6 U T R RADIO3 RTU 7 Two-Zone System A two-zone system that uses conventional radio over a single frequency is described in the following figure:
ZONE 1 MCP/M Store & Forward RTU 9 ZONE 2 RTU 2 RTU 1 RTU 3 RTU 4 RTU 5 RTU 6 RTU 9 (Site ID = 9) is configured as a Store & Forward repeater. It performs data exchange between units that operate on the same frequency but are unable to communicate directly for reasons of path and propagation. Any RTU in zone 1 may communicate with any RTU in zone 2 via this repeater. The figure below illustrates this system schematically. In this case, RTU 9 is a network node between the RADIO 1/1 and RADIO 1/2 links. The network software 10 treats the Store & Forward node as it treats the node between line and radio: logically the links appear as two different links, but physically they share the same port. The MOSCAD System - Overview RADIO1/1 RADIO1/2 MCP/M RTU 9 1 U T R 2 U T R 3 U T R 4 U T R Using Site Configuration, the MCP-M and the RTUs in zone 1 are configured to have access to the RADIO 1/1 link. The RTUs in zone 2 are configured to have access to the RADIO 1/2 link, and RTU 9, the network node, is configured to have access to both RADIO 1/1 and RADIO 1/2 links. Using Network Configuration, RTU 9 is configured as the only node in the network. This terminal is configured to have two links, RADIO 1/1 and RADIO 1/2. Multiple Zone System The following figure illustrates a MOSCAD system spanning multiple zones. MCP/M RTU 15 ZONE 1 RTU 40 ZONE 2 RTU 2 RTU 1 RTU 3 RTU 4 RTU 5 RTU 6 The schematic representation of this system is shown below. The system assumes that the two nodes, RTU 15 and RTU 40, cannot hear each other. They communicate via the MCP-M, which is also a Store & Forward node. This system, therefore, consists of four zones and three nodes (RTU 15, RTU 40, and MCP-M). Any communication between RTUs in different zones passes through these three nodes. RADIO1/3 RTU 15 RADIO1/1 MCP/M 1 U T R RADIO1/4 RTU 40 RADIO1/2 1 U T R 11 2 U T R 2 U T R The MOSCAD System - Overview In the above situation, three nodes with their accessible (logical) links should be defined, using Network Configuration. Using Site Configuration, the RTUs in zone 1 should be configured to have access to the RADIO 1/1 link, and the RTUs in zone 2 to the RADIO 1/2 link. RTU 15 should be configured to have access to both RADIO 1/1 and RADIO 1/3 links, while RTU 40 should be configured to have access to both RADIO 1/2 and RADIO 1/4 links. The MCP-M is configured to have access to both RADIO 1/3 and RADIO 1/4 links. Assuming that the two nodes (RTU 15 and RTU 40) can hear each other, the result is a system consisting of three zones and two nodes, as shown in the following figure:
MCP/M 3
1 O I D A R RADIO1/1 RTU 15 4 U T R RTU 40 RADIO1/2 1 U T R 5 U T R 2 U T R In this case, the two nodes do not communicate through the MCP-M. Therefore, the MCP-M does not serve as a node in the system. Note that the communication between RTUs in different zones passes only through two nodes. Dual Dial Port
(MOSCAD version V3.70, MOSCAD-L version V1.00) The CPU supports two dial links at Port2 and Port3. Port2 may be connected to an external AT modem and Port3 may be connected to either an external AT modem, or to an internal modem configured at dial option. Prior to using an external modem, emulate an external terminal using a PC and any standard communication program, and set its parameters as follows:
9600 bps (for example) 8 bits no parity 1 stop bit Enter the modem telephone numbers into the MOSCAD Phone Book utility. If your telephone works either in a pulse or in a tone mode, it is recommended to add the letter P(pulse) or T (tone) in front of the telephone number. If you are using an external modem, set its configuration according to the following list. 12 The MOSCAD System - Overview Action Disable off-line echoing Enable audio messages Disable quiet mode (The status codes are sent to the terminal.) Enable all codes Enable carrier detect when a connection is established. Command ATE0 ATV1 ATQ0 ATX4 AT&C1 You may enter the commands in one string, ATE0V1Q0X4&CI&W, where &W implies saving the above parameters for the next power-up. When several RTUs are connected to the PSTN (Public Switching Telephone Network), as illustrated below, several configurations are viable as described in the examples that follow. RTU 2 INTERNALMODEM ATPORT3 EXTERNALMODEM ATPORT2 RTU 1 PSTN EXTERNALMODEM ATPORT3 RTU 3 EXTERNAL MODEMAT PORT2 INTERNAL MODEMAT PORT3 EXTERNAL MODEMAT PORT2 EXTERNAL MODEMAT PORT3 RTU 4 RTU 5 Note that in the illustrated configurations, as in all the connections over the PSTN, there is only one link ID. It is the responsibility of the software to decide which line to dial. When two lines are available, the Port 2 line has priority. 1. To communicate between RTU 1 and RTU 2:
Configure RTU 1 Port 2 as external modem. Update the RTU 2 telephone number. Any transmission from RTU 1 to RTU 2 will cause automatic dialing. As the connection is established, information will be transferred from one modem to the other. When no information is transferred for a period longer than the Hanging up an unused line by INITIATOR after... Advanced Physical Layer parameter, the line will be disconnected. 13 The MOSCAD System - Overview 2. To communicate between RTU 1 and RTU 4:
Configure RTU 1 Port 2 as external modem. Update the two RTU 4 telephone numbers. Any transmission from RTU 1 to RTU 4 will cause automatic dialing to the first number in the phone book. If the first number is busy, or there is no answer, the second number is automatically dialed. As the connection is established, information will be transferred from one modem to the other. When no information is transferred for a period longer than the Hanging up an unused line by INITIATOR after... Advanced Physical Layer parameter, the line will be disconnected. 3. To communicate between RTU 4, RTU 5, and RTU 3 simultaneously:
Configure RTU 4 Port 2 as external modem and RTU 4 Port 3 as internal modem dial-up, Auto Answer & Dial. Update the two RTU 5 telephone numbers and the RTU 3 telephone number. Any transmission from RTU 4 to RTU 5 will cause automatic dialing from the first available port (when both ports are available, Port 2 is chosen) to the first number on the list. If the first number is busy, or there is no answer, the second number is automatically dialed. As the connection is established, information will be transferred from one modem to the other. When no information is transferred for a period longer than the Hanging up an unused line by INITIATOR after... Advanced Physical Layer parameter, the line will be disconnected. Any transmission from RTU 4 to RTU 3 while RTU 4 and RTU 5 are connected, will cause automatic dialing from Port 3. If RTU 4 and RTU 5 are disconnected, then Port 2 will be selected for dialing. 14 The MOSCAD System - Overview Starting a ToolBox Application ToolBox consists of different Windows applications. Each application is activated via an icon included in the ToolBox program folder. Entering the Password When a ToolBox application is activated at the beginning of a work session, ToolBox displays the Password window, where the password is entered and OK is clicked.
(See The Tools in the The ToolBox for MOSCAD RTUs section of this manual.) This operation activates the communication driver and the password remains in force throughout the session. If you want to access an RTU that requires a different password, you must stop the communication driver first. See Changing the Session Password below. Changing the Session Password To access an RTU that requires a different password, close all ToolBox tools and then double-click the Stop Communication Driver application icon in the ToolBox program folder. Then, activate the ToolBox application you want and enter the password.
WARNING If you try to stop the communication driver while a communication session is in progress, a message warns you that a logical channel is currently open. If you chose to continue (stop the driver), the results of the current communication cannot be predicted. It is advisable to finish the current task and then to stop the driver. 15 The ToolBox for MOSCAD RTUs MOSCAD ToolBox is a set of software tools designed to implement MOSCAD projects. The core of a MOSCAD project is one or more applications that reside in the RTUs that make up a MOSCAD system. ToolBox allows users of different levels and interests to deal with different aspects of the applications. For example, the application developer would usually work with the ToolBox programming tools, while other types of users would fine-tune the applications at the field, using the ToolBox customization and setup tools. Hardware and Software Requirements MOSCAD ToolBox runs on a Pentium 100 (or more powerful) computer under Windows 95 or Windows NT. It requires a minimum of 32Mb of RAM. Installing ToolBox The MOSCAD Programming ToolBox is installed like any other Windows application. Insert the installation disk in your CD driver, activate setup.exe, and follow installation messages and instructions. Written instructions can be found on the leaflet attached to the CD. Connecting ToolBox to RTU The unit (RTU) may be connected to a local computer via cable FLN6457, which ends with an adapter suitable for computer connection (25-pin female D-type connector). Any RS232 port of the RTU defined as RS232 Local Computer may be used for connection to the Programming ToolBox. This connection provides access to that specific RTU, or to any other RTU in the network, to perform all the functions described in this manual. The RS232 ports default configuration of RTUs received from factory is RS232 Local Computer (9600 baud). A Brief Tour This chapter provides a brief description of the MOSCAD/MOSCAD-L communication system, and clarifies basic concepts. The RTU MOSCAD is the name of Motorolas family of SCADA products. It is available in a variety of enclosures, with a multiplicity of two-way radios, and with many different types of input/output (I/O) modules. A MOSCAD RTU is a remote terminal unit in a MOSCAD system. 16 The ToolBox for MOSCAD RTUs Think of an RTU as a computer. It has a CPU, real-time clock, RAM and ROM memory, serial communication ports, etc. A remote terminal unit (RTU) which is installed at some field location is a computer. An RTU which may act as a district controller is a computer. An RTU that functions as the communications bridge between the radio (or other) communications system and the Master Control Center is a computer. Certainly, that Master Control Center is a computer. Just as a computer may be programmed to perform required tasks on a continuous basis, MOSCAD is programmed in an advanced, powerful version of the ladder-logic programming language (and/or C). The programmed rungs are compiled into the very same format that would be used to program an EPROM; the compiled code is downloaded into electrically-programmed ROM within the RTU. The application, as programmed, may then be monitored and debugged. The following picture shows the main parts of the MOSCAD. Radio or Modem Backup Battery AC Power Supply CPU Module Expansion I/O Modules NEMA Enclosure 17 The following picture illustrates MOSCAD-L. The ToolBox for MOSCAD RTUs The MOSCAD application developer need not have a degree or background in computer science. Any programming experience in ladder-logic, Basic, Pascal or C is helpful, but not required. Database Principles All worthwhile computer programming languages require the programmer to define the variables before they are used. The definition includes the variable name and variable logic type. The programming language reserves the appropriate memory for the variable type, and can check for type mismatches as the logic statements are written (create an immediate error if the logic statement uses an illegal named variable type). RTU applications must have all variables defined by name and type before they may be used. How those named variables are organized is unconventional from a computer programming perspective. However, it makes perfect sense when RTU-to-RTU or RTU-to-central communications is considered. The language organizes the programming variables into collections called tables. Tables look very much like computer spreadsheets: they include many rows and may include many columns. Each row and column intersection (cell) is a variable. Some tables have many rows but only one column. All the variables in a single-column table are of the same type, i.e. all bits, all values, all digital inputs, etc. Each variable in the table is uniquely named: PUMP1, PUMP2, etc. Such a table may contain up to 250 uniquely named variables. A single-column table is illustrated below:
18 The ToolBox for MOSCAD RTUs Other tables have many rows and many columns. All variable types within any column are the same, but the several different columns may be of different variable types. For example, a three column table may contain one column labeled PUMP and be a digital-input type; the next column may be labeled START and be an internal value type; the third column may be labeled RUNTIM and be a timer type. The variable names are a combination of the column name and the row number, i.e. PUMP,2 and START,4. This multiple-column table structure is particularly attractive when dealing with dissimilar but related data, particularly as it may apply to some physical device such as the pumps at a pump site. A multiple-column table may contain up to 250 rows and up to 8 columns. Such a table is illustrated below:
The programmer may create up to 127 tables of his/her own design. The design and organization of the tables should be carefully planned. The operation of the application can be monitored by observing the variables; a good table design collects related variables so that many different, but related, things can be observed simultaneously. A good table design anticipates which variables must be reported to a central site, and organizes those variables (whenever possible) into just a few tables. Understand this part of the project, and the technical details of the applicationsthey are both very important. Note that the protocol driver in the central has the same table structures as do the RTUs communicating with the central. Data transfer becomes the simple task of moving row/column data between identical tables. You, the programmer, define the variable names. You are not required to use a bit-
and-register notation that reflects the electrical design of the RTU. You may define and name your variables as you wish, with no restrictions other than name length. Even if you program in another language, the RTU system will accept your variable names. 19 The database supports many variable (data) types. For full details, refer to the Database Concept chapter in the Application Programmer manual. The ToolBox for MOSCAD RTUs Programming Philosophy In order to create an application program which meets your needs, first identify the tasks required of the program, including the information needed to complete each task
(e.g. digital inputs, variables from another site, permission flags from the central, etc.). Next, sketch, in flowchart form, the logical steps required to convert the stated inputs into the required output(s). Make sure that all combinations of inputs are properly addressed and lead to the correct output(s). This step is key, as it is much easier to correct mistakes in a flowchart on paper than to debug and correct lines of programming code. All of the logic operators that are used in Basic or Pascal or C programming languages are available to the RTU ladder-logic programmer. Only the syntax is different. Remember, the logic statements will eventually be compiled; you cant tell how it was programmed by looking at the compiled code. The operators are discussed at length in the Ladder Diagram Language chapter of the Application Programmer manual. Ladder logic originated from the language of relays. The contacts of the relays, singly or in combinations, appear to the left of the logic statements and constitute the tests. The coil of the relays appears to the right of the logic statement and constitutes the actions. Tests on the left, actions on the right. Line after line. The structure looks like the rungs of a ladder, hence the name of the programming language and the name
(rung) of each logic statement. The RTU implementation of ladder logic programming allows up to six lines per rung, and up to eight symbols on a single line. Therefore each RTU rung may indeed be a complete logic statement (IF this THEN that ORIF other-this THEN other-that ELSE
...). Some of the basic tests and actions are listed below. Tests (inputs)
The fundamental relay contact is Normally Open; it closes when the coil is active. There is also a Normally Closed relay contact that opens when the coil is active. The variable name being tested must be a bit-type(not a value-type) and appears above the symbol. These are illustrated on the left.
Its quite amazing how many decisions can be made with only these two operators. Put them in series and you have a logical AND see below. Put them in parallel and you have a logical OR. You can apply Boolean logic to reduce the number of required open/close contacts, as is mandatory with hardware logic solutions. But every RTU coil has an unlimited number of like-named contacts, so there is no cost incentive to minimize the number of relay contacts. You can therefore avoid such reductions and keep the logic readable.
| | | | | / |. x y z 20
( L )
( U )
| < | Ladder logic originally treated only binary data relay contact open or closed. Ladder logic was later modified to handle value (non-binary) data. The ToolBox for MOSCAD RTUs
| = | The variable names being tested must be value-types (not bit-types) and appear above and below the symbol. These symbols are shown at left.
| Testing value data has many applications. Consider some process that must operate if a value exceeds some setpoint.
| A third type of test operator is the Differentiator. It checks for a difference between the current and previous state of the named variable(s) that precede
| it in the rung; the operator is true only when this difference occurs. The operator can be used to check for the rising or falling edge of the named variable(s), so that the associated action only occurs once. The index variable, if used in any of the preceding named variables, also appears above the differentiator symbol. Actions (Outputs)
) Relay On & Relay Off: The original ladder logic action was to energize the coil of a relay this remains the fundamental action. As long as the associated test is true, then the coil (action) will be energized (true). A extension of this concept is the NOT as long as the test is true, the action will not be true. The named variable associated with the coil appears above these symbols as illustrated on the left. Latch & Unlatch: Situations exist wherein the test may be momentarily true, but the associated action should remain true until specifically made not true. Combinational logic can be used to create this action, or more simply the Latch and Unlatch actions may be used. If the test(s) in the rung used to latch the coil is true then the named variable will be latched; a similar action will happen in the rung used to unlatch the coil. Rungs are tested and executed sequentially, as they appear in the task, so if both rungs are simultaneously true then the action in the last rung to be executed will determine the state of the named variable. The symbols are shown on the left.
( SCAN ) Scan: This action reads input data from physical I/O modules into the CPU module, and updates the appropriate variables in the several data tables. The action also writes data from the CPU data tables to the I/O modules. And the action updates mapped bit and value variables within the data tables.
( MOVE ) Move Low & Move High: When the associated test is true, these actions
( MOVH) move (copy) value data from one variable to another without changing the source variable. Move Low (MOVE) is more commonly used; it moves all 16 bits of one value variable to another value variable. Move Low may also be used to move 8 consecutive bits in a single-column table into the low byte of a value variable (bit packing); Move High (MOVH) would be used to move 8 other consecutive bits in a single-column table into the high byte of the value variable. MOVE or MOVH can also be used to move the low or high byte respectively of a value variable to 8 consecutive bits of a single-
column table (bit unpacking). 21 The ToolBox for MOSCAD RTUs The Tools ToolBox is a collection of software programs that eases the task of coding the flowchart steps and making the RTU run the application correctly. A printer is required if the user wants hard copies of the application; the application is also stored on the hard disk. After installing ToolBox, the icons of the various tools included in your package appear in the MOSCAD Programming ToolBox folder, as shown below. Many of the basic tools are described in detail in the System Setup and Diagnostics
(SSD) manual. These include, Site Configuration, Network Configuration, various Utilities, and Diagnostic tools. To start a tool:
1. Connect to the RTU (though you can set configuration values and develop applications without an RTU connection). 2. Double-click the icon of the tool you want. If a password is required, the following dialog box appears. 3. Type the password and click OK. 4. The main window of the selected tool appears. If a password was required, but was incorrectly entered, no communication is established between the RTU and the ToolBox. If the Cancel button is pressed, the tool starts up, but some of the communications-related functions will be hidden (gray) 22 The ToolBox for MOSCAD RTUs Site Configuration (MOSCAD-L) Lets start with Site Configuration (this brief tour illustrates the site configuration for MOSCAD-L; the processes described here are very similar to those that apply to the full MOSCAD system). This program is used to define which I/O modules are present in the unit and where they will be placed in the module rack. It is also used to determine the functionality of the RS-232 and radio (modem) ports on the CPU module to be defined. The address of the specific RTU is then defined, and the combination downloaded into the RTUs CPU module. This process gives some personality to the RTU; this process must be accomplished via a local cable between the ToolBox computer and the RTU. After activating the MOSCAD-L Site Configuration application, the following window appears:
The File menu includes commands for starting a new configuration, retrieving an existing set (file) of configuration values, saving a configuration, printing the contents of a configuration file, and the like. Click the File menu (or press ALT+F) to open it. It looks as shown below. 23 The ToolBox for MOSCAD RTUs To start configuring a site, select the New command from the File menu or click on the New icon. This automatically opens a new file, with default configuration settings, as shown below. The sections marked Module1 Module2, Module3 each represent an expansion I/O module in the unit. (See the picture of the unit in The RTU section above.) The CPU module does not appear on the Site Configuration screen, as it is always placed in Rack 0, Module 0. The other I/O modules may be specified by clicking the desired Module (e.g. Module1) button. After clicking Module1, the I/O Modules dialog box appears, which enables you to select a type for the module:
After selecting the module type from the list, click OK. Repeat the process (click the Module2 button, then open the type list, etc.) for all the required I/O modules. Made a mistake? Just click Type again, and select another value from the type list. The current definitions of the three ports of the CPU module appear on the main window. One port, usually Port 1, is by default defined as Link Name = Computer 1, and Port Type = RS232- Local Computer. Use this port for the local connection of the ToolBox. To see the default port definition, click the Port 1 button. The following is displayed:
24 The ToolBox for MOSCAD RTUs The other two ports are configured in a similar way, though the values vary. Port 2 defaults to the same configuration as Port 1, but can be changed as necessary. Port 3 usually defines the communications medium required (e.g. radio, modem ). Once the ports are configured, the values are saved in a site configuration file and downloaded to the unit. The Site Configuration section of the System Setup and Diagnostics manual describes the types and parameters for each port, as well as the procedure for defining, saving and downloading the site configuration to the RTU. Network Configuration The second major step is configuring the network. Most data radio communication systems have a single base transmitter located somewhere near the center of the physical coverage area, as illustrated below. The transmitter emits radio energy; the distance the emission travels define the coverage limits of the system. Normally, all data equipment will lie within this coverage area, in which case, no network configuration need be defined. RTU RTU RTU RTU RTU However, if one or more sites with data equipment lie outside this coverage area;
reliable communications with these sites cannot be assured. The RTU provides a solution to this problem which requires no additional hardware. A map of the network is created and existing units are used to relay information around the network to its destination. 25 The ToolBox for MOSCAD RTUs Any RTU can receive data, validate that data, and store it in a buffer for retransmission a few seconds later. An RTU with more than one communications medium (link), known as a network node, stores the data and relays it to another RTU. Note that network node RTUs are also capable of operating as regular RTUs;
thus no special, dedicated hardware is required. The data Store & Forward capability is a communications protocol task; and requires nothing to be programmed in the application. A logical name is assigned to each communications medium in the network (e.g. Radio1, Radio2, Line1, Line2). Most sites will have a single communications medium these are not network nodes. A few sites may have both a radio and a wireline modem, or two radios these are definitely network nodes. Some sites may have a single radio that communicates both with the main portion of the system and also with one or more out-of-range RTU sites. These are also network nodes; the link names would be Radio1/Zone1 and Radio1/Zone2 (abbreviated Radio1/1 and Radio1/2 respectively) or their equivalent. Use the Network Configuration program to define these network nodes and their respective links, as described in the Network Configuration section of the System Setup and Diagnostics manual. Application Programmer Once the site and network have been defined, building the application can be built, using the Application Programmer. The application (also called a project) consists of a database and a ladder program. 1 Activate Application Programmer from the MOSCAD Programming ToolBox folder, as you opened the Site Configuration and Network Configuration. (If you chose not to connect to the unit at this time, hit CANCEL when prompted for the Communication driver password. The main window appears as shown below. Note that most of the icons will be dimmed and unselectable. 2. From the Project menu, select the New command, or click on the New icon. The New dialog box is displayed. The ToolBox lists all existing applications (projects) under Directories; hence the list may vary from computer to computer. 26 The ToolBox for MOSCAD RTUs 3. For each project, Application Programmer opens a new subdirectory under tbox750\user. The path appears in the Selected Path box, and the insertion point is positioned where you are expected to type the name of the project. Type a project name of up to 8 characters and click the Create button. This creates the sub-
directories and the application files. Anything you save related to the application will be stored in that directory. Another user (e.g. user1) area can be created by changing the value in Selected Path. 4. Open the Edit menu. The commands Database Builder, Process Programming and I/O Link represent the main application building steps. Database Builder Database Builder is used to create the application variables. Variables are declared in table-like windows. Select Database Builder from the Edit menu. The following dialog box is displayed. The Database Builder window tabs show three types of tables, User Tables (created by the user specifically for the project), System Tables (available to the project), and Constants Table (available to the project). User Tables is selected by default. Here you may create (Append) and Edit tables of variables which represent the inputs and outputs of your system, as mentioned in Database Principles above. For full details, see the Application Programmer manual. 27 The ToolBox for MOSCAD RTUs Process Programming The defined variables may now be used in the coding of the various rungs of the application, which determine what actions are performed, under what conditions. You may wish to refer at this time to the lists of available tests and actions in Programming Philosophy above. Tests, actions, and variables you're ready to go. Both the Data Base Builder and the Process Programming use an Append/Add capability to define a new table or process, and an Edit capability to insert variables or logic statements into that table/process. Open the Edit menu and select Process Programming. The following dialog box is displayed. The MAIN process exists by default because it automatically runs at powerup or upon an application restart. The MAIN process provides the framework in which the application runs. Process and Rung Operations enable you to add and edit new rungs and processes. The logic of the rungs is programmed according to the logic of the flowchart created, which was based on the tasks required of the RTU. For full details on Process Programming, see the Application Programmer manual. I/O Link The Site Configuration program is used to define the physical aspects of the RTU hardware. The Application Programmer program is used to define a virtual process 28 The ToolBox for MOSCAD RTUs that has no link to any physical reality. Yet such a link is required. This is done using I/O Link. 1. In the Application Programmer main window, open the File menu and select Import Site Configuration. 2. Select the site configuration file related to your application (field.cfg). 3. Open the Edit menu and select I/O Link. The following dialog box is displayed. 4. The I/O Link dialog displays the application tables. The Status column shows those tables that include an I/O module which requires linking. The minus sign indicates incomplete link data. Highlight the first table that needs link information and click the Edit button. The table is displayed. For each variable in the table, enter the appropriate Rack and Module numbers on the RTU and the desired physical input or output on the specified module. These definitions are saved together with the rest of the project information. For a full description of the I/O Link procedure, see the Application Programmer manual. The link process is the only association between the physical reality of the site configuration and the virtual reality of the application. If the site configuration is 29 subsequently revised, the new version should be imported into the project. The application itself is not necessarily affected. The ToolBox for MOSCAD RTUs Compiler Once the application is saved, it must be converted into a form which can be understood by the CPU. The compiler turns the visual ladder logic table and rung definitions into code to be executed directly by the microprocessor in the CPU module. Open the Run-Time menu in the main window and select the Compiler command. A two-pass compilation takes place. Errors are reported along with the associated rung name. You must correct these errors to produce error-free compiled code. A successful compilation produces an End of Compilation message that provides a few items of information. Downloading and Monitoring The compiled code is ready to be downloaded into the CPU module. This can be done locally, using a cable, or remotely over the communications network (from any site in the system to any other site in the system). The runtime operation of the downloaded code may be monitored via an upload from the CPU. You can upload locally using a cable, or via the communications network. You may monitor the runtime values in any table or in any rung you choose the presentation format. 30 Remote Terminal Unit The MOSCAD Remote Terminal Unit (RTU) is a modular unit, comprised of a CPU module, communication boards, and I/O modules interconnected by a common modular bus. The modular construction allows you to configure each RTU according to the precise requirements of the application. It also permits future expansion as the application develops. The lighter model, MOSCAD-L RTU, includes only a CPU and three I/O modules. The RTU Hardware The core of the RTU is the CPU module. The other modules provide digital (discrete) and analog input/output capabilities. Each module is enclosed in a plastic box, which allows for fast assembly/disassembly
(snap-in technique) without the need for tools. In the MOSCAD RTU, each module has LED indicators that monitor operations. CPU Module The MOSCAD CPU module, based on the high-performance Motorola Integrated Multiprotocol Processor (IMP) MC68302, provides three communication channels, one of which is an interchangeable interface plug-in board. The module is located in slot 0 of rack number 0 - the leftmost module on the first bus of the first rack. MOSCAD-L is based on the LC68302 processor and provides three communication channels. Memories The CPU board contains two types of on-board memories:
Static CMOS RAM (SRAM), used for storing data and system parameters. The RAM is backed-up by a lithium battery. Segmented FLASH memory, used for storing the system program, the site configuration information, the user application, and the system configuration data, and programmed via Programming Toolbox. Front Panel - MOSCAD The CPU modules front panel includes the following:
Communication port connectors Twenty diagnostic LEDs Two push-buttons Battery CommunicationPorts 32 Remote Terminal Unit The CPU module has three communication ports with the following characteristics:
Communication port 1 with two interface options:
RS-485 for UART start/stop operation and baud rate of up to 57,600 b/sec (port 1A). RS-232C with full DCE/DTE operation and baud rate of up to 57,600 b/sec (port 1B). Communication port 2 with RS-232C interface as port 1b. Communication port 3 a plug-in port designed for various radio or line communications. The available plug-in boards are listed in Site Configuration. The two RS-232C ports (1b and 2) may be configured by the site configuration software
(see Site Configuration in the System Setup and Diagnostics Tools manual). The default configuration of both ports is RS232 Local Computer. DiagnosticLEDs In MOSCAD, the 20 diagnostic LEDs are arranged in 4 x 5 matrix. The function of each LED is described below:
CPU PWR LOAD CONF APPL MON AC TX1 TX2 TX3 CPU ERR RX1 RX2 RX3 RST BAT CM1 CM2 CM3 FAIL PORTS PWR (Power): Lights as long as the 12 V DC input power is applied to the RTU, indicating that the unit is operating. AC (AC Fail): Lights when the AC power supply to the unit fails (operates on the units 12 V battery). CPU (CPU Fail): Lights to indicate a malfunction in the CPU. The nature of the malfunction is indicated by the 16 LEDs situated in the four columns on the right, which light simultaneously with the CPU Fail LED, as detailed below (CPU LED is on):
(1) CM3 LED is on: RAM test has failed.
(2) RX3 LED is on: ROM test has failed.
(3) CM3 and RX3 LEDs are on: FLASH memory test has failed. 33 Remote Terminal Unit
(4) TX3 LED is on: Create software module has failed. (There is probably not enough memory. It is advisable to add a memory extension board or to reduce memory consumption.)
(5) CM3 and TX3 LEDs are on: Real time clock has failed.
(6) RX3 and TX3 LEDs are on: Internal clock has failed.
(7) CM3, RX3, and TX3 LEDs are on: Hardware breakpoint has failed.
(8) MON LED is on: XTAL rate change has failed.
(9) CM3 and MON LEDs are on: User request has failed.
(10) RX3 and MON LEDs are on: Application version was compiled and downloaded by a previous version of the Programming Toolbox.
(11) RX3, CM3, and MON LEDs are on: The current site configuration was downloaded by a previous version of the Programming Toolbox. RST (CPU Reset): Flashes upon reset of the CPU, usually caused by the watchdog timer, indicating that the software is not running properly. ERR (Error): Lights to indicate that an illegal state has been detected in the software, or a module/board is missing, and other malfunctions. These events are logged in a special error logger in the CPU. The contents of the error logger may be read via Programming Toolbox (see Diagnostics in the System Setup and Diagnostics Tools manual). BAT (low battery voltage): Lights to indicate that the voltage of the lithium battery (which backs up the CMOS RAM when the 12 V voltage is not supplied to the modules), is low. The battery must be replaced. Note that the battery may be replaced without interrupting RTU operation, by pulling out the used battery and inserting a new one. LOAD: Lights to indicate that a configuration definition or an application is being downloaded to the FLASH memory. CONF (configuration): Is lit to indicate that a site configuration definition has been loaded into the FLASH memory. APPL (application): Is lit to indicate that an application has been loaded into the FLASH memory. The LED flashes in the following cases:
When the application program is in the STOP SCAN state for performing diagnostics via the monitoring program of the Application Programmer. When the application run-time is too long (more than 1.2 seconds). This is caused by a mistake in the Ladder Diagram program, such as an infinite loop. When the application program is in the STOP state during hardware test performed by the Programming Toolbox. MON (monitor): Lights when the monitoring program of Application Programmer performs symbolic debugging of the Ladder Diagram function. This is achieved by inserting breakpoints to obtain snapshots of the data during the process. TX1: Lights when the RTU is transmitting data via port 1. RX1: Lights when the RTU is receiving data via port 1. 34 Remote Terminal Unit CM1: Lights when the communications channel used by port 1 is busy. TX2, RX2, CM2: As above, for port 2. TX3, RX3, CM3: As above, for port 3. By default, LEDs are always displayed. Even the command "Disable leds display" in "Leds Test" in the "HW Test" in the ToolBox will not turn any LEDs off. However, it is possible to set a time out for the LEDs. In the Site Configuration, use the "Advanced" menu, choose
"General System Parameters" and then "Leds". The "Leds operating mode" has a default value of "Light always". This may be changed to "Light up to time out". The default time out is 600 seconds, which is ten minutes. When the time out is reached, the LEDs turn off. This provides a small savings in electricity. Pressing the push-button will re-light the LEDs in CPU mode. When working in
"Light up to time out" mode, the command "Disable leds display" in "Leds Test" in the
"HW Test" in the ToolBox will turn all the LEDs off. Then the command "Enable leds display" will relight the LEDs in CPU mode. Push-buttonPB1 The main function of PB1 is to turn the LEDs on and off, as follows:
When the push-button is pressed once momentarily, the display is activated When the push-button is quickly pressed twice, the display turns off. To conserve energy, the display turns off after 10 minutes if it is not switched off manually. When the push-button is pressed continuously, all the LEDs light simultaneously (for LED test). The LEDs extinguish when the switch is no longer pressed. In all modules there are several LEDs that do not turn off when all other LEDs do. These LEDs, such as the four leftmost LEDs of the CPU module, indicate malfunctions and important events. Push-buttonPB2 For the use of the ladder application. A CPU restart is performed when the RTU is switched on, and PB1 and PB2 are pressed simultaneously for about 10 seconds continuously. A CPU restart is also performed when PB1 and PB2 are pressed simultaneously for about 30 seconds continuously while the RTU is operating. This erases the user flash memory (i.e. site configuration, applications, etc.) and restores the RTU to the default configuration. The buzzer sounds when the RTU is restarted. Battery The lithium battery backs up the CMOS RAM and the real time clock when the 12V voltage is not supplied to the modules. Note that the battery may be replaced without interrupting the RTUs operation by pulling out the used battery and inserting a new one. The RTU is shipped from the factory with the battery disconnected by an insulating strip
(to prolong battery life). Carefully pull out the strip before working with the RTU. If the RTU is to be stored for a long time, do not forget to place the insulating strip. Buzzer 35 The buzzer sounds during the cold start-up of the CPU module and while erasing the configuration/application from the FLASH memory. Remote Terminal Unit Front Panel MOSCAD-L The CPU modules front panel includes the following:
Twenty diagnostic LEDs One push-button DiagnosticLEDs In MOSCAD-L, the LEDs are arranged as shown below:
CPU M1 M2 M3 LOAD CONF Appl 1 5 9 MON 13 RST 2 ERR 3 BAT 4 TX1 6 RX1 7 CM1 8 TX2 10 RX2 11 CM2 12 TX3 14 RX3 15 CM3 16 The upper row of four LEDs (CPU, M1, M2, M3) is used to indicate what information is displayed in the remaining sixteen LEDs (CPU, or I/O Module 1, 2 or 3). Each press of the push-button switches from CPU LED display to M1 to M2 to M3, and then back to CPU. In any display mode, when blinking, M1, M2, and M3 also indicate I/O Module Fail. There are two possible reasons for I/O Module Fail:
(1) Missing I/O module
(2) Incorrect I/O module (doesn't match configuration in Flash) CPU RESET (RST LED) In the CPU LED display, one LED is NOT always under software control. This is the RST LED (second row, first column). When ONLY the CPU LED and the RST LED are on, then the CPU is in RESET state and these LEDs are hardware controlled. When ONLY the RST LED is on during startup (CPU LED OFF), the CPU is performing power up tests. CPU LEDs on startup: SERIOUS FAILURE (CPU FAIL) When a SERIOUS FAILURE is found during startup power up tests, the ERR LED will blink (CPU LED OFF). For example, on ROM fail, or RAM fail, or CREATE fail, the ERR LED will blink, and the LEDs in columns 3 and 4 will contain the error code indicating the CPU error. (See list of errors under CPU Fail in MOSCAD Diagnostic LEDs above.) 36 Remote Terminal Unit AI LEDs If both the UDF and the OVF LED for a channel are on, this indicates that the specified AI channel is not calibrated. If this occurs in the field, it indicates a hardware problem with the IO module. DC On-Off Switch In MOSCAD-L versions up to and including V2.0x, switching DC OFF with the DC On-
Off switch normally causes COLD RESTART. This is different than MOSCAD, which has a Lithium Battery backup to provide WARM RESTART. As of version V2.40, WARM RESTART may be triggered on MOSCAD-L (e.g. to replace a faulty I/O module,) if you have AC FAIL (see below) when you switch DC OFF. First disconnect the PWR IN connector, and wait until the PWR LED goes off. This is AC FAIL. Then switch DC OFF. Replace the I/O module. When DC is switched ON again, you should get WARM RESTART, if the battery is connected and functioning. Don't forget to reconnect the PWR IN connector; otherwise the battery will be drained. This procedure enables WARM RESTART on systems with Solar Panel which never have AC FAIL. COLD RESTART is performed by switching DC OFF with the DC On-Off switch, while pushing the push-button. ( V2.40) LEDs Timeout By default, LEDs are always displayed. Even the command "Disable leds display" in "Leds Test" in the "HW Test" in the ToolBox will not turn any LEDs off. However, it is possible to set a time out for the LEDs. In the Site Configuration, use the "Advanced" menu, choose
"General System Parameters" and then "Leds". The "Leds operating mode" has a default value of "Light always". This may be changed to "Light up to time out". The default time out is 600 seconds, which is ten minutes. When the time out is reached, the LEDs turn off. This provides a small savings in electricity. Pressing the push-button will re-light the LEDs in CPU mode. When working in
"Light up to time out" mode, the command "Disable leds display" in "Leds Test" in the
"HW Test" in the ToolBox will turn all the LEDs off. Then the command "Enable leds display" will relight the LEDs in CPU mode. Push-buttonPB1 Push-button during normal operation When the push-button is pressed once momentarily, the display is activated. Every consecutive short pressing of the push-button advances the display mode in those modules where more than one display mode is available. One long press (several seconds): Test LEDS. This will light all LEDS regardless of the display mode. When the push-button is released, the display will return to the CPU display state. However, after pressing for ten seconds the display will return to the CPU display state, even if the push-button is still pressed. One very long press (thirty/forty seconds): Erase Flash. During normal operation, press the push-button and hold it down continuously (thirty/forty seconds) until the LEDs blink 37 Remote Terminal Unit three times. Then the MOSCAD-L will erase the User Configuration, Application and everything else in the Flash memory. After that, CPU RESET will occur. Push-button during startup Push-button pressed while power turned on: Download System. CPU LED begins to blink
(all other LEDs off). CPU is in "Download System to Flash" mode. Push-button pressed after power is turned on and all LEDs are on: Erase User Flash. During startup, while all LEDs are on, press the push-button and hold it down continuously until the LEDs blink three times. Then the MOSCAD-L will erase the User Configuration, Application and everything else in the Flash memory. After that, CPU RESTART will occur. The push-button is also used when downloading system software (see System Downloader section in System Setup and Diagnostics Tools manual.) I/O Modules The RTU uses modular design with a variety of modules, such as:
Input modules, for discrete inputs and input counters or analog inputs Output modules, for discrete outputs or analog outputs Mixed input/output modules RTU Software The RTU software design is based on an object-oriented Multi-Tasking Executive System
(MTE). It has been designed so that during cold start-up it creates all software entities needed to support the different hardware modules and communication ports as configured via Site Configuration program by the system engineer. This permits the use of only one standard software package for all RTUs and provides flexibility in supporting the application requirements without sacrificing efficiency. The software supports a communication protocol based on the OSI model (published by ISO). The protocol comprises all of the seven recommended layers, adapted for SCADA. The RTU software also provides the following:
Ladder application processes divided to run under up to five different priorities, to improve time efficiency. Another ten tasks can be run by C Toolkit. Real time symbolic monitor debugger for the Ladder Diagram application. Clean power-down/power-up recovery of the RTU (supported by software and hardware). After power-up, the RTU continues from the same task that was suspended. The RTUs real time clock continues to advance with battery power during the outage time. The application decides whether anything is to be done about lost time. Clock synchronization between various RTUs; can be activated via the ToolBox or a Ladder application. Background housekeeping of the software entities to detect software and hardware malfunctions. 38 Remote Terminal Unit An error logger to store all abnormal conditions (software and hardware) for retrieval at any time by the Programming Toolbox Error Logger from any port in the system (not necessarily on the same RTU). Diagnostics of every software entity (using symbolic entity names) in the RTU, provided from any port in the system. The RTU does not have option jumpers or potentiometers. All options and adjustments are software controlled. This increases reliability while reducing the risk of forgetting adjustments. 39 MDLC Communication Protocol The MDLC communication protocol is based on the OSI (Open Systems Interconnection) model published by ISO. The protocol comprises the seven recommended layers adapted for SCADA, in which every RTU is simultaneously a distributed control unit and a communication node serving itself as well as other units. Information is transmitted in the form of variable-length digital words. Advanced security techniques are employed to provide protection against false messages. The protocol is efficient for transferring small quantities of information, such as measurements and discrete statuses, as well as for transferring large quantities of information, such as downloading software applications, including data base, process, etc. SITE A APPLICATION PRESENTATION SESSION TRANSPORT NETWORK MULTI-LINK CRC PHYSICAL SITE C APPLICATION PRESENTATION SESSION TRANSPORT NETWORK SITE B NETWORK MULTI-LINK MULTI-LINK MULTI-LINK CRC CRC CRC PHYSICAL PHYSICAL PHYSICAL The following subparagraphs describe the seven layers of the protocol, shown in the figure above:
Physical layer. Link layer. Network layer. Transportation layer. Session layer. Presentation layer. Application layer. 40 Physical Layer MDLC Communication Protocol The physical layer comprises the various communication ports and their associated software. The software contains all the specific handling required by the communication ports and provides an identical interface to the link layer. In this way, it is possible to define a standard entity for the link layer. The software is flexible and adapts itself to the number of ports and their various types as defined by the user, but the possibility of defining a large number of ports of various types does not impair software efficiency. The physical ports may also be configured to provide hard-copy printout to a printer. Link Layer The function of the link layer is to ensure proper communication over a single communication channel. The information is stored in variable-length frames where the link layer protocol contains the following fields (for a DATA frame):
The address of the unit to which the DATA is transmitted. The address of the transmitting unit. The number of the frame. CRC for error detection. Dual addressing is used to allow RTU-to-RTU transmission without central intervention, transmission to several centrals, or a hierarchical system where some of the RTUs serve as sub-centrals for the lower hierarchies. During reception, the address is identified by hardware (and not by software) at the physical level, in order not to spend software time on checking words that are not intended for that specific RTU. This preliminary screening enables reception of at least four different addresses per RTU: single address to access a specific RTU, broadcast address to access a group of RTUs, and two additional addresses enabling various communication operations. A link entity associated with a channel may receive several types of information:
information that is intended for that specific RTU and information passing through it and is designated to other RTUs. The link entity transmits an acknowledgment (ACK) to each RTU according to the DATA received from it. The ACK word is separated from the DATA word, since the RTU receiving the DATA is not necessarily the same RTU to which the ACK is addressed. The ACK word enables the receiving site to identify the missing frames and retransmit only those frames, thus saving air time by not repeating all the information transmitted. The CRC is 32 bits or 16 bits per CCITT definition. The frame synchronization (FLAG), at the beginning and at the end of each word, is transmitted in different ways for different physical ports. 41 MDLC Communication Protocol Network Layer A system is defined as a network whenever it uses more than one communication medium, such as wireline and/or various radios, as well as Store & Forward repeaters, all on a single frequency. The communications in the network occur among nodes, which physically may be RTUs, centrals, or repeaters. The network layer and its protocol are responsible for routing packets in the network via the various nodes to enable communication between any two sites in the network. It is possible to access any application anywhere in the system from any port in the system, such as the RS-232 ports of the various RTUs, for purposes of definition, monitoring, modification, diagnostics, error logging, etc. Transportation Layer The transportation layer ensures END-to-END completeness of the information transmission (between the RTU that has transmitted the message and the one that should receive it). This layer transfers the DATA in an orderly fashion to the session layer above it. The protocol of this layer assigns sequential numbers to the packets (independent of the numbers assigned by the link layer) and transmits an ACK word to indicate that the DATA is complete and all packets are transferred in the appropriate order to the layer above. The transport layer performs multiplexing, thus enabling several session entities (logical channels) to operate via one physical port or several physical ports. It is possible to define any number of logical channels, regardless of the number of physical channels defined. Session Layer The session layer enables the definition of any number of entities (instances), which are capable of conducting a session with a parallel entity in another RTU, a central, or a sub-
central. These entities and their protocol simultaneously conduct several sessions between any two sites, i.e., to simultaneously run several applications such as data transfer, diagnostics, monitoring, etc., without interference between the applications. The session handling includes the following:
Start session. Synchronization of message direction. End session. Abort session. Re-synchronize session. The session layer also provides for transfer of short one-frame messages from one site to the parallel application at another site without the need to start a session. 42 MDLC Communication Protocol Presentation Layer This layer handles the presentation of the DATA received from the various applications within the various packets. It performs the following:
Checks that the information transferred to the application is complete. Compresses the information. Encrypts the information. Checks authentication. Application Layer This layer contains all the communication applications required for maintaining a SCADA system, as detailed below:
a. b. c. d. e. f. g. h. i. j. Application enabling bi-directional data transfer upon request from the data bases of the sites. Software for downloading configuration to the sites:
I/O modules definition. Communication ports definition. Software for downloading and monitoring application software (defined by the user in the ladder diagram language) to the sites, including:
Definition of the data structure. Object code of processes. Real-time symbolic monitoring of data base and processes. Application for transmitting events and short messages. Application for broadcasts. Application for remote diagnostics of the hardware and the software. Application for the retrieval of error messages stored in the error logs of the sites. Application for the calibration of A/D and D/A modules. Application for communication analysis and accumulation of statistics. General Downloader to download various blocks (e.g. site configuration, ladder applications, network configuration, phone book, C blocks, third party drivers, x.25 conversion table, IP conversion table, etc.) 43
1 2 3 | users and installation guide | Users Manual | 3.20 MiB |
MOSCAD-M Remote Terminal Unit Owners Manual 68P02961C50-O CONTENTS INTRODUCTION.........................................................................................................................1 SCOPE OF THIS MANUAL ...............................................................................................................1 GENERAL DESCRIPTION ................................................................................................................1 HARDWARE OPTIONS....................................................................................................................2 Line, RS232 and RS485 Communication Interfaces..............................................................................2 Radio Communication Interfaces ..........................................................................................................2 I/O Configurations.................................................................................................................................2 Power Supply and Battery .....................................................................................................................2 INSTALLATION ..........................................................................................................................3 GENERAL ......................................................................................................................................3 Power Connections:...............................................................................................................................3 WALL MOUNTING.........................................................................................................................3 Wall Mounting with Screws ...................................................................................................................4 Wall Mounting on DIN Rail...................................................................................................................5 CONNECTIONS...............................................................................................................................7 Ground Connection................................................................................................................................7 Power Connections................................................................................................................................7 Backup Battery Connection ...................................................................................................................7 Internal Radio Connection - antenna ....................................................................................................7 External Radio Connection....................................................................................................................7 Line Communication Connection ..........................................................................................................8 INSTALLATION OF BACKUP BATTERIES .........................................................................................9 MISCELLANEOUS.........................................................................................................................10 Open the Case Door.............................................................................................................................10 Close the Case Door............................................................................................................................10 Antenna Placement ..............................................................................................................................10 Fixed Site Antennas .............................................................................................................................10 THE MOSCAD-M UNIT............................................................................................................11 OVERVIEW ..................................................................................................................................11 COMMUNICATION PORTS ............................................................................................................12 CONNECTORS..............................................................................................................................12 CONTROLS AND INDICATORS.......................................................................................................12 68P02961C50-O
'Motorola Inc., 2001 August 2001 Contents LED Control.........................................................................................................................................13 System Software Downloading ............................................................................................................13 CPU Reset............................................................................................................................................13 LED DISPLAY INDICATIONS........................................................................................................14 CPU Page LED Functions...................................................................................................................14 IO1 Page LED Functions.....................................................................................................................15 IO2 Page LED Functions.....................................................................................................................17 IO3 Page LED Functions.....................................................................................................................18 AO Page LED Functions .....................................................................................................................19 User Page LED Functions...................................................................................................................20 I/OS (ALL MODELS)....................................................................................................................22 Wetting switch connection (x2)............................................................................................................22 DO Magnetic Relay connection (x4) ...................................................................................................23 DO Open Collector (x4).......................................................................................................................23 DI (x12)................................................................................................................................................24 ADDITIONAL I/OS (EXPANDED I/O MODELS ONLY) ....................................................................25 AI (x4) ..................................................................................................................................................25 AO (x1).................................................................................................................................................26 DI (x3)..................................................................................................................................................27 Pin Assignment - Main Board TBs ......................................................................................................28 Pin Assignment - Expansion Board TBs..............................................................................................29 BACKUP BATTERY ......................................................................................................................29 POWER SUPPLY...........................................................................................................................30 POWER MANAGEMENT.........................................................................................................31 OVERVIEW ..................................................................................................................................31 RUN MODE .................................................................................................................................31 SLEEP MODE...............................................................................................................................32 WAKEUP EVENTS........................................................................................................................33 ETHERNET INTERFACE OPTION .......................................................................................34 OVERVIEW ..................................................................................................................................34 EXTERNAL ETHERNET INTERFACE UNIT......................................................................................34 INSTALLATION.............................................................................................................................35 Connections .........................................................................................................................................35 APPENDIX A: CABLES AND ADAPTERS............................................................................36 GENERAL ....................................................................................................................................36 RTU-TO-COMPUTER/TERMINAL CONNECTIONS..........................................................................36 RTU-TO-MODEM CONNECTIONS ................................................................................................37 RTU-to-Modem Asynchronous Connection.........................................................................................37 RTU-TO-RTU CONNECTION.......................................................................................................38 RTU-to-RTU Asynchronous Communications Connection .................................................................38 ii Contents APPENDIX B: MODELS AND ACCESSORIES....................................................................39 GENERAL ....................................................................................................................................39 INSTALLATION OF MOSCAD-M WITH GP140/328/HT750/ PRO5150 RADIO...........................41 MOSCAD-M INSTALLATION KIT FOR GP140/GP328/HT750/ PRO5150 RADIOS ....................42 MOSCAD-M DEBUG HARDWARE KIT.......................................................................................42 MOSCAD-M Board..............................................................................................................................42 Debug Setup.........................................................................................................................................43 Logic Analyzer .....................................................................................................................................45 Pin Assignment Logic Analyzer TBs.................................................................................................45 APPENDIX C: CHANGING THE ANALOG INPUT MEASUREMENT TYPE................46 GENERAL ....................................................................................................................................46 DISASSEMBLING THE RTU ..........................................................................................................46 Remove Connectors .............................................................................................................................46 Open RTU ............................................................................................................................................46 Remove Main Board ............................................................................................................................47 Remove Expansion Board....................................................................................................................47 Place Jumpers......................................................................................................................................48 REASSEMBLING THE RTU ...........................................................................................................49 Install Expansion Board ......................................................................................................................49 Install Main Board...............................................................................................................................50 Close Case ...........................................................................................................................................50 iii INTRODUCTION Scope of this Manual This manual provides instructions for the installation and operation of the MOSCAD-M Remote Terminal Unit (RTU). It also provides on-site tuning instructions for RTU elements that do not necessarily require shop level assistance. This manual covers the basic RTU and most communications and I/O options. The online help of the MOSCAD-M RTU Configurator contains additional information on the RTU. General Description The RTU is a remotely located unit used for monitoring and control of local equipment. The unit can operate in stand-alone mode, or as an intelligent RTU or node on a distributed control system. The RTU consists of the following components installed in a plastic case: printed circuit board, internal/external radio, and battery housing. This manual describes both basic and expanded I/O models. The MOSCAD-M is a low-power unit that incorporates a variety of power save modes which enable the unit to operate with minimal power consumption. The RTU case is suitable for either wall or DIN rail mounting. Figure 1 provides a general view of the MOSCAD-M RTU. The MOSCAD-M RTU is enclosed in an indoor plastic case and is intended for outdoor base station use. The installer must make sure that the installation meets the requirements of the standard and protects the unit from weather hazards. The antenna must be physically secured at a permanent outdoor location. Figure 1 MOSCAD-M RTU General View with Case 1 Introduction Hardware Options Line, RS232 and RS485 Communication Interfaces A variety of Line, RS232, and RS485 communication interfaces are available:
RS485 adapter RS232 multiplexer Ethernet Interface Unit Radio Communication Interfaces Internal radio UHF High Band Internal radio UHF Low Band A variety of radios can be attached using internal DPSK or duo-binary modem:
Variety of external radios (GP140/328, HT750, PRO5150) For details on the available external radio models, and their connection to the RTU, see Appendix B. I/O Configurations Different models of the MOSCAD-M RTU have slightly different I/O configurations. Models with basic I/O configuration:
12 Digital Input 8 Digital Output (4 Magnetically Latched, 4 Open Collector) 2 Digital Output (Solid State) Models with expanded I/O configuration:
15 Digital Input 8 Digital Output (4 Magnetically Latched, 4 Open Collector) 4 Analog Input (4-20 mA) 1 Analog Output (0-5V or 4-20mA) 2 Digital Output (Solid State) Power Supply and Battery The power supply and backup battery options are:
9-30V DC power input (compatible with 12V DC Solar Panel) 3 x C backup battery (for Real Time Clock and RAM retention) 2 INSTALLATION General MOSCAD-M SAFETY SUMMARY The MOSCAD-M should be installed by qualified and authorized technicians. If the installation involves high-voltage connections, technicians must be specifically qualified to handle high voltage. This equipment was tested with cables 3 meters in length. If longer cables and/or cabinets are used, the installer is responsible for making sure that the installation complies with the requirements of the relevant standard. The product is a radio accessory. The installer must make sure that the radio connected to the system has all required approvals and that the installation meets the requirements of the standard. This equipment is a base station unit and complies with the FCC base station requirements. The antenna must be installed outdoors. Power Connections:
This device accepts 9-30V DC input, maximum 2.5A @15V DC. This chapter covers the following installation procedures:
Wall mounting Connections Backup Batteries Miscellaneous Wall Mounting The dimensions of the unit are: width 21.5 cm (8.46"), height 18.5 cm (7.28"), depth .85 cm (.33"), weight 1.5kg maximum (see Figure 2). 3 Installation Figure 2 Dimensions of MOSCAD-M RTU Plastic Case The unit can be installed on screws or on DIN rail mounting. Before installing the MOSCAD-M RTU, verify that there is sufficient space around the unit. Allow 20 cm (7.87") from the bottom of the box for the TB connectors. When an RF connector is attached (internal radio models), allow for an extra 10 cm (4"): 2.02 cm (.8") from the top of the box for the RF connector and 8 cm (3.15") for the wires. For models with external radios, allow 8 cm (3.15"). Wall Mounting with Screws The MOSCAD-M can be mounted on the wall using screws, as shown in Figure 3. 1. Secure two screws (maximum head size 0.9 mm) on the wall, 105 mm apart. 2. Hang the unit on the screws, fitting the two cavities on the back cover of the unit over the screws (see Figure 3). The screws used should not protrude from the wall surface by more than 6 mm or by less than 4 mm. 4 Installation Figure 3 Installation of MOSCAD-M Screw Mount It is also possible to attach the MOSCAD-M to the wall using the small screw hole at the bottom of case, though this requires dismantling the RTU, which is generally discouraged. Consult Motorola service personnel before opening the MOSCAD-M casing. To mount the RTU:
1. Open the case and dismantle the parts of the MOSCAD-M. 2. Secure the back of the case against the wall using a screw whose diameter is less than 3.5 mm and head size is at least 5.5 mm. 3. Reassemble the parts of the MOSCAD. Before beginning any disassembly or reassembly procedures, you should be adequately grounded to prevent damage to static sensitive devices in the unit. Wall Mounting on DIN Rail For mounting the RTU on a DIN rail, two universal foot elements (Phoenix Connectors MFC PIN UMK-FE) are required. To mount the unit, proceed as follows:
1. Slide the two foot elements into the recesses on the back cover of the unit as shown in Figure 4. Press until they click behind the snaps that secure their placement. (See zoomed image in Figure 5.) 5 Installation Figure 4 DIN Rail Attachment SNAP Figure 5 DIN Rail Attachment-Foot Element Snap-in (Enlarged) 2. Press the unit onto the DIN rail, using both universal foot elements. The elements can be used on DIN rail 35 mm and G rails. (See Figure 6). Figure 6 MOSCAD-M Mounted on DIN Rail 6 Installation Connections Verify that all power and ground connections are made in accordance with local standards. Ground Connection Connect the grounding cable directly to the protective grounding pins 9 and 10 (PGND) in the main power-in connector
(see TB1 in Figure 9). Power Connections The unit can be connected directly to a 9-30V DC source through the main Power-In connector
(see Figure 9) where Pin #1 is + (positive) and Pin #2 is (negative). It is recommended to connect the main power supply to the unit with a 3.5 amp fuse on the cable. Backup Battery Connection The RTU has a special chamber for 3 C alkaline backup batteries (not supplied) that are used to retain the units RAM and Real Time Clock in power fail situations. Internal Radio Connection - antenna The internal radio is connected through the 14-pin connector on the Main board inside the plastic housing. Its power is driven from that connector. When an internal radio is installed, Port 3 of the radio cannot be used. External Radio Connection Connect the external radio to Port 3 (see Figure 9). Verify that the radio button is set to ON. The radio signals are driven from the AUX connector in Figure 9. It is recommended to replace the external radio only when the unit is powered off. 7 Installation If the external radio is connected to an outside power supply, first power on the unit, and then power on the radio. The auxiliary power supply (maximum 2A) can be changed to 6V, 6.5V, 7.5V, 8V, 9V or 9.6V DC by changing the setting of the P11 jumper located on the Main board. (See markings on the board.) To set the power to 8V, remove the jumper and save for future use. This is usually set in the factory according to the external power supply of the radio. The default setting is 9V DC. To change the voltage, follow the disassembly instructions in Appendix C, place the jumper and reassemble. Line Communication Connection Line Communications are connected through Ports 1 or 2 (see Figure 9.) Port 1 can be programmed as RS485 (1A) or RS232 (1B). Port 2 can be programmed as RS232. 8 Installation Installation of Backup Batteries The backup battery should not be installed before the unit is connected to the main power supply. This may cause the battery to drain. 1. Place 3 C size alkaline batteries into the carton cylinder, each in the same direction, as shown in Figure 7 below. Figure 7 Backup Battery Cylinder and 3 Backup C Batteries 2. Place the cylinder with the batteries into the battery case in the direction indicated on the unit (see Figure 8 below). Figure 8 Installation of Backup Batteries 9 Installation Miscellaneous Open the Case Door To open the case door properly, press the two clips (latches) and pull the wing to an open position. The cable cover is opened counter-clockwise to expose the cable connections and the backup battery cover is opened clockwise to expose the battery housing. Close the Case Door To close the case door properly, press until the latch clicks. Note that if the batteries in the housing are not inserted properly, the backup battery cover door may not close. If the cable connections are not threaded properly through the cable holes, the cable cover may not close. Antenna Placement The antenna is connected to the internal radio through the snap hole on top of the plastic housing (see Figure 9). For models with external radios, screw the antenna onto the radio antenna connector. An antenna placed on top of the plastic housing produces strong electromagnetic fields that could be harmful to the electronics of the MOSCAD-M RTU and to people in the vicinity. Fixed Site Antennas The antenna installation must comply with the following requirements in order to assure optimal performance and make sure human exposure to radio frequency electromagnetic energy is within the guidelines set forth by the local regulations. The antenna must be mounted outside the building. Mount the antenna on a tower if at all possible. As with all fixed site antenna installations, it is the responsibility of the licensee to manage If the antenna is to be mounted on a building, then it must be mounted on the roof. the site in accordance with applicable regulatory requirements. This may require additional compliance actions such as site survey measurements, signage, and site access restrictions in order to ensure that exposure limits are not exceeded. 10 THE MOSCAD-M UNIT Overview The MOSCAD-M RTU (shown below) contains power connections, line communication ports, internal/external radio interfaces, radio modems and I/Os. Figure 9 MOSCAD-M Unit 11 Communication Ports The MOSCAD-M Unit The MOSCAD-M RTU has 3 ports available:
PORT 1 -
RS232 Configurator Port (for programming and monitoring the unit), RS232 External Dialup Modem, or RS485 Communication, User protocol
(1A is used for RS485)
(1B is used for RS232) Secondary Port RS232 (User protocol) External Radio interface PORT 2 PORT 3 Ports 2 and 3 can work simultaneously with each other and with either Port 1A or Port 1B. Ports 1A and 1B cannot work simultaneously. Port 3 cannot be used when an internal radio is installed. Connectors The MOSCAD-M RTU has the following connectors available (see Figure 9):
RS485 Port 1A (RJ45, 4 pin) RS232 Port 1B (RJ45, 8 pin) RS232 Port 2 (RJ45, 8 pin) External Radio Port 3 (RJ45, 8 pin) AUX out for external radio power supply (2 pin) Power In/Solid State DO (10 pin) - TB1 DO (10 pin) TB2 DO/DI (10 pin) TB3 DI (10 pin) TB4 DI/AO (10 pin) TB5 AI (10 pin) - TB6 The MOSCAD-M RTU has the following internal connectors. Internal radio connector (14 pin) Backup Battery connector (2 pin) I/O Expansion connector (26 pin) Controls and Indicators The push-button is used to activate the LED panel, to toggle the LED panel so that it displays the status of the CPU or of the I/Os, to initiate software downloading to the CPU, and to erase User Flash memory and RAM. 12 The MOSCAD-M Unit LED Control Display On/Advance When the display is off, pressing the push-button once, momentarily, activates the display. Every consecutive momentary depression of the push-button advances the display to the next page, in the following order: CPU > IO1 (I/O Page 1-DI) > IO2 (I/O Page 2-DO) > IO3
(I/O Page 3-AI) > Page 4 (AO) > Page 5 (User Application Controlled) > Page 6 (Hardware Test Controlled). The next depression of the push-button returns the display to the CPU. Display Off The display can be programmed using the Configurator Site Configuration tool to turn off automatically after a predefined period of time if the push-button has not been pressed. LED Test When the push-button is pressed continuously for a few seconds, all LEDs light up simultaneously. When the push-button is released, the LEDs turn off. User Flash Erase After power-up, all LEDs light up. To erase the User Flash, press the push-button while the LEDs are lit. All the LEDs flash three times. Now, release the push-button. Alternatively, press the push-button continuously for at least 40 seconds at any time to erase the User Flash. User RAM Erase (Cold Restart) Turn off the power supply, while the push-button is depressed. The next time the unit is powered up, it will perform cold restart, which means all data stored in the RAM is erased. Note: The data that is stored in the Flash (i.e. applications, site configuration, and network configuration) will not be erased. System Software Downloading During power up, press the push-button continuously. This will cause the unit to enter bootstrap downloading mode, in which the FLASH is programmed from a PC connected to Port 1 of the MOSCAD-M. The CPU LED will begin to blink at 1 Hz, indicating that the CPU has entered bootstrap downloading mode. If after 120 seconds no bootstrap software is loaded and executed, the normal power-up procedure is performed. CPU Reset To reset the CPU when a backup battery is not installed, turn the power supply to the unit off and on again. When a backup battery is installed, follow the Cold Restart method described above. 13 The MOSCAD-M Unit LED Display Indications A 5 4 matrix of LEDs is used for diagnostics and testing of the unit (see Figure 10). The top row indicates to which page or toggle (CPU, IO1, IO2, IO3, Page 4, Page 5, Page 6) the LED panel is set. To advance from one page to another, press the push-button once quickly. The first depression of the push-button activates the display. Subsequent short depressions of the push-button advance the display to the next page: CPU > IO1 (I/O Page 1-DI) > IO2 (I/O Page 2-DO) > IO3 (I/O Page 3-AI) > Page 4 (AO) > Page 5 (User Application Controlled) > Page 6
(Hardware Test Controlled). In each page, the LEDs have different functions, as described in the charts below. CPU IO1 IO2 IO3 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Figure 10 LED Panel CPU Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the initial CPU
(Page 0) toggle or display (CPU LED on). Name CPU IO1 IO2 IO3 LED 1 LOAD LED 5 CONF LED 9 APPL On/Off On:
Flashing:
Function/Indication Display is in CPU mode. CPU is in bootstrap mode OR FPGA is not loaded correctly. Off Off Off On On On A file (e.g. configuration, application program) is being downloaded to FLASH memory. A Site configuration definition has been loaded into FLASH memory. An application program has been loaded into FLASH memory. 14 On/Off Function/Indication The MOSCAD-M Unit On On On On On On On On On On On On On Controlled by application for user use. The CPU is in Reset mode. An error has occurred. The backup battery does not exist or has reached a critical level of 3.5V. The RTU is transmitting data via Port 1. The RTU is receiving data via Port 1. The communication channel used by Port 1 is busy. The RTU is transmitting data via Port 2. The RTU is receiving data via Port 2. The communication channel used by Port 2 is busy. The RTU is transmitting data via Port 3. The RTU is receiving data via Port 3. The communication channel used by Port 3 is busy. Name LED 13 MON LED 2 RST LED 3 ERR LED 4 BATT LED 6 TX1 LED 7 RX1 LED 8 CM1 LED 10 TX2 LED 11 RX2 LED 12 CM2 LED 14 TX3 LED 15 RX3 LED 16 CM3 15 IO1 Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the IO1
(Page 1) toggle or display (IO1 LED on). The MOSCAD-M Unit Name CPU IO1 IO2 IO3 LED 1 LED 2 LED 3 LED 4 LED 5 LED 6 LED 7 LED 8 LED 9 LED 10 LED 11 LED 12 LED 13 LED 14 LED 15 On/Off Off Flashing:
On Off Off On On On On On On On On On On On On On On On Function/Indication FPGA is not loaded correctly. Display is in IO1 page. DI1 is on. DI2 is on. DI3 is on. DI4 is on. DI5 is on. DI6 is on. DI7 is on. DI8 is on. DI9 is on. DI10 is on. DI11 is on. (Can be fast counter) DI12 is on. (Can be fast counter) DI13 is on. (Models with expansion board only) DI14 is on. (Models with expansion board only) DI15 is on. (Models with expansion board only) The LED is not updated after each change in DI status, but rather after the user performs a scan. Thus, the status of the DI reflects the status as of the last software scan. 16 IO2 Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the IO2
(Page 2) toggle or display (IO2 LED on). The MOSCAD-M Unit Name CPU IO1 IO2 IO3 LED 1 LED 2 LED 3 LED 4 LED 5 LED 6 LED 7 LED 8 LED 9 LED 10 On/Off Off Flashing:
Off On Off On On On On On On On On On On Function/Indication FPGA is not loaded correctly. Display is in IO2 page. DO1 is set. DO2 is set. DO3 is set. DO4 is set. DO5 is set. DO6 is set. DO7 is set. DO8 is set. Solid State 1 (AI wetting) is set. Solid State 2 (DI wetting) is set. 17 The MOSCAD-M Unit IO3 Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the IO3
(Page 3) toggle or display (IO3 LED on). Each AI has two LEDS which represent its status
(underflow or overflow). When both LEDS are lit, that means that this specific AI is not calibrated. Name CPU IO1 IO2 IO3 LED 1 LED 2 LED 3 LED 4 LED 5 LED 6 LED 7 LED 8 LED 9 LED 10 LED 11 LED 12 LED 13 LED 14 LED 15 LED 16 On/Off Off Flashing:
Off Off On On On On Off On On On Off On On On Off On On On Off Function/Indication FPGA is not loaded correctly. Display is in IO3 page. AI1 Overflow. AI1 Underflow. AI1 is uncalibrated. AI1 measures Current. (If AI1 is On, it measures Voltage.) AI2 Overflow. AI2 Underflow. AI2 is uncalibrated. AI2 measures Current. (If AI2 is On, it measures Voltage.) AI3 Overflow. AI3 Underflow. AI3 is uncalibrated. AI3 measures Current. (If AI3 is On, it measures Voltage.) AI4 Overflow. AI4 Underflow. AI4 is uncalibrated. AI4 measures Current. (If AI4 is On, it measures Voltage.) 18 AO Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the AO
(Page 4) toggle or display (CPU and IO1 LEDs on). The MOSCAD-M Unit Name CPU IO1 IO2 IO3 LED 1 LED 2 LED 3 LED 4 LED 5 LED 6 LED 7 LED 8 LED 9 LED 10 LED 11 LED 12 LED 13 LED 14 LED 15 LED 16 On/Off Function/Indication On On Off Off On On On Off Off Off Off Off Off Off Off Off Off Off Off Off Display is in AO page. AO1 Voltage. AO1 Current. AO1 is uncalibrated. 19 The MOSCAD-M Unit User Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the User
(Page 5) toggle or display (CPU and IO2 LEDs on). The LEDs are controlled by the user C Application. Name CPU IO1 IO2 IO3 LED 1 LED 2 LED 3 LED 5 LED 6 LED 7 LED 9 LED 10 LED 11 LED 13 LED 14 LED 15 LED 16 On/Off Function/Indication On Off On Off On On On On On On On On On On On On On User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled User Controlled The user may choose to define the functions of the diagnostic LEDs in an application program. The display returns from a user-defined toggle to the CPU toggle when the push-button is pressed or as a result of a C command. (See C Toolkit for MOSCAD Family RTUs manual.) 20 Hardware Test Page LED Functions The following table describes the functions of the diagnostic LEDs when set to the Hardware Test (Page 6) toggle or display (CPU and IO3 LEDs on). The LEDs are controlled by the Hardware Test utility of the MOSCAD-M Configurator. The MOSCAD-M Unit Name CPU IO1 IO2 IO3 LED 1 LED 2 LED 3 LED 5 LED 6 LED 7 LED 9 LED 10 LED 11 LED 13 LED 14 LED 15 On/Off Function/Indication On Off Off On On On On On On On On On On On On On Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled Hardware Test Controlled 21 The MOSCAD-M Unit I/Os (All Models) Wetting switch connection (x2) Two solid state (SS1, SS2) Digital Outputs are provided for wetting/supply voltage control of the DI, AI, or external devices. They are connected to the Power In TB1 (pins 3-8) and can drive up to 400mA each. The switches are equipped with over-current protection, limiting the current driven through each of them to 400 mA maximum. Figure 11 shows how the solid state DOs are to be connected. It is recommended that the wetting power be connected to the solid state output with a fuse of 1 amp. Figure 11 Main Board Solid State Digital Output I/O Connection 22 DO Magnetic Relay connection (x4) Four magnetically latched Digital Outputs are connected to TB2. They can drive up to 2A. Figure 12 shows how the DOs are to be connected. The MOSCAD-M Unit Figure 12 Main Board Magnetically Latched Digital Output I/O Connection DO Open Collector (x4) Four open collector Digital Outputs are connected to TB2/TB3. The DOs can sink a current of up to 500mA. They are divided into two groups of two, each with a common ground. Figure 13 shows how the DOs are to be connected Figure 13 Main Board Open Collector Digital Output I/O Connection 23 DI (x12) Twelve wet Digital Inputs are connected to TB3-TB5. Three of these (DI1-DI3) may be used as Wakeup events for the RTU. DI11-DI12 can be used to count pulses of up to 10KHz. They count the rising edge of the pulse. They can also show the actual state of the DI (On/Off). Figure 14 shows how the DIs are to be connected. The MOSCAD-M Unit Figure 14 Main Board Digital Inputs I/O Connection 24 The MOSCAD-M Unit Additional I/Os (Expanded I/O Models only) AI (x4) Four Analog Inputs are connected via TB6. (See Figure 9.) The AIs are 4-20mA or 0-5V. Each AI has a jumper which determines the measurement. If the jumper is placed (closed), the AI is set up to measure current (4-20mA). If it is not placed (removed), it measures voltage
(0-5V). The jumpers are placed in the factory based on customer order. If the status of the jumpers is changed, the AI Type must be changed accordingly in the Hardware Test tool of the MOSCAD-M Configurator. See Configurator help. Four options are available for the AI expansion configuration. The default AI setup of all MOSCAD-M PLUS radios will be 4-20mA (no option is required.) Options Default V741 V742 V743 V744 AI2 AI1 4-20mA 4-20mA 4-20mA 4-20mA 4-20mA 4-20mA 4-20mA 0-5V 0-5V 0-5V AI4 AI3 4-20mA 4-20mA 4-20mA 0-5V 0-5V 0-5V 0-5V 0-5V 0-5V 0-5V A label on the plastic housing will specify the AI setup. If, for some reason, the jumpers need to be changed, the RTU must be disassembled. For instructions, see Appendix C. Figure 15 shows how the AIs are to be connected. Figure 15 Expansion Board Analog Input (Voltage/Current) I/O Connection 25 The MOSCAD-M Unit AO (x1) One Analog Output is connected to TB5. The AO is 0-20mA or 0-5V. The AO type (current or voltage) is determined by connecting to the proper pin on the TB and by selecting the proper AO type in the software (either via the Configurator Hardware Test utility or the user software application.) The AO can be driven from an internal or external power supply. The minimum output resistance for voltage is 5K. The maximum output resistance for current is as shown below:
Current Output Maximum Output Power Supply Internal Internal Internal External (24VDC) External (24VDC) External (24VDC) 8VDC 6VDC 9VDC 23-30VDC 22VDC 20VDC Resistance 120 100 250 750 700 Max 600 The figure below shows how the AO is to be connected. Figure 16 Expansion Board Analog Output I/O Connection 26 DI (x3) An additional 3 wet Digital Inputs are connected via TB5. Figure 17 shows how the DIs are to be connected. The MOSCAD-M Unit Figure 17 Expansion Board Wet Digital Input I/O Connection 27 Pin Assignment - Main Board TBs The following charts indicate the function of each pin in the various terminal blocks (TBs) on the Main board as shown in Figure 9. The MOSCAD-M Unit Function TB1
(Power) Pin #
1 2 3 4 5 6 7 8 9 10 Vin +
Vin -
SS1in SS1out SS1gnd SS2in SS2out SS2gnd PGND PGND Function TB3
(DO/DI) Pin #
1 2 3 4 5 6 7 8 9 10 COM DO5, DO6 DO7 DO8 COM DO7, DO8 DI1 DI2 DI3 COM DI1-DI3 DI4 DI5 Function DO1A in DO1B out DO2A in DO2B out DO3A in DO3B out DO4A in DO4B out DO5 (OC) DO6 (OC) Function DI6 DI7 COM DI4-DI7 DI8 DI9 DI10 COM DI8-DI10 DI11 DI12 COM DI11-DI12 TB2
(DO) Pin #
1 2 3 4 5 6 7 8 9 10 TB4
(DI) Pin #
1 2 3 4 5 6 7 8 9 10 28 Pin Assignment - Expansion Board TBs The following charts indicate the function of each pin in the various terminal blocks (TBs) on the Expansion board as shown in Figure 9. The MOSCAD-M Unit Function TB5
(DI/AO) Pin #
Function TB6
(AI) Pin #
1 2 3 4 5 6 7 8 9 10 DI13 COM DI13-DI14 DI14 DI15 PGND Vin +
Vin -
Iout COM AO Vout 1 2 3 4 5 6 7 8 9 10 PGND AI1 +
AI1 -
AI2 +
AI2 -
AI3 +
AI3 -
AI4 +
AI4 -
PGND Backup Battery Below 8.9V DC, the unit enters Low Power Sleep mode. As long as the input power is above 6V DC, the unit is still powered from the main power supply input. If the input power drops below 6V DC, the unit will use the backup battery to preserve the contents of the RAM and Real Time Clock (RTC) data. In this case, the unit is in Low Power Sleep mode and not in Reset mode. This means that the status of outputs 1 to 8 is preserved. The battery will retain the data for at least 70 days (cumulative). Power consumption from the backup battery will be <5mA @ 4.5V DC. If no backup battery is detected, or if the backup battery falls below 3.1V DC (power fail), the unit will shut down until power is restored. In this case, the RAM and Real Time Clock
(RTC) data will not be retained. LED 4 (BATT) will indicate when the backup battery voltage drops below 3.5V. This indication is also available for the user application. Under these circumstances, the SS1 and SS2 Solid State switches are turned off even if they were set to independent operation mode. 29 The MOSCAD-M Unit Power Supply The MOSCAD-M can be operated from an input of 9-30V DC. The minimum input level is determined by the output voltage level required for the AUX/Internal radio. The table below describes the minimum input levels for the different settings:
Output Power 6 6.5 7.5 8 9 9.6 Minimum Input Power 9 9 9 10 10.5 11.5 The AUX/Internal radio power is set by a jumper on the Main board. The table below describes the different models with their default settings from the factory:
Model F4570A F4571A F4572A F4573A F4574A F4575A F4580A F4581A F4582A F4583A F4584A F4585A Output Power 9.6 9 9 7.5 7.5 7.5 9.6 9 9 7.5 7.5 7.5 Minimum Input Power 11.5 10.5 10.5 9 9 9 11.5 10.5 10.5 9 9 9 30 POWER MANAGEMENT Overview The MOSCAD-M includes a Power Management feature which is controlled by the user application. The unit can operate in four power save modes:
Power Management Disabled (in which the entire system is operational and no power saving technique is used) Run mode (in which the entire system is operational and power is provided only to active ports of the unit) Idle Sleep mode (in which the unit uses low power) Low Power Sleep mode (in which the unit is basically off) When the MOSCAD-M is powered up, it operates in Run mode. If all application and system tasks are idle, and the Power Management Feature is enabled, the RTU will enter Idle Sleep mode in order to conserve power. The unit will return to Run mode if one of several Wakeup events occurs. If the input power falls below 8.9V, the unit automatically enters Low Power Sleep mode. The unit will return to its previous mode (Run or Idle Sleep) when the input power returns to at least 9.3V. The Power Management Feature, which is disabled by default, can be enabled by the user application. Run Mode In Run mode, tasks will execute, suspend and exit, as necessary. In order to execute, each application and system task will request a visa from the visa manager. When the task suspends or exits, its visa is returned. If all visas in the system have been returned, the unit can enter Idle Sleep mode. A task can choose to operate without a visa; however, it may be forced into Idle Sleep mode by the system when all other tasks have returned their visas. Before a task suspends itself, it will define those Wakeup events which will cause it to wake up. When the requested Wakeup event occurs, the task will receive a signal and awaken (even if the Power Management feature is disabled.) If one of these events occurs while the system is in Run mode, it will prevent the system from entering Idle Sleep mode. Total power consumption from the main power supply in Run mode is at most 150mA @ 14V DC. Typically, power consumption will be 50mA. The additional power consumed by the radio in Run mode depends on the radio type and will be at least 40mA. 31 Power Management Sleep Mode Idle Sleep - All system and application tasks are idle. The MOSCAD-M will enter Sleep mode in the following situations:
Low Power Sleep - The main power supply falls below 8.9V. Power consumption is minimized by switching off the power of all non-active circuits and devices (communications inputs and outputs, etc). In Sleep mode, the units power consumption will be <5mA @ 14V DC. In Sleep mode, the current consumption is <5mA. However, the power consumption will be significantly higher if the AO is enabled or the radio port is defined as a Wakeup event. If Port 3 is enabled in Sleep mode, the power consumption will be 30mA and the radio power consumption will be at least 40mA, for a total of at least 70mA. When entering Idle Sleep mode, the following power supplies are disabled:
Radio/auxiliary power supply AI power supply AO power supply SS1 and SS2 switches power supply 3.3V Peripheral power supply Port 1 UART, Port 2 UART power supply One or more of these power supplies might be left active, depending on the type of Wakeup events that are selected. (See Wakeup events below.) The AO power supply will not be disabled in Idle Sleep mode if a value is set in the AO. By default, The solid state SS1 and SS2 switches are controlled by the Power Management feature. However, it is possible to configure them to an independent operation mode where they are controlled
(enabled/disabled) by the user application only. If the unit enters Low Power Sleep mode, SS1 and SS2 will be turned off even if set to independent operation mode. If one of several preprogrammed Wakeup events occurs, the unit will return from Idle Sleep mode to Run mode. Those tasks which requested the Wakeup event will wake up and any other tasks will remain suspended. If, however, the unit is in Low Power Sleep mode, it will not respond to Wakeup events. When a power level of 9.3V is restored at the power input, the unit will revert to its previous mode. 32 Wakeup Events Power Management When enabling the Power Management feature, the MOSCAD-M user should configure those Wakeup events that will wake up the unit from Idle Sleep mode. The possible Wakeup events are:
DI Wakeup When a Change of State occurs in DI1 and/or DI2 and/or DI3, a Wakeup event is generated. Push-Button Wakeup Pressing the push-button when the unit is in Idle Sleep Mode will cause a Wakeup event.
(The push-button is enabled at all times.) The unit will enter Run mode for at least 30 seconds. Communication Port Wakeup A signal received at one of the units three ports, if designated by the user as a Wakeup event, will cause the unit to wake up. Port 1 Wakeup: when data stream is received. Port 2 Wakeup: when data stream is received. Port 3 Wakeup: when an indication for an active channel (channel monitor) is received. Periodic (Internal) Wakeup The Real Time Clock (RTC) will cause the unit to wake up every 5 minutes to reset the watchdog timer. The user application can request a wakeup after a certain period of time or upon receipt of a specific Wakeup event. This will then cause the system tasks (and the unit) to wake up and the unit to return to Run mode. See the C Toolkit for MOSCAD Family RTUs manual (68P02956C75) for details on the system functions which provide these services to the application. For more information on the Power Management Feature, see the MOSCAD-M RTU Configurator Users Guide (68P02961C55). 33 ETHERNET INTERFACE OPTION Overview The Ethernet interface option is used as a communication link for the MOSCAD-M units with Local Area Networks (LAN). The Ethernet interface option supports TCP/IP protocol on a Twisted Pair (TP) connector, with automatic polarity correction. External Ethernet Interface Unit Enclosed in a plastic box, the external Ethernet Interface unit provides an RS232 port for connection of MOSCAD units to LAN. The external Ethernet unit is powered by 9-15V DC and has indication LEDs on its front panel. The system software of the external Ethernet unit can be upgraded using the Ethernet Interface Downloader program. The following figure depicts the front panel of the Ethernet unit. 12V DC (9-15V) Power inlet Power LED RS232 Connector to RTU RST - Reset DIAG - Diagnostics Data Present Ethernet indication LEDs Ethernet twisted pair connector RS232 indication LEDs Figure 18 External Ethernet Unit Front Panel The Ethernet indication LEDs are:
TX - Ethernet Transmit RX - Ethernet Receive LI - Ethernet Link Integrity The RS232 indication LEDs are:
TX - RS232 Transmit RX - RS232 Receive CM - RS232 Channel Monitor 34 Installation The unit can be connected to Port 1 or Port 2 of the MOSCAD-M RTU. (See Figure 9.) Connections Ethernet Interface Option To connect the external Ethernet Interface unit, proceed as follows:
1. Connect the communication cable (FKN5953A) between the external Ethernet Interface unit RS232 Port (P2) and the MOSCAD-M RS232 port (Port 1B or Port 2). If the communication cable is not long enough (80 cm) for external connections, use a longer cable. 2. If no radio is attached to the MOSCAD-M, connect the power cable (FKN4465A) between the Ethernet unit power inlet and the AUX DC connector on the MOSCAD-M. Make sure that the AUX DC is configured to 9V DC and above, as described in the External Radio Connection section of the Installation chapter. If a radio (internal or external) is attached to the MOSCAD-M, connect the Ethernet unit power inlet to an external 9-15V DC power supply using the external power cable FKN4090A (not supplied). 3. Connect the Ethernet Interface unit Ethernet Port (P1) to the LAN, using an Ethernet twisted pair shielded cable. Install a Suppression Core (Fair-Rite) P.N. 0443164151 on the cable as shown below. MOSCAD-M RTU 9V DC from the AUX DC outlet in MOSCAD-M Ethernet Unit Use Port 1 or Port 2 RS232 connectors FKN5953A FKN4465A To LAN Figure 19 Connection of External Ethernet Unit to MOSCAD-M RTU (without radio) 35 APPENDIX A: CABLES AND ADAPTERS General This appendix provides supplementary data on cables and adapters used in various MOSCAD-M systems. The following applications are covered:
RTU-to-Computer/Terminal Connections RTU-to-Modem Connections RTU-to-RTU Connections RTU-to-Computer/Terminal Connections For a 25-pin or 9-pin D-type connector, use the FLN6457 cable kit, in order to connect one of the RTU RS232 ports to a computer or terminal. The kit includes a cable with RJ45 modular jacks on both ends, an RJ45 to 25-pin female D-Type adapter, and an RJ45 to 9-pin D-Type adapter. When the connector is facing upwards, the left-hand pin is Pin No. 1, and the right-hand pin is Pin No. 8. J2
(25-Pin D-Type) 2 3 Tx DATA Rx DATA 4 5 6 7 20 7 RTS CTS DSR GND DTR Rec Line (DCD) RJ45 Connector J1
(RJ45) Tx DATA Rx DATA RTS CTS DSR GND DTR Rec Line (DCD) 2 1 5 8 7 4 3 6
(9-Pin D-Type)
(3)
(2)
(7)
(8)
(6)
(5)
(4)
(1) Figure 22 RJ45-to-D-Type Female Connector Adapter 36 Appendix A: Cables and Adapters RTU-to-Modem Connections Only R&TTE approved modems should be used to connect the RTU to the PSTN. RTU-to-Modem Asynchronous Connection For a 9-pin or 25-pin connection, use the FLN6458 cable kit to connect one of the MOSCAD-M RTU RS232 ports asynchronously to a modem. (The RTU serves as DTE.) The kit includes a cable with RJ45 modular jacks on both ends and an RJ45 to 9-pin and 25-pin male D-Type adapter (see Figure 21). The possible RTU configurations are detailed below:
Port No. Configurator Definition 1 RS-232 UART External Dialup Modem (MDLC) 1. Before transmitting, the RTU sends an RTS=on signal to the modem, and will not transmit unless it receives a feedback CTS=on signal from the modem. 2. The RTU will not receive unless it receives a DCD=on signal from the modem. 3. When using a modem in auto-answer mode (connected to a computer port) for remote service, the RTU does not support the RTS/CTS protocol, as the port is designed to operate with a local computer as well as with a modem. When the connector is facing upwards, the left-hand pin is Pin No. 1, and the right-hand pin is Pin No. 8. RJ45 Connector J1
(RJ45) Tx DATA Rx DATA RTS CTS GND DTR Rec Line (DCD)
+12V 1 2 6 3 4 8 5 7 NOT USED
(9-Pin D-Type)
(3)
(2)
(7)
(8)
(5)
(4)
(1) Figure 21 RJ45-to-D-Type Male Connector Adapter 37 J2
(25-Pin D-Type) 2 3 Tx DATA Rx DATA 4 5 7 20 8 RTS CTS GND DTR Rec Line (DCD) Appendix A: Cables and Adapters RTU-to-RTU Connection RTU-to-RTU Asynchronous Communications Connection This section provides data on the cable (not supplied) recommended for the RTU-to-RTU RS232 asynchronous interconnection (refer to Figure 22). The following table defines the RTU port for this connection type. Port No. Configurator Definition 1B 2 RS-232 UART RTU-to-RTU (MDLC) RS-232 UART RTU-to-RTU (MDLC) When the connector is facing upwards, the left-hand pin is Pin No. 1, and the right-hand pin is Pin No. 8. RJ45 Connector J1
(RJ45) 1 2 3 4 5 6 7 8 Tx DATA Rx DATA CTS GND DCD RTS
+12V DTR J2
(RJ45) 1 2 3 4 5 6 7 8 Tx DATA Rx DATA CTS GND DCD RTS
+12V DTR NOT CONNECTED NOT CONNECTED Figure 22 RTU-to-RTU RS232 Asynchronous Communications Cable 38 APPENDIX B: MODELS AND ACCESSORIES General The chart below describes the models, options and accessories available. MOSCAD-M RTU Models MOSCAD-M with Interface to External Radio MOSCAD-M with 4W 403-433 MHz Internal Radio MOSCAD-M with 4W 438-470 MHz Internal Radio MOSCAD-M with 5W 136-174 MHz External Radio MOSCAD-M with 4W 403-470 MHz External Radio MOSCAD-M with 4W 470-512 MHz External Radio MOSCAD-M Plus with Interface to External Radio MOSCAD-M Plus with 4W 403-433 MHz Internal Radio MOSCAD-M Plus with 4W 438-470 MHz Internal Radio MOSCAD-M Plus with 5W 136-174 MHz External Radio MOSCAD-M Plus with 4W 403-470 MHz External Radio MOSCAD-M Plus with 4W 470-512 MHz External Radio MOSCAD-M Options ENH: Set radio to: HT750 ENH: Set radio to: GP140 ENH: Set radio to: GP328 ENH: Set radio to: PRO5150 ALT: Set 4AI to: 3 x 4-20mA & 1 x 0-5V ALT: Set 4AI to: 2 x 4-20mA & 2 x 0-5V ALT: Set 4AI to: 1 x 4-20mA & 3 x 0-5V ALT: Set 4AI to: 4 x 0-5V Model F4570 F4571 F4572 F4573 F4574 F4575 F4580 F4581 F4582 F4583 F4584 F4585 Option V951 V952 V953 V954 V741 V742 V743 V744 39 Appendix B: Models and Accessories Miscellaneous Accessory ADD: MOSCAD-M Installation Kit for GP/HT/PRO Radios V154 ADD: MOSCAD-M Installation Kit for HT1000 Radio ADD: DIN Rail ADD: Bracket for Ethernet Unit FLN3010 V153 V020 V056 Programming Tools MOSCAD-M Configurator MOSCAD Family C Toolkit Software MOSCAD-M Debug Kit (C Toolkit) Model F4560 F4561 FLN3012 40 Appendix B: Models and Accessories Installation of MOSCAD-M with GP140/328/HT750/PRO5150 Radio MOSCAD-M models which are equipped with GP140, GP328, HT750 or PRO5150 radios should be connected as shown below. If your MOSCAD-M model does not include one of these radios, the MOSCAD-M Installation Kit for GP140/GP328/HT750/PRO5150 Radios can be purchased. The radio is then connected as shown below. GP140/GP328/HT750/PRO5150 Radio BNC Adapter HLN9756A Audio Accessory Adapter HLN9716B Mounting Bracket (Kit FCN5516A) DC Power Cable FKN4465A Audio Communication Cable FKN8023A Figure 23 Connection of MOSCAD-M to GP140/328/HT750/PRO5150 Radio Secure the Mounting Bracket to the DIN Rail. Attach the radio to the Mounting Bracket using snaps. Route the Audio Communication Cable from the PORT 3 connector of the MOSCAD-M to the Audio Accessory Adapter. Plug in and tighten the connector. Route the DC Power Cable from the AUX. DC connector of MOSCAD-M to the Mounting Bracket and plug in the connector. Make sure the AUX power is set to 7.5V DC. Set the middle knob (channel select knob) to Channel 1. Use the BNC Adapter to connect an external antenna to the radio. 41 Appendix B: Models and Accessories MOSCAD-M Installation Kit for GP140/GP328/HT750/PRO5150 Radios The MOSCAD-M Installation Kit for GP140/GP328/HT750/PRO5150 Radios enables users to install a GP140, GP328, HT750 or PRO5150 radio (externally) to the MOSCAD-M. The Installation Kit includes:
Mounting Bracket (FCN5516A) Audio Communication Cable (FKN5953A) Audio Accessory Adapter (HLN9716B) DC Power Cable (FKN4465A) BNC Adapter (HLN9756A) DIN Rail Radio Connectors (Part #0786144U05) See Figure 23 for connection details. MOSCAD-M Debug Kit The MOSCAD-M Debug kit enables the user to debug a C application using the XRAY debugger. Set up the MOSCAD-M Configurator PC as described below, then follow the debugging instructions in the C Toolkit for MOSCAD Family RTUs manual. MOSCAD-M Board The kit consists of a special MOSCAD-M board, specifically built for debugging. The system software (system.krl) is burned into the flash memory at the factory. Another system file
(MmxyyD2.krl) is available with the Debug System Installation (FVN9779) MOSCAD-M Configurator and must be downloaded before using the Microtec XRAY debugger. The debug board has no plastic housing and all components are visible. Next to the push-
button there are two additional buttons which do not exist in the standard MOSCAD-M. The leftmost button is Reset. The rightmost button is NMI (Non Masked Interrupt). The NMI (or CTRL+C from the PC keyboard) will stop the program. Two megabytes of RAM are installed in the debug board to enable downloading the system software from the PC to the unit. 42 Debug Setup Appendix B: Models and Accessories By default, downloading from the PC to the unit is done via Port 2. When the unit is first powered up, LED 12 (CM2) should be lit, indicating that the debugger should be downloaded via Port 2. In order to connect to Port 1, a modified system file must be downloaded to the flash. This file is available from the factory. To set up the system for debugging, do as follows:
a) Compile and link your application using Microtec tools. b) Connect the MOSCAD-M Configurator to the debug board as you would the standard MOSCAD-M board. c) In the Site Configuration utility, set Port 2 to Not Used. d) Download the site configuration. e) Connect Port 1 of the RTU to the COM port of the PC. f) Switch off the RTU, then switch it on again, while the push-button is pressed. The system will then be in bootstrap mode where a new system can be downloaded. g) If a communication session is open with the RTU, make sure to use the Stop Communication utility in the Configurator. h) In the Downloader utility, make sure the proper PC COM port is specified in the download session and download the system file using the MMxyyD2.KRL file. The .krl file, which is found in the C:\MConf150\system directory when the debug system is installed, downloads the corresponding system and kernel files to the RTU. i) Make sure that the CM2 LED is lit, indicating that the port is ready to communicate with the Microtec debugger. j) Connect Port 2 of the RTU to the PC COM port on which the XRAY debugger runs. k) Copy the include file (e.g. MM_V100.inc) which suits your MOSCAD-M version into the directory. Compile and link your source files. l) Use the MCDEBUG.BAT file to load the C application into the RAM. m) Follow the debug instructions in the C Toolkit for MOSCAD Family RTUs manual. If the unit is powered off or if the main power input falls below 3.1V DC, the RAM data will not be retained and the debugger will have to be downloaded again. 43 Appendix B: Models and Accessories Logic Analyzer The MOSCAD-M debug board can be connected to a Logic Analyzer in order to perform sophisticated debugging. The Logic Analyzer is used when it is necessary to see what is running on the data and address bus. This is generally in extreme cases where the memory is corrupted and the problem cannot be found using the debugger capabilities. The Logic Analyzer is connected to the board through connectors P12, P13, and P14 on the upper right-hand side of the board. These connectors (Motorola part # 2808044H09) are not provided with the MOSCAD-M board and must be ordered separately and assembled. The pins of the connection cable should be configured according to the Pin Assignment below. Once the pins are configured, the cables should be connected from the Logic Analyzer to the connectors on the board. Pin Assignment Logic Analyzer TBs The following charts indicate the function of each pin in the various connectors. P12 Pin #
Function P12 Pin #
Function 1 2 3 4 5 6 7 8 9 10 NC NC PG0_DTACK Address bus Add bit 15 Address bus Add bit 14 Address bus Add bit 13 Address bus Add bit 12 Address bus Add bit 11 Address bus Add bit 10 Address bus Add bit 9 11 12 13 14 15 16 17 18 19 20 Address bus Add bit 8 Address bus Add bit 7 Address bus Add bit 6 Address bus Add bit 5 Address bus Add bit 4 Address bus Add bit 3 Address bus Add bit 2 Address bus Add bit 1 PG1_A0 GND 44 Appendix B: Models and Accessories P13 Pin #
Function P13 Pin #
Function 1 2 3 4 5 6 7 8 9 10 EMUCS EMUIRQ HIZ Data bit 21 Flash chip select
(CSA0) UDS signal LDS signal LWE_LB signal UWE_UB signal RW signal 11 12 13 14 15 16 17 18 19 20 EN_OF signal RESET signal CSB1 - upper RAM chip select CSB0 - lower RAM chip select Data bus D20 Data bus D19 Data bus D18 Data bus D17 Data bus D16 GND P14 Pin #
Function P14 Pin #
Function 1 2 3 4 5 6 7 8 9 10 NC NC CLK0 (clock out signal) Data bus D15 Data bus D14 Data bus D13 Data bus D12 Data bus D11 Data bus D10 Data bus D9 11 12 13 14 15 16 17 18 19 20 Data bus D8 Data bus D7 Data bus D6 Data bus D5 Data bus D4 Data bus D3 Data bus D2 Data bus D1 Data bus D0 GND 45 APPENDIX C: CHANGING THE ANALOG INPUT MEASUREMENT TYPE General This chapter describes changing the units of measurements of the AIs, from current to voltage and vice versa. To do so, the RTU is disassembled, jumpers are placed on the Expansion board, and the unit is reassembled, as described below. The AI setup of the MOSCAD-M PLUS radios is described under AI (x4) in the Installation chapter. If the status of the jumpers is changed, the AI Type must be changed accordingly in the Hardware Test tool of the MOSCAD-M Configurator. See Configurator help. Before beginning any disassembly or reassembly procedures, you should be adequately grounded to prevent damage to static sensitive devices in the unit. Disassembling the RTU Remove Connectors Before opening the RTU, the five 10-pin connectors on the bottom of the RTU must be disconnected. Note the configuration of the connections so that they can be easily reconnected after placing the jumpers and reassembling the RTU. Open RTU Turn the unit upside down, so that the rightmost wing is closer to you. Using both thumbs, press the two tabs (A) at the bottom of the unit, as shown in Figure 24, to release the back of the case. Lift the cover (B) and push forward slightly (C), to release the cover from the top tabs. Figure 24 Opening MOSCAD-M RTU Plastic Case 46 Appendix C: Changing the Analog Input Measurement Type Remove Main Board Press the two small tabs (A) at the top of the Main board (shown in Figure 25) to release the top of the Main board. Then press the two small tabs at the bottom of the Main board (B) to release the bottom of the Main board. Lift the Main board out of the housing. Figure 25 Removing Main Board from MOSCAD-M RTU Remove Expansion Board Press the two small tabs at the top of the Expansion board (A) to release the top of the Expansion board. (See Figure 26.) Then press the two small tabs at the bottom of the Expansion board (B) to release the bottom of the Expansion board. Lift the Expansion board out of the housing. Figure 26 Removing Expansion Board from MOSCAD-M RTU 47 Appendix C: Changing the Analog Input Measurement Type Place Jumpers Flip over the Expansion board. Locate the four jumpers marked P7, P8, P9, and P10, near the center of the board, as shown in Figure 27. All jumpers which are placed measure 4-20mA. To change an AI to 0-5V, remove the jumpers. Make sure to save the cap. To change an AI to 4-20mA, place the jumpers. Press the cap down until you hear it click. Figure 27 Expansion Board with Jumpers The chart below shows the correlation of jumpers to AIs. AI1 P7 AI2 P8 AI3 P9 AI4 P10 48 Appendix C: Changing the Analog Input Measurement Type Reassembling the RTU Install Expansion Board With the jumpers facing down and the 10-pin connectors on your right, lower the bottom of the Expansion board into the case. Align the peg on the upper left-hand side of the board (A) and the two tongues toward the bottom of the board (A) with the matching grooves (A) (see Figure 28). Press the Expansion board under the two large snaps at the bottom of the board until you hear them click (B). Press the top of the Expansion board under the two small snaps until you hear them click (C). Figure 28 Installing Expansion Board 49 Appendix C: Changing the Analog Input Measurement Type Install Main Board Hold the Main board with the push-button facing down and the 10-pin connectors on the right. Lower the board, aligning the two small gray round pegs (A) (see Figure 29) on the bottom of board and the small oblong peg on the upper left-hand side of the board with the matching grooves. Using both thumbs, press the bottom of the Main board under the two bottom snaps
(B). Use both thumbs to press the top of the board under the two top snaps (C). Figure 29 Installing Main Board Close Case Hold the back of the case face down, with the holes for screw mount to your left. Align the two top snaps with the two grooves on the top of the case back. Press with both thumbs until you hear it click. Use both thumbs to press the bottom of case back under the snaps until you hear it click. Turn the unit right side up. Reconnect the 10-pin connectors in their original configuration. 50
1 2 3 | label artwork and placement photos | ID Label/Location Info | 264.07 KiB | February 06 2000 |
MOTOROLA INC. FCC ID: AZ489FT4840 Sample Label Artwork Radio Products Group EXHIBIT 1 8000 West Sunrise Boulevard, Fort Lauderdale, Florida 33322. (954) 723-5000 SHEET 1 of 3 MOTOROLA INC. FCC ID: AZ489FT4840 FCC ID Label location Radio Products Group EXHIBIT 1 8000 West Sunrise Boulevard, Fort Lauderdale, Florida 33322. (954) 723-5000 SHEET 2 of 3 MOTOROLA INC. FCC ID: AZ489FT4840 FCC Warning Label location Radio Products Group EXHIBIT 1 8000 West Sunrise Boulevard, Fort Lauderdale, Florida 33322. (954) 723-5000 SHEET 3 of 3
1 2 3 | table of contents and label | ID Label/Location Info | 9.45 KiB |
MOTOROLA INC. FCC ID: AZ4FLN2582A LIST OF EXHIBITS DESCRIPTION EXHIBIT REFERENCE Identification label information I.
General Information 1. Production Plans 2. Data Submittal Procedure II. Certification of Data III. External Photographs IV. Circuit Descriptions V. Schematic Diagrams VI. Test Report 1. Data Index 2. RF Output Data 3. Occupied Bandwidth 4. Conducted Spurious Emissions 6. Powerline Conducted Spurious Emissions 6. Radiated Spurious Emissions 7. Frequency Stability, Transient Behavior 90214
(Temperature & Supply Voltage) VII. Test Set-up Procedures VIII. Instruction Manual IX. Internal Photographs. X. Parts List and Tune-Up procedures XII. Operational Description 1. Technical Characteristics 2. Application XIII. Cover Letter 1 1a 2 3 4 5 6 6 6A 6B 6C 6D 6E 6F 7 8 9 10 11 12 13 XI. RF Exposure Information 2.1091, 2.1093 2.1061 2.1033 2.1033 2.1033 2.1046 2.1049(i) 2.1051 15.208 2.1053, 15.209 2.1047, 90.213, EXHIBIT 1 Page 1 of 3 MOTOROLA INC. FCC ID: AZ4FLN2582A LOCATION A nameplate of the type presented below will be affixed to every transmitter. It will be placed on the outside of the housing at the bottom back of the transmitter. TYPE The label is a paper polyester film laminate with a pressure sensitive adhesive backing. The adhesive is a permanent type acrylic with a minimum peel strength of 40 oz/inch. Model:
FCC ID:
P44- UHF2 FLN2582A AZ4FLN2582A Made in Israel by MOTOROLA INC. Label Text EXHIBIT 1 Page 2 of 3 MOTOROLA INC. FCC ID: AZ4FLN2582A EXHIBIT 1A - GENERAL INFORMATION 1. Production Plans Quantity production is planned. 2. Data Submittal Procedure:
Data is supplied in accordance with Part 2, Sub-part J of the Commissions rules. The intended use of this transceiver includes applications covered in the Code of Federal Regulations Title 47, Parts 15 and 90. Transmitter power shall not exceed 4 watts and this power level shall not be adjustable by the user. EXHIBIT 1 Page 3 of 3
1 2 3 | covering letter including new part numbers for the certificate | Cover Letter(s) | 24.47 KiB |
October 20, 2001 Authorization & Evaluation Division Federal Communications Commission Laboratory 7435 Oakland Mills Road Columbia, MD 21046 Subject: Application for Permissive Change of MOSCAD-L P44-UHF FLN5922A (438-
470 MHz), FCC ID: AZ 489FT4840 Attention: Mr. Frank Coperich, Dear Mr. Coperich:
Motorola Communications herein submits application for Permissive Change of the MOSCAD Series Of Products to include a new product configuration for Equipment Authorization Certification. This certification was issued for MOSCAD-L P44-UHF FLN5922A (438-470 MHz) Remote Terminal Unit. The new configuration is MOSCAD-M F4582A (438-470 MHz) and MOSCAD-M F4572A (438-470 MHz) Remote Terminal Unit. Again, both MOSCAD-L and MOSCAD-M use the same RF Module (438-470 MHz) Note that The only difference between F4581A and F4571A is the removal of an expansion board. Attached in this submission is:
- The new operators/install. Manual (describing the use only as a Base Station).
- Service Manual including Circuit and block diagrams and service information.
- Test report including spurious emissions. A complete Permissive Change application is enclosed, Please feel free to contact Rob Stirling at (604) 218 1762 for testing details, or if you require any information about the submission. Sincerely, Rob Stirling, P.Eng EMAIL protocollabs@earthlink.net
1 2 3 | PN Change request | Cover Letter(s) | 6.86 KiB | March 10 2000 |
October 2, 2000 Authorization & Evaluation Division Federal Communications Commission Laboratory 7435 Oakland Mills Road Columbia, MD 21046 Subject: Application for permissive change of Transmitter with FCC ID: AZ489FT4840, EA98934. Attention: Mr. Frank Coperich, Dear Mr. Coperich:
Per our recent EMAILs and telephone conference, Protocol Labs on behalf of Motorola, Inc. is requesting a modification to the transmitter model number information that is be listed in the notes section of the Grant for Equipment Authorization in the noted FCC Grant. The model number information should be listed as follows:
Moscad-L P44-UHF FLN5922A, SCADA Terminal Thank you for your assistance and guidance in this matter. If you have any questions, feel free to contact me at (604) 218-1762. Sincerely, Robert E. Stirling, P.Eng Rob Stirling, P.Eng EMAIL protocollabs@earthlink.net
1 2 3 | attestation statement | Attestation Statements | 5.70 KiB |
MOTOROLA INC. FCC ID: AZ4FLN2582A CERTIFICATION OF DATA The technical data supplied with this application, having been taken under my supervision and is hereby duly certified. The following is a statement of my qualifications:
1) I have received a BASc degree in Electrical Engineering from University of British Columbia, Canada, in 1986. 2) I have 10 years experience in developing, testing and certifying electronics and communication products. NAME:
Robert E. Stirling, P.Eng. SIGNATURE: Robert E. Stirling DATE:
April 8, 2000 POSITION:
Director, Senior Engineer, Protocol Labs FCC Registration number: 96437 EXHIBIT 2 SHEET 1 OF 1
1 2 3 | cover letter | Cover Letter(s) | 30.82 KiB |
MOTOROLA INC. FCC ID: AZ4FLN2583A April 12, 2000 Authorization & Evaluation Division Federal Communications Commission Laboratory 7435 Oakland Mills Road Columbia, MD 21046 Subject: Application for Certification of our base station transmitter, Model P44-UHF2 FLN2583A with FCC ID: AZ4FLN2583A Attention: Mr. Frank Coperich, Mr. George Tannahill. Gentlemen:
Motorola Communication, Kerminitzki 3 TelAviv, Israel, herein submits this application for Certification of the subject transmitter. This transmitter is intended for use in a base station environment with capabilities for data communications with a variable transmit power of 0.25 to 4 Watt. The subject transmitter complies with Section 90.203 of the Rules in that the operator cannot directly program transmit frequencies using the unit's normally accessible external controls. A complete Certification application is enclosed, contact Rob Stirling at (604) 218 1762 for testing details, or Mr. Mike Ramnath at (954)723-793 or Fax (954)723-4794 if you require any information about the submission. Sincerely, Rob Stirling, P.Eng EMAIL protocollabs@earthlink.net Radio Products Group EXHIBIT 13 8000 West Sunrise Boulevard, Fort Lauderdale, Florida 33322. (954) 723-5000 SHEET 1 OF 1
1 2 3 | model and fcc id change request | Cover Letter(s) | 6.18 KiB | February 06 2000 |
MOTOROLA INC. FCC ID: AZ4FLN2582A May 31, 2000 Authorization & Evaluation Division Federal Communications Commission Laboratory 7435 Oakland Mills Road Columbia, MD 21046 Subject: Part Number and FCC ID Changes for Certification of our base station transmitter, Model P44-UHF2 FLN2582A with FCC ID: AZ4FLN2582A Attention: Mr. Frank Coperich, Mr. George Tannahill. Gentlemen:
We would hereby like to request a change to the noted transmitter model number, part number and FCC ID in the pending application. The unit Model Number is F6839A, The radio module part number is FRN5922A, and the new requested FCC ID would be AZ489FT4840. Label artwork and placement photos are enclosed in the submission, please feel free to contact me at (604) 218 1762 or the following EMAIL address. Sincerely, Rob Stirling, P.Eng EMAIL protocollabs@earthlink.net Radio Products Group EXHIBIT 13 8000 West Sunrise Boulevard, Fort Lauderdale, Florida 33322. (954) 723-5000 SHEET 1 OF 1
1 2 3 | operational data | Operational Description | 9.39 KiB |
MOTOROLA INC. FCC ID: AZ4FLN2582A OPERATIONAL DESCRIPTION P44- UHF1 FLN2582A I. Transmitter Technical Characteristics A. Specific Operating Power Levels:
RATED: 0.25 to 4 Watts, variable, not user adjustable MEASURED: Refer to Exhibit 6A Maximum Power Rating: 4 Watts Means provided for variation of operating power: Factory set or performed by authorized personnel using published Tune-up Procedure B. Frequency Range:
438-470 MHz C. Frequency Stability:
D. Types of Emissions:
F2D Data radio E. Spurious Emissions:
RATED: 0.00025% ( 2.5 ppm) MEASURED: Refer to Exhibits 6F-1 and 6F-2. RATED: 1.567 uW (-58.05 dBm) maximum, which corresponds to 57.6dBc at the 4.0 Watt setting. Refer to Exhibit 6E. F. DC Operating Voltages and Currents:
Refer to Exhibit 6A. II. Transmitter Application The following features, options, accessories, and installations characterize the transmitter. A. Power Supply:
115 Vac (Nominal) or 12 Vdc battery (backup) B. Antenna External 50-ohm antenna, Type-N Connector provided EXHIBIT 12 SHEET 1 OF 2 MOTOROLA INC. FCC ID: AZ4FLN2582A C. Transmission Modes DPSK 1200 BPS FSK 2400 BPS DFM 4800 BPS Dual Binary (COS) 9600 BPS D. Maximum Transmit Channel Capability:
1 Channel, 12.5 Channel Bandwidth, Full Duplex E. Housing Style:
The transmitter assembly is shielded with a metal can and is mounted on the communication module of the MOSCAD-L can as shown in the accompanying photographs. The communication module is housed in the MOSCAD-L Plastic Chassis. The transmitter circuitry is contained on a single printed circuit board that is mounted inside the metal can on a carrier board, and secured to it with screws. A fitted cover completes the shielding enclosure, as shown in the accompanying photographs. F. Programmability:
Programming is accomplished by the use of an IBM PC computer or through a link with another terminal, using the MOSCAD-L Toolbox Software. This provides means for adjustment of the transmitter, including programming of the channel frequencies, communication protocols and data rates. NOTE: The transmitter power is NOT programmable by the operator. EXHIBIT 12 SHEET 2 OF 2
1 2 3 | tuneup info | Parts List/Tune Up Info | 51.52 KiB |
MOTOROLA INC. FCC ID: AZ4FLN2582A MoBat Wireless application Proceed. No: 12MB000004 Date:07/99 Issue:O MATERIAL or METHODS SPECIFICATION Assembly name : P42/44 UHF For customer use Kits : FRN5916/17 P42 FRN5922/23 P44 O Rev. ECN No. Apvrd by Q.A. Date Page Issue 1 O 2 O 3 O 4 O 5 O 6 O 7 O 8 O 9 O 10 O 11 O 12 O 13 O 14 O 15 O 16 O 17 O 18 O 19 O 20 O 21 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 25 24 22 0 Page 23 Issue 0 Approvals :
Written by Approved by Quality Assurance Yehuda Eder Sofer signature :
signature :
signature :
Date ______ Date :______ Date :______ EXHIBIT 10 PAGE 1 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A TABLE OF CONTENTS 1. SPECIFICATIONS ...................................... 3 1.1 Introduction .................................. 3 1.2 Detailed Technical Specification .............. 3 1.2.1 General ................................ 3 1.2.2 Transmitter ............................ 4 1.2.3 Receiver ............................... 4 1.2.4 Power Supply ........................... 6 1.2.5 Environmental .......................... 7 2.TEST EQUIPMENT & PROGRAMS ............................ 8 RADIO ADJUSTMENTS - GENERAL ......................... 10 2.1.TRANSMITTER CALIBRATION ....................... 10 2.2.RECEIVER CALIBRATION .......................... 12 3.RECEIVE FINAL TEST SPECIFICATIONS .................... 15 3.1. Sensitivity/Selectivity .................... 15 3.1.1.12 dB Sinad ............................ 15 3.1.2. Adjacent channel selectivity .......... 16 3.1.3. spurious response rejection 3.1.4. Intermodulation response rej. ....... 16 3.2.DISC Output and Distortion .................... 16 3.3.RX Hum and Noise .............................. 17 3.4.Receiver Audio Frequency Response ............. 17 3.5.RSSI .......................................... 18 3.6.Standby Current Drain ......................... 18 4.TRANSMIT FINAL TEST SPECIFICATIONS ................... 19 4.1.Transmitter Frequency Accuracy ................ 19 4.2.RF Power Output ............................... 19 4.3.Transmitter Current Drain ..................... 20 4.4.Modulation Sensitivity (Deviation) ............ 20 4.5.Transmitter Distortion ........................ 21 4.6.Tx Hum and Noise .............................. 21 4.7.Transmitter Audio Frequency Response .......... 22 4.8.Transmitter attack time. 4.9.Transmitter Spurious emissions 5. P44/P42 INTERFACE ................................... 23 EXHIBIT 10 PAGE 2 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 1. SPECIFICATIONS 1.1 Introduction The P42/44 UHF are a radio tranceivers module that is intended to be a subassembly in terminals products. The radio covers the tranceivers frequency ranges of 403-433Mhz and 438-470Mhz the at 12.5KHz channel spacing. It includes no voice processing circuitry and is optimized for dataoperation. The purpose of this document is to define the performance requirements for the UHF radios. 1.2 Detailed Technical Specification All specifications will be met over the temperature range of -30 to +60 degree C at the supply 7.5 volt DC. 1.2.1 General Frequency range FRN5916/7 p42 403-433Mhz/438-470Mhz FRN5922/23 p44 403-433Mhz/438-470Mhz Modulation Antenna Impedance FM 50 ohms Frequency stability 2.5 ppm Duty Cycle Normal opration :
Maximum Rating :
20% Tx 80% Rx - 10 Sec Tx., 40 Sec Rx. Continuous transmission should not exceed 25 seconds. EXHIBIT 10 PAGE 3 of 21 MOTOROLA INC. 1.2.2 Transmitter RF Output - High power:
Measured per EIA RS-152-B section 3 4W min. at room temperature and 7.5 VDC
+2/-3 dB from -30 to 70 degree C 6 to 9 VDC FCC ID: AZ4FLN2582A Conducted Spourious:
-60dBc non-harmonic
-60 dBc harmonic Measured per EIA RS-152-B section 4 Radiated Spourious:
Measured per FCC Part 15. 500uV/m at 3 m Audio Frequency Response:
Measured per Section 5.7 in this spec. 3Hz to 5KHz ; +/- 2dB Distortion:
Measured per Section 5.5 in this spec. 5%
Hum and Noise 25 dB Measured per Section 5.6 in this spec. MOD Input sensitivity Measured per Section in this spec. 350mVrms/ +/-2khz dev +/-0.5dB Modulation Stability Measured per Section 5.4 in this spec.
+/-10%
Tx Turn-on Time:
10 msec. EXHIBIT 10 PAGE 4 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A Transmit Current 2.5A Frequency Stability 2.5ppm EXHIBIT 10 PAGE 5 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 1.2.3 Receiver Receiver Sensitivity 12 dB Sinad Measured per RS-204-C Paragraph 7.0 with external de-emphasis network.
-113dBm Measured per RS-204-C Paragraph 12.0 with external de-emphasis Adjacent Channel Selectivity 60dB 60dB Spurious and Image Measured per RS-204-C Paragraph Intermodulation Measured per RS-204-C Paragraph 14.0 with external de-emphasis network. 60dB Conducted Spurious Emission Measured per RS-204-C Paragraph 16.0 .
-57dBm Audio Frequency Response Measured per Section 4.4 in this spec. 3 Hz to 5 KHz +/-2dB Distortion Measured per Section 4.2 in this spec. 5%
Hum and Noise 25dB Measured per Section 4.3 in this spec. DISC Output Stability Measured per Section 4.2 in this spec.
+/- 10%
RSSI Output Measured per Section 4.5 in this spec. See Figure 7.1 Receiver settling Time Measured per APPENDIX I, Section 4 10 msec. Receiver Settling Time From Battery Save Mode to fully operation Measured per APPENDIX I, Section 5 10 msec 1.2.4 Power Supply ... Nominal Voltage 7.5 volts DC Operational Voltage Range 6 to 9 volts DC Polarity Negative Ground Current Drain :
Battery Save Mode:
Receiver :
10mA 50mA EXHIBIT 10 PAGE 6 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A Transmit :
2.5A@4watt EXHIBIT 10 PAGE 7 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 1.2.5 Enviromental Temperature : The radio will operate and meet the stated specifications from -30 to +60 degree C. Storage temperature -40 to +80 degree C. Humidity: 95% humidity at +50 degree C, 63.5 hrs exposed. Vibrations and Shock : Per EIA RS152B MDI doc #910,0436, Survival four foot drop on concrete when installed inside host product. EXHIBIT 10 PAGE 8 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 2.TEST EQUIPMENT &PROGRAMS DC Power Supply, 0-10v, 0-5a Digital Multimeter (Fluke 87 Or Eq.) Oscilloscope (0 .. 100 MHz) IBM PC XT/AT or Compatible Computer HP8920A Communication Test Set HP 8656B/8657A Signal Generator X 3 3 Way RF Combiner Modulation Analyzer c/w Power Sensor HP8901B/HP11722A Audio Analyzer HP8903B EXHIBIT 10 PAGE 9 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 2.1. RADIO ALIGNMENT AND ADJUSTMENTS - GENERAL There are total of 5 alignments and adjustments to be made in the radio. holes are located on the top The test fixture uses a PC computer to load the information for the channel frequency, modulation function, adapt timer, TX keying, battery save mode etc. to the synthesizer IC for the p42 .For the p44 use p44 RSS (radio service software) to load frequencies 2.1.TRANSMITTER CALIBRATION Key radio only while making adjustments or measurements. The transmitter tune-up frequency is 455MHz. Adjust the DC supply voltage to 7.5+/0.1 volts DC. Program the radio transmitter to the tune-up frequency and key the radio with no modulation applied. Monitor transmitter RF sample on the modulation analyzer and set the tune-up uency to the following limit by adjusting the trimmer (R532) Modulation Analyzer settings:
Measurement : FREQ. Specials : 7.1 SPCL Limit: 455MHz +/-200 Hz EXHIBIT 10 PAGE 10 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A Using the same procedure, monitor the RF power output on the modulation analyzer. Set the output power to the following limit by adjusting R595, Modulation Analyzer settings:
Measurement : RF POWER Limit: 1 to 4W (according to the request ) +/-0.15W Using the same procedure as and MOD Attenuation value per the table bellow , Key the radio and apply 2400 Hz tone at 350mVrms to the MOD inputs of the Radio (pin 6). Adjust as MOD ATT with the software. on the top housing . set deviation to the to 2khz +/-50hz. Note: Apply the 20Hz tone and check deviation of 2khz +/- 0.5db. Modulation Analyzer settings:
Measurement : FM LP Filter :15KHz Detector : Peak+
Limit: 2KHz +/- 0.5db EXHIBIT 10 PAGE 11 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 2.2.RECEIVER CALIBRATION The receiver tune-up frequency is 455MHz. Program the radio receiver to the tune-up frequency and set the RF generator to the tune-up Apply -47dB RF signal modulated by 2.4KHz tone 2KHz deviation check carrier detector 5v. Apply an modulated RF signal at -110 dBm at the tune-up frequency. Adjust 593, that is For carrier detect CAL to 0 volt .increase the signal level to 107dbm and verify 5v on the carrier detect output. EXHIBIT 10 PAGE 12 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 3.RECEIVE FINAL TEST SPECIFICATIONS CAUTION: AVOID TRANSMISSION DURING RECEIVER TESTS Note 1: All receiver tests are to be performed with an RF test cable connected to Note 2: Modulation frequency must be set to 0 Hz to avoid unwanted noise at the DISC inputs. Note 3: "Extreme conditions", unless otherwise specified, refers to voltage variations between 6 V and 9 VDC and temperature range of -30C to +60C . Note 4: Tests are provided on frequencies: low, middle, high. 3.1. Sensitivity/Selectivity 3.1.1. 12dB Sinad Apply an on-channel RF signal at a level of -113 dBm. Modulate with a 1KHz tone at 2KHz deviation. Measure the SINAD Audio Analyzer settings:
Measurement : SINAD LP Filter : 30KHz PSHF : ON Limit: 12 dB min. 3.1.2. Adjacent channel selectivity Measured per ETS 300 113 5.2.5 Subclause 9.6 3.1.3. Spurious response rejection Measured per ETS 300 113 5.2.6 Subclause 9.7 3.1.4. Intermodulation response rej Measured per ETS 300 113 5.2.7 Subclause 9.8 EXHIBIT 10 PAGE 13 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 3.2.DISC Output and Distortion Apply an on-channel RF signal at a level of -47 dBm. Modulate with a 2.4KHz tone at 2KHz deviation. Measure the level and distortion at the DISC output of the test fixture. Change the RF level to -80 dBm and 47dBm and measure the distortion at each level. Audio Analyzer settings:
Measurement : AC LEVEL : for Disc level measurement
: DISTN : for distortion measurement LP Filter : 30KHz Limits :
AC Level : 140mVrms +/- 20mV Distortion :
@-80dBm : 5% max.
@-47dBm : 5% max. Limit at extreme conditions :
AC Level : 140mVrms +/-40mV Distortion : 10% max. at any level . 3.3.RX Hum and Noise Audio Analyzer settings:
Measurement : AC Level Ratio, Log LP Filter : 30KHz Limit: -25 dB min. Limit at extreme conditions: 20dB Apply an on-channel RF signal at a level of -47 dBm. Modulate with a 2.4KHz tone at 2KHz deviation. Measure the level at the DISC output of the test fixture and record as 0dB reference . Remove the modulation and measure the relative AC level in dB note the hum and noise level. 3.4.Receiver Audio Frequency Response Apply an on-channel RF signal at a level of -47 dBm. Modulate with 2.4KHz tone at 2KHz deviation. Measure the level at the test fixture DISC output. Establish a 0 dB reference. Change the modulation frequency to 20 Hz, then to 500 Hz, then to 5000 Hz. Verify that the audio frequency response (relative to the 0 dB reference) is within the following limits. Audio Analyzer settings:
Measurement : AC Level Ratio, Log LP Filter : 30KHz Limit: +/- 2dB max . Limit at extreme conditions :+/- 2dB max. EXHIBIT 10 PAGE 14 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 3.5.RSSI Apply an on-channel RF signal with no modulation at a level of -110 dBm. Measure the DC voltage at the RSSI output. Repeat the test at -66 dBm. Audio Analyzer settings:
Measurement : DC Level LP Filter : 30KHz Limits :
@ -110dBm : 1VDC +/- 150mV
@ -66dBm : 2.2VDC min. 4.2VDC max. Limit at extreme conditions:
@ -110dBm : 1VDC +/- 200mV
@ -66dBm : 2.2VDC min. 4.2VDC max. 3.6.Standby Current Drain 4.6.1 RECEIVER CURRENT:
Limit : 50mA max. 4.6.2 SLEEP CURRENT Limit : 10mA max. Measure the receiver current drain with no RF signal applied to the receiver Measure the receiver current drain with no RF signal applied to the receiver ,Set channel 8 on the p44 and on p42 send the Standby synthesizer word. EXHIBIT 10 PAGE 15 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 4.TRANSMIT FINAL TEST SPECIFICATIONS WARNING: The radio shall transmit continuously no more than 20 seconds without a heat sink Note : test frequencies:
Channel 1 frequency: 438.000MHz Channel 2 frequency: 455.000MHz (tune-up frequency) Channel 3 frequency: 470.000MHz 4.1.Transmitter Frequency Accuracy Verify that the exact frequency (on any channel) is within the following limit. Measure the RF power output on the three test channels Modulation Analyzer settings:
Measurement : RF POWER Modulation Analyzer settings:
Measurement : FREQ Specials : 7.1 SPCL Limit: +/-200Hz max Limit at extreme conditions: 2.5ppm 4.2.RF Power Output Limits :
antenna (J1):
High power : 4 +/- 0.3W Low Power : 1W +/- 0.2W Limit at extreme conditions:
antenna (J1):
High power : 4W +2/-3dB Low Power : 1W +/- 3dB 4.3.Transmitter Current Drain Measure the transmitter current drain while keyed at each antenna using a calibrated ammeter or current measuring power supply. Verify that current drain is within the following limit. Limit : 2.5 A max. @ High power 4.4.Modulation Stability (Deviation) 5.4.1Key the radio, set the Mod Attenuation according to the following table:
Apply a 2.4KHz tone at a propriety level to achieve 350mVrms on radio Mod terminals. Measure deviation (while the radio is keyed) on the Modulation Analyzer. 5.4.2Key the radio, set the Mod Attenuation according to the following table:
Apply a 20Hz tone at a propriety level to achieve 350mVrms on radio Mod terminals. EXHIBIT 10 PAGE 16 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A Measure deviation (while the radio is keyed) on the Modulation Analyzer. Modulation Analyzer settings :
Measurement : FM LP Filter :15KHz Detector : Peak+
Limit : 2KHz +/-0.1KHz @ 455MHz with 2.4khz tone 2KHz +/-0.2KHz @ any other channel and with 20hz tone Limit at extreme conditions : 2KHz +/-0.4KHz EXHIBIT 10 PAGE 17 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A Using the same procedure as above, key the radio and measure the distortion. Verify that the distortion is within the following limit. 4.5.Transmitter Distortion Modulation Analyzer settings :
Measurement : FM LP Filter :15KHz Detector : Peak+
Specials : 2.2SPCL Audio Analyzer settings :
Measurment : DISTN LP Filter: 30KHz Limit : 5% max. Limit at extreme conditions : 7% max. EXHIBIT 10 PAGE 18 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A Using the same procedure as above, key the radio. Measure the AC level at Modulation Analyzer audio output and set the Audio analyzer to 0 dB reference. Set the Mod.Frequency to 0Hz. Read the hum and noise ratio . 4.6.Tx Hum and Noise Modulation Analyzer settings :
Measurment : FM LP Filter :15KHz Detector : Peak+
Specials : 2.2SPCL Audio Analyzer settings :
Measurment : AC Level Ratio, Log LP Filter: 30KHz Limit: -25dB max. Limit at extreme conditions: -20dB max. 4.7.Transmitter Audio Frequency Response Using the same procedure ,Apply a 2.4 kHz signal to the MOD input. Establish RMS position on the Modulation analyzer and 0dB reference. Change audio frequency to 50 Hz, 500 Hz, 1000 Hz and 5000 Hz. Verify that the response is within the following limit relative to deviation at 2.4KHz tone.. Modulation Analyzer settings :
Measurment : FM LP Filter :15KHz Detector : RMS or AVG Limit : +/-2 dB max. Limit at extreme conditions: +/- 2dB max. 4.8.Transmitter attack time Measured per ETS 300 113 5.1.7 Subclause 8.8 and 8.10.1 4.9.Transmitter Spurious emissions Measured per ETS 300 113 5.1.5 Subclause 8.6 EXHIBIT 10 PAGE 19 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 5. P44 INTERFACE P1 INTERFACE CONNECTOR PIN OUT PINS 1 2 SYMBOL SWB+
TYPE
+7.5V DC DESCRIPTION GND RADIO POWER SUPPLY
+7.5V DC 7.5V IN TRANSMIT MODE 3 4 5 6 7 8 9 10 11 12 13 14 XB+
RX 5V TX 5V
+5V
+5V MOD IN+
SQ DET RESET INPUT OUTPUT INPUT RSSI OUTPUT DISC+
CH SEL B CH SEL A CH SEL C CH SEL D OUTPUT INPUT INPUT INPUT INPUT 5V IN RECEIVE MODE ONLY 5V IN TRANSMIT MODE ONLY DIFFERENTIAL INPUT FOR DATA MODULATION CARRIER DETECT PULL DOWN WHILE PROGRAMING RECEIVED SIGNAL STRENGTH INDICATOR DISCRIMINATOR OUTPUT SELECTING CHANNEL PULL DOWN TO LOUD CHANNEL SELECTING CHANNEL SELECTING CHANNEL EXHIBIT 10 PAGE 20 of 21 MOTOROLA INC. FCC ID: AZ4FLN2582A 6. P42 INTERFACE P1 INTERFACE CONNECTOR PIN OUT PINS 1 2 SYMBOL SWB+
TYPE
+7.5V DC 3 4 5 6 7 8 9 11 12 13 14 XB+
RX 5V TX 5V MOD IN+
LOCK DET SYN LE SYN DATA SQ DET RSSI DISC+
+5V
+5V
+5V INPUT OUTPUT INPUT INPUT OUTPUT OUTPUT OUTPUT INPUT 12MB000004 07/99 DESCRIPTION GND RADIO POWER SUPPLY
+7.5V DC 7.5V IN TRANSMIT MODE
+5V IN RECEIVE MODE ONLY
+5V IN TRANSMIT MODE ONLY DIFFERENTIAL INPUT FOR DATA MODULATION SYNTHESIZER LOCK INDECATION PULL DOWN WHILE LOUDING SYN PAR. DATA TO SYNTHESIZER CARRIER DETECT IND./ADAPT (FOR INTERMEC) RECEIVED SIGNAL STRENGTH INDICATOR DISCRIMINATOR OUTPUT SYN +5V EXHIBIT 10 PAGE 21 of 21
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2002-01-24 | 438 ~ 470 | TNB - Licensed Non-Broadcast Station Transmitter | Class II permissive change or modification of presently authorized equipment |
2 | 2000-10-31 | 438 ~ 470 | TNB - Licensed Non-Broadcast Station Transmitter | |
3 | 2000-07-17 | 438 ~ 470 | TNB - Licensed Non-Broadcast Station Transmitter | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 3 | Effective |
2002-01-24
|
||||
1 2 3 |
2000-10-31
|
|||||
1 2 3 |
2000-07-17
|
|||||
1 2 3 | Applicant's complete, legal business name |
Motorola Solutions, Inc.
|
||||
1 2 3 | FCC Registration Number (FRN) |
0003778479
|
||||
1 2 3 | Physical Address |
8000 West Sunrise Blvd
|
||||
1 2 3 |
Ft Lauderdale, 33322
|
|||||
1 2 3 |
United States
|
|||||
app s | TCB Information | |||||
n/a | ||||||
app s | FCC ID | |||||
1 2 3 | Grantee Code |
AZ4
|
||||
1 2 3 | Equipment Product Code |
89FT4840
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 3 | Name |
D**** Z********
|
||||
1 2 3 | Title |
Regulatory Compliance Manager
|
||||
1 2 3 | Telephone Number |
95472********
|
||||
1 2 3 | Fax Number |
--********
|
||||
1 2 3 |
d******@motorolasolutions.com
|
|||||
app s | Technical Contact | |||||
1 2 3 | Firm Name |
Protocol Labs
|
||||
1 2 3 |
Protocol labs
|
|||||
1 2 3 | Name |
R**** E****** S********
|
||||
1 2 3 |
R****** S****
|
|||||
1 2 3 | Physical Address |
28945 McTavish Rd
|
||||
1 2 3 |
28945 McTaviish Rd.
|
|||||
1 2 3 |
Abbotsford
|
|||||
1 2 3 |
Abbotsford, V4X 2E7
|
|||||
1 2 3 |
Canada
|
|||||
1 2 3 | Telephone Number |
604 2********
|
||||
1 2 3 | Fax Number |
604 6********
|
||||
1 2 3 |
p******@earthlink.net
|
|||||
app s | Non Technical Contact | |||||
1 2 3 | Firm Name |
Protocol Labs
|
||||
1 2 3 |
Motorola Inc
|
|||||
1 2 3 |
Motorola, Radio Products Group
|
|||||
1 2 3 | Name |
R******** S******
|
||||
1 2 3 |
M**** R******
|
|||||
1 2 3 | Physical Address |
28945 McTavish Rd
|
||||
1 2 3 |
28945 McTaviish Rd.
|
|||||
1 2 3 |
8000 West Sunrise Boulevard
|
|||||
1 2 3 |
Abbotsford
|
|||||
1 2 3 |
Abbotsford, V4X 2E7
|
|||||
1 2 3 |
Fort Lauderdale, Florida 33322
|
|||||
1 2 3 |
Canada
|
|||||
1 2 3 |
United States
|
|||||
1 2 3 | Telephone Number |
604 2********
|
||||
1 2 3 |
954-7********
|
|||||
1 2 3 |
(954)********
|
|||||
1 2 3 | Fax Number |
604 6********
|
||||
1 2 3 |
954-7********
|
|||||
1 2 3 |
(954)********
|
|||||
1 2 3 |
p******@earthlink.net
|
|||||
1 2 3 |
e******@email.mot.com
|
|||||
1 2 3 |
M******@Motorola.com
|
|||||
app s | Confidentiality (long or short term) | |||||
1 2 3 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
1 2 3 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 3 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 3 | Equipment Class | TNB - Licensed Non-Broadcast Station Transmitter | ||||
1 2 3 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | MOSCAD Series SCADA Terminals | ||||
1 2 3 | Moscad-L P44-UHF FLN5922A, SCADA Terminal | |||||
1 2 3 | MOSCAD-L P44-UHF1 FLN2582A , SCADA Terminal | |||||
1 2 3 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 3 | Modular Equipment Type | Does not apply | ||||
1 2 3 | Purpose / Application is for | Class II permissive change or modification of presently authorized equipment | ||||
1 2 3 | Original Equipment | |||||
1 2 3 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 2 3 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 3 | Grant Comments | Single channel bandwidth mode. Power output may be reduced to .5 W. Approved for use as part of a base station. | ||||
1 2 3 | Approved for use as part of a base station. Single channel bandwidth mode. Power output may be reduced to .5 W. | |||||
1 2 3 | Single channel bandwidth mode. Power output may be reduced to .5 W. | |||||
1 2 3 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 3 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 3 | Firm Name |
Protocol Labs
|
||||
1 2 3 | Name |
R**** S******
|
||||
1 2 3 | Telephone Number |
604-6********
|
||||
1 2 3 | Fax Number |
604-6********
|
||||
1 2 3 |
r******@protocol-emc.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 90.210 | 438.00000000 | 470.00000000 | 4.0000000 | 1.5000000000 ppm | 11K2DXW | ||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 90.210 | 438.00000000 | 470.00000000 | 4.0000000 | 1.5000000000 ppm | 11K2DXW | ||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
3 | 1 | 90.210 | 438.00000000 | 470.00000000 | 4.0000000 | 1.5000000000 ppm | 11K2DXW |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC