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 <[email protected] mailto:[email protected]> 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 [email protected] <mailto:[email protected]>. 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

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 [email protected] 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 <[email protected] mailto:[email protected]> 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 [email protected] <mailto:[email protected]>. 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 [email protected]. 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

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 <mailto:[email protected][email protected]> 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 <mailto:[email protected][email protected] mailto:[email protected]> 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-3http://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 mailto:[email protected][email protected] mailto:[email protected]. 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-bbhttps://www.amsat.org/mailman/listinfo/amsat-bb

---

Sent via mailto:[email protected][email protected]. 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-bbhttps://www.amsat.org/mailman/listinfo/amsat-bb

-- Mark L. Hammond [N8MH]