[amsat-bb] Falconsat-3 upload problem

Mark L. Hammond marklhammond at gmail.com
Tue Jun 18 13:45:22 UTC 2019 

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:amsat-bb at amsat.org>amsat-bb at amsat.org> 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:amsat-bb at amsat.org>amsat-bb at amsat.org <mailto:amsat-bb at amsat.org>> 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 <mailto:AMSAT-BB at amsat.org>AMSAT-BB at amsat.org <mailto:AMSAT-BB at amsat.org>. AMSAT-NA
>>>Â  Â  Â makes this open forum available
>>>Â  Â  Â to all interested persons worldwide without requiring membership.
>>>Â  Â  Â Opinions expressed
>>>Â  Â  Â are solely those of the author, and do not reflect the official
>>>Â  Â  Â views of AMSAT-NA.
>>>Â  Â  Â Not an AMSAT-NA member? Join now to support the amateur satellite
>>>Â  Â  Â program!
>>>Â  Â  Â Subscription settings: <https://www.amsat.org/mailman/listinfo/amsat-bb>https://www.amsat.org/mailman/listinfo/amsat-bb
>>>
>>
>>_______________________________________________
>>Sent via <mailto:AMSAT-BB at amsat.org>AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
>>to all interested persons worldwide without requiring membership. Opinions expressed
>>are solely those of the author, and do not reflect the official views of AMSAT-NA.
>>Not an AMSAT-NA member? Join now to support the amateur satellite program!
>>Subscription settings: <https://www.amsat.org/mailman/listinfo/amsat-bb>https://www.amsat.org/mailman/listinfo/amsat-bb
>>
>>
>>
>>-- 
>>Mark L. Hammond [N8MH]

More information about the AMSAT-BB mailing list