
I am using the Aardvark I2C/SPI Host Adapter with Aardvark Software API as a master device on the I2C interface. I am observing that the I2C signals remain low, which seems related to the py_aa_target_power() function.
My questions - why are the lines not staying high as expected after re-enabling power? Is there something I might be missing in the configuration or the timing?
For my setup, I am using the Level Shifter Board to scale the voltage from 5V down to 3.3V. In my implementation, I invoke the py_aa_target_power() function after configuring the I2C interface, following the examples provided in the Python API documentation. The VCC is connected to Pin 4, which is specified for powering the I2C bus.
I also use AA_TARGET_POWER_QUERY to check if the current state is as expected. After pins 4 and 6 are both activated, the status reports as correct, but when measuring their voltages directly, it appears that the pins are not powered.
Response from Technical Support:Thank you for your questions! This behavior appears to be related to hardware, not software, specifically the internal pull-up resistors of the Aardvark adapter.
If the lines are not remaining high as expected after re-enabling power, this is most likely related to the behavior of the internal pull-up resistors within the Aardvark adapter.
Here is a simple overview of disabling pull-up resistors with API commands as well as Control Center Serial Software:
For more details about the roles of pull-up resistors, refer to this article:
We hope this answers your questions. Additional resources that you may find helpful include the following:
If you want more information, feel free to contact us with your questions, or request a demo that applies to your application.