Difference: MuonDaqPitFaq (1 vs. 11)

Revision 112008-08-26 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

FAQs for commissioning of LHCb Muon System

Line: 8 to 8
 
Changed:
<
<

Software configuration

>
>

HowTos

 
Changed:
<
<

HowTos

>
>

Reach the network

 
Changed:
<
<

Starting From scratch

>
>
Use the netgw01 proxy.
 
Changed:
<
<
Experts: R. Nobrega, C. Deplano
>
>

Get the account

 
Changed:
<
<
  • Start PVSS project
  • From GEDI start the CreateStructure panel
  • Ask expert for assistance

Normal Start

  • Start PVSS project
  • Start OPC server: do it sequentially, before SB then ODE
    • Start OPC server -num 5 : serves the SB
    • Start OPC server -num 4 : serves the ODES
  • Go in the fwDeviceEditorNavigator panel
  • Switch to Navigator mode
  • Select the ODE/Hardware Unit you want to test

-- AlessioSarti - 15 May 2008

>
>
-- AlessioSarti - 26 Aug 2008
 
META FILEATTACHMENT attachment="PNPI_Istructions.ppt" attr="" comment="Instruction for HV PNPI system" date="1205744751" name="PNPI_Istructions.ppt" path="PNPI_Istructions.ppt" size="938496" stream="PNPI_Istructions.ppt" user="Main.AlessioSarti" version="1"

Revision 102008-05-15 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"
Changed:
<
<

Page that contains FAQs for DAQ testing in the pit

>
>

FAQs for commissioning of LHCb Muon System

 
Changed:
<
<

Useful links / informations / documentation

Online pages

Documentation

Computer names

Item/Stat/side PCName SystemNumber SystemName ProjectName
Feb 2&3/C MUDAQC03w 260 MUDAQC23 MUDAQC23
Feb 4&5/C MUDAQC04w 261 MUDAQC45 MUDAQC45
Feb 1/C MUDAQC01w 262 MUDAQC1 MUDAQC1
Feb 1/A MUDAQA01w 263 MUDAQA1 MUDAQA1
Feb 2&3/A MUDAQA03w 264 MUDAQA23 MUDAQA23
Feb 4&5/A MUDAQA04w 265 MUDAQA45 MUDAQA45
ODE/C MUODEC01w 266 MUDAQCO1 MUODECO1 (Q3)
ODE/C MUODEC02w 267 MUDAQCO2 MUODECO2 (Q4)
ODE/A MUODEA01w 268 MUDAQAO1 MUODEAO1
ODE/A MUODEA02w 269 MUDAQAO2 MUODEAO2(Q2)
T&P MUDCS01w 270 MUDCSSEN MUDCSSEN
FSM/C MUECSC01W 279 MUDAQC MUDAQC
FSM/A MUECSA01W 280 MUDAQA MUDAQA
LV/C MULVC01w 210 MUDCSLVC MUDCSLVC
LV/A MULVA01w 211 MUDCSLVA MUDCSLVA
HV/C MUHVC01w 212 MUHVC01 MUHVC01
HV/C MUHVC02w 213 MUHVC02 MUHVC02
HV/A MUHVA01w 214 MUHVA01 MUHVA01
HV/A MUHVA02w 215 MUHVA02 MUHVA02

The shortcuts that should be used can be found under g:\\online\ecs\shortcuts\MUON

FEB, DAQ Maps

The Maps can be found on the PC in the pit in a folder on the Desktop named: MAPS

Hardware Configuration

LV

For any problem please contact M. Lenzi

  • To control LV you should:
    • Log on into lbts.cern.ch PC (online interface to the rest of the world)
    • From lbts you make a remote desktop connection to computer UI01
    • On UI01 you should look into 'MyComputer' going trough G: -> online -> ecs -> muon -> Shortcuts
    • Then you click on the shortcut of the pvss project you need (LV side A or C, depending on what you want to do). Details on PVSS project can be found below.

PVSS project

Developer: M. Lenzi

>
>
This page contains the FAQs related to the commissioning of LHCb Muon System
 
