OpenBCM V1.06 (Linux)

Packet Radio Mailbox

ED1ZAC

[C.D.G. OpenBCM]

 Login: GUEST





  
CX2SA  > SATDIG   24.06.19 23:45l 1050 Lines 37721 Bytes #8 (0) @ WW
BID : AMSATBB14245
Subj: AMSAT-BB-digest V14 245
Path: ED1ZAC<ED1ZAC<IZ3LSV<IW8PGT<CX2SA
Sent: 190624/2133Z @:CX2SA.SAL.URY.SOAM #:8666 [Salto] FBB7.00e $:AMSATBB14245
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. Re: Correct up-link frequency for PO-101 (Diwata-2)
      (Stephen  E. Belter)
   2. Re: Satpc32 (k6vug@?????????.????
   3. Re: Correct up-link frequency for PO-101 (Diwata-2) (Mac A. Cody)
   4. Re: Correct up-link frequency for PO-101 (Diwata-2)
      (Alfredos (fredy) Damkalis)
   5. G5400B rotor problem (Roy Dean)
   6. Another first: rotor problems (Hans BX2ABT)
   7. ANS-175 AMSAT News Service Special Bulletin - CORRECTION BoD
      Candidates (JoAnne K9JKM)
   8. DN15 ROVE - W3ZM/7 "KI7UNJ" (KI7UNJ Tucker)
   9. Pre-launch TLE's for PSAT2 (Robert Bruninga)
  10. Re: Falconsat-3 upload problem (Chris Thompson)


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

Message: 1
Date: Mon, 24 Jun 2019 04:01:35 +0000
From: "Stephen  E. Belter" <seb@??????.???>
To: "Mac A. Cody" <maccody@???.???>, "amsat-bb@?????.????
<amsat-bb@?????.???>
Subject: Re: [amsat-bb] Correct up-link frequency for PO-101
(Diwata-2)
Message-ID: <0B961C18-5F9B-48EB-80AC-E76FE26A6CF5@??????.???>
Content-Type: text/plain; charset="utf-8"

Mac,

I used these frequencies from the @????????? Twitter home page:
Uplink 437.500 MHz, 141.3 Hz CTCSS
Downlink 145.900 MHz

I had no trouble getting into PO-101 on three passes during Field Day.  I
was able to talk to myself for all three passes for the entire pass.

Of course, I was in Copper Center, Alaska and nobody else within range was
heard.

My point is that these frequencies worked, so the AMSAT website and their
Twitter home page are most likely correct.  My station was a standard Arrow,
IC-9700, with manual tuning.

73, Steve N9IP
--
Steve Belter, seb@??????.???



?On 6/23/19, 7:35 PM, "AMSAT-BB on behalf of Mac A. Cody via AMSAT-BB"
<amsat-bb-bounces@?????.??? on behalf of amsat-bb@?????.???> wrote:

    On the AMSAT FM Satellite Frequency Summary it lists the
    up-link frequency for PO-101 (Diwata-2) as 437.500 MHz.
    On the PHL Microsat website, the up-link frequency is
    listed as 437.7 MHz.?? Which is correct??? I tried to
    work PO-101 during Field Day yesterday and had no
    success getting in with my radio set to 437.500 MHz,
    and Doppler-shift adjusted near values.?? Of course,
    being Field Day, I could have just been 'out-gunned'.
    I do wonder, though.

    73,

    Mac / AE5PH
    _______________________________________________
    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: 2
Date: Mon, 24 Jun 2019 05:07:07 +0000 (UTC)
From: "k6vug@?????????.???? <k6vug@?????????.???>
To: "amsat-bb@?????.???? <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satpc32
Message-ID: <1674974958.890162.1561352827010@????.?????.???>
Content-Type: text/plain; charset=UTF-8

 To add a bit of personal experience - calibrating the uplink forced both
stations "walk" the band during the QSO.? Eventually, realized that
adjusting the downlink instead was a better choice, and has been smooth
sailing since.?

Technically speaking, the calibration of the downlink takes care of
abnormalities in the entire chain and that lets the program (SatPC32 etc.)
ensure that the uplink is spot-on any time you pan the downlink, during the
pass.?

(Disclaimer - while there are a different schools of thought, the above is
solely based on personal observations, failures and successes. Individual
mileage may vary.)??
?
?
73!?
Umesh, k6vug?
?
?

    On Sunday, June 23, 2019, 4:49:12 PM PDT, Bob via AMSAT-BB
<amsat-bb@?????.???> wrote:

 Hi,

The manual is your friend.? The secret sauce is to adjust your uplink on
the CAT menu until you can hear yourself, then save the uplink calibration.
Trying to tune the radio knob caused both the uplink and downlink to change
and is not how you calibrate things, but is exactly the behavior you want
(manually tuning to find someone to call, and being spot on with your
downlink too.? I do feel sorry for the folks, hundreds (thousands?),
vainly sending dots/dashes during Field Day attempting to find themselves.
The secret sauce is to do that before Field Day.? With the exception of
AO-7 which was unusually far off, all the other dozen+ satellites were
within a couple hundred hertz or less of the calibration values I use at
home on my 9100 (in a fairly stable thermal environment).

Good luck, but rest assured that SatPC32 works great controlling Doppler.

73, Bob, WB4SON


On Sun, Jun 23, 2019 at 5:49 PM Bruce via AMSAT-BB <amsat-bb@?????.???>
wrote:

> I bought a Yaesu G5500 to use during field day this year, we got tired
> of the arm strong rotor. This is the first time I have used SATPC32 for
> anything more than AOS-LOS predictions. I still moved the rotor by hand.
> Have not been able to get the Yaesu cable built to have the LVB tracker
> control the rotor. May work on that for next year.
>
> Used the ICOM IC-9100 and a laptop this year. It worked great to set the
> frequency for the FM satellites but was horrible for any SSB satellite.
> I can find myself with the computer turned off. When I tried to use
> Satpc32, it would jump to somewhere in the passband and no matter how i
> tried to adjust the radio to find myself, satpc32 had a mind of its own.
> So, never made an SSB contact. Of course it is more fun to do this
> during field day with everyone watching.
>
> So what is the secret for making Satpc32 see where you have found the
> sweet spot on the up and down link when you click CAT control instead of
> doing what it wants? I would have thought it would read the settings
> from the radio and go from there. After all, it takes me a few seconds
> to find myself and really easier to adjust for Doppler manually. I
> wanted to give the automated feature a go for those watching.
>
> 73...bruce
>
> --
>
> Bruce Paige, KK5DO
>
> AMSAT Director Contests and Awards
> AMSAT Board Member 2016-2020
>
> ARRL Awards Field Checker (WAS, 5BWAS, VUCC), VE
>
> Houston AMSAT Net - Wed 0100z on Echolink - Conference *AMSAT*
> Also live streaming MP3 at http://www.amsatnet.com
> Podcast at http://www.amsatnet.com/podcast.xml or iTunes
>
> Latest satellite news on the ARRL Audio News
> http://www.arrl.org
>
> AMSAT on Twitter http://www.twitter.com/amsat
>
> _______________________________________________
> 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
>
_______________________________________________
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: 3
Date: Mon, 24 Jun 2019 00:09:29 -0500
From: "Mac A. Cody" <maccody@???.???>
To: "Stephen E. Belter" <seb@??????.???>,	"amsat-bb@?????.????
<amsat-bb@?????.???>
Subject: Re: [amsat-bb] Correct up-link frequency for PO-101
(Diwata-2)
Message-ID: <44ceb868-acb2-097e-0b43-1360b2ae80d8@???.???>
Content-Type: text/plain; charset=utf-8; format=flowed

That's what I was using.?? Like I said, I was probably just
out-gunned by more powerful stations.

73,

Mac / AE5PH

On 6/23/19 11:01 PM, Stephen E. Belter wrote:
> Mac,
>
> I used these frequencies from the @????????? Twitter home page:
> Uplink 437.500 MHz, 141.3 Hz CTCSS
> Downlink 145.900 MHz
>
> I had no trouble getting into PO-101 on three passes during Field Day.  I
was able to talk to myself for all three passes for the entire pass.
>
> Of course, I was in Copper Center, Alaska and nobody else within range was
heard.
>
> My point is that these frequencies worked, so the AMSAT website and their
Twitter home page are most likely correct.  My station was a standard Arrow,
IC-9700, with manual tuning.
>
> 73, Steve N9IP
> --
> Steve Belter, seb@??????.???
>
>
>
> ???On 6/23/19, 7:35 PM, "AMSAT-BB on behalf of Mac A. Cody via AMSAT-BB"
<amsat-bb-bounces@?????.??? on behalf of amsat-bb@?????.???> wrote:
>
>      On the AMSAT FM Satellite Frequency Summary it lists the
>      up-link frequency for PO-101 (Diwata-2) as 437.500 MHz.
>      On the PHL Microsat website, the up-link frequency is
>      listed as 437.7 MHz.?? Which is correct??? I tried to
>      work PO-101 during Field Day yesterday and had no
>      success getting in with my radio set to 437.500 MHz,
>      and Doppler-shift adjusted near values.?? Of course,
>      being Field Day, I could have just been 'out-gunned'.
>      I do wonder, though.
>
>      73,
>
>      Mac / AE5PH
>      _______________________________________________
>      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: 4
Date: Mon, 24 Jun 2019 07:50:36 +0300
From: "Alfredos (fredy) Damkalis" <fredy@?????.??>
To: "Mac A. Cody" <maccody@???.???>, "amsat-bb@?????.????
<amsat-bb@?????.???>
Subject: Re: [amsat-bb] Correct up-link frequency for PO-101
(Diwata-2)
Message-ID: <6e3f6422-0309-c4d3-6c2b-cb6fbd7ca7e5@?????.??>
Content-Type: text/plain; charset=utf-8

Hi,

I think the problem started from this "official" site[1] where the
frequency is listed as 437.700 MHz.

According to the twiiter account of Diwata-2 satellite[2] this is an old
site and needs update.

The right frequency is the one coordinated by IARU[3] and also listed in
the description of the twitter account of Diwata-2[4] and it is indeed
437.500 MHz.

73,
fredy

[1] https://phl-microsat.upd.edu.ph/diwata2
[2] https://twitter.com/Diwata2PH/status/1140257484965199872
[3] http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=593
[4] https://twitter.com/Diwata2PH


On 6/24/19 6:33 AM, Mac A. Cody via AMSAT-BB wrote:
> On the AMSAT FM Satellite Frequency Summary it lists the
> up-link frequency for PO-101 (Diwata-2) as 437.500 MHz.
> On the PHL Microsat website, the up-link frequency is
> listed as 437.7 MHz.?? Which is correct??? I tried to
> work PO-101 during Field Day yesterday and had no
> success getting in with my radio set to 437.500 MHz,
> and Doppler-shift adjusted near values.?? Of course,
> being Field Day, I could have just been 'out-gunned'.
> I do wonder, though.
>
> 73,
>
> Mac / AE5PH
> _______________________________________________
> 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: 5
Date: Mon, 24 Jun 2019 07:50:45 -0400
From: Roy Dean <royldean@?????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] G5400B rotor problem
Message-ID:
<CADGPg2s-Fm-n7N6SN3p=L8Ou3JMRAqc0hoL6hKoPzgpvtqDi4Q@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Rick, there is a new option in Hamlib specifically for the G5400B +
FoxDelta combo (about a month old). Might want to try that as it solved all
my problems.

--Roy
K3RLD


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

Message: 6
Date: Mon, 24 Jun 2019 21:34:57 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: AMSAT <amsat-bb@?????.???>
Subject: [amsat-bb] Another first: rotor problems
Message-ID: <76303575-ae5d-179d-d1d5-6d69d8c9cff2@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

There is a first for everything. So today for the first time in my 10
years as an amateur radio operator I experienced that my KR-400 rotator
(partially) stopped working. It has not been in use for 10 years, only
the last 8 months and the motor was cleaned and greased before the
install. Before I start dismantling everything I would like to see if
any of you have any good advice.

The problem --- it will turn right, not left.

What I measured --- between terminals 5 and 6 (right turn) I measured 31
Volts, which is normal. Between 4 and 6 (left turn) only 21 Volts. Rotor
not connected to the controlling box when measuring.

My thoughts --- must be in the controlling box. However, there is simply
nothing there in the circuit that I think could act up. From the
transformer one terminal carrying 29 Volts goes to two switches. The
other terminal is neutral. There is the light bulb between the two
terminals and a 70 uF/50V capacitor between the two switches.

I could be entirely wrong, so spill any info and/or tips that you can
give me, here. Cheers,

Hans

BX2ABT



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

Message: 7
Date: Mon, 24 Jun 2019 09:38:22 -0500
From: JoAnne K9JKM <k9jkm@???????.???>
To: "amsat-bb@?????.???? <amsat-bb@?????.???>
Subject: [amsat-bb] ANS-175 AMSAT News Service Special Bulletin -
CORRECTION BoD Candidates
Message-ID: <da52321a-b1c2-5f1f-814c-ae7e22be5907@???????.???>
Content-Type: text/plain; charset=utf-8; format=flowed

AMSAT NEWS SERVICE SPECIAL BULLETIN
ANS-175

* CORRECTION: 2019 Candidates for the AMSAT Board of Directors

SB SAT @ AMSAT $ANS-175.01
ANS-175 AMSAT News Service Special Bulletin

AMSAT News Service Special Bulletin 175.01
 From AMSAT HQ KENSINGTON, MD.
June 24, 2019
To All RADIO AMATEURS
BID: $ANS-175.01


CORRECTION: 2019 Candidates for the AMSAT Board of Directors

ANS-174, as originally published, omitted one of the candidates for
the upcoming AMSAT Board of Directors Election. We apologize for this
omission.

The corrected list of 2019 candidates, in alphabetical order by last
name are:

Jerry Buxton, N0JY
Howard (Howie) Defelice, AB2S
Drew Glasbrenner, KO4MA
Jeff Johns, WE4B
Brennan Price, N4QX
Patrick Stoddard, WD9EWK
Paul Stoetzer, N8HM
Michelle Thompson, W5NYV

This year AMSAT membership will select four candidates to the Board of
Directors. The four candidates receiving the highest number of votes
will be seated as voting members of the Board of Directors. Two
alternate directors will be selected based on the next highest number
of votes received.

Ballots will be mailed to the AMSAT membership by July 15, 2019.

The election closes September 15, 2019.

Sincerely,
Clayton L. Coleman, W5PFG
AMSAT Secretary




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

Message: 8
Date: Mon, 24 Jun 2019 09:35:16 -0700
From: KI7UNJ Tucker <ki7unj@?????.???>
To: AMSAT BB <amsat-bb@?????.???>
Subject: [amsat-bb] DN15 ROVE - W3ZM/7 "KI7UNJ"
Message-ID:
<CAPFr_UkxqcZm1ikEVaXEaACjX8PO_=XLET_=UUD1itjYxuf9Jw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Only 4 short days till  #JosephOrBustRove

While DN15 is my MAIN Goal I will be in DN05 as well for 1 or 2 passes.

I will be operating as W3ZM/7 while on this trip, and it will be logged
that way.

APRS Tracking: https://aprs.fi/#!call=ki7unj-9

FRIDAY  1600Z-2200Z (AO-91/92/PO-101) passes will be on the fly, keep eye
on twitter https://twitter.com/ki7unj.

June 28th (29th UTC DN15)
0331Z    AO-92

June 29th (DN15)
1801Z    AO-92
1832Z    AO-91
2249Z    SO-50

June 30th DN05 (+DN15?)
1853Z     AO-91

Soon as the June 29th and later schedule comes out for Diwata2PH  (PO-101)
I will post but hope to be on any pass that is on and FP for me.


--


Casey Tucker  KI7UNJ
https://twitter.com/KI7UNJ
https://www.qrz.com/db/KI7UNJ
http://bit.do/ki7unj
<https://www.google.com/url?q=http://bit.do/ki7unj&sa=D&source=hangouts&ust=15
21073499558000&usg=AFQjCNFcQLn6C9nmmvpQiBbD6XvN-QjKug>


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

Message: 9
Date: Mon, 24 Jun 2019 16:33:04 -0400
From: Robert Bruninga <bruninga@????.???>
To: AMSAT-BB <amsat-bb@?????.???>
Subject: [amsat-bb] Pre-launch TLE's for PSAT2
Message-ID: <6b4abc54c9e4ea22afcd83ba587fca91@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

PSAT2
1 99999U          19176.15625000  .00001426  00000-0  27052-4 0 00004
2 99999 028.4525 150.8888 0388671 088.0149 091.1931 14.93486277000010

But when we play that forward to launch time, the satellite is about 10
minutes ahead of the launch. So take it with a grain of salt.

Our best guess is as follows.  This is delta-time from launch (planned at
0330z) (USNA is our ground station here in Annapolis, MD on the USA East
coast).

time ?t  location               direction
---------   -----------------     ------------
0:00        Launch (Fla)       E
0:49        Australia             W
1:13        Hawaii                  SW
1:31        California            SW
1:35        USNA                   SW
2:33        Australia             W
2:57        Hawaii                  SW
3:07        California            SW
3:21        USNA                   S
4:31        Japan                   SE
4:39        Hawaii                  W
4:51        California            SW
6:09        Japan                   SW
6:23        Hawaii                  NW
6:59        Argentina           NE
7:47        Japan                   SW
8:07        Hawaii                  NW
8:32        Argentina           NE
9:29        Japan                   SW
9:51        Hawaii                  W
10:19     Argentina           NW

Bob


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

Message: 10
Date: Mon, 24 Jun 2019 16:21:46 -0500
From: Chris Thompson <g0kla@????.???>
To: Hans BX2ABT <hans.bx2abt@???.?????.???>
Cc: AMSAT <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Falconsat-3 upload problem
Message-ID:
<CAJOf0+vYqm8ow0v80+HA8OFKCKQQkAu0469g-Xebj=F-_VKkWw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Sorry for the late reply.  I've been a bit buried in other tasks.

I don't think I have seen this issue before.  I have seen the issue were we
keep requesting a file, even though it is fully downloaded, because
FalconSat-3 changes the timestamps when it updates files.  But I have not
seen this issue.  So I have logged it here:
https://github.com/ac2cz/Falcon/issues/43

I'll check the code and see if I introduced an issue with some changes I
did to fix another bug.

Can you send me the file that you have difficulty uploading?  Or attach it
to the github issue?

73
Chris

On Wed, Jun 19, 2019 at 7:32 AM Hans BX2ABT <hans.bx2abt@???.?????.???>
wrote:

> Okay, many hours googling and reading later......... I came upon two
> documents with some relevant information. First this is from the
> document "Pacsat File Header Definition". As it already says, it give a
> definition:
>
> -------BEGIN-------
> 3.1.9 body_checksum
>
> id              :    0x09
> length          :    2
> data            :    unsigned int body_checksum
>
> A 16 bit checksum formed by adding all bytes in the file body into a 16
> bit variable, ignoring overflow.  The <body_checksum> does not include
> the bytes comprising the PACSAT file header.
>
> The <body_checksum> is primarily intended to detect mis-corrected
> multi-bit errors caused by Single Event Upsets in the PACSAT memory.
>
> INITIALIZATION - The correct <body_checksum> must be supplied.
> -------END-------
>
> I don't quite understand the second but last sentence: does the PACSAT
> memory get upset by my messages?
>
>
>  From "Pacsat Protocol: File Transfer Level 0" document more on the
> upload procedures:
>
> -------BEGIN-------
> 7.4. Completion of Upload
>
> 7.4.1 Successful Upload Completion
>
> When the server receives the DATA_END packet it will check the integrity
> of the file as far as possible.  If the checks pass, the server will
> downlink a
> UL_ACK_RESP packet.
>
> Packet: UL_ACK_RESP
> Information: none
>
> After transmitting the UL_ACK_RESP the server uplink state variable is
> UL_CMD_OK.  After receiving the UL_ACK_RESP, the client uplink state
> variable is UL_CMD_OK.
>
> 7.4.2 Failure Caused by Server Rejecting Upload
>
> The server may reject an upload while the client is sending DATA packets
> (due to file system problems on the server) or after the client has sent
> the DATA_END packet (due to corruption of the file).
>
> If the server must abort the upload while receiving DATA packets or
> after receiving the DATA_END checks fail, it sends the UL_NAK_RESP packet.
>
> Information: 1 byte
>       unsigned char err_code;
> <err_code>     must be one of:
>
> ER_BAD_HEADER - The file either has no PFH, or has a badly-formed PFH.
> ER_HEADER_CHECK - The PFH checksum failed.
> ER_BODY_CHECK - The PFH body checksum failed.
> ER_NO_ROOM - The server ran out of room for file storage before the
> upload was complete. The server will implement procedures to avoid
> frequently running out of room, but this cannot be guaranteed.
>
> After transmitting the UL_NAK_RESP packet, the server uplink state
> variable is UL_CMD_OK.  After receiving the UL_ERROR_RESP, the client
> uplink state variable is UL_CMD_OK.
> -------END-------
>
> So I clearly get a UL_NAK_RESP packet with the ER_BODY_CHECK error.
>
> I also downloaded the PACSAT Ground Station software source code from
> G0KLA (hello Chris). The hex code for the BODY_CHECKSUM is 0x09. If you
> search for that in the source code you come up with the file Crc16.java.
> My coding skills are very minimal, so I don't grok the code completely,
> but I do see something strange in that file Crc16.java:
>
> -------BEGIN-------
>
> String s = "HELLO";
>
>       byte[] bytes = s.getBytes();
>
>
>       //Crc16 crc = new Crc16(bytes);
>       short cs = 0;
>       for(byte b : bytes)
>           cs += b & 0xff;
>       System.out.println(cs);
>
>       PacSatField pf = new PacSatField(cs, 0x09);
>       System.out.println(pf);
>      }
> -------END-------
>
> String s is probed for the number of bytes, then "converted" into
> variable cs, which is the PacSatField 0x09, iow the Body_Checksum. Now
> string s is simply "HELLO" and I don't see if this is hard coded or that
> this string changes according to the content of the message body. Any
> Java programmers here who want to help me look at it?
>
> Any help appreciated. Cheers,
>
> Hans
>
> BX2ABT
>
>
> On 06/18/2019 10:07 PM, Hans BX2ABT via AMSAT-BB wrote:
> > Hello all,
> >
> > Got all your TESTING UPLOAD messages in loud and clear. My message to
> > K4KDR didn't get send out. I'm still (re)searching about the cause of
> > this. Later......
> >
> > Hans
> >
> > BX2ABT
> >
> >
> > On 06/18/2019 09:45 PM, Mark L. Hammond wrote:
> >> Hi Hans,
> >>
> >> I was able to upload a message (to you!) on FS-3 last night/this
> >> morning, fully automated.  So the satellite is evidently behaving OK.
> >>
> >> Hope you get it figured out.  Since I don't use Direwolf, sorry I
> >> can't give any suggestions.
> >>
> >> 73,
> >>
> >> Mark N8MH
> >>
> >> At 08:07 AM 6/18/2019 +0800, Hans BX2ABT wrote:
> >>
> >>> I didn't write it directly, but I assumed from the description you
> >>> would read that I indeed run full duplex (and to add to this: my
> >>> system is Linux, not Windows). If not Direwolf will wait for a free
> >>> window to throw out packets which will never happen because FS-3 is
> >>> on all the time. No, everything is working, except for the problem I
> >>> described before: all commands to the bird are heard and responded
> >>> to, but uploading a message will fail.
> >>>
> >>> Desensing is also not the problem: got the appropriate filters in
> >>> place for that. Cheers,
> >>>
> >>> Hans
> >>>
> >>> BX2ABT
> >>>
> >>> On 06/17/2019 10:52 PM, Mark L. Hammond wrote:
> >>>> Hello Hans, I have not been working FS-3 recently, since the
> >>>> IC-9700 will not do 9600 packet [iCom, please fix!!] :( ? ?  So I
> >>>> cannot comment on recent uploads.? However, to add to Bob's
> >>>> thoughts--are you running full duplex? ? It's critical.?  Also, is
> >>>> your transmit signal desensitizing your receive signal?? ?  That is
> >>>> important, too.?
> >>>>
> >>>> In the next week or so I will change radios at my station so I can
> >>>> again use FS-3. ?  I'll be better able to share current experiences
> >>>> with you.
> >>>>
> >>>> 73,
> >>>>
> >>>> Mark N8MH
> >>>>
> >>>> On Mon, Jun 17, 2019 at 9:19 AM Hans BX2ABT via AMSAT-BB
> >>>> <amsat-bb@?????.??? <mailto:amsat-bb@?????.???>> wrote:
> >>>>
> >>>>     I'm not behind my shack computer right now, but I know that PSGS
> >>>>     and
> >>>>     Direwolf each have a TX delay. Are you referring to those maybe
> >>>>     being
> >>>>     too long? If so, then why are all other commands?  (DL and
> >>>>     directory
> >>>>     listings) giving me no problem?
> >>>>
> >>>>     73 de Hans
> >>>>
> >>>>     BX2ABT
> >>>>
> >>>>
> >>>>     On 06/17/2019 08:53 PM, Robert Bruninga wrote:
> >>>>     > I am no expert.?  But remember that your RF and all processing
> >>>>     has to
> >>>>     > be full duplex.?  The turn arround for packets in the
> >>>>     satellite is
> >>>>     > instantaneous.
> >>>>     > with no TXD delays.?  Bob
> >>>>     >
> >>>>     >
> >>>>     > On Mon, Jun 17, 2019 at 2:24 AM Hans BX2ABT via AMSAT-BB
> >>>>     > <amsat-bb@?????.??? <mailto:amsat-bb@?????.???>
> >>>>     <mailto:amsat-bb@?????.??? <mailto:amsat-bb@?????.???>>> wrote:
> >>>>     >
> >>>>     >?  ?  ? Up til now I have been successful in getting
> >>>>     PacSatGroundStation
> >>>>     >?  ?  ? (PSGS)
> >>>>     >?  ?  ? to work on receive. You can go here if you want to see
> >>>>     my setup:
> >>>>     >?  ?  ? http://bx2abt.com/main/Falconsat-3
> >>>>     <http://bx2abt.com/main/Falconsat-3> . I can hit FalconSat-3
> >>>> with a
> >>>>     >?  ?  ? directory request or file download request and get an
> >>>>     immediate
> >>>>     >?  ?  ? response
> >>>>     >?  ?  ? and consequent downloads. Uploading is a different
> >>>>     story, however. I
> >>>>     >?  ?  ? have been able to get some messages uploaded, but it
> >>>>     was more by
> >>>>     >?  ?  ? chance.
> >>>>     >?  ?  ? Right now if I want to upload I seem to get into a loop
> >>>>     where PSGS
> >>>>     >?  ?  ? keeps
> >>>>     >?  ?  ? on sending out the same frame (I presume), then
> >>>>     disconnects, after
> >>>>     >?  ?  ? which
> >>>>     >?  ?  ? the whole cycle starts over again.
> >>>>     >
> >>>>     >?  ?  ? ? From the PSGS debugging info you can see that I am
> >>>>     successful in
> >>>>     >?  ?  ? logging into PFS3-12. My file gets a designated ID
> >>>>     (1f14 in this
> >>>>     >?  ?  ? case)
> >>>>     >?  ?  ? and is ready to be received. Then it uploads what I
> >>>>     presume is one
> >>>>     >?  ?  ? frame
> >>>>     >?  ?  ? (you can see this in Direwolf where the same chunk of
> >>>>     data is send
> >>>>     >?  ?  ? over
> >>>>     >?  ?  ? and over again) after which possibly the reason why
> >>>>     things don't
> >>>>     >?  ?  ? work:
> >>>>     >?  ?  ? "ER_BODY_CHECK received while uploading:
> >>>>     >?  ?  ?
> >>>> /home/hans/PacSatGroundData/FalconSat-3/BX2ABT17.txt.out". The only
> >>>>     >?  ?  ? mention of ER_BODY_CHECK I can find on the internet is
> >>>>     that it is
> >>>>     >?  ?  ? sent
> >>>>     >?  ?  ? when the checksum on the file body fails. After that
> >>>>     the whole
> >>>>     >?  ?  ? sequence
> >>>>     >?  ?  ? starts again, so the message never gets uploaded and
> >>>>     out of the queue.
> >>>>     >
> >>>>     >?  ?  ? Does this problem lie with FalconSat-3, Direwolf or
> >>>>     PGSG, or
> >>>>     >?  ?  ? somewhere
> >>>>     >?  ?  ? else? Where is the checksum being made? This is my
> >>>>     first forray into
> >>>>     >?  ?  ? packet radio/PacSat, so I'm not an expert (yet). I
> >>>>     don't want to make
> >>>>     >?  ?  ? any (un)educated guesses, thus any help or hints are
> >>>>     appreciated.
> >>>>     >?  ?  ? Cheers,
> >>>>     >
> >>>>     >?  ?  ? Hans
> >>>>     >?  ?  ? BX2ABT
> >>>>     >
> >>>>     >
> >>>>     >
> >>>>     >?  ?  ? This is the output (with debugging turned on) of PSGS:
> >>>>     >
> >>>>     >?  ?  ? --------BEGIN-------
> >>>>     >?  ?  ? Open ABCD:
> >>>>     >?  ?  ? Ready to upload file: BX2ABT17.txt.out
> >>>>     >?  ?  ? B: 209908947.
> >>>>     >?  ?  ? U>>
> >>>>     >?  ?  ? DEBUG 3: Open: Adding UP LINK Event: UL_CONNECT
> >>>>     >?  ?  ? PB: Empty..
> >>>>     >?  ?  ? I>>From:PFS3-12 to BX2ABT?  Ctrl: 0 Type: I Cmd PF: 0
> >>>>     NR: 0 NS: 0?
> >>>>     >?  ?  ? 5 2 cc
> >>>>     >?  ?  ? a7 fb 5c 4> SUCCESSFUL LOGIN to PFS3-12 by BX2ABT
> >>>>     >?  ?  ? DEBUG 3: Open: Adding UP LINK Event: From:PFS3-12 to
> >>>>     BX2ABT Ctrl: 0
> >>>>     >?  ?  ? Type: I Cmd PF: 0 NR: 0?  NS: 0?  5 2 cc a7 fb 5c 4>
> >>>>     SUCCESSFUL
> >>>>     >?  ?  ? LOGIN to
> >>>>     >?  ?  ? PFS3-12 by BX2ABT
> >>>>     >?  ?  ? DEBUG 3: Cmd Ok: Adding UP LINK Event: UL_REQUEST_UPLOAD
> >>>>     >?  ?  ? DEBUG 3: Cmd Ok: UL_CMD: From:BX2ABT to PFS3-12 Ctrl: 0
> >>>>     Type: I
> >>>>     >?  ?  ? Cmd PF:
> >>>>     >?  ?  ? 0 NR: 0?  NS: 0?  8 3 14 1f 0 0 31 3 0 0 UL CMD:
> >>>>     UPLOAD_CMD File: 1f14
> >>>>     >?  ?  ? Size: 331
> >>>>     >?  ?  ? S>>
> >>>>     >?  ?  ? I>>From:PFS3-12 to BX2ABT?  Ctrl: 22 Type: I Cmd PF: 0
> >>>>     NR: 1 NS: 1?
> >>>>     >?  ?  ? 8 4
> >>>>     >?  ?  ? 14 1f 0 0 31 3 0 0> Ready to receive file: 1f14 from
> >>>>     BX2ABT?  at
> >>>>     >?  ?  ? off: 817
> >>>>     >?  ?  ? DEBUG 3: Waiting: Adding UP LINK Event: From:PFS3-12 to
> >>>>     BX2ABT
> >>>>     >?  ?  ? Ctrl: 22
> >>>>     >?  ?  ? Type: I Cmd PF: 0 NR: 1?  NS: 1?  8 4 14 1f 0 0 31 3 0
> >>>>     0> Ready to
> >>>>     >?  ?  ? receive
> >>>>     >?  ?  ? file: 1f14 from BX2ABT?  at off: 817
> >>>>     >?  ?  ? DEBUG 3: Waiting: UL_GO_RESP: From:PFS3-12 to BX2ABT?
> >>>>     Ctrl: 22
> >>>>     >?  ?  ? Type: I
> >>>>     >?  ?  ? Cmd PF: 0 NR: 1?  NS: 1?  8 4 14 1f 0 0 31 3 0 0> Ready
> >>>>     to receive
> >>>>     >?  ?  ? file:
> >>>>     >?  ?  ? 1f14 from BX2ABT?  at off: 817
> >>>>     >?  ?  ? DEBUG 3: Waiting: GO FILE>From:PFS3-12 to BX2ABT?
> >>>>     Ctrl: 22 Type: I
> >>>>     >?  ?  ? Cmd
> >>>>     >?  ?  ? PF: 0 NR: 1?  NS: 1?  8 4 14 1f 0 0 31 3 0 0> Ready to
> >>>>     receive file:
> >>>>     >?  ?  ? 1f14
> >>>>     >?  ?  ? from BX2ABT?  at off: 817
> >>>>     >?  ?  ? DEBUG 3: Data: Adding UP LINK Event: UL_DATA_END
> >>>>     >?  ?  ? DEBUG 3: Data: UL_DATA_END: UL_DATA_END
> >>>>     >?  ?  ? S>>
> >>>>     >?  ?  ? I>>From:PFS3-12 to BX2ABT?  Ctrl: 44 Type: I Cmd PF: 0
> >>>>     NR: 2 NS: 2?
> >>>>     >?  ?  ? 1 7
> >>>>     >?  ?  ? 10> UL NAK 16: ER_BODY_CHECK
> >>>>     >?  ?  ? DEBUG 3: Data End: Adding UP LINK Event: From:PFS3-12
> >>>>     to BX2ABT
> >>>>     >?  ?  ? Ctrl: 44
> >>>>     >?  ?  ? Type: I Cmd PF: 0 NR: 2?  NS: 2?  1 7 10> UL NAK 16:
> >>>>     ER_BODY_CHECK
> >>>>     >?  ?  ? DEBUG 3: Data End: UL_NAK_RESP: From:PFS3-12 to BX2ABT
> >>>>     Ctrl: 44
> >>>>     >?  ?  ? Type: I
> >>>>     >?  ?  ? Cmd PF: 0 NR: 2?  NS: 2?  1 7 10> UL NAK 16:
> >>>> ER_BODY_CHECK
> >>>>     >?  ?  ? NAK: ER_BODY_CHECK received while uploading:
> >>>>     >?  ?  ? /home/hans/PacSatGroundData/FalconSat-3/BX2ABT17.txt.out
> >>>>     >
> >>>>     >?  ?  ? TIME-1: PHT: uptime is 469/13:51:30.? Time is Sat Jun
> >>>>     08 12:19:29
> >>>>     >?  ?  ? 2019.
> >>>>     >?  ?  ? U>>
> >>>>     >?  ?  ? DEBUG 3: Idle: Adding UP LINK Event: UL_DISCONNECTED
> >>>>     >?  ?  ? DEBUG 3: Idle: Adding UP LINK Event: Open ABCD:
> >>>>     >?  ?  ? Open ABCD:
> >>>>     >?  ?  ? B: 209908947.
> >>>>     >?  ?  ? PB: Empty..
> >>>>     >?  ?  ? ---------END-------
> >>>>     >
> >>>>     >?  ?  ? This is what Direwolf's output is:
> >>>>     >
> >>>>     >?  ?  ? --------BEGIN-------
> >>>>     >?  ?  ? PFS3-1 audio level = 68(+118/-110)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-1>LSTAT:I P:0x13A8 o:0 l:31473 f:31529, d:1
> >>>>     st:4 e:26<0x0d>
> >>>>     >?  ?  ? Unknown APRS Data Type Indicator "I", Ambulance
> >>>>     >?  ?  ? [0L] BX2ABT>PFS3-12:(SABM cmd, p=1)
> >>>>     >
> >>>>     >?  ?  ? PFS3-12 audio level = 69(+115/-111)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-12>BX2ABT:(UA res, f=0)
> >>>>     >
> >>>>     >?  ?  ? PFS3-12 audio level = 70(+119/-110)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-12>BX2ABT:(I cmd, n(s)=0, n(r)=0, p=0,
> >>>>     >?  ?  ? pid=0xf0)<0x05><0x02>^<0xa8><0xfb>\<0x04>
> >>>>     >?  ?  ? [0L] BX2ABT>PFS3-12:(I cmd, n(s)=16, n(r)=120, p=0,
> >>>>     >?  ?  ?
> >>>> pid=0x08)<0x08><0x03><0x14><0x1f><0x00><0x00>1<0x03><0x00><0x00>
> >>>>     >
> >>>>     >?  ?  ? PFS3-12 audio level = 70(+121/-110)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-12>BX2ABT:(RR res, n(r)=1, f=0)
> >>>>     >
> >>>>     >?  ?  ? PFS3-12 audio level = 70(+121/-109)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-12>BX2ABT:(I cmd, n(s)=17, n(r)=120, p=0,
> >>>>     >?  ?  ?
> >>>> pid=0x08)<0x04><0x14><0x1f><0x00><0x00><0xfe><0x00><0x00><0x00>
> >>>>     >?  ?  ? [0L] BX2ABT>PFS3-12:(I cmd, n(s)=1, n(r)=2, p=0,
> >>>>     >?  ?  ? pid=0xf0)<0xfe><0x00>
> >>>>     >?  ?  ? the internet server that you sent me a message on April
> >>>>     11, but
> >>>>     >?  ?  ? unfortunately I never was able to download it. It took
> >>>>     a while to get
> >>>>     >?  ?  ? the transmitting part working, but now it does and I'm
> >>>> very
> >>>>     >?  ?  ? pleased to
> >>>>     >?  ?  ? be able to contact you via FS-3. Truly an amazin
> >>>>     >?  ?  ? [0L] BX2ABT>PFS3-12:(RR cmd, n(r)=2, p=1)
> >>>>     >
> >>>>     >?  ?  ? PFS3-11 audio level = 65(+118/-109)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-11>PBLIST:PB: Empty.<0x0d>
> >>>>     >?  ?  ? Unknown APRS Data Type Indicator "P", Original Balloon
> >>>>     (think Ham b
> >>>>     >
> >>>>     >?  ?  ? PFS3-12 audio level = 66(+117/-109)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-12>BX2ABT:(RR res, n(r)=1, f=1)
> >>>>     >?  ?  ? [0L] BX2ABT>PFS3-12:(I cmd, n(s)=33, n(r)=120, p=0,
> >>>>     >?  ?  ?
> >>>> pid=0x08)<0x08><0x03><0x00><0x00><0x00><0x00>1<0x03><0x00><0x00>
> >>>>     >
> >>>>     >?  ?  ? PFS3-12 audio level = 74(+125/-111)? ? [NONE] |||||||||
> >>>>     >?  ?  ? [0.4] PFS3-12>BX2ABT:(DISC cmd, p=1)
> >>>>     >?  ?  ? [0L] BX2ABT>PFS3-12:(UA res, f=1)
> >>>>     >?  ?  ? --------END-------
> >>>>     >
> >>>>     >?  ?  ? _______________________________________________
> >>>>     >?  ?  ? Sent via AMSAT-BB@?????.??? <mailto:AMSAT-BB@?????.???>
> >>>>     <mailto: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
> >>>>     <https://www.amsat.org/mailman/listinfo/amsat-bb>
> >>>>     >
> >>>>
> >>>>     _______________________________________________
> >>>>     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
> >>>>     <https://www.amsat.org/mailman/listinfo/amsat-bb>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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@????.???


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

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 14, Issue 245
*****************************************


Read previous mail | Read next mail


 27.06.2019 12:03:43lGo Back Go up