Hi, Owen Thanks for doing some work on this, it look cool.
The current set of Gobot i2c drivers all use the sysfs Read() and Write() interface. The new SMBLOCK based interface is an experimental interface, and seems like it seems some additional work on Raspi. I will take a look into it, if you don't mind entering an issue on our GH tracker it would be appreciated: https://github.com/hybridgroup/gobot/issues Thanks! Regards, Ron On Sunday, February 19, 2017 at 8:01:32 PM UTC+1, Owen Waller wrote: > > Hi Everyone, > > With the release of GoBot 1.2 I thought I would try and put together a > "metal bot" for the PiGlow on a Raspberry Pi 1. > > The PiGlow <https://shop.pimoroni.com/products/piglow> is based around a > SN3218 IC that drives the 18 leds on the board. The SN3218 communication > with the Pi is via 12c. > GoBot 1.2 rewrote the i2c subsystem, but I can't get it to drive the > PiGlow at all. > > My stab at getting this to work is here: > https://play.golang.org/p/_DDEiwZqt1 > > The code is in the style of a "metal bot" as I want to reuse this code as > part of a small project to replace some python code. > The code should turn on LED zero. But when the code runs nothing happens. > There's no terminal output indicating a non-nil error and there are lights > on the PiGlow. > > The code is based on the existing PiGlow library, by Toon Schoenmakers[1] > - which does not use GoBots i2c subsystem. That libraries test code runs > fine on the board, so the PiGlow itself is working ok. My initialisation > code is based on Toon's. > > Can a friendly Gopher who has more experience of GoBot and a similar > hardware set-up, spot what I might be doing wrong? > > Thanks > > Owen > > [1]https://github.com/schoentoon/piglow > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
