40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Mon Oct 2 18:08:10 2017, gautam, Update, CDS, c1ioo DC errors c1ioo_CDS_errors.png
    Reply  Mon Oct 2 18:50:55 2017, jamie, Update, CDS, c1ioo DC errors 
       Reply  Mon Oct 2 19:03:49 2017, gautam, Update, CDS, [Solved] c1ioo DC errors CDSoverview.png
Message ID: 13350     Entry time: Mon Oct 2 18:50:55 2017     In reply to: 13349     Reply to this: 13351
Author: jamie 
Type: Update 
Category: CDS 
Subject: c1ioo DC errors 
Quote:

 

  • This time the model came back up but I saw a "0x2000" error in the GDS overview MEDM screen.
  • Since there are no DACs installed in the c1ioo expansion chassis, I thought perhaps the problem had to do with the fact that there was a "DAC_0" block in the c1x03 simulink diagram - so I deleted this block, recompiled c1x03, and for good measure, restarted all (three) models on c1ioo.
  • Now, however, I get the same 0x2000 error on both the c1x03 and c1als GDS overview MEDM screens (see Attachment #1).

From page 21 of T1100625, DAQ status "0x2000" means that the channel list is out of sync between the front end and the daqd.  This usually happens when you add channels to the model and don't restart the daqd processes, which sounds like it might be applicable here.

It looks like open-mx is loaded fine (via "rtcds lsmod"), even though the systemd unit is complaining.  I think this is because the open-mx service is old style and is not intended for module loading/unloading with the new style systemd stuff.

ELOG V3.1.3-