Skip to main content
Raspberry Pi

Return to Question

Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
clarified that I don't want to just ignore a false warning
Source Link
ericksonla
ericksonla
  • 153
  • 2
  • 7

I'm getting a RuntimeWarning: This channel is already in use, continuing anyway. from a line of code that gets run many times with different pins. I'm concerned that I may be trying to use a GPIO pin that was already being used for something else (for example, I already found one where I was using an I2C pin for GPIO while also using I2C). How can I figure out which pin is causing the error without just manually checking each one?

I tried looking for something like issetup() or similar to check before I run setup, but nothing like that appears to exist.

I'm getting a RuntimeWarning: This channel is already in use, continuing anyway. from a line of code that gets run many times with different pins. How can I figure out which pin is causing the error without just manually checking each one?

I tried looking for something like issetup() or similar to check before I run setup, but nothing like that appears to exist.

I'm getting a RuntimeWarning: This channel is already in use, continuing anyway. from a line of code that gets run many times with different pins. I'm concerned that I may be trying to use a GPIO pin that was already being used for something else (for example, I already found one where I was using an I2C pin for GPIO while also using I2C). How can I figure out which pin is causing the error without just manually checking each one?

I tried looking for something like issetup() or similar to check before I run setup, but nothing like that appears to exist.

Source Link
ericksonla
ericksonla
  • 153
  • 2
  • 7

Which pin "is already in use"?

I'm getting a RuntimeWarning: This channel is already in use, continuing anyway. from a line of code that gets run many times with different pins. How can I figure out which pin is causing the error without just manually checking each one?

I tried looking for something like issetup() or similar to check before I run setup, but nothing like that appears to exist.