It's been a while since i've looked into pi/etc, but from memory there were arduino shields that you could add onto it, giving you the best of the power of pi, with the better I/O support of arduino. Not sure how easy it is to get going/cost/etc, but might fit your solution?
Alternately, I would probably look at the possibility of running an actor on the closest 'powerful' node to your arduino, and then use a streamlined process to communicate with it/watch it directly (a bit more complex, but you would be able to stick to native arduino/etc) /2c - Glenn / devalias On Thursday, 14 August 2014 12:15:46 UTC+10, Josh Powers wrote: > > Thanks all for the replies, I didn't see them until just now. I assumed I > would get notified by groups when one came. > > At any rate, I am still quite interested in this as a possibility, for my > purposes an arduino or propeller (paralax) solution would be much more > inline with my goals, rather than a pi, mostly because the pi doesnt have a > ton of io, where the application I am considering would need that. Also I > am not intending to have the actors on the devices be standalone, they > would need to communicate to a proper set of jvm based akka actors. > > I will look into other options but also I will likely look into the pi and > see if I can make it fit my needs, it is nice that it can just run the jvm. > On the topic of the pi what options would I have for communication, > specifically would it be able to communicate over serial, or even better > could I feed it my own class for communication? (likely going to be using > xbee radios in api mode / doing zigbee mesh, really akka is ideal for this > sort of situation just need to figure out how to get it working in my world > :).) > > Thanks again. > Josh > > On Monday, August 4, 2014 3:10:23 AM UTC-7, Konrad Malawski wrote: >> >> Hi Josh, >> We didn't yet publish/document our actor / cluster protocols very >> explicitly. >> We'd like to do this at some point, so perhaps other impls could talk to >> an akka cluster – no plans on when this might happen though. >> This plays into an interesting story about exposing actors as services – >> we're not there yet though. >> >> As for arduino's... I guess using plain C there would be a better option >> there? >> There is an Akka inspired C implementation "libcppa" around, but that's >> for in-memory AFAIR. >> If you'd go down the road of making them a cluster you'll have to >> implemen cluster memberships etc. (depends on use case again, but if >> they're "in the field" that's probably not a good idea if they're on GPRS >> etc). >> >> I'm not sure about your use-case, but perhaps using Raspberry Pi's would >> fit this better? >> They're able to run a JVM nicely and you could use Akka on them directly. >> >> >> -- >> Cheers, >> Konrad 'ktoso' Malawski >> hAkker @ Typesafe >> >> <http://typesafe.com> >> > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
