I have never actually used Falconsat for APRS except for a test a few years ago. And have never used its BBS. So I need you to clarify some things for me as to how it looks to an end user...
I was wondering how Falconsat-3 prioritizes APRS vs. BBS traffic? It seems as though APRS might take a backseat to BBS traffic due to the high volume of stations accessing the BBS. That assumes that the system can't handle more than one process at a time or that the BBS is given higher priority.
It doesnt prioritize, it just digipeats what it hears. How do you measure APRS success? Presumably, getting a successful digipeat once a pass should be sufficient for remote stations "getting in" and being logged heard in the APRS-IS (I call this beacon modde).. Of course it takes a higher success rate if one is trying to do a live APRS message contact with another operator.
Ground station transmissions are relatively short at 9600 baud so I don't believe packet collisions are keeping APRS traffic from getting through. I have no problem accessing the BBS, but APRS access seems restricted even when the beacon set to 30 second intervals.
So what is your observed degree of "restricted"? 90%?, 50%? 10%? per packet transmitted (for live messages)? Or success "per pass" for :beacon mode"? Remember, that when accessing the BBS mode, there is an automatic retry involved, whereas for APRS a missed packet is just missed.'
Any thoughts...Tony -K2MO
Bob, Wb4APR
Sent via AMSAT-BB(a)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!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org