开云体育

The latest firmware revision to the NinoTNC has PSK shaped transmit envelopes 2400 Hz wide and up to 2400 baud! // 3/4.31: 24-Oct-23 : // : Improved DCD LED coast time and CSMA logic. // : Added IL2P+CRC (IL2Pc) modes to reduce false decodes. // : Restored full dynamic range of AGC. // : Change self-learn callsign algorithm to UI frames only. // : // : MODE SWITCH MAPPING // : // : *** GFSK MODES ** // : These require a '9600' data port or * // : discriminator/varactor connection. * // : IL2P, IL2Pc modes included for performance comparison. * // : ** // : 0000 9600 GFSK AX.25 * // : 0001 9600 GFSK IL2P * // : 0010 9600 GFSK IL2Pc * // : 0011 4800 GFSK IL2P * // : 0100 4800 GFSK IL2Pc * // : ** // : // : *** FM AFSK MODES **** // : These are suitable for FM radio speaker/ * // : mic connection. * // : ** // : 0101 2400 DPSK IL2P Phase reversal of 2400 Hz tone * // : 0110 1200 AFSK AX.25 Legacy FM Packet, APRS * // : 0111 1200 AFSK IL2P * // : ** // : // : *** SSB AFSK MODES *** // : Legacy HF packet 1600/1800 Hz tone FSK. * // : Filtered for 500 Hz occupied bandwidth. * // : ** // : 1100 300 AFSK AX.25 * // : 1101 300 AFSK IL2P * // : 1110 300 AFSK IL2Pc * // : ** // : // : *** SHAPED PSK MODES * // : These are suitable for SSB radios, or FM radios. * // : Phase modulation of 1500 Hz tone. * // : Filtered for occupied bandwidth depending on baud. * // : 300 BPSK, 600 QPSK send 300 symbols/sec, 500 Hz OBW. * // : 1200 BPSK, 2400 QPSK send 1200 symbols/sec, 2400 Hz OBW.* // : ** // : 1000 300 BPSK IL2Pc * // : 1001 600 QPSK IL2Pc * // : 1010 1200 BPSK IL2Pc * // : 1011 2400 QPSK IL2Pc * // : 1111 1200 BPSK IL2P * // : ** 73 'QBH

ARRL Hails FCC Action to Remove Symbol Rate Restrictions 11/13/2023 ARRL The National Association for Amateur Radio? reports that earlier today, the FCC Commissioners unanimously voted to amend the Amateur Radio Service rules to replace the baud rate limit on the Amateur HF bands with a 2.8 kHz bandwidth limit to permit greater flexibility in data communications. “The Federal Communications Commission today adopted new rules to incentivize innovation and experimentation in the amateur radio bands by removing outdated restrictions and providing licensees with the flexibility to use modern digital emissions,” announced FCC. “Specifically, we remove limitations on the symbol rate (also known as baud rate) -- the rate at which the carrier waveform amplitude, frequency, and/or phase is varied to transmit information -- applicable to data emissions in certain amateur bands,” concluded the FCC Report and Order and Further Notice of Proposed Rulemaking, adopted November 13, 2023. “The amateur radio community can play a vital role in emergency response communications, but is often unnecessarily hindered by the baud rate limitations in the rules.” Consistent with ARRL’s request, the amended rules will replace the current HF restrictions with a 2.8 kHz bandwidth limit. “We agree with ARRL that a 2.8 kilohertz bandwidth limitation will allow for additional emissions currently prohibited under the baud rate limitations while providing sufficient protections in the shared RTTY/data sub bands,” concluded the FCC Report and Order. ARRL President Rick Roderick, K5UR, hailed the FCC’s action to remove the symbol rate restrictions. Roderick stated that “this action will measurably facilitate the public service communications that amateurs step up to provide, especially at times of natural disasters and other emergencies such as during the hurricane season. Digital technology continues to evolve, and removing the outmoded data restrictions restores the incentive for radio amateurs to continue to experiment and develop more spectrum-efficient protocols and methods while the 2.8 kHz bandwidth limit will help protect the shared nature of our bands. We thank Congresswoman [Debbie] Lesko (AZ-08) for her efforts on behalf of all Amateurs to get these restrictions removed.” In a Further Notice of Proposed Rulemaking (FNPRM), the FCC proposes to eliminate similar restrictions where they apply in other bands. “We propose to remove the baud rate limitation in the 2200 meter band and 630 meter band … and in the very high frequency (VHF) bands and the ultra-high frequency (UHF) bands. Additionally, we seek comment on the appropriate bandwidth limitation for the 2200 meter band, the 630 meter band, and the VHF/UHF bands.” ARRL has previously expressed its support for eliminating the symbol rate limits in favor of bandwidth limits where they apply on the VHF and UHF bands but suggested that the bandwidth limits themselves be reviewed in light of today’s technology and tomorrow’s possibilities. Similarly, when eliminating the baud limits on the 2200 and 630-meter bands, consideration should be given to what, if any, bandwidth limits are appropriate.

