09.18 SN changed degrader to 5.7mm Al (4mm + all variable degraders + additional 1mm)

09.24 R53 continues

      DSSSD#1 I_L to 8.16uA
      FEE64 temps OK
      Julabo FL11006 recirculating chiller OK - op temp +20 deg C

      Example HEC ADC spectra DSSSD #1-3 (attachments 1-12) 

09.59 R53 ends 
      Beam off - problem with refrigeration plant for BigRIPS quads

10.39 FEE64 temperatures (attachment 13)

10.51 Check ALL ASIC Control parameters 

11.15 Stat and Hit spectra for all AIDA FEE64 modules (attachments 14-15)
      Illustrates common noisy channels for each FEE64 channels 1 & 55 of 0-63
   

11.28 R54 
      Short run without beam, BNC PB-4 pulser frequency ~1Hz

12.55 R54 ends OK

14.00 Plot of leakage currents up to now included.
      Gradual increase in all detectors over course of experiment.
      Bias voltage on detector 1 (ch 1) increased to +150V at 0900 on 03/05, causing 
      an increase in I_L over preceding value.

16.00 Beam expected 21.00

18.30 No beam.
      HV ch 2 tripped (det 3)
      Reset HV and observed expected leakage current

19.00 HV ch 1 also tripped.
      Increased HV to +150V. Leakage current @ 8.02uA

09.19 Beam off on arrival, now back
      R51 running

      BigRIPS 88Ge setting

      Degraders 4mm Al + 1.3mm Al variable, MINOS target filled 

      FEE64 temperatures OK
      Julabo FL11006 recirculating chiller OK, operating temp +20 deg C
      Detector HV OK
      AIDA SYNC/PAUSE/RESUME rates OK

10.05 R51 ends

10.51 Change BigRIPS setting to 94Se

      OR MACB triggers from nnaida1, 2, 6, 10, 13 & 14 input EURICA trigger module input #7
      All nnaida1, 2, 6, 10, 13 & 14 fast discriminators currently disabled.

11.33 R53

      BigRIPS 94Se setting

      c. 15.54 EURICA DAQ LUPO timestamp reset

14.00 Degrader changed t0 4mm fixed + 0.7mm variable (Al)

Online spectra to monitor condition during run R51.

Position and energy spectra indicate implantation in 2nd DSSD. 

Tracking spectra is consistent with a larger beam angle on the horizontal direction.

Some first analysis of building events to look for implants and decays

Using both DISC and slow comparator values for time-stamp (whatever is available). Clearly there are some ADC
hits with a very early value for their corresponding time-stamp, that result in negative or very large dTS
values. Probably safer to use only ADC data for now (it's likely the simple algorithm used to correlate
discriminator hits and ADC hits can not cope with current conditions of ADC hits >> DISC hits):

time_stamp_dist_disc.png

Comparing analysis of file R51_3 for the two conditions: using the Fast discriminator data when available for
low energy range, or using only the time-stamp from the ADC hits.


The first two figures (time_stamp_dist_disc.png, XY_implant_disc_R51.png) are for including DISC hits as
time-stamp for event building: some have much smaller values than corresponding ADC hits, so the event is cut
short and we see a small number of identified implants.

Second set of plots is the same data but using only the timestamp for the slow comparator of the low energy
range. The number of identified events is much higher (compare 'Integral' value of the stats box).

Adjusted setting of MUSIC detector signals during break

MUSIC ---> (16dB att)  --> Lemo split --->  J13

                                                                  ---> J14

MUSIC ---> (16dB att)  --> Lemo split --->  J15

                                                                   ---> J16

MUSIC ---> (BNC att.)  --> Lemo split --->  J17

                                                                  ---> J18

MUSIC ---> (BNC att.)  --> Lemo split --->  J19

                                                                  ---> J20

A couple seem to bee too much attenuated.  Spectra for 88Ge setting attached.

0055: Degrader changed. 1mm removed.

            1.4mm total

0537: R38 ends nnaida11 slow comparator 0x20 -> 0x40 LEC fast comparator -> 0xff

0530: R39 10.00 AIDA status screenshots

1159: R39 ends HEC fast comparator 0x2 -> 0xf (all FEE64s)

