April 2017 - AMSAT-BB - mailman.amsat.org

ISS Beaconator
by Clayton Coleman 19 Apr '17

19 Apr '17

These are actual packets decoded by my station between 16:31-16:33 UTC today, April 18. I could post more than two minutes but it doesn't paint a different picture. Fortunately not everyone on the planet has their beacons set to go off every 2-3 seconds. 73 Clayton W5PFG Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:23] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:25] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:28] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:30] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:32] 'g.7l #/]SP= Fm RS0ISS To CQ <UI pid=F0 Len=36 >[11:31:35] >ARISS - International Space Station Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:44] 'g.7l #/]SP= Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:31:51] =3726.20N/07742.21W-73' Via ISS w4tbd(a)arrl.net FM17dk IGate WLNK-1 Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:32:07] =3726.20N/07742.21W-73' Via ISS w4tbd(a)arrl.net FM17dk IGate WLNK-1 Fm K9JKM To CQ Via RS0ISS* <UI pid=F0 Len=33 >[11:32:14] =4211.29N/08827.08W-Greetings :-) Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:28] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:30] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:32] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:35] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:37] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:40] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:44] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:46] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:47] 'g.7l #/]SP= Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:32:52] =3726.20N/07742.21W-73' Via ISS w4tbd(a)arrl.net FM17dk IGate WLNK-1 Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:33:03] 'g.7l #/]SP= Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:33:31] 'g.7l #/]SP=

4 5

FM Voice and Packet Satellites
by Alan 18 Apr '17

18 Apr '17

Back in the days when Pluto was still a planet, and I had hair, circa 1988, there were two types of questions which were repeatedly asked of the satellite builders: 1. Why do you keep making me build a new modem to copy data every time you build a new satellite? Can't you just use a TNC? Why not fly a W0RLI packet BBS? 2. Why can't you just build a flying FM repeater, so I can use my regular equipment? The techies who built satellites explained patiently both of these were Really Bad Ideas; both are extremely poor choices from a technical standpoint. They are single channel, and use one of the most inefficient modulation schemes known to hams. We have spent the past 25+ years proving the techies were right on both accounts. Consider the numerous detailed discussions concerning problems with both over the past few days. Those techies would be, and perhaps in some cases are, nodding knowingly at seeing the validity of those objections being born out. But the users have also been proven right. Satellite APRS manages to work despite these limitations, and FM satellites are often in use AOS to LOS with normally good cooperation. (Everybody is a newbie sometime.) The ability to use rather simple equipment, easily understood, has won out over technically "sweeter" solutions. Users have tacitly decided that the limitations are a good tradeoff. The proof is the number of successful QSOs and Dxpeditions reported. However, the limitations are inherent in the chosen technology, and education, innovation, consensus, and courtesy can only do so much. Keep in mind there are other voice options in the form of linear satellites now, and with only slightly greater complexity. You can chase DX, grids, and rag chew at the same time without taking away resources from other users. To borrow a phrase from AMSAT-NA's Official Curmudgeon, Tom, K3IO, "But wait, there's more!" Digital voice and data systems are being developed by the current generation of techies which will make microwave systems, and the resulting bandwidth, available to the everyone using digital signal processing and eBay parts. As Phil Karn, KA9Q, puts it, any sufficiently advanced modulation scheme is indistinguishable from noise. But with that noise will come the ability to accommodate voice, TV, and data simultaneously. For some, the tradeoff of greater complexity for almost unbelievable capability will be worth it. For others, simplicity and familiarity will win out. In both cases, that is in the best traditions of amateur radio. 73s, Alan WA4SCA Curmudgeon (jg)

1 0

Thoughts on ISS packet switch back to 145.825 MHz (long)
by Patrick STODDARD (WD9EWK/VA7EWK) 18 Apr '17

18 Apr '17

