- pacsat-dev - mailman.amsat.org

task list as of 4/25/2024
by Bill 25 Apr '24

25 Apr '24

For our meeting this Thursday I would like to answer 2 questions: Are there any other tasks that should be on this list? Do we have the manpower/interest is completing these tasks for UND? Remaining Pacsat tasks as of 4/22/2024, revised 4/25/2024 Current Software Tasks: Software for monitor and control of 70cm power amplifier Host IHU telemetry interface Error reporting Minor issues ( commanding, telem control, etc ) Current Hardware Tasks: 7 components that do not fit layout Redesign power system and add to layout ( Vsys = 5.6v Buss voltages = 5.0v, 3.3v, and 1.2v) Correct I2C connection to temperature sensor Select crystal and add to layout Correct layout for T601 Power plane issues for Power Amp and 5V regulator Test 70cm Power Amp circuit Correct preamp bias issues Test receivers and determine differential vs single ended RX inputs Layout was done for Rev C schematic. Add Rev D changes Other tasks for a Flight Ready design: Measure power requirements Identify configuration changes for flight (config.h) Create Interface Control Document

1 0

Re: Possible issue with two AX5043s
by Bob Stricklin 25 Apr '24

25 Apr '24

I have been looking through the code and I can force PLLVCOI to 0x92 by setting this value at line 445 of ax5043-ax25.c and commenting out the other lines that write this register. However I also see PLLRANGINGA is changing and can be different for device 4 when I read registers. This is in the cal routine I think Burns has been referring too. This could be an SPI read issues also? This area of code is going to need more work. Bob On Apr 25, 2024, at 12:04 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org> wrote: Chis, It was showing up at boot and when I executed the test rx command. I can’t remember if or how much I tested before rewiring the receiver transformers then having the power supply go out. If I did test it was just for startup and I would have ignored the messages. I’ll reset the RAM once the updated code is in place. Thanks Jim Jim, The receiver frequency for each chip is stored in MRAM. So if you have them set to the same frequency that will stay there. You need to reset the MRAM to get the defaults. I think a ranging error will show up at boot, printed in the console, but I could be wrong. 73 Chris On Thu, Apr 25, 2024, 12:51 Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote: Bob, I finally got everything back in place and brought Blinky up last night. I'm getting a ranging error on device 0 and no messages from the others Same when I attempt the rx command. All four receivers are showing the same frequency. I checked this morning and I'm not running the latest code so have it downloaded and will test tonight if possible. If it goes well, I'll look into your question. Technically all four receives should have the same PLL value as the PLL should range over the two meter band. I'll look at that as well. Have to deep dive into the manual. I'm suffering from a stiff neck this week and not able to do much. Always something! Jim WA4CWI Looking at the feedback from the reading the AX5043 devices I see two have different PLL vales. The PLL sets the frequency conditions so this may be involved with the two devices that do not seem to be working. A listing of the register values reported is attached. Also the code I think is setting these registers. I have not had time to dig into the code. If an issue can be seen by someone that has looked at this code I would appreciate the help. Bob ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Possible issue with two AX5043s
by Jim McCullers 25 Apr '24

25 Apr '24

Chis, It was showing up at boot and when I executed the test rx command. I can’t remember if or how much I tested before rewiring the receiver transformers then having the power supply go out. If I did test it was just for startup and I would have ignored the messages. I’ll reset the RAM once the updated code is in place. Thanks Jim Jim, The receiver frequency for each chip is stored in MRAM. So if you have them set to the same frequency that will stay there. You need to reset the MRAM to get the defaults. I think a ranging error will show up at boot, printed in the console, but I could be wrong. 73 Chris On Thu, Apr 25, 2024, 12:51 Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: Bob, I finally got everything back in place and brought Blinky up last night. I'm getting a ranging error on device 0 and no messages from the others Same when I attempt the rx command. All four receivers are showing the same frequency. I checked this morning and I'm not running the latest code so have it downloaded and will test tonight if possible. If it goes well, I'll look into your question. Technically all four receives should have the same PLL value as the PLL should range over the two meter band. I'll look at that as well. Have to deep dive into the manual. I'm suffering from a stiff neck this week and not able to do much. Always something! Jim WA4CWI Looking at the feedback from the reading the AX5043 devices I see two have different PLL vales. The PLL sets the frequency conditions so this may be involved with the two devices that do not seem to be working. A listing of the register values reported is attached. Also the code I think is setting these registers. I have not had time to dig into the code. If an issue can be seen by someone that has looked at this code I would appreciate the help. Bob ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Possible issue with two AX5043s
by Chris Thompson 25 Apr '24

