|Re: [ecf-dev] pi4j and OSGi (remote) services|
For everyone's additional info:
I've created, committed, pushed 3 projects now to the RaspberryPI repo:
1) A 'GPIO pin service type' (IGPIOPin) API project, with just two interfaces: IGPIOPin and IGPIOPinAsync. In the future, this may very well have a GPIO controller service type added, but for now it's keep it simple. This is in project bundles/org.eclipse.ecf.raspberrypi.gpio.
2) A pi4j-based implementation of this GPIO Pin service, in project bundles/org.eclipse.ecf.raspberrypi.gpio.pi4j. When started, this bundle creates 20 IGPIOPin instances using pi4j PinImpl underneath, and registers these 20 instances with the OSGi service registry.
3) A very very simple test bundle, in project test/bundles/org.eclipse.ecf.raspberrypi.test.gpio. All this bundle does (for now) is create a ServiceTracker and report to System.out any IGPIOPin instances registered, but I'll probably hook up a light or something to one of the GPIO pins and try out the pin.toggle() to make sure pi4j works as expected.
After I do some basic testing on an actual raspberry pi I intend to use remote services to export the IGPIOPin services and run some basic test code...probably using Eclipse as a remote service consumer.
Any comments appreciated.
On 7/10/2014 2:25 PM, Scott Lewis wrote: