February 2023 - pacsat-dev - mailman.amsat.org

Mailing lists were hung
by Burns Fisher (AMSAT) 04 Feb '23

04 Feb '23

The mailing lists were archiving but not actually re-sending mail between about 1000z Feb 1 till earlier today. That appears to include the bb as well. Matt just fixed it and will be looking for the root cause so you probably got a bunch of mail from early this morning. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Is there a pacsat meeting tonight?
by Burns Fisher (AMSAT) 04 Feb '23

04 Feb '23

No the mailing list was hung so we never got the invite till later. The mtg ID changes week to week so you probably tried an old one. On Sat, Feb 4, 2023 at 8:06 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I joined on Thursday but there was no meeting. Did the meeting move to > Fridays? > > 73 > Chris > > On Sat, Feb 4, 2023, 00:44 Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I have not seen an invite. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

2 1

Re: Is there a pacsat meeting tonight?
by Chris Thompson 04 Feb '23

04 Feb '23

I joined on Thursday but there was no meeting. Did the meeting move to Fridays? 73 Chris On Sat, Feb 4, 2023, 00:44 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I have not seen an invite. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Fwd: [AMSAT-BB] Possible way to alleviate Greencube congestion: Internet server queue manager integrated with UZ7HO Digipeater software
by Bob Stricklin 03 Feb '23

03 Feb '23

Here is a message John Brier spent a good deal of time thinking though. Its a different idea on how to use digital packets. Begin forwarded message: From: "Timokhov, Sasha via AMSAT-BB" <amsat-bb(a)amsat.org<mailto:amsat-bb@amsat.org>> Subject: [AMSAT-BB] Re: Possible way to alleviate Greencube congestion: Internet server queue manager integrated with UZ7HO Digipeater software Date: February 1, 2023 at 10:01:45 AM CST To: John Brier <johnbrier(a)gmail.com<mailto:johnbrier@gmail.com>> Cc: AMSAT BB <amsat-bb(a)amsat.org<mailto:amsat-bb@amsat.org>> Reply-To: "Timokhov, Sasha" <sasha.timokhov(a)student.tdsb.on.ca<mailto:sasha.timokhov@student.tdsb.on.ca>> Hey John! Cool idea! 73! VE3SVF On Wed, Feb 1, 2023 at 8:53 AM John Brier via AMSAT-BB <amsat-bb(a)amsat.org<mailto:amsat-bb@amsat.org>> wrote: Hi sat ops, Would it be possible/legal to add functionality to UZ7HO Digpeater software to enable a VOLUNTARY / opt-in feature where when you click Send, CQ etc. (to TX a packet), instead of immediately keying the radio, a TX request is sent to a central Internet server (to be created) that sorts requests in some sort of fair sequence and then one by one commands/allows the various requesters to actually TX their packet? The sequence could be sorted by time, i.e. whoever sent the request first gets in line first. It could be partially random to account for latency (whoever is closest to the server doesn't always go first). Additional functionality could be added to the Digpeater software, or a central website, to display the queue so you can see your place and watch the people in front of you send their packets and see yourself move up the queue. This would allow everyone to calm down, knowing their turn is coming. On the IO-117 side hopefully this would mean less long gaps with no packets digpeated/much higher rate of digipeats. Imagine if everyone used it: when busy, IO-117 would be digipeating practically non-stop with gaps to RX as short as a single transmission. The Digipeater software could give each operator a certain number of tries to get the packet digipeated (say 3) before putting them at the back of the queue again if they all fail to be digipeated. The Digipeater software could determine if they are successfully digipeated by checking the RX packets for its own message, and reporting back to the Internet server. The Internet server could even check SatNOGS to verify if the packet was digipeated (it seems telemetry is uploaded in real time). The Internet server software could even be on SatNOGS. You could also do something like WSJT-X and require everyone to have accurate NTP time and packets are sent at specific intervals, RX happens at specific intervals, but all in order, this way there isn't an issue with varied latencies between the server and the requesters. The sorting happens as fast as possible but the scheduling in the intervals is a bit delayed. You could program all sorts of sorting heuristics to make things fair or optimize for certain things. If a new station DX station comes on the digipeater and a pile up starts, maybe the Internet server can be enabled to see who is near their LOS and put them at the top of the queue, or just prioritize anyone near LOS. If a DX station goes out of IO-117 FP, requests to TX to it would not be allowed and the requester could be denied and told why. If stations have contacted each other before from the same grids maybe they could have lower priority. You could even let people complete whole QSOs quickly before moving to the next person in the queue if they are all calling the same DX station, if the DX station is also using the new feature and/or following a set QSO format/exchange. Another benefit of this is it helps low power stations as there is less need to run high power to compete. In the FCC rules at least, it is a requirement that you use the lowest power necessary to achieve the radio comms goal, so if this proposal is possible it is very much in the spirit of the rules and maybe even necessary. It seems a little ridiculous for everyone to be running as much power and gain as possible when I can get in easily with 5-7 watts and 10 elements when the bird is mostly over SA. Of course rovers without internet service can't use this, many people will never use this for various reasons, and they could just not enable the feature and use the Digipeater software as they do today, sending TX commands immediately. Adding this code and creating an Internet server would take a lot of work. I have no solution for that but maybe if UZ7HO can't do it an extension interface can be added to it and someone else can write an extension that communicates with the Internet server. Someone else could also make the Internet server. Or someone could write a new Digipeater software that has all this functionality. If any of this is possible/doable I think it could make IO-117 / GreenCube a lot more easy and fun to work. 73, John Brier KG4AKV P.S. Sorry this isn't more well thought out. I'm not a programmer and I'm just throwing out as many ideas as I can think of. Maybe some are possible. ----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org<https://url.emailprotection.link/?bWHOqmuFCpfOhnILToqf6ps3f0aWOOFhj2DUZrSti…>. 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. Acceptable Use and Privacy Policies available at https://www.amsat.org/about-amsat/<https://url.emailprotection.link/?bJ-dwWnUgqH9nPOKGILHrfZSs2w22pZXugJCxYz_D…> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org<https://url.emailprotection.link/?bxxCC5TuKmCFb1TRunmlCokCC1HV1MDXUW3I4GHLF…> To unsubscribe send an email to amsat-bb-leave(a)amsat.org<https://url.emailprotection.link/?bWHOqmuFCpfOhnILToqf6ps3f0aWOOFhj2DUZrSti…> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> ----------------------------------------------------------- Sent via AMSAT-BB(a)amsat.org<http://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. Acceptable Use and Privacy Policies available at https://www.amsat.org/about-amsat/ 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

1 0

Tonights meeting
by Bill 03 Feb '23

03 Feb '23

It looks like my invitation that I sent today did not go out for some reason. My apologies. Bill

1 0

Is there a pacsat meeting tonight?
by Burns Fisher (AMSAT) 03 Feb '23

03 Feb '23

I have not seen an invite. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Pacsat dev meeting 2-2-2023
by Bill 02 Feb '23

02 Feb '23

Pacsat dev meeting 2-2-2023 Thu, Feb 2, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/239406461 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3122 - One-touch: tel:+15713173122,,239406461# Access Code: 239-406-461 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0