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

Re: PACSAT Operating Instructions
by Burns Fisher (AMSAT) 09 May '23

09 May '23

Ok, thanks. I saw a video about hooking up DireWolf to a BaoFeng radio, and I have exactly that radio. I'm not sure about the PTT though. I could also use my Kenwood D72--it does APRS, so it may even have a builtin TNC for other purposes. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 8:15 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Yes, DireWolf to a sound card and then to a radio. You could test receive > with an sdr as long as you can get the audio into DireWolf. > > I can provide details on DireWolf setup tomorrow. > > 73 > Chris > > On Mon, May 8, 2023, 17:06 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: > >> I assume you need to connect DireWolf through a sound card to a radio >> too. Or am I not following somthing? Your software does not do SDR like >> FoxTelem, right? >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Mon, May 8, 2023 at 1:41 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> If you have received a PACSAT Booster Board from Jim, then here are some >>> instructions for testing/using it. >>> >>> >>> First make sure you have followed Burns instructions to install the IDE >>> and flash the launchpad. You know this has worked when you have the >>> console up and can type commands. When it tells you to type a command in >>> these instructions, it means on the PACSAT Console. You can type help to >>> show a list of commands. >>> >>> >>> >>> I suggest installing DireWolf on the same or another computer. You need >>> to set it up to operate in full duplex at 9600bps. Initially you can use >>> DireWolf to see you are receiving packets. Then you need to connect the >>> ground station software by telling Pac Sat Ground that the TNC is connected >>> to TCP port 8001, using the File > Settings screen. >>> >>> >>> >>> In the console type: >>> >>> *send pb status * >>> >>> >>> >>> This will transmit a packet and it should say PB Empty in DireWolf. >>> >>> >>> >>> Then type: >>> >>> *ls * >>> >>> >>> >>> This should show there are no files on the sat. If this does not work >>> then type: >>> >>> *unmount fs* >>> >>> *format fs* >>> >>> *mount fs * >>> >>> >>> >>> In the console type: >>> >>> *make psf* >>> >>> >>> This will create a set of test files >>> >>> >>> >>> Type: >>> >>> *ls * >>> >>> >>> >>> To list them. We now need to set the time before we load them into the >>> directory. We dont have a real time clock so it needs to be set manually. >>> >>> >>> >>> Look up the current Unix time on the web. I use >>> https://www.unixtimestamp.com/ >>> >>> Type: >>> >>> *set unix time <value> * >>> >>> >>> >>> Then you can type: >>> >>> *load dir * >>> >>> >>> >>> This will load the files into the directory and set their upload time. >>> In the future PACSAT will load the directory at boot. Probably once we >>> have a real time clock in place. >>> >>> Type : >>> >>> *list dir * >>> >>> >>> >>> This will list all the files in the directory. Now when you reset the >>> satellite the files will still be in the file system with the correct >>> upload time, but the directory will be empty. You can type: >>> >>> *load dir * >>> >>> >>> >>> Without having to set the Unix Time, and it will load the files and >>> remember their upload time. >>> >>> >>> >>> In the Pacsat ground station you can press the DIR button if the PB is >>> available, i.e. you are not already on the PB. If it thinks you are on the >>> PB then you can type this on the console: >>> >>> *send pb status * >>> >>> >>> >>> If you press the DIR button it should request the directory and >>> download all the headers. If you interrupt the download then subsequent >>> requests will ask for the holes in the directory. >>> >>> >>> >>> You can press the FILE button to download a file . Either type the file >>> number you want in the box or click on the file in the directory to >>> populate the box. You can also give a file a download priority by pressing >>> numbers 1-9. See the manual for Details. >>> >>> >>> >>> Feel free to ask any questions. >>> >>> >>> 73 >>> >>> Chris >>> >>> -- >>> Chris E. Thompson >>> chrisethompson(a)gmail.com >>> g0kla(a)arrl.net >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>> View archives of this mailing list at >>> https://mailman.amsat.org/hyperkitty/list/[email protected] >>> 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/[email protected] > 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