1202: R40 nnaida8 no SYNCS see attachments 19-22

           VFEP toggled merge pause state check merge activity spinner accelerates nnaida8 GO Electronics (from select required function menu of Run Control) nnaida8 started OK toggled merge pause state

1500: Attachments 23-28 show waveforms, low E and high E spectra for nnaida6+11.

           Increasing fast comp threshold to 0xf shifts position of energy cut off away from zero point, as expected, but does not remove low E peak around ch 32500.

1530: Increase bias to +150V on det 1 (ch 1). Attachments 29-34 show waveforms, low E and high E spectra with increased bias voltage. Diode link threshold at 0x23

           V high E events in .L spectra show reduction over those before bias increase.

           In .H spectra from both nnaida6+11, increased bias reduced threshold. Finite threshold still seen on n-side however (greater than on p-side).

           All references/comparisons in this ELog entry re. nnaida11 are w.r.t. to spectra/waveforms seen at this 'standard' setting.

1544: Changed diode link thresh on nnaida11 to 0x11. Attachments 35-37.

           Saved run R42.

           High energy spectra saw threshold increase of ~700ch, but no other changed were observed.

1555: Change nnaida11 diode link thresh to 0x29. Saved run R43. Attachments 38-40.

            Saw reduction in high E threshold by ~700 ch but no other obvious changes.

1610: Changed diode link thresh on nnaida11 to 0x14 and preAmp reference to 0x20. Saved run R44. Attachments 41-44.

            Waveforms look much worse, more flatlining that previously seen.

            High E spectra show marginally higher threshold. No significant change in low E spectra.

1630: Changed nnaida11 preAmp ref to 0x40 and diode link thresh to 0x38. Saved run R45. Attachments 45-47

           Waveforms look similar to original setting. High E spectra show no significant change.

          Low E spectra have small peak near 32k and v. wide stretching to top of FSR.

1643: Changed nnaida11 preAmp ref to 0x60 and diode link thresh to 0x58. Saved run R46. Attachments 48-50.

            Waveforms settled on ~7500 much more frequently, with most signals beginning and returning to ~7500.

            High E spectra thresh at ~33500 as it was with 'standard' setting.

            Low E spectra show vast reduction in high E rubbish, looking more like an exponential decay compared to previous wide 'mound'.

            Big improvement over previous settings. Will try all n-side FEE with these settings later.

1700: Changed nnaida11 diode link thresh to 0x5a. Saved run R47 (~2hr run during tea break and other work).

           0x60 HEC fast comparator threshold (all FEE64s except nnaida30) 0x02.

19.04 R47 ends Change BigRIPS setting from 110Zr to 88Ge

19.15 R48 Pulser walkthough BNC PB-4 amplitude 90,000-10,000 @ 10,000 step, freq 25Hz.

            nnaida7 showed no SYNCS.

            Used procedure described above (1202) - nnaida7 recovered OK

19.28 Started run R48 - pulser walkthrough.

            R48 ends OK..

1944: Changed fast comparator threshold on LEC for...

• nnaida 1: 0xb -> 0x30
• nnaida2: 0x18 -> 0x30
• nnaida6: 0x10 -> 0x30
• nnaida10: 0x10 -> 0x30
• nnaida13: 0x12 -> 0x30
• nnaida14: 0x14 -> 0x30

          Change, for all n-side FEE64s, preAmp reference from previous value to 0x60 and diode link thresh to 0x5a.

          Saved settings to /MIDAS/DB/EXPERIMENTS/AIDA/2015Apr30-diode-mod3

 (around) 20:30 pm: started data taking for 88Ge setting. First runs are with empty H target at MINOS/DALI for transmission measurement.

                                     Degrader also changed during run R50. Initially: 0.6mm + 0.4mm + (0.3 mm?) + 1mm. The 1mm degrader was removed after ~ 1hr of run.

2300: NNAIDA#11: changed Fast Comparator of Low Energy channels to 0x40. It was set at 0xFF, and no discriminator data being produced. Rate of ~12 kHz for discriminator events in NNAIDA#11 for this setting (comparable to other FEE64s).

         RUN: R51_* started after adjusting the NNAIDA11 setting

I have an eight FEE64 system now in place on the LYCCA chamber with a PB-5 pulser going into the adapter cards test input. The test capacitor is 30pF.

I was going to explore the effect of the thresholds on the pulser peak.

I notice that the spectra look like those taken in RIKEN and not a single peak. In the 1GeV range I would interpret this as noise but since this is such a high energy i don't quite understand what is happening in the ASIC.

I thought i would share it with you.

PB-5 input to 50R is 10v with no attenuation. Signal height on the inline 'scope is +5.2v

ASICs are set to "default" with 1GeV range and 3uS shaping time.

Let me know if anything useful can be gleaned by more tests on LYCCA.

I have an eight FEE64 system now in place on the LYCCA chamber with a PB-5 pulser going into the adapter cards 
test input. The test capacitor is 30pF.

I was going to explore the effect of the thresholds on the pulser peak.

I notice that the spectra look like those taken in RIKEN and not a single peak. In the 1GeV range I would 
interpret this as noise but since this is such a high energy i don't quite understand what is happening in the 
ASIC.

I thought i would share it with you.

PB-5 input to 50R is 10v with no attenuation. Signal height on the inline 'scope is +5.2v

ASICs are set to "default" with 1GeV range and 3uS shaping time.

Let me know if anything useful can be gleaned by more tests on LYCCA.



Q = CV = 30pF * 5V = 150pC => ~ 3.42GeV => ADC channel ~ 27880

The spectra imply a positive test input. The spectra imply an inconsistency between the data
supplied and the peak position.

You display the spectra on a log scale ...  so the majority of events are in the peak ... but
why do some channels so a peak and others a peak plus a small number of higher amplitude/events?

What ASIC settings are you using?

What is the PB-5 frequency? ... PB-5 settings?

> I have an eight FEE64 system now in place on the LYCCA chamber with a PB-5 pulser going into the adapter cards 
> test input. The test capacitor is 30pF.
> 
> I was going to explore the effect of the thresholds on the pulser peak.
> 
> I notice that the spectra look like those taken in RIKEN and not a single peak. In the 1GeV range I would 
> interpret this as noise but since this is such a high energy i don't quite understand what is happening in the 
> ASIC.
> 
> I thought i would share it with you.
> 
> PB-5 input to 50R is 10v with no attenuation. Signal height on the inline 'scope is +5.2v
> 
> ASICs are set to "default" with 1GeV range and 3uS shaping time.
> 
> Let me know if anything useful can be gleaned by more tests on LYCCA.
> 
> 
> 
> Q = CV = 30pF * 5V = 150pC => ~ 3.42GeV => ADC channel ~ 27880
> 
> The spectra imply a positive test input. The spectra imply an inconsistency between the data
> supplied and the peak position.
> 
> You display the spectra on a log scale ...  so the majority of events are in the peak ... but
> why do some channels so a peak and others a peak plus a small number of higher amplitude/events?
> 
> What ASIC settings are you using?
> 
> What is the PB-5 frequency? ... PB-5 settings?

PB-5 is at 100Hz, fall time is 1 ms. 
ASIC settings default from VHDL.
They are in the manual. See EDOC955 at npg.dl.ac.uk

29300 => 2.1GeV ( very approx )  so yes this doesn't make sense. 
Hard to have a specific calibration or will your beam time give that.

I think the 30pF is correct but i can measure it on Wednesday......

      diode link threshold 0xca -> 0xb6
                           0x11 -> 0x2c 

00.20 R31
      1mm + 1.4mm Al degrader
00.42 R31 ends

      R32
      -1mm Al degrader
00.54 R32 ends

Data indicates changes to diode link threshold is 'switching off' decay p+n strip events,
n+n strips appear to be less affected

01.00 R33
      diode link threshold 0xca -> 0xbf
                           0x11 -> 0x23 

      ASIC parameters saved to /MIDAS/DB/EXPERIMENTS/AIDA/2015Apr30-diode-mod2

Ignore R34 & R35

09.40 Fast LEC/MEC discriminators disabled:
     Mask bits 31->0, 63->32 *not* 0->31 and 32->63 as implied by Disc Controls window

         Chan                 Mask
                             31->0      63->32
nnaida1                        0x0   0x4000000
nnaida2  ch 22, 26       0x4400001   0x8000000
nnaida6  ch  1                 0x2         0x0
nnaida9  ch 45 "               0x0      0x2000
nnaida10 ch 31 "        0x82000000  0x80000000
nnaida11 ch 55 "               0x0    0x800000
nnaida13                       0x0   0x4000000
nnaida16 ch 55 "               0x0    0x800000

Local Controls -> Timing O/P Control Register 0xc -> 0xe (OR64) https://elog.ph.ed.ac.uk/AIDA/79

09.48 R36
      BigRIPS 110Zr setting
      Degrader ?
10.43 R36 ends
      Beam off for ion source re-tune

10.50 nnaida6 good events c. 250k, c. 20Hz PAUSE/RESUME
      change slow comparator 0x14 -> 0x20
      rate/channel ~5kHz -> ~1kHz

      ASIC parameters saved to /MIDAS/DB/EXPERIMENTS/AIDA/2015Apr30-diode-mod2

12.00 VFEP updates 
      DataAcquisitionControl.tcl and sys.tcl

      Fast comparator masks are now saved
      MACB trigger mode default 0xe (OR64) and can be saved as a setting

      Stop/Go logic altered so that electronics data generation is the last to be GOED and first to be STOPPED 

12.10 Beam back

12.13 R38

From 20.00 29.4.15

Added
 3mm Al plate in front of MACI + Veto plastic detectors 
(offset in front of AIDA)

From 09.00 30.4.15

Added
 2mm Al plate following MUSIC
 +
 1.0 + 0.6 + 0.3 + 0.4 = 2.3mm Al plate (variable degrader)

1 - nnaida1 DSSSD#3 p+n (pulser?)
2 - nnaida1 DSSSD#3 p+n heavy ion
3 - nnaida6 DSSSD#1 p+n
4 - nnaida16 DSSSD#1 n+n
5 - nnaida14 DSSSD#2 p+n
6 - nnaida3 DSSSD#3 n+n
7 - nnaida13 DSSSD#3 p+n

50MSPS, 14-bit ADC, 1000 samples
Each trace is the most recent capture for that specific channel

Overnight
      Degrader OUT
      DAQ ran OK - data file R22
      DSSSD #3 (N1419 ch #2) tripped, re-enabled OK 

      Attachments 1-15 from R22
      nnaida10 DSSSD #1 ASIC #1-4 HEC ADC spectra + hit patterns
      nnaida2 DSSSD #1 ASIC #1-4 HEC ADC spectra + hit patterns
      nnaida1 DSSSD #1 ASIC #1-4 HEC ADC spectra + hit patterns
      HEC fast comparator LLD 0x8 - standard ASIC parameters

09.06 Beam off

09.36 Beam on

09.46 R23
      HEC fast comparator LLD 0x8 -> 0x2

c. 10.00 beam lost, cyclotron re-tuning

10.56 R23 stopped

11.20 FEE64 firmware update - /MIDAS/Aida/FEE_Riken_Apr14_26.bin
      See attachment 16

11.58 R24
14.35 R24 stopped

      R25 diode link threshold nnaida1 0xca -> 0xba, nnaida3 0x11 -> 0x18
14.52 R25 stopped

      R26 diode link threshold nnaida1 -> 0xbc, nnaida3 -> 0x1c
15.06 R26 stopped

15.00 Beam off

15.25 BigRIPS changed to 110Zr setting. Tuning.

17.05 Beam on

Ignore R27_0

17.06 R28
17.49 R28 stopped

Ignore R29, R30

22.56 diode link threshold 0xca -> 0xb6 (cf. preAmp ref 0xb2)
                           0x11 -> 0x2c (cf. preAmp ref 0x30)

      ASIC parameters saved to      /MIDAS/DB/EXPERIMENTS/AIDA/2015Apr30-diode-mod

23.18 Fast LEC/MEC discriminators disabled:
      Mask bits 31->0, 63->32 *not* 0->31 and 32->63 as implied by Disc Controls window

         Chan                 Mask
                             31->0      63->32
