- pacsat-dev - mailman.amsat.org

Re: PACSAT Operating Instructions
by Chris Thompson 10 May '23

10 May '23

Hi Burns, Yes. I just haven't had time to do that. The startup routine would have to be changed to detect if it is vhf or uhf and then pass the right value as appropriate. Then we could remove my override. 73 Chris On Wed, May 10, 2023, 15:13 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris et al, > > Does it make sense to put the values that we want in the MRAM status > section right now? In that way we don't have two different places that are > setting the values differently, and it is relatively easy to change using > the existing "change" commands. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, May 10, 2023 at 3:09 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Hi Corey >> >> Glad to see things are working. >> >> I agree the frequencies are a little screwy. The TX defaults to 435750 >> based on some original Golf code I think. We can set that to default to >> whatever we want. The receiver defaults to 145835 but I have a bit of >> code that overrides it in the startup of the receiver. That hard codes the >> receiver to UHF and 436800. Initially that was because the boards I had >> only worked on 70cms. Now it is because the receive config does not work >> that well on 2m. You can go into deviceSupport/src/ax5043-ax25.c and >> comment out these two two lines in start_ax25_rx(): >> freq = 436800000; // Use for testing >> band_vhf = BAND_UHF; >> >> Then it will work as expected and receive (sort of) on 2m. >> >> 73 >> Chris >> >> On Wed, May 10, 2023 at 2:42 PM Corey Minyard via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> It could be the serial port, that makes some sense, I guess. >>> >>> I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still >>> works, but the 5043s still don't. >>> >>> I think I found it. R10 and R11 are not populated. One of them says >>> 330 ohms, one says zero. What needs to be put here? I think I have >>> some SM resistors, but probably 0603, and these look smaller. >>> >>> -corey >>> >>> > Ok, I got both mails. One thing I notice is that there is some >>> backflow of >>> > power from the serial line which lights the LED (dimly) even if the >>> > LaunchPad is unpowered. Could that be the reason for the 2.7V? I have >>> > those jumpers installed on both halves of the board, but I'm surprised >>> the >>> > MRAM works at all if you don't have it installed (maybe that 2.7V is >>> > enough---and I don't see how that relates to the 5043). >>> >>> On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: >>> > >>> > I send this from my acm.org account and realised it's not going to get >>> > to the pacsat mailing list. So here it is again. >>> > >>> > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: >>> > > >>> > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: >>> > > > Ok, glad the MRAM is working. Any chance that you don't have the >>> two >>> > > > jumpers on the LaunchPad required to power the 5043s? These would >>> be a >>> > > > pair on the right (components up, USB down, I think) just below >>> the bottom >>> > > > set of pins. >>> > > >>> > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both >>> installed. >>> > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. >>> > > >>> > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the >>> > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, >>> > > which is strange. That's what powers the MRAMs and the temperature >>> > > sensor. >>> > > >>> > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other >>> side >>> > > of the jumper. I'm wondering if the power is somehow coming through >>> the >>> > > 5043s and getting to the MRAMs, but I don't see how that could >>> happen. >>> > > >>> > > > >>> > > > BTW, I don't even try to push Jim's board all the way on. It is >>> tight as >>> > > > it is and I want to be able to get it back off (relatively) >>> easily. But >>> > > > regardess, the tops of the pins are all level, even though the >>> newly >>> > > > soldered pins have a plastic holder at the bottom and the original >>> pins do >>> > > > not. >>> > > >>> > > Yeah, strange. I didn't notice until I tried to put the board on. >>> My >>> > > board now looks terrible, but it seems to be making good contact now. >>> > > >>> > > I looked at close-up pictures on TI's web site, and the pins I had >>> look >>> > > the same as the ones in the picture. >>> > > >>> > > -corey >>> > > >>> > > > >>> > > > 73, >>> > > > >>> > > > Burns Fisher, WB1FJ >>> > > > *AMSAT(R) Engineering -- Flight Software* >>> > > > >>> > > > >>> > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < >>> > > > pacsat-dev(a)amsat.org> wrote: >>> > > > >>> > > > > 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 >>> > > > > >>> > > > > ----------------------------------------------------------- >>> > > > > >>> > > > > 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 >> > > ----------------------------------------------------------- > > 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

