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

Re: pacsat dev mtg 10-26-2023
by Corey Minyard 26 Oct '23

26 Oct '23

On Thu, Oct 26, 2023 at 06:29:07PM +0000, Bill via pacsat-dev wrote: > > I cannot attend this evening. Bob Stricklin will host tonight. I also cannot attend, I'll be on the road. Sounds like the presentation went great. Talk to you next week. -corey > > pacsat dev mtg 10-26-2023 > Thu, Oct 26, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/821196965 > > 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,,821196965# > > Access Code: 821-196-965 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 821 196 965 > Or dial directly: 821196965(a)67.217.95.2 or 67.217.95.2##821196965 > > > 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 10-26-2023
by Bill 26 Oct '23

26 Oct '23

I cannot attend this evening. Bob Stricklin will host tonight. pacsat dev mtg 10-26-2023 Thu, Oct 26, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/821196965 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,,821196965# Access Code: 821-196-965 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 821 196 965 Or dial directly: 821196965(a)67.217.95.2 or 67.217.95.2##821196965 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Plastic boxes for Prototype board and the CubSat sized prototype
by Bob Stricklin 26 Oct '23

26 Oct '23

I just realized I put the support for the USB connector on the wrong end so I have changed it in this version. A new file may also solve your issue. Bob On Oct 26, 2023, at 11:46 AM, Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Hummm, I did this in Solidworks using inches. The box should be 5.16 inches by 2.66 inches by .46 inches. These are the other dimensions. Is there an option for you to select inches or mm in your software. I could export this in other formats or in mm if that would help. Bob On Oct 26, 2023, at 10:34 AM, Chris Thompson <chrisethompson(a)gmail.com<mailto:chrisethompson@gmail.com>> wrote: Bob, It looks like the size of the box was lost in the export. The STL box is 2.9 x 0.46 x 5.41 mm and will use just 0.44cm of filament according to my slicer. That does not sound right. When I load it into the printer I can not see the box on the preview. I can try to scale it up but not sure what factor to use. 73 Chris On Thu, Oct 26, 2023 at 11:07 AM Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Chris, Here are STL files. The 64kb file is the box for the prototype board you have. Let me know if you see any changes that need to be made. The think the SMA antenna landing places on the larger box will need to be changed. Bob On Oct 26, 2023, at 9:47 AM, Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Bob, Very interesting. If you send over the STL files then I will try printing it here. It would be nice to have a box. 73 Chris On Thu, Oct 26, 2023, 10:21 Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: All, As some of you know, I managed to break the USB connector off the prototype board while taking it to the AMSAT symposium. I have repaired it by cutting the end off a USB cable and soldering the leads on directly. It's a little kluge but working. To protect my connections and to protect the board a little I designed a box and that will be 3D printed. If this works out and you want one for your board I can pass along the info later. It will take about two weeks to get the box and check it out. There is an area provided for the USB connector. The connector on the PCB will come off without a lot of angular pulling force. Also designed a box for the larger CubeSat prototype. Attaching a copy of this too. I add two places to mount an SMA connector for antennas which may be a stiff piece of wire or connected to a remote antenna. I have order one of these to try out. This is a half baked idea and open for suggestions about how to improve on it. I have two covers one for each side so you can get access to parts for testing or changes. The cost for me to make all four parts is about $46 including shipping and handling. I use something called Craftcloud.com<http://craftcloud.com/>. Bob ----------------------------------------------------------- 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/> ----------------------------------------------------------- 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/> ----------------------------------------------------------- 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/> -- Chris E. Thompson chrisethompson(a)gmail.com<mailto:chrisethompson@gmail.com> g0kla(a)arrl.net<mailto:g0kla@arrl.net> ----------------------------------------------------------- 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

1 0

Re: Plastic boxes for Prototype board and the CubSat sized prototype
by Chris Thompson 26 Oct '23

26 Oct '23

Bob, It looks like the size of the box was lost in the export. The STL box is 2.9 x 0.46 x 5.41 mm and will use just 0.44cm of filament according to my slicer. That does not sound right. When I load it into the printer I can not see the box on the preview. I can try to scale it up but not sure what factor to use. 73 Chris On Thu, Oct 26, 2023 at 11:07 AM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris, > > Here are STL files. The 64kb file is the box for the prototype board you > have. > Let me know if you see any changes that need to be made. > > The think the SMA antenna landing places on the larger box will need to be > changed. > > > Bob > > > > > > On Oct 26, 2023, at 9:47 AM, Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > Bob, > > Very interesting. If you send over the STL files then I will try printing > it here. It would be nice to have a box. > > 73 > Chris > > On Thu, Oct 26, 2023, 10:21 Bob Stricklin via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > All, > > As some of you know, I managed to break the USB connector off the > prototype board while taking it to the AMSAT symposium. > I have repaired it by cutting the end off a USB cable and soldering the > leads on directly. It's a little kluge but working. > > To protect my connections and to protect the board a little I designed a > box and that will be 3D printed. If this works out > and you want one for your board I can pass along the info later. It will > take about two weeks to get the box and check it out. > There is an area provided for the USB connector. The connector on the PCB > will come off without a lot of angular pulling force. > > Also designed a box for the larger CubeSat prototype. Attaching a copy of > this too. I add two places to mount an SMA connector for antennas > which may be a stiff piece of wire or connected to a remote antenna. I > have order one of these to try out. This is a half baked idea and open for > suggestions about > how to improve on it. I have two covers one for each side so you can get > access to parts for testing or changes. > > The cost for me to make all four parts is about $46 including shipping and > handling. I use something called Craftcloud.com <http://craftcloud.com/>. > > Bob > > > > > ----------------------------------------------------------- > > 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 > > > > ----------------------------------------------------------- > > 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

2 1

Re: Plastic boxes for Prototype board and the CubSat sized prototype
by Bob Stricklin 26 Oct '23

26 Oct '23

Chris, Here are STL files. The 64kb file is the box for the prototype board you have. Let me know if you see any changes that need to be made. The think the SMA antenna landing places on the larger box will need to be changed. Bob On Oct 26, 2023, at 9:47 AM, Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Bob, Very interesting. If you send over the STL files then I will try printing it here. It would be nice to have a box. 73 Chris On Thu, Oct 26, 2023, 10:21 Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: All, As some of you know, I managed to break the USB connector off the prototype board while taking it to the AMSAT symposium. I have repaired it by cutting the end off a USB cable and soldering the leads on directly. It's a little kluge but working. To protect my connections and to protect the board a little I designed a box and that will be 3D printed. If this works out and you want one for your board I can pass along the info later. It will take about two weeks to get the box and check it out. There is an area provided for the USB connector. The connector on the PCB will come off without a lot of angular pulling force. Also designed a box for the larger CubeSat prototype. Attaching a copy of this too. I add two places to mount an SMA connector for antennas which may be a stiff piece of wire or connected to a remote antenna. I have order one of these to try out. This is a half baked idea and open for suggestions about how to improve on it. I have two covers one for each side so you can get access to parts for testing or changes. The cost for me to make all four parts is about $46 including shipping and handling. I use something called Craftcloud.com<http://craftcloud.com/>. Bob ----------------------------------------------------------- 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/> ----------------------------------------------------------- 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

1 0

Update on PCB prototype
by Bob Stricklin 26 Oct '23

26 Oct '23

All, Regarding the prototype PCB that is being built, the assembly house did a 1X check on the parts vs the layout and came back with the attached list of issues. I have addressed these issues as stated under comments. The PCB was released to be manufactured. The lead-time is stated to be about 2 weeks. I also pushed a complete set of the design files to GitHub PacSat-Dev_Docs. All the parts needed are either in hand at the assembly house or they are on order (5 parts) with no issues on delivery known at this time. Jumper coax lines are also on order. I would expect it to take at least 2 weeks for the assembly folks to setup and assemble the PCBs once they are received. So we should see prototypes around the end of November or first part of December. Also attaching an assembly drawing I made with some details. The assemble house wanted a detailed assembly drawing so I made 3D cad views of several parts that were not already in KiCAD so they would show up in the 3D rendering of the PCB from and back. These are placed on the GitHub as STEP files. There is also an assembly drawing output from Kicad showing placement of the parts on the PCB to aid in assembly. I am documenting this so everyone knows what is going on and to maintain a full open source position. Bob

1 0

Re: Plastic boxes for Prototype board and the CubSat sized prototype
by Chris Thompson 26 Oct '23

26 Oct '23

Bob, Very interesting. If you send over the STL files then I will try printing it here. It would be nice to have a box. 73 Chris On Thu, Oct 26, 2023, 10:21 Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > All, > > As some of you know, I managed to break the USB connector off the > prototype board while taking it to the AMSAT symposium. > I have repaired it by cutting the end off a USB cable and soldering the > leads on directly. It's a little kluge but working. > > To protect my connections and to protect the board a little I designed a > box and that will be 3D printed. If this works out > and you want one for your board I can pass along the info later. It will > take about two weeks to get the box and check it out. > There is an area provided for the USB connector. The connector on the PCB > will come off without a lot of angular pulling force. > > Also designed a box for the larger CubeSat prototype. Attaching a copy of > this too. I add two places to mount an SMA connector for antennas > which may be a stiff piece of wire or connected to a remote antenna. I > have order one of these to try out. This is a half baked idea and open for > suggestions about > how to improve on it. I have two covers one for each side so you can get > access to parts for testing or changes. > > The cost for me to make all four parts is about $46 including shipping and > handling. I use something called Craftcloud.com. > > Bob > > > > > ----------------------------------------------------------- > > 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

Plastic boxes for Prototype board and the CubSat sized prototype
by Bob Stricklin 26 Oct '23

26 Oct '23

