In browsing the HiPi::Device::I2C documentation I came across the scan_bus() function that loops through all of the possible I2C addresses and returns a list of active addresses.
This script scans the I2C bus and prints the found addresses. This would have been very useful in debugging the OLED scripts!
#! /usr/bin/perl
# hipiI2Cscanner.pl - Scan the I2C Bus for active devices
# using the HiPi Raspberry Pi Perl Library
# Documentation at https://raspberry.znix.com/
#
# James M. Lynes, Jr. - KE4MIQ
# Created: June 28, 2020
# Last Modified: 08/28/2020 - Initial test version
# 08/29/2020 - Change to printf to print address in Hex
use strict;
use warnings;
use HiPi qw( :i2c );
use HiPi::Device::I2C;
$SIG{INT} = \&trapcc; # Trap CTRL-C Signal
my $dev = HiPi::Device::I2C->new(); # Create I2C Object
my @attached = $dev->scan_bus(); # Scan I2C bus for
# attached devices
print "\nI2C Bus Scanner\n"; # List found devices
print "===============\n";
foreach my $addr(@attached) {
printf "Found address: %x\n", $addr;
}
print "Done...\n";
sub trapcc{
die "Terminated by CTRL-C Signal\n\n"; # Kill the script
}
James
There's never enough time to do it right, but always enough time to do it over...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|