
Team: A few days ago, I made a proposal for naming Eagle's communications services and solicited comments. I received many good comments.
I really think it important that we have unambiguous service class names. Based on all the comments, I propose: U/V "linear" L/S "linear" Text messaging Low Rate ACP High Rate ACP
While I'd prever something less ambiguous than "linear", our customers seem to understand that "linear" means SSB/CW/PSK31/SSTv . . . . etx.
Any strong objections to this?
If not, I'll get the announcement on AMSAT.org changed. It's time to get precise.
Thanks & 73, Jim [email protected]

I really think it important that we have unambiguous service class names. Based on all the comments, I propose: U/V "linear" L/S "linear" Text messaging Low Rate ACP High Rate ACP
While I'd prever something less ambiguous than "linear", our customers seem to understand that "linear" means SSB/CW/PSK31/SSTv . . . . etx.
Any strong objections to this?
Works for me, Jim.
Not to muddy the waters, but am I correct that the SDX units will have two Rx inputs and two Tx outputs, and that we will as a result also have available U/S "linear" and L/V "linear" modes.
-Lyle
participants (2)
-
Jim Sanford
-
Lyle Johnson