OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
CX2SA  > SATDIG   08.01.20 08:44l 796 Lines 25365 Bytes #999 (0) @ WW
BID : AMSATBB156
Read: GUEST
Subj: AMSAT-BB-digest V15 6
Path: IZ3LSV<IR1UAW<I0OJJ<I0OJJ<GB7CIP<N3HYM<CX2SA
Sent: 200108/0638Z @:CX2SA.SAL.URY.SOAM #:22546 [Salto] FBB7.00e $:AMSATBB156

>From cx2sa%cx2sa.sal.ury.soam@i0ojj.ampr.org Wed Jan  8 07:40:42 2020
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0m) with SMTP
	id AA94747 ; Wed, 08 Jan 2020 07:40:42 +0100
Message-Id: <AMSATBB156@i0ojj.bbs>
>From: cx2sa@cx2sa.sal.ury.soam
X-JNOS-User-Port: Telnet   (i0ojj @ 44.134.32.240)  -> Sending message

From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. Re: A9JBQ? (Bob Hammond)
   2. Version 0.36 pacsat (Kevin)
   3. Needed Home Grids ~EM58 (Michael N4DCW)
   4. Re: FS-3 (PacSat Ground Station) - holes not filled (Hans BX2ABT)
   5. Re: FS-3 (PacSat Ground Station) - holes not filled
      (Mark L. Hammond)
   6. Re: FS-3 (PacSat Ground Station) - holes not filled (Hans BX2ABT)
   7. Problem with SatPC32 Doppler Frequency Control (Bernie and Cheryl)
   8. Re: Problem with SatPC32 Doppler Frequency Control
      (Stefan Wagener)
   9. Re: Version 0.36 pacsat (Chris Thompson)
  10. Re: FS-3 (PacSat Ground Station) - holes not filled
      (Chris Thompson)
  11. AO-92 in L/v at 0218 utc for 24 hours 8 Jan 2019 (Mark L. Hammond)
  12. CAS-6/TIANQIN-1 TT&C Frequency or Object Number? (Mark Jessop)
  13. How do I reply to a message on here. (Bernie and Cheryl)


----------------------------------------------------------------------

Message: 1
Date: Mon, 6 Jan 2020 14:44:39 -0800
From: Bob Hammond <propgrinder@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] A9JBQ?
Message-ID:
<CAKoB7Oq7AW5m_c9HDfXNDJXE=-154Jtyr2+s7UYOdanv1Z0cAA@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Solved.  I missed the W as in WA9JBQ.  Thanks all.

Bob W7OTJ

On Mon, Jan 6, 2020 at 2:04 PM Bob Hammond <propgrinder@?????.???> wrote:

> I made contact with, I think, A9JBQ this morning at ~1921 UTC on AO-91.  I
> can't find that call in the QRZ or FCC database.
>
> Anyone?
>


------------------------------

Message: 2
Date: Mon, 6 Jan 2020 15:20:49 -0800
From: Kevin <wa7fwf@?????.???>
To: "amsat-bb@?????.???? <amsat-bb@?????.???>
Subject: [amsat-bb] Version 0.36 pacsat
Message-ID: <3f3f0144-b2a3-eb47-a510-dc586158d204@?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

Big shout out to Chris for version 0.36, I had a 10K file go up quickly
and with no issue, especially like that the percentage complete is shown
in the upload process.

73
Kevin WA7FWF


------------------------------

Message: 3
Date: Mon, 6 Jan 2020 23:22:15 -0500
From: Michael N4DCW <michael@?????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] Needed Home Grids ~EM58
Message-ID: <868A7896-E813-48F3-9A39-53B5D5EB424B@?????.???>
Content-Type: text/plain; charset=us-ascii

Good evening, AMSAT,

*Hypothetically*, if I were to plan a roving trip around EM58 on MLK
weekend, are there any stations that are in need of their home grids
adjoining EM58?

That would be any station whose QTH is within EM47-49, EM57-59, or 67-69.

Thanks in advance,
Michael, N4DCW


------------------------------

