Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/NS4RLXKUNLNOTYTIRZBFVV5IHHPNIIV3/
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/NS4RLXKUNLNOTYTIRZBFVV5IHHPNIIV3/", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/", "message_id": "CAH+ksJyrrUUc8af2cNK5o=2dnPUYHu=uR2cE+57Z9WeV7YkhCg@mail.gmail.com", "message_id_hash": "NS4RLXKUNLNOTYTIRZBFVV5IHHPNIIV3", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NS4RLXKUNLNOTYTIRZBFVV5IHHPNIIV3/", "sender": { "address": "sasha.timokhov (a) student.tdsb.on.ca", "mailman_id": "abf5d90949d949a3b0066448486cc6df", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/abf5d90949d949a3b0066448486cc6df/emails/" }, "sender_name": "Timokhov, Sasha", "subject": "[AMSAT-BB] Re: Possible way to alleviate Greencube congestion: Internet server queue manager integrated with UZ7HO Digipeater software", "date": "2023-02-01T16:00:42Z", "parent": null, "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Hey John!\n\nCool idea!\n\n73!\n\nVE3SVF\n\nOn Wed, Feb 1, 2023 at 8:53 AM John Brier via AMSAT-BB <[email protected]>\nwrote:\n\n> Hi sat ops,\n>\n> Would it be possible/legal to add functionality to UZ7HO Digpeater\n> software to enable a VOLUNTARY / opt-in feature where when you click\n> Send, CQ etc. (to TX a packet), instead of immediately keying the\n> radio, a TX request is sent to a central Internet server (to be\n> created) that sorts requests in some sort of fair sequence and then\n> one by one commands/allows the various requesters to actually TX their\n> packet?\n>\n> The sequence could be sorted by time, i.e. whoever sent the request\n> first gets in line first. It could be partially random to account for\n> latency (whoever is closest to the server doesn't always go first).\n>\n> Additional functionality could be added to the Digpeater software, or\n> a central website, to display the queue so you can see your place and\n> watch the people in front of you send their packets and see yourself\n> move up the queue. This would allow everyone to calm down, knowing\n> their turn is coming. On the IO-117 side hopefully this would mean\n> less long gaps with no packets digpeated/much higher rate of\n> digipeats. Imagine if everyone used it: when busy, IO-117 would be\n> digipeating practically non-stop with gaps to RX as short as a single\n> transmission.\n>\n> The Digipeater software could give each operator a certain number of\n> tries to get the packet digipeated (say 3) before putting them at the\n> back of the queue again if they all fail to be digipeated. The\n> Digipeater software could determine if they are successfully\n> digipeated by checking the RX packets for its own message, and\n> reporting back to the Internet server. The Internet server could even\n> check SatNOGS to verify if the packet was digipeated (it seems\n> telemetry is uploaded in real time). The Internet server software\n> could even be on SatNOGS.\n>\n> You could also do something like WSJT-X and require everyone to have\n> accurate NTP time and packets are sent at specific intervals, RX\n> happens at specific intervals, but all in order, this way there isn't\n> an issue with varied latencies between the server and the requesters.\n> The sorting happens as fast as possible but the scheduling in the\n> intervals is a bit delayed.\n>\n> You could program all sorts of sorting heuristics to make things fair\n> or optimize for certain things. If a new station DX station comes on\n> the digipeater and a pile up starts, maybe the Internet server can be\n> enabled to see who is near their LOS and put them at the top of the\n> queue, or just prioritize anyone near LOS. If a DX station goes out of\n> IO-117 FP, requests to TX to it would not be allowed and the requester\n> could be denied and told why. If stations have contacted each other\n> before from the same grids maybe they could have lower priority.\n>\n> You could even let people complete whole QSOs quickly before moving to\n> the next person in the queue if they are all calling the same DX\n> station, if the DX station is also using the new feature and/or\n> following a set QSO format/exchange.\n>\n> Another benefit of this is it helps low power stations as there is\n> less need to run high power to compete. In the FCC rules at least, it\n> is a requirement that you use the lowest power necessary to achieve\n> the radio comms goal, so if this proposal is possible it is very much\n> in the spirit of the rules and maybe even necessary. It seems a little\n> ridiculous for everyone to be running as much power and gain as\n> possible when I can get in easily with 5-7 watts and 10 elements when\n> the bird is mostly over SA.\n>\n> Of course rovers without internet service can't use this, many people\n> will never use this for various reasons, and they could just not\n> enable the feature and use the Digipeater software as they do today,\n> sending TX commands immediately.\n>\n> Adding this code and creating an Internet server would take a lot of\n> work. I have no solution for that but maybe if UZ7HO can't do it an\n> extension interface can be added to it and someone else can write an\n> extension that communicates with the Internet server. Someone else\n> could also make the Internet server. Or someone could write a new\n> Digipeater software that has all this functionality.\n>\n> If any of this is possible/doable I think it could make IO-117 /\n> GreenCube a lot more easy and fun to work.\n>\n> 73, John Brier KG4AKV\n>\n> P.S. Sorry this isn't more well thought out. I'm not a programmer and\n> I'm just throwing out as many ideas as I can think of. Maybe some are\n> possible.\n>\n> -----------------------------------------------------------\n>\n> Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum available\n> to all interested persons worldwide without requiring membership. Opinions\n> expressed\n> are solely those of the author, and do not reflect the official views of\n> AMSAT-NA.\n> Acceptable Use and Privacy Policies available at\n> https://www.amsat.org/about-amsat/\n>\n> View archives of this mailing list at\n> https://mailman.amsat.org/hyperkitty/list/[email protected]\n> To unsubscribe send an email to amsat-bb-leave(a)amsat.org\n> Manage all of your AMSAT-NA mailing list preferences at\n> https://mailman.amsat.org\n>\n\n\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/NS4RLXKUNLNOTYTIRZBFVV5IHHPNIIV3/", "counter": 2, "name": "attachment.html", "content_type": "text/html", "encoding": "utf-8", "size": 6224, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/NS4RLXKUNLNOTYTIRZBFVV5IHHPNIIV3/attachment/2/attachment.html" } ] }