There were some issues with the new code, so we reverted h1ascimc back to its original code at 13:40. We will try again next week.
When h1ascimc was restarted by itself, h1iopasc0 ran long and reported a DAC error, though on the 16bit-DAC MEDM there were no associated FIFO errors reported.
When h1ascimc was started as part of a complete model restart (rtcds start --all) this DAC error does not appear.
The DAC error is clearable by DIAG-RESET'ing the IOP, but we are unsure if the DAC is a cycle behind at this point. At the moment the safest restart if DAC errors appear is a full restart of all models.
There were some issues with the new code, so we reverted h1ascimc back to its original code at 13:40. We will try again next week.
When h1ascimc was restarted by itself, h1iopasc0 ran long and reported a DAC error, though on the 16bit-DAC MEDM there were no associated FIFO errors reported.
When h1ascimc was started as part of a complete model restart (rtcds start --all) this DAC error does not appear.
The DAC error is clearable by DIAG-RESET'ing the IOP, but we are unsure if the DAC is a cycle behind at this point. At the moment the safest restart if DAC errors appear is a full restart of all models.