| |
CX2SA > SATDIG 17.06.19 16:44l 1095 Lines 43724 Bytes #999 (0) @ WW
BID : AMSATBB14234
Read: GUEST
Subj: AMSAT-BB-digest V14 234
Path: IW8PGT<CX2SA
Sent: 190617/1441Z @:CX2SA.SAL.URY.SOAM #:8177 [Salto] FBB7.00e $:AMSATBB14234
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Recent rove by N6DNM in DN00/10, DN20/30, DN41/51, DM79,
DM58/59, DM48/49 grids (Dmitry Mizin)
2. AO-85 report from the 2019-06-16 - 0028 UTC pass (John Brier)
3. Re: AO-85 report from the 2019-06-16 - 0028 UTC pass (Jeff Johns)
4. Falconsat-3 upload problem (Hans BX2ABT)
5. Re: AO-85 report from the 2019-06-16 - 0028 UTC pass (Alan)
6. Re: Fixed elevation - how many elements? (Hasan al-Basri)
7. Re: Falconsat-3 upload problem (Robert Bruninga)
8. Re: Falconsat-3 upload problem (Hans BX2ABT)
9. Re: Falconsat-3 upload problem (Robert Bruninga)
----------------------------------------------------------------------
Message: 1
Date: Sun, 16 Jun 2019 18:28:09 -0700
From: Dmitry Mizin <dmitry.mizin@?????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] Recent rove by N6DNM in DN00/10, DN20/30, DN41/51,
DM79, DM58/59, DM48/49 grids
Message-ID:
<CAF=oU+htdXzyVZ4zT1+aFXF=x=yQBLoqujL+u00oV4stDfohQw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Hello,
Thank You for chasing me on my recent trip from above grids and mostly
gridlines. I have uploaded (and corrected some) all entries into LOTW. I am
sure I still have made a few mistakes with entries - so, if you worked me
between 20190606 and 20190615 when I was in those gridline(s) and do not
see a LOTW confirmation - please let me know.
There were two undecipherable entries in my audio recordings from DM58/59
and DM48/49 both on SO-50 - if you are one of them, please let me know and
I will review my recordings again. Once confirmed - will upload corrected
entries.
Thank you all again! It was a blast as this was my first "big" trip doing
those activations. There will be more coming soon.
Dmitry Mizin, N6DNM
------------------------------
Message: 2
Date: Sun, 16 Jun 2019 22:45:21 -0400
From: John Brier <johnbrier@?????.???>
To: AMSAT BB <amsat-bb@?????.???>
Subject: [amsat-bb] AO-85 report from the 2019-06-16 - 0028 UTC pass
Message-ID:
<CALn0fKP7+dkNeTdXjFf3hg1hXnRdBn85c8q4edd=7am6yO1WpA@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Hi,
I made five QSOs on this 47 degree pass from FM05. I was using my
Kenwood TM-V71 radio at 50 watts and an Alaskan Arrow II antenna with
the last third boom section removed.
I didn't hear the bird for the first couple minutes of the pass and
couldn't get it to come on myself. Eventually it came on and I heard
Clayton W5PFG not long after that so I assume he turned the
transponder on. In the first half of the pass it was difficult to get
a solid signal into the sat. Other stations had the same problems.
Audio was sometimes really low, great other times, and distorted at
times as well.
The last part of the pass was not bad though. I was able to
consistently get a signal into the bird, even at 10 or 5 watts. I had
a conversation with Roy K3RLD about this as we were both having the
same good luck. This reminded me of past AO-85 behavior where it is
easier to get in in the last part of the pass. I was actually on top
of a landfill park in my town so I had a perfect view of the horizon
and was able to get in all the way to LOS, albeit with some picket
fencing effects on the downlink.
Stations contacted:
W5PFG
W5HRH
N9XCO *
N0RC
K3RLD
Also heard ???PML
* This was Richard N9XCO's first sat QSO. He just finished setting up
a IC-9700/G-5500/SatPC32 station
One odd thing I noticed is at the end of the pass I believe I was at
145.970 MHz, 10 KHz down from the center frequency of 145.980. It
looked so weird I did a double take and doubted I was really at that
frequency. I don't know if the bird was off frequency or if it was
something on my end.
My audio recording is here:
https://www.dropbox.com/s/j1xduj3had9gicm/2019-06-16_0028_UTC_AO-85_KG4AKV_FM0
5.WAV?dl=0
73, John Brier KG4AKV
------------------------------
Message: 3
Date: Sun, 16 Jun 2019 23:41:03 -0500
From: Jeff Johns <jeff30339@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] AO-85 report from the 2019-06-16 - 0028 UTC
pass
Message-ID: <B1B227E2-34EF-4698-BEF3-E77A70405815@?????.???>
Content-Type: text/plain; charset=us-ascii
KB4PML
Jeffrey Alan Johns WE4B
> On Jun 16, 2019, at 9:45 PM, John Brier via AMSAT-BB <amsat-bb@?????.???>
wrote:
>
> Hi,
>
> I made five QSOs on this 47 degree pass from FM05. I was using my
> Kenwood TM-V71 radio at 50 watts and an Alaskan Arrow II antenna with
> the last third boom section removed.
>
> I didn't hear the bird for the first couple minutes of the pass and
> couldn't get it to come on myself. Eventually it came on and I heard
> Clayton W5PFG not long after that so I assume he turned the
> transponder on. In the first half of the pass it was difficult to get
> a solid signal into the sat. Other stations had the same problems.
> Audio was sometimes really low, great other times, and distorted at
> times as well.
>
> The last part of the pass was not bad though. I was able to
> consistently get a signal into the bird, even at 10 or 5 watts. I had
> a conversation with Roy K3RLD about this as we were both having the
> same good luck. This reminded me of past AO-85 behavior where it is
> easier to get in in the last part of the pass. I was actually on top
> of a landfill park in my town so I had a perfect view of the horizon
> and was able to get in all the way to LOS, albeit with some picket
> fencing effects on the downlink.
>
> Stations contacted:
>
> W5PFG
> W5HRH
> N9XCO *
> N0RC
> K3RLD
> Also heard ???PML
>
> * This was Richard N9XCO's first sat QSO. He just finished setting up
> a IC-9700/G-5500/SatPC32 station
>
> One odd thing I noticed is at the end of the pass I believe I was at
> 145.970 MHz, 10 KHz down from the center frequency of 145.980. It
> looked so weird I did a double take and doubted I was really at that
> frequency. I don't know if the bird was off frequency or if it was
> something on my end.
>
> My audio recording is here:
>
>
https://www.dropbox.com/s/j1xduj3had9gicm/2019-06-16_0028_UTC_AO-85_KG4AKV_FM0
5.WAV?dl=0
>
> 73, John Brier KG4AKV
> _______________________________________________
> 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, 17 Jun 2019 14:24:19 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: AMSAT <amsat-bb@?????.???>
Subject: [amsat-bb] Falconsat-3 upload problem
Message-ID: <87c87ffd-cab4-12f9-01f3-92588698c8b8@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed
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 . 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-------
------------------------------
Message: 5
Date: Mon, 17 Jun 2019 06:39:08 -0500
From: "Alan" <wa4sca@?????.???>
To: <amsat-bb@?????.???>
Subject: Re: [amsat-bb] AO-85 report from the 2019-06-16 - 0028 UTC
pass
Message-ID: <000001d52501$4718f2b0$d54ad810$@?????.???>
Content-Type: text/plain; charset="us-ascii"
John,
Interesting report. One of the widely reported anomalies is that the
carrier is not timing out as it should.
73,
Alan
WA4SCA
<-----Original Message-----
<From: AMSAT-BB [mailto:amsat-bb-bounces@?????.???? On Behalf Of John
<Brier via AMSAT-BB
<Sent: Sunday, June 16, 2019 21:45 PM
<To: AMSAT BB <amsat-bb@?????.???>
<Subject: [amsat-bb] AO-85 report from the 2019-06-16 - 0028 UTC pass
<
<Hi,
<
<I made five QSOs on this 47 degree pass from FM05. I was using my
<Kenwood TM-V71 radio at 50 watts and an Alaskan Arrow II antenna with
<the last third boom section removed.
<
<I didn't hear the bird for the first couple minutes of the pass and
<couldn't get it to come on myself. Eventually it came on and I heard
<Clayton W5PFG not long after that so I assume he turned the
<transponder on. In the first half of the pass it was difficult to get
<a solid signal into the sat. Other stations had the same problems.
<Audio was sometimes really low, great other times, and distorted at
<times as well.
<
<The last part of the pass was not bad though. I was able to
<consistently get a signal into the bird, even at 10 or 5 watts. I had
<a conversation with Roy K3RLD about this as we were both having the
<same good luck. This reminded me of past AO-85 behavior where it is
<easier to get in in the last part of the pass. I was actually on top
<of a landfill park in my town so I had a perfect view of the horizon
<and was able to get in all the way to LOS, albeit with some picket
<fencing effects on the downlink.
<
<Stations contacted:
<
<W5PFG
<W5HRH
<N9XCO *
<N0RC
<K3RLD
<Also heard ???PML
<
<* This was Richard N9XCO's first sat QSO. He just finished setting up
<a IC-9700/G-5500/SatPC32 station
<
<One odd thing I noticed is at the end of the pass I believe I was at
<145.970 MHz, 10 KHz down from the center frequency of 145.980. It
<looked so weird I did a double take and doubted I was really at that
<frequency. I don't know if the bird was off frequency or if it was
<something on my end.
<
<My audio recording is here:
<
<https://www.dropbox.com/s/j1xduj3had9gicm/2019-06-16_0028_UTC_AO-
<85_KG4AKV_FM05.WAV?dl=0
<
<73, John Brier KG4AKV
<_______________________________________________
<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: 6
Date: Mon, 17 Jun 2019 07:31:43 -0500
From: Hasan al-Basri <hbasri.schiers6@?????.???>
To: Kenneth P Alexander <ve3hls@?????.???>
Cc: AMSAT -BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Fixed elevation - how many elements?
Message-ID:
<CAM4UQf3Qc1DbjKjeMF6xP4rXQa19dzpLajJ5=o=cmyuwkpDwcw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
10 dBi gain antennas have enough 3 dB beamwidth that you can fixed EL at 15
deg, and still have good horizon gain (where it is most needed), and only
see loss directly overhead for a 20 or 30 sec period (Might even be
shorter). See Bob Bruninga's posting about how this works, it is VERY
informative. Applies only to LEO birds.
I am about to use an EAntenna with 5 el on 2m, 8 el on 70cm, with specified
gain of 10 dBi
73, N0AN
Hasan
On Sun, Jun 16, 2019 at 12:19 PM Kenneth P Alexander via AMSAT-BB <
amsat-bb@?????.???> wrote:
> Hi Martin,
>
> I think you've analyzed your situation pretty well when it comes to numbers
> of elements, beamwidths, etc. A few thoughts:
> - if you can try a few satellite passes from around your property with a
> handheld yagi, like an Arrow just gain a little first hand experience to
> see what your minimum elevations are going to look like.
> - you might be surprised to find that some houses are more "transparent"
> to VHF/UHF signals than others. There are several ops here who regularly
> work satellites with portable antennas from inside their houses. Don't
> consider every obstacle to be impenetrable.
>
> With all that said, if I was in your position I'd go for a 3 or 4-element
> 2m yagi and I'd go to the extra trouble of getting crossed yagis so you can
> use circular polarization to reduce signal fading. For 70 cm the
> 7-elements on my Arrow handheld antenna has always been sufficient, and go
> for crossed yagis again. If you think the trees will really be a problem
> then go with 4 elements on 2m and a few extra on 70 cm, but realize that if
> you're buying commercial antennas you're stuck with what the sellers
> offer. This is about as much as I'd want to swing around with an
> inexpensive azimuth rotator (You didn't say what kind of rotator it was)
>
> Finally, my antenna situation at home was even more awful than yours. My
> back yard was smaller than my living room and it was surrounded by 3-storey
> townhouses on all sides. I decided to become a rover and it was the most
> adventure-packed 2 years of my life! I travelled all over eastern VE3 and
> western VE2 and activated just over 70 grids, many of which had never been
> activated before. Amsat ops are always looking for new activations and are
> very grateful to thos who have the chance to get out there and activate
> them.
>
> I hope this helps a little. You'll get plenty more replies and have lots
> to sort through soon!
>
> 73,
>
> Ken Alexander (VE3HLS)
> So Phisai, Thailand
> Blog: bueng-ken.com
>
>
> On Sun, Jun 16, 2019 at 2:44 PM Martin Cooper via AMSAT-BB <
> amsat-bb@?????.???> wrote:
>
> > I'm contemplating building a couple of yagis, possibly even crossed
> > ones, and putting them up at fixed elevation (i.e. az-only rotator).
> > What I'm unclear about is how many elements to consider.
> >
> > My location is really pretty dreadful for seeing sky. There's a big
> > hill to the NE that restricts me to above 40 degrees in that
> > direction. I'm in a single-storey house, with neighbouring two-storey
> > houses to the NW, SW, and S. In between all that, there are other
> > single-storey houses, and trees in most of the gaps between houses. I
> > can't afford to put up a tower (and it could never get above the hill
> > anyway), so I'm looking at not too much above my roofline.
> >
> > To at least get through the trees, I'd think more elements would be
> > better. But more elements narrows the beam, and at fixed elevation,
> > that, at some point, will restrict even further how much of the sky I
> > can play with.
> >
> > I'm looking for thoughts on how many elements would be recommended,
> > and how many would be too many, for a fixed elevation, both for VHF
> > and UHF. Ultimately, I'd like to be able to get on the linears, so not
> > limited to the FM sats. Any thoughts would be much appreciated.
> >
> > Thanks in advance.
> >
> > Martin.
> > KD6YAM
> > _______________________________________________
> > 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: 7
Date: Mon, 17 Jun 2019 08:53:24 -0400
From: Robert Bruninga <bruninga@????.???>
To: Hans BX2ABT <hans.bx2abt@???.?????.???>
Cc: AMSAT <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Falconsat-3 upload problem
Message-ID:
<CALdCfNLc4iEpvZfRvYzrc9CL5omLQRFBMKN09Dz9YgnpLD6iaw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
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@?????.???>
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 . 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@?????.???. 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: 8
Date: Mon, 17 Jun 2019 21:17:53 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: Robert Bruninga <bruninga@????.???>
Cc: AMSAT <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Falconsat-3 upload problem
Message-ID: <41975c4c-fbd9-4742-b62e-139f025b594c@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed
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@?????.???>> 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 . 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@?????.???>. 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: Mon, 17 Jun 2019 10:32:44 -0400
From: Robert Bruninga <bruninga@????.???>
To: Hans BX2ABT <hans.bx2abt@???.?????.???>
Cc: AMSAT <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Falconsat-3 upload problem
Message-ID:
<CALdCfNL-eFer94_2XvemSK4W7LsvP+obsnm2FFfXZ5x1+akxTg@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Its not the TXD on your end, but that there is none in the satellie So you
have to be receiving all the time, even while transmitting.
Again, this may not be the problem at your station at all. But I just
thought it is useful to repeat the info.
That is why many people do not see themselves on APRS via PFS3, because by
the time their rig goes into receive, after transmitting APRS, the digipeat
has already occured and they missed it.
Bob
On Mon, Jun 17, 2019 at 9:17 AM Hans BX2ABT <hans.bx2abt@???.?????.???>
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@?????.???> 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 . 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@?????.???. 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
>>
>
>
------------------------------
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 234
*****************************************
Read previous mail | Read next mail
| |
