August 2023 - pacsat-dev - mailman.amsat.org

Temp sensor
by Bill Reed 07 Aug '23

07 Aug '23

My temp sensor at get temp shows 90 degrees but my infrared thermometer reads 79. Is this an issue? Bill

1 0

Re: Problem solved
by Chris Thompson 07 Aug '23

07 Aug '23

Glad to hear this is working. I have noticed one thing with version X0.1e. When you press the reset button on the launchpad it pauses for about a second before printing to the console. Is that an intentional change to the boot process? Otherwise we should investigate what changed. 73 Chris On Sat, Aug 5, 2023 at 5:26 PM Bill Reed via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k..... > > > ----------------------------------------------------------- > > 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Problem solved
by Jim McCullers 06 Aug '23

06 Aug '23

That's where it went! Knew the inventory was off by one. Woops The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k..... ----------------------------------------------------------- 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

Problem solved
by Bill Reed 05 Aug '23

05 Aug '23

The MAX31725 SCL line had a zero ohm pullup. Fixed with 4.7k.....

1 0

Re: Pacsat ver 0.1e update
by Chris Thompson 05 Aug '23

05 Aug '23

I think I just had to clear MRAM. The garbage must have been some old data. Otherwise it seems to work. 73 Chris On Sat, Aug 5, 2023 at 10:53 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Confirmed that X1.0e runs here too. get temp returns the temperature as > expected. > > But there is an issue. There is garbage printed to the console, likely > when we send a frame: > > [image: image.png] > > 73 > Chris > > On Sat, Aug 5, 2023 at 10:40 AM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> 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/[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 >> > > > -- > 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/[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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat ver 0.1e update
by Bob Stricklin 05 Aug '23

05 Aug '23

Bill, I would lean more toward your issue being a problem on the soldering or pull up resistors on the I2C bus. Using a meter with the power to the board off you might check the resistance on the clock and data bus to ground. Measure the value of resistance across the pull up resistors to be sure they are a big value like a few k ohms. Then look at the solder connects as best you can and make sure things are making contact. Instead you can use an oscilloscope and watch the action on the clock and data bus just to be sure something is there and cleanly jumping between about 3V and ground. The temp sensor may be solder on the board with the wrong orentation. Usually the part is fine it is getting proper connection that is a problem. There is a device sold I have used in the past called an Aardvark to monitor and talk to an I2C bus. I have also used code on a rpi to do this which I can find if needed. I think the bus voltages are the same so you could just jumper over from the pi I2C to the pacsat-dev board and include ground. Doing all this is more difficult and takes time. Bob > On Aug 5, 2023, at 9: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/[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: Pacsat ver 0.1e update
by Chris Thompson 05 Aug '23

05 Aug '23

Confirmed that X1.0e runs here too. get temp returns the temperature as expected. But there is an issue. There is garbage printed to the console, likely when we send a frame: [image: image.png] 73 Chris On Sat, Aug 5, 2023 at 10:40 AM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > 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/[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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

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/[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

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