opened notification socket with handle=0 about pigpio-client

[giminni]

BTW I use the latest pigpio daemon (64) if I use the node-red-pigpio node it works with the same
configuration (172.17.0.1:8888), therefore I assume it is a socket handling issue.

@guymcswain is there any workaround or mitigation?

[guymcswain]

Sorry that I have just now seen this. I'll will be looking into this issue today and will get back to you. Thanks for using pigpio-client!

…

On Dec 27, 2017 4:29 AM, "Giovanni Minniti" ***@***.***> wrote: @guymcswain <https://github.com/guymcswain> is there any workaround or mitigation? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcZ5jBqxM5twl4bmR7CzI6K-1RloHLiKks5tEhwPgaJpZM4RJ_xH> .

[guymcswain]

Thank you for the debug trace. I see that a notification handle (0) was opened. You performed two gpio.modeSet() commands to pins 11 and 13, then write 0 and 1 respectively to these pins. If you read the pin values back you should observe their levels in the last 32 bits (little endian). So I would expect response= 3 0 0 0 13 0 0 0 0 0 0 0 1 0 0 0 after reading pin 13. Also, the notification handle is used internally to pigpio-client. It is used for things like gpio.notify(). Please clarify your question if I have missed your point.

…

On Dec 27, 2017 4:29 AM, "Giovanni Minniti" ***@***.***> wrote: @guymcswain <https://github.com/guymcswain> is there any workaround or mitigation? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcZ5jBqxM5twl4bmR7CzI6K-1RloHLiKks5tEhwPgaJpZM4RJ_xH> .

[giminni]

I connected GPIO pin11 and pin13 to a relay card. If I use node-red-contrib-pigpio I can successful toggle the relay. If I use your library I am unable to open or close the relay contact.

According to the debug list, I see no change of value (request/response shows the same bit array)

My question is the pigpioVersion correct?
Why I cannot toggle the relay writing 0 to pin11 or pin13?
Which settings are right?
Is handle=0 correct?
Do I need pipelining or other flags?
Is there a workaround for this?

[guymcswain]

My question is the pigpioVersion correct?

Yes

Is handle=0 correct?

Yes. But this could also be any positive integer. It's what the OS returns as a file descriptor.

Do I need pipelining or other flags?

Pipelining settings should not matter to functionality. It is there more for convenience and possibly performance improvement.

Why I cannot toggle the relay writing 0 to pin11 or pin13?

Unknown. What you showed above should work. Are you connected to pins 23 (GPIO11) and 33 (GPIO13) on the Raspberry Pi 40 pin connector? Make sure you don't have SPI enabled as GPIO11 has alternate function as SPI_CLK.

[guymcswain]

@giminni , please let me know if you need additional assistance, have abandoned pigpio-client or otherwise so that I may close this issue.

[giminni]

@guymcswain
finally I found my error.

It was a bit misleading having myPin = GPIO, e.g. pin11 is GPIO(17).
Can you add some notes into your examples, this would reduce hunting bugs where there aren't.

Your library works perfectly, thank for helping me pointing into the right direction.

Keep up the work on this library!