All, As some of you know, I managed to break the USB connector off the prototype board while taking it to the AMSAT symposium. I have repaired it by cutting the end off a USB cable and soldering the leads on directly. It's a little kluge but working. To protect my connections and to protect the board a little I designed a box and that will be 3D printed. If this works out and you want one for your board I can pass along the info later. It will take about two weeks to get the box and check it out. There is an area provided for the USB connector. The connector on the PCB will come off without a lot of angular pulling force. Also designed a box for the larger CubeSat prototype. Attaching a copy of this too. I add two places to mount an SMA connector for antennas which may be a stiff piece of wire or connected to a remote antenna. I have order one of these to try out. This is a half baked idea and open for suggestions about how to improve on it. I have two covers one for each side so you can get access to parts for testing or changes. The cost for me to make all four parts is about $46 including shipping and handling. I use something called Craftcloud.com<http://Craftcloud.com>. Bob

1 0

Presentation - Congratulations
by Jim McCullers 21 Oct '23

21 Oct '23

Great presentation guys. Just got through looking at it. Great demo Chris and it worked! Far better than one I saw last night. Look forward to getting the review next Thursday and hopefully will be at next year's meeting. On an AX5043 note, I've made the first steps in restructuring the code to support four receivers and adding more capabilities to the AX5043. As in all things, the learning curve has requested it's penance. Next up will be the two receiver test on 144 and 70cm. For for the test the PacSat code has been disabled and the APRS decoder from the Raspberry PI version inserted so I can use my Kenwood HT to easily switch between bands. We could use a third AX5043 on the board for full PacSat testing but there's enough to do with the restructuring. Easy to switch back to PacSat when the restructure is complete. 73, Jim McCullers WA4CWI

1 0

Re: In the hotel
by Chris Thompson 20 Oct '23

20 Oct '23

Thanks Mark, I'll consider that. 73 Chris On Fri, Oct 20, 2023, 08:55 Mark L. Hammond via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > 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/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: 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/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

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

MRAM Layout has changed
by Chris Thompson 12 Oct '23

12 Oct '23

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

1 0

Demo files uploaded
by Chris Thompson 12 Oct '23

12 Oct '23

I have checked in the demo files. They are in the Demo folder in AMSAT-NA/PacSatDocs/Demo This consists of the Demo script and the two folders for the setup and operation on the demo. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: "Mostly paused" for a couple weeks
by Chris Thompson 12 Oct '23

12 Oct '23

I don't know what to say, but our thoughts are with you and your family. Chris On Thu, Oct 12, 2023, 08:17 Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Some of y'all know but not all... I'm in the midst of addressing a > family tragedy (my sister took her life this past weekend). As a result, > I'm mostly pausing my AMSAT responsibilities to shed some load for a > couple weeks. > > Please understand if I'm not particularly responsive to AMSAT emails. I > anticipate having things wrangled into submission by the time Symposium > rolls around. > > Jonathan > > -- > Jonathan Brandenburg, KF5IDY > > > ----------------------------------------------------------- > > 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

"Mostly paused" for a couple weeks
by Jonathan Brandenburg 12 Oct '23

12 Oct '23

Some of y'all know but not all... I'm in the midst of addressing a family tragedy (my sister took her life this past weekend). As a result, I'm mostly pausing my AMSAT responsibilities to shed some load for a couple weeks. Please understand if I'm not particularly responsive to AMSAT emails. I anticipate having things wrangled into submission by the time Symposium rolls around. Jonathan -- Jonathan Brandenburg, KF5IDY

1 0

Re: Annual Meeting proceedings
by Bill Reed 09 Oct '23

09 Oct '23

Revised docs have been submitted for publication. 🙂 Bill On 10/7/2023 12:41 PM, Chris Thompson via pacsat-dev wrote: > I reviewed the two documents and made some minor changes. I also > generated pdfs as we are publishing these and they are also checked > back into git. > > 73 > Chris > > On Fri, Oct 6, 2023 at 4:31 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > wrote: > > Sure, ok with me. > 73, > > Burns Fisher, WB1FJ > /AMSAT(R) Engineering -- Flight Software/ > > > On Fri, Oct 6, 2023 at 4:30 PM Chris Thompson via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > I am good with that assuming Burns is. I can read through them > this weekend and see if they need any changes. > > > 73 > Chris > > On Fri, Oct 6, 2023, 14:58 Bill Reed via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > We discussed this briefly last night. > > Why don't we publish these docs in the proceedings? > > "PACSAT BBS Operations", 10 Nov 2022, by Chris > > and > > "PACSAT Software Architecture", 19 Mar 2023 by Chris and Burns > > 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 > > > > -- > 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 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

1 0

Re: Annual Meeting proceedings
by Chris Thompson 07 Oct '23

07 Oct '23

I reviewed the two documents and made some minor changes. I also generated pdfs as we are publishing these and they are also checked back into git. 73 Chris On Fri, Oct 6, 2023 at 4:31 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: > Sure, ok with me. > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, Oct 6, 2023 at 4:30 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I am good with that assuming Burns is. I can read through them this >> weekend and see if they need any changes. >> >> >> 73 >> Chris >> >> On Fri, Oct 6, 2023, 14:58 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> >> wrote: >> >>> We discussed this briefly last night. >>> >>> Why don't we publish these docs in the proceedings? >>> >>> "PACSAT BBS Operations", 10 Nov 2022, by Chris >>> >>> and >>> >>> "PACSAT Software Architecture", 19 Mar 2023 by Chris and Burns >>> >>> 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 >> > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Annual Meeting proceedings
by Chris Thompson 06 Oct '23