Re: PACSAT Operating Instructions
by Burns Fisher (AMSAT) 09 May '23

09 May '23

I assume you need to connect DireWolf through a sound card to a radio too. Or am I not following somthing? Your software does not do SDR like FoxTelem, right? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 1:41 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > If you have received a PACSAT Booster Board from Jim, then here are some > instructions for testing/using it. > > > First make sure you have followed Burns instructions to install the IDE > and flash the launchpad. You know this has worked when you have the > console up and can type commands. When it tells you to type a command in > these instructions, it means on the PACSAT Console. You can type help to > show a list of commands. > > > > I suggest installing DireWolf on the same or another computer. You need > to set it up to operate in full duplex at 9600bps. Initially you can use > DireWolf to see you are receiving packets. Then you need to connect the > ground station software by telling Pac Sat Ground that the TNC is connected > to TCP port 8001, using the File > Settings screen. > > > > In the console type: > > *send pb status * > > > > This will transmit a packet and it should say PB Empty in DireWolf. > > > > Then type: > > *ls * > > > > This should show there are no files on the sat. If this does not work > then type: > > *unmount fs* > > *format fs* > > *mount fs * > > > > In the console type: > > *make psf* > > > This will create a set of test files > > > > Type: > > *ls * > > > > To list them. We now need to set the time before we load them into the > directory. We dont have a real time clock so it needs to be set manually. > > > > Look up the current Unix time on the web. I use > https://www.unixtimestamp.com/ > > Type: > > *set unix time <value> * > > > > Then you can type: > > *load dir * > > > > This will load the files into the directory and set their upload time. > In the future PACSAT will load the directory at boot. Probably once we > have a real time clock in place. > > Type : > > *list dir * > > > > This will list all the files in the directory. Now when you reset the > satellite the files will still be in the file system with the correct > upload time, but the directory will be empty. You can type: > > *load dir * > > > > Without having to set the Unix Time, and it will load the files and > remember their upload time. > > > > In the Pacsat ground station you can press the DIR button if the PB is > available, i.e. you are not already on the PB. If it thinks you are on the > PB then you can type this on the console: > > *send pb status * > > > > If you press the DIR button it should request the directory and download > all the headers. If you interrupt the download then subsequent requests > will ask for the holes in the directory. > > > > You can press the FILE button to download a file . Either type the file > number you want in the box or click on the file in the directory to > populate the box. You can also give a file a download priority by pressing > numbers 1-9. See the manual for Details. > > > > Feel free to ask any questions. > > > 73 > > Chris > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > 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 >

2 1

PACSAT Operating Instructions
by Chris Thompson 08 May '23

08 May '23

If you have received a PACSAT Booster Board from Jim, then here are some instructions for testing/using it. First make sure you have followed Burns instructions to install the IDE and flash the launchpad. You know this has worked when you have the console up and can type commands. When it tells you to type a command in these instructions, it means on the PACSAT Console. You can type help to show a list of commands. I suggest installing DireWolf on the same or another computer. You need to set it up to operate in full duplex at 9600bps. Initially you can use DireWolf to see you are receiving packets. Then you need to connect the ground station software by telling Pac Sat Ground that the TNC is connected to TCP port 8001, using the File > Settings screen. In the console type: *send pb status * This will transmit a packet and it should say PB Empty in DireWolf. Then type: *ls * This should show there are no files on the sat. If this does not work then type: *unmount fs* *format fs* *mount fs * In the console type: *make psf* This will create a set of test files Type: *ls * To list them. We now need to set the time before we load them into the directory. We dont have a real time clock so it needs to be set manually. Look up the current Unix time on the web. I use https://www.unixtimestamp.com/ Type: *set unix time <value> * Then you can type: *load dir * This will load the files into the directory and set their upload time. In the future PACSAT will load the directory at boot. Probably once we have a real time clock in place. Type : *list dir * This will list all the files in the directory. Now when you reset the satellite the files will still be in the file system with the correct upload time, but the directory will be empty. You can type: *load dir * Without having to set the Unix Time, and it will load the files and remember their upload time. In the Pacsat ground station you can press the DIR button if the PB is available, i.e. you are not already on the PB. If it thinks you are on the PB then you can type this on the console: *send pb status * If you press the DIR button it should request the directory and download all the headers. If you interrupt the download then subsequent requests will ask for the holes in the directory. You can press the FILE button to download a file . Either type the file number you want in the box or click on the file in the directory to populate the box. You can also give a file a download priority by pressing numbers 1-9. See the manual for Details. Feel free to ask any questions. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

