-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I encountered some problems, need help #2
Comments
Looks like those pins have already been opened by something, I'd check the gpio directory first. You can also try use gpio.close(pin) at the start of the code. |
This happens when you run the app and then close it by using ctrl+c in the terminal and then run it again. The pins remain open. Closing them at runtime should help. Sent from my iPhone
|
By the way, the code is really old and not maintained anymore. I suggest you to use this version instead because it's more recent. https://github.com/mirceageorgescu/raspi-tank-2 Sent from my iPhone
|
@mirceageorgescu Thanks for your reply ~ I went to try ~ THX。 |
[raspi-tank-2] cover [raspi-tank] ? |
Hi,mirceageorgescu
This is my reminder being given, what is the reason, what is the solution?
pi@raspberrypi ~/raspi-tank $ sudo node app.js
info - socket.io started
Listening 3000 in development mode
Error when trying to open pin 16
gpio-admin: could not flush data to /sys/class/gpio/export: Device or resource busy
Error when trying to open pin 15
gpio-admin: could not flush data to /sys/class/gpio/export: Device or resource busy
Error when trying to open pin 12
gpio-admin: could not flush data to /sys/class/gpio/export: Device or resource busy
Error when trying to open pin 11
gpio-admin: could not flush data to /sys/class/gpio/export: Device or resource busy
debug - client authorized
info - handshake authorized 3427653791296134524
debug - setting request GET /socket.io/1/websocket/3427653791296134524
debug - set heartbeat interval for client 3427653791296134524
debug - client authorized for
debug - websocket writing 1::
THX
Mr_dbo
The text was updated successfully, but these errors were encountered: