Re^3: How RPi::WiringPi suite is automagically unit tested

Hi again stevieb, might I ask a few questions?

How many different types of sensors have you got working for the Pi? Is there a list by application type?

And even though it's not needed, why do you do I2C bus testing with the Arduino?

I'm not really a human, but I play one on earth. ..... an animated JAPH

Comment on Re^3: How RPi::WiringPi suite is automagically unit tested

Replies are listed 'Best First'.
Re^4: How RPi::WiringPi suite is automagically unit tested by stevieb (Canon) on Aug 20, 2017 at 12:45 UTC
I do not have a list currently, but I will put one together. Some of the sensors require specific timing and such, so I've already written specific modules for to make it much easier for the end user (eg: RPi::DHT11, RPi::HCSR04, RPi::WiringPi's `servo()` etc). Many other sensors require nothing more than toggling a GPIO to read/write, such as hall effect sensors, PIR motion sensors etc. As far as the Arduino, it kind of is needed. It allows me to test all of the functionality of RPi::I2C... read/write, read/write to specific addresses, and most importantly, read/write block data. Because I can code the Arduino in any way I like, I can add/change the way the pseudo-hardware operates, and therefore enhance the tests in the future.	[reply] [d/l]
Re^5: How RPi::WiringPi suite is automagically unit tested by Ravenhall (Beadle) on Aug 23, 2017 at 18:13 UTC
Interesting set of modules for the Pi. I don't see any examples in the FAQ for the camera though.	[reply]
Re^6: How RPi::WiringPi suite is automagically unit tested by stevieb (Canon) on Aug 24, 2017 at 11:27 UTC
I haven't written any Perl code that performs camera operations. I started down that path, but life happened and had to temporarily abandon the project. I do have a couple of Pi camera 2 modules, but the brief time I've played with them, I just used the pre-installed camera CLI commands.	[reply]