writing and running pigpiod scripts? about pigpio-client

[btsimonh]

I gave a PR which implements all the script functions provided by pigpiod :).

[guymcswain]

I don’t recommend using scripts as they are not thread safe. With pigpio, the canonical way for precise control of gpio is to use the DMA. Look at the waveform methods. They are driven by dma.

[btsimonh]

I'm not sure I understand...

What I would like to achieve is to set values for multiple GPOs effectively simultaneously, like a salvo. I'm not really concerned when they are set; what is important is that they are set together, not one after the other (within limits, obviously. I don't need uS precision).

I do note that once I've run a script which controls certain pins, the pigpio-client has lost control of those pins.
i.e. if I have a gpio open on pin 17, and then run a script which sets pin 17, then the gpio instance in pigpio-client no longer works.
So pigpiod must be trashing the handles of the open gpios if there is a conflict, I guess... not important from my perspective, as I won't be using the gpio instances again after initial setup (output, pwm freq, etc.).

Love the library... very easy to use & the code is pretty understandable :). When looking for a pigpio library, I also found https://github.com/satoren/node-pigpio - it seems comprehensive, but taking a look at how it's written, I would never have been able to understand it ....

[guymcswain]

I’m traveling so getting internet connections. Have you looked at the read/write bank apis? You can update multiple gpio in one command I may not have implemented the client side api. If so, that would be a useful contribution you can add to the library.

…

On Sat, Jan 21, 2023 at 10:10 AM btsimonh ***@***.***> wrote: I'm not sure I understand... What I would like to achieve is to set values for multiple GPOs effectively simultaneously, like a salvo. I'm not really concerned *when* they are set; what is important is that they are set together, not one after the other (within limits, obviously. I don't need uS precision). I do note that once I've run a script which controls certain pins, the pigpio-client has lost control of those pins. i.e. if I have a gpio open on pin 17, and then run a script which sets pin 17, then the gpio instance in pigpio-client no longer works. So pigpiod must be trashing the handles of the open gpios if there is a conflict, I guess... not important from my perspective, as I won't be using the gpio instances again after initial setup (output, pwm freq, etc.). Love the library... very easy to use & the code is pretty understandable :). When looking for a pigpio library, I also found https://github.com/satoren/node-pigpio - it seems comprehensive, but taking a look at how it's written, I would never have been able to understand it .... — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHDHTDFCEEPZ4YKV2SAYCKLWTQC7LANCNFSM6AAAAAAUCLPBRY> . You are receiving this because you commented.Message ID: ***@***.***>