| |
CX2SA > SATDIG 17.10.17 06:17l 771 Lines 26150 Bytes #999 (0) @ WW
BID : AMSATBB12259
Read: GUEST
Subj: AMSAT-BB-digest V12 259
Path: IW8PGT<IZ3LSV<I0OJJ<N6RME<CX2SA
Sent: 171017/0413Z @:CX2SA.SAL.URY.SOAM #:23282 [Salto] FBB7.00e $:AMSATBB12259
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: ISS back on packet (Greg D)
2. Re: ISS back on packet (Greg D)
3. Re: ISS back on packet (Andrew Rich)
4. Re: ISS back on packet (Greg D)
5. Geo p4 (Ted)
6. Re: [OZAPRS] What bird did this digi off ? (Scott Evans)
7. Re: [OZAPRS] What bird did this digi off ? (Andrew Rich)
8. Beacon on heard (Andrew Rich)
9. ANS Bulletin Format Problem (JoAnne Maenpaa)
10. Re: ANS Bulletin Format Problem (JoAnne K9JKM)
11. Re: WSJT-X FT8 QSO confirmed between W2JAZ and W5RKN on FO-29
(Clayton Coleman)
12. Re: ANS Bulletin Format Problem (Zach Metzinger)
13. Re: ANS Bulletin Format Problem (Zach Metzinger)
14. Re: WSJT-X FT8 QSO confirmed between W2JAZ and W5RKN on FO-29
(David Swanson)
----------------------------------------------------------------------
Message: 1
Date: Sun, 15 Oct 2017 12:02:05 -0700
From: Greg D <ko6th.greg@xxxxx.xxx>
To: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] ISS back on packet
Message-ID: <d353a165-179e-9f3a-c779-619f602914c6@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Hi Andrew,
Nice tool. Two suggestions:
1. Make the call sign search case-independent. Easier to type in lower
case, but all the call signs are in upper case.
2. Have filter options in the search to limit the search for packets
originated by the call sign, or destined to the call sign.
Greg KO6TH
Andrew Rich wrote:
> Not on SSTV
>
> http://59.167.159.165/satreporter/index2.html
>
> Sent from my iPhone
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 2
Date: Sun, 15 Oct 2017 12:24:29 -0700
From: Greg D <ko6th.greg@xxxxx.xxx>
To: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] ISS back on packet
Message-ID: <46fa1aac-6c19-b58e-aec8-7825e32ee31e@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
One more... Make the satellite position icons at the top clickable for
a default search for that satellite's traffic. Basically the "ISS Only"
link, but for each satellite.
Greg KO6TH
Greg D wrote:
> Hi Andrew,
>
> Nice tool. Two suggestions:
>
> 1. Make the call sign search case-independent. Easier to type in lower
> case, but all the call signs are in upper case.
> 2. Have filter options in the search to limit the search for packets
> originated by the call sign, or destined to the call sign.
>
> Greg KO6TH
>
>
> Andrew Rich wrote:
>> Not on SSTV
>>
>> http://59.167.159.165/satreporter/index2.html
>>
>> Sent from my iPhone
>> _______________________________________________
>> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
>> to all interested persons worldwide without requiring membership.
Opinions expressed
>> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 3
Date: Mon, 16 Oct 2017 08:55:57 +1000
From: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
To: Greg D <ko6th.greg@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] ISS back on packet
Message-ID: <8D46C92F-5410-47FF-AC04-8D7885C1B255@xxxxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Done
Sent from my iPhone
> On 16 Oct 2017, at 5:24 am, Greg D <ko6th.greg@xxxxx.xxx> wrote:
>
> One more... Make the satellite position icons at the top clickable for
> a default search for that satellite's traffic. Basically the "ISS Only"
> link, but for each satellite.
>
> Greg KO6TH
>
>
> Greg D wrote:
>> Hi Andrew,
>>
>> Nice tool. Two suggestions:
>>
>> 1. Make the call sign search case-independent. Easier to type in lower
>> case, but all the call signs are in upper case.
>> 2. Have filter options in the search to limit the search for packets
>> originated by the call sign, or destined to the call sign.
>>
>> Greg KO6TH
>>
>>
>> Andrew Rich wrote:
>>> Not on SSTV
>>>
>>> http://59.167.159.165/satreporter/index2.html
>>>
>>> Sent from my iPhone
>>> _______________________________________________
>>> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
>>> to all interested persons worldwide without requiring membership.
Opinions expressed
>>> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
>>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>>> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 4
Date: Sun, 15 Oct 2017 19:50:19 -0700
From: Greg D <ko6th.greg@xxxxx.xxx>
To: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] ISS back on packet
Message-ID: <57de6e82-eab8-d8c5-60b1-e15bf2125727@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Thanks!
Greg KO6TH
Andrew Rich wrote:
> 1 done
> 2 coming
>
> Sent from my iPhone
>
>> On 16 Oct 2017, at 5:02 am, Greg D <ko6th.greg@xxxxx.xxx> wrote:
>>
>> Hi Andrew,
>>
>> Nice tool. Two suggestions:
>>
>> 1. Make the call sign search case-independent. Easier to type in lower
>> case, but all the call signs are in upper case.
>> 2. Have filter options in the search to limit the search for packets
>> originated by the call sign, or destined to the call sign.
>>
>> Greg KO6TH
>>
>>
>> Andrew Rich wrote:
>>> Not on SSTV
>>>
>>> http://59.167.159.165/satreporter/index2.html
>>>
>>> Sent from my iPhone
>>> _______________________________________________
>>> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
>>> to all interested persons worldwide without requiring membership.
Opinions expressed
>>> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
>>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>>> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 5
Date: Sun, 15 Oct 2017 21:27:32 -0700
From: "Ted" <k7trkradio@xxxxxxx.xxx>
To: "'R.T.Liddy'" <k8bl@xxxxxxxxx.xxx>, "'W3AB/GEO'" <w3ab@xxxxx.xxx>
Cc: 'AMSAT BB' <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Geo p4
Message-ID: <007601d34637$1664b280$432e1780$@xxxxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
He is actually licensed
K7TRK
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of R.T.Liddy
Sent: Saturday, October 14, 2017 6:54 PM
To: W3AB/GEO
Cc: AMSAT BB
Subject: Re: [amsat-bb] Geo p4
No VK4TEC in QRZ.com
No person with last name "Rich" with a VK4 Callsign.
de Bob K8BL (ex-VK4BTL)
From: W3AB/GEO via AMSAT-BB <amsat-bb@xxxxx.xxx>
To: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
Cc: AMSAT BB <amsat-bb@xxxxx.xxx>
Sent: Saturday, October 14, 2017 9:45 PM
Subject: Re: [amsat-bb] Geo p4
So?
?___
Sent from my two way wrist watch
73 de W3AB/GEO?
On Oct 14, 2017, 16:53, at 16:53, Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
wrote:
>So I watched the amsat-uk talks
>
>A rich ham radio guy is splurging on a geo satellite and the germans
>are driving it
>
>What happened USA ?
>
>Sent from my iPhone
>_______________________________________________
>Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
>to all interested persons worldwide without requiring membership.
>Opinions expressed
>are solely those of the author, and do not reflect the official views
>of AMSAT-NA.
>Not an AMSAT-NA member? Join now to support the amateur satellite
>program!
>Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available to all
interested persons worldwide without requiring membership. Opinions
expressed are solely those of the author, and do not reflect the official
views of AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available to all
interested persons worldwide without requiring membership. Opinions
expressed are solely those of the author, and do not reflect the official
views of AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 6
Date: Mon, 16 Oct 2017 08:34:18 +0000
From: Scott Evans <vk7hse@xxxxx.xxx>
To: Australian APRS Users <ozaprs@xxxx.xxx.xx>
Cc: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] [OZAPRS] What bird did this digi off ?
Message-ID:
<CADT=L5HGxkwSjPfP0Y7i-W9165NW+9qdfJQsUt64dE3=9fntow@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
That's most likely NO-84
On Mon., 16 Oct. 2017, 18:57 Andrew Rich, <vk4tec@xxxxxxxxxxxxx.xxx> wrote:
>
> 017-10-16 16:01:44 AEST: VK2HFF-10
> <https://aprs.fi/?c=raw&limit=&call=VK2HFF-10>>APRSAT,PSAT
> <http://aprs.fi/?c=raw&limit=&call=PSAT>,ARISS*
> <http://aprs.fi/?c=raw&limit=&call=ARISS>,SGATE,qAR,VK4TEC
> <http://aprs.fi/?c=raw&limit=&call=VK4TEC>
> :=3401.15S/15042.30E`[QF55IX] testing new antenna
> 2017-10-16 16:01:44 AEST: VK2HFF-10
> <https://aprs.fi/?c=raw&limit=&call=VK2HFF-10>>APRSAT,PSAT
> <http://aprs.fi/?c=raw&limit=&call=PSAT>,ARISS*
> <http://aprs.fi/?c=raw&limit=&call=ARISS>,SGATE,qAR,VK4TEC
> <http://aprs.fi/?c=raw&limit=&call=VK4TEC>
> :=3401.15S/15042.30E`[QF55IX] testing new antenna
> _______________________________________________
> OZAPRS mailing list
> OZAPRS@xxxx.xxx.xx
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
------------------------------
Message: 7
Date: Mon, 16 Oct 2017 18:37:41 +1000
From: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
To: Australian APRS Users <ozaprs@xxxx.xxx.xx>
Cc: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] [OZAPRS] What bird did this digi off ?
Message-ID: <2EC4A518-1B06-4FBC-A0B5-A2A406395407@xxxxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Thanks you I have made id so in Satreporter
if ((m/^PSAT/) || (m/PSAT-1\*/) || (m/,ARISS\*,/))
> On 16 Oct 2017, at 6:34 pm, Scott Evans <vk7hse@xxxxx.xxx> wrote:
>
> That's most likely NO-84
>
>
> On Mon., 16 Oct. 2017, 18:57 Andrew Rich, <vk4tec@xxxxxxxxxxxxx.xxx
<mailto:vk4tec@xxxxxxxxxxxxx.xxx>> wrote:
>
> 017-10-16 16:01:44 AEST: VK2HFF-10
<https://aprs.fi/?c=raw&limit=&call=VK2HFF-10>>APRSAT,PSAT
<http://aprs.fi/?c=raw&limit=&call=PSAT>,ARISS*
<http://aprs.fi/?c=raw&limit=&call=ARISS>,SGATE,qAR,VK4TEC
<http://aprs.fi/?c=raw&limit=&call=VK4TEC>:=3401.15S/15042.30E`[QF55IX]
testing new antenna
> 2017-10-16 16:01:44 AEST: VK2HFF-10
<https://aprs.fi/?c=raw&limit=&call=VK2HFF-10>>APRSAT,PSAT
<http://aprs.fi/?c=raw&limit=&call=PSAT>,ARISS*
<http://aprs.fi/?c=raw&limit=&call=ARISS>,SGATE,qAR,VK4TEC
<http://aprs.fi/?c=raw&limit=&call=VK4TEC>:=3401.15S/15042.30E`[QF55IX]
testing new antenna
> _______________________________________________
> OZAPRS mailing list
> OZAPRS@xxxx.xxx.xx <mailto:OZAPRS@xxxx.xxx.xx>
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
<http://lists.aprs.net.au/mailman/listinfo/ozaprs>
> _______________________________________________
> OZAPRS mailing list
> OZAPRS@xxxx.xxx.xx
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
------------------------------
Message: 8
Date: Mon, 16 Oct 2017 12:18:11 +1000
From: Andrew Rich <vk4tec@xxxxxxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Beacon on heard
Message-ID: <46E3A66C-FD72-4AD4-84EF-07FDE56F4283@xxxxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Wha programs beacon on hearing a satellite ?
Uiss ?
Andrew
Sent from my iPhone
------------------------------
Message: 9
Date: Mon, 16 Oct 2017 10:20:53 -0500
From: "JoAnne Maenpaa" <k9jkm@xxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] ANS Bulletin Format Problem
Message-ID: <001b01d34692$5be8f680$13bae380$@xxx>
Content-Type: text/plain; charset="US-ASCII"
Hello everyone,
We've received several reports that the AMSAT News Service bulletins are
arriving in an unreadable, mashed up, no carriage-return/no-line-feed
format. The problem is being investigated.
Others have no problem with receiving their bulletins.
In the meantime if you are affected, I'd refer readers to the ANS archive
where the format remains normal and readable:
http://www.amsat.org/pipermail/ans/2017/date.html -or-
http://www.amsat.org/pipermail/ans/
--
73 de JoAnne K9JKM
k9jkm@xxxxx.xxx
------------------------------
Message: 10
Date: Mon, 16 Oct 2017 21:16:55 -0500
From: JoAnne K9JKM <k9jkm@xxxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ANS Bulletin Format Problem
Message-ID: <093b2566-c890-aa60-4a52-2f2509c0a6c8@xxxxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
All ANS bulletins are sent plain text. We can't control what end users
are reading them with!
On 10/16/2017 9:12 PM, Andrew Rich wrote:
> You need to understand there are two types of email plain text and HTML
>
> The messed up text happens when the sender and client don't mix
>
> What are you using to send ?
>
> Andrew
>
> Sent from my iPhone
>
>> On 17 Oct 2017, at 1:20 am, JoAnne Maenpaa <k9jkm@xxxxxxx.xxx> wrote:
>>
>> Hello everyone,
>>
>> We've received several reports that the AMSAT News Service bulletins are
>> arriving in an unreadable, mashed up, no carriage-return/no-line-feed
>> format. The problem is being investigated.
>>
>> Others have no problem with receiving their bulletins.
>>
>> In the meantime if you are affected, I'd refer readers to the ANS archive
>> where the format remains normal and readable:
>> http://www.amsat.org/pipermail/ans/2017/date.html -or-
>> http://www.amsat.org/pipermail/ans/
>>
>> --
>> 73 de JoAnne K9JKM
>> k9jkm@xxxxx.xxx
>>
>>
>> _______________________________________________
>> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
>> to all interested persons worldwide without requiring membership.
Opinions expressed
>> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
--
73 de JoAnne K9JKM
k9jkm@xxxxx.xxx
------------------------------
Message: 11
Date: Mon, 16 Oct 2017 22:47:03 -0500
From: Clayton Coleman <kayakfishtx@xxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] WSJT-X FT8 QSO confirmed between W2JAZ and
W5RKN on FO-29
Message-ID:
<CAPovOwdCQ+LM4Gisz2H=aV_Svs7N2gsfFA3i6pj0R3ZkPmm5Vg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
Some may think it is experimental but I personally find it very
disruptive to use certain digital modes on satellites. It is more
disturbing when the stations performing these "experiments" fail to
minimize their station ERP to a reasonable level.
Tonight on FO-29 I witnessed first hand how disruptive it is when a
station decides to experiment with MSK144 while others are trying to
use the shared transponder resource.
Some of these modes are 100% duty cycle for periods, then switch off,
and back on again in a sequence. This doesn't seem very compatible
with your typical satellite transponder.
For the life of me I cannot figure out why someone would even think
about attempting these modes on AO-7 when the transponder's more
sensitive nature is common knowledge.
73
Clayton
W5PFG
------------------------------
Message: 12
Date: Mon, 16 Oct 2017 22:48:02 -0500
From: Zach Metzinger <zmetzing@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ANS Bulletin Format Problem
Message-ID: <57c04425-ccfb-60e9-3338-0ff96d8eaf0e@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
On 10/16/17 21:16, JoAnne K9JKM wrote:
> All ANS bulletins are sent plain text. We can't control what end users
> are reading them with!
Hello JoAnne,
A slight clarification: they appear to be a base64-encoded MIME[1]
payload. In the headers, we can see:
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
> Thunderbird/52.4.0
> MIME-Version: 1.0
<...>
> Content-Transfer-Encoding: base64
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Then, in the body, we see the base64-encoded message:
> QU1TQVQgTkVXUyBTRVJWSUNFCkFOUy0yODgKClRoZSBBTVNBVCBOZXdzIFNlcnZpY2UgYnVsbGV0
> aW5zIGFyZSBhIGZyZWUsIHdlZWtseSBuZXdzIGFuZCBpbmZvci0KbWF0aW9uIHNlcnZpY2Ugb2Yg
> QU1TQVQgTm9ydGggQW1lcmljYSwgVGhlIFJhZGlvIEFtYXRldXIgU2F0ZWxsaXRlCkNvcnBvcmF0
<...>
Since there is a base64 decoder involved in this decoding process, it
might be that some clients are getting it wrong. I have had no issue
viewing the ANS bulletins on Thunderbird, to be expected, Android K-9
mail, or mutt.
Now, I'm not entirely sure how Thunderbird decides when it should base64
encode the message, but I have my Preferences -> Composition -> General
-> Send Options -> (x) "Send messages as plain text if possible"
checked. I have verified that my messages are not base64 encoded.
If you truly want to send text-only messages, and this option is not
checked, you might try doing so. Then, send yourself an ANS bulletin and
use View -> Message Source to verify that the message body appears as
plain text.
Hope that helps!
--- Zach
N0ZGO
[1] https://en.wikipedia.org/wiki/MIME
------------------------------
Message: 13
Date: Mon, 16 Oct 2017 23:00:14 -0500
From: Zach Metzinger <zmetzing@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ANS Bulletin Format Problem
Message-ID: <3d9e0c43-1d21-e530-9ca3-5cfe9b4f236c@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
On 10/16/17 22:54, Andrew Rich wrote:
> I use perl to send true plain text
Hello Andrew,
While that might be useful in an automated setting, I don't believe one
must to go to those extremes to solve the issue reported to JoAnne.
Thunderbird is quite capable of sending 7bit ASCII messages (without HTML).
--- Zach
N0ZGO
------------------------------
Message: 14
Date: Mon, 16 Oct 2017 23:03:06 -0500
From: David Swanson <dave@xxxxxxxxxxxxx.xxx>
To: "Ronald G. Parsons" <w5rkn@xxxxx.xxx>
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] WSJT-X FT8 QSO confirmed between W2JAZ and
W5RKN on FO-29
Message-ID:
<CANq+eyWZFaJex+-22KLPXOVORBCP=fNL1CEnwHOr4L7xWuqpaw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
On the FO29 pass at 0155z this evening, I noticed a very hard time getting
into the transponder. The pass was nearly overhead, and the 3w-4w that is
normally sufficient was barely cutting it. I also noticed it was 'up and
down' alot, whereas some moments it was easy to get in, then it would be
nearly impossible. There were also pockets of 'noise' all over the
transponder, that sounded somewhat digital, but I just couldn't place them.
I found W5PFG in the passband (who was portable in a rare grid in western
Texas) and he commented on the difficulty of working an otherwise easier
bird tonight as well. I checked the screen, and no other birds were
obviously in range, so I started scanning around the passband to see what I
could hear. Up around 435.870 I found (or rather heard) what I was looking
for. I fired up my recorder and captured this:
https://drive.google.com/open?id=0B8W_KstbAsD_VF9NbGR3ZXlicUE
For those not familiar, that is the telltale sound of MSK144. I work a fair
amount of Meteor Scatter in addition to operating satellites, and the noise
is unmistakable. Since my shack PC has wsjt-x installed, I quickly fired it
up and went to the msk144 mode and after some quick tweaking started
decoding the signal. This is a screenshot of what I saw:
http://druidnetworks.com/w5rkn-msk144-fo29.jpg
This signal continued for at least 8 minutes (that I recorded) in a 5
second T/R cycle while FO29 was passing high over North America. Every 5
second the digital signal would get transmitted, and all other SSB qsos
would start to fail. You might call this an experiment, but I call it
intentional QRM.
*For the record* You are not the first person to play with wsjt-x modes on
the linear satellites. Some months ago during the late night hours on the
XW's and FO29 when the footprint was primarily over the desert southwest
and south pacific, I to "experimented" with FT8 and MSK144. I purposely ran
my transmitted signal thru over 100ft of low grade coax to attenuate my
uplink to ~1.5w ERP. I made sure the entire transponder was empty before
starting, announcing myself, then started the transmission. I decoded
myself successfully, said "Well that was dumb" and never did it again. I
purposely didn't announce what I had done to the world because I knew
someone would think they were being cool too, and would fire up a 2700hz
wide 50% duty cycle mode on a high US pass and QRM people trying to make
QSOs out of existence, because said individual would lack even basic
situational awareness and courtesy to others. What is extra hilarious about
the fact that it is you being the responsible party for destroying a pass,
is your constant whining to this mailing list about people using too much
power on AO-7, when you're one of the worst offenders. On July 16th this
summer, I was roving in EM35 and you called me on the 2155z pass of AO7,
and you got the first 3 letters of your callsign out before you killed the
bird. I know it was you, because I had already made 3 QSOs right at my AOS
with other stations using a reasonable amount of power, and as soon as you
key'd up the whole bird started FMing and croaked before you even finished
your call. You didn't get that grid that day, and after the stunt you
pulled this evening - you won't be getting any grids from me in the future
either.
-Dave, KG5CCI
On Sat, Oct 14, 2017 at 2:24 PM, Ronald G. Parsons <w5rkn@xxxxx.xxx> wrote:
> Dave,
>
> I some sense you are right, but this is a weak signal mode usable only
> when the satellite is far away so the Doppler shift change each second is
> very small. It isn?t the power being transmitted, but the power received
> at the satellite that matters, and it was being used only when the
> satellite was near maximum range. There were other signals on the
> transponder, both SSB and CW, that were so strong they were causing both
> amplitude changes and ?FMing? of my downlink signal. During preliminary
> testing with the satellite near, I observed no noticeable changes to other
> signals in the passband when my signal was strong. Strong CW and SSB
> signals from others, due to their amplitude changes did produce noticeable
> changes to my downlink. This could be why we were not successful on AO-7,
> but were successful on our first try on FO-29, which is more tolerant of
> other strong signals on the passband.
>
> Ron W5RKN
>
> On Oct 14 14:34:56 UTC 2017, "Dave Webb KB1PVH" <kb1pvh at gmail.com>
> wrote:
>
> >Ron,
> >
> > I feel your email is a little like "Do as I say, not as I do". Aren't you
> >posting repeatedly asking people to use low power on AO-7, and here you
> are
> >attempting a full duty cycle mode on AO-7.
> >
> >Dave-KB1PVH
> >
> >
> >Sent from my Galaxy S7
>
> On Oct 13, 2017 11:18 PM, "Ronald G. Parsons" <w5rkn at w5rkn.com> wrote:
>
> > A few days ago, Rick, W2JAZ, asked me if the new, short, weak signal
> > protocol, FT8, could be used on satellites. I posited it might work near
> > AOS or LOS where the Doppler corrections are small. FT8 is operationally
> > similar to the older protocols but four times faster (15-second T/R
> > sequences) and less sensitive by a few dB.
> >
> > So we set out to configure our satellite stations to use WSJT-X with FT8.
> > With some configuration advice from W0DHB, we each got our systems
> > configured. Mine (W5RKN) is a Flex-6500 with two DEMI transverters
> running
> > SmartSDR, SatPC32, FlexSATPC, and WSJT-X. Rick?s (W2JAZ) is a Flex-5000
> > with U/V module, running PowerSDR, SatPC32, FlexSATPC, and WSJT-X.
> >
> > After a couple runs on AO-7 without success, we tried again tonight on
> the
> > 0220Z (14 Oct) pass of FO-29. I started out at my AOS calling CQ W5RKN
> > EM10. After several transmissions without success, the reply W5RKN W2JAZ
> > FN29 popped up on the screen. Then followed the usual signal report, RRR
> > and 73 transmissions.
> >
> > As soon as I can figure out the appropriate fields for LoTW, we?ll log
> the
> > QSO there.
> >
> > I am not aware of other WSJT-X QSOs on the satellites, so I?d be
> > interested in other?s experiences,
> >
> > Ron and Rick
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> expressed
> are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@xxxxx.xxx.
AMSAT-NA makes this open forum available to all interested persons worldwide
without requiring membership. Opinions expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT member? Join now to support the amateur satellite program!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 12, Issue 259
*****************************************
Read previous mail | Read next mail
| |
