- pacsat-dev - mailman.amsat.org

Re: PACSAT Operating Instructions
by Corey Minyard 09 May '23

09 May '23

Burns sent me the info on that. I ran J5 pin 12 to a via on the bottom right of U1. After doing that wiring change, all but one MRAM appears to be working. It looks like R5 got removed somehow, I may have done that removing the wire. I just installed a bridge there, since it's a zero-ohm resistor, and the mram seems to be working now. The temperature sensor on the daughter board seems to be working. I don't think the 5043's are working. I'm not getting anything on transmit, and I eventually get: Pacsat>send pb status ## SELF TEST: pb_test_status TX QUEUE FULL: Could not add UI frame to Packet Queue PB Empty. ## PASSED SELF TEST: pb_test_status after running that a few times. At startup, I'm getting: ERROR: In start_rx, axradio_init returned: 5 ERROR: In start_tx, axradio_init_70cm returned: 5Initializing PB Task ERROR: Failed in init PB Status Timer -corey On Mon, May 8, 2023 at 9:51 PM Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Chris, > > Please take a look at the email I sent out earlier. > There is the possibility of a wiring error on the board with my white wire correction. > > As for the connectors being longer, I never noticed that and these should be the same connectors I sent Burns and Chris. > Burns say the MRAM is working after the wiring change and the AX5043s are working for Chris and Burns so not certain there. > > Attached is the revised schematic. I'll have the Kicad files on github hopefully tomorrow. Have a couple of issues to deal with. > > Jim McCullers > WA4CWI > > > > I sent this earlier, but just to Chris. > > I got my board today and soldered on the connectors. Looking at the board now, I see that the connectors that came with the launchpad are around 1cm longer than the ones Jim supplied. I can't get the mram or ax5043s to be detected. I don't think it's making good contact on the connectors, for obvious reasons. Do I need to trim the old connector, or did I do something wrong? > > I clipped the pins, and still no help. The power light by the serial connector works, and the serial port works. But the mrams and the ax5043's are not there. > > I can't find the schematics in the git repository. PacSatDocs, I assume. I guess I need to start debugging to figure out what is wrong. > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: PACSAT Operating Instructions
by Jim McCullers 09 May '23

09 May '23

Chris, Please take a look at the email I sent out earlier. There is the possibility of a wiring error on the board with my white wire correction. As for the connectors being longer, I never noticed that and these should be the same connectors I sent Burns and Chris. Burns say the MRAM is working after the wiring change and the AX5043s are working for Chris and Burns so not certain there. Attached is the revised schematic. I'll have the Kicad files on github hopefully tomorrow. Have a couple of issues to deal with. Jim McCullers WA4CWI I sent this earlier, but just to Chris. I got my board today and soldered on the connectors. Looking at the board now, I see that the connectors that came with the launchpad are around 1cm longer than the ones Jim supplied. I can't get the mram or ax5043s to be detected. I don't think it's making good contact on the connectors, for obvious reasons. Do I need to trim the old connector, or did I do something wrong? I clipped the pins, and still no help. The power light by the serial connector works, and the serial port works. But the mrams and the ax5043's are not there. I can't find the schematics in the git repository. PacSatDocs, I assume. I guess I need to start debugging to figure out what is wrong. -corey

1 0

Newest PACSAT daughter board
by Jim McCullers 09 May '23

09 May '23

Burns has informed me I reversed my own directions and MRAM fix may not be correct. Please review the attached images and if the board you received looks like the ‘Before’ image break out the soldering iron and swap them. The correct wiring is the ‘After’ image. I write directions much better than I follow them, even my own. Burns reports with the changes the AX5043 are ranging correctly and the MRAM works. Jim McCullers WA4CWI

1 0

Re: PACSAT Operating Instructions
by Corey Minyard 09 May '23

09 May '23

