You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Greg A. (JIRA)" <ji...@apache.org> on 2015/07/23 16:00:10 UTC
[jira] [Closed] (CAMEL-8567) New camel-raspberry component
[ https://issues.apache.org/jira/browse/CAMEL-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg A. closed CAMEL-8567.
--------------------------
Estimated Complexity: (was: Moderate)
> New camel-raspberry component
> -----------------------------
>
> Key: CAMEL-8567
> URL: https://issues.apache.org/jira/browse/CAMEL-8567
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.16.0
> Environment: Linux and Raspberry Pi Raspbian
> Reporter: Greg A.
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: GPIO, I/O, RasberryPi, component, features
> Fix For: 2.16.0
>
> Attachments: camel-raspberry.patch
>
>
> I've started a new component to interface with an RaspberryPI.
> I think it could be very interesting component to have for camel.
> With this first version you manage all GPIO for Model A, A+, B, B+, 2B
> Features
> - input / ouput digital pin management
> * with TOGGLE, LOW, HIGH action
> * from("rbpi://pin?id=2&mode=input&state=HIGH") --> send new msg when HIGH
> * to("rbpi://pin?id=9&mode=output&state=LOW&action=HIGH") --> when receive msg set to HIGH
> - input / ouput analog pin management
> * for double value
> * rbpi://pin?id=1&mode=analog_input
> - input / ouput pwn pin
> * for int value
> * rbpi://pin?id=1&mode=pwm_input
> I also developed an CamelMain stuff to test it very quickly on a Raspberry Pi.
> One input -> log -> one output, stay tuned !!!
> I've also create a mock to emulate RBPI on my Mac
> Pi4j uses ASF : http://pi4j.com/license.html
> Pi4j is OSGi compliant
> but I don't know if component is correctly OSGi compliant
> I am writing an documentation too.
> TODO :
> - smarter URI style like rbpi://pin/1/mode?[options]
> - output endpoint with dynamic PIN
> - GUI GPIO emulator
> - i2c integration
> - spi integration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)