Dave mentions in his summary below, HAM1 HPI model was restarted this morning so I could add some temporary DQ channels to the frames for the ground to HPI feedforward I'm working on at that chamber. These channels are meant to be temporary until we decide if the FF is going to be permanent or not, but having in the frames right now will make commissioning the ff easier. These channels are: 

 0$ check_model_daq_configuration h1hpiham1
--------------------- file times ----------------------
Mon Aug 14 13:52:54 2023 = Model build time

Tue Aug  8 11:32:55 2023 = Current configuration load time

DAQ configuration is changed, processing...

++: fast channel H1:HPI-HAM1_3DL4CINF_A_X_IN1_DQ added to the DAQ
++: fast channel H1:HPI-HAM1_3DL4CINF_A_Z_IN1_DQ added to the DAQ
++: fast channel H1:HPI-HAM1_3DL4CINF_B_X_IN1_DQ added to the DAQ
++: fast channel H1:HPI-HAM1_3DL4CINF_B_Z_IN1_DQ added to the DAQ
++: fast channel H1:HPI-HAM1_3DL4C_FF_X_IN1_DQ added to the DAQ
++: fast channel H1:HPI-HAM1_3DL4C_FF_Y_IN1_DQ added to the DAQ
++: fast channel H1:HPI-HAM1_3DL4C_FF_Z_IN1_DQ added to the DAQ
Total number of DAQ changes = 7
(7 additions, 0 deletions)

The A_X, A_Z, B_X and B_Z channels are the uncalibrated individual adc channels that I connected to the 3dl4c ff path. A_X and B_X don't currently have any sensors attached, but I hope to do something about that soon. The FF_X, FF_Y and FF_Z channels are the calibrated cartesian basis channels that get filtered and summed into the cart drives drives. FF_Z is the only channel that has any real data on it at the moment. No real changes to the model to do this, but I did have to make a custom library part to add the channels to the table. Added channels are in the screen shot.