nnaida1                        0x0   0x4000000
nnaida2  ch 22, 26       0x4400001   0x8000000
nnaida6  ch  1                 0x1         0x0
nnaida9  ch 45 "               0x0      0x2000
nnaida10 ch 31 "        0x82000000  0x80000000
nnaida11 ch 55 "               0x0    0x800000
nnaida13                       0x0   0x4000000
nnaida16 ch 55 "               0x0    0x800000

00.04 Local Controls -> Timing O/P Control Register 0xc -> 0xe (OR64) https://elog.ph.ed.ac.uk/AIDA/79

A first online analysis code is running now in Desktop 4 aidas1

The source code and executable are in 

/homes/npg/AIDAonline

The following command launches the program from the above directory:

aidas1> ./AIDA-online.exe 

The code is set to update histograms every 10e6 events (about once per minute?).

Otherwise, click on the terminal running the program and press any key. This will produce the following menu:

online monitor is paused;
press 0 <Enter> to stop, 1 <Enter> to restart;


If <1> is selected the histogram are updated and the execution is continued.

If <0> is selected the program requests a confirmation and then exits (without saving the histograms, that's the
next step).


A few (interesting) screenshots attached.

I have tried the latest version ( 26 ) of the FEE64 code and carried out some measurements of the Fast Trigger delay from the Pulser signal ( not the Pulser Trigger out ) and observed the following.

The pulser gives a centroid of 28217 in the histogram.

This seems to me to be sensible as the discriminator is only a very simple comparator.

The OR64 ( 0xE )  signal works as True Fast NIM Logic. The OR16s ( 0xC ) logic works as inverse Fast NIM.

The OR64 is derived from the individual masked discriminator outputs. By default the Mask is not set.

1230: Attachments 