06 Oct '23

I am good with that assuming Burns is. I can read through them this weekend and see if they need any changes. 73 Chris On Fri, Oct 6, 2023, 14:58 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > We discussed this briefly last night. > > Why don't we publish these docs in the proceedings? > > "PACSAT BBS Operations", 10 Nov 2022, by Chris > > and > > "PACSAT Software Architecture", 19 Mar 2023 by Chris and Burns > > 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

Annual Meeting proceedings
by Bill Reed 06 Oct '23

06 Oct '23

We discussed this briefly last night. Why don't we publish these docs in the proceedings? "PACSAT BBS Operations", 10 Nov 2022, by Chris and "PACSAT Software Architecture", 19 Mar 2023 by Chris and Burns Bill

1 0

Re: Pacsat dev mtg 10/5/2023
by Corey Minyard 06 Oct '23

06 Oct '23

I was going to try to make this, but I'm in California right now and won't be able to. -corey - AE5KM On Thu, Oct 5, 2023 at 1:45 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Pacsat dev mtg 10/5/2023 > Thu, Oct 5, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/851719045 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (312) 757-3121 > - One-touch: tel:+13127573121,,851719045# > > Access Code: 851-719-045 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 851 719 045 > Or dial directly: 851719045(a)67.217.95.2 or 67.217.95.2##851719045 > > > 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 10/5/2023
by Bill 05 Oct '23

05 Oct '23

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

1 0

Re: Watchdog
by Chris Thompson 03 Oct '23

03 Oct '23

Yes, at least part of the errors structure is saved on a reset to indicate what happened. I have not changed any of that. 73 Chris On Tue, Oct 3, 2023, 14:13 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > The STM32L processor knows how to disable the WD when you are at > breakpoints in the debugger. If the TMS does not do that, it is the only > reason I can think of that there would be a problem. > > And just a check: Is the s/w still set up so that the errors structure is > not wiped out by a reset? In other words, that the WD flags will be > available after the WD triggers and the system reboots? I seem to remember > that was a fair bit of hassle to make that happen and I don't just remember > how I did it :-) > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Tue, Oct 3, 2023 at 1:53 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Bug fixed and now the local errors structure is copied into the downlink. >> >> I think we should leave the WD enabled and see if it causes any issues. >> Thoughts on that? >> >> 73 >> Chris >> >> On Tue, Oct 3, 2023 at 1:37 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Thanks for that. >>> >>> I think it all works then. I can see the bits get set (or not when it >>> triggers). They wdReports not making it into the downlink though. They >>> are visible in errors.c So that is likely a bug in the way they are copied >>> onto the frame. >>> >>> 73 >>> Chris >>> >>> On Tue, Oct 3, 2023 at 11:35 AM Burns Fisher (AMSAT) via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Chris, wdReport is the bitmap of tasks that have called the watchdog >>>> report routine in the last few seconds. When you call >>>> ForceInternalWatchdogTrigger, you go into an infinite loop. Since the OS >>>> is set not to do pre-emption, that prevents ALL tasks from running and from >>>> reporting in. It is possible that you might have called this at such a >>>> time that a different task is the one that did not report in. >>>> >>>> If you want to try having a single task not report, put a call to >>>> vTaskYield() inside the infinite loop. That will prevent the current task >>>> from reporting, but allow all the others. And yes, the console task is not >>>> monitored, so it will not show a bit missing if you have the infinite loop >>>> without the yield, and should not trip the WD at all if you use yield. >>>> >>>> 73, >>>> >>>> Burns Fisher, WB1FJ >>>> *AMSAT(R) Engineering -- Flight Software* >>>> >>>> >>>> On Tue, Oct 3, 2023 at 11:24 AM Chris Thompson via pacsat-dev < >>>> pacsat-dev(a)amsat.org> wrote: >>>> >>>>> Ok, that call works and the watchdog resets the IHU as expected. The >>>>> console is not in wdReports so I could not see if the data ends up in the >>>>> Telemetry. So I put the call in the PB routine that handles DIR >>>>> broadcasts. We get a reset as expected when a DIR is requested. But I >>>>> can't see the missing bit in wdReports. They are all still set. I need to >>>>> dig a bit deeper as I perhaps don't understand how this is tracked. >>>>> >>>>> 73 >>>>> Chris >>>>> >>>>> On Mon, Oct 2, 2023, 18:44 Chris Thompson via pacsat-dev < >>>>> pacsat-dev(a)amsat.org> wrote: >>>>> >>>>>> Thanks! Will try that tomorrow. >>>>>> >>>>>> 73 >>>>>> Chris >>>>>> >>>>>> On Mon, Oct 2, 2023, 17:25 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> >>>>>> wrote: >>>>>> >>>>>>> Call "ForceInternalWatchdogTrigger". That prevents any other tasks >>>>>>> from running so after a few seconds, bang! The command to do that is "test >>>>>>> internal wd". >>>>>>> >>>>>>> There is code for an external watchdog (i.e. using a wd chip outside >>>>>>> of the processor) but that won't be used on the Launchpad. >>>>>>> >>>>>>> 73, >>>>>>> >>>>>>> Burns Fisher, WB1FJ >>>>>>> *AMSAT(R) Engineering -- Flight Software* >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < >>>>>>> pacsat-dev(a)amsat.org> wrote: >>>>>>> >>>>>>>> I made some changes to allow the watchdog to be started. Once I >>>>>>>> added some calls to the Uplink task and removed the CAN task from the >>>>>>>> wdReports list it stopped rebooting in a loop due to the watchdog. >>>>>>>> >>>>>>>> I now have it running with the watchdog enabled but I can't cause >>>>>>>> it to trigger the watchdog from a task. So I either don't understand what >>>>>>>> needs to be done or the watchdog is not working properly. >>>>>>>> >>>>>>>> The watchdog enabled code is checked into g0kla_watchdog >>>>>>>> >>>>>>>> If there is a simple line of code to trigger the watchdog then let >>>>>>>> me know. I was just trying to add a suitable delay. >>>>>>>> >>>>>>>> 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/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 >>>>>> >>>>> >>>>> ----------------------------------------------------------- >>>>> >>>>> 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 >>>> >>> >>> >>> -- >>> 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/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 >>> >> >> >> -- >> 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/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: Watchdog
by Burns Fisher (AMSAT) 03 Oct '23

