Thanks for following up. I'll look into this. My experience is more in web apps and I've gotten into python for playing with raspberry pi and have slowly taken more interest in learning about hardware. So your suggestions will be something I'll have to research and then test out. Tomorrow I'll post more of my code if you're curious to see. But this is separate from my robot. These picos are connected to a pi and other than that, the pi simply runs chromium at boot with an address to connect to the bot thanks to a flask server running on the robot's pi. The reason for the picos is to have keys/leds/rotary encoders to fire keycodes because the web server is listening for events like keyup and keydown. I'll post again tomorrow, but for now bedtime as I have to go to the junkyard tomorrow to look for a power steering pump for my mini : )It's unclear how the robot's software works. So it's hard for anyone to do anything other ask for more data. Step-by-step troubleshooting can provide further information towards diagnosing and solving the problem. Often, we use fallback known-good software to test things.
It is possible to verify that both Pico boards work (or does not) in a connected-at-bootup scenario by manually running a test program to connect to each Pico, separately, then simultaneously. If say they are controlled via serial USB, first check that the devices are present. Maybe run programs to talk serial USB, see of both work, and then simultaneously. If the steps work manually, then you need to look further along the chain. And so on. A step-by-step determination of what works and what doesn't.
Statistics: Posted by elpollopollopollo — Sat May 11, 2024 12:24 am