RF Components / Power Requirements
by Jonathan Brandenburg 05 May '23

05 May '23

As discussed last night, I've completed some preliminary work on the radiation tolerant circuitry. That does bring up one question... Bob, do you already have circuitry for watchdog protection and current limiting in the schematic / on the board? Or does that still have to be shoehorned into the board? To refine the design I've prototyped, I need to know the anticipated/budgeted power requirements. The part I'm looking at for current limiting, MAX4995AAUT+T, can handle 600mA. If we derate that a bit (are we using 50%?) we can handle 300mA. That's quite a lot so I don't expect an issue with hitting max current except possibly the power amplifier and it's not clear to me if the power amplifier needs to be protected against latchup anyway. In our previous designs, we have a separate current limiter for each AX5043, the power amplifier, and the TMS570. (I think the LNAs are bundled with the AX5043 for the purposes of power limits and peripheral power requirements for TXCOs and such ). I don't think we'll need that many here but we'll probably need one for each voltage rail. Do we have answers to some of the following questions or is some of still being determined: 1. What power output level are we using on the AX5043? Max current at 16dbm TX is 48 mA plus 6.5 mA for VHF receiver or 9.5 mA for UHF receive. 2. What LNAs are we using? Does each AX5043 have its own LNA? (I haven't looked for a schematic so tell me to go find it myself if it's in Github.) 3. What power amplifier are we using and what is the power output? (I still need to double-check a need for current limiter here.) 4. Do we have a characterization for the TMS570 configuration to know which subsystems will be active and thus have a power budget for the TMS570? Thanks a lot! Jonathan -- Jonathan Brandenburg, KF5IDY

1 0

Re: AX.25 code
by Chris Thompson 05 May '23

05 May '23

Thanks Corey. I will review. I'm sure it will be helpful. Especially the errors you have noted. 73 Chris On Thu, May 4, 2023, 21:17 Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > My code for AX.25 is part of the gensio library. The individual files are > at: > > https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25.c > > https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25_addr.c > > The gensio library is a whole framework for all kinds of stream and > packet I/O. But you should be able to pull out the middle of the file > that has the state machine, pretty much unmodified, and use it. > > One thing that might be more interesting is I documented a bunch of > bugs in the spec in the comments at the top of the gensio_ax25.c file. > > Anyway, it's available if you want it. I'd be willing to split out > the state machine if you wanted something that was individually > maintainable. > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > 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

AX.25 code
by Corey Minyard 05 May '23

05 May '23

My code for AX.25 is part of the gensio library. The individual files are at: https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25.c https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25_addr.c The gensio library is a whole framework for all kinds of stream and packet I/O. But you should be able to pull out the middle of the file that has the state machine, pretty much unmodified, and use it. One thing that might be more interesting is I documented a bunch of bugs in the spec in the comments at the top of the gensio_ax25.c file. Anyway, it's available if you want it. I'd be willing to split out the state machine if you wanted something that was individually maintainable. -corey

1 0

Pacsat dev mtg 5/4/2023
by Bill 04 May '23

04 May '23