https://www.arrl.org/news/arrl-urges-comments-to-fcc-on-60-meter-band Link to article above. ARRL Urges Comments to FCC on 60-Meter Band 10/10/2023 ARRL The National Association for Amateur Radio? is asking that all radio amateurs urge the Federal Communications Commission (FCC) to continue the existing use of the 60-meter band. A public comment period is open until October 30, 2023. ARRL encourages expressions of support to the FCC for the current 100 W ERP power limit (instead of reducing the power limit to 15 W EIRP) and continuing secondary access to the current channels. ARRL has assembled a web page with instructions on how to submit your comments, as well as background information on the issue: www.arrl.org/60-meter-band. To submit a filing of your comments for the FCC’s consideration in the rulemaking process, go to the FCC web page for the Notice of Proposed Rulemaking’s (NPRM) Docket Number 23-120 at https://www.fcc.gov/ecfs/search/docket-detail/23-120. If you wish to directly enter your comments, select the button labeled SUBMIT AN EXPRESS FILING or if you are uploading a document that contains your comments, select SUBMIT A STANDARD FILING. When submitting your comments, be sure the correct proceeding’s docket number, 23-120, is included on the form. Your name and comments will be entered into the official public record of the proceedings and will be viewable by anyone who visits the docket web page. While radio amateurs are encouraged to include any comments they would like in their submissions, they’re especially encouraged to draw upon their personal experiences using the 60-meter band for public service purposes and for its location between the amateur 80- and 40-meter bands, which is critical to ensuring signal propagation to certain geographic areas during variations in time and the solar cycle. For example, ensuring radio amateurs have a continuum of communication capabilities across the 7 MHz, 5 MHz, and 3.5 MHz bands is valuable for emergency communications, especially between the US and Caribbean nations during hurricane season. Some of the main points to comment on for this NPRM are: Urging the FCC to keep the four existing channels allocated to amateur radio on a secondary basis. Urging the FCC to keep the 100 W power limit for the four existing channels and the new 15 kHz subband. ARRL Public Relations and Outreach Manager Sierra Harrop, W5DX, underscored the importance of commenting, urging members to speak up. “ARRL members make up the strongest voice in matters of amateur radio spectrum defense,” said Harrop. “Your membership and participation in the rulemaking process both ensure ARRL continues to make the difference when our band privileges are threatened. Please join us in effort to protect our 60-meter band privileges

