Not logged in
Thu Jan 24 20:03:40 2008, Andrey, Configuration, SUS, Changes to Dataviewer channels (XARM)
Fri Jan 25 08:55:26 2008, rob, Configuration, General, Changes to Dataviewer channels (XARM)
Fri Jan 25 10:14:35 2008, rob, Configuration, SUS, Changes to Dataviewer channels (XARM)
Fri Jan 25 10:14:35 2008
In reply to:
Changes to Dataviewer channels (XARM)
While "clicking the appropriate blue button" on the DAQ MEDM screen,
CODAQ_DETAIL,adl screen, I obviously clicked some blue button that I should not have clicked,
and as a result the signal in Dataviewer from the channel "C1:SUS-ITMX_POS" has disappeared (it is now a straight line).
Description of what has happened and of my wrong actions:
I had two channels opened in Dataviewer simultaneously (both "C1:SUS-ETMX_POS" and "C1:SUS-ITMX_POS"),
and after clicking some blue button on CODAQ_DETAIL,adl screen,
the signal from "C1:SUS-ITMX_POS" became
a straight line,
while signal from "C1:SUS_ETMX_POS" continued to be a random noise.
I was scared that I made worse for the channels and for Dataviewer, and
I started clicking random blue buttons chaotically
hoping that it will restore the signal from "C1:SUS-ITMX_POS". Random clicking on arbitrary blue buttons did not return the signal.
As the channel "C1:SUS-ETMX_POS" works normally, I will be measuring Q-factors of ETMX tonight,
but it is obvious that
someone else (Rana, Robert,Steve?) needs to restore the correct settings for "C1:SUS-ITMX_POS"
Moreover, as I was clicking chaotically all the blue buttons on CODAQ_DETAIL,adl screen,
someone else (Rana, Robert, Steve?) will need to check somehow that I did not destroy signals from some other channels.
I apologize for the negative consequences of my channel adding,
but Rana asked me in the very beginning in September to let others know if I spoil something, so that others would be aware of it and could fix the problem.
I eventually resolved the situation by restarting the
processor, which had somehow got confused by the
clicking random blue buttons chaotically
. The data acquisition should be working again.