October 2023 - pacsat-dev - mailman.amsat.org

Re: In the hotel
by Mark L. Hammond 20 Oct '23

20 Oct '23

Hi Chris! Glad to hear that you're here! We are meeting the Board now, until noon or so. It's an open meeting, not closed as originally announced. Welcome to join us. There is an AMSAT sign outside our room. Mark L. Hammond [N8MH] AMSAT Director and Command Station On Fri, Oct 20, 2023 at 9:51 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I'm in the hotel if anyone would like to meet up and discuss or practice > the presentation. I see we are on at 3.15pm today. > > Bill, we should make sure all the hardware works and discuss how/when we > will set it up in the room. > > 73 > Chris > > ----------------------------------------------------------- > > 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

In the hotel
by Chris Thompson 20 Oct '23

20 Oct '23

I'm in the hotel if anyone would like to meet up and discuss or practice the presentation. I see we are on at 3.15pm today. Bill, we should make sure all the hardware works and discuss how/when we will set it up in the room. 73 Chris

1 0

Re: Power Point Slide for AMSAT Symposium
by Jim McCullers 16 Oct '23

16 Oct '23

Looks good Bob. Jim McCullers WA4CWI

1 0

Power Point Slide for AMSAT Symposium
by Bob Stricklin 16 Oct '23

16 Oct '23

1 0

PacSat dev mtg 10/12/2023
by Bill 12 Oct '23

12 Oct '23

PacSat dev mtg 10/12/2023 Thu, Oct 12, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/951846397 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (646) 749-3122 - One-touch: tel:+16467493122,,951846397# Access Code: 951-846-397 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 951 846 397 Or dial directly: 951846397(a)67.217.95.2 or 67.217.95.2##951846397 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: MRAM Layout has changed
by Burns Fisher (AMSAT) 12 Oct '23

12 Oct '23