I sent this earlier, but just to Chris. I got my board today and soldered on the connectors. Looking at the board now, I see that the connectors that came with the launchpad are around 1cm longer than the ones Jim supplied. I can't get the mram or ax5043s to be detected. I don't think it's making good contact on the connectors, for obvious reasons. Do I need to trim the old connector, or did I do something wrong? I clipped the pins, and still no help. The power light by the serial connector works, and the serial port works. But the mrams and the ax5043's are not there. I can't find the schematics in the git repository. PacSatDocs, I assume. I guess I need to start debugging to figure out what is wrong. -corey On Mon, May 8, 2023 at 12:41 PM Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > If you have received a PACSAT Booster Board from Jim, then here are some instructions for testing/using it. > > > First make sure you have followed Burns instructions to install the IDE and flash the launchpad. You know this has worked when you have the console up and can type commands. When it tells you to type a command in these instructions, it means on the PACSAT Console. You can type help to show a list of commands. > > > > I suggest installing DireWolf on the same or another computer. You need to set it up to operate in full duplex at 9600bps. Initially you can use DireWolf to see you are receiving packets. Then you need to connect the ground station software by telling Pac Sat Ground that the TNC is connected to TCP port 8001, using the File > Settings screen. > > > > In the console type: > > send pb status > > > > This will transmit a packet and it should say PB Empty in DireWolf. > > > > Then type: > > ls > > > > This should show there are no files on the sat. If this does not work then type: > > unmount fs > > format fs > > mount fs > > > > In the console type: > > make psf > > > This will create a set of test files > > > > Type: > > ls > > > > To list them. We now need to set the time before we load them into the directory. We dont have a real time clock so it needs to be set manually. > > > > Look up the current Unix time on the web. I use https://www.unixtimestamp.com/ > > Type: > > set unix time <value> > > > > Then you can type: > > load dir > > > > This will load the files into the directory and set their upload time. In the future PACSAT will load the directory at boot. Probably once we have a real time clock in place. > > Type : > > list dir > > > > This will list all the files in the directory. Now when you reset the satellite the files will still be in the file system with the correct upload time, but the directory will be empty. You can type: > > load dir > > > > Without having to set the Unix Time, and it will load the files and remember their upload time. > > > > In the Pacsat ground station you can press the DIR button if the PB is available, i.e. you are not already on the PB. If it thinks you are on the PB then you can type this on the console: > > send pb status > > > > If you press the DIR button it should request the directory and download all the headers. If you interrupt the download then subsequent requests will ask for the holes in the directory. > > > > You can press the FILE button to download a file . Either type the file number you want in the box or click on the file in the directory to populate the box. You can also give a file a download priority by pressing numbers 1-9. See the manual for Details. > > > > Feel free to ask any questions. > > > 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

Re: PACSAT Operating Instructions
by Burns Fisher (AMSAT) 09 May '23

09 May '23

Ok, thanks. I saw a video about hooking up DireWolf to a BaoFeng radio, and I have exactly that radio. I'm not sure about the PTT though. I could also use my Kenwood D72--it does APRS, so it may even have a builtin TNC for other purposes. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 8:15 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Yes, DireWolf to a sound card and then to a radio. You could test receive > with an sdr as long as you can get the audio into DireWolf. > > I can provide details on DireWolf setup tomorrow. > > 73 > Chris > > On Mon, May 8, 2023, 17:06 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: > >> I assume you need to connect DireWolf through a sound card to a radio >> too. Or am I not following somthing? Your software does not do SDR like >> FoxTelem, right? >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Mon, May 8, 2023 at 1:41 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> If you have received a PACSAT Booster Board from Jim, then here are some >>> instructions for testing/using it. >>> >>> >>> First make sure you have followed Burns instructions to install the IDE >>> and flash the launchpad. You know this has worked when you have the >>> console up and can type commands. When it tells you to type a command in >>> these instructions, it means on the PACSAT Console. You can type help to >>> show a list of commands. >>> >>> >>> >>> I suggest installing DireWolf on the same or another computer. You need >>> to set it up to operate in full duplex at 9600bps. Initially you can use >>> DireWolf to see you are receiving packets. Then you need to connect the >>> ground station software by telling Pac Sat Ground that the TNC is connected >>> to TCP port 8001, using the File > Settings screen. >>> >>> >>> >>> In the console type: >>> >>> *send pb status * >>> >>> >>> >>> This will transmit a packet and it should say PB Empty in DireWolf. >>> >>> >>> >>> Then type: >>> >>> *ls * >>> >>> >>> >>> This should show there are no files on the sat. If this does not work >>> then type: >>> >>> *unmount fs* >>> >>> *format fs* >>> >>> *mount fs * >>> >>> >>> >>> In the console type: >>> >>> *make psf* >>> >>> >>> This will create a set of test files >>> >>> >>> >>> Type: >>> >>> *ls * >>> >>> >>> >>> To list them. We now need to set the time before we load them into the >>> directory. We dont have a real time clock so it needs to be set manually. >>> >>> >>> >>> Look up the current Unix time on the web. I use >>> https://www.unixtimestamp.com/ >>> >>> Type: >>> >>> *set unix time <value> * >>> >>> >>> >>> Then you can type: >>> >>> *load dir * >>> >>> >>> >>> This will load the files into the directory and set their upload time. >>> In the future PACSAT will load the directory at boot. Probably once we >>> have a real time clock in place. >>> >>> Type : >>> >>> *list dir * >>> >>> >>> >>> This will list all the files in the directory. Now when you reset the >>> satellite the files will still be in the file system with the correct >>> upload time, but the directory will be empty. You can type: >>> >>> *load dir * >>> >>> >>> >>> Without having to set the Unix Time, and it will load the files and >>> remember their upload time. >>> >>> >>> >>> In the Pacsat ground station you can press the DIR button if the PB is >>> available, i.e. you are not already on the PB. If it thinks you are on the >>> PB then you can type this on the console: >>> >>> *send pb status * >>> >>> >>> >>> If you press the DIR button it should request the directory and >>> download all the headers. If you interrupt the download then subsequent >>> requests will ask for the holes in the directory. >>> >>> >>> >>> You can press the FILE button to download a file . Either type the file >>> number you want in the box or click on the file in the directory to >>> populate the box. You can also give a file a download priority by pressing >>> numbers 1-9. See the manual for Details. >>> >>> >>> >>> Feel free to ask any questions. >>> >>> >>> 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: PACSAT Operating Instructions
by Burns Fisher (AMSAT) 09 May '23