Changed:
<
<
  • The PVSS project has its FSM and to control anything you need, first of all, to 'take' privileges....
  • Then you can navigate the panels trough the Quadrant and stations that you need to work on.
>
>

Muon Page and LHCb Twiki Page

 
Changed:
<
<
FAQs:
  • Q:
  • A:

Maraton Issues

Experts: M. Lenzi, p. Ciambrone For any hardware problem please contact the experts.

Sometimes the Maraton goes into a funny state: it shows errors that are unlikely to be real hardware failures. In those cases you should carefully check:

  • That the OPC server is running correctly and the RCM is talking communicating correctly
  • That the communication btw the RCM and the Maraton is correct

OPC server restart can be done only with administrator privileges (ask M. Lenzi)

To exit from real funny situation the following chain of actions has proved to help:

Turn off PVSS and OPC server
Reboot RCM crate
Restart PVSS and OPC server
Poer cycle the Maraton

After each step you need to check that the communication is going as expected. Latest maraton known problem: last november! Since then everything is running smoothly.

HV

PNPI system

Systec

For problems concerning systec operation, please contact R. Nobrega or C. DePlano.

>
>
 

Software configuration

Line: 123 to 30
 
  • Switch to Navigator mode
  • Select the ODE/Hardware Unit you want to test
Changed:
<
<

Available tests

Connectivity Test

Experts: R. Nobrega, C. Deplano

General remarks

Timing:

  • It's crucial, to avoid wasting test time that is already enormous, to FIX before running the full connectivity test, all the ECS connections problems that can be spotted easily in the very first part of the connectivity test:
Output
  • L:\\pvss\connectivity\path_to_your_favourite_Q

Running test

a) Go in the fwDeviceEditorNavigator panel
b) Switch to Navigator mode
c) Select the ODE/Hardware Unit you want to test
d) Right click on 'view'
e) Select : 'Connectivity test'
f) Make the first part of the test: configuration
g) Click on 'continue' that perform the connectivity test.
h) Save the results with Export.txt into the ReportRun directory.

Changing/updating mapping

  • Call the expert
  • Remeber that you need to update the OPC server configuration file [created with Create structure panel] with updated information, restart the PVSS and the OPC server to have your modification properly taken.

Timing test

Experts: C. Deplano, S.Cadeddu

