- pacsat-dev - mailman.amsat.org

KiCad Files
by Bob Stricklin 27 Aug '23

27 Aug '23

All, I posted the current KiCAD project files in PacSatDocs under Hardware/PCB This package uses KiCAD Version 7.0.6-7.0.6-ubuntu22.04.1, release build There is still work to be done but I wanted to get this out there because the files are close to complete. In the next couple of days I will make some PDF files for of the schematics and PCB and pst those as well for anyone that does not want to install this version of KiCAD. If you do happen to load this and see you see things that need to be changed please let me know. Bob N5BRG

1 0

Re: MRAM
by Chris Thompson 25 Aug '23

25 Aug '23

I have some larger MRAM chips that I got earlier in the project when I was going to make a small prototype board. Burns had supplied the instructions. Then Rich sent me one so I forgot about it. I have 4 but I am nervous to try to replace the ones on the booster board in case I can't get it to work again! I do have a hot air soldering station and did lift and replace two of the AX5043s, so perhaps it is not beyond my skill. But I may wait until I have finished any other code changes needed for symposium. 73 Chris On Fri, Aug 25, 2023, 13:26 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > That seems reasonable since Jonathan likes to spend money. And it is not > that much anyway, as such things go. > > I believe that the (base) software should automatically support larger > MRAMs since I first developed that part of it on a breadboard with a larger > MRAM. However, I only had a single chip on that breadboard, so no > guarantee, I'd be happy to be the guinea pig, at least once I get the I2c > driver fixed up. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, Aug 25, 2023 at 1:17 PM Jim McCullers via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> At Thursday night’s meeting Chris brought up having more MRAM on future >> boards. >> >> The daughter board uses four smaller capacity chips due to the number >> required for the six boards created. >> >> >> >> The MRAM chips on the current board can be replaced but it will have to >> be done using a heat gun due to the pin characteristics of the chips. >> >> We could do some board swapping as no spares exist and I can replace the >> modules and test this time as we have capable software. >> >> >> >> One meg (128x8) regular chips (non-automotive/flight) cost approximately >> $10 each and four meg (512kx8) are approximately $21 each in single lots. >> >> Discounts start at purchases of 10 but are not that substantial. >> >> >> >> Jim McCullers >> >> WA4CWI >> >> ----------------------------------------------------------- >> >> 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

Re: MRAM
by Burns Fisher (AMSAT) 25 Aug '23

25 Aug '23

That seems reasonable since Jonathan likes to spend money. And it is not that much anyway, as such things go. I believe that the (base) software should automatically support larger MRAMs since I first developed that part of it on a breadboard with a larger MRAM. However, I only had a single chip on that breadboard, so no guarantee, I'd be happy to be the guinea pig, at least once I get the I2c driver fixed up. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Aug 25, 2023 at 1:17 PM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > At Thursday night’s meeting Chris brought up having more MRAM on future > boards. > > The daughter board uses four smaller capacity chips due to the number > required for the six boards created. > > > > The MRAM chips on the current board can be replaced but it will have to be > done using a heat gun due to the pin characteristics of the chips. > > We could do some board swapping as no spares exist and I can replace the > modules and test this time as we have capable software. > > > > One meg (128x8) regular chips (non-automotive/flight) cost approximately > $10 each and four meg (512kx8) are approximately $21 each in single lots. > > Discounts start at purchases of 10 but are not that substantial. > > > > Jim McCullers > > WA4CWI > > ----------------------------------------------------------- > > 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

MRAM
by Jim McCullers 25 Aug '23

25 Aug '23

At Thursday night's meeting Chris brought up having more MRAM on future boards. The daughter board uses four smaller capacity chips due to the number required for the six boards created. The MRAM chips on the current board can be replaced but it will have to be done using a heat gun due to the pin characteristics of the chips. We could do some board swapping as no spares exist and I can replace the modules and test this time as we have capable software. One meg (128x8) regular chips (non-automotive/flight) cost approximately $10 each and four meg (512kx8) are approximately $21 each in single lots. Discounts start at purchases of 10 but are not that substantial. Jim McCullers WA4CWI

1 0

Re: Pacsat dev mtg 8/24/2023
by Corey Minyard 24 Aug '23

24 Aug '23

I had something else come up tonight, and I'm not going to be able to make it again. --corey - AE5KM On Thu, Aug 24, 2023 at 1:09 PM Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Oops. I won't be there tonight. I've been working on fixing the I2c driver so that it does a restart rather than a stop/start between writing a command and reading a register. This may (or may not) fix the problem reading the RTC, but it is wrong in any case and needs fixing both for PacSat and for Golf. > > 73, > > Burns Fisher, WB1FJ > AMSAT(R) Engineering -- Flight Software > > > On Thu, Aug 24, 2023 at 2:04 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: >> >> Pacsat dev mtg 8/24/2023 >> Thu, Aug 24, 2023 7:00 PM - 9:00 PM (CDT) >> >> Please join my meeting from your computer, tablet or smartphone. >> >> https://meet.goto.com/942587421 >> >> 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,,942587421# >> >> Access Code: 942-587-421 >> >> Join from a video-conferencing room or system. >> Dial in or type: 67.217.95.2 or inroomlink.goto.com >> Meeting ID: 942 587 421 >> Or dial directly: 942587421(a)67.217.95.2 or 67.217.95.2##942587421 >> >> >> 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 > > > ----------------------------------------------------------- > > 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: Pacsat dev mtg 8/24/2023
by Burns Fisher (AMSAT) 24 Aug '23

24 Aug '23

Oops. I won't be there tonight. I've been working on fixing the I2c driver so that it does a restart rather than a stop/start between writing a command and reading a register. This may (or may not) fix the problem reading the RTC, but it is wrong in any case and needs fixing both for PacSat and for Golf. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Aug 24, 2023 at 2:04 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg 8/24/2023 > Thu, Aug 24, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/942587421 > > 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,,942587421# > > Access Code: 942-587-421 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 942 587 421 > Or dial directly: 942587421(a)67.217.95.2 or 67.217.95.2##942587421 > > > 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 >

1 0

Pacsat dev mtg 8/24/2023
by Bill 24 Aug '23

24 Aug '23

Pacsat dev mtg 8/24/2023 Thu, Aug 24, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/942587421 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,,942587421# Access Code: 942-587-421 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 942 587 421 Or dial directly: 942587421(a)67.217.95.2 or 67.217.95.2##942587421 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Version 0.1g
by Chris Thompson 23 Aug '23

23 Aug '23

I merged my latest development branch with main. This includes the draft RTC code. Burns is now working on the driver to see if we can get it to work correctly. My draft code works but is not optimal. This version also includes maintenance functions that expire old files and old uploads. The uploads use a new table in MRAM so you will need to issue "clear mram" after flashing this. You can test the new table with "test upload table". Files are purged after 5 days, partial uploads are purged 3 days after the latest packet received. These are in a #define but in the future will need to be commendable from the ground. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Another Possible PA
by Jim McCullers 23 Aug '23

23 Aug '23

I'll give the spec sheet a look over before tomorrow night's meeting. 73, Jim McCullers Looks like this part would work for us. If we set it up to work at a lower voltage we can limit power output and DC power needed. Bob

1 0

Another Possible PA
by Bob Stricklin 23 Aug '23

23 Aug '23

Looks like this part would work for us. If we set it up to work at a lower voltage we can limit power output and DC power needed. Bob

1 0