Boards

DOL Board

There are two types of DOL. While the transmission part is the same, the reception has two types of FIFO memory size (16384word or 512word). The reception size is crucial only for DOL involved in the DAQ (see DOL key in Fbf configuration files, where is mentioned the FIFO half size). The reception size is not critical for the DOL involved in the loops (Pr, Gc, Susp DOLs).

In case of replacement :

•  Check the serial number before replacing them (see hardware inventory DB or in /virgoDev/Hl/HlDol/HlDol file)
  

• Restore the same jumpers position (level and acknowledge switches). Check that the switch number sum is equal to 7.
  

TIM Board

Many jumpers and dip switches to set base address.

In case of replacement :

• Restore the jumpers and the dip switches position.

ADC298 16 channels Board

In case of replacement:

• Check the correspondance between board number and board VME address:

VME address = A0100000 for board 1
VME address = A0200000 for board 2
...
VME address = A0F00000 for board 15
VME address = B0000000 for board 16
VME address = B0300000 for board 19

....

VME address = B0C00000 for board 28

etc...

In case that a ADC298 board is not working correctly check:

• That the timing signals are connected correctly and that the timing board is set up correctly
• That the board is not installed on the VSB bus plug
• That the jumpers are set correctly
• That the respective configuration file is correct (serial number, address, etc.)

RIO Board

In case of replacement :

if the RIO can be connected to the console, retrieve all the parameters of the PPCMonitor (BIOS) with the following commands:

#show boot
#show inet
#show vme

RIO VSB mezzanine

In certain situations (Gc) RIOS have a VSB mezzanine mounted. Replacement of such a RIO requires umounting the VSB mezzanine of the defectuous RIO and mounting on the same PMC slot of the new RIO.

RIO Jumper Settings

In order to configure a CPU board for rioXXA or rioXXB the jumpers (DIPs) have to be set accordingly. They can be found on the middle lower part of the CPU board's frontside (the one with the cooling elements) (there are 2 or 3 DIPs with 4 switches each), as shown in the following schema:

..left: port plugs..
..right: VME connectors..

  DIP1  DIP2  DIP3
  1234  1234  1234

Note: The ON position is the one towards the board center, the OFF position towards the border.

Dip 3 switch description :

1 : enable SYSRESET transmission
2 : enable SYSRESET reception
3 : enable SLOT1 (only for the first left VME board)     
4 :

rioXXA
DIP1:
DIP2:

 1      2      3      4
OFF    OFF    OFF    OFF 

DIP3:

 1      2      3      4 
ON     OFF    ON     OFF 

rioXXB, rioXXC

DIP1:
DIP2:

 1      2      3      4
OFF    OFF    OFF    OFF 

DIP3:

 1      2      3      4
OFF    ON     OFF    OFF 

To correctly set the Master/Slave relationship also the priority via the PPC boot parameter setting:
PPCMON> set vme

.........

vme_req_level must be set to 2 for the rioXXB and then to 1 for the rioXXC

On the rioXXA it must be checked that this parameter is at its default value 3

After mounting the new RIO, plug the console, reset the RIO and restore the parameter of the PPCMonitor (see RIO BIOS Configuration).

If the boot fails :

• Check the parameters of the boot.
• Check the the boot service (inet_server) is available by using :
  

   ping 193.205.72.245 

if the ping fails, call the computing service on-call.

if the boot starts but is not completed, do at least 3 or 4 trials by resetting the RIO. After call the computing service on-call.

if the boot completes, try to login using the virgorun account from the console. If login fails, check the NFS mounting field on the inet parameters. It should look like :

inet_mount : lynxos.virgo.infn.it:/opt/LynxOS/rioRoot

When login as virgorun succeeds, check that you are in /olusers/virgorun directory, and that you can reach /virgoDev, /virgoData, /virgoLog and /virgoApp directories.If one access fails, retry 3 or 4 times by resetting the RIO. After call the computing service on-call.

Camera Board & Jumper Settings

In case of replacing a Camera Board all jumpers and switches have to be checked and put at the same position than at the original board. Only the front face DIP switches (which contain the board setup) must not be adjusted. Finally, at the GxS configuration file (/virgoData/GxS/GxSnnXX.cfg) the number of the board has to be changed accordingly at the following line:

CAMERA cam <board_number> 350 0.0

Diagnostic Tools

DOL

You can test a DOL communication link with the following setup:
Be careful to perform these tests without anything else running on the crate (active test).
To see the status of a DOL type:

#rioxxA#/virgoApp/Do/<version>/DoStatus.exe -n <DOL number>

To change the status of a DOL type:

#rioyyA#/virgoApp/Do/<version>/DoCommand.exe -n <DOL number>

The receiver board should : - Enable Remote Commands (RmC flag).
Send a "Start Packet" from the sender side using DoCommand.exe (the State Machine SM flag of the receiver should go to "Yes"). Now you can send data to test the link.
To send data you can use the following command from the sender side:

rioxxA#/virgoApp/Do/<version>/RIO806X/DoSendData.exe <sender addr>

You can check the reception of data with:

rioxxA#/virgoApp/Do/<version>/RIO806X/DoRecvData.exe <receiver addr>

You can also test the data reception using the following command on the receiver side:

rioxxA#/virgoApp/Do/<version>/RIO806X/DoSpy.exe /virgoData/Fbf/FbfXXXX.cfg

This shows the current status of the DOL using the Fbf configuration (having the DOL keyword with corresponding DOL address set). This tool does not affect the normal operation contrary to the other ones (i.e. it is passive).

DOL Quality Check

In order to test the HW of a DOL, e.g. when receiving it back from reparation, you can use the tool "/virgoApp/Do/<version>/RIO806X/DoTest.exe". This tools provides the following tests:

1 - Bus selection test
2 - Status and Interrupt Test
3 - Data Transfer Test
4 - Flow Control Mode Test
5 - Automatic Test

Any test should be performed with both a short and a 3-km long fiber (i.e. less power).

Notes:
Currently there seems to be a bug in the Status and Interrupt Test, that produces the following failure:
Check Rx Byte(s) count................................FAIL

RIO

At boot time (interrupt from console) use:

#diag

VME

#VxVmeProbe <address> 9 4 <10>
#VxVmeReadProbe e8ee2100 9 4 <10>
#VxMonitor
#vmeconfig -d
#vmeconfig -m

TIM

#VxItFunctionLink.exe

Note: at Ti/tests/ you can find several more test applications.