[daip] MCANT message
Eric Greisen
egreisen at cv3.cv.nrao.edu
Thu Dec 6 12:18:32 EST 2001
Data Analysts writes:
>
> What does this mean?
>
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:23:40.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:23:50.0
> FILLM1: Found 18166-18587 : 0 50.000 MHz at IAT 1/ 01:23:53.3
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:24:00.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 4 at 0/01:24:10.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 4 at 0/01:24:20.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:24:50.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 4 at 0/01:24:50.0
> FILLM1: Found 18210-25282 : 0 50.000 MHz at IAT 1/ 01:24:53.3
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:24:50.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:25:00.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 4 at 0/01:25:10.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 4 at 0/01:25:10.0
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 3 at 0/01:25:30.0
> FILLM1: Found 18166-18587 : 0 50.000 MHz at IAT 1/ 01:25:53.3
> FILLM1: MCANT: Bad nom. sens. for ant 7 IF 1 at 0/01:25:50.0
>
You would have to ask Ken Sowinski about this. A few such messages
seem to be normal and imply that the IF was essentially off for a
while.
Eric
More information about the Daip
mailing list