Thanks to Mac, KE5QDA, I have had to reconsider the Digital Dilemma! He asked if I considered Winlink2K to be a digital mode. WELL, I had not even considered that question and I had to do some research on the topic. What I found out (after some soul searching) caused me to re-do my original Digital Dilemma post ... here's my thinking...
From the Winlink2K website:
"Winlink 2000 (WL2K) is a worldwide system of volunteer resources supporting e-mail by radio, with non-commercial links to internet e-mail. "
After reading this, I view WL2K as a pipeline rather than a digital mode of communication.
And I am sure there is LOTS of room for argument and discussion. Feel free to discuss because there's plenty of room for other opinions.
Any way, if this is my feeling on WL2K, then what about PSKMail? I reviewed the features list and came to the same conclusion. PSKMail is also PRIMARILY a pipeline to support email. It has some other features that kind of cloud the picture (mainly texting via APRS) but the main function is pipeline rather than allowing station to station communication.
There is WAY MORE information at each of these websites. WL2K is the "official" choice of just about everyone who is any kind of official.
Consider the following a VERY BRIEF introducton to these two programs ....
WinLink 2000 - Provides Email - WL2K Website
1. Windows (obviously)
2. Uses PACTOR 1,2, and 3 and requires pactor modem which is pricey.
3. Some proprietary features? ("The Winlink 2000 system, and Winlink user software is built, maintained and supported by the Winlink Development Team (WDT), your membership in the Amateur Radio Safety Foundation, and your tax deductible contributions.")
4. Recently introduced a sound card mode called WINMOR
5. APRS text messaging is possible as well as some packet usage for "last mile" coverage.
6. Lots of email servers world-wide. If you happen onto one of these frequencies, you'll probably have to move your QSO.
PSKMail - Provides Email - PSKMail Website
1. Linux BUT available in Windows emulator (puppy_linux)
2. Uses Fldigi
3. Modes - PSK250 with ARQ
4. GUI easy to use and provides email, APRS and Chat mode.
5. Upload/download email from internet and works with Linux email program called EVOLUTION.
6. While most email servers are in Europe, there appears to be a couple of email servers in the U.S. (one in San Antonio.)
... AR
Showing posts with label ARES. Show all posts
Showing posts with label ARES. Show all posts
Saturday, August 15, 2009
Wednesday, July 01, 2009
Email is Essential to Deliver NTS Messages
Delivery of National Traffic System messages is difficult in today's world. The low participation of amateurs in traffic handling makes the sending of messages, and, especially the delivery of messages, very spotty. The problem is, in a word - COVERAGE.
Looking at Oklahoma, we have hams in every community. Few, if any, of these hams are interested in handling the NTS traffic. This means the few hams who do enjoy passing and delivering message have to cover much more of the state.
This makes email essential to provide the COVERAGE that is needed.
I can make every net that is available within the state and still not find anyone willing to take and deliver a message to an amateur in a given town. Given the choice between a long distance call and an email, I think the choice is obvious.
Unless we can develop more interest in NTS message-handling and attract amateurs to support the NTS network, we will have to rely more on email to deliver our messages.
So what should be the guidelines for email delivery? An op-ed piece in QST recommended message delivery by email once the message was received by an amateur in the same ARRL Section as the recipient.
This seems like a good recommendation since our coverage is lacking at this level.
And why bother? It is the NETWORK and the TRAINING that are important! The network of the NTS message nets has been long established for efficiency in communication. It is important to keep these nets functional in case the need arises on a local or even a national level. Maybe there is something better, but until we develop it to the point we can depend on it, let's keeep the traffic nets operational.
The TRAINING is important as well. Learning the net procedures facilitates good habits. Practice in sending and receiving of formatted text helps develop accuracy and operator confidence.
But until message handling becomes all the rage within our ranks and people are fighting over sending and receiving messages, we will need to supplement our coverage with email.
... AR
Looking at Oklahoma, we have hams in every community. Few, if any, of these hams are interested in handling the NTS traffic. This means the few hams who do enjoy passing and delivering message have to cover much more of the state.
This makes email essential to provide the COVERAGE that is needed.
I can make every net that is available within the state and still not find anyone willing to take and deliver a message to an amateur in a given town. Given the choice between a long distance call and an email, I think the choice is obvious.
Unless we can develop more interest in NTS message-handling and attract amateurs to support the NTS network, we will have to rely more on email to deliver our messages.
So what should be the guidelines for email delivery? An op-ed piece in QST recommended message delivery by email once the message was received by an amateur in the same ARRL Section as the recipient.
This seems like a good recommendation since our coverage is lacking at this level.
And why bother? It is the NETWORK and the TRAINING that are important! The network of the NTS message nets has been long established for efficiency in communication. It is important to keep these nets functional in case the need arises on a local or even a national level. Maybe there is something better, but until we develop it to the point we can depend on it, let's keeep the traffic nets operational.
The TRAINING is important as well. Learning the net procedures facilitates good habits. Practice in sending and receiving of formatted text helps develop accuracy and operator confidence.
But until message handling becomes all the rage within our ranks and people are fighting over sending and receiving messages, we will need to supplement our coverage with email.
... AR
Labels:
ARES,
ARRL,
emergency,
membership,
National Traffic System,
NTS
Monday, June 29, 2009
NTS Rule Number One: Deliver The Message!
If I have received a National Traffic System message from any source (usually an NTS net) then I am obligated to deliver that message to the recipient by whatever means at my disposal. This seems to me to be the "Golden Rule" of handling NTS traffic.
Recently, I had a Field Day message to be delivered to my Section Manager. I tried to send the message on three different nets but, due to band conditions, I was not successful. As a last resort, I sent the message by email.
Wow, did I get slammed! One of the more experienced message-handlers listening on the net complained to the Section Manager that I was cheating! Evidently, he was listening to my attempt to send the message but made no effort to help with a relay. He did complain strenuously enough that I was asked to send the message via another net when possible.
Fortunately, conditions were better the day after Field Day and I was able to successfully send the message to the Section Manager. So, there was no harm done other than to my reputation and my ego.
Needless to say, I gave this some thought and went back and forth over some of the issues. Does it really matter HOW I deliver an NTS message? The "purist" might say that it does matter, but let's talk about this a little bit.
Delivery Methods:
The accepted practice is to PHONE the recipient via the phone number included in the message and read the message text (translating the ARRL Codes if needed).
If the received message has a bad phone number, then what do I do?
If the recipient is not a ham, then I research the phone number in the phone book (or online) to see if there is a new number listed. Then I call and deliver the message after making sure I'm talking to the intended recipient. If there is no phone number, I return the message as undeliverable (ARL FORTY SEVEN).
If the recipient is a ham and there is no new listing in the phone book, I look the recipient up on QRZ to verify the street address and see if there is an email listed. If there is, then I email the recipient the message; if not, then I return the message as not deliverable.
And, at times, I have even MAILed a message via postcard to the recipient's address on the message.
But I get the message delivered to the best of my ability!
Just so you'll know (especially if you're a Monday Morning Quarterback}, I'll use email delivery when I have to.
PS - Get off the sidelines and into the game - its FUN!
...AR
Recently, I had a Field Day message to be delivered to my Section Manager. I tried to send the message on three different nets but, due to band conditions, I was not successful. As a last resort, I sent the message by email.
Wow, did I get slammed! One of the more experienced message-handlers listening on the net complained to the Section Manager that I was cheating! Evidently, he was listening to my attempt to send the message but made no effort to help with a relay. He did complain strenuously enough that I was asked to send the message via another net when possible.
Fortunately, conditions were better the day after Field Day and I was able to successfully send the message to the Section Manager. So, there was no harm done other than to my reputation and my ego.
Needless to say, I gave this some thought and went back and forth over some of the issues. Does it really matter HOW I deliver an NTS message? The "purist" might say that it does matter, but let's talk about this a little bit.
Delivery Methods:
The accepted practice is to PHONE the recipient via the phone number included in the message and read the message text (translating the ARRL Codes if needed).
If the received message has a bad phone number, then what do I do?
If the recipient is not a ham, then I research the phone number in the phone book (or online) to see if there is a new number listed. Then I call and deliver the message after making sure I'm talking to the intended recipient. If there is no phone number, I return the message as undeliverable (ARL FORTY SEVEN).
If the recipient is a ham and there is no new listing in the phone book, I look the recipient up on QRZ to verify the street address and see if there is an email listed. If there is, then I email the recipient the message; if not, then I return the message as not deliverable.
And, at times, I have even MAILed a message via postcard to the recipient's address on the message.
But I get the message delivered to the best of my ability!
Just so you'll know (especially if you're a Monday Morning Quarterback}, I'll use email delivery when I have to.
PS - Get off the sidelines and into the game - its FUN!
...AR
Labels:
ARES,
ARRL,
National Traffic System,
nets,
NTS,
QRZ,
traffic handling
Sunday, May 31, 2009
IRLP and WX4NHC
The National Hurricane Center conducted a communications test on Saturday, May 30. Their primary frequency was 14.325. Stations were instructed to check in and give their local weather. I imagine they had tons of check-ins.
They also were taking check-ins on IRLP Node 9219. I linked in to the NHC net using Kevin's (KD5RHF) repeater (Node 3487) on 146.535 simplex. This was about 2 pm Saturday afternoon.
The net control was DU2EX in Germany. When he called for check-ins, I answered with my call sign and he acknowledged me. I was not familiar with the process and gave my wx report too soon. DU2EX then accepted and acknowledged other check-ins.
At the end of the check-in list, he passed control to WX4NHC at the Hurricane Center. The station accepting WX reports then called me for my report. I gave my location and the temperature. He asked for my name and I responded that information. Then he thanked me and went on to the next station.
Very interesting support for the NHC when the next hurricane heads to the U.S.
I just want to thank Kevin (KD5RHF) for making this mode of communication available ... AR
They also were taking check-ins on IRLP Node 9219. I linked in to the NHC net using Kevin's (KD5RHF) repeater (Node 3487) on 146.535 simplex. This was about 2 pm Saturday afternoon.
The net control was DU2EX in Germany. When he called for check-ins, I answered with my call sign and he acknowledged me. I was not familiar with the process and gave my wx report too soon. DU2EX then accepted and acknowledged other check-ins.
At the end of the check-in list, he passed control to WX4NHC at the Hurricane Center. The station accepting WX reports then called me for my report. I gave my location and the temperature. He asked for my name and I responded that information. Then he thanked me and went on to the next station.
Very interesting support for the NHC when the next hurricane heads to the U.S.
I just want to thank Kevin (KD5RHF) for making this mode of communication available ... AR
Sunday, May 10, 2009
Military Communications Test on May 9, 10
Had a good time trying to work the MARS stations on the air Saturday. I worked two of the Army stations (40M) and one Navy station (80M).
This event is always challenging since the MARS stations are transmitting on their allotted frequencies and listening on the legal Amateur frequencies. You have to listen to the MARS station and find out where they are listening. Then you call them on that frequency. Good practice!
I was not able to copy the message from the Secretary of Defense. This message is sent via RTTY, AMTOR, MT63 by various stations. If you copy it and send it in for verification, then you will receive a letter from the Secretary of Defense. I have qualified the past two years, but not able to copy this year.
Good event for practicing split operation as well as digital modes.
...AR
This event is always challenging since the MARS stations are transmitting on their allotted frequencies and listening on the legal Amateur frequencies. You have to listen to the MARS station and find out where they are listening. Then you call them on that frequency. Good practice!
I was not able to copy the message from the Secretary of Defense. This message is sent via RTTY, AMTOR, MT63 by various stations. If you copy it and send it in for verification, then you will receive a letter from the Secretary of Defense. I have qualified the past two years, but not able to copy this year.
Good event for practicing split operation as well as digital modes.
...AR
Thursday, April 16, 2009
Narrow Band Emergency Messaging System
Also in the April 2008 issue of QST, there was a short mention of the Narrow Band Emergency Messaging System which is based on PSK, RTTY, or MFSK rather than Packet messaging.
NBEMS was developed by Skip Teller, KH6TY, creator of DigiPan and Dave Freese, W1HKJ, creator of the Linux-based Fldigi.
In my estimation, this program suite takes direct aim at the much-touted and expensive Winlink process.
Together, NBEMS package lets you exchange text and small files in several modes using ARQ - Automatic Repeat reQuest. As you may or may not know, ARQ supports checking and resending data to provide error free transmission of data.
Everything is handled through sound card interfaces so no expensive TNC is required.
Fldigi program puts you on the air on RTTY, PSK31, PSK63, PSK125, PSK25 and MFSK. If you want to use the ARQ features, then the Flarq program interfaces with the Fldigi to make it happen.
There is a very active Yahoo Group supporting NBEMS testing on VHF and 30 meters. Good success has been had with communication between VHF FM mobiles even using vertical antennas. This opens up all kinds of possibilities due to the many hams with this equipment.
The programs are available at: w1hkj.com/NBEMS
...AR
NBEMS was developed by Skip Teller, KH6TY, creator of DigiPan and Dave Freese, W1HKJ, creator of the Linux-based Fldigi.
In my estimation, this program suite takes direct aim at the much-touted and expensive Winlink process.
Together, NBEMS package lets you exchange text and small files in several modes using ARQ - Automatic Repeat reQuest. As you may or may not know, ARQ supports checking and resending data to provide error free transmission of data.
Everything is handled through sound card interfaces so no expensive TNC is required.
Fldigi program puts you on the air on RTTY, PSK31, PSK63, PSK125, PSK25 and MFSK. If you want to use the ARQ features, then the Flarq program interfaces with the Fldigi to make it happen.
There is a very active Yahoo Group supporting NBEMS testing on VHF and 30 meters. Good success has been had with communication between VHF FM mobiles even using vertical antennas. This opens up all kinds of possibilities due to the many hams with this equipment.
The programs are available at: w1hkj.com/NBEMS
...AR
Packet Radio for Emergency Messaging - OUTPOST
Outpost creates a screen that resembles an Internet e-mail application. The user doesn't need to be overly familiar with packet radio. You just need to know how to type and click send. Outpost takes care of the rest.
Outpost was covered in the April 2008 issue of QST. It is available at www.outpostpm.org
Outpost was written by Jim Oberhofer, KN6PE. He is a member of the Cupertino, CA ARES group ( www.cupertinoares.org ).
This program provides the following:
This gives a whole different set of programs for using packet radio for emergency messaging.
...AR
Outpost was covered in the April 2008 issue of QST. It is available at www.outpostpm.org
Outpost was written by Jim Oberhofer, KN6PE. He is a member of the Cupertino, CA ARES group ( www.cupertinoares.org ).
This program provides the following:
- Supports all 3 packet message types - Private, NTS, and Bulletins.
- Create messages from imported files, from scratch, or by REPLY or FWD.
- Built-in message form maker. An NTS message form is provided.
- Supports TNCs, AGWPE, and Telnet interfaces.
- Automatic query/posting to BBS based on time.
This gives a whole different set of programs for using packet radio for emergency messaging.
...AR
Monday, April 13, 2009
Packet Radio for Emergency Communications - EcomScs
In the April issue of CQ Magazine there is an article concerning the use of packet radio for Emergency Communications. This is one of several articles I've seen lately on this topic.
These programs are available at the following website:
www.qsl.net/kb2scs
Even though packet use has been relegated mainly to the APRS applications, the use of packet in EmCom is growing.
The EcomScs program can send and receive messages formatted as NTS messages in attachments. The program handles sending and receiving messages when connected to the bulletin board. Keyboard to keyboard communication is supported as well. Any type of file may be sent or received, whether binary or text. It also allows the user to create their own message forms. It will send picture files as attachments. The program does do some optimization of the file.
GateWayScs provides a temporary mailbox to send and receive local packet mail until normal bulletin board services can be set up or restored. It also can be used to provide an internet gateway for packet messages.
The article describes emergency driven uses for both of these programs. This progam pair provides invaluable connectivity during an emergency situation. Well worth more investigation.
...AR
These programs are available at the following website:
www.qsl.net/kb2scs
Even though packet use has been relegated mainly to the APRS applications, the use of packet in EmCom is growing.
The EcomScs program can send and receive messages formatted as NTS messages in attachments. The program handles sending and receiving messages when connected to the bulletin board. Keyboard to keyboard communication is supported as well. Any type of file may be sent or received, whether binary or text. It also allows the user to create their own message forms. It will send picture files as attachments. The program does do some optimization of the file.
GateWayScs provides a temporary mailbox to send and receive local packet mail until normal bulletin board services can be set up or restored. It also can be used to provide an internet gateway for packet messages.
The article describes emergency driven uses for both of these programs. This progam pair provides invaluable connectivity during an emergency situation. Well worth more investigation.
...AR
Subscribe to:
Posts (Atom)