19.00 Screenshots taken during R20

 The Fast Trigger output of the FEE64 is formed from the OR of the four OR16 signals ( one from each of the ASICs.

The logic levels of the OR16 signals are active low in the FPGA and so if the are OR'd together then the output is inactive if any one of the ASICs is inactive.

This is a problem when the Fast Trigger is being used by other DAQ systems.

A new FPGA program 0x1b4FE01A ( version 26 ) is being compiled.

The Fast Trigger output will provide the logic AND of the four OR16 signals which should give the correct signal. This setting is selected by "Setup".

The other settings available using the Trigger register are shown below. Note that OR64 is the logic OR of the masked outputs of the ASIC individual Discriminator outputs.

when 0 => 

trigger_hit <= ASIC1_data_ready ;

when 1 =>

trigger_hit <= ASIC1_rdo_range  and ASIC1_data_ready ;

when 2 =>

trigger_hit <= ASIC2_rdo_range  and ASIC2_data_ready ;

when 3 =>

trigger_hit <= led_trigger(0) ;

when 4 =>

trigger_hit <= led_raw(0) ;

when 5 =>

trigger_hit <= chan_reset(0) ;

when 6 =>

trigger_hit <= force_capture_sync ;

when 7 =>

trigger_hit <= force_capture ;

when 8 =>

trigger_hit <= ASIC1_OR_16 ;

when 9 =>

trigger_hit <= ASIC2_OR_16 ;

when 10 =>

trigger_hit <= ASIC3_OR_16 ;

when 11 =>

trigger_hit <= ASIC4_OR_16 ;

when 12 =>

trigger_hit <= ASIC4_OR_16 and ASIC3_OR_16 and ASIC2_OR_16 and ASIC1_OR_16;

when 13 =>

trigger_hit <= led_trigger(1) ;

when 14 =>

trigger_hit <= OR64 ;

when 15 =>

trigger_hit <= ASIC4_OR_16 or ASIC3_OR_16 or ASIC2_OR_16 or ASIC1_OR_16;

Overnight
      Beam tuning, PID tests - beam stopped in scintilator detector + 1" thick Pb bricks 
      DAQ ran OK (not to disk)
      DSSSD #3 tripped, re-enabled OK 


09.00 AIDA temperatures - attachment 1
      CAEN N1419 HV settings - attachment 2

09.25 Statistics & lost activity - attachments 3-8

10.30 Scintilator detector + 1" thick Pb bricks removed
      ~1KHz 84Zn to Degrader + MICA + Veto + AIDA DSSSDs #1-3 + 10mm Al

      Data file R15 12.15-12.59 beam lost
      Attachments 9-14 DSSSD #1-3 HEC ADC spectra, HEC LLD 0x08

      Attachments 15-16 Examples of Data Readout Control following stalled DAQ GO (no SYNCs) 

      Data file R16 13.02-13.46 SYNCs lost/MERGE stalled
      HEC LLD 0x02

      Data file R17 13.46-14.20

      Data file R19 15.30-17.05

      Data file R20 17.06
      Fast comparator LLD HEC 0x02, LEC 0x20 (except nnaida30 HEC 0x20)

22.14 Data file R22 22.14 - 30.4.15 09.00
      Now using /data20/TapeData/May2015 to store data
      Spectra cleared at start of run
      DAQ OK, CAEN N1419 ch #2 tripped
      

       

replace RPI with model B+.  4 USB ports + 4 port switch

The RPI system has been replaced by a model B+ which has 4 internal USB ports

Connects to: 

    AIDA Power Control  USB1

    Serial port to FEE for console output     USB0

    CAEN N1419 HV power supply   USB2

All 3 connections use a USB => RS232 convert chip. The hardware cannot simply tell these apart. The USB ports assigned should however remain constant as long as the connections remain the same.

Power up RPI system.

At end of boot check the last couple of lines on the console for the assigned IP address.  Should be 10.1.1.114.

login using ID npg     Password is the same as for the data acq system.

then type startx

When the graphical console appears.

Firstly click on the icon TclHttpd Server to start the web server.

Start the web browser (Icon immediately to the right of the MENU icon at extreme left of the top row).

Connect to  http://localhost:8015/AIDA/Rly16/Rly16.tml         (the browser will have this in its recently used list)

The software now checks the potential USB devices for one which responds correctly to a request for the firmware in the AIDA Power Control box.

The GUI shows the port in use. Currently it is /dev/ttyUSB1

Even if the hardware changes the software should find the correct port to use but this suggests the other uses will also have changed   (you may need to use dmesg to locate which ports are assigned)

You can use the icon PuTTY Client to start the putty program.

connect and open for USB0 to monitor the FEE64 console

connect and open for USB2 to control the CAEN N1419

You can connect from a remote terminal using  ssh -X -l npg nnrpi1   

 However to start putty from the command line you will need

    sudo chmod 660 /dev/ttyUSB0;  putty                (for the FEE console)

or

   sudo chmod 660 /dev/ttyUSB2; putty                 (for the N1419 control)

28/04/15

1420: Carried out ASIC optimisation tests to find best shaping time. Chose system wide shaping time of 0x6.

           Waveforms of example FEEs/channels attachments 1-6.

20.34 Pulser walkthough - data file /TapeData/May2015/R14_0

           BNC PB_4 settings

           90,000 - 10,0000 @ 10,000 step

           t_r = 50ns, tau_d = 50us

          - polarity

          x10 attenuator in

         tail pulse, delay min, int ref

        frequency 250Hz

We've constructed a beta trigger with the signals from the p-side of the three DSSDs (OR of all fast
discriminator channels of each FEE).

det1 -> NNAIDA#6 -> MACB#10.2
det1 -> NNAIDA#10 -> MACB#3.4
det2 -> NNAIDA#2 -> MACB#10.3
det2 -> NNAIDA#14 -> MACB#3.2
det3 -> NNAIDA#1 -> MACB#10.4
det3 -> NNAIDA#13 -> MACB#3.3

beta-trigger is OR of all above MACB trigger outputs. Diagram for logic circuit is in paper logbook.


Bellow are some oscilloscope sceenshots. Some things to note about the MACB trigger outputs:

- all show multiple outputs for each pulser input. Some channels seem to have higher level for such 'multiplicity'.

- the width of the outputs varies for different channels (from ~40 ns to ~300 ns)

- the delay between the pulser signal and the output from the MACB is quite large, and also different for each
MACB (measured from ~800 ns up to 2 usec).


