[amsat-bb] FS-3 (PacSat Ground Station) - holes not filled

Tue Jan 7 19:45:56 UTC 2020

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 at amsat.org>
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 at msa.hinet.net
> > <mailto:hans.bx2abt at msa.hinet.net>> 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 at amsat.org <mailto:amsat-bb at amsat.org>> 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 at amsat.org <mailto:AMSAT-BB at 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:
> >>         https://www.amsat.org/mailman/listinfo/amsat-bb
> >>
> >>
> >>
> >>     --
> >>     Mark L. Hammond [N8MH]
> >
> >
> >
> > --
> > Mark L. Hammond [N8MH]
> _______________________________________________
> Sent via AMSAT-BB at 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>

-- 
Chris E. Thompson
chrisethompson at gmail.com
g0kla at arrl.net