January 2024 - pacsat-dev - mailman.amsat.org

Re: Schematic of Blinky
by Burns Fisher (AMSAT) 31 Jan '24

31 Jan '24

Thanks for the spreadsheet. But I can't search in the schematic you sent either. PRINT is not the way to go for a searchable PDF. You need to PLOT. It does not seem to make any difference other than the text. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Jan 31, 2024 at 2:25 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns, > > I believe the copy on GitHub was printed but here is one I just made which > for sure is printed. > Note this is Rev D and includes some changes but most of these are not > related to software. > > I am also attaching the spread sheet I did in the past and updated > recently which is a list of pin assignments from the CPU. This is easier to > work with for a software reference. > > Bob > > > > > > On Jan 31, 2024, at 12:18 PM, Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > Actually, I just found them on the PC104. > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, Jan 31, 2024 at 1:13 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > wrote: > > Hi Bob, > > I'm just getting started on software for the Blinky, but to do that, I > need to find things on the schematic. I found the schematic on gihub > (Schematic_231004.pdf) but it is not searchable, so I really can't find > (easily) where traces connect. For example, I found "UART_TX1 (as well as > RX1,2 and Tx2) but can't easily see what they connect to. Is there a > header somewhere (I could not see that on the physical board). > > If you can tell me where the UART lines go reasonbly soon, that would > help, but in the slightly longer term if you can make a KiCad PDF schematic > with the "plot" command rather than the "print" command (the ONLY thing > that I know about Kicad, I might add), that will produce a PDF with actual > text in it such that it can be searched. > > Thanks! > > 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/[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: Schematic of Blinky
by Bob Stricklin 31 Jan '24

31 Jan '24

Burns, I believe the copy on GitHub was printed but here is one I just made which for sure is printed. Note this is Rev D and includes some changes but most of these are not related to software. I am also attaching the spread sheet I did in the past and updated recently which is a list of pin assignments from the CPU. This is easier to work with for a software reference. Bob On Jan 31, 2024, at 12:18 PM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote: Actually, I just found them on the PC104. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Wed, Jan 31, 2024 at 1:13 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc<mailto:[email protected]>> wrote: Hi Bob, I'm just getting started on software for the Blinky, but to do that, I need to find things on the schematic. I found the schematic on gihub (Schematic_231004.pdf) but it is not searchable, so I really can't find (easily) where traces connect. For example, I found "UART_TX1 (as well as RX1,2 and Tx2) but can't easily see what they connect to. Is there a header somewhere (I could not see that on the physical board). If you can tell me where the UART lines go reasonbly soon, that would help, but in the slightly longer term if you can make a KiCad PDF schematic with the "plot" command rather than the "print" command (the ONLY thing that I know about Kicad, I might add), that will produce a PDF with actual text in it such that it can be searched. Thanks! 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> 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<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Schematic of Blinky
by Burns Fisher (AMSAT) 31 Jan '24

31 Jan '24

Hi Bob, I'm just getting started on software for the Blinky, but to do that, I need to find things on the schematic. I found the schematic on gihub (Schematic_231004.pdf) but it is not searchable, so I really can't find (easily) where traces connect. For example, I found "UART_TX1 (as well as RX1,2 and Tx2) but can't easily see what they connect to. Is there a header somewhere (I could not see that on the physical board). If you can tell me where the UART lines go reasonbly soon, that would help, but in the slightly longer term if you can make a KiCad PDF schematic with the "plot" command rather than the "print" command (the ONLY thing that I know about Kicad, I might add), that will produce a PDF with actual text in it such that it can be searched. Thanks! 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 1

Flight software description
by Burns Fisher (AMSAT) 30 Jan '24

30 Jan '24

I have told about a zillion people about a zillion times that there are reasonably detailed description of the flight software in a Wiki in our Redmine repository. What is Redmine you ask? Well, you see the problem. It was created for problem and document tracking at the start of the Golf project, but no one paid attention or used it except for Zack and me. So I have not even bothered to create accounts for new people. In any case, more people are asking about the flight software. The description, while really written for Golf, is essentially true for Golf, Pacsat, and Fox, Thus I decided to put it in the Golf SVN (and I'll put it in the PacSat document git repo soon). It is in https://svn.amsat.org/golf/FlightSoftwareDescriptions. There are 4 pdf files there with different things of interest. And I just realized I have a duplicate and am missing one file, but I have to leave now,. The most important 3 are there: Multiple_CPUs_with_Code_Composer_Studio.pdf Software_Description.pdf Use_of_HalCoGen_with_Golf_and_PacSat_Flight_Software.pdf These are PDFs. The source is in Redmine. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Test data and Updated Box
by Burns Fisher (AMSAT) 29 Jan '24

29 Jan '24

I told Bob a few minutes ago I had gotten but not opened the package. I had a couple minutes, so I just opened it and plugged it in. Blinky is blinking! So it appears that all is well shipping-wise. Thanks!

1 0

Re: Test data and Updated Box
by Burns Fisher (AMSAT) 29 Jan '24

29 Jan '24

So does that mean that you have been able to talk to the AX5043s and you know SPI is working? How about MRAM? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sun, Jan 28, 2024 at 11:08 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > All, > > I spent a time this weekend testing the boards and tweaking/changing the > part values mostly in the 2M PreAmp and power divider section. > > I created a new folder in Github PacSatDoc for TestData and uploaded the > photos and a video to this folder. Not sure how Github feels about this but > I will see. > We can delete things after people have a chance to take a look. > > The boiled down results are the PreAmp frontend has a range of 10 dB gain > through the FET + Filter+ Power divider to 5 dB on the lowest. I checked > all 8 of the balanced ports and found them to be mostly the same. > > I turned down the 140 MHz carrier until I could see it just about the > noise on the spectrum analyze and the most sensitive channel was working at > -94dB. > > Power supply info/photos was also uploaded. > > Over the next few days I hope the test the final amplifier. > > Uploaded a new set of STL files for the box. I looking at options to get > these printed now. > > Tomorrow i will push the code I have up to my GitHub site. > > Bob > > > > > > > ----------------------------------------------------------- > > 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

Test data and Updated Box
by Bob Stricklin 29 Jan '24

29 Jan '24

All, I spent a time this weekend testing the boards and tweaking/changing the part values mostly in the 2M PreAmp and power divider section. I created a new folder in Github PacSatDoc for TestData and uploaded the photos and a video to this folder. Not sure how Github feels about this but I will see. We can delete things after people have a chance to take a look. The boiled down results are the PreAmp frontend has a range of 10 dB gain through the FET + Filter+ Power divider to 5 dB on the lowest. I checked all 8 of the balanced ports and found them to be mostly the same. I turned down the 140 MHz carrier until I could see it just about the noise on the spectrum analyze and the most sensitive channel was working at -94dB. Power supply info/photos was also uploaded. Over the next few days I hope the test the final amplifier. Uploaded a new set of STL files for the box. I looking at options to get these printed now. Tomorrow i will push the code I have up to my GitHub site. Bob

1 0

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/[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

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