- pacsat-dev - mailman.amsat.org

Re: Launchpad for Ron
by Chris Thompson 17 Jun '24

17 Jun '24

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 < pacsat-dev(a)amsat.org> 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 < > pacsat-dev(a)amsat.org> 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 -- pacsat-dev(a)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(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/pacsat-dev@amsat.org > 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: Launchpad for Ron
by Chris Thompson 17 Jun '24

17 Jun '24

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 < pacsat-dev(a)amsat.org> 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 -- pacsat-dev(a)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(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

Launchpad for Ron
by Bill Reed 17 Jun '24

17 Jun '24

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

1 0

Cursory look at compression on Pacsat
by Corey Minyard 16 Jun '24

16 Jun '24

I spent some time looking at implementations of compression algorithms. As Bob pointed out, memory can be an issue with these libraries. I was hoping to say that zlib (gzip) would be suitable, but its minimum memory requirement appears to be 128K. There appears to be a way to reduce that, but it's still probably going to be too big. Later, better algorithms like bzip are going to be even more memory intensive. I searched around and there are a large number of compression libraries that are free and designed for microcontrollers, with memory requirements in the hundreds of bytes (or even less!). None are as good as even zlib, but they are better than LZW (compress) and would be adequate. Also, more critically, they are designed to compress small amounts of data efficiently. The trouble then becomes finding one with a Java implementation, if we are planning to send the compressed data over the download or uplink. Is this something worth pursuing? -corey - AE5KM

1 0

Launchpad working
by Bill Reed 14 Jun '24

14 Jun '24

I was able to upload software to the launchpad. It was a "stupid operator" error. Bill

1 0

Pacsat dev mtg
by Bill 13 Jun '24

13 Jun '24

Pacsat dev mtg Thu, Jun 13, 2024 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/941540501 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3122 - One-touch: tel:+15713173122,,941540501# Access Code: 941-540-501 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 941 540 501 Or dial directly: 941540501(a)67.217.95.2 or 67.217.95.2##941540501 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

LaunchPad Weight
by Jim McCullers 11 Jun '24

11 Jun '24

I measured the TI LaunchPad/Pacsat board combination and the weight was less than expected. The combined weight was 2.9 ounces. The TI launch pad weighs 1.6 oz and the Pacsat board 1.2. The extra combined ounce is attributed to the scales which measure only .1 degree. This is a link to the TMS370 LaunchPad web site that includes documentation as well as schematic. Jim McCullers WA4CWI

1 0

Pacsat Alternative Receiver Front End Design
by Jim McCullers 06 Jun '24

06 Jun '24

For consideration to reduce component cost and weight without loss of performance.

1 0

Pacsat dev mtg 6/6/2024
by Bill 06 Jun '24

06 Jun '24

Pacsat dev mtg 6/6/2024 Thu, Jun 6, 2024 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/156305253 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3112 - One-touch: tel:+15713173112,,156305253# Access Code: 156-305-253 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 156 305 253 Or dial directly: 156305253(a)67.217.95.2 or 67.217.95.2##156305253 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Pacsat new team members
by Chris Thompson 05 Jun '24

05 Jun '24

Great, I look forward to it. Welcome Cameron and Ron. 73 Chris On Wed, Jun 5, 2024, 16:20 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Two new team members will be joining us at tomorrows meeting: > > Cameron Castillo - circuit board layout > > Ron Fevig, N0UCV - Testing and user documentation > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0