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

Re: Task names
by Burns Fisher (AMSAT) 19 Apr '23

19 Apr '23

See my thoughts below: 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This is probably a question just for Burns but I will copy to the list so > it is logged for posterity. > > We need to update the task names. From the architecture design I have the > following: > RxTask > TxTask > Ax25Task > UplinkTask > PbTask > CommandTask > ConsoleTask > TelemCollectionTask > > In the code today we define the names here, I think: > typedef enum { > CurrentTaskWD=0, > CANSupportWD, > Not required. We are not using CAN in pacsat > > TelemetryWD, > Note: This task COLLECTS the telemetry every n seconds (4 in Fox and Golf I think) > ControlWD, > This may not be needed. In Fox and Golf it is the task that formats and downlinks (via Radio task) the telemetry. If the telemetry task just writes the telemetry into a file, then no one needs to format it differently. OTOH, if there are different modes etc like Golf and Fox, we might need something. RadioWD, > Is this going to be the same as Rx and Tx? Maybe not needed. > CommandWD, > This may still be needed. On Fox/Golf it is send command data to decode by the Radio task. Probably something like that still required? > IdleWD, // Note used in RT > I bet this is supposed to be "NOT" rather than "NOTE". But I'd have to check. FreeRTOS DOES have an idle task. In Fox, the idle task just whacks away at the watchdog so if there is no idle time, we reboot. On RT, we may use it to check memory, but I don't know why it does not need to pay attention to the WD. > ExperimentWD, > I'm not sure we need this. Pacsat IS a payload. CoordinateWD, > Not required. This is only for Golf where there are multiple processors. Unless we need something similar to coordinate the host and the pacsat payload. > /* Add any new tasks to watch in here. Maximum number of tasks is 9. > */ > /* The nine limit is the number of bits available in the downlink */ > LastWD, > InterruptThd = LastWD, > ConsoleTsk > }WdReporters_t; > > I have listed 8 tasks. We probably want the Experiment to be the 9th. > But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? > Or should we just assume 4 bits and have 16? > Worth a double check. THis comment (written by me no doubt) seems overly simplistic. But note that this is a bitmask, not a number. The bitmask shows which tasks have and have not kicked the watchdog. So to have 16, we need 16 bits. > > 73 > Chris > > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Task names
by Chris Thompson 19 Apr '23

19 Apr '23

Also note there is a second enum for InterTask notifications, which currently has this: typedef enum { ToNone=-1, ToDownlinkControl=0, ToCommand, ToRxTask, ToTxTask, ToTelemetry, // New message destinations go above here ToCAN, ToCoordinate, NumberOfDestinations } DestinationTask; Should this contain the same list as the WD Reports? 73 Chris On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This is probably a question just for Burns but I will copy to the list so > it is logged for posterity. > > We need to update the task names. From the architecture design I have the > following: > RxTask > TxTask > Ax25Task > UplinkTask > PbTask > CommandTask > ConsoleTask > TelemCollectionTask > > In the code today we define the names here, I think: > typedef enum { > CurrentTaskWD=0, > CANSupportWD, > TelemetryWD, > ControlWD, > RadioWD, > CommandWD, > IdleWD, // Note used in RT > ExperimentWD, > CoordinateWD, > /* Add any new tasks to watch in here. Maximum number of tasks is 9. > */ > /* The nine limit is the number of bits available in the downlink */ > LastWD, > InterruptThd = LastWD, > ConsoleTsk > }WdReporters_t; > > I have listed 8 tasks. We probably want the Experiment to be the 9th. > But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? > Or should we just assume 4 bits and have 16? > > 73 > Chris > > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Task names
by Chris Thompson 19 Apr '23

19 Apr '23

This is probably a question just for Burns but I will copy to the list so it is logged for posterity. We need to update the task names. From the architecture design I have the following: RxTask TxTask Ax25Task UplinkTask PbTask CommandTask ConsoleTask TelemCollectionTask In the code today we define the names here, I think: typedef enum { CurrentTaskWD=0, CANSupportWD, TelemetryWD, ControlWD, RadioWD, CommandWD, IdleWD, // Note used in RT ExperimentWD, CoordinateWD, /* Add any new tasks to watch in here. Maximum number of tasks is 9. */ /* The nine limit is the number of bits available in the downlink */ LastWD, InterruptThd = LastWD, ConsoleTsk }WdReporters_t; I have listed 8 tasks. We probably want the Experiment to be the 9th. But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? Or should we just assume 4 bits and have 16? 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Main branch updated
by Chris Thompson 19 Apr '23

19 Apr '23

Burns made some changes to be compatible with Jim's new boards and I finished refactoring the PACSAT code to use the file system. That is all merged back into main now and pushed to the repository. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Filesystem code
by Corey Minyard 15 Apr '23

15 Apr '23

I wigged out on this. I can pick it up in Addison, if you like, or you can mail it to me. Whichever is easier for you. Address is: 7406 Wheatfield Rd, Garland, TX 75044 If I come out there, I have an appointment I need to make in Addison, what's a good day/time for you? -corey On Fri, Apr 07, 2023 at 06:21:41PM +0000, Jonathan Brandenburg via pacsat-dev wrote: > I have confirmed I have it... Now, how to best get it to Corey... I can ship > it from Addison post office, I can get it to Bill soon (if Corey is going to > see Bill at a club meeting or something), or Corey can pick it up in > Addison. > Thoughts? > Jonathan > > On 4/7/2023 11:41 AM, Burns Fisher (AMSAT) via pacsat-dev wrote: > > Jonathan, did I send you the extra Launchpad that I ended up with? In > > any case, do you want to give one to Corey? Corey, you may have to > > solder on some .1" header pins for Jim's board to have all the required > > connections. I know the headers are DNP around the outside where they > > are not used, but I'm not sure that all the inside ones are there > > either. > > > > > > > > 73, > > > > Burns Fisher, WB1FJ > > /AMSAT(R) Engineering -- Flight Software/ > > > > > > On Fri, Apr 7, 2023 at 12:30 PM Corey Minyard via pacsat-dev > > <pacsat-dev(a)amsat.org> wrote: > > > > I have the filesystem code mostly ready. I changed the configuration > > to use 256 byte block. It's available in the filesystem branch. > > > > So I will need a launchpad and a board with MRAM. My address is: > > > > 7406 Wheatfield Rd, Garland, TX 75044 > > > > Chris, you can test it if you like, too. I haven't written any tests > > for anything yet, that needs to be added. > > > > There is code to automatically mount the filesystem on startup and > > format the filesystem if it detects corruption. > > > > There are three new console commands: mount fs, unmount fs, and > > format fs. > > > > The commands are the normal POSIX commands with "red_" prefixed, > > red_open(), red_close(), read_read(), etc. > > > > I need to write a README about how this is all set up. > > > > -corey > > > > ----------------------------------------------------------- > > > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > > View archives of this mailing list at > > https://mailman.amsat.org/hyperkitty/list/[email protected] > > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > > Manage all of your AMSAT-NA mailing list preferences at > > https://mailman.amsat.org > > > > > > ----------------------------------------------------------- > > > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/[email protected] > > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org > > > -- > 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/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: FYI Launchpad
by Jim McCullers 15 Apr '23

15 Apr '23

I have headers that will ship with the boards, exclusive of Burns and Chris. My bad. Obviously a ‘feature’ of the newer LaunchPad boards. Jim McCullers WA4CWI I expect to get Jim's prototype board that plugs into a LaunchPad today, so I wanted to get everything ready. I did not want to disconnect all my rat's nest of jumper wires and breadboards that I was initially using to check out the pins for Jim, but luckily I have another new LaunchPad. Here is the odd thing (which I think Chris has also mentioned). While the one that I was initially using clearly had headers factory-soldered for connectors J6-J9, they are DNF for the new LaunchPad that I have. Thus I soldered in headers. (I only hope they are sufficiently straight to fit Jim's board when it arrives!). If the time comes when anyone needs to do this, I have a whole box full of headers that can easily be broken to the right length. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software

1 0

FYI Launchpad
by Burns Fisher (AMSAT) 15 Apr '23

15 Apr '23

I expect to get Jim's prototype board that plugs into a LaunchPad today, so I wanted to get everything ready. I did not want to disconnect all my rat's nest of jumper wires and breadboards that I was initially using to check out the pins for Jim, but luckily I have another new LaunchPad. Here is the odd thing (which I think Chris has also mentioned). While the one that I was initially using clearly had headers factory-soldered for connectors J6-J9, they are DNF for the new LaunchPad that I have. Thus I soldered in headers. (I only hope they are sufficiently straight to fit Jim's board when it arrives!). If the time comes when anyone needs to do this, I have a whole box full of headers that can easily be broken to the right length. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Pacsat Dev Mtg 4/13/2023
by Burns Fisher (AMSAT) 13 Apr '23

13 Apr '23

Second Thursday. As usual I won't be there. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Apr 13, 2023 at 3:40 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat Dev Mtg 4/13/2023 > Thu, Apr 13, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/504515061 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (571) 317-3112 > - One-touch: tel:+15713173112,,504515061# > > Access Code: 504-515-061 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 504 515 061 > Or dial directly: 504515061(a)67.217.95.2 or 67.217.95.2##504515061 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Pacsat Dev Mtg 4/13/2023
by Bill 13 Apr '23

13 Apr '23

Pacsat Dev Mtg 4/13/2023 Thu, Apr 13, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/504515061 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3112 - One-touch: tel:+15713173112,,504515061# Access Code: 504-515-061 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 504 515 061 Or dial directly: 504515061(a)67.217.95.2 or 67.217.95.2##504515061 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Main sw branch updated.
by Chris Thompson 11 Apr '23

11 Apr '23

I merged the filesystem code into main. I have also merged the ax25_9600 branch into main. That was slightly more difficult because there were quite a lot of merge conflicts with the filesystem changes. Corey, you should check that I did not accidentally lose anything. The file write/read test still works, so it should be fine. Note that this still includes my fake filesystem for the PB routines. I will decommission those next and use the new file system. For now it seemed best to merge these two large changes together so that future development sits on top of them. We will continue to develop in branches so that main always compiles and works. With fairly regular updates to main to avoid branches getting too far apart. 73 Chris

1 0