February 2024 - pacsat-dev - mailman.amsat.org

Re: Power coming out of AX5043
by Chris Thompson 17 Feb '24

17 Feb '24

Also, out issue tracker for the software is here: https://github.com/AMSAT-NA/PacSatSW/issues I just added this one, but if you see other problems then feel free to add them or as me to add. Future ideas should be logged as enhancements. We can group all of these into 'projects' if we want or as 'milestones' so it is very flexible and allows a large number of issues to be filtered to just the right ones for an objective. Note that some of the issues are actually closed and I need to do a pass through to clean them up. One other 'rule' that Burns and I have used in the past is that the person who raises the issue is the person who closes it, once they are happy. 73 Chris On Sat, Feb 17, 2024, 09:28 Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Hi all, > > The power setting commands were never ported over from Golf. As Bob said > it is currently hard coded to a minimum level for testing in the shack. > > We will want this to be commandable in the future, at least to a couple of > levels as Burns said. > > 73 > Chris > > On Sat, Feb 17, 2024, 09:18 Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> A couple thoughts (and these are based on memory, not looking at code >> since I am not in my shack) >> >> First, Jim, remember that any changes that I made are all on the git >> branch that starts WB1FJ... And that branch will not work on the >> launchpad. This branch came off "MAIN" so anything in any other branches >> is not included in WB1FJ... >> >> Second, I did not explicitly mess with anything relating to power in my >> last round of changes, although most of the calls into the AX5043 code I >> had to change to include an argument to say which chip to use. For >> something transmit-only, though I'm not sure. >> >> And finally, the way power works on Golf (and I probably did not change >> this when I originally ported it to Launchpad, although someone else may >> have): There is a high power and a low power. The values for high and low >> are either constants or in MRAM. But the commands are essentially to set >> it to high or low power. On Golf, there is a high/low pair for both normal >> mode and safe mode, but there are no such modes on Pacsat of course. Since >> that must have been ripped out at some point--probably that original port, >> or by Chris later--I'm not sure just how the power works at this point. >> >> Sorry, I'd look at more of this, but I have a busy weekend prepping for >> and teaching a ham radio class. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Sat, Feb 17, 2024 at 12:20 AM Jim McCullers via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I did some housekeeping last weekend on the files and it appears I went >>> one step to far and don't have the latest version of the software. >>> I'll pull it down tomorrow. The version I have sets the 0x0020 which is >>> very low. >>> Max power is 0x0fff. >>> >>> Remember the range is not linear. >>> >>> Congrats >>> >>> Jim >>> >>> >>> One more point… >>> Max power 16 dB would with 5V and we are using 3.3v on the AX5043. >>> >>> > On Feb 16, 2024, at 9:25 PM, Bob Stricklin via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> > >>> > I did test a board today and found it was transmitting every 30 >>> seconds with a power level of about -28 dBm. >>> > >>> > I spent some time looking at the code and found where the power level >>> is set to ox0d in a config file and get AX reports this value. >>> > >>> > I see in the data sheet for AX5043 where power should range from -10 >>> dB to 16 dB and uses a 12 bit value to set the level. Possibly we are just >>> adjusting upper 8 bits. >>> > >>> > We will also be losing power in the differential to single ended >>> converter and shaping circuit. I will probe on this a little more tomorrow >>> but likely just leave it alone and move on for now to be sure and ship >>> boards Monday. >>> > >>> > I also see the 30 second interval in the code and some other comments >>> about setting power but does not seem like this is being used. >>> > >>> > I could not get a continuous tone and I did not spend time setting up >>> a tight loop to transmit. >>> > >>> > I did change the call sign in the configuration to mine. >>> > >>> > Bob >>> > >>> > ----------------------------------------------------------- >>> > >>> > 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 >>> >> >> ----------------------------------------------------------- >> >> 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

Re: Power coming out of AX5043
by Chris Thompson 17 Feb '24

17 Feb '24

