I have several Raspberry Pi's in service / planned to be in service:

• Two (sometimes three) running on this aircraft:
  • One with a GPS receiver, it provides a WiFi AP for the onboard Ethernet, a DHCP server, and an NTP server that is tightly synchronized to GPS time. I also put together a duplicate of this system for this aircraft.
  • One that runs the dataloggers I wrote in Perl (available here) to log data from multiple sources, the measurement system is a five hole probe combined with an INS and meteorological sensors with the goal of doing Eddy covariance measurements, including methane and CO2 using a separate system. (In fact, this was the system that inspired WebPerl - even if priorities shifted and I didn't get to rewrite the web interface in Perl (-: )
  • We have a third system, not built by me, that we can optionally install and that uses an RPi to control and read out both a multispectral camera and a thermal camera and store the images.
• I'm working on an RPi that will connect to a datalogger on one of our weather stations in order for us to transmit its data to our servers over a nearby WiFi network.
• I'm designing a data logger for an in situ CO2 probe that will most likely be running a WiFi AP and hosting a web interface to configure the logger, and view and download the logger data. And I hope to get a chance to use your RPi:: libraries here!
• Plus of course the various RPi's I have sitting in my lab and at home (RetroPie is great).

... and of course I use Perl on all of them, more or less heavily :-)

Speaking in general, one of the many things I like about Perl is its how tightly it is integrated with *NIX OSes - just look at how many Perl functions mirror the underlying APIs. And one of the things I like about RPi's is that they are basically embedded systems, with many similarities to systems with much smaller microcontrollers, but they in fact are full-fledged Linux systems (the only real caveat being the higher power consumption). In a time where many things are getting abstraction layers (cloud services, JavaScript on the server, REST APIs for everything...), I think the *NIX philosophy is still alive and well in the RPi world. And so IMHO this is a great place for Perl to shine :-)

Since Raspberry Pi's are aimed at teaching about embedded systems, I think the learning aspect is important. Look at it this way: if we didn't have these libraries for newcomers to simply reach for, then what reason would they have to seriously consider Perl <update> for their hardware interfacing needs? </update> So I think it's great you've made all those modules available! :-)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.