Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
Hello Jim!
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
For English, of course.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
V and S are also used for band designators, so it might get confusing for an S class user on U/V, or a V class user on S2/C...
Could us M for text Messaging...
A, B, C, D might be easier after all!
Lyle
Lyle's right, class S and V will be far too confusing - I've had trouble getting my head around Class 2 for example, class V would be worse.
How about :-
Class ND (Narrowband Digital) instead of class 2/V
and also Class HD (High speed Digital) instead of Class 3/H
These letters give a useful descriptor and don't clash with the band names. They also don't have the air of superiority (or inferiority!) compared to straight 0123/ABCD sequences.
You could have Class M or Class T (Text) for the old class 0.
Class A is logical, I know you really meant Analogue....
regards
Grant G8UBN
Hello Jim!
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
For English, of course.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
V and S are also used for band designators, so it might get confusing for an S class user on U/V, or a V class user on S2/C...
Could us M for text Messaging...
A, B, C, D might be easier after all!
Lyle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
The H had been designated for AO-40 for the H service on that satellite. H service was "high frequency" (15m and 10m) operation. Lyle notes also that V and S have prior references, as would B.
It is a difficult mine field.
Dick Jansson --------------------------- mailto:rjansson@cfl.rr.com rjansson@cfl.rr.com --------------------------- -----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Jim Sanford Sent: Sunday, 08 October, 2006 1753 To: 'AMSAT Eagle' Subject: [eagle] Service class names
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
MessageDick:
Yes, there may be some confusion, but in the case of AO-40 et all. it "Mode" H, not "Class" H.
Still, it would be worthwhile to think about a little further.
Sorry you couldn't make the AMSAT meeting. It went well.
73,
Bill ----- Original Message ----- From: Dick Jansson-rr To: 'Jim Sanford' ; 'AMSAT Eagle' Sent: Sunday, October 08, 2006 2:16 PM Subject: [eagle] Re: Service class names
The H had been designated for AO-40 for the H service on that satellite. H service was "high frequency" (15m and 10m) operation. Lyle notes also that V and S have prior references, as would B.
It is a difficult mine field.
Dick Jansson --------------------------- rjansson@cfl.rr.com --------------------------- -----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Jim Sanford Sent: Sunday, 08 October, 2006 1753 To: 'AMSAT Eagle' Subject: [eagle] Service class names
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
------------------------------------------------------------------------------
_______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Jim:
Right on. I had suggested A, B, C, etc. But your approach is better.
Just got home.
Nice seeing you and everyone.
73,
Bill, W3XO ----- Original Message ----- From: Jim Sanford To: 'AMSAT Eagle' Sent: Sunday, October 08, 2006 12:52 PM Subject: [eagle] Service class names
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
------------------------------------------------------------------------------
_______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
On Sun, Oct 08, 2006 at 01:52:39PM -0400, Jim Sanford wrote:
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
I recommend A, B, C, D, or alpha, beta, delta, gamma
I think that assuming that all "Class 1" users are digital voice users is a mistake. Also, S, V, and H are overloaded with frequency band meanings.
Why not a simple naming system like???:
1. SMS Mode (for Class 1) 2. Digital Voice (for Class 2) 3. Wideband (for Class 3)
Just my $0.02
73, Ken Ernandes, N2WWD
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Eric Blossom Sent: Monday, October 09, 2006 2:04 PM To: Jim Sanford Cc: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
On Sun, Oct 08, 2006 at 01:52:39PM -0400, Jim Sanford wrote:
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
I recommend A, B, C, D, or alpha, beta, delta, gamma
I think that assuming that all "Class 1" users are digital voice users is a mistake. Also, S, V, and H are overloaded with frequency band meanings.
_______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
SC (SatChat), DV (Digital Voice), WB (WideBand)?
TD (Text Data rate), LD (Low Data rate), HD (High Data rate)?
There's bound to be confusion unless you resort to digraphs or more.
73 Frank AB2KT
Ken Ernandes wrote:
Why not a simple naming system like???:
- SMS Mode (for Class 1)
- Digital Voice (for Class 2)
- Wideband (for Class 3)
Just my $0.02
73, Ken Ernandes, N2WWD
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Eric Blossom Sent: Monday, October 09, 2006 2:04 PM To: Jim Sanford Cc: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
On Sun, Oct 08, 2006 at 01:52:39PM -0400, Jim Sanford wrote:
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
I recommend A, B, C, D, or alpha, beta, delta, gamma
I think that assuming that all "Class 1" users are digital voice users is a mistake. Also, S, V, and H are overloaded with frequency band meanings.
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
HDSC -- high data-rate (or high definition) satellite comminication sounds like a good name for services offered by the ACP.
73,
John KD6OZH
----- Original Message ----- From: "Frank Brickle" brickle@pobox.com To: "Ken Ernandes" kene@braxtontech.com Cc: "'AMSAT Eagle'" Eagle@amsat.org Sent: Monday, October 09, 2006 18:47 UTC Subject: [eagle] Re: Service class names
SC (SatChat), DV (Digital Voice), WB (WideBand)?
TD (Text Data rate), LD (Low Data rate), HD (High Data rate)?
There's bound to be confusion unless you resort to digraphs or more.
73 Frank AB2KT
Ken Ernandes wrote:
Why not a simple naming system like???:
- SMS Mode (for Class 1)
- Digital Voice (for Class 2)
- Wideband (for Class 3)
Just my $0.02
73, Ken Ernandes, N2WWD
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Eric Blossom Sent: Monday, October 09, 2006 2:04 PM To: Jim Sanford Cc: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
On Sun, Oct 08, 2006 at 01:52:39PM -0400, Jim Sanford wrote:
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
I recommend A, B, C, D, or alpha, beta, delta, gamma
I think that assuming that all "Class 1" users are digital voice users is a mistake. Also, S, V, and H are overloaded with frequency band meanings.
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt
On Mon, 2006-10-09 at 11:51 -0700, Matt Ettus wrote:
By not having an ordering, nobody gets slighted, and there is less confusion.
I like this idea.
Bdale
I like it because it's clear (less cryptic) of what's offered and there's no implication of a hierarchy (i.e., "class" or numbering could be interpreted as there being more or less importance given to one type of service).
73, Ken N2WWD
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Matt Ettus Sent: Monday, October 09, 2006 2:51 PM To: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
I think that Matt has hit the nail on the head. This a simple extension of an existing nomenclature system. We worked hard to establish this system for AO-40. It isn't broken, don't fix it - use it!
Dick Jansson --------------------------- rjansson@cfl.rr.com ---------------------------
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Matt Ettus Sent: Monday, 09 October, 2006 1851 To: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
I hope that the U/V digital service is 8-bit transparent so that it can be used efficiently for non-text communication, like APRS and collecting weather data with the fewest number of bits. It's also not a store-and-forward system so it really isn't messaging - although that could be added if message size was restricted. The number of data rates implemented in the ACP or SDX could be increased, so attaching names to each data rate may be a problem. How about calling class 1 advanced low-speed satellite communication (ALSC) and class 2 and 3 advanced high-speed satellite communication (AHSC)? There could then be a suffix for each data rate, such as AHSC-4800 and AHSC-256K.
73,
John KD6OZH
----- Original Message ----- From: "Dick Jansson-rr" rjansson@cfl.rr.com To: "'Matt Ettus'" matt@ettus.com; "'AMSAT Eagle'" Eagle@amsat.org Sent: Monday, October 09, 2006 21:35 UTC Subject: [eagle] Re: Service class names
I think that Matt has hit the nail on the head. This a simple extension of an existing nomenclature system. We worked hard to establish this system for AO-40. It isn't broken, don't fix it - use it!
Dick Jansson
rjansson@cfl.rr.com
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Matt Ettus Sent: Monday, 09 October, 2006 1851 To: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
John B. Stephensen wrote:
I hope that the U/V digital service is 8-bit transparent so that it can be used efficiently for non-text communication, like APRS and collecting weather data with the fewest number of bits. It's also not a store-and-forward system so it really isn't messaging - although that could
To keep the system stateless on the spacecraft since we do not want to add a coprocessor, increase the internal communications complexity etc. Frank proposes and I support him since I believe it is right that we will use jabber servers on the ground to hold the data AND do store/forward. I do not want to build a messaging file system,. etc. on the spacecraft. Cooperation servers on the ground, using the net to move data between them, seems to be the right way to go.
We particularly like the ejabber server. It is implemented in Erlang/OTP.
The conference went well. I am taking a couple of days off from AMSAT and spending them with Shann, N2HPE, touring. I will be home Wednesday.
Bob
be added if message size was restricted. The number of data rates implemented in the ACP or SDX could be increased, so attaching names to each data rate may be a problem. How about calling class 1 advanced low-speed satellite communication (ALSC) and class 2 and 3 advanced high-speed satellite communication (AHSC)? There could then be a suffix for each data rate, such as AHSC-4800 and AHSC-256K.
73,
John KD6OZH
One of the big advantages of XMPP (Jabber) as the underlying protocol is a rich set of services that depend only on the terrestrial servers for their implementation. And it's all there already, servers and clients both.
If somebody wanted to do it, an AX25 - XMPP gateway would be pretty simple to construct, purely as an adjunct to a terrestrial server implementation.
Similarly, if there were a need, it would be trivial to encapsulate APRS messages in XMPP. Not the other way around, however.
73 Frank AB2KT
Robert McGwier wrote:
John B. Stephensen wrote:
I hope that the U/V digital service is 8-bit transparent so that it can be used efficiently for non-text communication, like APRS and collecting weather data with the fewest number of bits. It's also not a store-and-forward system so it really isn't messaging - although that could
To keep the system stateless on the spacecraft since we do not want to add a coprocessor, increase the internal communications complexity etc. Frank proposes and I support him since I believe it is right that we will use jabber servers on the ground to hold the data AND do store/forward. I do not want to build a messaging file system,. etc. on the spacecraft. Cooperation servers on the ground, using the net to move data between them, seems to be the right way to go.
We particularly like the ejabber server. It is implemented in Erlang/OTP.
The conference went well. I am taking a couple of days off from AMSAT and spending them with Shann, N2HPE, touring. I will be home Wednesday.
Bob
be added if message size was restricted. The number of data rates implemented in the ACP or SDX could be increased, so attaching names to each data rate may be a problem. How about calling class 1 advanced low-speed satellite communication (ALSC) and class 2 and 3 advanced high-speed satellite communication (AHSC)? There could then be a suffix for each data rate, such as AHSC-4800 and AHSC-256K.
73,
John KD6OZH
I agree that a store and forward server isn't needed in the satellite. The satellite only needs to multiplex byte streams received on the uplinks onto a common downlink.
73,
John KD6OZH
----- Original Message ----- From: "Robert McGwier" rwmcgwier@comcast.net To: "John B. Stephensen" kd6ozh@comcast.net Cc: "Dick Jansson-rr" rjansson@cfl.rr.com; "'Matt Ettus'" matt@ettus.com; "'AMSAT Eagle'" Eagle@amsat.org Sent: Tuesday, October 10, 2006 02:58 UTC Subject: Re: [eagle] Re: Service class names
John B. Stephensen wrote:
I hope that the U/V digital service is 8-bit transparent so that it can be used efficiently for non-text communication, like APRS and collecting weather data with the fewest number of bits. It's also not a store-and-forward system so it really isn't messaging - although that could
To keep the system stateless on the spacecraft since we do not want to add a coprocessor, increase the internal communications complexity etc. Frank proposes and I support him since I believe it is right that we will use jabber servers on the ground to hold the data AND do store/forward. I do not want to build a messaging file system,. etc. on the spacecraft. Cooperation servers on the ground, using the net to move data between them, seems to be the right way to go.
We particularly like the ejabber server. It is implemented in Erlang/OTP.
The conference went well. I am taking a couple of days off from AMSAT and spending them with Shann, N2HPE, touring. I will be home Wednesday.
Bob
be added if message size was restricted. The number of data rates implemented in the ACP or SDX could be increased, so attaching names to each data rate may be a problem. How about calling class 1 advanced low-speed satellite communication (ALSC) and class 2 and 3 advanced high-speed satellite communication (AHSC)? There could then be a suffix for each data rate, such as AHSC-4800 and AHSC-256K.
73,
John KD6OZH
-- AMSAT Director and VP Engineering. Member: ARRL, AMSAT-DL, TAPR, Packrats, NJQRP, QRP ARCI, QCWA, FRC. ARRL SDR WG Chair "You see, wire telegraph is a kind of a very, very long cat. You pull his tail in New York and his head is meowing in Los Angeles. Do you understand this? And radio operates exactly the same way: you send signals here, they receive them there. The only difference is that there is no cat." - Einstein
For what it's worth, I like Matt's names. They are simple and elegant. You don't have to look them up in a book to understand them.
On Oct 9, 2006, at 11:51 AM, Matt Ettus wrote:
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
They are good names, and I think they should be adopted as the official designators. Unfortunately the average length is 11.8 characters so you can bet they will be abbreviated. It might not be a bad idea to nail down the shorthand names as well. (The obvious contractions (UVL, LSL, TXM, LRA, HRA) don't ring clearly to my ear.)
73 Frank AB2KT
Louis McFadin wrote:
For what it's worth, I like Matt's names. They are simple and elegant. You don't have to look them up in a book to understand them.
On Oct 9, 2006, at 11:51 AM, Matt Ettus wrote:
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
The linear mode shorthand can just remain U/V and L/S although many users probably still say mode B or mode S. If we start with 3-letter abbreviations that are easy to remember, LSL and HSL for low-speed and high-speed satellite link might work.
73,
John KD6OZH
----- Original Message ----- From: "Frank Brickle" brickle@pobox.com To: "Louis McFadin" w5did@amsat.org Cc: "'AMSAT Eagle'" Eagle@amsat.org Sent: Tuesday, October 10, 2006 03:24 UTC Subject: [eagle] Re: Service class names
They are good names, and I think they should be adopted as the official designators. Unfortunately the average length is 11.8 characters so you can bet they will be abbreviated. It might not be a bad idea to nail down the shorthand names as well. (The obvious contractions (UVL, LSL, TXM, LRA, HRA) don't ring clearly to my ear.)
73 Frank AB2KT
Louis McFadin wrote:
For what it's worth, I like Matt's names. They are simple and elegant. You don't have to look them up in a book to understand them.
On Oct 9, 2006, at 11:51 AM, Matt Ettus wrote:
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
I think the users can and will determine the abbreviations. We have given them some names they can use and understand. Let them do the rest.
On Oct 9, 2006, at 9:08 PM, John B. Stephensen wrote:
The linear mode shorthand can just remain U/V and L/S although many users probably still say mode B or mode S. If we start with 3- letter abbreviations that are easy to remember, LSL and HSL for low- speed and high-speed satellite link might work.
73,
John KD6OZH
----- Original Message ----- From: "Frank Brickle" brickle@pobox.com To: "Louis McFadin" w5did@amsat.org Cc: "'AMSAT Eagle'" Eagle@amsat.org Sent: Tuesday, October 10, 2006 03:24 UTC Subject: [eagle] Re: Service class names
They are good names, and I think they should be adopted as the official designators. Unfortunately the average length is 11.8 characters so you can bet they will be abbreviated. It might not be a bad idea to nail down the shorthand names as well. (The obvious contractions (UVL, LSL, TXM, LRA, HRA) don't ring clearly to my ear.)
73 Frank AB2KT
Louis McFadin wrote:
For what it's worth, I like Matt's names. They are simple and elegant. You don't have to look them up in a book to understand them.
On Oct 9, 2006, at 11:51 AM, Matt Ettus wrote:
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
On Tue, Oct 10, 2006 at 04:08:44AM -0000, John B. Stephensen wrote:
The linear mode shorthand can just remain U/V and L/S although many users probably still say mode B or mode S. If we start with 3-letter abbreviations that are easy to remember, LSL and HSL for low-speed and high-speed satellite link might work.
73,
John KD6OZH
The danger with "low" and "high" is we may end up with the mess that USB has: low, high, full with no obvious ordering between "high" and "full".
That said, I'm not attached. I like Matt's idea.
Eric
I second that motion.
Louis McFadin wrote:
For what it's worth, I like Matt's names. They are simple and elegant. You don't have to look them up in a book to understand them.
On Oct 9, 2006, at 11:51 AM, Matt Ettus wrote:
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________
Been think about this more. How about dumping the word "class" altogether.
Why not use "level" instead?.
Furthermore, I have come to agree with those who say that terms like "H" are ingrained in the mind of users as band designations.
So, I suggest Level A would be what was called Class 0, Level B as what was called Class 1 etc.
This is MY final word on the subject but, obviously, I don't have the final word.
73,
Bill ----- Original Message ----- From: "Eric Blossom" eb@comsec.com To: "Jim Sanford" wb4gcs@amsat.org Cc: "'AMSAT Eagle'" Eagle@amsat.org Sent: Monday, October 09, 2006 1:03 PM Subject: [eagle] Re: Service class names
On Sun, Oct 08, 2006 at 01:52:39PM -0400, Jim Sanford wrote:
Team: I learned at Symposium that some don't like some of the class names we've been using to discuss various services.
I reaffirmed at Symposium that we need consistent names for the services we'll provide, just like we've settled on band names.
To give us the precise nomenclature I think we need for effective communication, I propose:
Class A for what we used to call Class 0 (A from the old "Analog", which we need to stamp out.) Class S for what we used to call Class 1 (S from SMS) Class V for what we used to call Class 2 (small station digital Voice) Class H for what we used to call Class 3 (High rate)
I started with A, B, . . . and decided to propose more intuitive names.
Unless one of you strongly objects in the next few hours, I'll have the ANS announcement and AMSAT web page updated.
It was great to see many of you this weekend.
Thanks & 73, Jim wb4gcs@amsat.org
I recommend A, B, C, D, or alpha, beta, delta, gamma
I think that assuming that all "Class 1" users are digital voice users is a mistake. Also, S, V, and H are overloaded with frequency band meanings.
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
participants (13)
-
Bdale Garbee -
Bill Tynan -
Dick Jansson-rr -
Eric Blossom -
Frank Brickle -
Grant Hodgson -
Jim Sanford -
John B. Stephensen -
Ken Ernandes -
Louis McFadin -
Lyle Johnson -
Matt Ettus -
Robert McGwier