Ok, I can't reproduce that. I checked out the LaunchPad branch and flashed the LaunchPad here. It does not reset every 10 seconds. It runs fine with a changed callsign. With "monitor on" I can see a received packet from the ground.
Some things to note. If the RxTask was not working then that was perhaps causing the watchdog to reset. I don't see anything that would cause that, but perhaps the initial setup hangs or the read RSSI hangs. That would trigger the watchdog. But with that said get AX is reading from the Chip it seem...
You should try to reset the frequencies to their default values. Rhe 900MHz frequency does not look like it ranged correctly so perhaps that caused the init to fail. You can't reset everything with "init new proc" because it looks like that was not defined at this time. But you should be able to use the command "lower rx freq" and then "save freq". But there is a maximum amount you can lower it as I remember...
If it is a new LaunchPad from TI then I seem to remember that Jim had some setup instructions. There was a jumper or two to add or remove. Did you do those changes? Or was this the working LunchPad board from Bob which already had those changes?
73 Chris
On Mon, Jun 17, 2024 at 4:26 PM Chris Thompson via pacsat-dev < [email protected]> wrote:
I will try to reproduce that here. To see if it is a hardware issue, or not.
73 Chris
On Mon, Jun 17, 2024 at 1:05 PM Bill Reed via pacsat-dev < [email protected]> wrote:
I received Bob's launchpad and have found the following:
I am using the Launchpad branch on github.com/AMSAT-NA/PacSatSW
I edited the config.h file to change the pacsat callsign to Ron's call - k0UND
I started testing and found that the launchpad would transmit OK but it didn't receive.
I connected the console and found that the launchpad was resetting every 10 seconds. The reset was precede by "WDxx"
I assumed that the Watchdog was causing the reset and I commented out "#define WATCHDOG ENABLE" This change stopped the resets but it still didn't receive.
Pacsat>get ax5043 status provided:
AX5043 dev 1 TX: FIFOSTAT: 21 PWRMODE:: 0d XTALCAP: 0 PLLLOOP: 0a PLLCPI: 10 PLLVCOI: 97 PLLRANGINGA: 49 PLLVCODIV: 24 FREQ 435759999 Hz MODULATION: a TXPWRCOEFFB0: 20 TXPWRCOEFFB1: 0
AX5043 dev 0 RX: FIFOSTAT: 00 PWRMODE: 05 XTALCAP: 0 PLLLOOP: 09 PLLCPI: 08 PLLVCOI: 97 PLLRANGINGA: 08 PLLVCODIV: 30 FREQ 915300000 Hz MODULATION: 8 TXPWRCOEFFB0: 20 TXPWRCOEFFB1: 0
It looks like the RX dev 0 FIFOSTAT:00 and FREQ 915300000 Hz could indicate a problem.
Frequency should read FREQ 145835000 Hz
Could this be an AX5043 chip problem?
Any suggestions on what I might do for additional debugging?
Does anyone have an available launchpad I can send to Ron?
Bill
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-- Chris E. Thompson [email protected] [email protected]
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org