I just got a chance to look at the code. As you may known the MRAM is divided into two partitions. Partition 0 contains the various states info that we want to keep as well as FileUploadsTable (and I don't really know what that is). But at the start and end of this partition is a uint32_t containing the version number of the MRAM layout. The version number is in the code as a constant (MRAMmap.h MRAM_VERSION), and it is written into the mram when it is initialized. If you change the structure, you SHOULD change the version number, but if you don't and the length of the stuff in the middle changes, you will get the warning. If you do change the version number in the code but don't init the MRAM you also get the warning. HOWEVER, of course if the MRAM gets messed up even if the structure is unchanged, you get the same message. One thing between the two version cells is InProcessFileUpload_t FileUploadsTable[MAX_IN_PROCESS_FILE_UPLOADS]; I don't know what this is, but given that it is an array, it seems a likely possibility that it could have overflowed and wiped out the second version cell and cause your problem. It would also flow into partition 1, which contains the file system, so that could also get messed up. I hope this helps... 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Oct 12, 2023 at 1:38 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Yes. I've don't it. I will monitor to see when I get it again. > > 73 > Chris > > On Thu, Oct 12, 2023, 12:26 Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Have you done the clear mram to start again? How long before you get the >> error again? >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Thu, Oct 12, 2023 at 12:07 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I'm unsure if it really messes up the receiver or if that is just a >>> coincidence. I made the receiver work by rebooting the windows laptop that >>> controls the ground station. Go figure. >>> >>> But the MRAM definitely sees this issue. I see the message at reboot. >>> >>> 73 >>> Chris >>> >>> On Thu, Oct 12, 2023, 11:00 Burns Fisher (AMSAT) via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Hmm. There is a place in the MRAM (maybe one at the beginning and one >>>> at the end?) with a version number. When you init the MRAM, the version >>>> number in the code (I think it is in the header file that defines the >>>> contents of the MRAM) is written into that/those spot/s. Then it compares, >>>> I think in the console code every command (it is really easy to miss >>>> otherwise). >>>> I don't think I compare it anywhere else. >>>> >>>> Assuming you did not change the layout, my first thought would be that >>>> when we put the file system into the MRAM, the version number is somehow >>>> overlayed so it gets changed when some particular thing happens in the file >>>> system. Or maybe the file system overflows? If it is that latter (an >>>> overflow) that could end up corrupting the file system. Would that explain >>>> why the receiver is not working? Of course you can clear mram..I suppose >>>> that means you have to re-init the file system too? >>>> >>>> 73, >>>> >>>> Burns Fisher, WB1FJ >>>> *AMSAT(R) Engineering -- Flight Software* >>>> >>>> >>>> On Thu, Oct 12, 2023 at 10:41 AM Chris Thompson via pacsat-dev < >>>> pacsat-dev(a)amsat.org> wrote: >>>> >>>>> Burns (and others), >>>>> >>>>> I think there is a bug that corrupts MRAM. From time to time I get >>>>> the message "*****MRAM layout has changed. You must issue clear >>>>> mram******" even though I have not changed the layout. What causes that? >>>>> It looks like it may then cause an issue where the receiver does not work. >>>>> >>>>> 73 >>>>> Chris >>>>> >>>>> -- >>>>> Chris E. Thompson >>>>> chrisethompson(a)gmail.com >>>>> g0kla(a)arrl.net >>>>> >>>>> ----------------------------------------------------------- >>>>> >>>>> 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 >>> >> >> ----------------------------------------------------------- >> >> 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: MRAM Layout has changed
by Chris Thompson 12 Oct '23

12 Oct '23

Yes. I've don't it. I will monitor to see when I get it again. 73 Chris On Thu, Oct 12, 2023, 12:26 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Have you done the clear mram to start again? How long before you get the > error again? > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Thu, Oct 12, 2023 at 12:07 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I'm unsure if it really messes up the receiver or if that is just a >> coincidence. I made the receiver work by rebooting the windows laptop that >> controls the ground station. Go figure. >> >> But the MRAM definitely sees this issue. I see the message at reboot. >> >> 73 >> Chris >> >> On Thu, Oct 12, 2023, 11:00 Burns Fisher (AMSAT) via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Hmm. There is a place in the MRAM (maybe one at the beginning and one >>> at the end?) with a version number. When you init the MRAM, the version >>> number in the code (I think it is in the header file that defines the >>> contents of the MRAM) is written into that/those spot/s. Then it compares, >>> I think in the console code every command (it is really easy to miss >>> otherwise). >>> I don't think I compare it anywhere else. >>> >>> Assuming you did not change the layout, my first thought would be that >>> when we put the file system into the MRAM, the version number is somehow >>> overlayed so it gets changed when some particular thing happens in the file >>> system. Or maybe the file system overflows? If it is that latter (an >>> overflow) that could end up corrupting the file system. Would that explain >>> why the receiver is not working? Of course you can clear mram..I suppose >>> that means you have to re-init the file system too? >>> >>> 73, >>> >>> Burns Fisher, WB1FJ >>> *AMSAT(R) Engineering -- Flight Software* >>> >>> >>> On Thu, Oct 12, 2023 at 10:41 AM Chris Thompson via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Burns (and others), >>>> >>>> I think there is a bug that corrupts MRAM. From time to time I get the >>>> message "*****MRAM layout has changed. You must issue clear mram******" >>>> even though I have not changed the layout. What causes that? It looks >>>> like it may then cause an issue where the receiver does not work. >>>> >>>> 73 >>>> Chris >>>> >>>> -- >>>> Chris E. Thompson >>>> chrisethompson(a)gmail.com >>>> g0kla(a)arrl.net >>>> >>>> ----------------------------------------------------------- >>>> >>>> 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 >> > > ----------------------------------------------------------- > > 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: MRAM Layout has changed
by Burns Fisher (AMSAT) 12 Oct '23

12 Oct '23

Have you done the clear mram to start again? How long before you get the error again? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Oct 12, 2023 at 12:07 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I'm unsure if it really messes up the receiver or if that is just a > coincidence. I made the receiver work by rebooting the windows laptop that > controls the ground station. Go figure. > > But the MRAM definitely sees this issue. I see the message at reboot. > > 73 > Chris > > On Thu, Oct 12, 2023, 11:00 Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Hmm. There is a place in the MRAM (maybe one at the beginning and one at >> the end?) with a version number. When you init the MRAM, the version >> number in the code (I think it is in the header file that defines the >> contents of the MRAM) is written into that/those spot/s. Then it compares, >> I think in the console code every command (it is really easy to miss >> otherwise). >> I don't think I compare it anywhere else. >> >> Assuming you did not change the layout, my first thought would be that >> when we put the file system into the MRAM, the version number is somehow >> overlayed so it gets changed when some particular thing happens in the file >> system. Or maybe the file system overflows? If it is that latter (an >> overflow) that could end up corrupting the file system. Would that explain >> why the receiver is not working? Of course you can clear mram..I suppose >> that means you have to re-init the file system too? >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Thu, Oct 12, 2023 at 10:41 AM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Burns (and others), >>> >>> I think there is a bug that corrupts MRAM. From time to time I get the >>> message "*****MRAM layout has changed. You must issue clear mram******" >>> even though I have not changed the layout. What causes that? It looks >>> like it may then cause an issue where the receiver does not work. >>> >>> 73 >>> Chris >>> >>> -- >>> Chris E. Thompson >>> chrisethompson(a)gmail.com >>> g0kla(a)arrl.net >>> >>> ----------------------------------------------------------- >>> >>> 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: MRAM Layout has changed
by Chris Thompson 12 Oct '23

12 Oct '23

I'm unsure if it really messes up the receiver or if that is just a coincidence. I made the receiver work by rebooting the windows laptop that controls the ground station. Go figure. But the MRAM definitely sees this issue. I see the message at reboot. 73 Chris On Thu, Oct 12, 2023, 11:00 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Hmm. There is a place in the MRAM (maybe one at the beginning and one at > the end?) with a version number. When you init the MRAM, the version > number in the code (I think it is in the header file that defines the > contents of the MRAM) is written into that/those spot/s. Then it compares, > I think in the console code every command (it is really easy to miss > otherwise). > I don't think I compare it anywhere else. > > Assuming you did not change the layout, my first thought would be that > when we put the file system into the MRAM, the version number is somehow > overlayed so it gets changed when some particular thing happens in the file > system. Or maybe the file system overflows? If it is that latter (an > overflow) that could end up corrupting the file system. Would that explain > why the receiver is not working? Of course you can clear mram..I suppose > that means you have to re-init the file system too? > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Thu, Oct 12, 2023 at 10:41 AM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Burns (and others), >> >> I think there is a bug that corrupts MRAM. From time to time I get the >> message "*****MRAM layout has changed. You must issue clear mram******" >> even though I have not changed the layout. What causes that? It looks >> like it may then cause an issue where the receiver does not work. >> >> 73 >> Chris >> >> -- >> Chris E. Thompson >> chrisethompson(a)gmail.com >> g0kla(a)arrl.net >> >> ----------------------------------------------------------- >> >> 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: MRAM Layout has changed
by Burns Fisher (AMSAT) 12 Oct '23

12 Oct '23

Hmm. There is a place in the MRAM (maybe one at the beginning and one at the end?) with a version number. When you init the MRAM, the version number in the code (I think it is in the header file that defines the contents of the MRAM) is written into that/those spot/s. Then it compares, I think in the console code every command (it is really easy to miss otherwise). I don't think I compare it anywhere else. Assuming you did not change the layout, my first thought would be that when we put the file system into the MRAM, the version number is somehow overlayed so it gets changed when some particular thing happens in the file system. Or maybe the file system overflows? If it is that latter (an overflow) that could end up corrupting the file system. Would that explain why the receiver is not working? Of course you can clear mram..I suppose that means you have to re-init the file system too? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Oct 12, 2023 at 10:41 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns (and others), > > I think there is a bug that corrupts MRAM. From time to time I get the > message "*****MRAM layout has changed. You must issue clear mram******" > even though I have not changed the layout. What causes that? It looks > like it may then cause an issue where the receiver does not work. > > 73 > Chris > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > 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