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

Re: AX25 code
by Chris Thompson 12 May '23

12 May '23

ok, thanks. I will have a look. 73 Chris On Fri, May 12, 2023 at 8:51 AM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > On Thu, May 11, 2023 at 8:01 PM Corey Minyard via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > > > For Chris, mostly, > > > > In my AX25 code, the two queues are named read_data and write_data, > > you can search for those values. The length, position, and size are > > right after it and described in the comment above. > > > > There are also some functions named "sub_seq", "add_seq" and > > "seq_in_range" that handle the wraparound. In particular, > > seq_in_range is a little tricky. And I see that I should comment > > those better. > > Just to be clear, those are used for both sequence number handling and > for circular buffer handling. I've added some comments to document > them a little better. > > > > > And if you want, I can look at splitting up my code into a library > > that has the state machine that could be re-used. It may be some > > overkill, though, it does all the extended sequencing, XID, and such > > that we don't need. > > > > -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 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

Re: AX25 code
by Corey Minyard 12 May '23

12 May '23

On Thu, May 11, 2023 at 8:01 PM Corey Minyard via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > For Chris, mostly, > > In my AX25 code, the two queues are named read_data and write_data, > you can search for those values. The length, position, and size are > right after it and described in the comment above. > > There are also some functions named "sub_seq", "add_seq" and > "seq_in_range" that handle the wraparound. In particular, > seq_in_range is a little tricky. And I see that I should comment > those better. Just to be clear, those are used for both sequence number handling and for circular buffer handling. I've added some comments to document them a little better. > > And if you want, I can look at splitting up my code into a library > that has the state machine that could be re-used. It may be some > overkill, though, it does all the extended sequencing, XID, and such > that we don't need. > > -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

1 0

AX25 code
by Corey Minyard 11 May '23

11 May '23

For Chris, mostly, In my AX25 code, the two queues are named read_data and write_data, you can search for those values. The length, position, and size are right after it and described in the comment above. There are also some functions named "sub_seq", "add_seq" and "seq_in_range" that handle the wraparound. In particular, seq_in_range is a little tricky. And I see that I should comment those better. And if you want, I can look at splitting up my code into a library that has the state machine that could be re-used. It may be some overkill, though, it does all the extended sequencing, XID, and such that we don't need. -corey

1 0

Re: Pacsat dev mtg 5/11/2023
by Burns Fisher (AMSAT) 11 May '23

11 May '23

Second Thursday, so I won't be there. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, May 11, 2023 at 3:48 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Thu, May 11, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/961241293 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (408) 650-3123 > - One-touch: tel:+14086503123,,961241293# > > Access Code: 961-241-293 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 961 241 293 > Or dial directly: 961241293(a)67.217.95.2 or 67.217.95.2##961241293 > > > 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 5/11/2023
by Bill 11 May '23

11 May '23

Thu, May 11, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/961241293 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (408) 650-3123 - One-touch: tel:+14086503123,,961241293# Access Code: 961-241-293 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 961 241 293 Or dial directly: 961241293(a)67.217.95.2 or 67.217.95.2##961241293 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Building/loading PacSat software
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Chris said in a previous mail that I had sent out info about how to build PacSat. Maybe I did, but I can't find it. So for Bill and any others, here is at least a quick version. Without actually DOING it again, I may miss something. We can use this thread to clarify, and I know several other people have done it. Please do speak up if I miss something. =========================== The first thing you want to do is to download and install TI's Code Composer Studio. Look at https://www.ti.com/tool/CCSTUDIO I use the Linux version 10.2.0.00009, but there are several versions newer. I tend not to update unless I need to, but feel free to try the newer one. (We should freeze the version before we start testing for flight!) When you run CCS, go to the "File" menu and select "Import" and the Git/Projects from Git. (I don't know what smart import, another choice is, so I probably did not use it). I think it will suggest a project called "PacSat" and that is what you should choose. Let it all install/download, etc, and then push the "Hammer" key to build. Hopefully this will work. Then you can plug in your LaunchPad and hit the "bug" button to download and debug. If you are not gonig to use the debugger, just hit the red square to disconnect and it will run. Remember that you have to have a serial port connected to Jim's board (the 3 pins labelled Rx, Tx, and Gnd). Use a terminal emulator to connect to this at 38400 baud. Hopefully, this all does the trick. Have I missed anything Chris, Corey, Jim? I have not done the full download in a good long time, so there are probably additional things you have to slog through. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Code Cleanup
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Folks, I have removed references to the HET (High Efficiency Timer--essentially a co-processor in the TMS570) emulation of I2c and UART. We need extra UARTs and I2c busses in Golf, and Golf is where I initially ported the PacSat code from. This is step one of cleaning out Golf stuff. I've already removed anything that might be ITAR sensitive (and I don't think there was anything). This is just removing unnecessary stuff that need not take up space in flash. I don't think this will cause anyone any serious problems merging since most of it was in drivers, but it is currently in a branch called CleanUpHET. I'll put in a pull request to merge that with main, and if I hear no comments, will do that in a few days. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

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

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