Update: we were able to fix the issue! On the panel side, the following two errors in setup/programming were present:
1 - in the tuxedo touch panel settings, the tuxedo touch panel was set as the “primary RIS device”.
We unchecked that. (The other relevant settings were ECP address = 1 (which specifies the virtual keypad address used by the tuxedo touch panel), RIS address = 25).
2 - in the panel, the 189 field was set at 1,1,5,5. And there were also a number of physical keypad addresses activated in fields 190-196.
We decided to use ECP address 2 for the 4232CBM, so we changed the 189 field to 1,5,1,1 (I only have 1 partition, the 5 in this setting in the 2nd position enabling RIS for ECP address 2 for partition 1). We also disabled all of the physical keypad addresses in fields 190-196, as I don’t have any physical keypads, and just to be extra clean about the setup. Not sure if we needed to disable fields 190-196, or if ECP addresses 5 and 6 (fields 3 and 4 in setup field 189) needed to remain enabled (with 1 in each of those fields) but these are the settings I have seen online so we went with it.
After the above we just needed to specify ECP address 2 on the control4 4232CBM driver side, and power cycle the 4232CBM and/or reconnect in the driver for the 4232cbm to “grab” the new programming from the driver. After that, we were up and running!
Thanks to everyone for your help and suggestions.