From the Editor We hope you enjoyed the premier issue of The NTS Letter. We heard from many of you and thank you for your kind words of support. We hope you will spread the word to others. Feel free to share this newsletter with those who may or may not be ARRL members but who have shown an interest in message handling. (Of course, you could encourage non-members to join.) Also remember to send news or suggestions from your Sections. We want to hear from you. NTS 2.0 Update We have begun to produce PowerPoint presentations and training videos, which will be available on the NTS2 website. The first training video is now available at https://nts2.arrl.org/ntsgte-an-aprs-nts-gateway/. This video is about the APRS-NTS Gateway, and information on this topic can be found later in this newsletter. The teams are currently producing a video about the encapsulation of ICS-213 and other agency forms for use particularly on voice and CW networks. Because we believe recognition is so important not only for showing appreciation, but also for motivating and encouraging traffic handlers, we have been working on a recognition program for both new and experienced traffic handlers. More on that in an upcoming issue. Because emergency service agencies expect delivery of messages within 30 minutes, as reported last month Don Rolph, AB1PH, has conducted transcontinental tests on 20 meters using digital modes to explore how propagation issues affect point-to-point communication across the country. Don reports these were mostly successful but says more tests will be conducted on 30 meters. He welcomes more operators to participate in these tests. There are no updates on the new net directory, but we continue to press forward. ICS-213 Compatibility: Using Radiograms to Pass Served Agency Forms From the NTS2.arrl.org website: In emergencies, practice exercises, and other scenarios, radio amateurs will likely pass messages for the various served agencies, such as FEMA, Red Cross, and others. It is important that we are able to relay these messages in a way that is compatible with the agencies' existing methods. While NTS stations are used to using the standard radiogram format, agencies will use their own forms, such as the ICS-213 form pictured here. As part of NTS 2.0, numerous NTS stations and EmComm operators have worked together to define methods and procedures for passing these various agency forms encapsulated within radiograms. This allows the NTS relay stations to handle radiograms as they are used to, while served agencies can continue to utilize their forms. The NTS 2.0 website discusses how to encode these complex forms for transmission through the National Traffic System as radiograms, and their final delivery to the served agency in the native form format. We realize that radiograms with encapsulated agency forms are much longer than traditional radiograms and take more time and effort when passed on CW or voice modes. We expect these forms to be passed primarily via digital modes for most emergencies, but there can indeed be circumstances when they need to be sent via voice or CW. This could be due to the scale and type of emergency, or because of delivering station capabilities. To be prepared for these circumstances, we hope voice and CW participants and their nets will take pains to become familiar with the forms and develop proficiency through the practice of handling the encoded forms on those modes. The NTS 2.0 Digital and EmComm working groups have developed encoding for: ICS-213 form Texas EMA STAR form HICS-213 form ARC-213 form It is anticipated that encoding for more forms will be established as we move forward. We will be updating this material as it is developed. Massachusetts Rhode Island Digital Net A New England NTS net played an integral role in a recent ARES Simulated Emergency Test on Cape Cod. The Massachusetts Rhode Island Digital Net (MARIDN) meets weekly for the purpose of passing formal, written NTS messages within, into, and out of the Sections of Eastern and Western Massachusetts and Rhode Island. MARIDN is

The Great Car Run Packet Caper Every August antique car enthusiasts hold a 90 mile run for cars made before 1920 that goes from New London, MN to New Brighton, MN. For many years the Willmar Ham radio club provided communications support by placing mobile hams with 2 meter transceivers amoungst the participants. They used the 146.91 repeater which is a wide area coverage machine and put up a net control tent at the Buffalo, MN halfway stop. Usually a crowd would gather around to hear the progress. The old guard in our club reveled in this opportunity to show off their repeater and made no secret of it. One of the other factions in our club were the digital packet radio folks like myself who saw greater possibilities by merging radio and data. One of the obvious uses combined the new GPS service many of us had with digital radio to allow us to track a GPS transmitter paired together. The much re known APRS was in it's infancy then - the biggest snag was a lack of decent maps to plot on the computer screen. The popular thing at the time was to attach a GPS to a laptop computer running the Delorme mapping program. The present location would show as a green arrow on a very detailed map! In doing some experiments, I discovered it was possible to send the data from a GPS to the computer via packet radio, cutting the cord, so to speak. We ran experiments on quiet simplex frequencies to fine tune the process and stay below the "old guard's" radar. In the summer of 1994 with the help of John K0CQW and Joe N0NCO, we put together the system. John got us access to a tower near Lake Minne Belle where we installed a temporary packet repeater which filled in a coverage hole once we were out of the Spicer packet nodes range. Joe set up his own tent in Buffalo with a 1000W Honda generator, packet station, antenna and the biggest monitor I'd seen attached to his laptop computer that was running the Delorme mapping program. I was the tracking car. It took a little convincing to allow me to join the pack, but once in, I just stayed a safe distance behind whoever was the leader. I was mostly in the dark as to how it was working as my radio was tied up doing packet. When we stopped in Litchfield I was able to hear the good news that everything was working better than we'd hoped! At Buffalo, word got out that Joe had a graphic display of the run going and the crowd gathered round to watch. When we got to the Buffalo fairgrounds, our stopping point, I peeled off and drove over to the tent. The folks watching the arrow thought the old car was outside, but, it was just me, grinning ear to ear in my Dodge Colt with the GPS antenna "boob" on the roof. For a day, at least, we'd stole their fire. Mike N0QBH

