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
On is false and off is true #2
Comments
I don't have a DS2406 handy. Can you see if this does the right thing? |
Great, Ill have a go at it this weekend. Btw are you into Go engines? Saw such repositories on your profile. Skickat från min mobil, -------- Originalmeddelande -------- I don't have a DS2406 handy. Can you see if this does the right thing? — |
I write a lot of code in the go programming language. I was unfamiliar with go engines. I use mostly brushless electric motors. :) |
Oh I thought it was about the game Go :-) Software engines that plays Go (like chess computers) is an interesting field. They still dont beat good humans. Skickat från min mobil, -------- Originalmeddelande -------- I write a lot of code in the go programming language. I was unfamiliar with go engines. I use mostly brushless electric motors. :) — |
Hi, I finally got around to testing, sorry for the delay. It works fine now, thanks for the effort. Håkan Westrin 20 december 2014, Dustin Sallings notifications@github.com skrev:
|
Hi again, sorry for bothering you again. I asked about fixing the boolean value half a year ago since the setSwitchState was not consistent with the getSwitchState. Now they are consistent which is good, thanks. The problem is now that setSwitchState(true) does not turn the switch on. That is, it does not open the drain PIO pin. It actually closes it. setSwitchState(false) will on the other hand close the switch (activate the sink capability of the pin). One could argue about what boolen value means open or closed (and on or off) but you own example suggest you share my view that true means on (means closed). This means in short that I think my original comment was wrong, it was not the getSwitchState() that was in error but actually the setSwitchState().
The text was updated successfully, but these errors were encountered: