Skip to content
Discussion options

You must be logged in to vote

Ok, found the problem. I removed old code at one point, thinking it would not be necessary. But, apparently, it is ;).
Setting a GPIO to "input" is only necessary if there is a sensor connected to it. Otherwise, it's possible to read the value of an "output" pin without setting the pin to "input" first. /G<x>,I sets a pin to "input" to define the pins state, but this has the abovementioned effect on "output" pins. On the other hand, setting a value to a GPIO automatically drives the pin as "output". Bug is fixed in the most recent version.

Replies: 5 comments 8 replies

Comment options

You must be logged in to vote
1 reply
@tscholand
Comment options

Comment options

You must be logged in to vote
1 reply
@tscholand
Comment options

Comment options

You must be logged in to vote
2 replies
@tscholand
Comment options

@tscholand
Comment options

Comment options

You must be logged in to vote
2 replies
@tscholand
Comment options

@fredlcore
Comment options

Comment options

You must be logged in to vote
2 replies
@tscholand
Comment options

@fredlcore
Comment options

Answer selected by fredlcore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants