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

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

31 Aug '23

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

1 0

Re: Fwd: Re: Fwd: ITAR/EAR "Clearance" Process
by Jim McCullers 28 Aug '23

28 Aug '23

At some point we probably need outside experience and involvement to resolve RF issues. I can design a few filters that would be adequate but have zero experience working with PAs, definitely for space, and don’t want to see a repeat of the failed PAs like earlier. That’s where experience counts. As for software ideas or ideas concerning what a Pacsat should be is above my pay grade but I do have ideas. I do admit to my Pacsat experience being limited to chasing FalconSat-3 in it’s latter days. Never did make a connection but learned from my mistakes. As for avoidance of structured meetings I can relate but will say what I’ve learned in the past year sitting in on the Wednesday night meeting is invaluable. Deduct $.02 from my next paycheck. 73 Jim McCullers WA4CWI Does anyone on the team think we need an analog RF engineer at this point. Let me know if you think we do. I don't want to dilute our team meetings with "observers".... -------- Forwarded Message -------- Subject: Re: Fwd: ITAR/EAR "Clearance" Process Date: Mon, 28 Aug 2023 14:12:44 +0000 From: Jonathan Brandenburg <mailto:jonathan@jonathanbrandenburg.com> <jonathan(a)jonathanbrandenburg.com> To: Bill Reed <mailto:bill@brconnect.com> <bill(a)brconnect.com> His background is analog RF engineering, I believe. Jonathan On 8/28/2023 9:04 AM, Bill Reed wrote: Any idea what his skill set is? On 8/28/2023 8:36 AM, Jonathan Brandenburg wrote: Bill, Dave Benzel (email address below) is expressing an interest in discussion packet sats... If you want (it's entirely up to you) would you like to contact him as a potential volunteer? He attended one weekly engineering meeting and I take it he doesn't want to participate in structured meetings so I'm not sure how to engage him but I figure I'll let you know there's interest from him in packet sats. Jonathan -------- Forwarded Message -------- Subject: Re: ITAR/EAR "Clearance" Process Date: Fri, 25 Aug 2023 13:37:18 -0500 From: benzoid19(a)mindspring.com <mailto:benzoid19@mindspring.com> <mailto:benzoid19@mindspring.com> <benzoid19(a)mindspring.com> Reply-To: benzoid19(a)mindspring.com <mailto:benzoid19@mindspring.com> <mailto:benzoid19@mindspring.com> <benzoid19(a)mindspring.com> To: Jonathan Brandenburg <mailto:jonathan@jonathanbrandenburg.com> <jonathan(a)jonathanbrandenburg.com> Hi Jonathan - Thanks for note. No, nothing specific. At this point in my career, I am just looking for less structure... which doesn't really seem to fit in with your perfectly appropriate way of conducting projects. Thanks for keeping me in mind - I would really enjoy making what ever contribution I can, that may help unload some of your other folks. Seems like a great bunch, and can't wait to see us get more hardware in orbit. I'd like to send you some ideas I had on packet sats - working with the really fun IO-117 sat gave me a few ideas on how to improve this general system. Haahaaha - probably nothing you all haven't already thought of though !! - dB KD6RF -- Jonathan Brandenburg 1-214-213-1066 jonathan(a)jonathanbrandenburg.com <mailto:jonathan@jonathanbrandenburg.com> Using ProtonMail secure email service.

1 0

Re: Fwd: Re: Fwd: ITAR/EAR "Clearance" Process
by Burns Fisher (AMSAT) 28 Aug '23

28 Aug '23

