DOCSLIB.ORG

Using the Wisconsin Packet Network

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

by Andy Nemec, KB9ALN This series of articles originally appeared in the Badger State Smoke Signals between 1995-2003, and is a tutorial designed to help newer packet operators navigate the Wisconsin Network and use common packet radio facilities. Packet Radio operators who have been active for some time may also find some of this information useful, and we hope you do, too. Part - 1 - Explains what a node is in it's basic form. Part - 2 - Explores how nodes are connected together in a network. Part - 3 - How nodes exchange routing information. Part - 4 - Making the best of bad paths. Part - 5 - A network journey - Green Bay to Milwaukee. Part - 6 - The journey continues. Part - 7 - Segmenting your connection circuit - how and why. Part - 8 - Q&A about nodes. Part - 9 - A look at the X-1J node. Part - 10 - An introduction to TCP/IP packet stations. Part - 11 - Using TCP/IP stations as network nodes. Part - 12 - Your station as part of the packet network. Part - 13 - Optimizing your radio and TNC for packet use. Part - 14 - BBS Basics with emphasis on the MSYS BBS. Part - 15 - Sending messages from an MSYS BBS. Part - 16 - Using an MSYS BBS as a Node. Part - 17 - Q&A on the MSYS BBS. Part - 18 - Using the Kantronics KA-Node Part - 19 - Using the REQDIR and REQFILE on BBSs. Part - 20 - 9600 bps TNC and radio information. Part - 21 - Handling NTS traffic via Packet Radio. Part - 22 - How to avoid "Flame" messages. Part - 23 - Part 1 of "The New Age" of Packet Radio. Part - 24 - Part 2 - Automated packet and "new" protocols. Part - 25 - TCP/IP and Future Packet. Part - 26 - More TCP/IP and future packet - network needs. Part - 27 - General Info on mail forwarding to your TNC. Part - 28 - Setting a Tiny-2 TNC up for mail forwarding. Part - 29 - Setting a KPC-3 TNC up for mail forwarding. Part - 30 - Setting up an AEA TNC for mail forwarding. Part - 31 - Emergency operations and packet radio. Part - 32 - More info on emergency packet operating. Part - 33 - Planning your emergency packet system. Part - 34 - An APRS Primer. Part - 35 - Internet Gateways - Part One. Part - 36 - Internet Gateways - Part Two. Part - 37 - Internet Gateways - Part Three. Part - 38 - Internet Gateway Q&A. Part - 39 - A look at Flexnet. Part - 40 - What is TNOS/Linux, do I need it? --Return- - Back to the Main Index Using the Wisconsin Network - Part One by Andy Nemec, KB9ALN This is part one of a series of articles designed to help packeteers understand and use the packet radio node network in Wisconsin. In Part one, we start off with a general discussion of nodes and networking, in basic terms. It is oriented toward the newer packet operators, but even experienced operators may find some useful information in here. We hope that this series adds to your enjoyment of the packet radio, and you find it good reading. What is a node? A node in it's basic form can be called an intellegent digipeater. Those of you who have operated your packet stations any time at all know that every TNC can be used as a Digital Repeater. This is done in order to extend the distance a packet station can send and receive packets. A digital repeater just simply repeats packets that are addressed to it. An intellegent digipeater has the ability to make sure that the repeated packets reach where they are supposed to go. Nodes are sophisticated, intellegent digipeaters, and some types are capable of much more than just digipeating. For our purposes, we will lump these nodes into 3 catagories, Non-Network Nodes, Special Purpose Nodes, and Network Nodes. A Non-Network node is one that basically is an intellegent Digipeater. It recieves a packet from one station, And sends it to another, checking to see if it arrived. Alone it serves a useful function. It will also tell you what stations it has heard, and when. A good example of a non-network node is a Kantronics KA-Node, sometimes called a "Wild Node". This KA-Node is part of most Kantronics TNC's. Some nodes, including fancier Kantronics nodes, perform special purposes, like Gateway Service. This brings us to the Special Purpose Nodes. These may connect 2-Meter packet radio activity to 20 Meters, connect Packet radio to a satellite link, access to a Public Bulletin Board System, or a DX Spotting system. Special purpose nodes may be linked to other nodes in a Network, but not always are. Some newer nodes provide so many features that they almost can be classified as Multi-Purpose. Then we come to Network Nodes. The Network Node is connected to other Network Nodes, and together they offer one attractive feature. That is the ability to send and receive packets over great distances with great speeds. These nodes carry digipeating on to a science, and even speak their own language to make sure the packets reach their destination. There are several different kinds of Network Nodes out there, and we will not devote the time and space to something you aren't likely to encounter. In Wisconsin, the over- whelming majority of Network Nodes in use are called "TheNet". This is the type of firmware (operating system) that the node uses to route packets to the right place. Our discussion of Network Nodes will be oriented toward "TheNet" type nodes found in Wisonsin. Note that the Network Nodes know how to get "route" a packet based on where you want to tell it to go. Each node has talked to other network nodes, telling it what it can hear and talk to. They exchange information on what other nodes it can connect to, and the signal quality of these nodes. We won't get into the details of how the process works here, but this fact is useful to know. Each of these nodes has a callsign, like any other Ham Radio Station. They are sponsored by a club or an individual, like a voice repeater. They also have another name they are known by, an alias. This alias generally starts with the state name, and 3 to 5 letters that give some clue to its location. Usually these are chosen from the local airport designator. For example, here in Green Bay our local network node is known as WIGRB, WI for Wisconsin, with GRB the airport designator. Other nodes on the network know that WIGRB exists, the best way to get to it, and where else it can go. This is valuable information for packet operators, because it helps to get them where they want to go. In Part-2, we will discuss how a Network is put together, so you understand how to use it in an effective way. Using the Wisconsin Network - Part 2 by Andy Nemec, KB9ALN In Part one of our series, we discussed what digipeaters and nodes are, the different kinds of nodes, and what makes them so special. In Part Two, we will continue our discussion. Let's review. A digipeater is a simple repeater of packets. A node is a more sophisticated repeater of packets, it knows if a packet was received, and can often allow you to send your packets over a very long distance. A network node is linked to other nodes and is often capable of doing more than just repeating your packets. We've talked about using nodes to pass our packets a longer distance. However, the need for a network of nodes grew out of another problem closely related to this need for distance. You may have found that not everybody in the packet community is on the same frequency in different parts of the state. This was done on purpose, so that people would not crowd up on one frequency, making it useless. Different areas of the state are divided up into seperate Local Areas. This is usually done by region, county, or even parts of a city. Each division is called a "LAN", meaning "Local Area Network", having a separate LAN frequency. Some way had to be devised so that different areas could communicate with each other, and that is where the network of nodes comes in. The Nuts and Bolts of a Node system. A node in it's physical form is a TNC, a Radio and the antennas it needs to work, similar to other packet stations. The TNC is specially modified with a different set of operating instructions. Some garden variety TNC's have a node built in, like a Kantronics TNC. Network nodes are most often dedicated TNC/Radio Combinations set up specially for the purpose. Network nodes are also connected, by Radio, by wire, or by both. Nodes connected by wire at one location form a "Node Stack". The node radios in a particular stack operate on different frequencies and all "Talk" to each other, and with other node stacks. They exchange information concerning their ability to contact other network nodes. Network Nodes that contact each other over the air usually do so on dedicated frequencies reserved for Node-to-Node commun- ication. This is called a "Backbone", and is devoted to connecting different nodes together so that your packets can be passed a greater distance and to other LAN frequencies. The graphic below will demonstrate a pair of network node stacks that carry packets between 2 LANS by way of a backbone. If you guessed that the people operating on the Green Bay LAN can connect to the people operating on the Appleton LAN even though they are on different frequencies, you are right.
Recommended publications
  • The Beginner's Handbook of Amateur Radio

    The Beginner's Handbook of Amateur Radio

    FM_Laster 9/25/01 12:46 PM Page i THE BEGINNER’S HANDBOOK OF AMATEUR RADIO This page intentionally left blank. FM_Laster 9/25/01 12:46 PM Page iii THE BEGINNER’S HANDBOOK OF AMATEUR RADIO Clay Laster, W5ZPV FOURTH EDITION McGraw-Hill New York San Francisco Washington, D.C. Auckland Bogotá Caracas Lisbon London Madrid Mexico City Milan Montreal New Delhi San Juan Singapore Sydney Tokyo Toronto McGraw-Hill abc Copyright © 2001 by The McGraw-Hill Companies. All rights reserved. Manufactured in the United States of America. Except as per- mitted under the United States Copyright Act of 1976, no part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of the publisher. 0-07-139550-4 The material in this eBook also appears in the print version of this title: 0-07-136187-1. All trademarks are trademarks of their respective owners. Rather than put a trademark symbol after every occurrence of a trade- marked name, we use names in an editorial fashion only, and to the benefit of the trademark owner, with no intention of infringe- ment of the trademark. Where such designations appear in this book, they have been printed with initial caps. McGraw-Hill eBooks are available at special quantity discounts to use as premiums and sales promotions, or for use in corporate training programs. For more information, please contact George Hoare, Special Sales, at [email protected] or (212) 904-4069. TERMS OF USE This is a copyrighted work and The McGraw-Hill Companies, Inc.
  • Kenwood TH-D74A/E Operating Tips

    Kenwood TH-D74A/E Operating Tips

    1 Copyrights for this Manual JVCKENWOOD Corporation shall own all copyrights and intellectual properties for the product and the manuals, help texts and relevant documents attached to the product or the optional software. A user is required to obtain approval from JVCKENWOOD Corporation, in writing, prior to redistributing this document on a personal web page or via packet communication. A user is prohibited from assigning, renting, leasing or reselling the document. JVCKENWOOD Corporation does not warrant that quality and functions described in this manual comply with each user’s purpose of use and, unless specifically described in this manual, JVCKENWOOD Corporation shall be free from any responsibility for any defects and indemnities for any damages or losses. Software Copyrights The title to and ownership of copyrights for software, including but not limited to the firmware and optional software that may be distributed individually, are reserved for JVCKENWOOD Corporation. The firmware shall mean the software which can be embedded in KENWOOD product memories for proper operation. Any modifying, reverse engineering, copying, reproducing or disclosing on an Internet website of the software is strictly prohibited. A user is required to obtain approval from JVCKENWOOD Corporation, in writing, prior to redistributing this manual on a personal web page or via packet communication. Furthermore, any reselling, assigning or transferring of the software is also strictly prohibited without embedding the software in KENWOOD product memories. Copyrights for recorded Audio The software embedded in this transceiver consists of a multiple number of and individual software components. Title to and ownership of copyrights for each software component is reserved for JVCKENWOOD Corporation and the respective bona fide holder.
  • Examining Ambiguities in the Automatic Packet Reporting System

    Examining Ambiguities in the Automatic Packet Reporting System

    Examining Ambiguities in the Automatic Packet Reporting System A Thesis Presented to the Faculty of California Polytechnic State University San Luis Obispo In Partial Fulfillment of the Requirements for the Degree Master of Science in Electrical Engineering by Kenneth W. Finnegan December 2014 © 2014 Kenneth W. Finnegan ALL RIGHTS RESERVED ii COMMITTEE MEMBERSHIP TITLE: Examining Ambiguities in the Automatic Packet Reporting System AUTHOR: Kenneth W. Finnegan DATE SUBMITTED: December 2014 REVISION: 1.2 COMMITTEE CHAIR: Bridget Benson, Ph.D. Assistant Professor, Electrical Engineering COMMITTEE MEMBER: John Bellardo, Ph.D. Associate Professor, Computer Science COMMITTEE MEMBER: Dennis Derickson, Ph.D. Department Chair, Electrical Engineering iii ABSTRACT Examining Ambiguities in the Automatic Packet Reporting System Kenneth W. Finnegan The Automatic Packet Reporting System (APRS) is an amateur radio packet network that has evolved over the last several decades in tandem with, and then arguably beyond, the lifetime of other VHF/UHF amateur packet networks, to the point where it is one of very few packet networks left on the amateur VHF/UHF bands. This is proving to be problematic due to the loss of institutional knowledge as older amateur radio operators who designed and built APRS and other AX.25-based packet networks abandon the hobby or pass away. The purpose of this document is to collect and curate a sufficient body of knowledge to ensure the continued usefulness of the APRS network, and re-examining the engineering decisions made during the network's evolution to look for possible improvements and identify deficiencies in documentation of the existing network. iv TABLE OF CONTENTS List of Figures vii 1 Preface 1 2 Introduction 3 2.1 History of APRS .
  • Mind the Uppercase Letters

    Mind the Uppercase Letters

    Integration of APRS Network with SDI Tomasz Kubik1,2, Wojciech Penar1 1 Wroclaw University of Technology 2 Wroclaw University of Environmental and Life Sciences Abstract. From the point of view of large information systems designers the most important thing is a certain abstraction enabling integration of heterogeneous solutions. Abstraction is associated with the standardization of protocols and interfaces of appropriate services. Behind this façade any device or sensor system may be hidden, even humans recording their measurements. This study presents selected topics and details related to two families of standards developed by OGC: OpenLS and SWE. It also dis- cusses the technical details of a solution built to intercept radio messages broadcast in the APRS network with telemetric information and weather conditions as payload. The basic assumptions and objectives of a prototype system that integrates elements of the APRS network and SWE are given. Keywords: SWE, OpenLS, APRS, SDI, web services 1. Introduction Modern measuring devices are no longer seen as tools for qualitative and quantitative measurements only. They have become parts of highly special- ized solutions, used for data acquisition and post-processing, offering hardware and software interfaces for communication. In the construction of these solutions the latest technologies from various fields are employed, including optics, precision mechanics, satellite and information technolo- gies. Thanks to the Internet and mobile technologies, several architectural and communication barriers caused by the wiring and placement of the sensors have been broken. Only recently the LBS (Location-Based Services) entered the field of IT. These are information services, available from mo- bile devices via mobile networks, giving possibility of utilization of a mobile This work was supported in part by the Polish Ministry of Science and Higher Edu- cation with funds for research for the years 2010-2013.
  • Federal Communications Commission Record 10 FCC Red No

    Federal Communications Commission Record 10 FCC Red No

    FCC 95-113 Federal Communications Commission Record 10 FCC Red No. 9 alleviate congestion in the 222-225 MHz band and to per Before the mit the development of new regional and nationwide pack Federal Communications Commission et networks. Washington, D.C. 20554 3. The 216-218 and 219-220 MHz bands currently are allocated on a primary basis to the maritime mobile service for Automated Maritime Telecommunications Systems (AMTS).2 The 218-219 MHz band is allocated on a primary ET Docket No. 93-40 basis to Interactive Video and Data Services (IVDS).3 In addition, frequencies within the 216-220 MHz band are In the Matter of allocated on a secondary basis to wildlife telemetry,4 fixed and land mobile services, and aeronautical mobile Allocation of the RM-7747 services.5 Television broadcast channel 13 operations oc 219-220 MHz Band for Use by cupy the adjacent 210-216 MHz band. the Amateur Radio Service 4. Packet radio systems transmit digital data in groups or "packets" .using a specified format. Radio channels used by these systems are occupied only during the time individual REPORT AND ORDER "packets" of data are actually being transmitted. Upon completion of a transmission the channel becomes avail Adopted: March 14,1995; Released: March 17,1995 able for other traffic. Amateurs use packet radio for trans mitting a variety of material, including messages, computer programs, graphic images and data bases. These systems can By the Commission: be used in times of emergency to efficiently carry a large volume of messages when other communications facilities are out-of-service or overloaded.
  • Digital Modes RTTY

    Digital Modes RTTY

    Digital Modes RTTY Digital communication modes represent one of the fastest growing areas of interest in amateur radio, with the past decade seeing many developments. While there are other digital modes that radio amateurs are experimenting with, RTTY, AMTOR, and Packet Radio are the main digital modes on amateur radio. Newer modes such as GTOR are also emerging as amateur radio continues to develop in the area of digital communications. Baudot code is still the common denominator of digital modes, but it is far from standardised itself. While many use the term Baudot Code, others use the term Murray Code. These two names acknowledge two important telegraph pioneers, both of whom made major contributions in this field, however the correct term is CCITT International Alphabet No. 2. The differences between in practical systems is apparent in the punctuation characters and would not be noticed between two operators unless they used punctuation such as ! : % @ etc. Baudot is sent at differing speeds in different areas. Most US operation is at 45.45 baud (a hangover from a speed limitation by the FCC of 60 wpm for any coded operation), at 45 baud in Europe, while all operation in New Zealand is at 50 baud (after a collective decision to standardise to the commercial speed). Nowadays, computers have almost completely taken over from the mechanical teleprinter, so baud rate changes are no longer the problem they once were. ASCII This is used to a very small degree on amateur bands. The proliferation of personal computers in the ham shack, often with in–built communications facilities designed to work on telephone networks, encourages this mode, however there are much more practical ways to use a computer on the air.
  • PACKET RADIO from AEA to Z___Page 1 ABOUT the AUTHOR Some of Buck's Books About PACKET RADIO & Digi

    PACKET RADIO from AEA to Z___Page 1 ABOUT the AUTHOR Some of Buck's Books About PACKET RADIO & Digi

    ABOUT THE AUTHOR G. E. "Buck" Rogers Sr. K4ABT, is Senior Systems Engineer for ERICSSON Communications. Buck is a pioneer of packet radio, having written many feature articles for the leading Amateur radio, commercial and trade publications. He is PACKET RADIO Editor for CQ MAGAZINE, and authors the PACKET USERS NOTEBOOK, a monthly column in CQ. Some of Buck’s books about PACKET RADIO & Digital communications are: The PACKET RADIO AEA to Z Handbook The PACKET RADIO Beginner’s Guidebook The PACKET RADIO X-1J SysOp’s Handbook The PACKET RADIO Operator’s Handbook The PACKET RADIO OPERATORS MANUAL The PACKET RADIO General Information Handbook The "PRIME" Packet Radio Is Made Easy The PACKET USERS NOTEBOOK The ADVANCED PACKET RADIO HANDBOOK The PACKET COMMANDS HANDBOOK The GLOSSARY of PACKET TERMS HANDBOOK The RS-232 as related to PACKET HANDBOOK Buck conducts forums and seminars on packet radio and digital communications. Buck is an RF and Data Communications Engineer. He was instrumental in the design and implementation of the U. S. Air Force Local Area Network, Wide Area Network, and Global Information Networks (LAN, WAN & GIN). His credentials in other fields of R F communications include terrestrial microwave systems design, television/radio broadcast station design, and Public Service EDACS systems design. His communications consulting travels include the United States, Europe, Asia, and countries throughout the world. Buck is a licensed Amateur of 44 years, and holds the "lifetime" Commercial FCC First Class license (now called the General Class Commercial license) ABOUT THIS BOOK ______________________ PACKET RADIO from AEA to Z___Page 1 This book will provide detailed information for the newcomer to Packet Radio and to the seasoned veteran.
  • Linux Amateur Radio AX.25 HOWTO

    Linux Amateur Radio AX.25 HOWTO

    Linux Amateur Radio AX.25 HOWTO Jeff Tranter, VE3ICH [email protected] v2.0, 19 September 2001 The Linux operating system is perhaps the only operating system in the world that can boast native and standard support for the AX.25 packet radio protocol utilized by Amateur Radio operators worldwide. This document describes how to install and configure this support. Linux Amateur Radio AX.25 HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Changes from the previous version...................................................................................................1 1.2. Where to obtain new versions of this document...............................................................................1 1.3. Other related documentation.............................................................................................................1 2. The Packet Radio Protocols and Linux........................................................................................................3 2.1. How it all fits together......................................................................................................................3 3. The AX.25/NET/ROM/ROSE software components...................................................................................5 3.1. Finding the kernel, tools and utility packages..................................................................................5 3.1.1. The
  • Ethics and Operating Procedures for the Radio Amateur 1

    Ethics and Operating Procedures for the Radio Amateur 1

    EETTHHIICCSS AANNDD OOPPEERRAATTIINNGG PPRROOCCEEDDUURREESS FFOORR TTHHEE RRAADDIIOO AAMMAATTEEUURR Edition 3 (June 2010) By John Devoldere, ON4UN and Mark Demeuleneere, ON4WW Proof reading and corrections by Bob Whelan, G3PJT Ethics and Operating Procedures for the Radio Amateur 1 PowerPoint version: A PowerPoint presentation version of this document is also available. Both documents can be downloaded in various languages from: http://www.ham-operating-ethics.org The PDF document is available in more than 25 languages. Translations: If you are willing to help us with translating into another language, please contact one of the authors (on4un(at)uba.be or on4ww(at)uba.be ). Someone else may already be working on a translation. Copyright: Unless specified otherwise, the information contained in this document is created and authored by John Devoldere ON4UN and Mark Demeuleneere ON4WW (the “authors”) and as such, is the property of the authors and protected by copyright law. Unless specified otherwise, permission is granted to view, copy, print and distribute the content of this information subject to the following conditions: 1. it is used for informational, non-commercial purposes only; 2. any copy or portion must include a copyright notice (©John Devoldere ON4UN and Mark Demeuleneere ON4WW); 3. no modifications or alterations are made to the information without the written consent of the authors. Permission to use this information for purposes other than those described above, or to use the information in any other way, must be requested in writing to either one of the authors. Ethics and Operating Procedures for the Radio Amateur 2 TABLE OF CONTENT Click on the page number to go to that page The Radio Amateur's Code .............................................................................
  • Amateur Radio Guide to Digital Mobile Radio (DMR)

    Amateur Radio Guide to Digital Mobile Radio (DMR)

    Amateur Radio Guide to Digital Mobile Radio (DMR) By John S. Burningham, W2XAB February 2015 Talk Groups Available in North America Host Network TG TS* Assignment DMR-MARC 1 TS1 Worldwide (PTT) DMR-MARC 2 TS2 Local Network DMR-MARC 3 TS1 North America 9 TS2 Local Repeater only DMR-MARC 10 TS1 WW German DMR-MARC 11 TS1 WW French DMR-MARC 13 TS1 Worldwide English DMR-MARC 14 TS1 WW Spanish DMR-MARC 15 TS1 WW Portuguese DMR-MARC 16 TS1 WW Italian DMR-MARC 17 TS1 WW Nordic DMR-MARC 99 TS1 Simplex only DMR-MARC 302 TS1 Canada NATS 123 ---- TACe (TAC English) (PTT) NATS 8951 ---- TAC-1 (PTT) DCI 310 ---- TAC-310 (PTT) NATS 311 ---- TAC-311 (PTT) DMR-MARC 334 TS2 Mexico 3020-3029 TS2 Canadian Provincial/Territorial DCI 3100 TS2 DCI Bridge 3101-3156 TS2 US States DCI 3160 TS1 DCI 1 DCI 3161 TS2 DMR-MARC WW (TG1) on DCI Network DCI 3162 TS2 DCI 2 DCI 3163 TS2 DMR-MARC NA (TG3) on DCI Network DCI 3168 TS1 I-5 (CA/OR/WA) DMR-MARC 3169 TS2 Midwest USA Regional DMR-MARC 3172 TS2 Northeast USA Regional DMR-MARC 3173 TS2 Mid-Atlantic USA Regional DMR-MARC 3174 TS2 Southeast USA Regional DMR-MARC 3175 TS2 TX/OK Regional DMR-MARC 3176 TS2 Southwest USA Regional DMR-MARC 3177 TS2 Mountain USA Regional DMR-MARC 3181 TS2 New England & New Brunswick CACTUS 3185 TS2 Cactus - AZ, CA, TX only DCI 3777215 TS1 Comm 1 DCI 3777216 TS2 Comm 2 DMRLinks 9998 ---- Parrot (Plays back your audio) NorCal 9999 ---- Audio Test Only http://norcaldmr.org/listen-now/index.html * You need to check with your local repeater operator for the Talk Groups and Time Slot assignments available on your local repeater.
  • Pactor Brochure

    Pactor Brochure

    SCS PTC-II Radio Modem HF / VHF / UHF Up to 30 times faster than AMTOR, up to 6 times faster than PACTOR I Send email, transfer files, real-time data links. The PTC-II modem from Special Communications Systems is the data interface between your PC and radio equipment. From the German developers of the PACTOR I protocol comes PACTOR II, the most robust digital mode available. The PTC-II will maintain links in conditions with signal to noise ratios of minus 18 dB. That means data transfer with absolutely inaudible signals. Test proven with a 16 milliwatt link between Europe and Australia! The PTC-II is fully backwards compatible with all known PACTOR I implementations. Powered by a powerful Motorola CPU and DSP (digital signal processing), the PTC-II stands out as superior technology for HF radio data transfers. With optional Packet radio options for VHF/UHF 9600+ baud rates can be employed. backview Simple installation with compatible radios from Icom, Kenwood, Yaesu, SGC, SEA, Furuno, R&S and others. Use the PTC-II with commercial stations WLO, SailMail and others, as well as the international network of amateur radio opetators that support Pactor II. PC software for Windows or DOS. Desktop Or RCU Laptop PC Remote Remote Control controled PTC-II Win95 / 498 devices: Unit (optional) antenna or DOS rotor, lights, contact closures, external sensors, Radio control via Audio in/out, PTT etc! RS-232 (optional) and B+ to PTC-II VHF or UHF VHF or UHF transceiver for use transceiver for use Marine, Commercial or Amateur with Packet AFSK with Packet FSK module (optional) module (optional) HF SSB Transceiver Amateur • Commercial • Industrial • Marine Special Communications Systems GmbH Rontgenstr.
  • (Pdf) Download

    (Pdf) Download

    1 2 • Winlink programs group: “Official Group to support Winlink Team developed Products, both user and gateway software” • Winlink_for_EmComm: “Supports the discussion and use of the Winlink network and Winlink products for emergency or event support communications. ” 3 4 5 6 7 8 1. Digital voice radio works in exactly the same fashion, except that it deals with audio input, not text. 2. PACKET-1200 uses frequency shift keying (FSK) modulation with a 1000Hz shift and 1200 Bd symbol rate. There are a number of variations for PACKET-1200, including a PSK-based satellite version. PACKET-1200 can be seen in the VHF and UHF bands with indirect FM Modulation. FM bandwidth is 12 kHz. 3. See https://www.sigidwiki.com/wiki/PACKET#PACKET-1200 9 10 11 12 • That’s the packet sound • Each individual packet! • Carrier detect • ”NAK” = “NO ACKNOWLEDGEMENT” – resend • ”ACK” – “ACKNOWLEDGEMENT” – send the next packet • Too many retries, and the sending station stops sending (connection is dropped) • Breaking the message into small packets makes it easier to send a large message. But ALL packets MUST be received in order for the message to be read, 13 • One bye = 8 bits = 1 alphanumeric character • See https://tapr.org/pub_ax25.html • FLAG: start and end of each packet • Address: sender, receiver, and the path in between • Control (CTRL): The control field is responsible for identifying the type of “frame” being sent, and is also used to convey commands and responses from one end of the link to the other in order to maintain proper link control • The length of DATA is ≤ 255, and is set by the use.