<![CDATA[Node GPIO control (fast-gpio wrapper)]]>I couldn't find a node package to control the Omega2 pins (not a fully working one anyway) so thought I'd build one.
Perhaps someone might find it useful:

https://github.com/entozoon/omega2-gpio

It's essentially a fast-gpio wrapper, supporting digital I/O and PWM (no analague, at time of writing).
If anyone fancies contributing, fire over a pull request and I'm sure it'd be cool.

]]>http://community.onion.io/topic/2292/node-gpio-control-fast-gpio-wrapperRSS for NodeWed, 15 Jul 2026 17:16:47 GMTSun, 13 Aug 2017 18:17:41 GMT60<![CDATA[Reply to Node GPIO control (fast-gpio wrapper) on Sun, 13 Aug 2017 18:17:41 GMT]]>I couldn't find a node package to control the Omega2 pins (not a fully working one anyway) so thought I'd build one.
Perhaps someone might find it useful:

https://github.com/entozoon/omega2-gpio

It's essentially a fast-gpio wrapper, supporting digital I/O and PWM (no analague, at time of writing).
If anyone fancies contributing, fire over a pull request and I'm sure it'd be cool.

]]>http://community.onion.io/post/14131http://community.onion.io/post/14131Sun, 13 Aug 2017 18:17:41 GMT<![CDATA[Reply to Node GPIO control (fast-gpio wrapper) on Tue, 21 Nov 2017 06:28:02 GMT]]>looking at your code, seems that might have a sync/async conflict. set() is calling async->spawn but get() is calling execSync() which will block.

With a situation where you have reads and writes one of top of the other (such as a CLK/DATA pair of pins) have you run into an issue with the timing?

]]>http://community.onion.io/post/15142http://community.onion.io/post/15142Tue, 21 Nov 2017 06:28:02 GMT