Message: 4
Date: Tue, 7 Jan 2020 16:12:59 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: "Mark L. Hammond" <marklhammond@?????.???>,	Amsat - BBs
<amsat-bb@?????.???>
Subject: Re: [amsat-bb] FS-3 (PacSat Ground Station) - holes not
filled
Message-ID: <2cdff258-f8cb-8a7e-20c6-167d4678c5ac@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi Mark,


Using PacSat Ground Station (as per subject title) on Linux. I upgraded
to v0.36 but that didn't help. As a temporary solution I turned the
option to automatically fill holes off, but that still leaves the holes.
I now know the culprit, which is a WOD file with hex ID 2C40 from Jan
3rd. I know I had some notes saved on how to remove the offending holes,
but I can't find them. Removing the files named 2C40.act and
2C40.act.hol doesn't help.

73 and see you on FS-3.

Hans

BX2ABT


On 1/6/20 11:16 PM, Mark L. Hammond wrote:
> Hello Hans,
>
> Glad you're using Falconsat-3.?? Which client are you using---Wisp or
> Pacsat Ground Station?? The answers are different...
>
> For Wisp, there is a utility program in Wisp where you can reset the
> holes;? Poking around you'll find it.
>
> For? PacSat Ground Station---I *highly* recommend updating to the
> latest release (0.36).? Chris AC2CZ has made some great improvements,
> and directory information function (including requesting/filling
> holes!) is among them.??? I think the new code will resolve your hole
> issue, if that's your client...
>
> https://www.g0kla.com/pacsat/index.php
>
> 73!
>
> Mark N8MH
>
>
>
> On Sun, Jan 5, 2020 at 9:18 PM Hans BX2ABT via AMSAT-BB
> <amsat-bb@?????.??? <mailto:amsat-bb@?????.???>> wrote:
>
>     Hello Chris and others,
>
>     I've got a hole dated Jan 3, that doesn't want to be filled and I
>     can't
>     find my notes on how to deal with that. What files do need to be
>     deleted
>     or altered? Who can help me out with some advice here? Thanks.
>
>     --Hans (BX2ABT)
>
>     _______________________________________________
>     Sent via AMSAT-BB@?????.??? <mailto:AMSAT-BB@?????.???>. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>
>
>
> --
> Mark L. Hammond [N8MH]


------------------------------

Message: 5
Date: Tue, 7 Jan 2020 06:38:36 -0500
From: "Mark L. Hammond" <marklhammond@?????.???>
To: Hans BX2ABT <hans.bx2abt@???.?????.???>
Cc: Amsat - BBs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] FS-3 (PacSat Ground Station) - holes not
filled
Message-ID:
<CAPRXzyoR79RKBPJLpZ94ObjF39+YfvV9LxD9YTyQ7TnJOHoTzA@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Hi Hans,

Hmmm.   Are you seeing a hole in the file or a directory hole? I get the
impression it's maybe a hole in the file.  Can you mark the file "N" to
never download? Maybe Chris will speak up and point you in the right
direction.  It might be necessary to delete the directory file and rebuild
it.  That is located ....Documents\pacsat_data\FalconSat-3\directory.db

Sorry I can't think of anything else!

73,
Mark N8MH



On Tue, Jan 7, 2020 at 3:13 AM Hans BX2ABT <hans.bx2abt@???.?????.???>
wrote:

