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@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@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@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org