Early Packet Radio in central MN In 1991 when I got my Ham radio licence the other technical "rage" was Bulletin Board Services (BBS) which operated over phone lines with dial up modems allowing us to read and send messages (think early email) with our computer. The downside of BBS activity was cost. It was usually long distance to any of the bigger, non local BBS's, so the meter was always running. On the other hand, I'm sure the phone companies loved it. After I had gotten my feet wet in amateur radio, mainly in the VHF and UHF FM operations, I discovered Hams also communicated with computer modems over radio channels at whopping speeds of 300 and 1200 baud! Early on, a group of Hams from Tuscon, AZ designed and sold a modem kit called a Terminal Node Connector 2 (TNC2). It was an instant hit and several companies cloned the design, putting it in range of the typical ham for around $100. The TNC was connected to the computer with a serial cable and to the radio's microphone connection. This facet of ham radio took off, primarily because hams also tended to be early adopters of personal computers and love new gadgets. Our local college in Willmar had a wireless communication program that was very popular turning out two way radio technicians. It's instructor, Roger Williams W0WUG(sk) had a packet station at the lab and it was using a 100' tall tower, one of two the school had for training. As a result of it's height and quality installation, it had a wide coverage and many area hams used it to get on packet radio. About the same time Ham programmers were creating BBS and network software (mostly free) designed for radio use that also included message forwarding and routing routines. BBS programs were computer based while network modems were EPROM replacements for the TNC2 that eliminated the user interface and used intelligent algorithms to route the traffic. In essence, a network for Packet Radio was evolving before our eyes. Hams with high locations, like myself, were able to connect to these packet radio networks at night that were starting to appear in Minneapolis and St Cloud. It made us want more... One of the local hams, Dick Butler W0RIM(sk), had connections to the St. Cloud Ham club and made the introductions to Hank Koch NF0H(sk), Ed Steinblock K0VU(sk) and Jack Maus W0MBD(sk). Hank was already running a BBS, but found the connection to Minneapolis to be very unreliable. We all agreed a designated "backbone" that would move the traffic between us and the metro was needed. The result was a UHF (446 MHz) path extending from the west metro to a 1400' site east of Cold Spring. The Cold Spring site had a line of sight path to the Mpls "node" and a clear north-south path to St Cloud and my QTH on Ringo Lake near Spicer. Frankly, we were very fortunate geography was our friend. We used cutting edge (at the time) 9600 baud radio modems grafted to network TNCs for greatly increased throughput. At the time, the radio transceivers had to be modified to work at 9600 baud, so I turned to Roger W0WUG(sk) and a student of his Joel N0NCO, from Ridgewater Wireless to teach me how. I might also add another of Roger's former students, Dan Karg WB0GDB, was also active in packet radio and created the 9600 baud connection at the Minneapolis end. This, in turn, connected us to the rest of the packet radio BBS "world". With a solid connection in place, we had two local access BBSs running on each end for a total of four. Two in St Cloud, one at Ringo Lake and one in Willmar. About the same time I procured a rent free location at the 150' level on a 500' tower near Spicer. This was a wide area access node running 50W on VHF (145 MHz) and 1200 baud. With it, hams from a 30 mile radius could easily access the two local BBSs as well as other hams on this network. It was called MNSPI and served the packet community until the tower site was sold and we had to vacate around 2000. One of the earlest users of the Internet were Ham radio packet operators using "wormholes" between universities (where the Internet resided in those days). These w

Just a note with a new subject line - the WILMAR packet radio node is on line and open to ALL licensed Ham users. It's frequency is 145.670 MHz simplex. The packet data rate is 1200 baud. WILMAR is the node's alias and it has to conform to callsign max length of 6 characters. That's why it's spelled wrong :) A node's job is to act as a relay with good ears and a powerful "voice" due to it's antenna being on a commercial tower. This lets it connect weaker or more distant stations to each other, who normally don't hear each other well, much like a repeater does for voice comms. The WILMAR node responds to three different callsigns which have different purposes. To use the "relay" feature you connect to the alias WILMAR by typing c wilmar then press enter. Once connected, typing c and the call of the station you want initiates a connect attempt. To use the mailbox feature you instead connect to W0SW-1 by typing c w0sw-1 then enter. Once connected you will get a short menu of choices and typing h for a help menu. The main thing to remember is you really can't break anything beyond your own station and if you get frustrated, take a break. The 3rd callsign is last because it does nothing if you connect to it. W0SW is for connecting to a person sitting at the node. Normally it is unattended. This link is broken up into easy to digest parts and covers packet radio end to end. Even if it's 25 yrs old! https://choisser.com/packet/ Also, I'm looking for a contact with the StCloud club who would know about their node on 145.67 MHz. We need it working! 73 Mike N0QBH

Tony WD0HXV & I removed the WILMAR (note the spelling) node TNC from it's normal location under the LEC big tower Friday. This was done to change the node callsign from Ace Bonnema's KB0MNU to the Willmar EAR club callsign W0SW and to check over the health of the unit. I also turned off the CW ider as it is bad for the network and not required in the US. Tony and I tentatively plan to reinstall it Sunday. I'm hoping to cobble together a packet station for the meeting Tuesday and demo it to the troops. 73 Mike N0QBH

Hello Gang, I came across this important article about the National Traffic System. Which we really should all be familiar with in our amateur radio hobby. It looks like they are making some changes/updates this year in 2023 with this system NTS 2.0. https://tinyurl.com/NTS20VIDEO (The Video) https://tinyurl.com/NationalTrafficSystem (The Article) https://tinyurl.com/ARRL-NTS-20 (The Website) So please let us have a discussion about this subject at our next radio club meetings. On what we can do to practice and get familiar with on how to use this system. (Including when and where these nets are to pass traffic on.) Especially for emergency communications. And also our clubs can benefit with some points during field day too. And “REPLY ALL” so everyone within our 3 clubs can see your comments on this topic after everyone has a chance to discuss this topic in your respective club meetings. I am looking forward in finding out how many people are interested in the National Traffic System. And how we all can participate in it. DE KB?DCO Thomas Gagnon Cell: 320-552-0859 P.O. Box 4 Stewart, MN 55385

Hello, Ben!! I enjoyed chatting with you the other evening! I am grateful for your willingness to help with digital radio questions. Did you mention that there are some HAMS in Redwood, or Wabasso, that could assist me with a system for our hospital?? I am stuck behind a tech curve due to my age and never being in the VHF and repeater realm. Thank you for your interest!! With regards, Richard Klingler KF0LKG

What I find interesting - TARPN seems to have figured out how to implement forward error correction (FEC) to AX.25 packets. Packet's greatest downfall has always been lack of robustness - one error and the packet is trash. This could change. Another thing is they have figured out how to use mobile radios that claim to support 9600 baud packet (but never did very well) by reducing the speed in half to 4800 baud. I plan to build and test their NinoTNC with a couple of Yaesu FT-2600 2m radios that fall into the above mentioned category. https://tarpn.net/t/packet_radio_networking.html 73 Mike N0QBH

Hello members, The clubs quarterly meeting is coming up on Tuesday, October 24th at 6:30pm. The meeting will be held at the Kandiyohi County Rescue Squad building. The address is 213 Lakeland Dr NE Willmar, Mn 56201

Thank you, kindly!! i would certainly like to join your club. Richard Klingler KF0LKG

This link is chock full of info about ham radio TNC modems. https://tarpn.net/t/faq/faq_tnc.html 73 Mike N0QBH

In the first installment I discussed getting set up for packet reception. In this article I'll describe the transmitting side of packet radio. Most packet operators use their base station 2 meter mobile FM transceiver as the radio. Many of these newer radios have built in data connections, which makes things much easier. Else you take over the mic connection. Unless you are handy with fine, unforgiving soldering, buying custom cables from a reputable source can save a lot of aggravation. If you insist on attempting to solder your own, number #1 tip is to plug the connector you are soldering on, to a mating connector. This will keep the pins straight when the plastic gets soft. Tip #2 small amounts of liquid flux are your friends - particularly when tinning wires and also when making connections. Alcohol cleans up. The next question is what kind of TNC modem am I going to use? There are two paths here, hardware or software. Hardware would be a 1200 baud TNC with radio Tx, Rx and PTT, along with DC power and the serial data connection. Since most newer computers do not have async serial ports, you will need a Keyspan serial to USB interface. Don't forget the serial cables and possibly adapters. While most use computers running a serial terminal program to talk to the TNC, I've seen the truly nerdy use RS232 to Bluetooth adapters and communicate via tablet or fone. Software TNC setups use a radio to computer interface. Besides RF isolating and handling the transmit and receive audio, they usually incorporate a VOX type PTT to key the radio when there's data to send. I personally use and recommend the Signalink USB external soundcard modem. Others prefer the Rig Runner, altho I am not familiar with it. The most important thing to remember is you are going to be transmitting and like good Hams, we care about our signal. Besides frequency, there are two things under your control, power and deviation (loudness). Power is simple. Don't use more than you need to get the job done. Accessing a local node using your outdoor antenna will likely work fine at 5 Watts. Save the 50 Watts for when you need it. This would be a good place to point out many packet stations with a nearby node use Hand Held radios with an external antenna. Trying to use the rubber duck antenna often leads to all sorts of weird RFI issues. The packet transmit deviation adjustment is best with a radio service monitor, altho, the "by ear method" seems to work well in most cases for us mere mortals. Like I said earlier, deviation is how loudly the audio data signal is driving the transmitter can be either adjusted internally on most TNCs or on the front panel of the Signalink USB adapter. The "by ear method" requires a second radio to listen to your transmitted signal while you adjust the volume. The TNCs all have a CALibrate command to key the transmitter with alternating 1200 and 2200 Hz tones. Software TNCs usually require the packet program provide a calibrate function. In either case, choose an unused simplex frequency or, better yet, use a dummy load to transmit into while you are adjusting. The idea is to turn up the deviation adjustment to the transmitter until the signal heard at the receiver doesn't get any louder (without distorting), then lower it until the signal is just noticeably quieter. The way this works is most radios will limit deviation at about 4.5 kHz and your goal is 3 kHz. Once you are set, it's time to try it out with the KB0MNU packet node. It's on 145.670 MHz simplex and responds to it's alias WILMAR. (Note the spelling - we're limited to 6 chars). When you are connected, type help or ? to get a cheat sheet on using the node. I'm including this link to an old, but very comprehensive packet radio primer. It's broken down in to sections, most of the networking stuff is not necessary and apt to be confusing. https://choisser.com/packet/ 73 Mike N0QBH

