[Erik v.R., Dave, Jonathan]

h1omc0 was upgraded to support alternative duotone frequencies.

A new parameter was added to the iop model, h1iopomc0, 'duotone_frequency', currently set to '960', which configures the duotone frequency to 960/961 Hz, the standard frequencies.

The h1omc0 front end was moved from a the primary bootserver, h1vmboot1, to the secondary bootserver, h1vmboot0 using changes to the puppet configuration.

All models for h1omc0 were built and installed from RCG source rather than packages.  The git commit of the RCG source is tagged as 'h1_2024_12_10_variable_duotone'.

The omc0 front end and io chassis were shut down.  The timing card SN S2101117 was replaced with SN S2101084, which had newer firmware version 1589 that supports alternative duotone frequencies.

The IO chassis and front-end were restarted.

A few problems were encountered:

Running puppet on the secondary bootserver overwrote the DAQ master template and some EDC INI files.   The master file problem was revealed in the DAQ overview where most of the front ends were reporting no channels.  The EDC overwrite showed up as too few total EDC channels.

Running the puppet configuration on the production server re-enabled DHCP for hosts that were supposed to boot from the secondary bootserver.  These had to be manually commented out from the DHCPD configuration, then the service restarted.

To change the duotone to 1920 Hz, edit the h1ipomc0 model, set 'duotone_frequency=1920' in the parameter block, save the model.  Build and install the model then restart all models.