09 May '23

I assume you need to connect DireWolf through a sound card to a radio too. Or am I not following somthing? Your software does not do SDR like FoxTelem, right? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 1:41 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > If you have received a PACSAT Booster Board from Jim, then here are some > instructions for testing/using it. > > > First make sure you have followed Burns instructions to install the IDE > and flash the launchpad. You know this has worked when you have the > console up and can type commands. When it tells you to type a command in > these instructions, it means on the PACSAT Console. You can type help to > show a list of commands. > > > > I suggest installing DireWolf on the same or another computer. You need > to set it up to operate in full duplex at 9600bps. Initially you can use > DireWolf to see you are receiving packets. Then you need to connect the > ground station software by telling Pac Sat Ground that the TNC is connected > to TCP port 8001, using the File > Settings screen. > > > > In the console type: > > *send pb status * > > > > This will transmit a packet and it should say PB Empty in DireWolf. > > > > Then type: > > *ls * > > > > This should show there are no files on the sat. If this does not work > then type: > > *unmount fs* > > *format fs* > > *mount fs * > > > > In the console type: > > *make psf* > > > This will create a set of test files > > > > Type: > > *ls * > > > > To list them. We now need to set the time before we load them into the > directory. We dont have a real time clock so it needs to be set manually. > > > > Look up the current Unix time on the web. I use > https://www.unixtimestamp.com/ > > Type: > > *set unix time <value> * > > > > Then you can type: > > *load dir * > > > > This will load the files into the directory and set their upload time. > In the future PACSAT will load the directory at boot. Probably once we > have a real time clock in place. > > Type : > > *list dir * > > > > This will list all the files in the directory. Now when you reset the > satellite the files will still be in the file system with the correct > upload time, but the directory will be empty. You can type: > > *load dir * > > > > Without having to set the Unix Time, and it will load the files and > remember their upload time. > > > > In the Pacsat ground station you can press the DIR button if the PB is > available, i.e. you are not already on the PB. If it thinks you are on the > PB then you can type this on the console: > > *send pb status * > > > > If you press the DIR button it should request the directory and download > all the headers. If you interrupt the download then subsequent requests > will ask for the holes in the directory. > > > > You can press the FILE button to download a file . Either type the file > number you want in the box or click on the file in the directory to > populate the box. You can also give a file a download priority by pressing > numbers 1-9. See the manual for Details. > > > > Feel free to ask any questions. > > > 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

PACSAT Operating Instructions
by Chris Thompson 08 May '23

08 May '23

