- pacsat-dev - mailman.amsat.org

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