> Hi Mark,
>
> Using PacSat Ground Station (as per subject title) on Linux. I upgraded to
> v0.36 but that didn't help. As a temporary solution I turned the option to
> automatically fill holes off, but that still leaves the holes. I now know
> the culprit, which is a WOD file with hex ID 2C40 from Jan 3rd. I know I
> had some notes saved on how to remove the offending holes, but I can't find
> them. Removing the files named 2C40.act and 2C40.act.hol doesn't help.
>
> 73 and see you on FS-3.
>
> Hans
>
> BX2ABT
>
>
> On 1/6/20 11:16 PM, Mark L. Hammond wrote:
>
> Hello Hans,
>
> Glad you're using Falconsat-3.   Which client are you using---Wisp or
> Pacsat Ground Station?  The answers are different...
>
> For Wisp, there is a utility program in Wisp where you can reset the
> holes;  Poking around you'll find it.
>
> For  PacSat Ground Station---I *highly* recommend updating to the latest
> release (0.36).  Chris AC2CZ has made some great improvements, and
> directory information function (including requesting/filling holes!) is
> among them.    I think the new code will resolve your hole issue, if that's
> your client...
>
> https://www.g0kla.com/pacsat/index.php
>
> 73!
>
> Mark N8MH
>
>
>
> On Sun, Jan 5, 2020 at 9:18 PM Hans BX2ABT via AMSAT-BB <
> amsat-bb@?????.???> wrote:
>
>> Hello Chris and others,
>>
>> I've got a hole dated Jan 3, that doesn't want to be filled and I can't
>> find my notes on how to deal with that. What files do need to be deleted
>> or altered? Who can help me out with some advice here? Thanks.
>>
>> --Hans (BX2ABT)
>>
>> _______________________________________________
>> Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>>
>
>
> --
> Mark L. Hammond [N8MH]
>
>

--
Mark L. Hammond [N8MH]


------------------------------

Message: 6
Date: Tue, 7 Jan 2020 22:30:08 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: "Mark L. Hammond" <marklhammond@?????.???>
Cc: Amsat - BBs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] FS-3 (PacSat Ground Station) - holes not
filled
Message-ID: <fa2b32ba-d32e-f222-1842-0e7df6e4014d@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi Mark,

It's a directory hole. I never tried the "N" option, but I'll try it
tomorrow anyway. Cheers for that hint.

I'll also try to play with the directory.db file (don't worry, I have
backups of everything, hi hi).

Cheers,

Hans

BX2ABT

On 1/7/20 7:38 PM, Mark L. Hammond wrote:
> Hi Hans,
>
> Hmmm.?? Are you seeing a hole in the file or a directory hole? I get
> the impression it's maybe a hole in the file.? Can you mark the file
> "N" to never download? Maybe Chris will speak up and point you in the
> right direction.? It might be necessary to delete the directory file
> and rebuild it.? That is located
> ....Documents\pacsat_data\FalconSat-3\directory.db
>
> Sorry I can't think of anything else!
>
> 73,
> Mark N8MH
>
>
>
> On Tue, Jan 7, 2020 at 3:13 AM Hans BX2ABT <hans.bx2abt@???.?????.???
> <mailto:hans.bx2abt@???.?????.???>> wrote:
>
>     Hi Mark,
>
>     Using PacSat Ground Station (as per subject title) on Linux. I
>     upgraded to v0.36 but that didn't help. As a temporary solution I
>     turned the option to automatically fill holes off, but that still
>     leaves the holes. I now know the culprit, which is a WOD file with
>     hex ID 2C40 from Jan 3rd. I know I had some notes saved on how to
>     remove the offending holes, but I can't find them. Removing the
>     files named 2C40.act and 2C40.act.hol doesn't help.
>
>     73 and see you on FS-3.
>
>     Hans
>
>     BX2ABT
>
>
>     On 1/6/20 11:16 PM, Mark L. Hammond wrote:
>>     Hello Hans,
>>
>>     Glad you're using Falconsat-3.?? Which client are you
>>     using---Wisp or Pacsat Ground Station?? The answers are different...
>>
>>     For Wisp, there is a utility program in Wisp where you can reset
>>     the holes;? Poking around you'll find it.
>>
>>     For? PacSat Ground Station---I *highly* recommend updating to the
>>     latest release (0.36).? Chris AC2CZ has made some great
>>     improvements, and directory information function (including
>>     requesting/filling holes!) is among them.??? I think the new code
>>     will resolve your hole issue, if that's your client...
>>
>>     https://www.g0kla.com/pacsat/index.php
>>
>>     73!
>>
>>     Mark N8MH
>>
>>
>>
>>     On Sun, Jan 5, 2020 at 9:18 PM Hans BX2ABT via AMSAT-BB
>>     <amsat-bb@?????.??? <mailto:amsat-bb@?????.???>> wrote:
>>
>>         Hello Chris and others,
>>
>>         I've got a hole dated Jan 3, that doesn't want to be filled
>>         and I can't
>>         find my notes on how to deal with that. What files do need to
>>         be deleted
>>         or altered? Who can help me out with some advice here? Thanks.
>>
>>         --Hans (BX2ABT)
>>
>>         _______________________________________________
>>         Sent via AMSAT-BB@?????.??? <mailto:AMSAT-BB@?????.???>.
>>         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:
>>         https://www.amsat.org/mailman/listinfo/amsat-bb
>>
>>
>>
>>     --
>>     Mark L. Hammond [N8MH]
>
>
>
> --
> Mark L. Hammond [N8MH]