25 Apr '24

Jim, The receiver frequency for each chip is stored in MRAM. So if you have them set to the same frequency that will stay there. You need to reset the MRAM to get the defaults. I think a ranging error will show up at boot, printed in the console, but I could be wrong. 73 Chris On Thu, Apr 25, 2024, 12:51 Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Bob, > > I finally got everything back in place and brought Blinky up last night. > I'm getting a ranging error on device 0 and no messages from the others. > Same when I attempt the rx command. > All four receivers are showing the same frequency. > > I checked this morning and I'm not running the latest code so have it > downloaded and will test tonight if possible. > If it goes well, I'll look into your question. Technically all four > receives should have the same PLL value as the PLL should range over the > two > meter band. > I'll look at that as well. Have to deep dive into the manual. > > I'm suffering from a stiff neck this week and not able to do much. Always > something! > > Jim > WA4CWI > > Looking at the feedback from the reading the AX5043 devices I see two have > different PLL vales. The PLL sets the frequency conditions so this may be > involved with the two devices that do not seem to be working. > > A listing of the register values reported is attached. > > Also the code I think is setting these registers. I have not had time to > dig > into the code. If an issue can be seen by someone that has looked at this > code I would appreciate the help. > > > Bob > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Possible issue with two AX5043s
by Jim McCullers 25 Apr '24

25 Apr '24

Bob, I finally got everything back in place and brought Blinky up last night. I'm getting a ranging error on device 0 and no messages from the others. Same when I attempt the rx command. All four receivers are showing the same frequency. I checked this morning and I'm not running the latest code so have it downloaded and will test tonight if possible. If it goes well, I'll look into your question. Technically all four receives should have the same PLL value as the PLL should range over the two meter band. I'll look at that as well. Have to deep dive into the manual. I'm suffering from a stiff neck this week and not able to do much. Always something! Jim WA4CWI Looking at the feedback from the reading the AX5043 devices I see two have different PLL vales. The PLL sets the frequency conditions so this may be involved with the two devices that do not seem to be working. A listing of the register values reported is attached. Also the code I think is setting these registers. I have not had time to dig into the code. If an issue can be seen by someone that has looked at this code I would appreciate the help. Bob

1 0

Re: Remaining pacsat tasks for V1
by Chris Thompson 25 Apr '24

25 Apr '24

I've said before that most of the error reporting is missing. It needs to flow into the telemetry. There needs to be a review of robustness to make sure it will be reliable in failure scenarios. 73 Chris On Thu, Apr 25, 2024, 09:40 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Software: > > Maybe this is already done (Chris should know), but there should be a way > to tweak the Rx frequencies to be right 'on the money". The tweaking > commands are there as I recall, and it is easy to do the Tx frequency (just > watch it on a waterfall). But on Golf, at least, it was much easier just > to switch the Rx 5043s to transmit and adjust their frequency using a > waterfall too. Then when they are in receive mode, they receive on the > same frequency. That code may be there for one of the 5043s, but unless > Chris added it, probably not for all. (I say this because we will care > more that it be right on if the frequencies are coordinated etc etc. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Tue, Apr 23, 2024 at 11:34 AM Bill Reed via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I have been looking at the tasks that I think we would need to complete >> if we were to fly with UND in 2025. >> >> For our meeting this Thursday I would like to answer 2 questions: >> >> 1. Are there any other tasks that should be on this list? >> 2. Do we have the manpower/interest is completing these tasks for UND? >> >> Remaining Pacsat tasks as of 4/22/2024 >> >> Current Software Tasks: >> Software for monitor and control of 70cm power amplifier >> Host IHU telemetry interface >> Testing >> >> Current Hardware Tasks: >> 7 components that do not fit layout >> Redesign power system and add to layout >> ( Vsys = 5.6v Buss voltages = 5.0v, 3.3v, and 1.2v) >> Correct I2C connection to temperature sensor >> Select crystal and add to layout >> Correct layout for T601 >> Power plane issues for Power Amp and 5V regulator >> Test 70cm Power Amp circuit >> Correct preamp bias issues >> Test receivers and determine differential vs single ended RX inputs >> Layout was done for Rev C schematic. Add Rev D changes >> >> Other tasks for a Flight Ready design: >> Measure power requirements >> Identify configuration changes for flight >> Create Interface Control Document >> >> Bill >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Pacsat dev mtg 4/25/2024
by Bill 25 Apr '24

