Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

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

by stevieb (Abbot)
on Aug 18, 2017 at 23:04 UTC ( #1197631=note: print w/replies, xml ) Need Help??


in reply to Re: How RPi::WiringPi suite is automagically unit tested
in thread How RPi::WiringPi suite is automagically unit tested

zentara, et-al;

Here's a pic of the hardware layout that I test against. Please forgive the low quality image.

I was ready to have PCBs printed, but had to back out at the last minute, so currently, the test platform is still breadboarded, *usually* enclosed in a water/dust-tight container until I can get the custom boards developed.

As far as the LCD, top-row: date, time, previous unit test run status. Bottom row, run count and the git commit checksum of the last run performed. I've been toying with the layout, but this is adequate for now as this unit *only* tests a single software distribution. I have plans and provisions to use a 20 column by 4 row LCD (as soon as I acquire one), so that I can have distribution name along with other information for situations where I may want other Pis testing other distributions for me.

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

Replies are listed 'Best First'.
Re^3: How RPi::WiringPi suite is automagically unit tested
by zentara (Archbishop) on Aug 19, 2017 at 19:17 UTC
    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

      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.

        Interesting set of modules for the Pi. I don't see any examples in the FAQ for the camera though.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1197631]
help
Chatterbox?
and the fog begins to lift...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2017-11-20 01:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    In order to be able to say "I know Perl", you must have:













    Results (282 votes). Check out past polls.

    Notices?