------------------------------

Message: 7
Date: Tue, 7 Jan 2020 10:41:51 -0700
From: Bernie and Cheryl <hamdan@??.??????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] Problem with SatPC32 Doppler Frequency Control
Message-ID: <a116111f-6492-6658-c1bf-db9aa88bb63f@??.??????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

Dear Folks:

I can't get Doppler correction to work on my SatPC32 program /for most
of the satellites./? Let me be clear that, for SO-50, my Doppler
frequency correction works just fine.? That tells me that the hardware,
and some of the software, is set up properly.

Here's the difference that I see.? On the top of the SatPC32 screen,
there is a section that shows "Downlink" and "Uplink" frequencies, right
next to the portion where the pushbuttons exist to shift frequencies by
20khz, etc.? When I bring up SO-50 on SatPC32, the box below the
"Downlink" and "Uplink" sections is populated with the actual
frequencies, and they change during the course of a pass.? On the other
satellites, that box is a complete blank.? What do I need to do to get
the data to populate in that box, since I suspect that's what needs to
happen in order for Doppler correction to occur?

Thanks and 73 de Bernie, KF0QS



------------------------------

Message: 8
Date: Tue, 7 Jan 2020 11:50:45 -0600
From: Stefan Wagener <wageners@?????.???>
To: Bernie and Cheryl <hamdan@??.??????.???>
Cc: AMSAT BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Problem with SatPC32 Doppler Frequency Control
Message-ID:
<CAKu8kHCAZJpuroW4jrLaQACYgO6isjFB1UN2qkwKxdvLdYLa8w@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Did you enter the frequencies in your doppler.sqf file? Please read the
manual. It explains exactly what you need to do.

73, Stefan VE4SW

On Tue, Jan 7, 2020 at 11:46 AM Bernie and Cheryl via AMSAT-BB <
amsat-bb@?????.???> wrote:

> Dear Folks:
>
> I can't get Doppler correction to work on my SatPC32 program /for most
> of the satellites./  Let me be clear that, for SO-50, my Doppler
> frequency correction works just fine.  That tells me that the hardware,
> and some of the software, is set up properly.
>
> Here's the difference that I see.  On the top of the SatPC32 screen,
> there is a section that shows "Downlink" and "Uplink" frequencies, right
> next to the portion where the pushbuttons exist to shift frequencies by
> 20khz, etc.  When I bring up SO-50 on SatPC32, the box below the
> "Downlink" and "Uplink" sections is populated with the actual
> frequencies, and they change during the course of a pass.  On the other
> satellites, that box is a complete blank.  What do I need to do to get
> the data to populate in that box, since I suspect that's what needs to
> happen in order for Doppler correction to occur?
>
> Thanks and 73 de Bernie, KF0QS
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>


------------------------------

Message: 9
Date: Tue, 7 Jan 2020 14:34:23 -0500
From: Chris Thompson <g0kla@????.???>
To: Kevin <wa7fwf@?????.???>
Cc: "amsat-bb@?????.???? <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Version 0.36 pacsat
Message-ID:
<CAJOf0+vteL735KQ6vXbRR1s7r5OX8SX+UrwZqu26Ko+OyL3+Yw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Thanks Kevin!

For anyone that wants to download the new version or read about what
changed, it is here:
https://www.g0kla.com/pacsat/

73
Chris

On Mon, Jan 6, 2020 at 6:22 PM Kevin via AMSAT-BB <amsat-bb@?????.???>
wrote:

> Big shout out to Chris for version 0.36, I had a 10K file go up quickly
> and with no issue, especially like that the percentage complete is shown
> in the upload process.
>
> 73
> Kevin WA7FWF
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>