A Cheapskate's Approach to Packet Radio (Part 1 receiving) Packet radio Terminal Node Controllers (TNCs) are packet radio modems capable of communicating with each other over the air using the AX.25 protocols running at 300, 1200 or 9600 baud. The radio side has connections for transmit and receive audio as well as the PTT (press to talk). The TNC also has a 12 volt power input and an async serial data connection allowing it to communicate with a computer (and human). When operating packet with VHF radios, most use 1200 baud because it works well with voice radios and is a relatively forgiving data mode. Since packet radio is an old digital mode, it's hardware is often found at hamfest flea markets. Some common brands were Kantronics, MFJ, Pacomm and AEA. Because the TNC's are often 30 years old, they sometimes need some TLC to use them again. My point here is your mileage may vary. Another option that can work well is a virtual software TNC running on your computer. This method uses the computer's sound card to listen for and emit the 1200 baud modem audio (packet racket the old timers called it). While there are likely options for every computer type, I'll discuss a popular Windows program suite. A Ukrainian Ham named Andre UZ7HO has created and maintained a popular packet radio program who's latest version is called soundmodem114. He also has a terminal program called easyterm49 that operates seamlessly with soundmodem running. The terminal program provides the user a TNC like interface that is functional and uncluttered while soundmodem is like the packet "engine under the hood". Installing: Andre's packet radio TNC webpage: http://uz7.ho.ua/packetradio.htm The 3 files needed: soundmodem114.zip easyterm49.zip user_guide114_EN.zip I created a sub directory named /packet which holds the unzipped programs. Unzip the downloaded files to your new directory. Make desktop shortcuts for the programs. The user_guide114_EN.zip is a very handy .pdf document. Receiving packets: The following assumes your computer soundcard's MIC input is connected to a 2 meter FM radio's audio out. This usually takes a 1/8" stereo connector patch or jumper cord. Set the frequency to a packet channel like 145.670 (local node WILMAR) or 144.390 APRS. You'll want some activity to see things work. First start the soundmodem114 program. Then start the easyterm49 program. The unplugged volume should be adjusted low audible with squelch open. When the program is running and it's hearing the radio's open squelch, the effects should be visible on the waterfall display. An outdoor antenna will likely yield much more packet activity than one indoors, which will likely only hear the local node WILMAR. When a packet is decoded you will see it a a lot of info on the soundmodem screen, while the easyterm screen is much more like what you would see with a real TNC. Once you get it working, one of the fun things to do is listen in on the International Space Station (ISS) when they pass overhead several times a day on 145.825 MHz. You might even hear me use them as a APRS digipeater, sending the world my location. 73 Mike N0QBH

Good Afternoon, I just realized that I won't be able to run the Sunday evening net for the next 2 weeks, Sept. 24 & Oct. 1. I am looking for a volunteer or two. The script for the was posted here a couple of weeks ago. Please respond to this message if you're able to take one or both Sundays. Tony