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

Re: Expenses
by Burns Fisher (AMSAT) 30 Apr '24

30 Apr '24

How did you submit them Bob? You are going to be at Hamvention, right? I'll introduce you to the treasurer. He is really very good, so I'd guess that either he did not get your older submission, or Jerry forgot to approve it or something. How much is it? Jerry, are you on this list? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Apr 30, 2024 at 8:56 AM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > All, > > I received a check for $96 yesterday which covers the expense submitted on > 2/26/24 but still have not received a check for the 2/10/24 expense. > > Thanks to AMSAT for the $96 refund. > > Bob N5BRG > > ----------------------------------------------------------- > > 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

Expenses
by Bob Stricklin 30 Apr '24

30 Apr '24

All, I received a check for $96 yesterday which covers the expense submitted on 2/26/24 but still have not received a check for the 2/10/24 expense. Thanks to AMSAT for the $96 refund. Bob N5BRG

1 0

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

26 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

Blinky Lives
by Jim McCullers 23 Apr '24

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

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:[email protected]>> 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:[email protected]>> 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:[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<https://mailman.amsat.org/>

1 0

Re: Blinky RTC
by Chris Thompson 17 Apr '24

17 Apr '24

I also don't think we need a battery to keep time for the pacsat file system. We only need accurate time for file uploads and to expire old files. Those processes can be automatically suspended if the time is not set. The time is then fixed by sending a command that sets the clock. If we need accurate time for another reason, such as an experiment, then that could change of course. For telemetry we can fall back on using reset and uptime. 73 Chris On Tue, Apr 16, 2024, 20:36 Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I would say a battery is not needed. > > The clock chip is the only device on the board that has a volatile memory > and the current required to keep the data in place is very low. With the > capacitors on the PCB the time should be maintained over a month. This is > something we can test however it would be difficult to obtain an exact time > to live because when you power up to read the clock the caps will be > recharged. > > Assuming it will be possible to set the time shortly before launch or even > after launch it will be best not to have the added burden of a battery. > > Bob > > > On Apr 16, 2024, at 2:18 PM, Bill Reed via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > > > Should the blinky RTC have a battery? > > > > > > ----------------------------------------------------------- > > > > 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

Re: Blinky RTC
by Bob Stricklin 17 Apr '24

17 Apr '24

I would say a battery is not needed. The clock chip is the only device on the board that has a volatile memory and the current required to keep the data in place is very low. With the capacitors on the PCB the time should be maintained over a month. This is something we can test however it would be difficult to obtain an exact time to live because when you power up to read the clock the caps will be recharged. Assuming it will be possible to set the time shortly before launch or even after launch it will be best not to have the added burden of a battery. Bob > On Apr 16, 2024, at 2:18 PM, Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Should the blinky RTC have a battery? > > > ----------------------------------------------------------- > > 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: Blinky RTC
by Burns Fisher (AMSAT) 16 Apr '24

16 Apr '24

The eval board has a super-cap that lasts for several days without a battery. I don't know if that is how it is designed on Blinky, but I'd guess yes. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Apr 16, 2024 at 3:18 PM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Should the blinky RTC have a battery? > > > ----------------------------------------------------------- > > 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

Blinky RTC
by Bill Reed 16 Apr '24

16 Apr '24

Should the blinky RTC have a battery?

1 0

Blinky dimensions
by Bill Reed 16 Apr '24

16 Apr '24

Do we have a document that specifies: 1. Blinky overall dimensions 2. Blinky mounting hole positions 3. Blinky 104 pin connector position Bill

1 0

Re: URGENT Possible Pacsat launch
by Bob Stricklin 15 Apr '24

15 Apr '24

Sorry just now seeing these emails… I am not motivated to get involved in supporting any of the new projects. I am ok with helping to fix any issues with the board we have built but beyond that I would not like to be involved. I do not feel AMSAT is really behind these projects and has too many issues in the organization at this point for me to be willing to work on a project. Bob > On Apr 15, 2024, at 11:06 AM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Bill, > > Make certain you get a good idea of what they are doing for communications. > With a 3U I would assume they have communication requirements and plans defined. > We have to insure the addition of Pacsat would not result in interference to either party. > > Jim McCullers > WA4CWI > > > Team, > > Well, we learned from the budget situation that our ASCENT direction was to build a"proof of concept" solution. > I am not sure at this point why we are restricted and if this is an AMSAT officer (Jerry or Robert) or a BOD restriction. > > With that in mind, I was contacted over the weekend by a university that wants to launch pacsat. > The University of North Dakota is launching a 3U cubesat, probably in mid to late 2025. They have a commitment for an ELANA launch but no firm dates yet. They have .5U available out of 3U. > > So we need to make a decision here: > > 1. Do we want to support this launch? (Don't know yet how much support they will need. Probably lots.) > > 2. Do we have the time to provide support? > > 3. If you think it is good timing, I will invite the UND project lead ( Dr. Ron Fevig ) to our Thursday meeting. > > If we decide to move forward with this we will need to get Jerry's permission to move beyond a pure ASCENT project. > > Please let me know your feelings ASAP. I have a meeting with Dr. Fevig this afternoon and will try to better understand their requirements. > > Please let me know your feelings ASAP. ( 2nd request) I want to kill this if we don't think we can do it. > > 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

Timekeeping on Fox and Golf
by Burns Fisher (AMSAT) 15 Apr '24

15 Apr '24

I wrote this in a private email but given a lot of new people who had no experience with Fox, it seems worth posting to the list (and also to PacSat whose OBC is similar, although it does keep UTC somehow/somewhere, I think). ===================== Ever since Fox-1A and up through the Golf, the OBCs do not have a Real Time Clock (RTC), have never had a clue about the actual UTC time, and have only kept any time as accurate as their built-in timed interrupts are. The OBCs main time metric is Epochs (in general, the number of processor resets) and Seconds since the last Epoch start. The main thing that these times get used for are timestamps on telemetry, and the most critical thing is to ensure that telemetry downlinks can be sorted by time order on the ground even if they arrive at the AMSAT server out of order. In addition, on the ground we (really Alan Biddle) determines the UTC time of each reset. Given that, we can display the UTC telemetry time in FoxTelem. Sometimes this is more useful if it is reasonably accurate (like if you want to correlate something on the s/c to an orbital location like the South Atlantic Anomaly or the aurora or something like that, but generally even that is not terribly critical. All the software is geared to that Epoch/Second timekeeping, but on Golf I also planned to downlink the UTC time matched with a s/c time when/if it was available (there is a GPS on the Ettus, but whether it could give UTC without CoCom is unclear) in order to save Alan some work. Now that we will have a CoCom GPS available we will certainly have the time, but I have no plans to use it on the OBC except to downlink as above. The UTC time also comes with GPS coordinates so that time can be used to convert a coordinate list to TLE, but it is a timestamp, not realtime. The OBC still does not have an accurate RTC nor does it need one. Note to avoid a few emails: At least the ST32L151 processor does contain an RTC, but we don't use it. It would require an extra super-accurate crystal, plus it still has to be set in orbit, since we can't have any power on before release in orbit. And why do we use the epoch/seconds hoke? Because that is accurate from the moment the processor reboots. It does not have to wait for a GPS lock or a UTC uplink. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: URGENT Possible Pacsat launch
by Jim McCullers 15 Apr '24

15 Apr '24

Bill, Make certain you get a good idea of what they are doing for communications. With a 3U I would assume they have communication requirements and plans defined. We have to insure the addition of Pacsat would not result in interference to either party. Jim McCullers WA4CWI Team, Well, we learned from the budget situation that our ASCENT direction was to build a"proof of concept" solution. I am not sure at this point why we are restricted and if this is an AMSAT officer (Jerry or Robert) or a BOD restriction. With that in mind, I was contacted over the weekend by a university that wants to launch pacsat. The University of North Dakota is launching a 3U cubesat, probably in mid to late 2025. They have a commitment for an ELANA launch but no firm dates yet. They have .5U available out of 3U. So we need to make a decision here: 1. Do we want to support this launch? (Don't know yet how much support they will need. Probably lots.) 2. Do we have the time to provide support? 3. If you think it is good timing, I will invite the UND project lead ( Dr. Ron Fevig ) to our Thursday meeting. If we decide to move forward with this we will need to get Jerry's permission to move beyond a pure ASCENT project. Please let me know your feelings ASAP. I have a meeting with Dr. Fevig this afternoon and will try to better understand their requirements. Please let me know your feelings ASAP. ( 2nd request) I want to kill this if we don't think we can do it. 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

Re: URGENT Possible Pacsat launch
by Chris Thompson 15 Apr '24

15 Apr '24

I also agree with all the comments. I would tend to take any opportunity for a launch because they are so rare. But find out some more and we can make a decision. 73 Chris On Mon, Apr 15, 2024, 10:59 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > good comments, thanks. 1 week delay is good idea. > > On 4/15/2024 9:25 AM, Jim McCullers via pacsat-dev wrote: > > Bill, > > > > I believe it would be best for you to do the meeting, get a firm idea of > where they are, then make a decision. > > I would also suggest the invitation to join our meeting be a week later > so we can here your thoughts from the conversation and make a > go/no-go/maybe decision before getting in deeper. > > > > Jonathan explained to me way back when the project was a "proof of > concept" but with a possibility of flight. > > I'm still too green to know the whys of what's going on. > > > > Jim McCullers > > WA4CWI > > > > > > > > Team, > > > > Well, we learned from the budget situation that our ASCENT direction was > to build a"proof of concept" solution. > > I am not sure at this point why we are restricted and if this is an > AMSAT officer (Jerry or Robert) or a BOD restriction. > > > > With that in mind, I was contacted over the weekend by a university that > wants to launch pacsat. > > The University of North Dakota is launching a 3U cubesat, probably in > mid to late 2025. They have a commitment for an ELANA launch but no firm > dates yet. They have .5U available out of 3U. > > > > So we need to make a decision here: > > > > 1. Do we want to support this launch? (Don't know yet how much support > they will need. Probably lots.) > > > > 2. Do we have the time to provide support? > > > > 3. If you think it is good timing, I will invite the UND project lead ( > Dr. Ron Fevig ) to our Thursday meeting. > > > > If we decide to move forward with this we will need to get Jerry's > permission to move beyond a pure ASCENT project. > > > > Please let me know your feelings ASAP. I have a meeting with Dr. Fevig > this afternoon and will try to better understand their requirements. > > > > Please let me know your feelings ASAP. ( 2nd request) I want to kill > this if we don't think we can do it. > > > > 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 > > ----------------------------------------------------------- > > 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: URGENT Possible Pacsat launch
by Bill Reed 15 Apr '24

15 Apr '24

good comments, thanks. 1 week delay is good idea. On 4/15/2024 9:25 AM, Jim McCullers via pacsat-dev wrote: > Bill, > > I believe it would be best for you to do the meeting, get a firm idea of where they are, then make a decision. > I would also suggest the invitation to join our meeting be a week later so we can here your thoughts from the conversation and make a go/no-go/maybe decision before getting in deeper. > > Jonathan explained to me way back when the project was a "proof of concept" but with a possibility of flight. > I'm still too green to know the whys of what's going on. > > Jim McCullers > WA4CWI > > > > Team, > > Well, we learned from the budget situation that our ASCENT direction was to build a"proof of concept" solution. > I am not sure at this point why we are restricted and if this is an AMSAT officer (Jerry or Robert) or a BOD restriction. > > With that in mind, I was contacted over the weekend by a university that wants to launch pacsat. > The University of North Dakota is launching a 3U cubesat, probably in mid to late 2025. They have a commitment for an ELANA launch but no firm dates yet. They have .5U available out of 3U. > > So we need to make a decision here: > > 1. Do we want to support this launch? (Don't know yet how much support they will need. Probably lots.) > > 2. Do we have the time to provide support? > > 3. If you think it is good timing, I will invite the UND project lead ( Dr. Ron Fevig ) to our Thursday meeting. > > If we decide to move forward with this we will need to get Jerry's permission to move beyond a pure ASCENT project. > > Please let me know your feelings ASAP. I have a meeting with Dr. Fevig this afternoon and will try to better understand their requirements. > > Please let me know your feelings ASAP. ( 2nd request) I want to kill this if we don't think we can do it. > > 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

Re: URGENT Possible Pacsat launch
by Jim McCullers 15 Apr '24

15 Apr '24

Bill, I believe it would be best for you to do the meeting, get a firm idea of where they are, then make a decision. I would also suggest the invitation to join our meeting be a week later so we can here your thoughts from the conversation and make a go/no-go/maybe decision before getting in deeper. Jonathan explained to me way back when the project was a "proof of concept" but with a possibility of flight. I'm still too green to know the whys of what's going on. Jim McCullers WA4CWI Team, Well, we learned from the budget situation that our ASCENT direction was to build a"proof of concept" solution. I am not sure at this point why we are restricted and if this is an AMSAT officer (Jerry or Robert) or a BOD restriction. With that in mind, I was contacted over the weekend by a university that wants to launch pacsat. The University of North Dakota is launching a 3U cubesat, probably in mid to late 2025. They have a commitment for an ELANA launch but no firm dates yet. They have .5U available out of 3U. So we need to make a decision here: 1. Do we want to support this launch? (Don't know yet how much support they will need. Probably lots.) 2. Do we have the time to provide support? 3. If you think it is good timing, I will invite the UND project lead ( Dr. Ron Fevig ) to our Thursday meeting. If we decide to move forward with this we will need to get Jerry's permission to move beyond a pure ASCENT project. Please let me know your feelings ASAP. I have a meeting with Dr. Fevig this afternoon and will try to better understand their requirements. Please let me know your feelings ASAP. ( 2nd request) I want to kill this if we don't think we can do it. 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

Re: URGENT Possible Pacsat launch
by Burns Fisher (AMSAT) 15 Apr '24

15 Apr '24

I'm concerned about time for sure. I don't really have any. But I'm wondering if UND is also the place that is talking about using an LTM. In which case, the integration of these two things is an issue. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Apr 15, 2024 at 10:06 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Team, > > Well, we learned from the budget situation that our ASCENT direction was > to build a"proof of concept" solution. > I am not sure at this point why we are restricted and if this is an > AMSAT officer (Jerry or Robert) or a BOD restriction. > > With that in mind, I was contacted over the weekend by a university that > wants to launch pacsat. > The University of North Dakota is launching a 3U cubesat, probably in > mid to late 2025. They have > a commitment for an ELANA launch but no firm dates yet. They have .5U > available out of 3U. > > So we need to make a decision here: > > 1. Do we want to support this launch? (Don't know yet how much support > they will need. Probably lots.) > > 2. Do we have the time to provide support? > > 3. If you think it is good timing, I will invite the UND project lead ( > Dr. Ron Fevig ) to our Thursday meeting. > > If we decide to move forward with this we will need to get Jerry's > permission to move beyond a pure ASCENT project. > > Please let me know your feelings ASAP. I have a meeting with Dr. Fevig > this afternoon and will try to better understand > their requirements. > > Please let me know your feelings ASAP. ( 2nd request) I want to kill > this if we don't think we can do it. > > 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

URGENT Possible Pacsat launch
by Bill Reed 15 Apr '24

15 Apr '24

Team, Well, we learned from the budget situation that our ASCENT direction was to build a"proof of concept" solution. I am not sure at this point why we are restricted and if this is an AMSAT officer (Jerry or Robert) or a BOD restriction. With that in mind, I was contacted over the weekend by a university that wants to launch pacsat. The University of North Dakota is launching a 3U cubesat, probably in mid to late 2025. They have a commitment for an ELANA launch but no firm dates yet. They have .5U available out of 3U. So we need to make a decision here: 1. Do we want to support this launch? (Don't know yet how much support they will need. Probably lots.) 2. Do we have the time to provide support? 3. If you think it is good timing, I will invite the UND project lead ( Dr. Ron Fevig ) to our Thursday meeting. If we decide to move forward with this we will need to get Jerry's permission to move beyond a pure ASCENT project. Please let me know your feelings ASAP. I have a meeting with Dr. Fevig this afternoon and will try to better understand their requirements. Please let me know your feelings ASAP. ( 2nd request) I want to kill this if we don't think we can do it. Bill

1 0

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

11 Apr '24

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

1 0

TI regulator
by Bob Stricklin 05 Apr '24

05 Apr '24

I just checked what I said and the TI chip is an LDO regulator. The other two are switching regulators. Bob

1 0

Pacsat dev mtg 4-4-2024
by Bill 04 Apr '24

04 Apr '24

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

1 0