- pacsat-dev - mailman.amsat.org

Re: Latchup Protection and Watchdog Parts
by Burns Fisher (AMSAT) 24 Jan '23

24 Jan '23

Not really my forté but I’d worry that a higher current load switch for two devices would allow a higher current due to a SEU on a single device. Too much current and device fails before the load switch cuts it off? On Wed, Jan 25, 2023 at 11:37 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > On 1/19/23 17:40, Rich Gopstein via pacsat-dev wrote: > > Burns might remember the details (or Zach certainly would), but one of > > those parts was undersized for the RT-IHU and would cut out when we > > were transmitting with the ax5043. I think we had to back down the > > xmit power in order for the device not to reset. > > > > > It didn't take a whole lot of research for me to figure this one out. > The FPF2001 used on the Fox boards has a fixed current limit of 50mA. I > can see that could be sufficient for the Fox IHU since it uses a low > power processor and doesn't have transceivers or the power amplifier. > The direct replacement part for the FPF2001 is the TI TPS22942 and it > appears to be pin compatible with a fixed limit of 100mA. Would a 100mA > be a problem on Fox? I wouldn't think it would cause failure in the 10ms > it takes to blank the current but I make that statement without any real > basis. Perhaps the 40mA limit of the TI TPS22942 would be sufficient. > > Anyway, back to PACSAT... > > With the higher current capacity of the MAX4995, adjustable between 0 > and 600 mA, it could be the better choice than the fixed TI TPS22942. > I'm not aware of flight experience with either so I tend to look to the > MAX4995 with the adjustable and higher current limits. With this > decision and looking at the approach employed on the RT-IHU I could see > the following: > > 1 - The TMS570 and associated circuitry get their own MAX4995. As a > first order pass contained in Bob Stricklin's spreadsheet the current > requirement is 458.3mA, within the MAX4995's capabilities. If we want to > further "derate" we could put the TMS570 on one MAX4995 and have a > second MAX4995 for the peripherals. > > 2 - All five AX5043's require 100mA. Would we want to have 2 of the > AX5043's on one MAX4995 and the remaining AX5043's on the other MAX4995 > in case one MAX4995 fails prematurely? The value of this would depend on > all the AX5043's being equivalent in function (i.e., all could be used > for command and/or telemetry). This only takes care of this particular > failure mode and still leaves a lot of other failure modes in which an > early MAX4995 death would leave the system INOP so there may be limited > value in using two MAX4995's for the AX5043's. > > 3 - Finally, the amplifier/pre-amp is an additional 415mA. Again, if we > want to "derate" we could put the power amp on it's own MAX4995. > > > It looks like we need a minimum of 3 MAX4995's and a possible max of 6 > MAX4995's. (With further analysis, we might need one more to split the > 1.2V and 3.3V power lines to the TMS570.) The MAX4995 are small chips so > don't require a lot of real estate. We can discuss the risk vs reward of > using more MAX4995's at some point. > > I welcome comments > > Jonathan > > > -- > Jonathan Brandenburg > Radio Amateur Satellite Corporation > 1-214-213-1066 > > > ----------------------------------------------------------- > > 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: Latchup Protection and Watchdog Parts
by Jonathan Brandenburg 24 Jan '23

24 Jan '23

On 1/19/23 17:40, Rich Gopstein via pacsat-dev wrote: > Burns might remember the details (or Zach certainly would), but one of > those parts was undersized for the RT-IHU and would cut out when we > were transmitting with the ax5043. I think we had to back down the > xmit power in order for the device not to reset. > > It didn't take a whole lot of research for me to figure this one out. The FPF2001 used on the Fox boards has a fixed current limit of 50mA. I can see that could be sufficient for the Fox IHU since it uses a low power processor and doesn't have transceivers or the power amplifier. The direct replacement part for the FPF2001 is the TI TPS22942 and it appears to be pin compatible with a fixed limit of 100mA. Would a 100mA be a problem on Fox? I wouldn't think it would cause failure in the 10ms it takes to blank the current but I make that statement without any real basis. Perhaps the 40mA limit of the TI TPS22942 would be sufficient. Anyway, back to PACSAT... With the higher current capacity of the MAX4995, adjustable between 0 and 600 mA, it could be the better choice than the fixed TI TPS22942. I'm not aware of flight experience with either so I tend to look to the MAX4995 with the adjustable and higher current limits. With this decision and looking at the approach employed on the RT-IHU I could see the following: 1 - The TMS570 and associated circuitry get their own MAX4995. As a first order pass contained in Bob Stricklin's spreadsheet the current requirement is 458.3mA, within the MAX4995's capabilities. If we want to further "derate" we could put the TMS570 on one MAX4995 and have a second MAX4995 for the peripherals. 2 - All five AX5043's require 100mA. Would we want to have 2 of the AX5043's on one MAX4995 and the remaining AX5043's on the other MAX4995 in case one MAX4995 fails prematurely? The value of this would depend on all the AX5043's being equivalent in function (i.e., all could be used for command and/or telemetry). This only takes care of this particular failure mode and still leaves a lot of other failure modes in which an early MAX4995 death would leave the system INOP so there may be limited value in using two MAX4995's for the AX5043's. 3 - Finally, the amplifier/pre-amp is an additional 415mA. Again, if we want to "derate" we could put the power amp on it's own MAX4995. It looks like we need a minimum of 3 MAX4995's and a possible max of 6 MAX4995's. (With further analysis, we might need one more to split the 1.2V and 3.3V power lines to the TMS570.) The MAX4995 are small chips so don't require a lot of real estate. We can discuss the risk vs reward of using more MAX4995's at some point. I welcome comments Jonathan -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

PACSAT - AO-16
by Jim McCullers 23 Jan '23

23 Jan '23

At our development meeting last Thursday night one of the discussed items were the uplink frequencies of the original PACSAT. Curiosity over the weekend lead to a bit of online research that produced a few QST articles from the time period revealing details on the original PACSAT. PACSAT was AO-16 launched 33 years ago on January 22, 1990 along with an almost twin LUSAT (OSCAR-19) built by AMSAT Argentina. They were launched into sun synchronous orbit from the ESA facility in French Guiana with an altitude of 800km. Both were a new generation of Microsats measuring 230x230x213mm. AO-16 received on 2-meters at 145.9, 145.92, 145.94 and 145.96 mhz and transmitted on 437.050 with 4 watts maximum. LUSAT received on 2-meters at 145.84, 145.86, 145.88 and 145.90 mhz and transmitted on 437.125 with 4 watts maximum with a backup transmitter at 437.150. The frequencies vary by article probably reflecting changing configurations and the above were taken from a post launch article. Power output was variable by command and on 70cm achieved 65% efficiency. Uplink was FM, 1200 BPS Manchester encoded FSK and downlink was 1200 bps RC-BPSK SSB. Storage space was 4mb RAM. Interestingly, one QST article it list the designers of the command module and one call is familiar, N5BRG. All questions are now to you Bob! 73 Jim McCullers WA4CWI

1 0

Re: Latchup Protection and Watchdog Parts
by Rich Gopstein 20 Jan '23

20 Jan '23

Good question... Maybe it was just during development you need to disable it in order to successfully flash new code since nothing would be resetting the wd? I know on my board, the jumper is always in place so I don't know that we've tested the hw wd. Btw, the tms570 has a software watchdog which we have code for and we have tested. I also vaguely recall a conversation about the timing of the hw wd. I don't remember if it was the wd on the 1.1 board or the 1.2 board, but Zach had proposed a chip with a maximum timeout of something pretty short - well under a second. I was concerned that if something went south, the wd chip would continuously power cycle the processor multiple times a second. These conversations were from a while ago and I likely have the details wrong. On Fri, Jan 20, 2023, 8:18 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This I didn't know! Does anybody on the list know why the hardware > watchdog wasn't working as expected on the RT-IHU? > > Jonathan > On 1/19/23 17:43, Rich Gopstein wrote: > > And - as long as I'm thinking about it, we had to disable the hardware > watchdog on the RT-IHU to get it to run. I don't recall if that changed, > but if you get some RT-IHU boards, you might need to jumper the hardware WD > disable. > > Rich > > > On Thu, Jan 19, 2023 at 6:40 PM Rich Gopstein via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Burns might remember the details (or Zach certainly would), but one of >> those parts was undersized for the RT-IHU and would cut out when we were >> transmitting with the ax5043. I think we had to back down the xmit power >> in order for the device not to reset. >> >> Rich >> >> >> On Thu, Jan 19, 2023 at 5:46 PM Jonathan Brandenburg via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> In last week's meeting, I noted I had been looking at the schematics for >>> Fox-1 and RT-IHU and found the circuits for the latchup protection and >>> watchdog functions. I admit this might be basic to some, but I'm finding >>> it fascinating! Anyway... >>> >>> Since last week's meeting, I researched the parts used: >>> >>> onsemi FPF2001 is a current limit switch used on both Fox-1 and half the >>> RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the FPF2000 is >>> listed as end-of-life. It's replacement part is the TI TPS22942. >>> >>> MAX4995 is a current limit switch used on the other half of the. This >>> part looks good for new designs. >>> >>> >>> For the watchdog functionality, both Fox-1 and RT-IHU use the >>> STWD100NYWY3F chip. this parts looks good for new designs. >>> >>> >>> That's as far as I got. Next, I want to research the Fox-1 and RT-IHU >>> designs to determine the thresholds of the current limit switches. In >>> particular, I want to see if the TPS22942 is a suitable replacement, >>> assuming we have the same current requirements. >>> >>> That's where I'm at, >>> >>> Jonathan >>> >>> >>> -- >>> Jonathan Brandenburg >>> Radio Amateur Satellite Corporation >>> 1-214-213-1066 >>> >>> >>> ----------------------------------------------------------- >>> >>> 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 >> > -- > Jonathan Brandenburg > Radio Amateur Satellite Corporation > 1-214-213-1066 > > > ----------------------------------------------------------- > > 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