03 Oct '23

The STM32L processor knows how to disable the WD when you are at breakpoints in the debugger. If the TMS does not do that, it is the only reason I can think of that there would be a problem. And just a check: Is the s/w still set up so that the errors structure is not wiped out by a reset? In other words, that the WD flags will be available after the WD triggers and the system reboots? I seem to remember that was a fair bit of hassle to make that happen and I don't just remember how I did it :-) 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Oct 3, 2023 at 1:53 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Bug fixed and now the local errors structure is copied into the downlink. > > I think we should leave the WD enabled and see if it causes any issues. > Thoughts on that? > > 73 > Chris > > On Tue, Oct 3, 2023 at 1:37 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Thanks for that. >> >> I think it all works then. I can see the bits get set (or not when it >> triggers). They wdReports not making it into the downlink though. They >> are visible in errors.c So that is likely a bug in the way they are copied >> onto the frame. >> >> 73 >> Chris >> >> On Tue, Oct 3, 2023 at 11:35 AM Burns Fisher (AMSAT) via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Chris, wdReport is the bitmap of tasks that have called the watchdog >>> report routine in the last few seconds. When you call >>> ForceInternalWatchdogTrigger, you go into an infinite loop. Since the OS >>> is set not to do pre-emption, that prevents ALL tasks from running and from >>> reporting in. It is possible that you might have called this at such a >>> time that a different task is the one that did not report in. >>> >>> If you want to try having a single task not report, put a call to >>> vTaskYield() inside the infinite loop. That will prevent the current task >>> from reporting, but allow all the others. And yes, the console task is not >>> monitored, so it will not show a bit missing if you have the infinite loop >>> without the yield, and should not trip the WD at all if you use yield. >>> >>> 73, >>> >>> Burns Fisher, WB1FJ >>> *AMSAT(R) Engineering -- Flight Software* >>> >>> >>> On Tue, Oct 3, 2023 at 11:24 AM Chris Thompson via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Ok, that call works and the watchdog resets the IHU as expected. The >>>> console is not in wdReports so I could not see if the data ends up in the >>>> Telemetry. So I put the call in the PB routine that handles DIR >>>> broadcasts. We get a reset as expected when a DIR is requested. But I >>>> can't see the missing bit in wdReports. They are all still set. I need to >>>> dig a bit deeper as I perhaps don't understand how this is tracked. >>>> >>>> 73 >>>> Chris >>>> >>>> On Mon, Oct 2, 2023, 18:44 Chris Thompson via pacsat-dev < >>>> pacsat-dev(a)amsat.org> wrote: >>>> >>>>> Thanks! Will try that tomorrow. >>>>> >>>>> 73 >>>>> Chris >>>>> >>>>> On Mon, Oct 2, 2023, 17:25 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> >>>>> wrote: >>>>> >>>>>> Call "ForceInternalWatchdogTrigger". That prevents any other tasks >>>>>> from running so after a few seconds, bang! The command to do that is "test >>>>>> internal wd". >>>>>> >>>>>> There is code for an external watchdog (i.e. using a wd chip outside >>>>>> of the processor) but that won't be used on the Launchpad. >>>>>> >>>>>> 73, >>>>>> >>>>>> Burns Fisher, WB1FJ >>>>>> *AMSAT(R) Engineering -- Flight Software* >>>>>> >>>>>> >>>>>> On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < >>>>>> pacsat-dev(a)amsat.org> wrote: >>>>>> >>>>>>> I made some changes to allow the watchdog to be started. Once I >>>>>>> added some calls to the Uplink task and removed the CAN task from the >>>>>>> wdReports list it stopped rebooting in a loop due to the watchdog. >>>>>>> >>>>>>> I now have it running with the watchdog enabled but I can't cause it >>>>>>> to trigger the watchdog from a task. So I either don't understand what >>>>>>> needs to be done or the watchdog is not working properly. >>>>>>> >>>>>>> The watchdog enabled code is checked into g0kla_watchdog >>>>>>> >>>>>>> If there is a simple line of code to trigger the watchdog then let >>>>>>> me know. I was just trying to add a suitable delay. >>>>>>> >>>>>>> 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/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 >>>>> >>>> >>>> ----------------------------------------------------------- >>>> >>>> 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 >>> >> >> >> -- >> 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/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 >> > > > -- > 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/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: Watchdog
by Chris Thompson 03 Oct '23