If you have received a PACSAT Booster Board from Jim, then here are some instructions for testing/using it. First make sure you have followed Burns instructions to install the IDE and flash the launchpad. You know this has worked when you have the console up and can type commands. When it tells you to type a command in these instructions, it means on the PACSAT Console. You can type help to show a list of commands. I suggest installing DireWolf on the same or another computer. You need to set it up to operate in full duplex at 9600bps. Initially you can use DireWolf to see you are receiving packets. Then you need to connect the ground station software by telling Pac Sat Ground that the TNC is connected to TCP port 8001, using the File > Settings screen. In the console type: *send pb status * This will transmit a packet and it should say PB Empty in DireWolf. Then type: *ls * This should show there are no files on the sat. If this does not work then type: *unmount fs* *format fs* *mount fs * In the console type: *make psf* This will create a set of test files Type: *ls * To list them. We now need to set the time before we load them into the directory. We dont have a real time clock so it needs to be set manually. Look up the current Unix time on the web. I use https://www.unixtimestamp.com/ Type: *set unix time <value> * Then you can type: *load dir * This will load the files into the directory and set their upload time. In the future PACSAT will load the directory at boot. Probably once we have a real time clock in place. Type : *list dir * This will list all the files in the directory. Now when you reset the satellite the files will still be in the file system with the correct upload time, but the directory will be empty. You can type: *load dir * Without having to set the Unix Time, and it will load the files and remember their upload time. In the Pacsat ground station you can press the DIR button if the PB is available, i.e. you are not already on the PB. If it thinks you are on the PB then you can type this on the console: *send pb status * If you press the DIR button it should request the directory and download all the headers. If you interrupt the download then subsequent requests will ask for the holes in the directory. You can press the FILE button to download a file . Either type the file number you want in the box or click on the file in the directory to populate the box. You can also give a file a download priority by pressing numbers 1-9. See the manual for Details. Feel free to ask any questions. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

RF Components / Power Requirements
by Jonathan Brandenburg 05 May '23

05 May '23

As discussed last night, I've completed some preliminary work on the radiation tolerant circuitry. That does bring up one question... Bob, do you already have circuitry for watchdog protection and current limiting in the schematic / on the board? Or does that still have to be shoehorned into the board? To refine the design I've prototyped, I need to know the anticipated/budgeted power requirements. The part I'm looking at for current limiting, MAX4995AAUT+T, can handle 600mA. If we derate that a bit (are we using 50%?) we can handle 300mA. That's quite a lot so I don't expect an issue with hitting max current except possibly the power amplifier and it's not clear to me if the power amplifier needs to be protected against latchup anyway. In our previous designs, we have a separate current limiter for each AX5043, the power amplifier, and the TMS570. (I think the LNAs are bundled with the AX5043 for the purposes of power limits and peripheral power requirements for TXCOs and such ). I don't think we'll need that many here but we'll probably need one for each voltage rail. Do we have answers to some of the following questions or is some of still being determined: 1. What power output level are we using on the AX5043? Max current at 16dbm TX is 48 mA plus 6.5 mA for VHF receiver or 9.5 mA for UHF receive. 2. What LNAs are we using? Does each AX5043 have its own LNA? (I haven't looked for a schematic so tell me to go find it myself if it's in Github.) 3. What power amplifier are we using and what is the power output? (I still need to double-check a need for current limiter here.) 4. Do we have a characterization for the TMS570 configuration to know which subsystems will be active and thus have a power budget for the TMS570? Thanks a lot! Jonathan -- Jonathan Brandenburg, KF5IDY

1 0

Re: AX.25 code
by Chris Thompson 05 May '23

05 May '23

Thanks Corey. I will review. I'm sure it will be helpful. Especially the errors you have noted. 73 Chris On Thu, May 4, 2023, 21:17 Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > My code for AX.25 is part of the gensio library. The individual files are > at: > > https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25.c > > https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25_addr.c > > The gensio library is a whole framework for all kinds of stream and > packet I/O. But you should be able to pull out the middle of the file > that has the state machine, pretty much unmodified, and use it. > > One thing that might be more interesting is I documented a bunch of > bugs in the spec in the comments at the top of the gensio_ax25.c file. > > Anyway, it's available if you want it. I'd be willing to split out > the state machine if you wanted something that was individually > maintainable. > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

AX.25 code
by Corey Minyard 05 May '23

05 May '23

My code for AX.25 is part of the gensio library. The individual files are at: https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25.c https://github.com/cminyard/gensio/blob/master/lib/gensio_ax25_addr.c The gensio library is a whole framework for all kinds of stream and packet I/O. But you should be able to pull out the middle of the file that has the state machine, pretty much unmodified, and use it. One thing that might be more interesting is I documented a bunch of bugs in the spec in the comments at the top of the gensio_ax25.c file. Anyway, it's available if you want it. I'd be willing to split out the state machine if you wanted something that was individually maintainable. -corey

1 0