- pacsat-dev - mailman.amsat.org

Re: Pacsat ver 0.1e update
by Burns Fisher (AMSAT) 05 Aug '23

05 Aug '23

I was looking at this with Bill yesterday. That message should happen only if there is no response from the I2c message to the temp chip. Since it works just fine on mine, I'm guessing there is a hardware issue on Bill's board. He checked all the pins, so that implies to me either the chip is bad, or there is some issue with the board or the header connecting it to the LaunchPad. Or possibly a pullup on one of the I2c lines. I don't recall if there is a physical pullup or if they are programmed in the TMS570. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sat, Aug 5, 2023 at 10:00 AM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I upgraded my pacsat test hardware to software version 0.1d. It didn't > run. I discovered that the software was hanging up when it tried to > initialize the i2c temp sensor. That is new in 0.1d. In > troubleshooting with Chris and Burns we discovered that the calls to the > i2c initialization code were misplaced. That was fixed and uploaded to > github as version 0.1e. > > Version 0.1e runs on my test hardware but gives an i2c error message > every time it attempts to read the temp. This could be a hardware fault > on my test hardware. I have checked the temp sensor and all pins seem > to be correctly connected and connectivity of the SDL and SCA lines with > the TMS570 board is OK. I will be connecting the temp sensor to a > raspberry pi and running tests on that component. > > In order to continue to use the test hardware I have commented out > line191 in TelemAndControlTask.c which simply reports an error by > calling debug_print(). Entering 'get temp' on the pacsat console still > shows the error message. > > I'm having too much fun!! > > 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 >

1 0

Pacsat ver 0.1e update
by Bill Reed 05 Aug '23

05 Aug '23

I upgraded my pacsat test hardware to software version 0.1d. It didn't run. I discovered that the software was hanging up when it tried to initialize the i2c temp sensor. That is new in 0.1d. In troubleshooting with Chris and Burns we discovered that the calls to the i2c initialization code were misplaced. That was fixed and uploaded to github as version 0.1e. Version 0.1e runs on my test hardware but gives an i2c error message every time it attempts to read the temp. This could be a hardware fault on my test hardware. I have checked the temp sensor and all pins seem to be correctly connected and connectivity of the SDL and SCA lines with the TMS570 board is OK. I will be connecting the temp sensor to a raspberry pi and running tests on that component. In order to continue to use the test hardware I have commented out line191 in TelemAndControlTask.c which simply reports an error by calling debug_print(). Entering 'get temp' on the pacsat console still shows the error message. I'm having too much fun!! Bill

1 0

AX5043 Power Output
by Jim McCullers 03 Aug '23

03 Aug '23

The OnSemi AX5043 power study I mentioned last week can be found at: https://www.onsemi.cn/pub/collateral/and9314-d.pdf I've verified with duplicating their input numbers as best as possible and see similar results. As well, I performed a series of test using different criteria and again verified that the power output of the AX5043 is not a linear line but one that tapers off as the power is decreased. Therefore the formula given in the programming manual and duplicated by several developments is incorrect in setting power based on a percentage. In our use it is irrelative as we will be measuring the power output of the power amplifier and setting the AX5043 output as needed to drive the PA. However, it is good to know these things. As for harmonics; at 435.3 mhz with no output filtering the second harmonic is down by 34 db and the third by 44 db. With adequate output filtering on the power amplifier there should be no issues.

1 0

Pacsat dev mtg 8/3/2023
by Bill 03 Aug '23

03 Aug '23

Pacsat dev mtg 8/3/2023 Thu, Aug 3, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/582248093 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (872) 240-3212 - One-touch: tel:+18722403212,,582248093# Access Code: 582-248-093 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 582 248 093 Or dial directly: 582248093(a)67.217.95.2 or 67.217.95.2##582248093 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Pacsat ver 0.1d
by Chris Thompson 03 Aug '23

03 Aug '23

What are the symptoms? Does it fail to compile? 73 Chris On Thu, Aug 3, 2023, 10:41 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Haven't been able to get Pacsat ver 0.1d working. 0.1c worked fine. > Still trying to resolve this. > > Anyone else have 0.1d working? > > 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 >

1 0

Pacsat ver 0.1d
by Bill Reed 03 Aug '23

03 Aug '23

Haven't been able to get Pacsat ver 0.1d working. 0.1c worked fine. Still trying to resolve this. Anyone else have 0.1d working? Bill

1 0

Version 0.1d - Telemetry enabled
by Chris Thompson 28 Jul '23

28 Jul '23

I've merged my code brach into main, updated the version to 0.1d and pushed main back to github. This version supports the telemetry that I have prototyped. If you want to receive the telemetry you also need version 0.45b of the groundstation from here: https://www.g0kla.com/pacsat/index.php 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat dev mtg 7/27/2023
by Corey Minyard 27 Jul '23

27 Jul '23

I may or may not make it tonight. I don't have much to report, though. -corey On Thu, Jul 27, 2023 at 06:48:40PM +0000, Bill via pacsat-dev wrote: > Pacsat dev mtg 7/27/2023 > > Let's discuss what we might present at the amsat annual meeting. > > Thu, Jul 27, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/835171821 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (408) 650-3123 > - One-touch: tel:+14086503123,,835171821# > > Access Code: 835-171-821 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 835 171 821 > Or dial directly: 835171821(a)67.217.95.2 or 67.217.95.2##835171821 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > 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

Re: Pacsat dev mtg 7/27/2023
by Burns Fisher (AMSAT) 27 Jul '23

27 Jul '23

Apologies, but I will likely not make it back from dinner with friends in time tonight. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Jul 27, 2023 at 2:48 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg 7/27/2023 > > Let's discuss what we might present at the amsat annual meeting. > > Thu, Jul 27, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/835171821 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (408) 650-3123 > - One-touch: tel:+14086503123,,835171821# > > Access Code: 835-171-821 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 835 171 821 > Or dial directly: 835171821(a)67.217.95.2 or 67.217.95.2##835171821 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > 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

Pacsat dev mtg 7/27/2023
by Bill 27 Jul '23

27 Jul '23

Pacsat dev mtg 7/27/2023 Let's discuss what we might present at the amsat annual meeting. Thu, Jul 27, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/835171821 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (408) 650-3123 - One-touch: tel:+14086503123,,835171821# Access Code: 835-171-821 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 835 171 821 Or dial directly: 835171821(a)67.217.95.2 or 67.217.95.2##835171821 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0