- pacsat-dev - mailman.amsat.org

First pass at 2024 budget
by Bill Reed 12 Jan '24

12 Jan '24

Zach, here is my budget thinking at this point. Let's discuss when you can. Pacsat dev team please comment. *AMSAT Engineering Pacsat Project 2024 Budget submitted by NX5R Circuit Board Production - Pacsat AX5043 based design, Cubesat 1U, 92mm X92mm, PC104 interface. 2 production runs during 2024. 4-5 boards manufactured Spring 2024. 5-6 boards manufactured October 2024. - Total $24,000.* *JTAG support Hardware - Support hardware for 8 programmers. - Total $300* *AX5043 Inventory - The AX5043 went out of production in 2023. Parts are still available from some sources. We need to build inventory to protect our current design. - Total $5000* *Shipping and Miscellaneous parts - Estimate - Total $500 * *Marketing and Deployment - Promotion of Pacsat product and launch support. Travel for team members. Brochures and other printing costs. - Total $14,000 Total 2024 Budget = $43,800.*

1 0

Re: Issue with touch in project
by Bob Stricklin 11 Jan '24

11 Jan '24

Burns, It seems to me this line of code is referring to a folder that would be on the users system under his home directory called gitRepos. I have looking in Windows under user and my name (home folder) and on my linux computer which I built this code and not seeing this on either one. I do see errors referring to the touch. When I remove it I have lots of errors. It looks like something that was put in place a long time ago when the project was just rt-ihu. With the line in place the project will build but I don’t like seeing the errors. I have used touch to force creation of a file but did not know you could sweep through a project and update times to current time. I see it is used for this according to "man touch". I wonder if an older version of CCS was not handling time the way people wanted and this was a work around? Maybe I could fix this by changing the touch path to match my current system project path info. Am I really that worried about changing a time stamp? Strange how this causes issue when removed. Maybe the Makefile is not keeping up with project properties changes real time. Changing all the dates would force a make -B I haven’t figured out if Build Project generates a new Makefile on every build cycle. Bob On Jan 11, 2024, at 9:42 PM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: I think console routines fetches the time that the compile happened, so rebuilding it forces it to include the time of the compile regardless of whether anything else has changed in that routine. Touch should just change the date on the file so make will always compile it. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Thu, Jan 11, 2024 at 10:38 PM Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: <PacSatSW_Issue.jpeg> Here is the location of the “touch” issue? What is this for? Why does it break things if you remove it? ----------------------------------------------------------- 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<https://mailman.amsat.org/> ----------------------------------------------------------- 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: Issue with touch in project
by Burns Fisher (AMSAT) 11 Jan '24

11 Jan '24

I think console routines fetches the time that the compile happened, so rebuilding it forces it to include the time of the compile regardless of whether anything else has changed in that routine. Touch should just change the date on the file so make will always compile it. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Jan 11, 2024 at 10:38 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > > Here is the location of the “touch” issue? > > What is this for? > > Why does it break things if you remove it? > > ----------------------------------------------------------- > > 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

Issue with touch in project
by Bob Stricklin 11 Jan '24

11 Jan '24

[cid:27FC6D12-DABD-4B1A-8483-A2D48DEE25D3@StricklinRanch.com] Here is the location of the “touch” issue? What is this for? Why does it break things if you remove it?

1 0

Code Composer Search
by Jim McCullers 11 Jan '24

11 Jan '24

Bob is correct. The search symbol looks more like a rocket than flashlight. Chris told me there was a symbol on the tool bar and through experimentation and Google I realized it was a flashlight, not the common search symbol. Attached is an image how I do project searches. Like the flashlight it wasn't intuitive. Jim McCullers WA4CWI

1 0

Re: Pacsat dev mtg 1/11/2024
by Burns Fisher (AMSAT) 11 Jan '24

11 Jan '24

As usual, this is my other-meeting Thursday. See you next week. Bob, BTW, I got the debug board today. Looks good! Thank you. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Jan 11, 2024 at 1:09 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg 1/11/2024 > Thu, Jan 11, 2024 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/272073445 > > 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,,272073445# > > Access Code: 272-073-445 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 272 073 445 > Or dial directly: 272073445(a)67.217.95.2 or 67.217.95.2##272073445 > > > 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 1/11/2024
by Bill 11 Jan '24

11 Jan '24

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

1 0

Jonathan's request for TMS570 programming boards
by Burns Fisher (AMSAT) 10 Jan '24

10 Jan '24

Many moons ago, Jonathan had someone (Chris Grill) designing programming boards for the TMS570 since the one we use was obsolete. That never went anywhere. I recently saw a bunch for sale and bought them up and now have 10-ish additional boards. In addition, Carl Wick designed a nice little 3D printed case for them. Right now, Zach, Rich, Bob Strickland, and I have at least one board and Rich and I have a couple prototype cases. My question is: Is someone other than Golf-TEE folks and Pacsat really planning to use the TMS570 and could benefit from the programming boards? If not immediately, I can hold onto them, but I don't want anyone to waste time trying to build or buy them again now that we have plenty. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* PS: To be clear, there are at least three ways to load a program into a TMS570: One is via a LaunchPad evaluation board, which has something similar to the programming board built in. Another is a TI XDS110 programming device (a $200 piece of hardware that may or may not be available). And third using this board that I am talking about, a $20 board called a SensorTag board. (And Heimir has also written a boot loader to load via a serial port, but it must be loaded using one of the above methods in order to be used).

1 0

Re: Blinky Working
by Jim McCullers 10 Jan '24

10 Jan '24

Thanks Jim WA4CWI Jim, I appreciate you trying to make it work. Zipped code attached. Seems like a small zip file so may not be all there. On the other hand it is mostly text files. Bob On Jan 9, 2024, at 4:07 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org <mailto:pacsat-dev@amsat.org> > wrote: Blinky was a crap shoot at best to try the HCG and FreeRTOS. I’ll look at your HCG and see if I find a difference. I see the HCG below but not the source code. Send it along. At least it gave you something to test load. If the problem is not resolved when I receive a working board I’ll debug the code as the exercise it was intended to be. Congrats and 73, Jim McCullers WA4CWI ----------------------------------------------------------- pacsat-dev mailing list -- <mailto:pacsat-dev@amsat.org> pacsat-dev(a)amsat.org View archives of this mailing list at <https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to <mailto:pacsat-dev-leave@amsat.org> pacsat-dev-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at <https://mailman.amsat.org/> https://mailman.amsat.org

1 0

Re: Blinky Working
by Bob Stricklin 09 Jan '24

09 Jan '24

Jim, I appreciate you trying to make it work. Zipped code attached. Seems like a small zip file so may not be all there. On the other hand it is mostly text files. Bob On Jan 9, 2024, at 4:07 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Blinky was a crap shoot at best to try the HCG and FreeRTOS. I’ll look at your HCG and see if I find a difference. I see the HCG below but not the source code. Send it along. At least it gave you something to test load. If the problem is not resolved when I receive a working board I’ll debug the code as the exercise it was intended to be. Congrats and 73, Jim McCullers WA4CWI ----------------------------------------------------------- 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<https://mailman.amsat.org/>

1 0