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

Pacsat dev meeting 3/30/2023
by Bill 30 Mar '23

30 Mar '23

Pacsat dev meeting 3/30/2023 Thu, Mar 30, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/513907517 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-3112 - One-touch: tel:+15713173112,,513907517# Access Code: 513-907-517 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Pacsat dev meeting 3/23/2023
by Bill 23 Mar '23

23 Mar '23

Pacsat dev meeting 3/23/2023 Thu, Mar 23, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/222702053 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,,222702053# Access Code: 222-702-053 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Software Architecture Doc updated
by Chris Thompson 19 Mar '23

19 Mar '23

As discussed on the call, I have updated the software architecture document. Please review and let me know any comments. https://github.com/AMSAT-NA/PacSatDocs/blob/main/requirements/Pacsat-Softwa… 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat dev meeting 3/16/2023
by Corey Minyard 16 Mar '23

16 Mar '23

On Thu, Mar 16, 2023 at 04:30:46PM +0000, Bill via pacsat-dev wrote: > Pacsat dev meeting 3/16/2023 > Thu, Mar 16, 2023 7:00 PM - 9:00 PM (CDT) I probably won't be able to make this. Either I will be NCS for the storms coming through Dallas (and Bill will probably be out, too) or I have another obligation. -corey > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/537925421 > > 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,,537925421# > > Access Code: 537-925-421 > > > 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/[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

Pacsat dev meeting 3/16/2023
by Bill 16 Mar '23

16 Mar '23

Pacsat dev meeting 3/16/2023 Thu, Mar 16, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/537925421 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,,537925421# Access Code: 537-925-421 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Pacsat-dev meeting 3/9/2023
by Burns Fisher (AMSAT) 09 Mar '23

09 Mar '23

I think I previously said that I could not come on the 1st Thursday of the month. Nope...I counted wrong. It is the second Thursday. In any case, I won't be there tonight. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Mar 9, 2023 at 2:41 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat-dev meeting 3/9/2023 > Thu, Mar 9, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/243430525 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (872) 240-3412 > - One-touch: tel:+18722403412,,243430525# > > Access Code: 243-430-525 > > > 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/[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

Pacsat-dev meeting 3/9/2023
by Bill 09 Mar '23

09 Mar '23

Pacsat-dev meeting 3/9/2023 Thu, Mar 9, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/243430525 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (872) 240-3412 - One-touch: tel:+18722403412,,243430525# Access Code: 243-430-525 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Missing Mar 9 meeting
by Burns Fisher (AMSAT) 07 Mar '23

07 Mar '23

As always, I am unable to make the first meeting of the month. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

PacSat git repo changes
by Burns Fisher (AMSAT) 03 Mar '23

03 Mar '23

Hi All, Bill and I talked this morning and decided (actually confirmed that we both agreed with what we already thought) that the PacSat git repository names are confusing. Bill and I agreed to change them, and I have done so. This means that if you have cloned them, you will have to change the upstream names in your local repository to match in order to push upstream. Here are the changes: 1. pacsatx is now PacSatSw and is to be use only for software (and documentation in the form of comments). 2. pacsat is now PacSatDocs and is to be used for documentation, including hardware schematics, hardware layouts etc. 3. PacSatSw is now WB1FJPacSatToDelete. This was the original repo that I created PacSatSw can be cloned directly into Code Composer Studio--it contains some of the CCS metadata to describe to the compiler where header files are etc. Currently there are two subdirectories in PacSatDocs: "requirements" and "reference". Requirements contains documents about PacSat itself. Reference contains files taken from other repositories, generally Fox or Golf SVN. These will usually be PDF files, and are NOT the masters. If changes are required, they must be made in the source files, which are in their original repositories. Bill is thinking about what to do regarding hardware, but will probably add a "hardware" folder for schematics etc etc. WB1FJPacSatToDelete can be deleted if no one is using it. It has had no checkins since November...it was moved to what is now PacSatSw at that time. We hope and expect that we will not have to do this again, and we apologize to those who have to change their local git repos. But hopefully, this renaming makes it a lot more clear what is going on. 73, Burns and Bill

1 1

Re: PacSat git repo changes
by Corey Minyard 03 Mar '23

03 Mar '23

On Fri, Mar 03, 2023 at 06:27:54PM +0000, Burns Fisher (AMSAT) via pacsat-dev wrote: > Hi All, > > Bill and I talked this morning and decided (actually confirmed that we both > agreed with what we already thought) that the PacSat git repository names > are confusing. Bill and I agreed to change them, and I have done so. Thanks, I was thinking about making a suggestion like this, but the new names are good names. -corey > > This means that if you have cloned them, you will have to change the > upstream names in your local repository to match in order to push upstream. > > Here are the changes: > > > > 1. pacsatx is now PacSatSw and is to be use only for software (and > documentation in the form of comments). > 2. pacsat is now PacSatDocs and is to be used for documentation, > including hardware schematics, hardware layouts etc. > 3. PacSatSw is now WB1FJPacSatToDelete. This was the original repo that > I created > > > PacSatSw can be cloned directly into Code Composer Studio--it contains some > of the CCS metadata to describe to the compiler where header files are etc. > > Currently there are two subdirectories in PacSatDocs: "requirements" and > "reference". Requirements contains documents about PacSat itself. > Reference contains files taken from other repositories, generally Fox or > Golf SVN. These will usually be PDF files, and are NOT the masters. If > changes are required, they must be made in the source files, which are in > their original repositories. > > Bill is thinking about what to do regarding hardware, but will probably add > a "hardware" folder for schematics etc etc. > > WB1FJPacSatToDelete can be deleted if no one is using it. It has had no > checkins since November...it was moved to what is now PacSatSw at that time. > > We hope and expect that we will not have to do this again, and we apologize > to those who have to change their local git repos. But hopefully, this > renaming makes it a lot more clear what is going on. > > > 73, > > Burns and Bill > > ----------------------------------------------------------- > > 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