Personal tools
You are here: Home EGO ITF Software Support&Maintenance IMAC_LL (Nitel)
Navigation
Log in


Forgot your username or password?
 
Document Actions

IMAC_LL (Nitel)

by Martin Mohan last modified 2010-01-25 10:26

This page provides troubleshooting information should the display of IMAC data fail.

IMAC_LL (Nitel)

IMAC_LL stands for Infrastructure Monitoring Air Conditioning Laser Lab. It was added on 31/07/2007 and the values can be seen at.
http://wwwcascina.virgo.infn.it/commissioning/detectoroperation/index.htm -> Detector Monitoring -> Infrastrucures -> ACS_LL
The IMAC_LL information is obtained from controller running a legacy data acquistion program in the laser lab called nitel. The legacy program is a black box which does not support networking and was controlled by the operator sending commands to a serial port using a key board and writing down the return values. We connected to the serial interface using a serial/ethernet bridge (ip address 193.205.75.193). Data is obtained by the nitelServer simulating operator input.
At startup the nitelServer will automatically be setup to actively collect data.
After a power outage nitel data may not appear this may be either because the program has not been restarted or it has been restarted and is expecting a password.
1. Check the  computer in the laser lab is switched on and the nitel program on the PC is running. (the nitelServer gets its data from the nitel program).
2. After shutdown it may occur that you are prompted for a password by computer in laser lab. You can set password directly on machine or via telnet.
telnet  193.205.75.193 2001

To restart nitelServer...
1. Be sure you have exited telnet ( Only one application can access nitel program at 1 time. If you are still connected with telnet the nitelServer will not work).
2. If you suspect NetComm Serial Device is not working go to http://193.205.75.193/index.asp and select reboot.
traceroute from ctrl1 should be something like..
ctrl1[~]: traceroute 193.205.75.193
traceroute to 193.205.75.193 (193.205.75.193), 30 hops max, 38 byte packets
 1  193.205.72.1 (193.205.72.1)  1.586 ms  3.283 ms  7.139 ms
 2  fw1d (193.205.73.1)  8.051 ms  9.036 ms  12.804 ms
 3  * * *
 4  *
If you suspect a network problem. Connect serial Device to net somewhere else (e.g. in user room) and try ping/traceroute/telnet.

3. Restart nitelServer from ISYS Supervisor.
To check process maually.
3.1. Find machine -> "cmdomain Cascina;cm connects | grep nitel;-> ctrl100";
3.2. Find process  -> ssh ctrl100; "ps -ef  | grep nitel";

If nothing else works please contact person who last modified the software. scvsHistory nitel
If no-one is available some other hints are below.

IMAC_LL (Nitel) on-call hints when Detector Monitoring System is Grey

The first indication of a problem with the monitoring software may be a grey area in the “Detector Monitoring System" (Grey – No data is coming into monitor, Dark Grey – Corrupted data is coming into system).  If the data does not change this may also indicate an error.

  • You can also check if server is collecting data correctly using cm send command below. ( or check data on screen is green).
    # cmdomain Cascina
    # cm send -to nitelServer -type FbGetAllSmsData -t All -i -1 -t -1 -handler FbSmsData
    Message type FbSmsData received from nitelServer
    -int 0
    -text nitelServer_State 0 IMAC_LL_T_MAND 13.9 IMAC_LL_UR_RIPRES 54.0 IMAC_LL_VF 38.9 IMAC_LL_TA_1002 22.3 IMAC_LL_VP_BP01 52.5 IMAC_LL_FL_VM 0 IMAC_LL_FL_VR 0 IMAC_LL_AL_FIL 0 IMAC_LL_TA_1001 19.6 IMAC_LL_VP_BP04A 11.2 IMAC_LL_AL_VM 0
  • Check for LogSevere errors in the nitel log located at /virgoLog/ISYS/nitel.
  • If restarting does not work check whether telnet access is working and 11 values are being read (nitelServer must be stopped before using telnet). The nitel does not always initialise to the correct page and returns a general failure error. This is a bug which should be addressed in spr 1224.
#: telnet 193.205.75.193 2001
Trying 193.205.75.193...
n#. Punto Testo Sapim Valore Stato Commento

Stato : AUT automatico MAN manuale TAC/NTA Tacitato/Non tacitato
* modificabile - non valido STR/NST strutturato/Non strutt.

1. 2 RSUAI 1 T_MAND. 14.3 C AUT
2. 2 RSUAI 3 UR_RIPRESA 61.9 %rH AUT
3. 2 RSUAO 1 VF 58.9 % * AUT
4. 3 RSUAI 9 TA_1002 22.4 C AUT
5. 3 RSUAO 1 VP_BP01 50.0 % * AUT
6. 2 RSCOS 11 FL_VM 0 TAC NO FLUSSO VE.MAND. 401
7. 2 RSCOS 14 FL_VR 0 TAC NO FLUSSO VE.RIP. AHU 401
8. 2 RSCOS 21 AL_FIL 0 TAC ALLARME FILTRO AHU 401
9. 3 RSUAI 12 TA_1001 19.9 C AUT
10. 3 RSUAO 4 VP_BP04A 0.0 % * AUT
11. 1 RSCOS 11 AL_VM 0 - NON-STATO VE.MAND. 402



---------- 26.07.2007 14:43
Solo visualizzazione Immis. errata

Check that nitelServer is not lost on the FbsMoni from the daq Collect Cl Client, in this case issue the ReloadConfig command (or ask DAQ on-call).