Re: Newest PACSAT daughter board
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Just to clarify, only ONE white-wire needs to be changed. The one connecting to R4 is ok. The one connecting to R5 needs to be moved to a via along the edge of the board (it probably needs a longer wire unless you find a different way to make the connection to that trace). 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 10:42 PM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > 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 > > ----------------------------------------------------------- > > 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 10 May '23

10 May '23

Corey, Sorry but list has been offline. Populate with 330 ohm or almost anything. Zero may work and that's on my future test list. It's like the zero ohm resistors that we found out were not needed on the MRAMs to as load separation between the chips. Kicad protested that something had to be there and at that time on the MRAMs we did not know and still do not know on the 5043s. Not much literature on putting two on the same SPI bus. I ran out of 330s and forgot to populate when the shipment came in. Jim McCullers WA4CWI It could be the serial port, that makes some sense, I guess. I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still works, but the 5043s still don't. I think I found it. R10 and R11 are not populated. One of them says 330 ohms, one says zero. What needs to be put here? I think I have some SM resistors, but probably 0603, and these look smaller. -corey > Ok, I got both mails. One thing I notice is that there is some > backflow of power from the serial line which lights the LED (dimly) > even if the LaunchPad is unpowered. Could that be the reason for the > 2.7V? I have those jumpers installed on both halves of the board, but > I'm surprised the MRAM works at all if you don't have it installed > (maybe that 2.7V is enough---and I don't see how that relates to the 5043). On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: > > I send this from my acm.org account and realised it's not going to get > to the pacsat mailing list. So here it is again. > > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: > > > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: > > > Ok, glad the MRAM is working. Any chance that you don't have the > > > two jumpers on the LaunchPad required to power the 5043s? These > > > would be a pair on the right (components up, USB down, I think) > > > just below the bottom set of pins. > > > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both installed. > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. > > > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, > > which is strange. That's what powers the MRAMs and the temperature > > sensor. > > > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other > > side of the jumper. I'm wondering if the power is somehow coming > > through the 5043s and getting to the MRAMs, but I don't see how that could happen. > > > > > > > > BTW, I don't even try to push Jim's board all the way on. It is tight as > > > it is and I want to be able to get it back off (relatively) easily. But > > > regardess, the tops of the pins are all level, even though the > > > newly soldered pins have a plastic holder at the bottom and the > > > original pins do not. > > > > Yeah, strange. I didn't notice until I tried to put the board on. > > My board now looks terrible, but it seems to be making good contact now. > > > > I looked at close-up pictures on TI's web site, and the pins I had > > look the same as the ones in the picture. > > > > -corey > > > > > > > > 73, > > > > > > Burns Fisher, WB1FJ > > > *AMSAT(R) Engineering -- Flight Software* > > > > > > > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < > > > pacsat-dev(a)amsat.org> wrote: > > > > > > > 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 > > > > > > > > ----------------------------------------------------------- > > > > > > > > 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) 10 May '23

10 May '23

