RS-232 Full Modem Interface (8-Wire) Module for Protection Relay, IED, and Substation Automation Reference Design
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
AN706: EZSP-UART Host Interfacing Guide
AN706: EZSP-UART Host Interfacing Guide This application note describes how to connect a Host processor to a Network Co-Processor (NCP) using the UART-based Em- KEY POINTS berZNet Serial Protocol (EZSP). It assumes that you already • EZSP-UART protocol overview have a basic understanding of the EZSP-UART Gateway proto- • Physical interfaces col, as well as the signals needed by the UART interface. If not, • Command line options for Host refer to UG101: UART Gateway Protocol Reference Guide be- applications fore continuing. This application note has been updated to Em- • Hardware design considerations • Powering up, power cycling, and rebooting berZNet PRO 6.6 to reflect a minor update to the Silicon Labs • Bootloading Zigbee application framework, though the content of the EZSP- UART interface still applies to earlier versions of the EmberZNet PRO stack. silabs.com | Building a more connected world. Rev. 1.2 AN706: EZSP-UART Host Interfacing Guide Protocol Overview 1. Protocol Overview Silicon Labs designed EZSP as a protocol to allow communications between components running pieces of the EmberZNet PRO wire- less mesh stack, namely a Host processor and an NCP. The Host processor runs the application layer and executes on the POSIX platform such as Mac OS, Linux, or a Windows PC running Cygwin or the new Windows 10 BASH shell. You can also run this on an embedded platform like the Raspberry Pi. This lets you develop and test your application on an easy-to-use platform before porting your solution to a different Host processor with few changes. The NCP runs the EmberZNet PRO stack and physical layer (PHY). -
I.L. 40-614A 1 1. INTRODUCTION the Basic Interface to Remote Terminal, Or BIRT, Is an INCOM Network Master. BIRT Gives Users An
I.L. 40-614A 1. INTRODUCTION 3. DESCRIPTION The Basic Interface to Remote Terminal, or BIRT, is 3.1. Power Requirements an INCOM Network Master. BIRT gives users an economical way of getting information from their Range: 48 Vdc to 250 Vdc and 120 Vac INCOM-compatible devices since it connects directly between a user’s external MODEM or personal com- Burden: 3.5 W @ 48 Vdc puter and the INCOM network. 9 W @ 250 Vdc 5 W @ 120 Vac BIRT can directly replace Westinghouse MINTs, talk- ing to all INCOM-based communication devices. 3.2. Temperature Range BIRTs also include a special high-speed mode for communicating with SADIs – allowing users to collect For Operation: 0˚ to +55˚ C data from other manufacturer’s relays more rapidly For Storage: -20˚ to +80˚ C than ever before. 3.3. Physical Dimensions BIRTs are built to handle the abuse of substation environment; their “hardened” RS-232 serial port can The BIRT enclosure dimensions are identical to the handle surges and sustained high voltages that ERNI and SADI, as shown in figure 1. would destroy ordinary serial ports, and BIRTs can run on a wide range of voltages, from 48 to 250 Vdc Dimensions and weight of chassis or even 120 Vac, with no jumpers or adjustments needed. Height: 5.26” (133.6) mm) Width: 3.32” (84.3) mm) Depth: 5.92” (150.4) mm) 2. FEATURES Weight: 2.0 lbs (0.9 kg) BIRT is designed to be very flexible in its RS-232 External Wiring: See figures 2 and 3. -
I-Modem Command Reference
U.S. Robotics I-modem Command Reference U.S. Robotics I-modem Command Reference page i U.S. Robotics I-modem Command Reference The material contained in this manual is for information purposes only and is subject to change without notice. No part of this document may be reproduced, transmitted, transcribed, or stored in a retrieval system in any form or by any means, mechanical, magnetic, electronic, optical, chemical, or otherwise without the written permission of U.S. Robotics. U.S. Robotics and the U.S. Robotics logo are registered trademarks of U.S. Robotics. Courier, V.Everything, and I-modem are tradmarks of U.S. Robotics. Microsoft and Win- dows NT are registered trademarks of Microsoft Corporation. V.Fast Class and V.FC are trademarks of Rockwell International. MNP is a registered trademark of Microcom Sys- tems, Inc. Any trademarks, trade names, service marks, or service names owned or registered by any other company and used in this manual are the property of their respective companies. U.S. Robotics assumes no responsibility for errors or omissions in this manual. Nor does U.S. Robotics make any commitment to update the information contained herein. ©1997 U.S. Robotics Corp. 8100 N. McCormick Blvd. Skokie, IL 60076-2999 USA page ii U.S. Robotics I-modem Command Reference Table of Contents Chapter 1 Using the AT Command Set 1-1 General Rules for Using AT Commands 1-1 Basic AT Commands 1-2 S-registers 1-3 Chapter 2 Modes of Operation 2-1 Command and Online Modes 2-1 Controlling Local Echo 2-3 Data and Fax Modes 2-5 Chapter 3 Dialing, Answering, and Hanging Up 3-1 Making International Calls 3-7 Call Detection 3-9 page iii U.S. -
MVI69E-LDM Datasheet
DATASHEET MVI69E-LDM Linux Development Module for CompactLogix™ The MVI69E-LDM module allows users to develop and deploy C/C++ custom algorithm applications for CompactLogix™ systems. Users are also able to create drivers for specialty Ethernet and Serial end-devices. The Linux Development module comes with a built-in API for backplane communications to the processor. With the separate development kit DVD, you are the developer who controls exactly what this module can and cannot do. Features Ideal for custom algorithm applications One independent Ethernet port, and two independent, isolated, serial ports (RS232/422/485) Industrial fan-less design Built-in API included for backplane communications to the processor Linux Virtual Machine (VM) and development environment provided on our website VM contains preinstalled toolchain and libraries VM contains the popular Eclipse IDE Ethernet & multi-serial port example applications provided on VM CPU, Memory and OS Specifications Specification Description CPU 400MHz ARM9 G20 Operating System Linux (kernel 2.6.33.7) Linux Distribution TimeSys System Memory 64MB SDRAM Flash Memory 256MB NAND Flash General Hardware Specifications Additional Products Specification Description ProSoft Technology® offers a full Backplane Current Load 500 mA @ 5 Vdc complement of hardware and 3 mA @ 24 Vdc software solutions for a wide variety Operating Temperature 0°C to 60°C (32°F to 140°F) of industrial communication Storage Temperature -40°C to 85°C (-40°F to 185°F) platforms. For a complete list of Shock 15g operational -
MT5634HD8/16 User Guide MT5634HD8/16 User Guide P/N 82074700, Revision a Copyright © 1997 by Multi-Tech Systems, Inc
MT5634HD8/16 User Guide MT5634HD8/16 User Guide P/N 82074700, Revision A Copyright © 1997 by Multi-Tech Systems, Inc. All rights reserved. This publication may not be reproduced, in whole or in part, without prior expressed written permission from Multi-Tech Systems, Inc. Multi-Tech Systems, Inc. makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Multi-Tech Systems, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Multi-Tech Systems, Inc., to notify any person or organization of such revisions or changes. Revision Date Description A 11/15/97 Manual released. Multi-Tech, CommPlete, RASExpress, MultiExpress, MultiExpress Fax MultiModem, MultiModemZDX, MultiCommManager, and the Multi-Tech logo are trademarks of Multi-Tech Systems, Inc. Other trademarks and trade names mentioned in this publication belong to their respective owners. Multi-Tech Systems, Inc. 2205 Woodale Drive Mounds View, Minnesota 55112 (612) 785-3500 or (800) 328-9717 U.S. Fax (612) 785-9874 Technical Support (800) 972-2439 BBS (612) 785-3702 or (800) 392-2432 Fax Back (612) 717-5888 Internet Address: http://www.multitech.com Federal Communications Commission Statement This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. -
Lab #1 Serial Communication (2 Sessions)
MAE 493G/CpE 493M Mobile Robotics, © Yu Gu, Interactive Robotics Laboratory Fall 2013 LAB #1 SERIAL COMMUNICATION (2 SESSIONS) OBJECTIVE Learn about how to solder a null modem cable; Learn about the basic serial communication protocol; Learn how to send and receive serial communication packets from MATLAB; Practice MATLAB programing. INTRODUCTION I. Serial Communication Please reference the class handout on serial communication. For a DB9 connector commonly used for RS-232 standards, the definition of each pin is explained in Figure 1. Fig.1. DB9 Connector for RS232 Serial Communication II. Null Modem Cable To connect two computers using a RS232 serial connection, a null modem cable will be needed. There are several ways to make a null modem cable. If hand shaking is needed, follow Figure 2; and if hand shaking is not needed, follow Figure 3. Fig.2. Null Modem Cable with Hand Shaking Page 1 of 4 MAE 493G/CpE 493M Mobile Robotics, © Yu Gu, Interactive Robotics Laboratory Fall 2013 Fig.3. Null Modem Cable without Hand Shaking III. Soldering If you don’t already have experience with soldering, watch this video first: https://www.youtube.com/watch?v=I_NU2ruzyc4 IV. USB to Serial Adapter Since most of the modern computers do not have RS232 ports anymore, you will sometime need to use a USB to serial adapter to create new serial ports. The one we are using for this class is made by Micro Connectors Inc. It actually converts one USB port to two RS232 serial ports. Once properly installed, the serial port will show up as ‘COM 1’ and ‘COM 2’, or other numbers: ‘COM N’ and ‘COM N+1’. -
Series II Modem 336 Series II Modem 336+
AUGUST 2000 MD1640A MD1641A Series II Modem 336 Series II Modem 336+ CUSTOMER Order toll-free in the U.S.: Call 7877-877-BBOX (outside the U.S. call 724-746-5500) SUPPORT FREE technical support 24 hours a day, 7 days a week: Call 724-746-5500 or fax 724-746-0746 INFORMATION Mailing address: Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055-1018 Web site: www.blackbox.com • Email: [email protected] Series II Modems 336 and 336+ Series II Intelligent Data/Fax Modems Model 336 (Product Code MD1641A) Model 336+ (Product Code MD1640A) User Guide SERIES II INTELLIGENT DATA/FAX MODEMS DISCLAIMER This publication may not be reproduced, in whole or in part, without prior expressed written permission from the manufacturer. The manufacturer makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. The manufacturer reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of the manufacturer to notify any person or organization of such revisions or changes. TRADEMARKS USED IN THIS MANUAL MNP and Microcom Network Protocol are trademarks of Microcom Inc. AS/400 and System3x are registered trademarks of IBM. Appletalk, Mac, and Macintosh are registered trademarks of Apple Computer Inc. Unix is a registered trademark of X/Open Co. Ltd. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other trademarks mentioned in this manual -
Type RS-232 Adapter
Plug and Play Model 33 Tele- type RS-232 Adapter This plug and play adapter makes it simple to con- nect a Model 33 Teletype to an RS-232 serial port on computer. The adapter converts the 20ma cur- rent loop interface of the Teletype to/from RS-232 levels and obtains the power it requires for opera- tion directly from the teletype. An RJ-14 modular jack and standard flat phone wire (4 or 6 conduc- tor) are used for connection to the Teletype. On the computer side, modular DB-25 and DB-9 connect- ors are readily available and easy to configure as DCE or DTE as required. Adapter Installation • This adapter is designed for connection to a UCC-6 Call Control Unit. It is not compatible with Teletypes configured with a Telex Call Control Unit. • Disconnect the Teletype from power (unplug AC cord or turn off power strip). Note that even if the Line/Local knob is in the OFF position, the 48vac power supply on the UCC-6 is still powered. • Plug the adapter onto the P2 connector as shown. • Connect the phone cable into the modular jack (use 4 or 6 conductor phone cable). DB-25 and DB-9 Wiring Modular DB-x connectors make it easy to connect your Teletype to computers with different interface require- ments because you can easily swap between DB-x con- nectors at the computer end of the phone cable. Custom wiring of the DB-x connector requires no soldering – just push the pre-wired pins into the DB-x positions your appli- cation requires. -
Experimental Evaluation and Modeling of RF Modems for Use In
Experimental Evaluation of RF Modems for Use in Fleets of Multiple Cooperating Autonomous Undersea Vehicles Radim Bartos,ˇ Venkata S. Gorla, Rick J. Komerska and Steven G. Chappell Leon N. Cyril, and Rohit Sharma Autonomous Undersea Systems Institute Department of Computer Science Lee, NH 03824 University of New Hampshire, Durham, NH 03824 {komerska, chappell}@ausi.org Email: {rbartos, vsx2, lno2, rohits}@cs.unh.edu Abstract— This paper presents the results of the experimental of modems involve some form of user packetization. Since evaluation of three radio frequency (RF) modems for use as com- mismatch between modem and user packetization may lead to munication infrastructure among multiple surfaced cooperating degraded performance, it is important to understand whether autonomous undersea vehicles (AUVs), gateway buoys, and land or ship based operators. RF modems are inherently more complex and how internal modem packetization is implemented in a than their wired counterparts which makes it difficult to estimate device. Some RF modems support multi-hop communication, the performance they deliver to an application. Throughput, often in a way that is completely hidden from the user. While communication latency, and latency variation (jitter) are used this simplifies the setup and use, it is important to understand as the measures of performance. The experiments were designed the impact such techniques have on the modem performance. to subject the modems to the traffic patterns common in the AUV fleets. The results of the presented experiments should help to An intermediate node consumes energy for transmissions of set realistic expectations of RF modem performance and aid in forwarded messages and this action may not be reported to the the design of comprehensive communication solutions for AUVs. -
Kernel Debug for Microsoft® Windows® Server 2003 on HP Integrity Servers
Kernel Debug for Microsoft® Windows® Server 2003 on HP Integrity Servers May 2004 (First Edition) Part Number 368341-001 © 2004 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Kernel Debug for Microsoft® Windows® Server 2003 on HP Integrity Servers May 2004 (First Edition) Part Number 368341-001 Contents Introduction......................................................................................................................... 5 Supported Servers ............................................................................................................. 5 Who Should Use the Microsoft Windows OS Kernel Debugger ..................................... 5 Setting up the Windows OS Kernel Debug Environment................................................ 5 Hardware Requirements............................................................................................................................... -
Application Note Basic Instructions to Communicate with TESLA
Application Note Basic Instructions to Communicate with TESLA Compatibility • TESLA model: 4000 ! • Firmware version: 2.1 • TCP version: 3.1 Contents TESLA Communication Options and Ports ............................................................................................................. 2 Ports .................................................................................................................................................................... 4 Front ............................................................................................................................................................... 4 Rear ................................................................................................................................................................ 5 Setting up Computer for TESLA Communication.................................................................................................... 6 Installing TESLA Control Panel (TCP) ................................................................................................................ 6 Installing and Configuring ERLPhase USB Driver .............................................................................................. 6 Configuring Null Modem Drive ............................................................................................................................ 9 Cyber Security - Role Based Access Control (RBAC) .......................................................................................... 15 Roles Summary................................................................................................................................................ -
D: Serial Driver
CHAPTER 7 Serial Driver 7 This chapter describes how you can use the Serial Driver to transfer data to a device connected to a Macintosh modem or printer port. The Serial Driver supports 7 asynchronous serial data communication between applications and serial devices Serial Driver through these ports. The Serial Driver provides low-level support for communicating with serial devices that cannot be accessed through the Communications Toolbox or Printing Manager. For example, a scientific instrument or a printer that does not support QuickDraw. Before you decide to use the Serial Driver, you should determine whether it is the appropriate solution for your communication needs. The Communications Toolbox is the recommended method for integrating modems and other telecommunications devices into the Macintosh environment. The Communications Toolbox provides hardware-independent services and a standard interface that offers compatibility with all Macintosh models. To find out more about the Communications Toolbox, see Inside the Macintosh Communications Toolbox. Likewise, the Printing Manager is the recommended interface for printers and similar output devices. Using the Printing Manager makes your hardware or software product compatible with every other device or application that supports this standard interface. Refer to Inside Macintosh: Imaging With QuickDraw for more information. To use the Serial Driver, you should understand how to open, close, and communicate with device drivers using the Device Manager. You can find this information in