Not being an RF guy myself, I would not have thought so. But I saw this mail earlier and suggested to Jonathan that he contact Bill and Chris because of his "ideas about pacsats". Given that his ideas come from playing with an GreenCube and not from hardware, I thought maybe this was a software/operation suggestion. Up to you all, of course. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Aug 28, 2023 at 10:23 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I should have also pointed out that even though his professional > background is "analog RF engineer", his desire as a volunteer with AMSAT is > in the area of packet sats. We often allow people to exercise what I'll > term "hobby skills" as a volunteer. > Jonathan > > On 8/28/2023 9:17 AM, Bill Reed via pacsat-dev wrote: > > Does anyone on the team think we need an analog RF engineer at this > point. Let me know if you think we do. I don't want to dilute our team > meetings with "observers".... > > > -------- Forwarded Message -------- > Subject: Re: Fwd: ITAR/EAR "Clearance" Process > Date: Mon, 28 Aug 2023 14:12:44 +0000 > From: Jonathan Brandenburg <jonathan(a)jonathanbrandenburg.com> > <jonathan(a)jonathanbrandenburg.com> > To: Bill Reed <bill(a)brconnect.com> <bill(a)brconnect.com> > > His background is analog RF engineering, I believe. > Jonathan > > On 8/28/2023 9:04 AM, Bill Reed wrote: > > Any idea what his skill set is? > On 8/28/2023 8:36 AM, Jonathan Brandenburg wrote: > > Bill, > > Dave Benzel (email address below) is expressing an interest in discussion > packet sats... If you want (it's entirely up to you) would you like to > contact him as a potential volunteer? > > He attended one weekly engineering meeting and I take it he doesn't want > to participate in structured meetings so I'm not sure how to engage him but > I figure I'll let you know there's interest from him in packet sats. > > Jonathan > > > -------- Forwarded Message -------- > Subject: Re: ITAR/EAR "Clearance" Process > Date: Fri, 25 Aug 2023 13:37:18 -0500 > From: benzoid19(a)mindspring.com <benzoid19(a)mindspring.com> > <benzoid19(a)mindspring.com> > Reply-To: benzoid19(a)mindspring.com <benzoid19(a)mindspring.com> > <benzoid19(a)mindspring.com> > To: Jonathan Brandenburg <jonathan(a)jonathanbrandenburg.com> > <jonathan(a)jonathanbrandenburg.com> > > Hi Jonathan - > > Thanks for note. No, nothing specific. At this point in my career, I am > just looking for less structure... which doesn't really seem to fit in with > your perfectly appropriate way of conducting projects. > > Thanks for keeping me in mind - I would really enjoy making what ever > contribution I can, that may help unload some of your other folks. Seems > like a great bunch, and can't wait to see us get more hardware in orbit. > > I'd like to send you some ideas I had on packet sats - working with the > really fun IO-117 sat gave me a few ideas on how to improve this general > system. Haahaaha - probably nothing you all haven't already thought of > though !! > > - dB KD6RF > > > > > > -- > Jonathan Brandenburg > 1-214-213-1066jonathan(a)jonathanbrandenburg.com > Using ProtonMail secure email service. > > > ----------------------------------------------------------- > > 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 > > > -- > Jonathan Brandenburg, KF5IDY > > > ----------------------------------------------------------- > > 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: Fwd: Re: Fwd: ITAR/EAR "Clearance" Process
by Jonathan Brandenburg 28 Aug '23

28 Aug '23

I should have also pointed out that even though his professional background is "analog RF engineer", his desire as a volunteer with AMSAT is in the area of packet sats. We often allow people to exercise what I'll term "hobby skills" as a volunteer. Jonathan On 8/28/2023 9:17 AM, Bill Reed via pacsat-dev wrote: > > Does anyone on the team think we need an analog RF engineer at this > point. Let me know if you think we do. I don't want to dilute our > team meetings with "observers".... > > > > -------- Forwarded Message -------- > Subject: Re: Fwd: ITAR/EAR "Clearance" Process > Date: Mon, 28 Aug 2023 14:12:44 +0000 > From: Jonathan Brandenburg <jonathan(a)jonathanbrandenburg.com> > To: Bill Reed <bill(a)brconnect.com> > > > > His background is analog RF engineering, I believe. > Jonathan > > On 8/28/2023 9:04 AM, Bill Reed wrote: >> >> Any idea what his skill set is? >> >> On 8/28/2023 8:36 AM, Jonathan Brandenburg wrote: >>> >>> Bill, >>> >>> Dave Benzel (email address below) is expressing an interest in >>> discussion packet sats... If you want (it's entirely up to you) >>> would you like to contact him as a potential volunteer? >>> >>> He attended one weekly engineering meeting and I take it he doesn't >>> want to participate in structured meetings so I'm not sure how to >>> engage him but I figure I'll let you know there's interest from him >>> in packet sats. >>> >>> Jonathan >>> >>> >>> >>> -------- Forwarded Message -------- >>> Subject: Re: ITAR/EAR "Clearance" Process >>> Date: Fri, 25 Aug 2023 13:37:18 -0500 >>> From: benzoid19(a)mindspring.com <benzoid19(a)mindspring.com> >>> Reply-To: benzoid19(a)mindspring.com <benzoid19(a)mindspring.com> >>> To: Jonathan Brandenburg <jonathan(a)jonathanbrandenburg.com> >>> >>> >>> >>> Hi Jonathan - >>> >>> Thanks for note. No, nothing specific. At this point in my career, >>> I am just looking for less structure... which doesn't really seem to >>> fit in with your perfectly appropriate way of conducting projects. >>> >>> Thanks for keeping me in mind - I would really enjoy making what >>> ever contribution I can, that may help unload some of your other >>> folks. Seems like a great bunch, and can't wait to see us get more >>> hardware in orbit. >>> >>> I'd like to send you some ideas I had on packet sats - working with >>> the really fun IO-117 sat gave me a few ideas on how to improve this >>> general system. Haahaaha - probably nothing you all haven't already >>> thought of though !! >>> >>> - dB KD6RF >>> >>> >>> >>> > > -- > Jonathan Brandenburg > 1-214-213-1066 > jonathan(a)jonathanbrandenburg.com > Using ProtonMail secure email service. > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg, KF5IDY

1 0

Fwd: Re: Fwd: ITAR/EAR "Clearance" Process
by Bill Reed 28 Aug '23

28 Aug '23

Does anyone on the team think we need an analog RF engineer at this point. Let me know if you think we do. I don't want to dilute our team meetings with "observers".... -------- Forwarded Message -------- Subject: Re: Fwd: ITAR/EAR "Clearance" Process Date: Mon, 28 Aug 2023 14:12:44 +0000 From: Jonathan Brandenburg <jonathan(a)jonathanbrandenburg.com> To: Bill Reed <bill(a)brconnect.com> His background is analog RF engineering, I believe. Jonathan On 8/28/2023 9:04 AM, Bill Reed wrote: > > Any idea what his skill set is? > > On 8/28/2023 8:36 AM, Jonathan Brandenburg wrote: >> >> Bill, >> >> Dave Benzel (email address below) is expressing an interest in >> discussion packet sats... If you want (it's entirely up to you) would >> you like to contact him as a potential volunteer? >> >> He attended one weekly engineering meeting and I take it he doesn't >> want to participate in structured meetings so I'm not sure how to >> engage him but I figure I'll let you know there's interest from him >> in packet sats. >> >> Jonathan >> >> >> >> -------- Forwarded Message -------- >> Subject: Re: ITAR/EAR "Clearance" Process >> Date: Fri, 25 Aug 2023 13:37:18 -0500 >> From: benzoid19(a)mindspring.com <benzoid19(a)mindspring.com> >> Reply-To: benzoid19(a)mindspring.com <benzoid19(a)mindspring.com> >> To: Jonathan Brandenburg <jonathan(a)jonathanbrandenburg.com> >> >> >> >> Hi Jonathan - >> >> Thanks for note. No, nothing specific. At this point in my career, >> I am just looking for less structure... which doesn't really seem to >> fit in with your perfectly appropriate way of conducting projects. >> >> Thanks for keeping me in mind - I would really enjoy making what ever >> contribution I can, that may help unload some of your other folks. >> Seems like a great bunch, and can't wait to see us get more hardware >> in orbit. >> >> I'd like to send you some ideas I had on packet sats - working with >> the really fun IO-117 sat gave me a few ideas on how to improve this >> general system. Haahaaha - probably nothing you all haven't already >> thought of though !! >> >> - dB KD6RF >> >> >> >> -- Jonathan Brandenburg 1-214-213-1066 jonathan(a)jonathanbrandenburg.com Using ProtonMail secure email service.

1 0

KiCad Files
by Bob Stricklin 28 Aug '23

28 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

Pacsat Console
by Bill Reed 18 Aug '23

18 Aug '23

The python program I demoed last night is at: https://github.com/billreed/PacsatConsole program name is pacterm.py

1 0

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

17 Aug '23

I won't be able to make it tonight. -corey - AE5KM On Thu, Aug 17, 2023 at 04:05:01PM +0000, Bill via pacsat-dev wrote: > Pacsat dev mtg 8/17/2023 > Thu, Aug 17, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/351106037 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (224) 501-3412 > - One-touch: tel:+12245013412,,351106037# > > Access Code: 351-106-037 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 351 106 037 > Or dial directly: 351106037(a)67.217.95.2 or 67.217.95.2##351106037 > > > 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/17/2023
by Bill 17 Aug '23

17 Aug '23

Pacsat dev mtg 8/17/2023 Thu, Aug 17, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/351106037 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (224) 501-3412 - One-touch: tel:+12245013412,,351106037# Access Code: 351-106-037 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 351 106 037 Or dial directly: 351106037(a)67.217.95.2 or 67.217.95.2##351106037 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Annual Meeting presentation
by Jonathan Brandenburg 13 Aug '23

13 Aug '23

Truly great news! Thank you for making this happen, y'all! Jonathan On 8/12/2023 1:47 PM, Bill Reed via pacsat-dev wrote: > > > Looks like we are on the agenda!! > > -------- Forwarded Message -------- > Subject: Re: Annual Meeting presentation > Date: Sat, 12 Aug 2023 08:47:31 -0400 > From: Daniel Schultz <n8fgv(a)usa.net> > To: Bill Reed <bill(a)brconnect.com> > > > > That would be excellent, see you in Dallas. > > Dan > > ------ Original Message ------ > Received: Fri, 11 Aug 2023 04:34:25 PM EDT > From: Bill Reed <bill(a)brconnect.com> > To: Daniel Schultz <n8fgv(a)usa.net> > Subject: Annual Meeting presentation > >> Dan, >> >> I am lead person for the Pacsat development that is part of the Amsat >> engineering ASCENT program. >> >> We ( the team ) would like to offer to make a presentation about our >> pacsat development at the annual meeting. >> >> We have discussed the following agenda: >> >> 5 min - Bill Reed giving an intro to pacsat (5 slides) >> >> 5 min for 5 team members to describe their part of the development >> >> 25 min for team member Chris Thompson to give a live demo of the >> pacsat development and the pacsat ground terminal. >> >> Times are approximate. I would expect that each team member would >> have 2 or 3 slides. >> >> Let me know if you would like us to present. >> >> Bill Reed, NX5R >> >> 214 437-9555 >> > > > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- jbrandenburg(a)amsat.org

1 0

Re: Fwd: Re: Annual Meeting presentation
by Chris Thompson 12 Aug '23

12 Aug '23

Great! Chris On Sat, Aug 12, 2023, 14:47 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Looks like we are on the agenda!! > > -------- Forwarded Message -------- > Subject: Re: Annual Meeting presentation > Date: Sat, 12 Aug 2023 08:47:31 -0400 > From: Daniel Schultz <n8fgv(a)usa.net> <n8fgv(a)usa.net> > To: Bill Reed <bill(a)brconnect.com> <bill(a)brconnect.com> > > That would be excellent, see you in Dallas. > > Dan > > ------ Original Message ------ > Received: Fri, 11 Aug 2023 04:34:25 PM EDT > From: Bill Reed <bill(a)brconnect.com> <bill(a)brconnect.com> > To: Daniel Schultz <n8fgv(a)usa.net> <n8fgv(a)usa.net> > Subject: Annual Meeting presentation > > Dan, > > I am lead person for the Pacsat development that is part of the Amsat > engineering ASCENT program. > > We ( the team ) would like to offer to make a presentation about our > pacsat development at the annual meeting. > > We have discussed the following agenda: > > 5 min - Bill Reed giving an intro to pacsat (5 slides) > > 5 min for 5 team members to describe their part of the development > > 25 min for team member Chris Thompson to give a live demo of the pacsat > development and the pacsat ground terminal. > > Times are approximate. I would expect that each team member would have 2 > or 3 slides. > > Let me know if you would like us to present. > > Bill Reed, NX5R > > 214 437-9555 > > > > > ----------------------------------------------------------- > > 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

Fwd: Re: Annual Meeting presentation
by Bill Reed 12 Aug '23

12 Aug '23

Looks like we are on the agenda!! -------- Forwarded Message -------- Subject: Re: Annual Meeting presentation Date: Sat, 12 Aug 2023 08:47:31 -0400 From: Daniel Schultz <n8fgv(a)usa.net> To: Bill Reed <bill(a)brconnect.com> That would be excellent, see you in Dallas. Dan ------ Original Message ------ Received: Fri, 11 Aug 2023 04:34:25 PM EDT From: Bill Reed <bill(a)brconnect.com> To: Daniel Schultz <n8fgv(a)usa.net> Subject: Annual Meeting presentation > Dan, > > I am lead person for the Pacsat development that is part of the Amsat > engineering ASCENT program. > > We ( the team ) would like to offer to make a presentation about our > pacsat development at the annual meeting. > > We have discussed the following agenda: > > 5 min - Bill Reed giving an intro to pacsat (5 slides) > > 5 min for 5 team members to describe their part of the development > > 25 min for team member Chris Thompson to give a live demo of the > pacsat development and the pacsat ground terminal. > > Times are approximate. I would expect that each team member would > have 2 or 3 slides. > > Let me know if you would like us to present. > > Bill Reed, NX5R > > 214 437-9555 >

1 0

Ax5043 Power Requirements
by Jim McCullers 10 Aug '23

10 Aug '23

In our last weekly meeting Bob ask if I could do a transmit power requirement study on the AX5043. The attached document is the results of that analysis. 73, Jim McCullers WA4CWI

1 0

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

10 Aug '23

Pacsat dev mtg 8/10/2023 Thu, Aug 10, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/414170485 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (312) 757-3121 - One-touch: tel:+13127573121,,414170485# Access Code: 414-170-485 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 414 170 485 Or dial directly: 414170485(a)67.217.95.2 or 67.217.95.2##414170485 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Small fix--Pacsat software x0.1f
by Burns Fisher (AMSAT) 07 Aug '23

07 Aug '23

I removed testing to see whether Golf i2c devices are there. They are not, and it makes boot slower and messes up the display for "get i2c". I also made "get i2c" more clear. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: i2c data
by Burns Fisher (AMSAT) 07 Aug '23

07 Aug '23

Ignore it. The three ADCs are on Golf only, but at least one has the same address as the temp sensor, which is why it is showing up as true. I'm not sure why the temp sensor is showing up as false, but again, it is probably a screwup. I'll remove that stuff. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Aug 7, 2023 at 3:25 PM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Any idea what this is telling us: > > Pacsat> > Pacsat>get i2c > I2c device state: > ICR ADC: 1 Solar ADC: 0, CSS ADC: 0 > RT-IHU Temp 0 > Pacsat> > > > ----------------------------------------------------------- > > 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: RSSI reading
by Burns Fisher (AMSAT) 07 Aug '23

07 Aug '23

If you say "get rssi" it is read from the register right then and there. It looks like (need to ask Chris) it also checks the RSSI before it accepts a package, and in that case it also prints it out only moments after it took it. And it looks like it is only accepting (and printing) it if it is greater than 170 (raw value) which I think is -85dBm. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Aug 7, 2023 at 3:13 PM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > When is the RSSI reading taken? (incoming signal or no signal?) > > > ----------------------------------------------------------- > > 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

i2c data
by Bill Reed 07 Aug '23

07 Aug '23

Any idea what this is telling us: Pacsat> Pacsat>get i2c I2c device state: ICR ADC: 1 Solar ADC: 0, CSS ADC: 0 RT-IHU Temp 0 Pacsat>

1 0

RSSI reading
by Bill Reed 07 Aug '23

07 Aug '23

When is the RSSI reading taken? (incoming signal or no signal?)

1 0

Re: Temp sensor
by Burns Fisher (AMSAT) 07 Aug '23

07 Aug '23

Are you sure it is 90 degrees and not the pure number 90. 90 is about correct for the numeric output, but then it should say something like (75F) after that. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Aug 7, 2023 at 10:11 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > My temp sensor at get temp shows 90 degrees but my infrared thermometer > reads 79. Is this an issue? > > Bill > > > ----------------------------------------------------------- > > 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: Problem solved
by Burns Fisher (AMSAT) 07 Aug '23

07 Aug '23

The pause might be because the routine that polls I2c devices is working now, and since there is only one, they all time out. That routine could easily be changed to avoid polling devices we don't have. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Aug 7, 2023 at 8:51 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Glad to hear this is working. > > I have noticed one thing with version X0.1e. When you press the reset > button on the launchpad it pauses for about a second before printing to the > console. Is that an intentional change to the boot process? Otherwise we > should investigate what changed. > > 73 > Chris > > On Sat, Aug 5, 2023 at 5:26 PM Bill Reed via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k..... >> >> >> ----------------------------------------------------------- >> >> 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 >> > > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > 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

Temp sensor
by Bill Reed 07 Aug '23

07 Aug '23

My temp sensor at get temp shows 90 degrees but my infrared thermometer reads 79. Is this an issue? Bill

1 0

Re: Problem solved
by Chris Thompson 07 Aug '23

07 Aug '23

Glad to hear this is working. I have noticed one thing with version X0.1e. When you press the reset button on the launchpad it pauses for about a second before printing to the console. Is that an intentional change to the boot process? Otherwise we should investigate what changed. 73 Chris On Sat, Aug 5, 2023 at 5:26 PM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k..... > > > ----------------------------------------------------------- > > 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Problem solved
by Jim McCullers 06 Aug '23

06 Aug '23

That's where it went! Knew the inventory was off by one. Woops The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k..... ----------------------------------------------------------- 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

Problem solved
by Bill Reed 05 Aug '23

05 Aug '23

The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k.....

1 0

Re: Pacsat ver 0.1e update
by Chris Thompson 05 Aug '23

05 Aug '23

I think I just had to clear MRAM. The garbage must have been some old data. Otherwise it seems to work. 73 Chris On Sat, Aug 5, 2023 at 10:53 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Confirmed that X1.0e runs here too. get temp returns the temperature as > expected. > > But there is an issue. There is garbage printed to the console, likely > when we send a frame: > > [image: image.png] > > 73 > Chris > > On Sat, Aug 5, 2023 at 10:40 AM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I was looking at this with Bill yesterday. That message should happen >> only if there is no response from the I2c message to the temp chip. Since >> it works just fine on mine, I'm guessing there is a hardware issue on >> Bill's board. He checked all the pins, so that implies to me either the >> chip is bad, or there is some issue with the board or the header connecting >> it to the LaunchPad. Or possibly a pullup on one of the I2c lines. I >> don't recall if there is a physical pullup or if they are programmed in the >> TMS570. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Sat, Aug 5, 2023 at 10:00 AM Bill Reed via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I upgraded my pacsat test hardware to software version 0.1d. It didn't >>> run. I discovered that the software was hanging up when it tried to >>> initialize the i2c temp sensor. That is new in 0.1d. In >>> troubleshooting with Chris and Burns we discovered that the calls to the >>> i2c initialization code were misplaced. That was fixed and uploaded to >>> github as version 0.1e. >>> >>> Version 0.1e runs on my test hardware but gives an i2c error message >>> every time it attempts to read the temp. This could be a hardware fault >>> on my test hardware. I have checked the temp sensor and all pins seem >>> to be correctly connected and connectivity of the SDL and SCA lines with >>> the TMS570 board is OK. I will be connecting the temp sensor to a >>> raspberry pi and running tests on that component. >>> >>> In order to continue to use the test hardware I have commented out >>> line191 in TelemAndControlTask.c which simply reports an error by >>> calling debug_print(). Entering 'get temp' on the pacsat console still >>> shows the error message. >>> >>> I'm having too much fun!! >>> >>> Bill >>> >>> >>> ----------------------------------------------------------- >>> >>> 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 >> > > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat ver 0.1e update
by Bob Stricklin 05 Aug '23

05 Aug '23

Bill, I would lean more toward your issue being a problem on the soldering or pull up resistors on the I2C bus. Using a meter with the power to the board off you might check the resistance on the clock and data bus to ground. Measure the value of resistance across the pull up resistors to be sure they are a big value like a few k ohms. Then look at the solder connects as best you can and make sure things are making contact. Instead you can use an oscilloscope and watch the action on the clock and data bus just to be sure something is there and cleanly jumping between about 3V and ground. The temp sensor may be solder on the board with the wrong orentation. Usually the part is fine it is getting proper connection that is a problem. There is a device sold I have used in the past called an Aardvark to monitor and talk to an I2C bus. I have also used code on a rpi to do this which I can find if needed. I think the bus voltages are the same so you could just jumper over from the pi I2C to the pacsat-dev board and include ground. Doing all this is more difficult and takes time. Bob > On Aug 5, 2023, at 9:00 AM, Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > I upgraded my pacsat test hardware to software version 0.1d. It didn't run. I discovered that the software was hanging up when it tried to initialize the i2c temp sensor. That is new in 0.1d. In troubleshooting with Chris and Burns we discovered that the calls to the i2c initialization code were misplaced. That was fixed and uploaded to github as version 0.1e. > > Version 0.1e runs on my test hardware but gives an i2c error message every time it attempts to read the temp. This could be a hardware fault on my test hardware. I have checked the temp sensor and all pins seem to be correctly connected and connectivity of the SDL and SCA lines with the TMS570 board is OK. I will be connecting the temp sensor to a raspberry pi and running tests on that component. > > In order to continue to use the test hardware I have commented out line191 in TelemAndControlTask.c which simply reports an error by calling debug_print(). Entering 'get temp' on the pacsat console still shows the error message. > > I'm having too much fun!! > > Bill > > > ----------------------------------------------------------- > > 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 ver 0.1e update
by Chris Thompson 05 Aug '23

05 Aug '23

Confirmed that X1.0e runs here too. get temp returns the temperature as expected. But there is an issue. There is garbage printed to the console, likely when we send a frame: [image: image.png] 73 Chris On Sat, Aug 5, 2023 at 10:40 AM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I was looking at this with Bill yesterday. That message should happen > only if there is no response from the I2c message to the temp chip. Since > it works just fine on mine, I'm guessing there is a hardware issue on > Bill's board. He checked all the pins, so that implies to me either the > chip is bad, or there is some issue with the board or the header connecting > it to the LaunchPad. Or possibly a pullup on one of the I2c lines. I > don't recall if there is a physical pullup or if they are programmed in the > TMS570. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Sat, Aug 5, 2023 at 10:00 AM Bill Reed via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I upgraded my pacsat test hardware to software version 0.1d. It didn't >> run. I discovered that the software was hanging up when it tried to >> initialize the i2c temp sensor. That is new in 0.1d. In >> troubleshooting with Chris and Burns we discovered that the calls to the >> i2c initialization code were misplaced. That was fixed and uploaded to >> github as version 0.1e. >> >> Version 0.1e runs on my test hardware but gives an i2c error message >> every time it attempts to read the temp. This could be a hardware fault >> on my test hardware. I have checked the temp sensor and all pins seem >> to be correctly connected and connectivity of the SDL and SCA lines with >> the TMS570 board is OK. I will be connecting the temp sensor to a >> raspberry pi and running tests on that component. >> >> In order to continue to use the test hardware I have commented out >> line191 in TelemAndControlTask.c which simply reports an error by >> calling debug_print(). Entering 'get temp' on the pacsat console still >> shows the error message. >> >> I'm having too much fun!! >> >> Bill >> >> >> ----------------------------------------------------------- >> >> 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat ver 0.1e update
by Burns Fisher (AMSAT) 05 Aug '23

05 Aug '23

I was looking at this with Bill yesterday. That message should happen only if there is no response from the I2c message to the temp chip. Since it works just fine on mine, I'm guessing there is a hardware issue on Bill's board. He checked all the pins, so that implies to me either the chip is bad, or there is some issue with the board or the header connecting it to the LaunchPad. Or possibly a pullup on one of the I2c lines. I don't recall if there is a physical pullup or if they are programmed in the TMS570. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sat, Aug 5, 2023 at 10:00 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I upgraded my pacsat test hardware to software version 0.1d. It didn't > run. I discovered that the software was hanging up when it tried to > initialize the i2c temp sensor. That is new in 0.1d. In > troubleshooting with Chris and Burns we discovered that the calls to the > i2c initialization code were misplaced. That was fixed and uploaded to > github as version 0.1e. > > Version 0.1e runs on my test hardware but gives an i2c error message > every time it attempts to read the temp. This could be a hardware fault > on my test hardware. I have checked the temp sensor and all pins seem > to be correctly connected and connectivity of the SDL and SCA lines with > the TMS570 board is OK. I will be connecting the temp sensor to a > raspberry pi and running tests on that component. > > In order to continue to use the test hardware I have commented out > line191 in TelemAndControlTask.c which simply reports an error by > calling debug_print(). Entering 'get temp' on the pacsat console still > shows the error message. > > I'm having too much fun!! > > Bill > > > ----------------------------------------------------------- > > 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 ver 0.1e update
by Bill Reed 05 Aug '23

05 Aug '23

I upgraded my pacsat test hardware to software version 0.1d. It didn't run. I discovered that the software was hanging up when it tried to initialize the i2c temp sensor. That is new in 0.1d. In troubleshooting with Chris and Burns we discovered that the calls to the i2c initialization code were misplaced. That was fixed and uploaded to github as version 0.1e. Version 0.1e runs on my test hardware but gives an i2c error message every time it attempts to read the temp. This could be a hardware fault on my test hardware. I have checked the temp sensor and all pins seem to be correctly connected and connectivity of the SDL and SCA lines with the TMS570 board is OK. I will be connecting the temp sensor to a raspberry pi and running tests on that component. In order to continue to use the test hardware I have commented out line191 in TelemAndControlTask.c which simply reports an error by calling debug_print(). Entering 'get temp' on the pacsat console still shows the error message. I'm having too much fun!! Bill

1 0

AX5043 Power Output
by Jim McCullers 03 Aug '23

03 Aug '23

The OnSemi AX5043 power study I mentioned last week can be found at: https://www.onsemi.cn/pub/collateral/and9314-d.pdf I've verified with duplicating their input numbers as best as possible and see similar results. As well, I performed a series of test using different criteria and again verified that the power output of the AX5043 is not a linear line but one that tapers off as the power is decreased. Therefore the formula given in the programming manual and duplicated by several developments is incorrect in setting power based on a percentage. In our use it is irrelative as we will be measuring the power output of the power amplifier and setting the AX5043 output as needed to drive the PA. However, it is good to know these things. As for harmonics; at 435.3 mhz with no output filtering the second harmonic is down by 34 db and the third by 44 db. With adequate output filtering on the power amplifier there should be no issues.

1 0

Pacsat dev mtg 8/3/2023
by Bill 03 Aug '23

03 Aug '23

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

1 0

Re: Pacsat ver 0.1d
by Chris Thompson 03 Aug '23

03 Aug '23

What are the symptoms? Does it fail to compile? 73 Chris On Thu, Aug 3, 2023, 10:41 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Haven't been able to get Pacsat ver 0.1d working. 0.1c worked fine. > Still trying to resolve this. > > Anyone else have 0.1d working? > > Bill > > > ----------------------------------------------------------- > > 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 ver 0.1d
by Bill Reed 03 Aug '23

03 Aug '23

Haven't been able to get Pacsat ver 0.1d working. 0.1c worked fine. Still trying to resolve this. Anyone else have 0.1d working? Bill

1 0