Chris et al, Does it make sense to put the values that we want in the MRAM status section right now? In that way we don't have two different places that are setting the values differently, and it is relatively easy to change using the existing "change" commands. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, May 10, 2023 at 3:09 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Hi Corey > > Glad to see things are working. > > I agree the frequencies are a little screwy. The TX defaults to 435750 > based on some original Golf code I think. We can set that to default to > whatever we want. The receiver defaults to 145835 but I have a bit of > code that overrides it in the startup of the receiver. That hard codes the > receiver to UHF and 436800. Initially that was because the boards I had > only worked on 70cms. Now it is because the receive config does not work > that well on 2m. You can go into deviceSupport/src/ax5043-ax25.c and > comment out these two two lines in start_ax25_rx(): > freq = 436800000; // Use for testing > band_vhf = BAND_UHF; > > Then it will work as expected and receive (sort of) on 2m. > > 73 > Chris > > On Wed, May 10, 2023 at 2:42 PM Corey Minyard via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> It could be the serial port, that makes some sense, I guess. >> >> I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still >> works, but the 5043s still don't. >> >> I think I found it. R10 and R11 are not populated. One of them says >> 330 ohms, one says zero. What needs to be put here? I think I have >> some SM resistors, but probably 0603, and these look smaller. >> >> -corey >> >> > Ok, I got both mails. One thing I notice is that there is some >> backflow of >> > power from the serial line which lights the LED (dimly) even if the >> > LaunchPad is unpowered. Could that be the reason for the 2.7V? I have >> > those jumpers installed on both halves of the board, but I'm surprised >> the >> > MRAM works at all if you don't have it installed (maybe that 2.7V is >> > enough---and I don't see how that relates to the 5043). >> >> On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: >> > >> > I send this from my acm.org account and realised it's not going to get >> > to the pacsat mailing list. So here it is again. >> > >> > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: >> > > >> > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: >> > > > Ok, glad the MRAM is working. Any chance that you don't have the >> two >> > > > jumpers on the LaunchPad required to power the 5043s? These would >> be a >> > > > pair on the right (components up, USB down, I think) just below the >> bottom >> > > > set of pins. >> > > >> > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both >> installed. >> > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. >> > > >> > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the >> > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, >> > > which is strange. That's what powers the MRAMs and the temperature >> > > sensor. >> > > >> > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other >> side >> > > of the jumper. I'm wondering if the power is somehow coming through >> the >> > > 5043s and getting to the MRAMs, but I don't see how that could happen. >> > > >> > > > >> > > > BTW, I don't even try to push Jim's board all the way on. It is >> tight as >> > > > it is and I want to be able to get it back off (relatively) >> easily. But >> > > > regardess, the tops of the pins are all level, even though the newly >> > > > soldered pins have a plastic holder at the bottom and the original >> pins do >> > > > not. >> > > >> > > Yeah, strange. I didn't notice until I tried to put the board on. My >> > > board now looks terrible, but it seems to be making good contact now. >> > > >> > > I looked at close-up pictures on TI's web site, and the pins I had >> look >> > > the same as the ones in the picture. >> > > >> > > -corey >> > > >> > > > >> > > > 73, >> > > > >> > > > Burns Fisher, WB1FJ >> > > > *AMSAT(R) Engineering -- Flight Software* >> > > > >> > > > >> > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < >> > > > pacsat-dev(a)amsat.org> wrote: >> > > > >> > > > > 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 >> > > > > >> > > > > ----------------------------------------------------------- >> > > > > >> > > > > 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 >

1 0

Re: PACSAT Operating Instructions
by Chris Thompson 10 May '23

10 May '23

Hi Corey Glad to see things are working. I agree the frequencies are a little screwy. The TX defaults to 435750 based on some original Golf code I think. We can set that to default to whatever we want. The receiver defaults to 145835 but I have a bit of code that overrides it in the startup of the receiver. That hard codes the receiver to UHF and 436800. Initially that was because the boards I had only worked on 70cms. Now it is because the receive config does not work that well on 2m. You can go into deviceSupport/src/ax5043-ax25.c and comment out these two two lines in start_ax25_rx(): freq = 436800000; // Use for testing band_vhf = BAND_UHF; Then it will work as expected and receive (sort of) on 2m. 73 Chris On Wed, May 10, 2023 at 2:42 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > It could be the serial port, that makes some sense, I guess. > > I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still > works, but the 5043s still don't. > > I think I found it. R10 and R11 are not populated. One of them says > 330 ohms, one says zero. What needs to be put here? I think I have > some SM resistors, but probably 0603, and these look smaller. > > -corey > > > Ok, I got both mails. One thing I notice is that there is some backflow > of > > power from the serial line which lights the LED (dimly) even if the > > LaunchPad is unpowered. Could that be the reason for the 2.7V? I have > > those jumpers installed on both halves of the board, but I'm surprised > the > > MRAM works at all if you don't have it installed (maybe that 2.7V is > > enough---and I don't see how that relates to the 5043). > > On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: > > > > I send this from my acm.org account and realised it's not going to get > > to the pacsat mailing list. So here it is again. > > > > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: > > > > > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: > > > > Ok, glad the MRAM is working. Any chance that you don't have the two > > > > jumpers on the LaunchPad required to power the 5043s? These would > be a > > > > pair on the right (components up, USB down, I think) just below the > bottom > > > > set of pins. > > > > > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both > installed. > > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. > > > > > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the > > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, > > > which is strange. That's what powers the MRAMs and the temperature > > > sensor. > > > > > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other side > > > of the jumper. I'm wondering if the power is somehow coming through > the > > > 5043s and getting to the MRAMs, but I don't see how that could happen. > > > > > > > > > > > BTW, I don't even try to push Jim's board all the way on. It is > tight as > > > > it is and I want to be able to get it back off (relatively) easily. > But > > > > regardess, the tops of the pins are all level, even though the newly > > > > soldered pins have a plastic holder at the bottom and the original > pins do > > > > not. > > > > > > Yeah, strange. I didn't notice until I tried to put the board on. My > > > board now looks terrible, but it seems to be making good contact now. > > > > > > I looked at close-up pictures on TI's web site, and the pins I had look > > > the same as the ones in the picture. > > > > > > -corey > > > > > > > > > > > 73, > > > > > > > > Burns Fisher, WB1FJ > > > > *AMSAT(R) Engineering -- Flight Software* > > > > > > > > > > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < > > > > pacsat-dev(a)amsat.org> wrote: > > > > > > > > > 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 > > > > > > > > > > ----------------------------------------------------------- > > > > > > > > > > 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: PACSAT Operating Instructions
by Chris Thompson 10 May '23

10 May '23

DireWolf uses a config file. A template is supplied with the installation. It looks very complicated but you only have to change a very small amount. If you are using DireWolf in KISS mode you do not even need to set your callsign or Full Duplex. The ground station will do that when it connects to DireWolf. You do need to set the speed to 1200 or 9600, but I do that from the command line. I run DireWolf like this: direwolf -q d -B 9600 The -q d stops it printing APRS. The -B is the speed and can also be 1200. That means the only things you must set in the config file are the sound card and how to key the radio. When you run direwolf for the first time it prints out all the sound cards it can see and gives each a number. Note which numbers you want to use for Receive/Transmit. Then open the config file and edit the section labeled FIRST AUDIO DEVICE. Set the line ADEVICE to have the two sound card numbers after it. I have: ADEVICE 0 3 Which means sound card 0 for receive and soundcard 3 for transmit. You might be able to key the radio with VOX for testing. But I recommend keying it with a serial line. I use a DigiRig sound card that comes with a built in serial line setup to key the radio. But I have also used a serial line and a single transistor to key the radio. One advantage of the DigiRig is that he sells cables ready made for many radios. If you want to transmit outside of the shack then go into config.h in the PACSAT code and put in your own callsign. Also remember that it is transmitting and receiving 9600 bps packet on 70cms. This is currently hard coded but we should add a command to switch modes no doubt. If you want to change this then modify deviceSupport/ax5043-access.c - ax5043StartTx()/ax5043StartRx() to pass RATE_1200 vs RATE_9600 and update deviceSupport/ax5043-ax25.c - start_ax25_rx() - where the band is overridden to 70cms for receive. 2m will work for 1200bps but is very deaf for 70cms. Jim has solved this but the code fixes still need to be applied. 73 Chris On Mon, May 8, 2023 at 8:17 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > 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 >> > > ----------------------------------------------------------- > > 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 4

Re: Newest PACSAT daughter board
by Bob Stricklin 10 May '23

10 May '23

I received the board. I have soldered on the connectors and made the little wiring change you indicated Jim. It all looks very nice. I have not done any testing yet but will try to do some soon. Thanks for all your efforts. Bob On May 8, 2023, at 9:42 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: 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 <After.jpeg><Before.jpeg> ----------------------------------------------------------- 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/>

1 0

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

10 May '23

Ok, glad the MRAM is working. Any chance that you don't have the two jumpers on the LaunchPad required to power the 5043s? These would be a pair on the right (components up, USB down, I think) just below the bottom set of pins. BTW, I don't even try to push Jim's board all the way on. It is tight as it is and I want to be able to get it back off (relatively) easily. But regardess, the tops of the pins are all level, even though the newly soldered pins have a plastic holder at the bottom and the original pins do not. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > 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 > > ----------------------------------------------------------- > > 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 6

PacSat LaunchPad Daughter Board Files
by Jim McCullers 10 May '23

10 May '23

The launchpad daughter board Kicad files are now posted on github. The posted version has the white wire correction included. Jim McCullers WA4CWI

1 0

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

08 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