| |
CX2SA > SATDIG 14.01.10 22:04l 769 Lines 26834 Bytes #999 (0) @ WW
BID : AMSATBB523
Read: GUEST
Subj: AMSAT-BB-digest V5 23
Path: IZ3LSV<IK2XDE<ON4HU<SR1BSZ<F4BWT<F1BBI<CX2SA
Sent: 100114/2003Z @:CX2SA.LAV.URY.SA #:32745 [Minas] FBB7.00e $:AMSATBB523
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Today's Topics:
1. ARISSat-1 Documentation site (George Henry)
2. Re: ARISSat-1 Documentation site (Anthony Monteiro)
3. Re: HO-68 Schedule Jan 10-17 (i8cvs)
4. HO68 2:00 UTC (PY5LF)
5. Re: ARISSat-1 Documentation site (Nigel Gunn G8IFF/W8IFF)
6. Re: ARISSat-1 Documentation site (don)
7. FO-29 schedule Jan, Feb. (Mineo Wakita)
8. OSCAR-11 Report (Clive Wallis)
9. AMSAT adopts Acceptable Use Policy for mailing lists
(Gould Smith)
10. Re: FO-29 schedule Jan, Feb. (David Wing)
11. Re: FO-29 schedule Jan, Feb. (Andrew Glasbrenner)
12. Re: AMSAT adopts Acceptable Use Policy for mailing lists
(Bob McGwier)
13. AO-7 Northern Europe (Bob- W7LRD)
----------------------------------------------------------------------
Message: 1
Date: Wed, 13 Jan 2010 19:03:36 -0600
From: "George Henry" <ka3hsw@xxx.xxx>
Subject: [amsat-bb] ARISSat-1 Documentation site
To: "amsat bb" <amsat-bb@xxxxx.xxx>, <n6ghz@xxxxx.xxx>
Message-ID: <64AF32BD8C41402E9DC55643E280146C@xxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
I tried to visit the ARISSat-1 documentation site mentioned in the Nov/Dec
AMSAT Journal to look at the current schematics, and received a warning that
the site's security certificate was not issued by a trusted source.....
Dare I proceed?
George, KA3HSW
------------------------------
Message: 2
Date: Wed, 13 Jan 2010 20:17:57 -0500
From: Anthony Monteiro <aa2tx@xxxxxxx.xxx>
Subject: [amsat-bb] Re: ARISSat-1 Documentation site
To: "George Henry" <ka3hsw@xxx.xxx>, "amsat bb" <amsat-bb@xxxxx.xxx>,
<n6ghz@xxxxx.xxx>
Message-ID: <201001140118.o0E1I2OI007190@xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Hi George,
Yes, it is safe. You get a warning because
the site's certificate is invalid.
73,
Tony AA2TX
AMSAT VP Engineering
---
At 08:03 PM 1/13/2010, George Henry wrote:
>I tried to visit the ARISSat-1 documentation site mentioned in the Nov/Dec
>AMSAT Journal to look at the current schematics, and received a warning that
>the site's security certificate was not issued by a trusted source.....
>
>Dare I proceed?
>
>
>George, KA3HSW
>
>
>_______________________________________________
>Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
>Not an AMSAT-NA member? Join now to support the amateur satellite program!
>Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 3
Date: Thu, 14 Jan 2010 02:16:37 +0100
From: "i8cvs" <domenico.i8cvs@xxx.xx>
Subject: [amsat-bb] Re: HO-68 Schedule Jan 10-17
To: "Alan Kung" <alankung@xxxxxxx.xxx.xxx.xx>, "AMSAT-BB"
<amsat-bb@xxxxx.xxx>
Message-ID: <009a01ca94b7$39ac4e40$0201a8c0@xxx.xx>
Content-Type: text/plain; charset="iso-8859-1"
----- Original Message -----
From: "Alan Kung" <alankung@xxxxxxx.xxx.xxx.xx>
To: <amsat-bb@xxxxx.xxx>
Sent: Thursday, January 07, 2010 5:45 PM
Subject: [amsat-bb] HO-68 Schedule Jan 10-17
>
> 12 Jan. 2010
> HO-68 Linear Tansponder
> 19:205...Turn On
> South America,NA,North Asia
> 20:05...Turn Off
>
> 73
> Alan Kung, BA1DU
> HO-68(XW-1) Project Manager
> www.camsat.cn
>
Hi Alan, BA1DU
The path: South America,NA,North Asia of the above orbit 12 Jan 2010
of HO-68 linear transponder is wrong because the satellite covers instead
Africa and Europe.
This is why a lot of users following your schedule missed a very interesting
orbit with very high elevation over Europe.
I suggest you to remove the path of the satellite over the continents and
live only the time and the mode of operation as follows:
12 Jan. 2010
Linear Tansponder
19:20...Turn On
20:05...Turn Off
Doing this way every one will be obliged to check every orbit and see
if it covers it's foot print or not.
In addition I suggest to schedule HO-68 one week only FM and Digital
Transponder and one week only Linear Transponder.
This will simplify the job for you and for all satellite users giving to
everyone the maximum capability to work every possible orbit in the
preferred mode.
In the mean time and for the future I will not take any more in account
the path of HO-68 that you states over the continents because it is already
two time that I found it to be in mistake.
The last time the following orbit was also in mistake because I found that
it was not covering Europe.
07 Jan. 2010
HO-68 Linear Tansponder
21:45...Turn On
South Africa,Europe,Middle East Asia,NA,North
Pole,North Asia
22:30...Turn Off
Tank you for your cooperation.
73" de
i8CVS Domenico
------------------------------
Message: 4
Date: Thu, 14 Jan 2010 00:31:16 -0200
From: "PY5LF" <py5lf@xxxxxxxxxxxxx.xxx.xx>
Subject: [amsat-bb] HO68 2:00 UTC
To: "Alan Kung" <alankung@xxxxxxx.xxx.xxx.xx>
Cc: amsat-bb@xxxxx.xxx
Message-ID: <000e01ca94c1$a70a0090$f51e01b0$@xxx.xx>
Content-Type: text/plain; charset="us-ascii"
Ni hao Alan
You had posted this schedule for HO68 ;
14 Jan. 2010
HO-68 Linear Tansponder
02:00...Turn On
South America,NA,North Pole,North Asia
02:40...Turn Off
But I think there are type error and instead 14 JAN , must be 15 JAN. I just
tried to heard the sat but I had heard only telemetry.
I'm right or not ?
73
PY5LF
LUCIANO FABRICIO
CURITIBA-PR-BRAZIL
GG54JM
<http://www.qrz.com/db/py5lf> http://www.qrz.com/db/py5lf
<http://www.falautomation.com.br/> www.falautomation.com.br
------------------------------
Message: 5
Date: Thu, 14 Jan 2010 03:47:02 +0000
From: Nigel Gunn G8IFF/W8IFF <nigel@xxxxx.xxx>
Subject: [amsat-bb] Re: ARISSat-1 Documentation site
To: George Henry <ka3hsw@xxx.xxx>
Cc: amsat bb <amsat-bb@xxxxx.xxx>, n6ghz@xxxxx.xxx
Message-ID: <4B4E93B6.1010404@xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Is it any worse than the majority of sites that don't even have a security
certificate?
On 14-Jan-10 01:03, George Henry wrote:
> I tried to visit the ARISSat-1 documentation site mentioned in the Nov/Dec
> AMSAT Journal to look at the current schematics, and received a warning that
> the site's security certificate was not issued by a trusted source.....
>
> Dare I proceed?
------------------------------
Message: 6
Date: Thu, 14 Jan 2010 19:37:45 +1300
From: don <donmc@xxxx.xx.xx>
Subject: [amsat-bb] Re: ARISSat-1 Documentation site
To: amsat-bb@xxxxx.xxx
Message-ID: <4B4EBBB9.5020806@xxxx.xx.xx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 14/01/2010 4:47 p.m., Nigel Gunn G8IFF/W8IFF wrote:
> Is it any worse than the majority of sites that don't even have a security
certificate?
>
> On 14-Jan-10 01:03, George Henry wrote:
>
>> I tried to visit the ARISSat-1 documentation site mentioned in the Nov/Dec
>> AMSAT Journal to look at the current schematics, and received a warning
that
>> the site's security certificate was not issued by a trusted source.....
>>
>> Dare I proceed?
>>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>
>
What an asinine reply.....is it worse or not?
Don.
------------------------------
Message: 7
Date: Thu, 14 Jan 2010 20:10:55 +0900
From: "Mineo Wakita" <ei7m-wkt@xxxxxxxxx.xx.xx>
Subject: [amsat-bb] FO-29 schedule Jan, Feb.
To: <amsat-bb@xxxxx.xxx>
Message-ID: <80953553274A4CFEA0A500421120E709@xxxxxxxxxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-2022-jp";
reply-type=original
JARL says: The eclipse rate of FO-29 suddenly changes from January to
February, but it seems that the possibility of consecutive operation
is low, because the malfunction occurs in the battery control circuit.
But we make a temporary operative plan and operate it, because there is
the possibility of the spontaneous cure to be before approximately 2 years.
When the surplus occurred for the electricity income and expenditure,
we review an operative plan and do it.
It is operated until time to be OFF by UVC after a transmitter turned ON
on the following date and time.
Jan. UTC
16 21:00-
22 22:33-
24 10:35-
29 21:25-
31 09:30-
Feb. UTC
5 22:00-
7 10:00-
11 11:40-
12 20:53-
14 10:40-
It does not limit the use of the analog system transponder, but
please do uplink with the reasonable power. We may cancel the use
of the next day depending on the situation of the examination use.
JE9PEL, Mineo Wakita
------------------------------
Message: 8
Date: Thu, 14 Jan 2010 12:27:19 +0000
From: Clive Wallis <amsat-bb@xxxxx.xx.xx>
Subject: [amsat-bb] OSCAR-11 Report
To: amsat-bb@xxxxx.xxx
Message-ID: <4B4F0DA7.9000302@xxxxx.xx.xx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
OSCAR-11 REPORT 14 January 2010
This report covers the period from 30 November 2009 to 14 January 2010.
During this time the satellite was heard briefly on 10 & 11 December and
then from 31 December until 10 January. Good signals were received, and
decoded. Sometimes signals have been very strong, although frequent changes
in polarisation have been observed. The satellite was not heard
during solar eclipses, which now occur during the afternoon and evening
passes over the UK.
The last two 'off' periods have lasted 14 and 19 days respectively,
suggesting that the watchdog timer has been reset. However, the last
transmission period lasted for the full ten days, so it is possible that
transmissions may resume after ten days of silence, ie. around 20 January.
However, please note that the satellite's behaviour is now very
unpredictable, and until a pattern of operation is established, it is
impossible to predict what will happen next, with any certainty.
The telemetry is unchanged from the 2008 downloads. The on-board clock
is now 252 days slow. When last received in 2008 it was 83 days slow.
The increasing error suggests that the clock may be stopping, when the
satellite is in eclipse. During the last transmission period the date
failed to increment on one occasion, from 29 to 30 May.
-------------
RECEPTION REPORTS REQUESTED!
Please send reception reports to xxxxx@xxxxx.xxx (replace xxxxx by
g3cwv) or post to amsat-bb. If you have a file, please discuss it with me,
before sending it!
You may also like to add your reception report to the live satellite status
page, on the website set up by David KD5QGR and Bob WB4APR. The URL is
http://oscar.dcarr.org/index.php
The satellite transmits on 145.826 MHz., set receiver to NBFM. OSCAR-11
has a characteristic sound, rather like raspy slow morse code, sending
"di di dah dah dah dah dah dah dah" sent over five seconds. If you are
receiving a very weak signal, switch the receiver to CW or SSB. You
should hear several sidebands around the carrier frequency, should be
able to hear the characteristic 'morse code like' sound usually on at least
two of the sidebands.
Please note that you need a clean noise free signal to decode the
signals. There is an audio clip on my website
www.g3cwv.co,uk which may be useful for identification
and as test signal for decoding.
-------------
Reception reports have been received from Peter ZL3TC, Mike DK3WN, Jon
2M0IBO and Detlef DJ3AK. Many thanks for those.
The Beacon frequencies are -
VHF 145.826 MHz. AFSK FM ASCII Telemetry
UHF 435.025 MHz. OFF
S-band 2401.5 MHz. OFF
The satellite is now subject to eclipses during every orbit. Long term
predictions indicate that eclipses will occur until 2019, when there will
be some eclipse free periods until 2023. However these very long term
predictions should be regarded with caution, as large tracking errors can
accumulate over long periods of time.
When analogue telemetry was last received in March 2005, it showed that
one of the solar arrays had failed, and there was a large unexplained
current drain on the main 14 volt bus. After 25 years in orbit the battery
has undergone over 100,000 partial charge/discharge cycles, and
observations suggest that it cannot power the satellite during eclipses
lasting more than about ten minutes, or sometimes even during periods of
poor solar attitude.
Study of the satellite's behaviour prior to 2008 suggested that its
battery would not sustain operation during solar eclipses, and the watchdog
timer would switch the satellite OFF after less than an orbit. Eclipses
are now occur during every orbit and will continue for many years. In
practice this meant that OSCAR-11 would only be heard occasionally by
stations monitoring the frequency while listening for other satellites.
The satellite unexpectedly started sustained transmissions during
November 2009, suggesting that there may have been a failure causing
reduced drain on the power supplies or a change in the watchdog timer
characteristics.
The current status of the satellite, is that all the analogue telemetry
channels, 0 to 59 are zero, ie they have failed. The status channels 60 to
67 are still working. The real time clock is showing a large accumulated
error, although over short periods timekeeping is accurate to a few seconds
per month. The day of the month has a bit stuck at 'one' so the day of the
month may show an error of +40 days for some dates. The time display has
switched into 12 hour mode. Unfortunately, there is no AM/PM indicator,
since the time display format was designed for 24 hour mode.
The spacecraft computer and active attitude control system have switched
OFF, ie. the satellite' attitude is controlled only by the passive gravity
boom gradient, and the satellite is free to spin at any speed.
The watchdog timer now operates on a 20 day cycle. The ON/OFF times have
tended to be very consistent. The average of many observations show this to
be 20.7 days, ie. 10.3 days ON followed by 10.4 days OFF. However, poor
solar attitude may result may result in a low 14 volt line supply, which
may cause the beacon to switch OFF prematurely, and reset the watchdog
timer cycle. When this occurs, the beacon is OFF for 20.7 days.
Listeners to OSCAR-11 may be interested in visiting my website. If you need
to know what OSCAR-11 should sound like, there is a short audio clip for
you to hear. The last telemetry received from the satellite is available
for download. The website contains an archive of news & telemetry data. It
also contains details about using a soundcard or hardware demodulators for
data capture. There is software for capturing data, and decoding ASCII
telemetry. The URL is www.g3cwv.co.uk Please note that my old website
www.users.zetnet.co.uk/clivew is no longer being updated, athough it may
still be available.
If you place this bulletin on a terrestrial packet network, please
use the bulletin identifier $BID:U2RPT146.CWV, to prevent duplication.
73 Clive G3CWV xxxxx@xxxxx.xxx (please replace xxxxx by g3cwv)
------------------------------
Message: 9
Date: Thu, 14 Jan 2010 12:25:40 -0500
From: "Gould Smith" <gouldsmi@xxxxxxxxx.xxx>
Subject: [amsat-bb] AMSAT adopts Acceptable Use Policy for mailing
lists
To: <amsat-bb@xxxxx.xxx>
Message-ID: <CDB8B66F6BA1469BB446A135DCB03E7D@xxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
AMSAT adopts Use Policy for AMSAT mail lists
The AMSAT Board of Directors unanamously adopted an Acceptable Use Policy
for the AMSAT Public Mailing Lists on January 5, 2010. This policy takes
effect immediately and applies to all those using the AMSAT mailing lists.
The policy can be read below in text format or is available via a link on
the front page of the amsat.org Web site or directly from this link
http://www.amsat.org/amsat-new/images/fck_images/AMSAT%20AUP.pdf
Following the October 2009 AMSAT Board meeting Gould Smith, WA4SXM AMSAT VP
of User Services appointed a committe to develop a use policy for the
mailing lists. The members of the committe did an outstanding job of putting
together a document that is acceptable to all the committe members and was
passed without change by the BoD. Thank you to the committee members:
Stephen Belter, N9IP; Alan Biddle, WA4SCA ; Mark Hammond, N8MH; Samudra
Haque, N3RDX ;and Paul Williamson,KB5MU.
The policy will be added to the AMSAT Web site and included as part of the
process when applying to join any of the AMSAT mailing lists.
==============================================================================
==
Acceptable Use Policy for the AMSAT Public Mailing Lists
Approved by the AMSAT BoD 5 January 2010
The AMSAT Bulletin Board (AMSAT-BB) public mailing list carries general
AMSAT information and discussion. The purpose of this mailing list is to
provide a forum for general discussion of any satellite-related topic. The
Space Amateur Radio Experiment (SAREX) public mailing list contains
information and discussion pertaining to amateur radio operation on manned
space missions, including the Space Shuttle, Mir (formerly), and the
International Space Station. The name is leftover from the Shuttle Amateur
Radio Experiment (SAREX) aboard Space Shuttle flights. It is now mainly
concerned with ARISS operations aboard the International Space Station.
There are also regional AMSAT public mailing lists (e.g., AMSAT-DC,
AMSAT-Florida, and AMSAT-NE) and numerous private mailing lists (e.g., Board
of Directors, Officers, AO-51 operations, etc.).
Anyone can read the messages posted on any of the public mailing lists, and
many people from around the world do so. Our audience includes AMSAT
members, board members, and officers. At any given time, the readers may
also include amateur radio operators, shortwave listeners, minors, potential
financial donors, potential launch providers, officials from other amateur
radio and satellite organizations, officials from international space
agencies, and equipment suppliers and manufacturers. Since the archives of
the public mailing lists are available on the AMSAT website, the contents of
individual messages are easily found using common search engines. Because of
this wide readership, AMSAT insists that messages posted on its public
mailing lists conform to this Acceptable Use Policy (AUP).
Acceptable Content
We embrace diversity of opinions and values. In order to preserve a
constructive environment, we do insist that messages contain appropriate
content and are respectful of the members and readers of the list. All
posts should include the author's first name and call sign, or full name if
not currently licensed.
In general, messages for the AMSAT mailing lists should be related to
amateur radio satellites.
Examples of on-topic posts include:
* Announcements of general interest, including but not limited to AMSAT
news, meetings, satellite availability, and DXpeditions.
* Technical discussions, including the physics of space flight, modulation
techniques, satellite design, RF path loss calculations, noise figure, etc.
* Inquiries and suggestions about choosing equipment, learning operating
techniques, and troubleshooting problems.
* Discussion of AMSAT plans and policies in ways that foster better
understanding of the opportunities, trade-offs, and limitations that AMSAT
faces, and constructive suggestions for improvement.
* Posting of amateur radio satellite-related equipment and software
available for sale.
Unacceptable Content
Strong disagreements on issues are inevitable, but the AMSAT mailing lists
are not the place for exchanges which become spiteful, unproductive
exchanges. If you must have a heated exchange, it should be conducted
privately and not in public on a mailing list.
We define unacceptable content as anything that is:
* Illegal
* Insulting, abusive, harassing, or threatening
* Knowingly false or misrepresentative
Enforcement of this AUP
Access to the AMSAT mailing lists is a privilege and not a right. While
these rules cover most common situations, they cannot anticipate everything.
Consequently AMSAT reserves the right to take any actions it deems
appropriate to ensure these forums are not disrupted or abused.
Violators of this policy may be subjected to manual moderation or have their
ability to post messages suspended. Violators may or may not be warned
prior to enforcement.
If you feel that you've been unfairly blocked from the list, you may appeal
your situation in writing to:
The Radio Amateur Satellite Corporation
Attention: AMSAT-BB
850 Sligo Avenue, Suite 600
Silver Spring, MD 20910
Your letter of appeal will be forwarded to the VP of User Services and the
Director of Electronic Communications for consideration.
------------------------------
Message: 10
Date: Thu, 14 Jan 2010 09:46:51 -0800
From: "David Wing" <david@xxxxxx.xxx>
Subject: [amsat-bb] Re: FO-29 schedule Jan, Feb.
To: "'Mineo Wakita'" <ei7m-wkt@xxxxxxxxx.xx.xx>, <amsat-bb@xxxxx.xxx>
Message-ID: <74B26BEC760449D9A92CB6438C18956F@xxxxx>
Content-Type: text/plain; charset="us-ascii"
Mineo,
Thanks for this schedule.
Will the transmitter be ON for a specific amount of time? How can we
determine when the transmitter will go OFF?
Thanks,
David
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Mineo Wakita
Sent: Thursday, January 14, 2010 3:11 AM
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] FO-29 schedule Jan, Feb.
JARL says: The eclipse rate of FO-29 suddenly changes from January to
February, but it seems that the possibility of consecutive operation
is low, because the malfunction occurs in the battery control circuit.
But we make a temporary operative plan and operate it, because there is
the possibility of the spontaneous cure to be before approximately 2 years.
When the surplus occurred for the electricity income and expenditure,
we review an operative plan and do it.
It is operated until time to be OFF by UVC after a transmitter turned ON
on the following date and time.
Jan. UTC
16 21:00-
22 22:33-
24 10:35-
29 21:25-
31 09:30-
Feb. UTC
5 22:00-
7 10:00-
11 11:40-
12 20:53-
14 10:40-
It does not limit the use of the analog system transponder, but
please do uplink with the reasonable power. We may cancel the use
of the next day depending on the situation of the examination use.
JE9PEL, Mineo Wakita
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 11
Date: Thu, 14 Jan 2010 13:08:25 -0500
From: Andrew Glasbrenner <glasbrenner@xxxxxxxxxx.xxx>
Subject: [amsat-bb] Re: FO-29 schedule Jan, Feb.
To: David Wing <david@xxxxxx.xxx>
Cc: 'Mineo Wakita' <ei7m-wkt@xxxxxxxxx.xx.xx>, amsat-bb@xxxxx.xxx
Message-ID: <4B4F5D99.2050100@xxxxxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
As I understand it from Mineo's postings, when the battery voltage on
FO-29 hits a certain set point the satellite turns off. By design it
should turn back on when the voltage recovers, but that part is
malfunctioning. This makes it impossible to accurately determine how
long the transponder will stay on, because it is dependent on use as
well as other parameters.
For those that remember FO-20's last months of operation, the
transponder would often be on until someone used too much power on the
uplink, or there were too many users and it would then shut off. Later
as the voltage recovered it would turn back on. At the end it was only
operational while illuminated. I think FO-29 is behaving the same way,
except it requires command intervention to turn back on.
Is this essentially correct Mineo?
73, Drew KO4MA
------------------------------
Message: 12
Date: Thu, 14 Jan 2010 13:11:41 -0500
From: Bob McGwier <rwmcgwier@xxxxx.xxx>
Subject: [amsat-bb] Re: AMSAT adopts Acceptable Use Policy for mailing
lists
To: amsat-bb@xxxxx.xxx
Message-ID: <4B4F5E5D.7030106@xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
This is welcome and it took entirely too long. Its effectiveness will
entirely be determined by enforcement: swift and sure.
73's
Bob
N4HY
On 1/14/2010 12:25 PM, Gould Smith wrote:
> AMSAT adopts Use Policy for AMSAT mail lists
>
> The AMSAT Board of Directors unanamously adopted an Acceptable Use Policy
for the AMSAT Public Mailing Lists on January 5, 2010. This policy takes
effect immediately and applies to all those using the AMSAT mailing lists.
>
> The policy can be read below in text format or is available via a link on
the front page of the amsat.org Web site or directly from this link
> http://www.amsat.org/amsat-new/images/fck_images/AMSAT%20AUP.pdf
>
> Following the October 2009 AMSAT Board meeting Gould Smith, WA4SXM AMSAT
VP of User Services appointed a committe to develop a use policy for the
mailing lists. The members of the committe did an outstanding job of putting
together a document that is acceptable to all the committe members and was
passed without change by the BoD. Thank you to the committee members:
> Stephen Belter, N9IP; Alan Biddle, WA4SCA ; Mark Hammond, N8MH; Samudra
Haque, N3RDX ;and Paul Williamson,KB5MU.
>
> The policy will be added to the AMSAT Web site and included as part of the
process when applying to join any of the AMSAT mailing lists.
--
(Co)Author: DttSP, Quiktrak, PowerSDR, GnuRadio
Member: ARRL, AMSAT, AMSAT-DL, TAPR, Packrats,
NJQRP, QRP ARCI, QCWA, FRC.
"the only people for me are the mad ones,
the ones who are mad to live, mad to talk,
mad to be saved, desirous of everything at
the same time, the ones who never yawn or
say a commonplace thing, but burn, burn, burn
like fabulous yellow roman candles" Kerouac
Twitter:rwmcgwier
Active: Facebook,Myspace,LinkedIn
------------------------------
Message: 13
Date: Thu, 14 Jan 2010 19:26:42 +0000 (UTC)
From: Bob- W7LRD <w7lrd@xxxxxxx.xxx>
Subject: [amsat-bb] AO-7 Northern Europe
To: amsat-bb@xxxxx.xxx
Message-ID:
<545517465.11144731263497202706.JavaMail.root@xxxxxxx.xxxxxxxxxx.xx.xxxx.xxxxx
xx.xxx>
Content-Type: text/plain; charset=utf-8
At 2000Z (soon) I will have a good footprint into Northern Europe on
AO-7from Seattle Wa. CN87wk.? Frequency about 145.950-?.952 Lets try to make
it happen!
?
73 Bob W7LRD
Washington State AMSAT area coordinator
------------------------------
_______________________________________________
Sent via amsat-bb@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
http://amsat.org/mailman/listinfo/amsat-bb
End of AMSAT-BB Digest, Vol 5, Issue 23
***************************************
Read previous mail | Read next mail
| |