03 Oct '23

Bug fixed and now the local errors structure is copied into the downlink. I think we should leave the WD enabled and see if it causes any issues. Thoughts on that? 73 Chris On Tue, Oct 3, 2023 at 1:37 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Thanks for that. > > I think it all works then. I can see the bits get set (or not when it > triggers). They wdReports not making it into the downlink though. They > are visible in errors.c So that is likely a bug in the way they are copied > onto the frame. > > 73 > Chris > > On Tue, Oct 3, 2023 at 11:35 AM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Chris, wdReport is the bitmap of tasks that have called the watchdog >> report routine in the last few seconds. When you call >> ForceInternalWatchdogTrigger, you go into an infinite loop. Since the OS >> is set not to do pre-emption, that prevents ALL tasks from running and from >> reporting in. It is possible that you might have called this at such a >> time that a different task is the one that did not report in. >> >> If you want to try having a single task not report, put a call to >> vTaskYield() inside the infinite loop. That will prevent the current task >> from reporting, but allow all the others. And yes, the console task is not >> monitored, so it will not show a bit missing if you have the infinite loop >> without the yield, and should not trip the WD at all if you use yield. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Tue, Oct 3, 2023 at 11:24 AM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Ok, that call works and the watchdog resets the IHU as expected. The >>> console is not in wdReports so I could not see if the data ends up in the >>> Telemetry. So I put the call in the PB routine that handles DIR >>> broadcasts. We get a reset as expected when a DIR is requested. But I >>> can't see the missing bit in wdReports. They are all still set. I need to >>> dig a bit deeper as I perhaps don't understand how this is tracked. >>> >>> 73 >>> Chris >>> >>> On Mon, Oct 2, 2023, 18:44 Chris Thompson via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Thanks! Will try that tomorrow. >>>> >>>> 73 >>>> Chris >>>> >>>> On Mon, Oct 2, 2023, 17:25 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> >>>> wrote: >>>> >>>>> Call "ForceInternalWatchdogTrigger". That prevents any other tasks >>>>> from running so after a few seconds, bang! The command to do that is "test >>>>> internal wd". >>>>> >>>>> There is code for an external watchdog (i.e. using a wd chip outside >>>>> of the processor) but that won't be used on the Launchpad. >>>>> >>>>> 73, >>>>> >>>>> Burns Fisher, WB1FJ >>>>> *AMSAT(R) Engineering -- Flight Software* >>>>> >>>>> >>>>> On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < >>>>> pacsat-dev(a)amsat.org> wrote: >>>>> >>>>>> I made some changes to allow the watchdog to be started. Once I >>>>>> added some calls to the Uplink task and removed the CAN task from the >>>>>> wdReports list it stopped rebooting in a loop due to the watchdog. >>>>>> >>>>>> I now have it running with the watchdog enabled but I can't cause it >>>>>> to trigger the watchdog from a task. So I either don't understand what >>>>>> needs to be done or the watchdog is not working properly. >>>>>> >>>>>> The watchdog enabled code is checked into g0kla_watchdog >>>>>> >>>>>> If there is a simple line of code to trigger the watchdog then let me >>>>>> know. I was just trying to add a suitable delay. >>>>>> >>>>>> 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/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 >>>> >>> >>> ----------------------------------------------------------- >>> >>> 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 >> > > > -- > 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/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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Watchdog
by Chris Thompson 03 Oct '23

03 Oct '23

Thanks for that. I think it all works then. I can see the bits get set (or not when it triggers). They wdReports not making it into the downlink though. They are visible in errors.c So that is likely a bug in the way they are copied onto the frame. 73 Chris On Tue, Oct 3, 2023 at 11:35 AM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris, wdReport is the bitmap of tasks that have called the watchdog > report routine in the last few seconds. When you call > ForceInternalWatchdogTrigger, you go into an infinite loop. Since the OS > is set not to do pre-emption, that prevents ALL tasks from running and from > reporting in. It is possible that you might have called this at such a > time that a different task is the one that did not report in. > > If you want to try having a single task not report, put a call to > vTaskYield() inside the infinite loop. That will prevent the current task > from reporting, but allow all the others. And yes, the console task is not > monitored, so it will not show a bit missing if you have the infinite loop > without the yield, and should not trip the WD at all if you use yield. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Tue, Oct 3, 2023 at 11:24 AM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Ok, that call works and the watchdog resets the IHU as expected. The >> console is not in wdReports so I could not see if the data ends up in the >> Telemetry. So I put the call in the PB routine that handles DIR >> broadcasts. We get a reset as expected when a DIR is requested. But I >> can't see the missing bit in wdReports. They are all still set. I need to >> dig a bit deeper as I perhaps don't understand how this is tracked. >> >> 73 >> Chris >> >> On Mon, Oct 2, 2023, 18:44 Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Thanks! Will try that tomorrow. >>> >>> 73 >>> Chris >>> >>> On Mon, Oct 2, 2023, 17:25 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: >>> >>>> Call "ForceInternalWatchdogTrigger". That prevents any other tasks >>>> from running so after a few seconds, bang! The command to do that is "test >>>> internal wd". >>>> >>>> There is code for an external watchdog (i.e. using a wd chip outside of >>>> the processor) but that won't be used on the Launchpad. >>>> >>>> 73, >>>> >>>> Burns Fisher, WB1FJ >>>> *AMSAT(R) Engineering -- Flight Software* >>>> >>>> >>>> On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < >>>> pacsat-dev(a)amsat.org> wrote: >>>> >>>>> I made some changes to allow the watchdog to be started. Once I added >>>>> some calls to the Uplink task and removed the CAN task from the wdReports >>>>> list it stopped rebooting in a loop due to the watchdog. >>>>> >>>>> I now have it running with the watchdog enabled but I can't cause it >>>>> to trigger the watchdog from a task. So I either don't understand what >>>>> needs to be done or the watchdog is not working properly. >>>>> >>>>> The watchdog enabled code is checked into g0kla_watchdog >>>>> >>>>> If there is a simple line of code to trigger the watchdog then let me >>>>> know. I was just trying to add a suitable delay. >>>>> >>>>> 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/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 >>> >> >> ----------------------------------------------------------- >> >> 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Watchdog
by Burns Fisher (AMSAT) 03 Oct '23

03 Oct '23

Chris, wdReport is the bitmap of tasks that have called the watchdog report routine in the last few seconds. When you call ForceInternalWatchdogTrigger, you go into an infinite loop. Since the OS is set not to do pre-emption, that prevents ALL tasks from running and from reporting in. It is possible that you might have called this at such a time that a different task is the one that did not report in. If you want to try having a single task not report, put a call to vTaskYield() inside the infinite loop. That will prevent the current task from reporting, but allow all the others. And yes, the console task is not monitored, so it will not show a bit missing if you have the infinite loop without the yield, and should not trip the WD at all if you use yield. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Oct 3, 2023 at 11:24 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Ok, that call works and the watchdog resets the IHU as expected. The > console is not in wdReports so I could not see if the data ends up in the > Telemetry. So I put the call in the PB routine that handles DIR > broadcasts. We get a reset as expected when a DIR is requested. But I > can't see the missing bit in wdReports. They are all still set. I need to > dig a bit deeper as I perhaps don't understand how this is tracked. > > 73 > Chris > > On Mon, Oct 2, 2023, 18:44 Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Thanks! Will try that tomorrow. >> >> 73 >> Chris >> >> On Mon, Oct 2, 2023, 17:25 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: >> >>> Call "ForceInternalWatchdogTrigger". That prevents any other tasks from >>> running so after a few seconds, bang! The command to do that is "test >>> internal wd". >>> >>> There is code for an external watchdog (i.e. using a wd chip outside of >>> the processor) but that won't be used on the Launchpad. >>> >>> 73, >>> >>> Burns Fisher, WB1FJ >>> *AMSAT(R) Engineering -- Flight Software* >>> >>> >>> On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> I made some changes to allow the watchdog to be started. Once I added >>>> some calls to the Uplink task and removed the CAN task from the wdReports >>>> list it stopped rebooting in a loop due to the watchdog. >>>> >>>> I now have it running with the watchdog enabled but I can't cause it to >>>> trigger the watchdog from a task. So I either don't understand what needs >>>> to be done or the watchdog is not working properly. >>>> >>>> The watchdog enabled code is checked into g0kla_watchdog >>>> >>>> If there is a simple line of code to trigger the watchdog then let me >>>> know. I was just trying to add a suitable delay. >>>> >>>> 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/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 >> > > ----------------------------------------------------------- > > 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: Watchdog
by Chris Thompson 03 Oct '23

03 Oct '23

