Whew, third site in a row that I've had to point out the the script has remarks in it, and one of those remarks is that you need to do some manual mods to the script after looking at disassembly of part of the bin.

You need to run get_mtbl on a bin as first step--that program will give you a list of the bin's chunks as they are moved to RAM for execution. I have the program mark the start first chunk that has code in it--that chunk is the one you should disassemble (and you should use the RAM address that is in the move table as offset but you don't have to). That one chunk is where most of the bin mods are made, so I think it is always worth disassembly. Look for the "----code----" tag in the mtbl.txt file that get_mtbl generates--the code chunk to disassemble is the one that follows the tag.

But if you don't want to disassemble the whole code chunk, you don't have to--see in the script where is does FINDASC STPIO_open?--that finds the end of the PIO init code section. IF you disassemble the code in the PIO init section you will find a that a number of addresses are used to store bit masks and port bit control info. In the 218 bin they were:
PIO0, 0xcc76
PIO1, cc77
PIO2, cc78
PIO3--skipped
PIO4, cc7a
PIO5, cc7b

IN the 219 bin:
PIO0, 0xa8e9
PIO1, a8ea
PIO2, a8eb
PIO4, a8ed
PIO5, a8ee

Now, in the script you have function controls being switched between PIO0 and PIO2, so the remarks note that the search terms have -2 or +2 beteen them--that is because of the values used for the addresses of the bitmasks.

Also the diseqc sw control mod is modifying a PIO5 port bit use--so that RAM addr pointer is used as a seach term.

Does that help?