Ok.  I was thinking about just changing "DCT_DEFAULT_RX_FREQ" to the 70cm freq, but sounds like you have a slightly more complex idea, so I won't mess with it. :-)   Don't forget if you change the layout of the MRAM status area to also increment MRAM_VERSION so people will be reminded to re-init the MRAM.
73,

Burns Fisher, WB1FJ
AMSAT(R) Engineering -- Flight Software


On Wed, May 10, 2023 at 3:44 PM Chris Thompson <chrisethompson@gmail.com> wrote:
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@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@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@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@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@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@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@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@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@amsat.org
> > > > > Manage all of your AMSAT-NA mailing list preferences at
> > > > https://mailman.amsat.org
> > > >
> > > > -----------------------------------------------------------
> > > >
> > > > pacsat-dev mailing list -- 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@amsat.org
> > > > Manage all of your AMSAT-NA mailing list preferences at
> > > > https://mailman.amsat.org
> > > >

-----------------------------------------------------------

pacsat-dev mailing list -- 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@amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org


--

-----------------------------------------------------------

pacsat-dev mailing list -- 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@amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

-----------------------------------------------------------

pacsat-dev mailing list -- 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@amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org