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

Re: Dev meeting 5/30/2024 discussions
by Burns Fisher (AMSAT) 31 May '24

31 May '24

I have no problem with that as long as Cameron is not doing something for Golf (to be clear, Zach designed RTIHU V1.0 and V1.1. Cameron did V1.2, and may be called on to do a V1.3 cleanup.) I think that Cameron is working with Jeff Vollin and maybe some others on thruster research (an ASCENT program, I'd say). The point being some negotiation might be a good idea with Mike and/or Eric and Cameron himself. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, May 31, 2024 at 9:01 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Here is my summary of our discussions last night. > > Topic 1: > Mike Moore and the Fox Plus project have selected pacsat as one of the > payloads on their second > Fox Plus satellite, with launch planned for late 2025. > We feel that we should support that launch with our current version 1 > design. Consequently this > moves our ASCENT project to the status of a flight hardware provider. I > think we can support that > effort with the funds that remain from the ASCENT project. > The most significant task facing us is the clean up and build of the > existing pacsat prototype. In order > to accomplish that end, we need to add to our development team. I would > like to ask Cameron Castillo, > who did much of the RT-IHU layout, if he would join our engineering team > and help us complete our > Blinky layout. > > Topic 2: > I would like to ask Ron Fevig, N0UCV, if he would like to join our > engineering team. I would ask > him to do additional pacsat testing ( initially with our launchpad > hardware ) and provide documentation > for the pacsat user. Ron is currently an Amsat life member and a > professor at the University of North Dakota > Department of Space Studies. He is considering pacsat for a future > launch that is TBD. > > I solicit your opinions on these 2 Topics and I will not move forward > with implementation until I > have heard everyone's response. ( Chris and Bob responded last night) > > Bill > ( cell is 214 437-9555 if you want to discuss ) > > > ----------------------------------------------------------- > > 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: New Project
by Chris Thompson 31 May '24

31 May '24

I doubt the wooden transistors have much gain but perhaps a very low noise figure. Or perhaps they have forgotten to mention that it is still 90% silicon, metal and fiberglass with a wood shell... On Fri, May 31, 2024, 11:37 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Interesting thermal issues, I should think. > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, May 31, 2024 at 11:20 AM Jim McCullers via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Notty Pine Sat >> >> >> >> >> https://gizmodo.com/japan-launching-wooden-satellite-mitigate-debris-185150… >> >> >> >> Burns in a blaze of glory! >> >> ----------------------------------------------------------- >> >> 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: New Project
by Burns Fisher (AMSAT) 31 May '24

31 May '24

Interesting thermal issues, I should think. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, May 31, 2024 at 11:20 AM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Notty Pine Sat > > > > > https://gizmodo.com/japan-launching-wooden-satellite-mitigate-debris-185150… > > > > Burns in a blaze of glory! > > ----------------------------------------------------------- > > 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: Dev meeting 5/30/2024 discussions
by Jim McCullers 31 May '24

31 May '24

Sorry I had to moss the meeting last night. Appears it might be interesting. Bill, I would appreciate a call to discuss the discussion. Late Sunday afternoon might be best due to weekend family issues. It would be good to know how far ahead UND is on their design. If still in the early stage it would be benefical to have them use the RT-IHU layout and 104 connector pinouts to reduce the need of another board layout. The lack of a universal standard on that connector at least to the physical location is baffling. Bill, I might be able to call this afternoon. I'm waiting on my son to call with his plans for the day. He's in town for the weekend. Jim McCullers WA4CWI Here is my summary of our discussions last night. Topic 1: Mike Moore and the Fox Plus project have selected pacsat as one of the payloads on their second Fox Plus satellite, with launch planned for late 2025. We feel that we should support that launch with our current version 1 design. Consequently this moves our ASCENT project to the status of a flight hardware provider. I think we can support that effort with the funds that remain from the ASCENT project. The most significant task facing us is the clean up and build of the existing pacsat prototype. In order to accomplish that end, we need to add to our development team. I would like to ask Cameron Castillo, who did much of the RT-IHU layout, if he would join our engineering team and help us complete our Blinky layout. Topic 2: I would like to ask Ron Fevig, N0UCV, if he would like to join our engineering team. I would ask him to do additional pacsat testing ( initially with our launchpad hardware ) and provide documentation for the pacsat user. Ron is currently an Amsat life member and a professor at the University of North Dakota Department of Space Studies. He is considering pacsat for a future launch that is TBD. I solicit your opinions on these 2 Topics and I will not move forward with implementation until I have heard everyone's response. ( Chris and Bob responded last night) Bill ( cell is 214 437-9555 if you want to discuss ) ----------------------------------------------------------- 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

New Project
by Jim McCullers 31 May '24

31 May '24

Notty Pine Sat https://gizmodo.com/japan-launching-wooden-satellite-mitigate-debris-1851508 941 Burns in a blaze of glory!

1 0

Dev meeting 5/30/2024 discussions
by Bill Reed 31 May '24

31 May '24

Here is my summary of our discussions last night. Topic 1: Mike Moore and the Fox Plus project have selected pacsat as one of the payloads on their second Fox Plus satellite, with launch planned for late 2025. We feel that we should support that launch with our current version 1 design. Consequently this moves our ASCENT project to the status of a flight hardware provider. I think we can support that effort with the funds that remain from the ASCENT project. The most significant task facing us is the clean up and build of the existing pacsat prototype. In order to accomplish that end, we need to add to our development team. I would like to ask Cameron Castillo, who did much of the RT-IHU layout, if he would join our engineering team and help us complete our Blinky layout. Topic 2: I would like to ask Ron Fevig, N0UCV, if he would like to join our engineering team. I would ask him to do additional pacsat testing ( initially with our launchpad hardware ) and provide documentation for the pacsat user. Ron is currently an Amsat life member and a professor at the University of North Dakota Department of Space Studies. He is considering pacsat for a future launch that is TBD. I solicit your opinions on these 2 Topics and I will not move forward with implementation until I have heard everyone's response. ( Chris and Bob responded last night) Bill ( cell is 214 437-9555 if you want to discuss )

1 0

Pacsat dev mtg 5/30/2024
by Bill 30 May '24

30 May '24

Should be an interesting meeting tonight. We need to make some key decisions regarding Fox-Plus and University of North Dakota. Pacsat dev mtg 5/30/2024 Thu, May 30, 2024 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/460114245 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,,460114245# Access Code: 460-114-245 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 460 114 245 Or dial directly: 460114245(a)67.217.95.2 or 67.217.95.2##460114245 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Pacsat dev mtg 5/30/2024
by Bill 30 May '24

30 May '24

Should be an interesting meeting tonight. We need to make some key decisions regarding Fox-Plus and University of North Dakota. Pacsat dev mtg 5/30/2024 Thu, May 30, 2024 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/460114245 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,,460114245# Access Code: 460-114-245 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 460 114 245 Or dial directly: 460114245(a)67.217.95.2 or 67.217.95.2##460114245 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Fwd: pacsat on foxplus
by Jim McCullers 30 May '24

30 May '24

Definitely need the PCB layout. Good start. Are they V/U? Who’s building the antenna combiners? Jim FYI Attached is the preliminary Combo LIHU / Fox-Plus IHU PC104 connector. I have not "published" it yet as I'm waiting for feedback from the PCB designer. But I don't think it will change. PACSAT would get its power from the 5v_sw_1 or the 3v3_sw_1 depending on what you need. Both come from the ISISPACE EPS we are using. The [Rn] shown are zero ohm resistors which are populated for LIHU but not for Fox-Plus. Thanks, Mike On 5/29/24 11:33, Bill Reed wrote: Thanks. And can you direct me to your document for the Fox-Plus PC104? On 5/29/2024 10:10 AM, Mike Moore wrote: Very rough estimate for Fox-Plus-A is Q3 2025, with Fox-Plus-B to follow soon thereafter (Q4?) Mike K4MVM On 5/29/24 11:00, Bill Reed wrote: Do you have a rough estimate for a launch date? On 5/29/2024 9:45 AM, Mike Moore wrote: Bill, I am definitely interested in flying PACSAT. We will not be able to fly it on Fox-Plus-A (the first Fox-Plus) but want to put it on Fox-Plus-B. It would be flown as an experimental payload, so could be turned on and off by the OBC. The interface would be via the PC104 connector, so you will need to adapt to the Fox-Plus PC104. I will be on tonight's meeting, but I am going out of town on vacation for about 2 weeks starting tomorrow. Thanks and 73, Mike K4MVM On 5/28/24 16:05, Bill Reed wrote: Mike, I have heard rumors that the foxplus team might be interested in flying pacsat on a future flight. Can we discuss this at some point to see if a future flight might be possible. The pacsat team is completing the ASCENT proof of concept and we are evaluating what our next steps might be. Bill Reed Pacsat team lead bill(a)brconnect.com <mailto:bill@brconnect.com> Cell 214 437 9555

1 0

Re: Fwd: pacsat on foxplus
by Chris Thompson 29 May '24

29 May '24

Very good to hear. Thanks for forwarding. In addition to updating our connector it would be good to layout a timeline for work on other changes and testing. 73 Chris On Wed, May 29, 2024, 17:18 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > FYI > > > -------- Forwarded Message -------- > Subject: Re: pacsat on foxplus > Date: Wed, 29 May 2024 12:47:02 -0400 > From: Mike Moore <k4mvm.22(a)gmail.com> <k4mvm.22(a)gmail.com> > To: Bill Reed <bill(a)brconnect.com> <bill(a)brconnect.com> > > Attached is the preliminary Combo LIHU / Fox-Plus IHU PC104 connector. I > have not "published" it yet as I'm waiting for feedback from the PCB > designer. But I don't think it will change. PACSAT would get its power from > the 5v_sw_1 or the 3v3_sw_1 depending on what you need. Both come from the > ISISPACE EPS we are using. The [Rn] shown are zero ohm resistors which are > populated for LIHU but not for Fox-Plus. > > Thanks, > > Mike > > > On 5/29/24 11:33, Bill Reed wrote: > > Thanks. And can you direct me to your document for the Fox-Plus PC104? > > On 5/29/2024 10:10 AM, Mike Moore wrote: > > Very rough estimate for Fox-Plus-A is Q3 2025, with Fox-Plus-B to follow > soon thereafter (Q4?) > > Mike K4MVM > > > > On 5/29/24 11:00, Bill Reed wrote: > > Do you have a rough estimate for a launch date? > > On 5/29/2024 9:45 AM, Mike Moore wrote: > > Bill, > > I am definitely interested in flying PACSAT. We will not be able to fly it > on Fox-Plus-A (the first Fox-Plus) but want to put it on Fox-Plus-B. It > would be flown as an experimental payload, so could be turned on and off by > the OBC. The interface would be via the PC104 connector, so you will need > to adapt to the Fox-Plus PC104. > > I will be on tonight's meeting, but I am going out of town on vacation for > about 2 weeks starting tomorrow. > > Thanks and 73, > > Mike K4MVM > > > On 5/28/24 16:05, Bill Reed wrote: > > Mike, > > I have heard rumors that the foxplus team might be interested in flying > pacsat on a future flight. > > Can we discuss this at some point to see if a future flight might be > possible. The pacsat team is > completing the ASCENT proof of concept and we are evaluating what our next > steps might be. > > Bill Reed > Pacsat team lead > bill(a)brconnect.com > Cell 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: pacsat on foxplus
by Bill Reed 29 May '24

29 May '24

FYI -------- Forwarded Message -------- Subject: Re: pacsat on foxplus Date: Wed, 29 May 2024 12:47:02 -0400 From: Mike Moore <k4mvm.22(a)gmail.com> To: Bill Reed <bill(a)brconnect.com> Attached is the preliminary Combo LIHU / Fox-Plus IHU PC104 connector. I have not "published" it yet as I'm waiting for feedback from the PCB designer. But I don't think it will change. PACSAT would get its power from the 5v_sw_1 or the 3v3_sw_1 depending on what you need. Both come from the ISISPACE EPS we are using. The [Rn] shown are zero ohm resistors which are populated for LIHU but not for Fox-Plus. Thanks, Mike On 5/29/24 11:33, Bill Reed wrote: > Thanks. And can you direct me to your document for the Fox-Plus PC104? > > On 5/29/2024 10:10 AM, Mike Moore wrote: >> Very rough estimate for Fox-Plus-A is Q3 2025, with Fox-Plus-B to >> follow soon thereafter (Q4?) >> >> Mike K4MVM >> >> >> >> On 5/29/24 11:00, Bill Reed wrote: >>> Do you have a rough estimate for a launch date? >>> >>> On 5/29/2024 9:45 AM, Mike Moore wrote: >>>> Bill, >>>> >>>> I am definitely interested in flying PACSAT. We will not be able to >>>> fly it on Fox-Plus-A (the first Fox-Plus) but want to put it on >>>> Fox-Plus-B. It would be flown as an experimental payload, so could >>>> be turned on and off by the OBC. The interface would be via the >>>> PC104 connector, so you will need to adapt to the Fox-Plus PC104. >>>> >>>> I will be on tonight's meeting, but I am going out of town on >>>> vacation for about 2 weeks starting tomorrow. >>>> >>>> Thanks and 73, >>>> >>>> Mike K4MVM >>>> >>>> >>>> On 5/28/24 16:05, Bill Reed wrote: >>>>> Mike, >>>>> >>>>> I have heard rumors that the foxplus team might be interested in >>>>> flying pacsat on a future flight. >>>>> >>>>> Can we discuss this at some point to see if a future flight might >>>>> be possible. The pacsat team is >>>>> completing the ASCENT proof of concept and we are evaluating what >>>>> our next steps might be. >>>>> >>>>> Bill Reed >>>>> Pacsat team lead >>>>> bill(a)brconnect.com >>>>> Cell 214 437 9555 >>>>>

1 0

Bob Madison
by Bill Reed 25 May '24

25 May '24

Bob Madison is TBD.

1 0

Re: Quick tutorial on adding a console command to PacSat sw
by Bob Madison 24 May '24

24 May '24

Sounds like we need to do some code cleanup, refactoring, etc. Also some documentation. Comments? Bill On 5/24/2024 9:35 AM, Burns Fisher (AMSAT) via pacsat-dev wrote: > This is just how to add a command. I'll give an example that could > easily be used for temporarily raising the power. Adding it to the > MRAM requires additional work. > > This is all in the module ConsoleTask.c. I'll use the existing > command "raise tx freq" as an example. You need both the command > itself (raise tx freq) which can be any lower case string, and a label > (RaiseTxFreq) which has to be name that will work for a C variable. > > I'll use 'raise tx power' as an example to add, but you can look at > "raise tx freq" as an existing example. > > First create the label by adding it to the list of enums around line > 85. It does not matter where it goes in that list of enums. > enum { > nada=0 > ,getTemp > ,reset > ,resetBoth > ,startWD > ,preflight > ,raiseTxFreq <---- > > etc etc > } > > The commands are in three groups: Setup Commands, Debug Commands, and > Common Commands. Which one you choose only matters insofar as it > determines which help command they show up on. (helpall, helpdevo, > helpsetup, help). Anyway, chose one and add the new command. Example: > > commandPairs setupCommands[] = { > {"init new proc","Init DCT stuff that > will be set once for each unit",initSaved} > ,{"start tx tone", "Send a tone with > 5043", toneTx} > ,{"stop tx tone", "Stop sending the > tone",noToneTx} > ----> ,{"raise tx freq","Raise the telem > frequency by n Hz",RaiseTxFreq} > ,{"lower tx freq","Lower the telem > frequency by n Hz",LowerTxFreq} > ,{"raise rx freq","Raise the command > frequency by n Hz",RaiseRxFreq} > The text in the middle is printed when you say help. > > Then finally, there is a switch statement that takes up most of the > module. You want to add a new case with the label you created above. > For example > > case RaiseTxFreq:{ > int number = parseNumber(afterCommand); > DCTTxFreq += number; > printf("TxFreq=%d\n",DCTTxFreq); > quick_setfreq(AX5043Dev1, DCTTxFreq); > break; > } > > Notice that you can also use get a number that has been typed after > the command (i.e. raise tx freq 20). Also, this one just adds to the > static variable DCTTxFreq. Static meaning that it only exists within > the ConsoleTask.c module, but it does not get changed unless you > change it, or the next time the processor reboots. This also just > calls an AX5043 routine to change frequency. > > =============================== > I know Bob wants to be able to change the power. Do NOT look at > "GetRfPower", SelectRFPowerLevels, SetDCTDrivePower, etc. I think > Chris has 'disconnected' these, and besides they do not change the > power level immediately. They really just write into MRAM to be used > for another time. On Golf there is a routine named "ax5043_set_power" > but that has apparently been deprecated in pacsat. But I would > recommend some similar routine in one of the AX5043 modules under > device support rather than writing directly into the register in the > ConsoleTask.c module. We've tried to keep device-specific routines > together. > > I hope this is useful. > > 73, > > Burns Fisher, WB1FJ > /AMSAT(R) Engineering -- Flight Software/ > > ----------------------------------------------------------- > > 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

1 0

Quick tutorial on adding a console command to PacSat sw
by Burns Fisher (AMSAT) 24 May '24

24 May '24

This is just how to add a command. I'll give an example that could easily be used for temporarily raising the power. Adding it to the MRAM requires additional work. This is all in the module ConsoleTask.c. I'll use the existing command "raise tx freq" as an example. You need both the command itself (raise tx freq) which can be any lower case string, and a label (RaiseTxFreq) which has to be name that will work for a C variable. I'll use 'raise tx power' as an example to add, but you can look at "raise tx freq" as an existing example. First create the label by adding it to the list of enums around line 85. It does not matter where it goes in that list of enums. enum { nada=0 ,getTemp ,reset ,resetBoth ,startWD ,preflight ,raiseTxFreq <---- etc etc } The commands are in three groups: Setup Commands, Debug Commands, and Common Commands. Which one you choose only matters insofar as it determines which help command they show up on. (helpall, helpdevo, helpsetup, help). Anyway, chose one and add the new command. Example: commandPairs setupCommands[] = { {"init new proc","Init DCT stuff that will be set once for each unit",initSaved} ,{"start tx tone", "Send a tone with 5043", toneTx} ,{"stop tx tone", "Stop sending the tone",noToneTx} ----> ,{"raise tx freq","Raise the telem frequency by n Hz",RaiseTxFreq} ,{"lower tx freq","Lower the telem frequency by n Hz",LowerTxFreq} ,{"raise rx freq","Raise the command frequency by n Hz",RaiseRxFreq} The text in the middle is printed when you say help. Then finally, there is a switch statement that takes up most of the module. You want to add a new case with the label you created above. For example case RaiseTxFreq:{ int number = parseNumber(afterCommand); DCTTxFreq += number; printf("TxFreq=%d\n",DCTTxFreq); quick_setfreq(AX5043Dev1, DCTTxFreq); break; } Notice that you can also use get a number that has been typed after the command (i.e. raise tx freq 20). Also, this one just adds to the static variable DCTTxFreq. Static meaning that it only exists within the ConsoleTask.c module, but it does not get changed unless you change it, or the next time the processor reboots. This also just calls an AX5043 routine to change frequency. =============================== I know Bob wants to be able to change the power. Do NOT look at "GetRfPower", SelectRFPowerLevels, SetDCTDrivePower, etc. I think Chris has 'disconnected' these, and besides they do not change the power level immediately. They really just write into MRAM to be used for another time. On Golf there is a routine named "ax5043_set_power" but that has apparently been deprecated in pacsat. But I would recommend some similar routine in one of the AX5043 modules under device support rather than writing directly into the register in the ConsoleTask.c module. We've tried to keep device-specific routines together. I hope this is useful. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Pacsat dev mtg 5/23/2024
by Bill 23 May '24

23 May '24

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

1 0

Re: AX5043 Info
by Jim McCullers 23 May '24

23 May '24

Sorry, I thought I had mentioned Not Black Magic before. Excellent information except he did get the power setting incorrect which has been done by many as the documentation is incorrect. Probably the best write up I have seen and makes one wonder if he had inside information or played with it as a job. There are other code listings but BM is good. He also has a good one on FSK. I thought you were getting output from the AX5043 or I was confused about the 2 watt PA output post. Jim McCullers WA4CWI Here is a very nice posting by a 3rd party on setup of the AX5043. Everything is explained well. Some discussion on an analog mode near the bottom. https://www.notblackmagic.com/bitsnpieces/ax5043/ I still only see 0 dBm out of the AX5043. I do not have power register turned up all the way so I will try that next. I tried to post a software issue on get hub which included may code routine but this did not post properly. I am going to try again with a simpler issue. Still having some problem uploading things with going through a big ordeal here. I have corrections to code i will be trying to post later today. Bob

1 0

Re: AX5043 Info
by Chris Thompson 23 May '24

23 May '24

Hi Bob, We are aware of the not black magic post. I think Jonathan used it for his original prototype. I referred to it a lot. But his code does not work as written. It is a good starting point though. 73 Chris On Thu, May 23, 2024, 12:20 Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Here is a very nice posting by a 3rd party on setup of the AX5043. > Everything is explained well. Some discussion on an analog mode near the > bottom. > https://www.notblackmagic.com/bitsnpieces/ax5043/ > > > I still only see 0 dBm out of the AX5043. I do not have power register > turned up all the way so I will try that next. > > I tried to post a software issue on get hub which included may code > routine but this did not post properly. I am going to try again with a > simpler issue. Still having some problem uploading things with going > through a big ordeal here. I have corrections to code i will be trying to > post later today. > > > 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

AX5043 Info
by Bob Stricklin 23 May '24

23 May '24

Here is a very nice posting by a 3rd party on setup of the AX5043. Everything is explained well. Some discussion on an analog mode near the bottom. https://www.notblackmagic.com/bitsnpieces/ax5043/ I still only see 0 dBm out of the AX5043. I do not have power register turned up all the way so I will try that next. I tried to post a software issue on get hub which included may code routine but this did not post properly. I am going to try again with a simpler issue. Still having some problem uploading things with going through a big ordeal here. I have corrections to code i will be trying to post later today. Bob

1 0

I'm back from Dayton
by Bill Reed 22 May '24

22 May '24

Meeting this Thursday. Bill

1 0

RevD Schematic
by Bob Stricklin 22 May '24

22 May '24

I pushed up a copy of the RevD schematic under PacSatDocs->Hardware. This is not complete or finished but does have the changes I have been working with here relating to the PA and other fixes. I am currently biasing the gate of the PA with an external voltage supply set to 2.7 volts and 100 mA. This can be done with a voltage divider and a voltage reference later. Tenths of a volt mater here so best to have a good reference in the long run. This node pulls almost no current. The drain supply and current are setup by using a 50 ohm resistor in series with the 5V regulator. I see the voltage has dropped to about 4.9 volts due to series inductor and trace resistance. This can be improved on the next PCB layout. There is about 3 volts on the drain with this combination and the resulting overall current low enough so the current monitor MAX4995 does not shut things down when set to its max of 600 mA. This may need to be eliminated when we push for more power and get the drain bias up to 5V. More testing is needed. The gate is being driven with about 0 dB or RF and the AX5043 is capable of 16dBm according to the data sheet. There is currently a filter in this circuit to reduce harmonics which may need to be eliminated or optimized to get the power level up on the gate of the PA. The final output filter is doing a good job of stopping harmonics. However feeding harmonics into the PA can cause some heating and power loss. Having the TMS570 switch the PA power on only when transmitting will result in some power savings. When on the PA will have a substantial bias current. Some delay for power to settle may be needed. My goal here was to document my thought and work. Bob

1 0

PacSatSW
by Bob Stricklin 21 May '24

21 May '24

I just did a manual update from my MAC which has a key file for GitHub login. Should be fine with updated files. I need to add a keyhole to the linux computer I am using to see if thet allow CCS to work. Bob

1 0

Code is working
by Bob Stricklin 21 May '24

21 May '24

I now have the code turning the Rx and Tx LEDs on and off. Rx is always on now. Also should have PA power working but need to add the blue wires to this PCB. I will work on pushing code up to GitHub. Bob

1 0

Coding issue
by Bob Stricklin 21 May '24

21 May '24

I am having trouble getting the PA power and LEDs to switch the way I want. The most important code to me is in the tasked.c routine. This is were I am trying to do the power control and LED1 switching. I tried to PUSH my project into pacsatSW but apparently do not have permission to do so. Can this be changed? I raised an issue in issues and pasted my code in the issue. I would appreciate it if one of you can have a look and tell me what may fix the problem. My code is flagged with date 240519 N5BRG I have similar code blinking the LED3 for a heartbeat in interfaces->MET.c and this is working fine. Bob

1 0

Re: Progress
by Chris Thompson 18 May '24

18 May '24

Very good Bob, sounds great. 73 Chris On Sat, May 18, 2024, 10:43 Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I have the ability to make the power out of the AX5043 what I want it to > be thanks to the good suggestions. > > When I turn it up to max power I am seeing 0 dBm into the PA. At this > point the PA has 5 dBm out. To get to 2W we need 33 dBm to be at 2W however > we the amp would need to be higher by about 1 or 2 dBm to overcome the loss > of the final filter. I do have the PA held back by limiting its current and > only applying 5V and this time. I want to see the input side working > properly > before turning this up. I also want to change the code to allow the 5V be > turned on only when there is a need to send packets. Otherwise, the PA > continues to draw idle current and even though > the voltage drop is low there can be some heating. Eventually we will need > to look at the duty cycle of the PA and may need to plan on some sort of > heat sink/spreader which gets complicated > on a satellite. > > I am changing the LEDs to have one LED blink with a heart beat and one > each for TX and RX activity. > > There is no oscillations on PA at this point and the second harmonic is > not showing up past the filter at all. This is good news. > > Supply current goes up from 260 mA to about 360 mA when PA is active. This > will increase when we get more PA power output. > > I am working on the code to do power control and operate the LED. I have > one LED operating now and I see where to turn on TX LED. Bot TX and RX LEDs > can be controlled as part of the > interrupt routines coming from the AX5043 I believe. > > 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 18 May '24

18 May '24

I have the ability to make the power out of the AX5043 what I want it to be thanks to the good suggestions. When I turn it up to max power I am seeing 0 dBm into the PA. At this point the PA has 5 dBm out. To get to 2W we need 33 dBm to be at 2W however we the amp would need to be higher by about 1 or 2 dBm to overcome the loss of the final filter. I do have the PA held back by limiting its current and only applying 5V and this time. I want to see the input side working properly before turning this up. I also want to change the code to allow the 5V be turned on only when there is a need to send packets. Otherwise, the PA continues to draw idle current and even though the voltage drop is low there can be some heating. Eventually we will need to look at the duty cycle of the PA and may need to plan on some sort of heat sink/spreader which gets complicated on a satellite. I am changing the LEDs to have one LED blink with a heart beat and one each for TX and RX activity. There is no oscillations on PA at this point and the second harmonic is not showing up past the filter at all. This is good news. Supply current goes up from 260 mA to about 360 mA when PA is active. This will increase when we get more PA power output. I am working on the code to do power control and operate the LED. I have one LED operating now and I see where to turn on TX LED. Bot TX and RX LEDs can be controlled as part of the interrupt routines coming from the AX5043 I believe. Bob

1 0