The QUAD_MASTER.mdl file located in the (local) SVN checkout under '~/opt/rtcds/lho/h2/userapps/trunk/sus/common/models/' was modified to include more channels from the user model to be stored to frame files.  There were several issues with compiling and installing the new individual models for 'h2susitmy' and 'h2susetmy' on the common frontEnd machine, 'h2susb6'.  The channel list changes were made in the QUAD_MASTER part, which is shared by all quad optics in their individual models.  

Channel List issues:
1.) The new channel list contained quotes ("") in its comments, which is used by simulink to parse the model's .mdl file to text.  The quotes ("") within the comments of the channel list prevented the correct parsing of the channel list.  The quotes and comments were removed completely from QUAD_MASTER to compile. NOTE: the quotes were in lines that were supposedly commented out by simulink, however simulink apparently disregards commented when parsing to text.

2.) The initial file had a few channels requesting a 128 b/s rate to the framebuilder. The data rate minimum allowed by the RCG is 256 b/s, so the few channels initially at 128 are now at 256 b/s.

3.) The TMS model 'h2sustmsy' was last recompiled and installed under RCG 2.4, whereas the latest 'h2susetmy' model was compiled using RCG 2.5.  The IOP model running on 'h2susb6' was compiled under RCG 2.5 as well.  The error was in the IOP machine,'h2susb6', attempting to run two models ('h2susetmy' and 'h2sustmsy') that were compiled under different RCG versions.

The TMS model was compiled and installed on 'h2susb6' under RCG 2.5, and, after a DAQ reboot, all previous errors on 'h2susb6' were cleared.  Damping loops on both TMSY and ETMY M0/R0 were closed and confirmed functional by late afternoon.