Yet some more code about this... the /g operation generates a list, below I assign all regex matches to a list called @types. 
use warnings;
use strict;

my $_sensor_type =  'I2600*&^_A8699()^%#@C9800&*%A96';

my @types = $_sensor_type =~ /[a-z]+([0-9]+)/ig;

#parens aren't needed here but to make list clear,
#could have been:
#my @types = ($_sensor_type =~ /[a-z]+([0-9]+)/ig);

print join("\n",@types),"\n";
__END__
## prints ###
2600
8699
9800
96

[download]
Another question that comes up all the time is about this $1 stuff and what a pain it is. So how to you avoid having to use $1? Use a list slice to assign $1 to a scalar without having to go via $1! 
my $_sensor_type =  'I2600*&^_A8699()^%#@C9800&*%A96';
my $type = ($_sensor_type =~ /[a-z]+([0-9]+)/i)[0];
print "$type\n"; #prints 2600

#so what happens if the match and consequent slice fails?
$type ||= "some default";
#or check for undef

[download]
There are lots of cases where this trick is handy. Some types of split scenarios can produce undef values and this special Perl operator ||= can override that to a value, like even "".

In reply to Re^5: Repeated Pattern Matching Fails by Marshall
in thread Repeated Pattern Matching Fails by perlpal

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.