Scope screenshots: 

 - light blue is the trigger output from Pulser
 - dark blue is output from trigger channel of MACB

 MACB#10.2: tek00001.tif
 MACB#3.4: tek00002.tif
 MACB#10.3: tek00005.tif
 MACB#3.2: tek00007.tif
 MACB#10.4: tek000011.tif
 MACB#3.3: tek000018.tif

@ CAEN N1419

Set programmable parameters - see CAEN N1419 manual p.16 (attachment 1)

INTERLOCK = CLOSED
CONTROL = REMOTE

Set front panel switches HV on/off/kill = ON
No interlock jumpers




@ AIDA server

From a command terminal, login to nnrpi1 using ssh, set device permissions, and launch putty.

ssh -X nnrpi1 -l npg
password:
    :
    :
    :
% sudo chmod 777 /dev/ttyUSB2
% putty &

From the putty window sequentially select 'USB2', 'load' and 'open' - this will select
and load a saved serial session for device /dev/ttyUSB2 and launch a command terminal
for the serial session.

Enter the command 'caen' followed by return. Note the command is not echoed.

The CAEN HV interface should appear. Enter the command 'd' to display/modify parameters.
See CAEN N1419 manual pp.27-29 for further commands. See attachment 2.

N.B. The above procedure assumes:

/dev/ttyUSB0 = USB-controlled ac mains switch      (device pl2303)
/dev/ttyUSB1 = serial link to FEE64 system console (device FT232RL)
/dev/ttyUSB2 = CAEN N1419                          (device FT232BM)

However, these assignments may vary. You can use the command dmesg to check assignments.
For example,

