#touchpad

1 messages · Page 1 of 1 (latest)

celest ember
#

also unplugging for a few minutes vs overnight should make no difference

#

what version of CPy are you using?

unborn rain
#

adafruit-circuitpython-raspberry_pi_pico-en_GB-7.1.1

celest ember
#

that should be fine

#

could you upload your program? Use the + on the left

unborn rain
#

maybe i spoke too soon I just tried to nuke it and it didn't reset the error

celest ember
#

you're powering the track pad from a GPIO pin?

unborn rain
#

ya so I can cycle power to the trackpad before starting my I2C connectionnn

celest ember
#

looking up something in the datasheet...

#

the default drive strength of a GPIO pin on an RP2040 is only 4mA. Have you tried this when powering directly from 3.3V?

#

and 5mA may be typical consumption, but if there are surges of consumption (like maybe when you are touching the pad), then the voltage could dip.

unborn rain
#

I have tried with using the 3.3 pin, but was having this issues, which is why I switched.

#

l just looked up the active usage of the trackpad and it's 2.9 mA

#

when I say this issue I mean the resistor error

#

but their maybe multiple reasons for it

celest ember
#

if the I2C on the touchpad gets confused, then it could pull down the SCL or SDA lines (prob SDA) indefinitely, and then that would cause that error

unborn rain
#

but cycling power should fix the issue?

celest ember
#

we have seen this with various I2C sensors. They get wedged and hold down SDA indefinitely.

#

It should

#

there is no reset line, hunh, hmm

#

what is "DR"

unborn rain
#

and what you are describing is exactly why I put the power on a gpio pin

#

dr is data status

#

as in data ready to read

celest ember
#

are R7 and R8 in place on your touchpad?

unborn rain
#

only resistor I have removed is R1

#

I am lookign over the board though

celest ember
#

and you still have the 10k pullups?

unborn rain
#

4.7 k

#

I found r7 and r8 they are on their

celest ember
#

looks like strong drive strength is on, so the power pin has 12mA drive

#

I'm at a loss. If you had some other CircuitPython boards (not RP2040), I'd suggest trying one of those. The I2C problems you are seeing are unusual, and I'd suspect something unusual about the trackpad

unborn rain
#

I also tried the itsy bitsy as you previously suggested

#

it worked for a while

celest ember
#

itsy bitsy what?

unborn rain
#

m4 express

#

but it showed the same resistor error after a while

celest ember
#

that should be fine; this "worked for a while" business, and so forth is very odd, and I cannot explain it, except to blame the trackpad

#

are you still using soldered connections, or did you wire it up on a breadboard?

#

i would suspect a mechanical issue possibly as well (soldering, etc.)

unborn rain
#

I add the pin header to the pico, and added the female end to my touch pad wires. I should add I don't have 1 touch pad, but 3, I have wired them all up, and I have added the header to multiple picos,

celest ember
#

have you tried their arduino software on either the itsy or the RP2040

unborn rain
#

I tried the arduio on a teensey

celest ember
#

it should work on either of the other two with just pin changes

unborn rain
#

but when I tried to compile on a pico i ran into an errors I couldn't figure out

celest ember
#

the m4 would be more "standard". You still need to download our board support package. You can see the itsy guide for more info

unborn rain
#

what do you mean by a board support package ?

celest ember
#

arduino out of the box only supports mostly Arduino boards. For boards from other mfrs, you need to set a URL in the Preferences, and then download the Board Support Package for the mfr's fmaily of boards

unborn rain
#

oh I yes I downloaded the Pico support package

celest ember
unborn rain
#

oh, your talking use Arduino on the m4 express

celest ember
#

make sure you set the board, etc.

unborn rain
#

ok, I am going to bed, thanks for the info

celest ember
#

good night!

#

these are cheap enough, maybe I will order one or two to test

#

you could also try using SPI instead of I2C

unborn rain
#

I thought of that, but then I would have to restart from scratch as I don't know the first think about SPI

celest ember
#

perhaps there is also an issue with the trackpad going to sleep at inopportune times

#

there are some humidity sensors that go to sleep and you have to probe them to wake them up again.

unborn rain
#

If that were the issue. Unplugged it and plugging back it I would think would solve the issue at least temporarily

unborn rain
#

I read in an Arduino post someone had to manually toggle the pull down resistor to get it to start working. Is there a way for me to try this in circuit python? https://electronics.stackexchange.com/questions/228270/i2c-communication-wont-start-unless-sda-pullup-resistor-is-reinserted

celest ember
#

I think that problem is peculiar to that sensor. It's not true in general for I2C.

celest ember
#

From @unborn rain: Just wanted to let you know that I think I have the Trackpad working now. I have done two things. I plugged the trackpad back into the 3.3 v pin, rather then gpio, and I am not running Mu. I left it plugged in for a number of hours and it is still working, where as before it would only last a couple of minutes before kicking up an error.

#

Glad to hear! I am not sure why leaving it connected to Mu would make any difference, but that may not have been the ultimate fix.

unborn rain
#

I was having other issues with mu, specific related to using serial connection. Maybe it is just power, will be able to test further later. For now I have a solution

unborn rain
#

Proof! It total it is MU! I just started up MU, and instantly the program failed, where it had been running flawlessly for hours...

#

well that makes it hard to program and debug

celest ember
#

What exactly happens when it fails? What version of Mu are you using? What is your host computer and OS? And if you start the program with the Mu serial window open, do you see any errors printed?