--
Chris E. Thompson
chrisethompson@?????.???
g0kla@????.???


------------------------------

Message: 10
Date: Tue, 7 Jan 2020 14:45:56 -0500
From: Chris Thompson <g0kla@????.???>
To: Hans BX2ABT <hans.bx2abt@???.?????.???>
Cc: Amsat - BBs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] FS-3 (PacSat Ground Station) - holes not
filled
Message-ID:
<CAJOf0+vL0mM__9Py2a_J++DKYdvprBS6HfA4FQoSX2MQdyka_w@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Hans,

There should not be a situation where there is a hole that can not be
filled.  All those bugs are fixed :)  So please zip up your Falconsat-3
folder if you can, and send it to me.  I'd like to see what is going on.

Are the symptoms that the dir hole request is sent over and over?  If the
spacecraft responds with the file header and it is still not filled, then
that would be a bug of some sort.

Deleting the file and the .hol file won't change the directory hole
unfortunately.  Marking it as N won't prevent PSGS from trying to fill the
directory hole.  The hole is a gap in the From and To dates of the pacsat
file headers to either side of the file.  It's not a hole in the file
itself.  Strange holes can get created because the files grows on the
server and the From/To dates change.   So you can have an old header that
does not match what is on FS-3.  But trying to fill the hole should get you
the new header.

If the file is from Jan 3rd, then set the Age of your directory to 3 days
and then the hole will no longer be requested.  You can lengthen out the
directory age later as the file fades into the distance.  You set the
requested age from the menu Spacecraft > Falconsat-3.  It's on the window
that opens up.

73
Chris

On Tue, Jan 7, 2020 at 9:33 AM Hans BX2ABT via AMSAT-BB <amsat-bb@?????.???>
wrote:

> Hi Mark,
>
> It's a directory hole. I never tried the "N" option, but I'll try it
> tomorrow anyway. Cheers for that hint.
>
> I'll also try to play with the directory.db file (don't worry, I have
> backups of everything, hi hi).
>
> Cheers,
>
> Hans
>
> BX2ABT
>
> On 1/7/20 7:38 PM, Mark L. Hammond wrote:
> > Hi Hans,
> >
> > Hmmm.   Are you seeing a hole in the file or a directory hole? I get
> > the impression it's maybe a hole in the file.  Can you mark the file
> > "N" to never download? Maybe Chris will speak up and point you in the
> > right direction.  It might be necessary to delete the directory file
> > and rebuild it.  That is located
> > ....Documents\pacsat_data\FalconSat-3\directory.db
> >
> > Sorry I can't think of anything else!
> >
> > 73,
> > Mark N8MH
> >
> >
> >
> > On Tue, Jan 7, 2020 at 3:13 AM Hans BX2ABT <hans.bx2abt@???.?????.???
> > <mailto:hans.bx2abt@???.?????.???>> wrote:
> >
> >     Hi Mark,
> >
> >     Using PacSat Ground Station (as per subject title) on Linux. I
> >     upgraded to v0.36 but that didn't help. As a temporary solution I
> >     turned the option to automatically fill holes off, but that still
> >     leaves the holes. I now know the culprit, which is a WOD file with
> >     hex ID 2C40 from Jan 3rd. I know I had some notes saved on how to
> >     remove the offending holes, but I can't find them. Removing the
> >     files named 2C40.act and 2C40.act.hol doesn't help.
> >
> >     73 and see you on FS-3.
> >
> >     Hans
> >