Hi! Earlier today, I tweeted a quick comment about what I saw on the ISS 145.825 MHz digipeater just after 1900 UTC this afternoon. Since tweets are limited in length, I'm posting a longer message here... In the past few weeks, once word got out that a replacement for the failed Ericsson VHF HT on the ISS was being sent up to the station, many were anxiously looking forward to seeing the ISS digipeater move from 437.550 MHz back to 145.825 MHz, where it had been until the old radio's failure in mid-October 2016. I understood that many would welcome this change, but I was not jumping up and down with excitement. Unfortunately, after seeing the activity on the ISS digipeater in the past day or so since the replacement VHF radio was put on 145.825 MHz, my worries have been confirmed. For many, the move to 437.550 MHz meant many stations that could easily work 145.825 MHz would have to change. Whether it was a different antenna for the 70cm band or dealing with Doppler with the 437.550 MHz frequency, almost all of the unattended stations that had been present on the 145.825 MHz frequency were gone. If you wanted to use the ISS digipeater to work other stations, this was a great opportunity. Many stations using APRS-ready HTs and mobile transceivers were showing up, using a group of memory channels to compensate for Doppler, and were making contacts. Some fixed stations, including those already capable of satellite operating, were also showing up. Even on the busier passes, the 437.550 MHz always seemed to be clear of the clutter from the unattended stations that previously inhabited 145.825 MHz. Fast forward to yesterday (Friday, 14 April). The ISS digipeater switched to 145.825 MHz in time for afternoon/evening passes over Europe (around 1330-1400 UTC). Lots of stations showed up, based on looking at the ariss.net web site. The same thing started to happen here in North America, later in the day. The passes I worked last night were not bad, but there were more stations on one pass that went over much of the continental USA than I'd typically see on 437.550 MHz. By midday today (1900 UTC), it seemed like many more stations were on the frequency. I saw 11 other call signs on a pass just after that time this afternoon. At best, there may have been 4 or 5 other operators at their keyboards or keypads, looking to make contacts. The others were just squawking away, not answering APRS messages sent to them. By the time the ISS footprint was reaching the east coast, the frequency was congested. Lots of position beacons were coming through, but not much of anything else. This is not new; Clayton W5PFG wrote about this about a year ago, here on the AMSAT-BB list: http://amsat.org/pipermail/amsat-bb/2016-April/058200.html For the two passes I worked this afternoon, around 1900 and 2035 UTC, I made two QSOs on the earlier pass, and one on the later pass. A shame, considering there were so many other call signs on the earlier pass, and even some rare spots - stations in DM44 in northern Arizona and CM86 in Santa Cruz CA were seen. It is interesting that hams want to have their stations squawk on 145.825 MHz when nobody is at the keyboard. It could be doing it 24/7, no matter if the ISS is in view or not. Would anyone think of setting up their satellite station to automatically transmit their call sign and location every 15/30/60 seconds to SO-50, unattended? I think not! That could be a violation of the regulations, and would definitely be poor form by that operator. Bob Bruninga WB4APR has a couple of documents with recommendations for beacon intervals when working the ISS digipeater. One mentioned a 5-minute interval for unattended stations: http://www.aprs.org/iss-aprs/iss-tx.txt Another document recommends that unattended stations should be in "receive ONLY mode." (emphasis is Bob's): http://www.aprs.org/iss-aprs/utiquet.txt I agree with the latter. If your station is unattended, why have it transmit at all?! It may be different for less-populated parts of the world, where gateway stations may transmit and then receive their beacons from the ISS, which will show up on ariss.net and other sites. For Europe, and definitely North America, the gateways really don't need to transmit if they are unattended. There should be activity on most passes, maybe even late into the night, to know 145.825 MHz on the ISS is up and running. Please don't misunderstand me... I think it is great for hams to set up gateway stations listening on 145.825 MHz for the space-borne APRS activity (ISS, NO-84, even NO-44 when it gets enough power to transmit complete packets). But these stations, like other stations that aren't operating as gateways yet transmit automatically, shouldn't contribute to the congestion on the frequency. I know I am in the minority on the ISS digipeater moving back to 145.825 MHz. Between the unattended stations clogging up the frequency and some local interference I hear on 145.825 MHz around my house, having the ISS on 437.550 MHz was fun! I worked it from home, and on some of my road trips in the past 5+ months. Even for some of my last NPOTA activations at the end of 2016. I'll continue to work the ISS digipeater, almost exclusively with my APRS-ready HTs (TH-D72A, or TH-D74A), looking to make QSOs by exchanging APRS messages with other stations. If you can work packet from your station, and we are in the same footprints, I hope to hear you (and see you on my screen) soon. Like W5PFG mentioned a year ago, let's get more stations on 145.825 MHz making QSOs... 73! Patrick WD9EWK/VA7EWK http://www.wd9ewk.net/ Twitter: @WD9EWK