% dmesg | grep usb
[    1.178926] usbcore: registered new interface driver usbfs
[    1.184722] usbcore: registered new interface driver hub
[    1.190218] usbcore: registered new device driver usb
[    1.568604] usbcore: registered new interface driver smsc95xx
[    2.065233] dwc_otg bcm2708_usb: DWC OTG Controller
[    2.075294] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
[    2.087646] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
[    2.115566] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.127464] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.139731] usb usb1: Product: DWC OTG Controller
[    2.149477] usb usb1: Manufacturer: Linux 3.18.7+ dwc_otg_hcd
[    2.160291] usb usb1: SerialNumber: bcm2708_usb
[    2.190521] usbcore: registered new interface driver usb-storage
[    2.348492] usbcore: registered new interface driver usbhid
[    2.360241] usbhid: USB HID core driver
[    2.677666] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.897985] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    2.910008] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.217656] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.327968] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.340138] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.422390] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet,
b8:27:eb:0b:f6:73
[    3.517666] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[    3.630124] usb 1-1.3: New USB device found, idVendor=067b, idProduct=2303
[    3.642534] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.655514] usb 1-1.3: Product: USB-Serial Controller D
[    3.666257] usb 1-1.3: Manufacturer: Prolific Technology Inc. 
[    3.761138] usb 1-1.4: new low-speed USB device number 5 using dwc_otg
[    3.894746] usb 1-1.4: New USB device found, idVendor=046d, idProduct=c016
[    3.908414] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.922059] usb 1-1.4: Product: Optical USB Mouse
[    3.933904] usb 1-1.4: Manufacturer: Logitech
[    3.955374] input: Logitech Optical USB Mouse as
/devices/platform/bcm2708_usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:046D:C016.0001/input/input0
[    3.976035] hid-generic 0003:046D:C016.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Optical USB Mouse]
on usb-bcm2708_usb-1.4/input0
[    4.087698] usb 1-1.5: new low-speed USB device number 6 using dwc_otg
[    4.343360] usb 1-1.5: New USB device found, idVendor=04f2, idProduct=0402
[    4.359726] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.377627] usb 1-1.5: Product: USB Keyboard
[    4.377641] usb 1-1.5: Manufacturer: Chicony
[    4.456521] input: Chicony USB Keyboard as
/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:04F2:0402.0002/input/input1
[    4.475410] hid-generic 0003:04F2:0402.0002: input,hidraw1: USB HID v1.11 Keyboard [Chicony USB Keyboard] on
usb-bcm2708_usb-1.5/input0
[    4.634626] input: Chicony USB Keyboard as
/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:04F2:0402.0003/input/input2
[    4.657391] hid-generic 0003:04F2:0402.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Chicony USB
Keyboard] on usb-bcm2708_usb-1.5/input1
[    7.431307] usbcore: registered new interface driver usbserial
[    7.659127] usbcore: registered new interface driver usbserial_generic
[    7.806673] usbserial: USB Serial support registered for generic
[    8.078137] usbcore: registered new interface driver pl2303
[    8.408967] usbserial: USB Serial support registered for pl2303
[    9.088988] usb 1-1.3: pl2303 converter now attached to ttyUSB0                          <- FEE64 console
[   13.617763] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
[   13.749727] usb 1-1.2: New USB device found, idVendor=05e3, idProduct=0608
[   13.775541] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   13.807792] usb 1-1.2: Product: USB2.0 Hub
[   20.127979] usb 1-1.2.2: new full-speed USB device number 8 using dwc_otg
[   20.294212] usb 1-1.2.2: New USB device found, idVendor=0403, idProduct=6001
[   20.323567] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   20.357627] usb 1-1.2.2: Product: FT232R USB UART
[   20.397680] usb 1-1.2.2: Manufacturer: FTDI
[   20.415415] usb 1-1.2.2: SerialNumber: A801LOA8
[   20.542107] usbcore: registered new interface driver ftdi_sio
[   20.569826] usbserial: USB Serial support registered for FTDI USB Serial Device
[   20.628458] usb 1-1.2.2: Detected FT232RL
[   20.651619] usb 1-1.2.2: FTDI USB Serial Device converter now attached to ttyUSB1         <- ac mains switch
[   23.708086] usb 1-1.2.3: new full-speed USB device number 9 using dwc_otg
[   23.824265] usb 1-1.2.3: New USB device found, idVendor=0403, idProduct=6001
[   23.824306] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   23.824326] usb 1-1.2.3: Product: USB <-> Serial
[   23.824346] usb 1-1.2.3: Manufacturer: FTDI
[   23.833176] usb 1-1.2.3: Detected FT232BM
[   23.834515] usb 1-1.2.3: FTDI USB Serial Device converter now attached to ttyUSB2         <- CAEN N1419
[  775.531187] ftdi_sio ttyUSB2: usb_serial_generic_read_bulk_callback - urb stopped: -32
[  775.531296] ftdi_sio ttyUSB2: usb_serial_generic_read_bulk_callback - urb stopped: -32
[  775.705443] usb 1-1.2.3: USB disconnect, device number 9
[  780.036554] usb 1-1.2.3: new full-speed USB device number 10 using dwc_otg
[  780.153082] usb 1-1.2.3: New USB device found, idVendor=0403, idProduct=6001
[  780.153150] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  780.153174] usb 1-1.2.3: Product: USB <-> Serial
[  780.153193] usb 1-1.2.3: Manufacturer: FTDI
[  780.167981] usb 1-1.2.3: Detected FT232BM
[  780.169356] usb 1-1.2.3: FTDI USB Serial Device converter now attached to ttyUSB2         <- CAEN N1419
[ 2364.526816] ftdi_sio ttyUSB2: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 2364.526982] ftdi_sio ttyUSB2: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 2364.657165] usb 1-1.2.3: USB disconnect, device number 10
[ 2365.657499] usb 1-1.2.3: new full-speed USB device number 11 using dwc_otg
[ 2365.774075] usb 1-1.2.3: New USB device found, idVendor=0403, idProduct=6001
[ 2365.774116] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2365.774142] usb 1-1.2.3: Product: USB <-> Serial
[ 2365.774268] usb 1-1.2.3: Manufacturer: FTDI
[ 2365.788695] usb 1-1.2.3: Detected FT232BM
[ 2365.790604] usb 1-1.2.3: FTDI USB Serial Device converter now attached to ttyUSB2         <- CAEN N1419

If using >1 CAEN N1419 check the output of the command 'demsg usb' for FT232BM devices and identify
the USB device numbers. 

You should then set the device permissions for *each* /dev/ttyUSB[n] and start a putty session for *each*
CAEN N1419 module. You can distinguish CAEN N1419 modules by the address (Addr) label shown in the CAEN
display.