Thu, May 4, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/160711565 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (646) 749-3122 - One-touch: tel:+16467493122,,160711565# Access Code: 160-711-565 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 160 711 565 Or dial directly: 160711565(a)67.217.95.2 or 67.217.95.2##160711565 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Which TMS570?
by Bob Stricklin 04 May '23

04 May '23

Jonathan, The key part number is the one I have given you. This defines the 144 pin package and the definition of each pin. The QQ! on the end are: 1st Q - Temp range -40 to 125C Q1 - Automotive grade There can be a R on the end also which would bean tape and reel. No R would mead a flat pack. We could use either one. For prototype builds we could use other grades. For flight hardware we would like to have the best grade. Since a lot of TI volume is in automotive that grade which is probably the best we would want to pay for is not so expensive unless the price starts ratcheting up due to shortages. Bob > On May 3, 2023, at 9:27 PM, Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > I should point out the BoM I have is from the most recent board assembly but it was emailed directly from Zach so I don't know if it was posted to Subversion. (It is now as Cameron has been tracking down the latest schematics and layouts for the RT-IHU and has ensured they're posted to Subversion.) > > Bob, you're listing a slightly different part number... Is that significant? Could that have been from a previous BoM? This is confusing to me :( > > Jonathan > > On 5/3/2023 9:23 PM, Jonathan Brandenburg via pacsat-dev wrote: >> >> The RT-IHU BoM is showing TMS5700914APGEQQ1 for the complete part number... There is a good chance Zach Metzinger has a small supply of those but it's not clear to me how those are allocated. Perhaps reaching out to Zach is appropriate, especially for the initial boards. >> >> Thoughts? >> >> Jonathan >> >> On 5/3/2023 9:18 PM, Bob Stricklin via pacsat-dev wrote: >>> Jonathan, >>> >>> The chip number I am working with is: >>> >>> TMS570LS0914PGE >>> >>> This is the same part used on other AMSAT designs. I had looked into ordering a few also and noticed the long lead-time. >>> I would like to have two or three of these myself. >>> >>> There is a possibility someone else has a few left over from earlier builds. >>> >>> I would not be surprised to see the delivery keep getting pushed out. If China invades Taiwan we may never see them again. I don’t think a lot of Americans realize the impact this will have. >>> >>> Bob >>> >>> >>>> On May 3, 2023, at 5:16 PM, Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org> wrote: >>>> >>>> Howdy! >>>> >>>> Which TMS570 are you currently planning to use on the PACSAT board? I ask because I'd like to get an order in as stock is still sporadic. >>>> >>>> In particular, the RT-IHU uses the TMS5700914APGEQQ1, which I have ordered from Mouser but delivery is currently scheduled for Jan 2024. Digikey lists Nov 2023 for delivery at this time. >>>> >>>> The Launchpad uses a TMS570LS1224 device with one part, TMS5701224CPGEQQ1 showing a July 2023 delivery from Mouser and Digikey showing January 2024. >>>> >>>> I have admittedly done no research on the capabilities offered by these parts but I'm happy to order when we know what PACSAT will fly. >>>> >>>> Jonathan >>>> >>>> -- >>>> jbrandenburg(a)amsat.org >>>> >>>> >>>> ----------------------------------------------------------- >>>> >>>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>>> View archives of this mailing list at https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… >>>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>>> Manage all of your AMSAT-NA mailing list preferences at https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi… >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>> View archives of this mailing list at https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… >>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi… >> > -- > jbrandenburg(a)amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…

1 0

Re: Which TMS570?
by Jonathan Brandenburg 04 May '23

04 May '23

I should point out the BoM I have is from the most recent board assembly but it was emailed directly from Zach so I don't know if it was posted to Subversion. (It is now as Cameron has been tracking down the latest schematics and layouts for the RT-IHU and has ensured they're posted to Subversion.) Bob, you're listing a slightly different part number... Is that significant? Could that have been from a previous BoM? This is confusing to me :( Jonathan On 5/3/2023 9:23 PM, Jonathan Brandenburg via pacsat-dev wrote: > > The RT-IHU BoM is showing TMS5700914APGEQQ1 for the complete part > number... There is a good chance Zach Metzinger has a small supply of > those but it's not clear to me how those are allocated. Perhaps > reaching out to Zach is appropriate, especially for the initial boards. > > Thoughts? > > Jonathan > > On 5/3/2023 9:18 PM, Bob Stricklin via pacsat-dev wrote: >> Jonathan, >> >> The chip number I am working with is: >> >> TMS570LS0914PGE >> >> This is the same part used on other AMSAT designs. I had looked into >> ordering a few also and noticed the long lead-time. >> I would like to have two or three of these myself. >> >> There is a possibility someone else has a few left over from earlier >> builds. >> >> I would not be surprised to see the delivery keep getting pushed out. >> If China invades Taiwan we may never see them again. I don’t think a >> lot of Americans realize the impact this will have. >> >> Bob >> >> >>> On May 3, 2023, at 5:16 PM, Jonathan Brandenburg via pacsat-dev >>> <pacsat-dev(a)amsat.org> wrote: >>> >>> Howdy! >>> >>> Which TMS570 are you currently planning to use on the PACSAT board? >>> I ask because I'd like to get an order in as stock is still sporadic. >>> >>> In particular, the RT-IHU uses the TMS5700914APGEQQ1, which I have >>> ordered from Mouser but delivery is currently scheduled for Jan >>> 2024. Digikey lists Nov 2023 for delivery at this time. >>> >>> The Launchpad uses a TMS570LS1224 device with one part, >>> TMS5701224CPGEQQ1 showing a July 2023 delivery from Mouser and >>> Digikey showing January 2024. >>> >>> I have admittedly done no research on the capabilities offered by >>> these parts but I'm happy to order when we know what PACSAT will fly. >>> >>> Jonathan >>> >>> -- >>> jbrandenburg(a)amsat.org >>> >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>> View archives of this mailing list at >>> https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… >>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi… >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> 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 > -- jbrandenburg(a)amsat.org

1 0

Re: Which TMS570?
by Jonathan Brandenburg 04 May '23

04 May '23

The RT-IHU BoM is showing TMS5700914APGEQQ1 for the complete part number... There is a good chance Zach Metzinger has a small supply of those but it's not clear to me how those are allocated. Perhaps reaching out to Zach is appropriate, especially for the initial boards. Thoughts? Jonathan On 5/3/2023 9:18 PM, Bob Stricklin via pacsat-dev wrote: > Jonathan, > > The chip number I am working with is: > > TMS570LS0914PGE > > This is the same part used on other AMSAT designs. I had looked into ordering a few also and noticed the long lead-time. > I would like to have two or three of these myself. > > There is a possibility someone else has a few left over from earlier builds. > > I would not be surprised to see the delivery keep getting pushed out. If China invades Taiwan we may never see them again. I don’t think a lot of Americans realize the impact this will have. > > Bob > > >> On May 3, 2023, at 5:16 PM, Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org> wrote: >> >> Howdy! >> >> Which TMS570 are you currently planning to use on the PACSAT board? I ask because I'd like to get an order in as stock is still sporadic. >> >> In particular, the RT-IHU uses the TMS5700914APGEQQ1, which I have ordered from Mouser but delivery is currently scheduled for Jan 2024. Digikey lists Nov 2023 for delivery at this time. >> >> The Launchpad uses a TMS570LS1224 device with one part, TMS5701224CPGEQQ1 showing a July 2023 delivery from Mouser and Digikey showing January 2024. >> >> I have admittedly done no research on the capabilities offered by these parts but I'm happy to order when we know what PACSAT will fly. >> >> Jonathan >> >> -- >> jbrandenburg(a)amsat.org >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi… > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > 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 -- jbrandenburg(a)amsat.org

1 0