Re: Latchup Protection and Watchdog Parts
by Bob Stricklin 20 Jan '23

20 Jan '23

Jonathan, Attached is an Excel file I have worked on for PacSat power needs. Bob On Jan 20, 2023, at 7:17 AM, Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: I seem to remember that, too. As such, we may need to look at other parts or different versions of the same parts. That depends, obviously on the maximum current draw expected during normal operation. Does anybody on this list know if we have that information for the AX5043 chain? Jonathan On 1/19/23 17:40, Rich Gopstein via pacsat-dev wrote: Burns might remember the details (or Zach certainly would), but one of those parts was undersized for the RT-IHU and would cut out when we were transmitting with the ax5043. I think we had to back down the xmit power in order for the device not to reset. Rich On Thu, Jan 19, 2023 at 5:46 PM Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: In last week's meeting, I noted I had been looking at the schematics for Fox-1 and RT-IHU and found the circuits for the latchup protection and watchdog functions. I admit this might be basic to some, but I'm finding it fascinating! Anyway... Since last week's meeting, I researched the parts used: onsemi FPF2001 is a current limit switch used on both Fox-1 and half the RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the FPF2000 is listed as end-of-life. It's replacement part is the TI TPS22942. MAX4995 is a current limit switch used on the other half of the. This part looks good for new designs. For the watchdog functionality, both Fox-1 and RT-IHU use the STWD100NYWY3F chip. this parts looks good for new designs. That's as far as I got. Next, I want to research the Fox-1 and RT-IHU designs to determine the thresholds of the current limit switches. In particular, I want to see if the TPS22942 is a suitable replacement, assuming we have the same current requirements. That's where I'm at, Jonathan -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066 ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066 ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@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<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Latchup Protection and Watchdog Parts
by Rich Gopstein 20 Jan '23

20 Jan '23

And - as long as I'm thinking about it, we had to disable the hardware watchdog on the RT-IHU to get it to run. I don't recall if that changed, but if you get some RT-IHU boards, you might need to jumper the hardware WD disable. Rich On Thu, Jan 19, 2023 at 6:40 PM Rich Gopstein via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns might remember the details (or Zach certainly would), but one of > those parts was undersized for the RT-IHU and would cut out when we were > transmitting with the ax5043. I think we had to back down the xmit power > in order for the device not to reset. > > Rich > > > On Thu, Jan 19, 2023 at 5:46 PM Jonathan Brandenburg via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> In last week's meeting, I noted I had been looking at the schematics for >> Fox-1 and RT-IHU and found the circuits for the latchup protection and >> watchdog functions. I admit this might be basic to some, but I'm finding >> it fascinating! Anyway... >> >> Since last week's meeting, I researched the parts used: >> >> onsemi FPF2001 is a current limit switch used on both Fox-1 and half the >> RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the FPF2000 is >> listed as end-of-life. It's replacement part is the TI TPS22942. >> >> MAX4995 is a current limit switch used on the other half of the. This >> part looks good for new designs. >> >> >> For the watchdog functionality, both Fox-1 and RT-IHU use the >> STWD100NYWY3F chip. this parts looks good for new designs. >> >> >> That's as far as I got. Next, I want to research the Fox-1 and RT-IHU >> designs to determine the thresholds of the current limit switches. In >> particular, I want to see if the TPS22942 is a suitable replacement, >> assuming we have the same current requirements. >> >> That's where I'm at, >> >> Jonathan >> >> >> -- >> Jonathan Brandenburg >> Radio Amateur Satellite Corporation >> 1-214-213-1066 >> >> >> ----------------------------------------------------------- >> >> 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 >

2 1

Re: Latchup Protection and Watchdog Parts
by Jonathan Brandenburg 20 Jan '23

20 Jan '23