Running test (full procedure)

  • I pallini bianchi diventano rossi se c'e' un problema I2C (la ode non sta funzionando)
  • fase 0
    • Calibrazione DLL e Invio impulsaggio
      • Andare sul DEN dei computer delle camere interessati. Serve aver fatto partire la gerarichia (se non sono dead).
      • Fare il view su CRC
      • Prima di qualsiasi test serve il FE DLL calibration (10 min)
      • 3392 Sotto sync pulses, poi selezioni BCdelay e poi PIGI su sync pulse. (1 min)
    • Veto trigger
      • L0ctrl dentro il campo L0_veto scrivere 09

  • Fase 1:
    • F time : configurazione.
      • F time (tempo fine)
      • Timing test
      • write CMB conf
    • Poi continue
    • salva il log in L:\\pvss\timing\Reports\ _FT (tramite export txt)
    • ricetta da salvare solo per le camere. Ricetta si salva in commands.
      • nella parte chambers si fa save conf !!! Attenzione a non sovrascrivere !!!!
      • L:\\pvss\timing\recipes e poi scegli dove andare a salvare
      • salvare il file con CMB_FT

  • Devo chiudere tutto tra la fase 1 e la 2
    • Se devo ripartire dal tempo fine (se per qualche motivo devo ripartire) Per ripartire dalla ricetta
      • Commands
      • Chambers: load conf. La prendo da L:\\pvss\timing\Reports\ _FT (fondamentalmente i ritardi)

  • Fase 2:
    • C time (tempo largo): configurazione!
      • Skip CMB conf
      • C time
      • ASD ok
    • Per finalizzare la parte ode (e far partire il test) devi mettere il DAQ mode start in commands. (diventa blu se e' ok)
    • Bisogna mandare un L0 reset.
      • Aprire una ODE. Dentro L0ctrl
      • Scrivere 00 in L0ctrl.
      • Scrivere 00 L0_strb
      • Vado nel sync e vedo che BXid counter sta contando con un readall
    • Poi Start e Continue.
    • salva il log in L:\\pvss\timing\Reports\ _CT (tramite export txt)
    • ricetta da salvare solo per le camere e ODE. Ricetta si salva in commands (chambers e ode).
      • nella parte chambers si fa save conf !!! Attenzione a non sovrascrivere !!!!
      • lL:\\pvss\timing\recipes e poi scegli
      • salvare il file con CMB_CT ODE_CT
    • salvare la ricetta vera delle ODE (vedi sotto, meglio dopo control)

  • Devo chiudere tutto tra la fase 2 e la 3 * Se devo ripartire dal tempo fine (se per qualche motivo devo ripartire) Per ripartire dalla ricetta
      • Commands
      • Chambers: load conf. La prendo da L:\\pvss\timing\Reports\ _FT (fondamentalmente i ritardi)

  • Fase 3:
    • Controllo: configurazione!
      • Skip CMB conf
      • C time
      • ASD ok
      • Only looking histo
    • Controllare il DAQ mode ed in caso ripartire il tutto
    • Salvare il log

  • Verifica finale
    • Show Rep (nel timing test) ti fa vedere i risultati... Da usare per far partire il debugging.
    • Il rosso segnala errore.

  • Debugging
    • Grep for wrong nel file di controllo
      • Ibimax
      • Oppure non vedo nulla nei 16 BX

  • Salvare la ricetta vera
    • Vai nella ODE
      • Attenzione che quando si salva la ricetta devo aver svetato L0 scrivendo 08 dentro l'L0 veto
      • Dentro recipes (fondo dx)
      • Stiamo salvando con Physics!

-- AlessioSarti - 19 Mar 2008

>
>
-- AlessioSarti - 15 May 2008
 
META FILEATTACHMENT attachment="PNPI_Istructions.ppt" attr="" comment="Instruction for HV PNPI system" date="1205744751" name="PNPI_Istructions.ppt" path="PNPI_Istructions.ppt" size="938496" stream="PNPI_Istructions.ppt" user="Main.AlessioSarti" version="1"

Revision 92008-04-04 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 36 to 36
 
HV/A MUHVA01w 214 MUHVA01 MUHVA01
HV/A MUHVA02w 215 MUHVA02 MUHVA02
Added:
>
>
The shortcuts that should be used can be found under g:\\online\ecs\shortcuts\MUON
 

FEB, DAQ Maps

The Maps can be found on the PC in the pit in a folder on the Desktop named: MAPS

Line: 126 to 129
  Experts: R. Nobrega, C. Deplano
Changed:
<
<

Speed and parallelism

>
>

General remarks

 
Changed:
<
<
Some remarks:
  • So far we proved that is possible to run parallel jobs on different SB that are connected to different systec cables . This means that when you access one crate you can run up to four jobs in parallel without degrading the time performance
>
>
Timing:
 
  • It's crucial, to avoid wasting test time that is already enormous, to FIX before running the full connectivity test, all the ECS connections problems that can be spotted easily in the very first part of the connectivity test:
Added:
>
>
Output
  • L:\\pvss\connectivity\path_to_your_favourite_Q
 

Running test

Revision 82008-03-19 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 160 to 160
 
  • I pallini bianchi diventano rossi se c'e' un problema I2C (la ode non sta funzionando)
  • fase 0
Changed:
<
<
    • Calibrazione DLL!
    • Invio impulsaggio
>
>
    • Calibrazione DLL e Invio impulsaggio
      • Andare sul DEN dei computer delle camere interessati. Serve aver fatto partire la gerarichia (se non sono dead).
      • Fare il view su CRC
      • Prima di qualsiasi test serve il FE DLL calibration (10 min)
      • 3392 Sotto sync pulses, poi selezioni BCdelay e poi PIGI su sync pulse. (1 min)
 
    • Veto trigger
Added:
>
>
      • L0ctrl dentro il campo L0_veto scrivere 09
 
  • Fase 1:
    • F time : configurazione.
      • F time (tempo fine)
Line: 197 to 202
 
      • nella parte chambers si fa save conf !!! Attenzione a non sovrascrivere !!!!
      • lL:\\pvss\timing\recipes e poi scegli
      • salvare il file con CMB_CT ODE_CT
Changed:
<
<
    • salvare la ricetta vera delle ODE
>
>
    • salvare la ricetta vera delle ODE (vedi sotto, meglio dopo control)
 
  • Devo chiudere tutto tra la fase 2 e la 3
Added:
>
>
* Se devo ripartire dal tempo fine (se per qualche motivo devo ripartire) Per ripartire dalla ricetta
      • Commands
      • Chambers: load conf. La prendo da L:\\pvss\timing\Reports\ _FT (fondamentalmente i ritardi)
 
  • Fase 3:
Added:
>
>
    • Controllo: configurazione!
      • Skip CMB conf
      • C time
      • ASD ok
      • Only looking histo
    • Controllare il DAQ mode ed in caso ripartire il tutto
    • Salvare il log

  • Verifica finale
    • Show Rep (nel timing test) ti fa vedere i risultati... Da usare per far partire il debugging.
    • Il rosso segnala errore.

  • Debugging
    • Grep for wrong nel file di controllo
      • Ibimax
      • Oppure non vedo nulla nei 16 BX

  • Salvare la ricetta vera
    • Vai nella ODE
      • Attenzione che quando si salva la ricetta devo aver svetato L0 scrivendo 08 dentro l'L0 veto
      • Dentro recipes (fondo dx)
      • Stiamo salvando con Physics!
 
Changed:
<
<
-- AlessioSarti - 23 Nov 2007
>
>
-- AlessioSarti - 19 Mar 2008
 
META FILEATTACHMENT attachment="PNPI_Istructions.ppt" attr="" comment="Instruction for HV PNPI system" date="1205744751" name="PNPI_Istructions.ppt" path="PNPI_Istructions.ppt" size="938496" stream="PNPI_Istructions.ppt" user="Main.AlessioSarti" version="1"

Revision 72008-03-19 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 152 to 152
 
  • Call the expert
  • Remeber that you need to update the OPC server configuration file [created with Create structure panel] with updated information, restart the PVSS and the OPC server to have your modification properly taken.
Added:
>
>

Timing test

Experts: C. Deplano, S.Cadeddu

Running test (full procedure)

  • I pallini bianchi diventano rossi se c'e' un problema I2C (la ode non sta funzionando)
  • fase 0
    • Calibrazione DLL!
    • Invio impulsaggio
    • Veto trigger
  • Fase 1:
    • F time : configurazione.
      • F time (tempo fine)
      • Timing test
      • write CMB conf
    • Poi continue
    • salva il log in L:\\pvss\timing\Reports\ _FT (tramite export txt)
    • ricetta da salvare solo per le camere. Ricetta si salva in commands.
      • nella parte chambers si fa save conf !!! Attenzione a non sovrascrivere !!!!
      • L:\\pvss\timing\recipes e poi scegli dove andare a salvare
      • salvare il file con CMB_FT

  • Devo chiudere tutto tra la fase 1 e la 2
    • Se devo ripartire dal tempo fine (se per qualche motivo devo ripartire) Per ripartire dalla ricetta
      • Commands
      • Chambers: load conf. La prendo da L:\\pvss\timing\Reports\ _FT (fondamentalmente i ritardi)

  • Fase 2:
    • C time (tempo largo): configurazione!
      • Skip CMB conf
      • C time
      • ASD ok
    • Per finalizzare la parte ode (e far partire il test) devi mettere il DAQ mode start in commands. (diventa blu se e' ok)
    • Bisogna mandare un L0 reset.
      • Aprire una ODE. Dentro L0ctrl
      • Scrivere 00 in L0ctrl.
      • Scrivere 00 L0_strb
      • Vado nel sync e vedo che BXid counter sta contando con un readall
    • Poi Start e Continue.
    • salva il log in L:\\pvss\timing\Reports\ _CT (tramite export txt)
    • ricetta da salvare solo per le camere e ODE. Ricetta si salva in commands (chambers e ode).
      • nella parte chambers si fa save conf !!! Attenzione a non sovrascrivere !!!!
      • lL:\\pvss\timing\recipes e poi scegli
      • salvare il file con CMB_CT ODE_CT
    • salvare la ricetta vera delle ODE

  • Devo chiudere tutto tra la fase 2 e la 3

  • Fase 3:
 -- AlessioSarti - 23 Nov 2007

Revision 62008-03-17 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 13 to 13
 

Documentation

Changed:
<
<

Maps

>
>

Computer names

Item/Stat/side PCName SystemNumber SystemName ProjectName
Feb 2&3/C MUDAQC03w 260 MUDAQC23 MUDAQC23
Feb 4&5/C MUDAQC04w 261 MUDAQC45 MUDAQC45
Feb 1/C MUDAQC01w 262 MUDAQC1 MUDAQC1
Feb 1/A MUDAQA01w 263 MUDAQA1 MUDAQA1
Feb 2&3/A MUDAQA03w 264 MUDAQA23 MUDAQA23
Feb 4&5/A MUDAQA04w 265 MUDAQA45 MUDAQA45
ODE/C MUODEC01w 266 MUDAQCO1 MUODECO1 (Q3)
ODE/C MUODEC02w 267 MUDAQCO2 MUODECO2 (Q4)
ODE/A MUODEA01w 268 MUDAQAO1 MUODEAO1
ODE/A MUODEA02w 269 MUDAQAO2 MUODEAO2(Q2)
T&P MUDCS01w 270 MUDCSSEN MUDCSSEN
FSM/C MUECSC01W 279 MUDAQC MUDAQC
FSM/A MUECSA01W 280 MUDAQA MUDAQA
LV/C MULVC01w 210 MUDCSLVC MUDCSLVC
LV/A MULVA01w 211 MUDCSLVA MUDCSLVA
HV/C MUHVC01w 212 MUHVC01 MUHVC01
HV/C MUHVC02w 213 MUHVC02 MUHVC02
HV/A MUHVA01w 214 MUHVA01 MUHVA01
HV/A MUHVA02w 215 MUHVA02 MUHVA02

FEB, DAQ Maps

  The Maps can be found on the PC in the pit in a folder on the Desktop named: MAPS

Revision 52008-03-17 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 65 to 65
 After each step you need to check that the communication is going as expected. Latest maraton known problem: last november! Since then everything is running smoothly.
Added:
>
>

HV

PNPI system

 

Systec

For problems concerning systec operation, please contact R. Nobrega or C. DePlano.

Line: 124 to 130
 
  • Remeber that you need to update the OPC server configuration file [created with Create structure panel] with updated information, restart the PVSS and the OPC server to have your modification properly taken.

-- AlessioSarti - 23 Nov 2007 \ No newline at end of file

Added:
>
>

META FILEATTACHMENT attachment="PNPI_Istructions.ppt" attr="" comment="Instruction for HV PNPI system" date="1205744751" name="PNPI_Istructions.ppt" path="PNPI_Istructions.ppt" size="938496" stream="PNPI_Istructions.ppt" user="Main.AlessioSarti" version="1"

Revision 42008-02-02 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 23 to 23
  For any problem please contact M. Lenzi
Changed:
<
<
  • To control LV in side A you should:
    • Log ont lbts01.cern.ch
    • From lbts01 you make a remote desktop connection to computer MULVA01W
>
>
  • To control LV you should:
    • Log on into lbts.cern.ch PC (online interface to the rest of the world)
    • From lbts you make a remote desktop connection to computer UI01
    • On UI01 you should look into 'MyComputer' going trough G: -> online -> ecs -> muon -> Shortcuts
    • Then you click on the shortcut of the pvss project you need (LV side A or C, depending on what you want to do). Details on PVSS project can be found below.
 

PVSS project

Developer: M. Lenzi

Changed:
<
<
  • The PVSS project to be used is MUDCSLVA
  • Before trying anything remember to 'take' privileges....
>
>
  • The PVSS project has its FSM and to control anything you need, first of all, to 'take' privileges....
  • Then you can navigate the panels trough the Quadrant and stations that you need to work on.
  FAQs:
  • Q:
Line: 60 to 63
 

After each step you need to check that the communication is going as expected.

Added:
>
>
Latest maraton known problem: last november! Since then everything is running smoothly.
 

Systec

Added:
>
>
For problems concerning systec operation, please contact R. Nobrega or C. DePlano.
 

Software configuration

HowTos

Revision 32007-11-23 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Line: 13 to 13
 

Documentation

Added:
>
>

Maps

The Maps can be found on the PC in the pit in a folder on the Desktop named: MAPS

 

Hardware Configuration

LV

Line: 108 to 112
 
Added:
>
>

Changing/updating mapping

  • Call the expert
  • Remeber that you need to update the OPC server configuration file [created with Create structure panel] with updated information, restart the PVSS and the OPC server to have your modification properly taken.
  -- AlessioSarti - 23 Nov 2007

Revision 22007-11-23 - AlessioSarti

Line: 1 to 1
 
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Added:
>
>

Useful links / informations / documentation

Online pages

Documentation

 

Hardware Configuration

LV

For any problem please contact M. Lenzi

Added:
>
>
  • To control LV in side A you should:
    • Log ont lbts01.cern.ch
    • From lbts01 you make a remote desktop connection to computer MULVA01W
 

PVSS project

Developer: M. Lenzi

Added:
>
>
  • The PVSS project to be used is MUDCSLVA
  • Before trying anything remember to 'take' privileges....

FAQs:

  • Q:
  • A:
 

Maraton Issues

Experts: M. Lenzi, p. Ciambrone

Added:
>
>
For any hardware problem please contact the experts.

Sometimes the Maraton goes into a funny state: it shows errors that are unlikely to be real hardware failures. In those cases you should carefully check:

  • That the OPC server is running correctly and the RCM is talking communicating correctly
  • That the communication btw the RCM and the Maraton is correct

OPC server restart can be done only with administrator privileges (ask M. Lenzi)

To exit from real funny situation the following chain of actions has proved to help:

Turn off PVSS and OPC server
Reboot RCM crate
Restart PVSS and OPC server
Poer cycle the Maraton

After each step you need to check that the communication is going as expected.

 

Systec

Revision 12007-11-23 - AlessioSarti

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbOnline"

Page that contains FAQs for DAQ testing in the pit

Hardware Configuration

LV

For any problem please contact M. Lenzi

PVSS project

Developer: M. Lenzi

Maraton Issues

Experts: M. Lenzi, p. Ciambrone

Systec

Software configuration

HowTos

Starting From scratch

Experts: R. Nobrega, C. Deplano

  • Start PVSS project
  • From GEDI start the CreateStructure panel
  • Ask expert for assistance

Normal Start

  • Start PVSS project
  • Start OPC server: do it sequentially, before SB then ODE
    • Start OPC server -num 5 : serves the SB
    • Start OPC server -num 4 : serves the ODES
  • Go in the fwDeviceEditorNavigator panel
  • Switch to Navigator mode
  • Select the ODE/Hardware Unit you want to test

Available tests

Connectivity Test

Experts: R. Nobrega, C. Deplano

Speed and parallelism

Some remarks:

  • So far we proved that is possible to run parallel jobs on different SB that are connected to different systec cables . This means that when you access one crate you can run up to four jobs in parallel without degrading the time performance
  • It's crucial, to avoid wasting test time that is already enormous, to FIX before running the full connectivity test, all the ECS connections problems that can be spotted easily in the very first part of the connectivity test:

Running test

a) Go in the fwDeviceEditorNavigator panel
b) Switch to Navigator mode
c) Select the ODE/Hardware Unit you want to test
d) Right click on 'view'
e) Select : 'Connectivity test'
f) Make the first part of the test: configuration
g) Click on 'continue' that perform the connectivity test.
h) Save the results with Export.txt into the ReportRun directory.

-- AlessioSarti - 23 Nov 2007

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback