- pacsat-dev - mailman.amsat.org

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

29 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