> >     BX2ABT
> >
> >
> >     On 1/6/20 11:16 PM, Mark L. Hammond wrote:
> >>     Hello Hans,
> >>
> >>     Glad you're using Falconsat-3.   Which client are you
> >>     using---Wisp or Pacsat Ground Station?  The answers are different...
> >>
> >>     For Wisp, there is a utility program in Wisp where you can reset
> >>     the holes;  Poking around you'll find it.
> >>
> >>     For  PacSat Ground Station---I *highly* recommend updating to the
> >>     latest release (0.36).  Chris AC2CZ has made some great
> >>     improvements, and directory information function (including
> >>     requesting/filling holes!) is among them.    I think the new code
> >>     will resolve your hole issue, if that's your client...
> >>
> >>     https://www.g0kla.com/pacsat/index.php
> >>
> >>     73!
> >>
> >>     Mark N8MH
> >>
> >>
> >>
> >>     On Sun, Jan 5, 2020 at 9:18 PM Hans BX2ABT via AMSAT-BB
> >>     <amsat-bb@?????.??? <mailto:amsat-bb@?????.???>> wrote:
> >>
> >>         Hello Chris and others,
> >>
> >>         I've got a hole dated Jan 3, that doesn't want to be filled
> >>         and I can't
> >>         find my notes on how to deal with that. What files do need to
> >>         be deleted
> >>         or altered? Who can help me out with some advice here? Thanks.
> >>
> >>         --Hans (BX2ABT)
> >>
> >>         _______________________________________________
> >>         Sent via AMSAT-BB@?????.??? <mailto:AMSAT-BB@?????.???>.
> >>         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:
> >>         https://www.amsat.org/mailman/listinfo/amsat-bb
> >>
> >>
> >>
> >>     --
> >>     Mark L. Hammond [N8MH]
> >
> >
> >
> > --
> > Mark L. Hammond [N8MH]
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>


--
Chris E. Thompson
chrisethompson@?????.???
g0kla@????.???


------------------------------

Message: 11
Date: Tue, 07 Jan 2020 21:20:13 -0500
From: "Mark L. Hammond" <marklhammond@?????.???>
To: "AMSAT-BB" <AMSAT-BB@?????.???>
Subject: [amsat-bb] AO-92 in L/v at 0218 utc for 24 hours 8 Jan 2019
Message-ID: <20200108022014.E560780EC@??????????.?????.???>
Content-Type: text/plain; charset="us-ascii"

Happy L-band!  Subject says it all.

73,


Mark L. Hammond  [N8MH]



------------------------------

Message: 12
Date: Wed, 8 Jan 2020 11:29:47 +1100
From: Mark Jessop <vk5qi@??????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] CAS-6/TIANQIN-1 TT&C Frequency or Object Number?
Message-ID:
<CAJsuqdC4TR-ESbRGvpride7H3gd9r5xyo5WUfNd4aYm1yV8O0w@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Hi all,

>From this article, it looks like the CAS-6 payload V/UHF antennas on
TIANQIN-1 haven't yet been deployed:
http://www.arrl.org/news/view/camsat-says-cas-6-activation-for-amateur-use-has
-been-delayed

I'm wondering if TIANQIN-1 is beaconing on any other frequency? Clearly the
controllers are getting data from the sat somehow.

I have identified a few objects from the same launch transmitting on the
400-403 MHz TT&C band, though none of these have been named in the
catalogues (as seems to be typical for Chinese launches). In particular, I
have seen:
Object 44884 - 401.548 MHz
Object 44886 - 401.951 MHz (This is apparently a rocket body)
Object 44887 - 401.951 MHz
Object 44889 - 401.750 MHz

I'm wondering if any of these are TIANQIN-1 .. if the operators of the sat
have an object number, it would be great if they could share it, so we can
at least point our antennas in the right direction!

73
Mark VK5QI


------------------------------

Message: 13
Date: Tue, 7 Jan 2020 23:32:16 -0700
From: Bernie and Cheryl <hamdan@??.??????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] How do I reply to a message on here.
Message-ID: <a897b92b-f7bd-3e88-f823-8a77fe481848@??.??????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

I just got a reply to a prior post of mine and I'd like to thank the
author (VE4SW).? But I don't see any link on the reply where I can send
a reply.

I checked out the FAQ's and couldn't find the answer.

Thanks and 73 de Bernie, KF0QS



------------------------------

Subject: Digest Footer

_______________________________________________
Sent via amsat-bb@?????.???.
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!
https://www.amsat.org/mailman/listinfo/amsat-bb

------------------------------

End of AMSAT-BB Digest, Vol 15, Issue 6
***************************************




Read previous mail | Read next mail


 19.10.2024 09:24:05lGo back Go up