Sounds like a good plan re customs.

BTW, one thing I forgot to mention: I did not mess around at all (or nearly at all) with the receive and transmit code. So there are probably some places where it reads the frequency to set itself from MRAM, and I set it to read the frequency for receiver 1. I'm sure there is a lot of stuff that needs to be done to deal with all 4 receivers, but I only changed the low level routines to accept an Rx number argument, and then whoever called them to specify one of the receivers. For the init stuff and the raise/lower stuff I called the appropriate routines for whichever one you set, but I don't know anything about how they work.

73,

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

On Sun, Feb 11, 2024 at 5:50 PM Chris Thompson via pacsat-dev < pacsat-dev@amsat.org> wrote:

All sounds good Burns. I'm looking forward to testing this. As I told the others last Thursday, it will be after my ARISS conference, which is the week of Feb 19th. Bob will send the board to me in Florida and I will hand carry it back (hopefully convincing customs that duties should be waived, or paying the bill in person!).

No problem on delaying the merge. We can work off a branch for now and I can merge it later. It's good practice I think for main to be a version that is tested and works.

73 Chris

On Sun, Feb 11, 2024, 17:21 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev@amsat.org> wrote:

...

Version X0.2a pushed upstrem. This is all still in the branch WB1FJ_Port_to_Blinky

First you will note that it will frequently tell you that you have the wrong MRAM version. Some of these warnings were commented out. I may have done it in debugging, but it is important. Lots of things may not work right if this message appears. It gives several alternatives of commands that you can issue, but in this particular case,

YOU MUST ISSUE THE COMMAND 'init new proc'.

After that the messages will stop. The reason for all this is that I added 3 more receive frequency locations in MRAM, and those are only set up with init new proc.

This new version, as I implied above, saves 4 different receive frequencies. "init new proc' initializes them all the same, but you can adjust them with "raise rx freq n m" where n is the receiver number (1-4) and n is the number (in Hz) to raise the frequency by. There is also 'lower rx freq'. The versions for tx freq do not have a chip number. The maximum you can change the frequency for any of these (I think) is 32767Hz (it is 15 bits).

BTW, I think this is actually transmitting something. If I have the tx frequency set out of range, I get a TX queue filling up. ??????

Anyway, let me know if you have questions or if you need other stuff. I'm done for now. And btw, we are again expecting snow Tuesday, so my band rehearsal may be moved to Thursday again :-(

73,

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

---

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