- pacsat-dev - mailman.amsat.org

Pacsat dev mtg 6-15-2023
by Bill 15 Jun '23

15 Jun '23

Pacsat dev mtg 6-15-2023 Thu, Jun 15, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/553436741 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (408) 650-3123 - One-touch: tel:+14086503123,,553436741# Access Code: 553-436-741 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 553 436 741 Or dial directly: 553436741(a)67.217.95.2 or 67.217.95.2##553436741 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Pacsat main updated
by Chris Thompson 13 Jun '23

13 Jun '23

I merged version 0.1c into main. This has a few bug fixes to the AX25 data link state machine and cleans up a few things. I am going to take a break from working on the uplink/downlink and catalog all the TODO items that I noted as I worked on the code. They are mostly to do with error cases. I'll make a list of what needs to be worked on and how that will fit with logging errors and the telemetry we need to store/send. The AX25 connection needs a thorough test if anyone has time to work on that. Let me know if you find issues or log them on github. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Small software update
by Burns Fisher (AMSAT) 10 Jun '23

10 Jun '23

I updated the pacsat software to print something more reasonable about the MRAM size. (What I described to Bill was really not right...I simply had not previously indicated what I was displaying!) The version number is also updated to V0.1b (from a). Please remember to update this when you push changes to the repository so we can keep track of what we are using. (I think there are really a number of different versions all labelled V01.a---if you get b it will be the latest as of today). 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Pacsat console
by Corey Minyard 10 Jun '23

10 Jun '23

On Sat, Jun 10, 2023 at 03:06:47PM +0000, Bill Reed via pacsat-dev wrote: > My sign in returns: > > > > AMSAT-NA PacSat Console > > Flight Software X0.1a (built on Jun 10 2023 at 08:43:48) > > Compiled *RELEASE* > > **X, E, U, or DEBUG Version: Not configured for flight** > > Watchdog NOT Enabled > > Using FreeRTOS withOUT premption enabled; > > Free heap size is 55944 > > Flash memory size 1Mb+256Kb; MRAM size is 0x124, structure size is 0x124 > > > > > > Free heap size after tasks launched: 19056 > > *** NO RTC: SET THE UNIX TIME BEFORE UPLOADING ANY TEST FILES *** > > Starting RX with AX5043Device 0, vhf=1 9600bps=0, freq=145835000 > > Starting TX with AX5043Device 1, vhf=0 9600bps=0, freq=435760000 > > Pacsat> > > > > What does this line mean? > > Flash memory size 1Mb+256Kb; MRAM size is 0x124, structure size is 0x124 The MRAM size is a bit misleading, it's the size of the information data structure held at the beginning of MRAM. It's not the whole MRAM. -corey > > ----------------------------------------------------------- > > 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: Pacsat console
by Burns Fisher (AMSAT) 10 Jun '23

10 Jun '23

The flash memory size could have been written as 1.25 megabytes, I suppose. It was just taking the size and dividing by 1 meg and then the remainder by 1 k. The MRAM line has not been updated since a) the file system was added and b) since Jim used those very small MRAMs for the test board. The structure size is the size of the "status info" structure that is not part of the file system, and that is correct (in bytes). The MRAM size is not correct--it assumed the smallest MRAM was 1M. Use "get mram size" to get the actual size. I'll fix that at some point. Thanks for noticing! I usually totally ignore the startup info :-) Pacsat>get mram size MRAM Address Size=2 Partition 0 size=292, partition 1=65244 MRAM0 size is 16KBytes, MRAM1 size is 16KBytes MRAM2 size is 16KBytes, MRAM3 size is 16KBytes Notice that "Partition 0 size=292" is decimal for 0x124, the number shown above. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sat, Jun 10, 2023 at 11:06 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > My sign in returns: > > AMSAT-NA PacSat Console > Flight Software X0.1a (built on Jun 10 2023 at 08:43:48) > Compiled *RELEASE* > **X, E, U, or DEBUG Version: Not configured for flight** > Watchdog NOT Enabled > Using FreeRTOS withOUT premption enabled; > Free heap size is 55944 > Flash memory size 1Mb+256Kb; MRAM size is 0x124, structure size is 0x124 > > > Free heap size after tasks launched: 19056 > *** NO RTC: SET THE UNIX TIME BEFORE UPLOADING ANY TEST FILES *** > Starting RX with AX5043Device 0, vhf=1 9600bps=0, freq=145835000 > Starting TX with AX5043Device 1, vhf=0 9600bps=0, freq=435760000 > Pacsat> > > What does this line mean? > Flash memory size 1Mb+256Kb; MRAM size is 0x124, structure size is 0x124 > > > ----------------------------------------------------------- > > 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 console
by Bill Reed 10 Jun '23

10 Jun '23

My sign in returns: AMSAT-NA PacSat Console Flight Software X0.1a (built on Jun 10 2023 at 08:43:48) Compiled *RELEASE* **X, E, U, or DEBUG Version: Not configured for flight** Watchdog NOT Enabled Using FreeRTOS withOUT premption enabled; Free heap size is 55944 Flash memory size 1Mb+256Kb; MRAM size is 0x124, structure size is 0x124 Free heap size after tasks launched: 19056 *** NO RTC: SET THE UNIX TIME BEFORE UPLOADING ANY TEST FILES *** Starting RX with AX5043Device 0, vhf=1 9600bps=0, freq=145835000 Starting TX with AX5043Device 1, vhf=0 9600bps=0, freq=435760000 Pacsat> What does this line mean? Flash memory size 1Mb+256Kb; MRAM size is 0x124, structure size is 0x124

1 0

Re: Pacsat dev mtg 6-8-2023
by Burns Fisher (AMSAT) 08 Jun '23

08 Jun '23

As usual, on the 2nd Thursday of the month I will not be there. Nothing to report. I've been doing Golf when I have a chance to do AMSAT stuff this week. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Jun 8, 2023 at 3:14 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg 6-8-2023 > Thu, Jun 8, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/248915285 > > 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,,248915285# > > Access Code: 248-915-285 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 248 915 285 > Or dial directly: 248915285(a)67.217.95.2 or 67.217.95.2##248915285 > > > 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 6-8-2023
by Bill 08 Jun '23

08 Jun '23

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

1 0

Robert would like to attend tomorrow
by Jonathan Brandenburg 06 Jun '23

06 Jun '23

I won't be able to attend this week's meeting (I'll be attending a show)... But, Robert Bankston would like to attend (he spaced the last time you invited him). Could you please send Robert the invite for this week's PACSAT dev meeting? Jonathan -- jbrandenburg(a)amsat.org

1 0

Re: Open Source Satellite - Tuxera's Reliance Edge
by Jonathan Brandenburg 06 Jun '23

06 Jun '23

I'm authorized to respond to such queries. But in this case you're far more likely to sound like you know what you're talking about. Perhaps I could join you in the "interview". Could that make sense? Jonathan p.s. I'm attending SmallSat this year in Logan, UT. On 6/6/2023 8:51 PM, Chris Thompson via pacsat-dev wrote: > I agree it sounds like a good opportunity but Bill or Jonathan will > likely need to make that call. > > Either way, we should probably write a one page summary of what we are > trying to do, to cover situations like this. > > 73 > Chris > > On Tue, Jun 6, 2023, 15:48 Corey Minyard via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > I just got this, it could be a good opportunity for advertising what > we are doing. How would we handle this? > > -corey > > ---------- Forwarded message --------- > From: Corey Minyard <minyard(a)acm.org> > Date: Tue, Jun 6, 2023 at 2:46 PM > Subject: [justin.engle(a)tuxera.com: Open Source Satellite - Tuxera's > Reliance Edge] > To: <tcminyard(a)gmail.com> > > > ----- Forwarded message from Justin Engle > <justin.engle(a)tuxera.com> ----- > > Date: Tue, 6 Jun 2023 17:28:53 +0000 (GMT) > From: Justin Engle <justin.engle(a)tuxera.com> > To: "minyard(a)acm.org" <minyard(a)acm.org> > Subject: Open Source Satellite - Tuxera's Reliance Edge > > Good afternoon, Corey! > > When we last spoke, you said that you had been working on a small sat > that was running on open-source software (included Reliance Edge). > > We are going to Small Sat '23 in August and are looking for a story > like the one you are working on to help us get a stronger presence in > the small sat sector. Please let me know when you have some time to > talk. We would love to hear how Reliance Edge has been utilized in > your project as well as get some feedback from you as well. > > If you have any technical questions, give me a heads up and I can have > an FAE join our call to assist. > > Thanks! > > Justin Engle > Tuxera > Inside Sales Manager Americas > P: (567) 356-1459 > E: justin.engle(a)tuxera.com > W: www.tuxera.com <http://www.tuxera.com> > > > ----- End forwarded message ----- > > ----------------------------------------------------------- > > 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 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 -- jbrandenburg(a)amsat.org

1 0