Hi all, The power setting commands were never ported over from Golf. As Bob said it is currently hard coded to a minimum level for testing in the shack. We will want this to be commandable in the future, at least to a couple of levels as Burns said. 73 Chris On Sat, Feb 17, 2024, 09:18 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > A couple thoughts (and these are based on memory, not looking at code > since I am not in my shack) > > First, Jim, remember that any changes that I made are all on the git > branch that starts WB1FJ... And that branch will not work on the > launchpad. This branch came off "MAIN" so anything in any other branches > is not included in WB1FJ... > > Second, I did not explicitly mess with anything relating to power in my > last round of changes, although most of the calls into the AX5043 code I > had to change to include an argument to say which chip to use. For > something transmit-only, though I'm not sure. > > And finally, the way power works on Golf (and I probably did not change > this when I originally ported it to Launchpad, although someone else may > have): There is a high power and a low power. The values for high and low > are either constants or in MRAM. But the commands are essentially to set > it to high or low power. On Golf, there is a high/low pair for both normal > mode and safe mode, but there are no such modes on Pacsat of course. Since > that must have been ripped out at some point--probably that original port, > or by Chris later--I'm not sure just how the power works at this point. > > Sorry, I'd look at more of this, but I have a busy weekend prepping for > and teaching a ham radio class. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Sat, Feb 17, 2024 at 12:20 AM Jim McCullers via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I did some housekeeping last weekend on the files and it appears I went >> one step to far and don't have the latest version of the software. >> I'll pull it down tomorrow. The version I have sets the 0x0020 which is >> very low. >> Max power is 0x0fff. >> >> Remember the range is not linear. >> >> Congrats >> >> Jim >> >> >> One more point… >> Max power 16 dB would with 5V and we are using 3.3v on the AX5043. >> >> > On Feb 16, 2024, at 9:25 PM, Bob Stricklin via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> > >> > I did test a board today and found it was transmitting every 30 >> seconds with a power level of about -28 dBm. >> > >> > I spent some time looking at the code and found where the power level >> is set to ox0d in a config file and get AX reports this value. >> > >> > I see in the data sheet for AX5043 where power should range from -10 dB >> to 16 dB and uses a 12 bit value to set the level. Possibly we are just >> adjusting upper 8 bits. >> > >> > We will also be losing power in the differential to single ended >> converter and shaping circuit. I will probe on this a little more tomorrow >> but likely just leave it alone and move on for now to be sure and ship >> boards Monday. >> > >> > I also see the 30 second interval in the code and some other comments >> about setting power but does not seem like this is being used. >> > >> > I could not get a continuous tone and I did not spend time setting up a >> tight loop to transmit. >> > >> > I did change the call sign in the configuration to mine. >> > >> > Bob >> > >> > ----------------------------------------------------------- >> > >> > 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 >> > > ----------------------------------------------------------- > > 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: Power coming out of AX5043
by Burns Fisher (AMSAT) 17 Feb '24

17 Feb '24

A couple thoughts (and these are based on memory, not looking at code since I am not in my shack) First, Jim, remember that any changes that I made are all on the git branch that starts WB1FJ... And that branch will not work on the launchpad. This branch came off "MAIN" so anything in any other branches is not included in WB1FJ... Second, I did not explicitly mess with anything relating to power in my last round of changes, although most of the calls into the AX5043 code I had to change to include an argument to say which chip to use. For something transmit-only, though I'm not sure. And finally, the way power works on Golf (and I probably did not change this when I originally ported it to Launchpad, although someone else may have): There is a high power and a low power. The values for high and low are either constants or in MRAM. But the commands are essentially to set it to high or low power. On Golf, there is a high/low pair for both normal mode and safe mode, but there are no such modes on Pacsat of course. Since that must have been ripped out at some point--probably that original port, or by Chris later--I'm not sure just how the power works at this point. Sorry, I'd look at more of this, but I have a busy weekend prepping for and teaching a ham radio class. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sat, Feb 17, 2024 at 12:20 AM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I did some housekeeping last weekend on the files and it appears I went > one step to far and don't have the latest version of the software. > I'll pull it down tomorrow. The version I have sets the 0x0020 which is > very low. > Max power is 0x0fff. > > Remember the range is not linear. > > Congrats > > Jim > > > One more point… > Max power 16 dB would with 5V and we are using 3.3v on the AX5043. > > > On Feb 16, 2024, at 9:25 PM, Bob Stricklin via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > > > I did test a board today and found it was transmitting every 30 seconds > with a power level of about -28 dBm. > > > > I spent some time looking at the code and found where the power level is > set to ox0d in a config file and get AX reports this value. > > > > I see in the data sheet for AX5043 where power should range from -10 dB > to 16 dB and uses a 12 bit value to set the level. Possibly we are just > adjusting upper 8 bits. > > > > We will also be losing power in the differential to single ended > converter and shaping circuit. I will probe on this a little more tomorrow > but likely just leave it alone and move on for now to be sure and ship > boards Monday. > > > > I also see the 30 second interval in the code and some other comments > about setting power but does not seem like this is being used. > > > > I could not get a continuous tone and I did not spend time setting up a > tight loop to transmit. > > > > I did change the call sign in the configuration to mine. > > > > Bob > > > > ----------------------------------------------------------- > > > > 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

Re: Power coming out of AX5043
by Jim McCullers 17 Feb '24

17 Feb '24

I did some housekeeping last weekend on the files and it appears I went one step to far and don't have the latest version of the software. I'll pull it down tomorrow. The version I have sets the 0x0020 which is very low. Max power is 0x0fff. Remember the range is not linear. Congrats Jim One more point… Max power 16 dB would with 5V and we are using 3.3v on the AX5043. > On Feb 16, 2024, at 9:25 PM, Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > I did test a board today and found it was transmitting every 30 seconds with a power level of about -28 dBm. > > I spent some time looking at the code and found where the power level is set to ox0d in a config file and get AX reports this value. > > I see in the data sheet for AX5043 where power should range from -10 dB to 16 dB and uses a 12 bit value to set the level. Possibly we are just adjusting upper 8 bits. > > We will also be losing power in the differential to single ended converter and shaping circuit. I will probe on this a little more tomorrow but likely just leave it alone and move on for now to be sure and ship boards Monday. > > I also see the 30 second interval in the code and some other comments about setting power but does not seem like this is being used. > > I could not get a continuous tone and I did not spend time setting up a tight loop to transmit. > > I did change the call sign in the configuration to mine. > > Bob > > ----------------------------------------------------------- > > 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