Ok, that call works and the watchdog resets the IHU as expected. The console is not in wdReports so I could not see if the data ends up in the Telemetry. So I put the call in the PB routine that handles DIR broadcasts. We get a reset as expected when a DIR is requested. But I can't see the missing bit in wdReports. They are all still set. I need to dig a bit deeper as I perhaps don't understand how this is tracked. 73 Chris On Mon, Oct 2, 2023, 18:44 Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Thanks! Will try that tomorrow. > > 73 > Chris > > On Mon, Oct 2, 2023, 17:25 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: > >> Call "ForceInternalWatchdogTrigger". That prevents any other tasks from >> running so after a few seconds, bang! The command to do that is "test >> internal wd". >> >> There is code for an external watchdog (i.e. using a wd chip outside of >> the processor) but that won't be used on the Launchpad. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I made some changes to allow the watchdog to be started. Once I added >>> some calls to the Uplink task and removed the CAN task from the wdReports >>> list it stopped rebooting in a loop due to the watchdog. >>> >>> I now have it running with the watchdog enabled but I can't cause it to >>> trigger the watchdog from a task. So I either don't understand what needs >>> to be done or the watchdog is not working properly. >>> >>> The watchdog enabled code is checked into g0kla_watchdog >>> >>> If there is a simple line of code to trigger the watchdog then let me >>> know. I was just trying to add a suitable delay. >>> >>> 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/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: Watchdog
by Burns Fisher (AMSAT) 02 Oct '23

02 Oct '23

Call "ForceInternalWatchdogTrigger". That prevents any other tasks from running so after a few seconds, bang! The command to do that is "test internal wd". There is code for an external watchdog (i.e. using a wd chip outside of the processor) but that won't be used on the Launchpad. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I made some changes to allow the watchdog to be started. Once I added > some calls to the Uplink task and removed the CAN task from the wdReports > list it stopped rebooting in a loop due to the watchdog. > > I now have it running with the watchdog enabled but I can't cause it to > trigger the watchdog from a task. So I either don't understand what needs > to be done or the watchdog is not working properly. > > The watchdog enabled code is checked into g0kla_watchdog > > If there is a simple line of code to trigger the watchdog then let me > know. I was just trying to add a suitable delay. > > 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/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 >

2 1

Watchdog
by Chris Thompson 02 Oct '23

02 Oct '23

I made some changes to allow the watchdog to be started. Once I added some calls to the Uplink task and removed the CAN task from the wdReports list it stopped rebooting in a loop due to the watchdog. I now have it running with the watchdog enabled but I can't cause it to trigger the watchdog from a task. So I either don't understand what needs to be done or the watchdog is not working properly. The watchdog enabled code is checked into g0kla_watchdog If there is a simple line of code to trigger the watchdog then let me know. I was just trying to add a suitable delay. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Helpful page on the historical Microsats
by Jim McCullers 02 Oct '23

02 Oct '23

Thanks Mark. That’s good to know and close enough. Jim McCullers WA4CWI Hi all. The output power was around 1-4 Watts, command able. I can look it up if y’all really need the info. 73, Mark L. Hammond [N8MH] On Mon, Oct 2, 2023 at 2:34 PM Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org <mailto:pacsat-dev@amsat.org> > wrote: Uplinks 4 1200 3.5 KHz deviation Manchester encoded FSK Downlink 1 1200 BPSK Several watts output power. Not very specific. https://www.om3ktr.sk/druzice/microsat.html -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net> ----------------------------------------------------------- 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

1 0

Re: Helpful page on the historical Microsats
by Mark L. Hammond 02 Oct '23

02 Oct '23

Hi all. The output power was around 1-4 Watts, command able. I can look it up if y’all really need the info. 73, Mark L. Hammond [N8MH] On Mon, Oct 2, 2023 at 2:34 PM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Uplinks 4 1200 3.5 KHz deviation Manchester encoded > FSK > > Downlink 1 1200 BPSK Several watts output power. Not > very specific. > > > > https://www.om3ktr.sk/druzice/microsat.html > > > > > > -- > > 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/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: Helpful page on the historical Microsats
by Jim McCullers 02 Oct '23

02 Oct '23

Uplinks 4 1200 3.5 KHz deviation Manchester encoded FSK Downlink 1 1200 BPSK Several watts output power. Not very specific. https://www.om3ktr.sk/druzice/microsat.html -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net>

1 0

Helpful page on the historical Microsats
by Chris Thompson 02 Oct '23

02 Oct '23

https://www.om3ktr.sk/druzice/microsat.html -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Equipment available for AMSAT annual meeting demo
by Bill Reed 02 Oct '23

02 Oct '23

Chris: I can supply the following: 1 TM570 dev board with pacsat daughter board. 1 Windows 10 laptop with groundstation and direwolf. 1 Ubuntu laptop with groundstation and direwolf 2 TM-V71 radios for groundstation 1 pair of Baofeng radios w/TARPN TNC for groundstation 1 Signalink USB to TM-V71 1 Digirig USB to TM-V71 2 2/70 antennas with magmount 1 tripod with 2/70 base station antenna 1 SEC-1223 base station 12v power with anderson powerpole conn 1 5v power for TARPN TNC Other misc cables? Let me know how I can help. Bill

2 1

TMS570 Availability
by Jonathan Brandenburg 01 Oct '23

01 Oct '23

Just a quick announcement... Mouser delivered 25 x TMS5700914APGEQQ1 MCUs. We have some stock! Jonathan -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0