25 Apr '24

Pacsat dev mtg 4/25/2024 Thu, Apr 25, 2024 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/308552341 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3122 - One-touch: tel:+15713173122,,308552341# Access Code: 308-552-341 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 308 552 341 Or dial directly: 308552341(a)67.217.95.2 or 67.217.95.2##308552341 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Remaining pacsat tasks for V1
by Burns Fisher (AMSAT) 25 Apr '24

25 Apr '24

Software: Maybe this is already done (Chris should know), but there should be a way to tweak the Rx frequencies to be right 'on the money". The tweaking commands are there as I recall, and it is easy to do the Tx frequency (just watch it on a waterfall). But on Golf, at least, it was much easier just to switch the Rx 5043s to transmit and adjust their frequency using a waterfall too. Then when they are in receive mode, they receive on the same frequency. That code may be there for one of the 5043s, but unless Chris added it, probably not for all. (I say this because we will care more that it be right on if the frequencies are coordinated etc etc. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Apr 23, 2024 at 11:34 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I have been looking at the tasks that I think we would need to complete > if we were to fly with UND in 2025. > > For our meeting this Thursday I would like to answer 2 questions: > > 1. Are there any other tasks that should be on this list? > 2. Do we have the manpower/interest is completing these tasks for UND? > > Remaining Pacsat tasks as of 4/22/2024 > > Current Software Tasks: > Software for monitor and control of 70cm power amplifier > Host IHU telemetry interface > Testing > > Current Hardware Tasks: > 7 components that do not fit layout > Redesign power system and add to layout > ( Vsys = 5.6v Buss voltages = 5.0v, 3.3v, and 1.2v) > Correct I2C connection to temperature sensor > Select crystal and add to layout > Correct layout for T601 > Power plane issues for Power Amp and 5V regulator > Test 70cm Power Amp circuit > Correct preamp bias issues > Test receivers and determine differential vs single ended RX inputs > Layout was done for Rev C schematic. Add Rev D changes > > Other tasks for a Flight Ready design: > Measure power requirements > Identify configuration changes for flight > Create Interface Control Document > > Bill > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Possible issue with two AX5043s
by Bob Stricklin 25 Apr '24

25 Apr '24

Looking at the feedback from the reading the AX5043 devices I see two have different PLL vales. The PLL sets the frequency conditions so this may be involved with the two devices that do not seem to be working. A listing of the register values reported is attached. Also the code I think is setting these registers. I have not had time to dig into the code. If an issue can be seen by someone that has looked at this code I would appreciate the help. Bob

1 0

Remaining pacsat tasks for V1
by Bill Reed 23 Apr '24

23 Apr '24

I have been looking at the tasks that I think we would need to complete if we were to fly with UND in 2025. For our meeting this Thursday I would like to answer 2 questions: 1. Are there any other tasks that should be on this list? 2. Do we have the manpower/interest is completing these tasks for UND? Remaining Pacsat tasks as of 4/22/2024 Current Software Tasks: Software for monitor and control of 70cm power amplifier Host IHU telemetry interface Testing Current Hardware Tasks: 7 components that do not fit layout Redesign power system and add to layout ( Vsys = 5.6v Buss voltages = 5.0v, 3.3v, and 1.2v) Correct I2C connection to temperature sensor Select crystal and add to layout Correct layout for T601 Power plane issues for Power Amp and 5V regulator Test 70cm Power Amp circuit Correct preamp bias issues Test receivers and determine differential vs single ended RX inputs Layout was done for Rev C schematic. Add Rev D changes Other tasks for a Flight Ready design: Measure power requirements Identify configuration changes for flight Create Interface Control Document Bill

1 0