J. Kissel, O. Patane, D. Barker

Oli and I have moved on to recovering the SUS RM1, RM2, and PM1 post their migration from the h1sush2b computer / h1sushtts front-end model into the newly merged h1sush12 computer / IO chassis system and h1susham1 front-end model yesterday (see LHO aLOGs 88519 and 88527). We immediately noticed that all the raw OSEM ADC inputs were digital 0. We opened up the ADC MONITOR screen and found this auto-generated screen completely blank. Popped open the IOP for the whole computer to check it's report of these ADC cards, and they appeared normal. See attached MEDM screen collection.

Dave and I opened up the new h1susham1 front-end model and found that the bus selectors that were parsing the ADC2_2_HTTS and ADC3_2_HTTS goto tags were configured to read the Direct I/O Chassis ADC blocks' internal bus creator / output name rather than the card number. It's easier shown than described -- check out the before (r34117) vs. after (r34217) top level model.

I fixed this as one usually does -- 
    - double clicking on the bus selector, 
    - highlighting the channels from the "Signals on the bus" list that you want (which say, e.g. "adc_0_16, adc_0_17, adc_0_18, adc_0_19" instead of "adc_2_16, adc_2_17, adc_2_18, adc_2_19"), 
    - hitting "Select >>," to bring them over to the "Selected Signals," then 
    - deleting any "Selected Signals" which have question marks in front of them (i.e. "??adc_2_16").

This needed doing for all ADC2 and ADC3 bus selectors fed into the RM1, RM2, PM1, JM1, and JM3 library blocks, with channels selected so they match the along AA chassis input for those cards from D0902810-v12.

The new top level model has been committed to userapps svn rev r34217.