- pacsat-dev - mailman.amsat.org

Re: Status of the three boards
by Jim McCullers 26 Jan '24

26 Jan '24

Paranoia is helpful until it's not. Congrats I realized the other three boards were not working due to my paranoia. The 5V regulator must have at least 10 mA of current draw and I had all the follow on circuits disconnected. When I put a load in place all working fine. All three of these boards are working with blinking leds program now. Bob ----------------------------------------------------------- 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

Status of the three boards
by Bob Stricklin 26 Jan '24

26 Jan '24

I realized the other three boards were not working due to my paranoia. The 5V regulator must have at least 10 mA of current draw and I had all the follow on circuits disconnected. When I put a load in place all working fine. All three of these boards are working with blinking leds program now. Bob

1 0

Pacsat dev mtg 1/25/2024
by Bill 25 Jan '24

25 Jan '24

Pacsat dev mtg 1/25/2024 Thu, Jan 25, 2024 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/652852245 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-3212 - One-touch: tel:+18722403212,,652852245# Access Code: 652-852-245 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 652 852 245 Or dial directly: 652852245(a)67.217.95.2 or 67.217.95.2##652852245 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Progress
by Burns Fisher (AMSAT) 23 Jan '24

23 Jan '24

Bob, why don't you not both doing the HalCoGen changes and let me get the software. I'm so familiar with how I did HalCoGen and everything else that I can probably do it faster. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Jan 23, 2024 at 9:34 AM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Working hard on the boards. Spent the weekend swamping out and adding > parts to the 3 untouched boards. A few more parts need to be added. > > Have the power supply sections working. The chip for the 1.2 volt supply > is the most difficult to work with. > > Goal is to ship these out to people soon. I wanted to get one out to Burns > yesterday but taking longer to get them ready. > > Today is tied up with travel and doctors visits. > > I realize looking through the code that the bits on the IO lines are being > changed individually. This means that getting HCG correct was just a piece > of what we needed. Getting all the bits correct will take some time. > > Bob > > ----------------------------------------------------------- > > 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

Progress
by Bob Stricklin 23 Jan '24

23 Jan '24

Working hard on the boards. Spent the weekend swamping out and adding parts to the 3 untouched boards. A few more parts need to be added. Have the power supply sections working. The chip for the 1.2 volt supply is the most difficult to work with. Goal is to ship these out to people soon. I wanted to get one out to Burns yesterday but taking longer to get them ready. Today is tied up with travel and doctors visits. I realize looking through the code that the bits on the IO lines are being changed individually. This means that getting HCG correct was just a piece of what we needed. Getting all the bits correct will take some time. Bob

1 0

Software problems on blinky
by Burns Fisher (AMSAT) 19 Jan '24

19 Jan '24

Hi Bob, I was not able to go to the meeting last night, but I hear you are still having problems with the software. I just spent several hours debugging/staring at/thinking about a subtle problem causing an OS crash on my own Golf software, so I guess my thought is that I'm not too likely to be able to suggest a quick fix for you without a lot of hands-on. That said, if you want to send me a copy of the board, (and I understand that it may have flaws), I'm more than willing to look into the s/w problem. I'm sometimes pretty good at finding simple hw problems too. Let me know what you think. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Pacsat dev mtg 1/18/2024
by Bill 18 Jan '24

18 Jan '24

Pacsat dev mtg 1/18/2024 Thu, Jan 18, 2024 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/863270357 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-3311 - One-touch: tel:+18722403311,,863270357# Access Code: 863-270-357 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 863 270 357 Or dial directly: 863270357(a)67.217.95.2 or 67.217.95.2##863270357 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Not here tomorrow
by Corey Minyard 18 Jan '24

18 Jan '24

On Thu, Jan 18, 2024 at 02:57:43AM +0000, Burns Fisher (AMSAT) via pacsat-dev wrote: > Snow on Tuesday moved my band rehearsal from Tuesday to Thurs, so I won't > be there for another week. Today is my monthly day where I can't make it, either. -corey > > 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

Not here tomorrow
by Burns Fisher (AMSAT) 18 Jan '24

18 Jan '24

Snow on Tuesday moved my band rehearsal from Tuesday to Thurs, so I won't be there for another week. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Moving my project to Github
by Burns Fisher (AMSAT) 17 Jan '24

17 Jan '24

Does Bob need one of those very long random passwords that github generates, or else a public key to actuallly push code there now? Is that the problem possibly? I know I did the long pw sometime but it must have been saved. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Jan 17, 2024 at 9:16 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I suggest applying the code changes to a branch rather than pushing a new > repo. Create a branch in the original repo, check out the branch then copy > all the new repo code over it. Including the halogen changes. Then commit > and push the branch. > > 73 > Chris > > On Tue, Jan 16, 2024, 17:46 Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Any ideas, Chris? You are more of a git expert than I. >> >> Have you seen the memory issue either? >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Tue, Jan 16, 2024 at 5:41 PM Bob Stricklin via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I used the Git tool in CCS to clone the PacSatSWV2 repository locally. >>> Then I copied all the files into the cloned area and now trying to push it >>> back up. >>> >>> >>> >>> Bob >>> >>> >>> >>> >>> >>> *From:* Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> >>> *Sent:* Tuesday, January 16, 2024 4:36 PM >>> *To:* Bob Stricklin <bstrick(a)n5brg.com> >>> *Cc:* Pacsat Dev <pacsat-dev(a)amsat.org> >>> *Subject:* [pacsat-dev] Re: Moving my project to Github >>> >>> >>> >>> How did you get it in the first place? If you pulled it down from >>> github then it should just push right back up there? It's been a long time >>> since I tried to set it up new. I'll try to get some time to look tomorrow >>> if just pushing it does not work. >>> >>> >>> >>> OH, that is why Bill wanted a new repository. It would have been so >>> much easier just to pull Jim's version down and make a branch for yours on >>> the same repository. >>> >>> >>> 73, >>> >>> >>> >>> Burns Fisher, WB1FJ >>> >>> *AMSAT**(R) **Engineering -- Flight Software* >>> >>> >>> >>> >>> >>> On Tue, Jan 16, 2024 at 5:31 PM Bob Stricklin via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>> Do any of you know the proper steps for me to get this initial code into >>> Github? Here is a image of what I have done. I thought it was going to post >>> but a cannot get the commit button at bottom to take action. >>> >>> >>> >>> Bob >>> >>> >>> >>> >>> ----------------------------------------------------------- >>> >>> 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 >>> >> >> ----------------------------------------------------------- >> >> 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 >

1 0