Re: [go-nuts] Re: Gobot Beaglebone Black GPIO question...

Hi, everyone The issue turned out to simply be a matter of a misnamed pin, combined with some changes to how you configure the BeagleBone. The Beaglebone's Debian OS is now much simpler to setup, so some of our directions needed to be removed, as they were also interferring with the newer distr

Re: [go-nuts] Re: Gobot Beaglebone Black GPIO question...

>From what I recall gobot uses sysfs bases GPIO driver that writes to /sys/class/gpio/* (using mmaped GPIOs is another way) using standard file io. If I am you, I would start with simply using the digitalinput or button driver (https://godoc.org/gobot.io/x/gobot/drivers/gpio) straight. I think its

Re: [go-nuts] Re: Gobot Beaglebone Black GPIO question...

Gobot is great if you want to delegate the "event loop". If you want to keep control, you may want to take a look periph.io, which supports interrupt based edge detection , so no need to do a busy loop. Which library to use depends about how you

Re: [go-nuts] Re: Gobot Beaglebone Black GPIO question...

If you have more time to spare on this project, try to circumvent the events / subscriber functionality. Try to see if you can read directly from the adaptor: https://github.com/hybridgroup/gobot/blob/master/platforms/beaglebone/beaglebone_adaptor.go#L151 so inside your work function, you would d

[go-nuts] Re: Gobot Beaglebone Black GPIO question...

I'm at a loss... https://godoc.org/gobot.io/x/gobot#Eventer I think the first thing is that I'm not sure I understand how to diagnose this codehow to validate it's doing what I think it may or may not be doing. -- You received this message because you are subscribed to the Google Groups

[go-nuts] Re: Gobot Beaglebone Black GPIO question...

I put a fmt.Println() at the beginning and end of that work function and they both print, so it appears they are only running once...then it's no longer waiting for input. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] Re: Gobot Beaglebone Black GPIO question...

> > Not sure > It's fairly common demo code that more then a few people have used. Maybe it's wrong... > https://godoc.org/gobot.io/x/gobot/drivers/gpio#ButtonDriver > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe fro

[go-nuts] Re: Gobot Beaglebone Black GPIO question...

Hmm... I actually looked at that .On method. It does in fact call Subscribe(), then spawns a go routine. Strange, so maybe it is a device specific issue. Maybe try to move those .On handlers before the work := func() block, just in case... On Monday, 12 February 2018 00:41:58 UTC-5, Silviu Ca

[go-nuts] Re: Gobot Beaglebone Black GPIO question...

Hi Curtis, I used to play a bit with a Beaglebone Black a few years ago, but it's now gathering dust at my father's place. I really liked it at the time. Can you double check that you are correctly using your *work := func() ...* construct ? Here's what that documentation of the gobot.NewRobot