16 29

PSAT APRS
by Mark Lunday 18 Apr '17

18 Apr '17

What is the logic for the digipeater on/off? Is it illumination? Both passes were off (PSAT-1 callsign) Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[23:46:20] T#578,789,347,885,889,789,00011100 Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[07:57:38] T#062,813,074,957,550,803,00011100 Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=15 >[07:58:21] s#005459,0z001 Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[07:58:39] T#063,814,072,955,543,803,00011100 Mark Lunday, WD4ELG Greensboro, NC FM06be wd4elg(a)arrl.net http://wd4elg.blogspot.com SKCC #16439 FISTS #17972

2 1

My apologies
by Kevin M 18 Apr '17

18 Apr '17

There was a recent exchange on the BB here, where there were a lot of long e-mails that I somehow manged to read a few of out of order, missed a few words here and there that changed the meaning, etc. And in an attempt to 'help' I jumped in with my two cents trying to clear up what I thought was a simple misunderstanding which met with less than spectacular results. I also injected a bit of sarcasm in an attempt to insert some humor, when the situation was most likely beyond the point of such an attempt. In the end, I may have done nothing more than to upset folks on both sides. I simply want to say... my apologies to anyone that 'I' offended, and my apologies for proverbially 'butting my nose in' when it wasn't warranted. And if I created or 'enhanced' any existing hard feelings, again, my apologies. Ham radio... it's for fun. Life is too short. (Some disclaimers may apply.) Sincerely, Kevin Manzer N4UFO

1 0

Re: [amsat-bb] Thoughts on ISS packet switch back to 145.825 MHz (long)
by Mike Diehl 18 Apr '17

18 Apr '17

Greg, Thanks for the read. My point was just general simplex leaving protocols and other factors out just to keep it simple. Like you point out, adding in overhead we loose even more time. The major problem though is that the terrestrial stations can't hear each other so the door is wide open for collisions. Which is why unmanned beacons are trouble. I think what is being lost here is what is happening at the bird. It's not like a linear or FM transponder on full duplex where we can hear what is happening. We all know when we have a dead carrier on voice because the bird is instantly transmitting what it hears. Now in the case of simplex if a dead carrier was thrown at ISS for the whole pass then how exactly would we know? One could assume nobody was on. Lots of packets heard from the station can prove a lot were heard and decoded properly. A lack of packets can indicate two things, either it wasn't receiving a lot or there were too many. That's the point I've been trying to make this whole time. Beacons should be seen for what they are, stations just simply increasing the odds of collisions at the ISS receiver. 73, Mike Diehl AI6GS > On Apr 17, 2017, at 7:45 PM, Greg D <ko6th.greg(a)gmail.com> wrote: > > I believe APRS Packet is basically an Aloha network. See https://en.wikipedia.org/wiki/ALOHAnet > > 18.4% is the theoretical limit... Yes, surprisingly low. See the article for the math behind it. > > Greg KO6TH > > > Mike Diehl wrote: >> Congrats Stefan, you still have no idea what ISS heard, only what it digipeated. Please also prove me wrong that a simplex channel can support more than 50% utilization. The fact only 5% of the pass had the ISS radio transmitting can either prove nothing or support the fact that there is so much QRM AT THE ISS that very few complete packets were heard and digipeated. >> >> As far as black listing goes the FCC has no authority over what data a site decides to exclude from showing. Sorry but you're reading and not comprehending what I stated. >> >> 73, >> >> Mike Diehl >> AI6GS >> >> On Apr 17, 2017, at 5:30 PM, Stefan Wagener <wageners(a)gmail.com> wrote: >> >>> Well Mike, >>> >>> Here is my log from the last pass. It shows 29 digipeats (~75% decoding success at my station) for 8+ minutes. Each packet is barely 1 1/2 seconds! That is a utilization of less then 5% assuming my math is correct. >>> >>> In addition, asking for "blacklisting of licensed operators" is something I certainly will not support and fortunately neither does the FCC. >>> >>> 73, Stefan, VE4NSA >>> >>> >>> .......................................... >>> >>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:46:17] >ARISS - International Space Station >>> Fm KE7ZXE-4 To CQ Via RS0ISS <UI pid=F0 Len=28 >[18:47:17] >>> N7UWX DE KE7ZXE from CN86 me >>> Fm VE6PW To U1PSWQ Via RS0ISS,ARISS <UI pid=F0 Len=32 >[18:47:59] `*Zvl _-/` Hello via ISS _% >>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:48:18] >ARISS - International Space Station >>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:49:51]`p0Kl p[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:01]`p0Kl }[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:11]`p0Kl j[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:17] `yaHl _-/ Greetings via ISS from Circle Pines MN >>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:50:18] >ARISS - International Space Station >>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:24] `p0Kl O[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:28] `yaHl _-/ Greetings via ISS from Circle Pines MN >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:35] :KD0KZE :599 Via ISS de W8LR Jerry{62 >>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:39] `yaHl _-/ Greetings via ISS from Circle Pines MN >>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:50:49] 'u&Bl _-/]CQ via ARISS,EN56jd,Paul= >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:55] :KD0KZE :599 Via ISS de W8LR Jerry{62 >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:58] :N7EKY-6 :599 Via ISS de W8LR Jerry{63 >>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:51:01] `yaHl _-/ Greetings via ISS from Circle Pines MN >>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:11] `p0Kl w[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:21] `p0Kl"F[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm W8LR To S9SR2U Via RS0ISS <UI pid=F0 Len=47 >[18:51:38] `p0Kl!%[/>CQ: Via ISS de W8LR Middletown Ohio= >>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:52:07] `yaHl _-/ Greetings via ISS from Circle Pines MN >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:10] :KD0KZE :599 Via ISS de W8LR Jerry{62 >>> Fm W0BSH-3 To S8SW6R Via RS0ISS <UI pid=F0 Len=16 >[18:52:10] `v06l _>/]"5v}= >>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:52:16] 'u&Bl _-/]CQ via ARISS,EN56jd,Paul= >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:27] :N7EKY-6 :599 Via ISS de W8LR Jerry{63 >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:30] :N7EKY-6 :599 Via ISS de W8LR Jerry{64 >>> Fm W8LR To APK003 Via TS0ISS <UI pid=F0 Len=40 >[18:53:13] :N7EKY-6# :599 Via QSS de W8LR Jerry{07 >>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:53:15] :W0BSH-3 :599 Via ISS de W8LR Jerry{65 >>> >>> >>>> On Mon, Apr 17, 2017 at 4:51 PM, Mike Diehl <diehl.mike.a(a)gmail.com> wrote: >>>> Greg, >>>> >>>> You make a good point about the complications of dropped packets. I have some good recordings of voice stations getting a call back when as little as a single letter of their call was heard. It's amazing how well we can learn the voices of other ops when you're on regularly. This simply doesn't happen on packet. >>>> >>>> Another complication is that it is on simplex. That means on a 10 minute pass the maximum amount of time possible to digipeat is 5 minutes if the channel is fully saturated. Subtract out the ISS beacons we end up with less than 50% of the pass available for ISS to hear you. >>>> >>>> I'm not sure what the best solution is. You do bring up an interesting point about APRS-IS. Maybe it's possible to have them black list fixed beacon stations and remove the vanity aspect like you mentioned. >>>> >>>> 73, >>>> >>>> Mike Diehl >>>> AI6GS >>>> >>>> > On Apr 17, 2017, at 1:26 PM, Greg D <ko6th.greg(a)gmail.com> wrote: >>>> > >>>> > Gabriel Zeifman wrote: >>>> >> It's not complicated. However much it may be insisted ISS packet is not >>>> >> SO-50, it is practically the same thing (single channel operating on FM). >>>> > Actually, the ISS digi is worse. >>>> > >>>> > With voice communication, one can sometimes pick up the start or tail of >>>> > a call sign, as the astronaut demonstrated, and use that to filter a >>>> > second try. With digital, any bits that get corrupted result in no >>>> > reception at all. >>>> > >>>> > I hate to suggest this, and admit I am assuming a cause without >>>> > supporting evidence, but it might be necessary to remove the "vanity" >>>> > aspect of ISS digipeating, and take down or hide from general view the >>>> > reporting sites that support it. While a useful tool for >>>> > troubleshooting, I suspect the vanity aspect of seeing your call in a >>>> > public list day after day from an unattended station may be too strong a >>>> > draw for some, resulting in the clogged channel. The SatGates that >>>> > monitor for ISS and other APRS satellite traffic are still important >>>> > part of the infrastructure, so that the information can be datamined >>>> > from APRS-IS if you need it for troubleshooting. But the consolidated >>>> > lists of who has been seen digipeating through the ISS, I think, may be >>>> > contributing more trouble than they are worth. >>>> > >>>> > Greg KO6TH >>>> > >>>> > _______________________________________________ >>>> > Sent via AMSAT-BB(a)amsat.org. 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(a)amsat.org. 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 >>> >

1 0

Re: [amsat-bb] EM85 semi-rare?
by Kevin M 17 Apr '17

17 Apr '17

Hi Philip, I just made a trip up to Marion with the XYL to operate from EM85 last month, I had a good number of takers, even having to share the pass with another rover operating from a much needed grid to the south. I try to keep a list of grids around me and the more avid grid chasers that need them. That list will dwindle if not empty after such a trip, but within a short time, it grows again as new folks come into the hobby and get the bug. (AMSAT journal ran an article about the XYL & I going up there about 2 years ago, there and another grid. Fun day trip for the wife!) That said, I only have one callsign listed for EM85 at the moment, but that doesn't mean more don't need it. Not everyone can necessarily make a specific pass on a specific day. Yes, I keep EM95 fairly active and the EM96 line is just right up the road from me about 15-20 minutes. But, I have a about 5 on each list for EM84 and EM86 and I am sure there are more that need them. Bottom line, there are no regular sat ops in those grids. AND no regular op that I know of in EM85 (or else I wouldn't need to drive the hour or so up there periodically.) =^) So I am sure even an irregular presence in EM85 would be welcome! I suggest you make a note on your QRZ page that you welcome sked requests... because those of us afflicted with the grid chasing disease will ask other ops things like, 'Who did you work in XX99?' and then try and scare up a sked. As for gear, a pair of 817s is great... if you can't quite afford that, a full duplex HT or a pair of HTs for FM will do. Have a look at my gear on my special QRZ page and if you like the 'bag' idea, I can send you links to where to buy that particular bag and really good shoulder straps. (Also the power cable, battery, etc.) I got the bag and straps idea from N8HM who has about perfected the art of the 'wearable sat station'. https://www.qrz.com/db/N4UFO/P Whatever you do, just make sure to have fun... that's the name of the game. Sometimes we can get wrapped up and take the hunt too seriously. As has been said before. if you aren't having fun, you aren't doing it right. 73, Kevin N4UFO

1 0

Mayan Grids (Expeditioin)
by David Maciel (XE3DX) 17 Apr '17

17 Apr '17

Hello guys. I'm going to a new adventure, to be on vacation from April 11-23. I am going to do a tour that I have called "Mayan Grids" I will be in Mayan zones, the first days I will be with family, I think I will only work FM satellites. The second week I will be the route for wanted grids, there if I work on satellites of FM and SSB, I plan to activate the grids EK48, EK59, EK69, EK69, EL60, EL61, EL50, EL51 and others ... I will be in contact Via twitter @xe3dx when you have Internet signals, there are areas that are not covered. I hope to hear ... David Maciel XE3DX *http://www.qsl.net/xe3dx/ <http://www.qsl.net/xe3dx/>* *david.xe3dx(a)gmail.com <david.xe3dx(a)gmail.com>*

1 1

Thoughts on ISS packet switch back to 145.825 MHz (short)
by Clayton Coleman 17 Apr '17

17 Apr '17

It's pretty darn satisfying that I was able to have four, short, efficient packet QSO's with stations via the ISS pass today at 17:17 UTC. Thank you KC7MG, N1RCN, WN9Q, K4RTS and the handful of others live at their keyboards/radios. It's hard to believe that in this crazy, beacon-mad world, legitimate QSO's can be made! 73 Clayton W5PFG

1 0

Fwd: Dupe contacts on SO-50
by Gabriel Zeifman 17 Apr '17

17 Apr '17

> > I think the issue Tucker raises is more when veteran sat ops try to discuss their DXpedition to Pitcairn on a busy SO-50 pass. I think everyone supports new blood, even when they fumble. > > 73, > Gabe > NJ7H > >> On Apr 17, 2017, at 1:08 PM, R.T.Liddy <k8bl(a)ameritech.net> wrote: >> >> Tucker W4FS, >> >> >> First, you are far from being a curmudgeon! You'll have to put >> in many years of crankiness before you can claim that title. >> >> You raise a point that has persisted for quite a while regarding >> FM Satellites. Experienced operators usually follow the proper >> protocol/etiquette on the single-channel resource. They rarely >> chit-chat unless the bird is idle. As with anything else, newbies >> are learning the ropes. >> >> The FM SATs, as we all know, are where the new folks start out >> because they are easy due to readily available equipment. These >> operators are trying to figure everything out at once - the frequencies, >> the antennas, the PL, the AOS/LOS/AZ/EL, the protocol, etc., etc. >> >> Until they figure all of these things out, the rest of the users are >> going to have to endure problems of various kinds. It's the utter >> reality of the situation. However, they are the "new blood" that >> we need to keep this aspect of the hobby growing. >> >> And, believe it or not, not all SAT Ops are Grid Chasers. Some only >> care about the thrill of pointing a signal up toward the sky and >> saying hello to someone via something flying through Space. We have >> no choice but to co-exist in this environment. It is what it is. >> >> A good primer for new operators can be found on John K8YSE's website >> at: http://www.papays.com/sat/general.html >> >> All we can do is be good examples for the new/other users. When someone >> is operating from a rare Grid and we already have it confirmed, stay clear. If the >> pileup dies down and no one is calling, it's perfectly fine to say a quick hello >> to let them know they are being heard. During routine passes, if you hear a new >> Call, it's nice to give them a shout so they get the operating experience. >> >> 73 & GL 2 All, Bob K8BL >> >> ________________________________ >> >> >> >> >>>> On Apr 16, 2017, at 6:58 PM, Tucker McGuire <tucker(a)mcguireland.com> wrote: >>> >>> >> >>> Hello space bird enthusiasts, >> >>> >> >>> I have noticed that certain stations on busy SO-50 passes work the same >> >>> stations that they have worked on many previous passes when they are in the >> >>> same grid. Dupe contacts. >> >>> >> >>> This can prevent and has prevented other stations from trying to work new >> >>> grids that happen to be on or perhaps prevented them from working a new guy >> >>> that hasn't been on the satellites before. On quiet passes I see no issues >> >>> with working the same station you've worked hundreds of times before but on >> >>> busy SO-50 passes it is just disruptive. >> >>> >> >>> Maybe I'm just a curmudgeon but that's my two cents. >> >>> >> >>> Cheers & 73, >> >>> Tucker >> >>> W4FS >> >>> _______________________________________________ >> >>> Sent via AMSAT-BB(a)amsat.org. 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(a)amsat.org. 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(a)amsat.org. 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

2 1