I seem to remember that, too. As such, we may need to look at other parts or different versions of the same parts. That depends, obviously on the maximum current draw expected during normal operation. Does anybody on this list know if we have that information for the AX5043 chain? Jonathan On 1/19/23 17:40, Rich Gopstein via pacsat-dev wrote: > Burns might remember the details (or Zach certainly would), but one of > those parts was undersized for the RT-IHU and would cut out when we > were transmitting with the ax5043. I think we had to back down the > xmit power in order for the device not to reset. > > Rich > > > On Thu, Jan 19, 2023 at 5:46 PM Jonathan Brandenburg via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > In last week's meeting, I noted I had been looking at the > schematics for > Fox-1 and RT-IHU and found the circuits for the latchup protection > and > watchdog functions. I admit this might be basic to some, but I'm > finding > it fascinating! Anyway... > > Since last week's meeting, I researched the parts used: > > onsemi FPF2001 is a current limit switch used on both Fox-1 and > half the > RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the > FPF2000 is > listed as end-of-life. It's replacement part is the TI TPS22942. > > MAX4995 is a current limit switch used on the other half of the. This > part looks good for new designs. > > > For the watchdog functionality, both Fox-1 and RT-IHU use the > STWD100NYWY3F chip. this parts looks good for new designs. > > > That's as far as I got. Next, I want to research the Fox-1 and RT-IHU > designs to determine the thresholds of the current limit switches. In > particular, I want to see if the TPS22942 is a suitable replacement, > assuming we have the same current requirements. > > That's where I'm at, > > Jonathan > > > -- > Jonathan Brandenburg > Radio Amateur Satellite Corporation > 1-214-213-1066 > > > ----------------------------------------------------------- > > 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 athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

Re: Latchup Protection and Watchdog Parts
by Rich Gopstein 19 Jan '23

19 Jan '23

Burns might remember the details (or Zach certainly would), but one of those parts was undersized for the RT-IHU and would cut out when we were transmitting with the ax5043. I think we had to back down the xmit power in order for the device not to reset. Rich On Thu, Jan 19, 2023 at 5:46 PM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > In last week's meeting, I noted I had been looking at the schematics for > Fox-1 and RT-IHU and found the circuits for the latchup protection and > watchdog functions. I admit this might be basic to some, but I'm finding > it fascinating! Anyway... > > Since last week's meeting, I researched the parts used: > > onsemi FPF2001 is a current limit switch used on both Fox-1 and half the > RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the FPF2000 is > listed as end-of-life. It's replacement part is the TI TPS22942. > > MAX4995 is a current limit switch used on the other half of the. This > part looks good for new designs. > > > For the watchdog functionality, both Fox-1 and RT-IHU use the > STWD100NYWY3F chip. this parts looks good for new designs. > > > That's as far as I got. Next, I want to research the Fox-1 and RT-IHU > designs to determine the thresholds of the current limit switches. In > particular, I want to see if the TPS22942 is a suitable replacement, > assuming we have the same current requirements. > > That's where I'm at, > > Jonathan > > > -- > Jonathan Brandenburg > Radio Amateur Satellite Corporation > 1-214-213-1066 > > > ----------------------------------------------------------- > > 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

Latchup Protection and Watchdog Parts
by Jonathan Brandenburg 19 Jan '23

19 Jan '23

In last week's meeting, I noted I had been looking at the schematics for Fox-1 and RT-IHU and found the circuits for the latchup protection and watchdog functions. I admit this might be basic to some, but I'm finding it fascinating! Anyway... Since last week's meeting, I researched the parts used: onsemi FPF2001 is a current limit switch used on both Fox-1 and half the RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the FPF2000 is listed as end-of-life. It's replacement part is the TI TPS22942. MAX4995 is a current limit switch used on the other half of the. This part looks good for new designs. For the watchdog functionality, both Fox-1 and RT-IHU use the STWD100NYWY3F chip. this parts looks good for new designs. That's as far as I got. Next, I want to research the Fox-1 and RT-IHU designs to determine the thresholds of the current limit switches. In particular, I want to see if the TPS22942 is a suitable replacement, assuming we have the same current requirements. That's where I'm at, Jonathan -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

Re: Pacsat dev meeting 1-19-2023
by Jonathan Brandenburg 19 Jan '23

19 Jan '23

I'm afraid I won't make this evening's meeting... I'm out of town for almost two entire weeks with only a few hours at home and if I want to stay married, I won't get on any meetings tonight! I'll send a separate email with a brief update. Jonathan On 1/19/23 12:06, Bill via pacsat-dev wrote: > Pacsat dev meeting 1-19-2023 > Thu, Jan 19, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/210641357 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (224) 501-3412 > - One-touch: tel:+12245013412,,210641357# > > Access Code: 210-641-357 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > 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 -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0