- pacsat-dev - mailman.amsat.org

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/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

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/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

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

Blinky Lives
by Jim McCullers 22 Apr '24

22 Apr '24

1 0

Re: Pacsat dev mtg 4/18/2024
by Corey Minyard 18 Apr '24

18 Apr '24

This is the Thursday this month I can't make it. Talk to you next week. -corey On Thu, Apr 18, 2024 at 06:47:15PM +0000, Bill via pacsat-dev wrote: > Pacsat dev mtg 4/18/2024 > Thu, Apr 18, 2024 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/347194453 > > 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,,347194453# > > Access Code: 347-194-453 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 347 194 453 > Or dial directly: 347194453(a)67.217.95.2 or 67.217.95.2##347194453 > > > 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 4/18/2024
by Bill 18 Apr '24

18 Apr '24

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

1 0

Re: Blinky dimensions
by Burns Fisher (AMSAT) 17 Apr '24

17 Apr '24

Oh, ok....Indeed the location of the PC104 is not specified in the LTM ICD as I thought it was. That's odd. But Bill just said that he updated the Blinky with its PC104 location. Are they the same? Which one did you really want? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Apr 17, 2024 at 1:30 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > > Bill, > > I have revised the drawing to include the connector location based on the > hole locations in the PCB drill file. > > I don’t think the LTC document provides an exact location for these > holes. This board should match other AMSAT boards unless the connector was > relocated. It is quite easy to accidentally select the connector in KiCAD > and end up with it in a slightly different location. > > It would be good to research the connector drawing and see what the pin > spacings are. I thought they were 2 mm. The dimensions I show here are > slightly less than 2 mm in the length dimension. > Probably still work fine. > > The dimensions in the LTC document are in metric and the dimensions used > on the PCB layout are in mils. You can obtain more accurate placement with > KiCad because of the way it handles rounding. > > I will push a copy of this to the GitHub Hardware rev C board. > > Bob > > > > > On Apr 17, 2024, at 9:19 AM, Bill Reed <bill(a)brconnect.com> wrote: > > Your drawing does not show the position of the 102 pin connector. > > Does the position of the 102 pin connector match the LTM document? > On 4/16/2024 7:28 PM, Bob Stricklin wrote: > > Bill, > > Take a look at this ZIP file and you will find a mechanical drawing of the > PCB. > > > https://github.com/AMSAT-NA/PacSatDocs/blob/main/Hardware/PCB/PacSat_Dev_Re… > > The 104 pin connector is not specified here but the hole locations for the > connector are included in the drill file. > I will take a look at the dimensions and revise the drawing to include > three of the connector corner pins later. > > These dimensions match the LTM document. > > Bob > > > > > On Apr 16, 2024, at 11:24 AM, Bill Reed via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > Do we have a document that specifies: > > 1. Blinky overall dimensions > 2. Blinky mounting hole positions > 3. Blinky 104 pin connector position > > 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 >

1 0

Re: Blinky dimensions
by Bob Stricklin 17 Apr '24

17 Apr '24

Bill, I have revised the drawing to include the connector location based on the hole locations in the PCB drill file. I don’t think the LTC document provides an exact location for these holes. This board should match other AMSAT boards unless the connector was relocated. It is quite easy to accidentally select the connector in KiCAD and end up with it in a slightly different location. It would be good to research the connector drawing and see what the pin spacings are. I thought they were 2 mm. The dimensions I show here are slightly less than 2 mm in the length dimension. Probably still work fine. The dimensions in the LTC document are in metric and the dimensions used on the PCB layout are in mils. You can obtain more accurate placement with KiCad because of the way it handles rounding. I will push a copy of this to the GitHub Hardware rev C board. Bob On Apr 17, 2024, at 9:19 AM, Bill Reed <bill(a)brconnect.com<mailto:bill@brconnect.com>> wrote: Your drawing does not show the position of the 102 pin connector. Does the position of the 102 pin connector match the LTM document? On 4/16/2024 7:28 PM, Bob Stricklin wrote: Bill, Take a look at this ZIP file and you will find a mechanical drawing of the PCB. https://github.com/AMSAT-NA/PacSatDocs/blob/main/Hardware/PCB/PacSat_Dev_Re… The 104 pin connector is not specified here but the hole locations for the connector are included in the drill file. I will take a look at the dimensions and revise the drawing to include three of the connector corner pins later. These dimensions match the LTM document. Bob On Apr 16, 2024, at 11:24 AM, Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Do we have a document that specifies: 1. Blinky overall dimensions 2. Blinky mounting hole positions 3. Blinky 104 pin connector position Bill ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://mailman.amsat.org/>

1 0