Re: Power coming out of AX5043
by Bob Stricklin 17 Feb '24

17 Feb '24

One more point… Max power 16 dB would with 5V and we are using 3.3v on the AX5043. > On Feb 16, 2024, at 9:25 PM, Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > I did test a board today and found it was transmitting every 30 seconds with a power level of about -28 dBm. > > I spent some time looking at the code and found where the power level is set to ox0d in a config file and get AX reports this value. > > I see in the data sheet for AX5043 where power should range from -10 dB to 16 dB and uses a 12 bit value to set the level. Possibly we are just adjusting upper 8 bits. > > We will also be losing power in the differential to single ended converter and shaping circuit. I will probe on this a little more tomorrow but likely just leave it alone and move on for now to be sure and ship boards Monday. > > I also see the 30 second interval in the code and some other comments about setting power but does not seem like this is being used. > > I could not get a continuous tone and I did not spend time setting up a tight loop to transmit. > > I did change the call sign in the configuration to mine. > > Bob > > ----------------------------------------------------------- > > 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

Power coming out of AX5043
by Bob Stricklin 17 Feb '24

17 Feb '24

I did test a board today and found it was transmitting every 30 seconds with a power level of about -28 dBm. I spent some time looking at the code and found where the power level is set to ox0d in a config file and get AX reports this value. I see in the data sheet for AX5043 where power should range from -10 dB to 16 dB and uses a 12 bit value to set the level. Possibly we are just adjusting upper 8 bits. We will also be losing power in the differential to single ended converter and shaping circuit. I will probe on this a little more tomorrow but likely just leave it alone and move on for now to be sure and ship boards Monday. I also see the 30 second interval in the code and some other comments about setting power but does not seem like this is being used. I could not get a continuous tone and I did not spend time setting up a tight loop to transmit. I did change the call sign in the configuration to mine. Bob

1 0

Pacsat dev mtg 2/15/2024
by Bill 15 Feb '24

15 Feb '24

Pacsat dev mtg 2/15/2024 Thu, Feb 15, 2024 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/162004557 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (646) 749-3122 - One-touch: tel:+16467493122,,162004557# Access Code: 162-004-557 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 162 004 557 Or dial directly: 162004557(a)67.217.95.2 or 67.217.95.2##162004557 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: One more time to try--I think I am done :-)
by Burns Fisher (AMSAT) 12 Feb '24

12 Feb '24

Odd, I'm not sure how I got the wrong pins for the startup. But glad it was easy to fix. I think the error in start rx error 6. I think error 6 means the PLL did not lock. And that is expected on 2 meters unless that inductor gets put in. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sun, Feb 11, 2024 at 9:38 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > The code is working to turn PA and AX on and off. The only thing that is > different is PA is on 98 and AX is on 99. I just switched the wires and > everything is working as needed. The set pa on and off and set ax on and > off also working. > > I have also seen the message TX QUEUE FULL could not add UI frame to > Packet Queue at startup. This message then keeps popping up. > > Also on startup i see > ERROR: In start RX, axradio_init return 6. > Key magic mismatch > > One possible issue is the AX5043 will have a 200 us delay to power up then > some time for its on power up. May need a small delay after turning on AX > power. > > We can work with this version of the code for now. > > Thanks, > > Bob > > > > > On Feb 11, 2024, at 4:50 PM, Chris Thompson via pacsat-dev < > pacsat-dev(a)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(a)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(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

Re: One more time to try--I think I am done :-)
by Bob Stricklin 12 Feb '24

12 Feb '24

The code is working to turn PA and AX on and off. The only thing that is different is PA is on 98 and AX is on 99. I just switched the wires and everything is working as needed. The set pa on and off and set ax on and off also working. I have also seen the message TX QUEUE FULL could not add UI frame to Packet Queue at startup. This message then keeps popping up. Also on startup i see ERROR: In start RX, axradio_init return 6. Key magic mismatch One possible issue is the AX5043 will have a 200 us delay to power up then some time for its on power up. May need a small delay after turning on AX power. We can work with this version of the code for now. Thanks, Bob On Feb 11, 2024, at 4:50 PM, Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> 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(a)amsat.org<mailto:[email protected]>> 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(a)amsat.org<mailto:[email protected]> 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<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://mailman.amsat.org/> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> 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<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: One more time to try--I think I am done :-)
by Burns Fisher (AMSAT) 11 Feb '24

11 Feb '24

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(a)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(a)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(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