14.00 MACB settings (from left -> right)

           MACB#1 is grandparent in tree

           #2 and #3 are parents

           Rest are children.

14.05 MACBs 1 and 3 (master) replaced with spares. No change, clocks remain not locked.

 Apologies, I made a mistake in the information above.

MACB#1 is the grandparent, but #2 and #7 are the parents, with #3-6 and #8-11 the children.

The master goes through MACB#2 to the first port on #3.

So the current setup follows, and always has done, your instructions above.

Peakfind appears not to be working on aidas1 - example spectrum attached


aidas1> peakfind -spectrum /MIDAS/SpecData/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf -limit 33000 64000 -fwhm 85
-accept 10
Peak finding for /MIDAS/SpecData/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf, Title 
No.     Channel            Area           Fwhm 
aidas1> ls -l /MIDAS/SpecData/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf
-rwxrwxrwx. 1 nfsnobody nfsnobody 262656 May 30 10:42 /MIDAS/SpecData/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf


Same spectrum analysed at Edinburgh (Sun/Solaris 10)

w29> peakfind -spectrum /home/td/riken/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf -limit 33000 64000 -fwhm 85
-accept 10
Peak finding for /home/td/riken/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf, Title 
No.     Channel            Area           Fwhm 
  1   34649.72(3.059)      123.5(  11.3)   65.98
  2   35542.99(0.855)     1756.0(  42.0)   79.13
  3   36363.14(0.854)     1820.0(  42.8)   79.66
  4   37203.16(0.776)     2139.9(  46.4)   80.00
  5   38087.83(0.852)     1863.0(  43.3)   79.62
  6   38984.27(0.842)     1853.9(  43.2)   79.27
  7   39889.04(0.832)     1755.9(  42.0)   78.59
  8   40790.80(0.855)     1930.7(  44.2)   79.45
w29> ls -l /home/td/riken/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf
-rwxr-xr-x   1 td       staff     262656 May 30 02:42 /home/td/riken/AIDA/nnaida4/2016May30-03.41.52/1.5.L.msf

10.30 Pulser walkthrough carried out 90,000 - 10,000 @ 10,000 step

10.40 .msf spectra saved /MIDAS/SpecData/AIDA

13.30 Swapped MACB module #1 - no change (root module)
      Swapped MACB module #2 - no change
      Swapped MACB module #3 - no change (nnaida5 attached to port 1 of this MACB)

      Note cabling not changed during above tests

15.20 Swap nnaida5 & nnaida6 FEE module for nnaida31 & nnaida32 and update startup.tcl and dhcpd.conf
      accordingly - see attached and appended 

      No resyncs at all

16.15 Re-install original nnaida5 & nnaida6 

      No resyncs at all - see attachment 2

#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample  
#

authoritative;

ddns-update-style none; ddns-updates off;

max-lease-time 691200;

option domain-search code 119 = string;

subnet 10.1.1.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.1.255;
   option routers 10.1.1.250;
   pool {
      range 10.1.1.100 10.1.1.249;
   }
}

subnet 10.1.2.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.2.255;
   option routers 10.1.2.250;
   pool {
      range 10.1.2.100 10.1.2.249;
   }
}

subnet 10.1.3.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.3.255;
   option routers 10.1.3.250;
   pool {
      range 10.1.3.100 10.1.3.249;
   }
}

subnet 10.1.4.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.4.255;
   option routers 10.1.4.250;
   pool {
      range 10.1.4.100 10.1.4.249;
   }
}

subnet 10.1.5.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.5.255;
   option routers 10.1.5.250;
   pool {
      range 10.1.5.100 10.1.5.249;
   }
}

group {
   use-host-decl-names true;
   default-lease-time 3600;
   max-lease-time 14400;

   server-name "10.1.1.250";
   next-server 10.1.1.250;

   host nnrpi1 {
     hardware ethernet b8:27:eb:78:ee:44;
     fixed-address 10.1.1.251;
   }
   host nnaida1 {
     hardware ethernet 00:04:a3:2a:d0:1b;
     fixed-address 10.1.1.1;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida1,tcp";
   }
   host nnaida2 {
     hardware ethernet 00:04:a3:2a:d9:e1;
     fixed-address 10.1.1.2;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida2,tcp";
   } 
#   host nnaida5 {
#     hardware ethernet 00:04:a3:2a:d0:10;
#     fixed-address 10.1.1.5;
#     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida5,tcp";
#   }
#   host nnaida6 {
#     hardware ethernet 00:04:a3:2a:d4:b7;
#     fixed-address 10.1.1.6;
#     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida6,tcp";
#   }
   host nnaida5 {
     hardware ethernet 00:04:a3:2b:11:ae;
     fixed-address 10.1.1.5;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida5,tcp";
   }
   host nnaida6 {
     hardware ethernet 00:04:a3:2a:ed:b9;
     fixed-address 10.1.1.6;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida6,tcp";
   }
   host nnaida9 {
     hardware ethernet 00:04:a3:2a:d9:ad;
     fixed-address 10.1.1.9;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida9,tcp";
   }
   host nnaida10 {
     hardware ethernet 00:04:a3:2a:f7:07;
     fixed-address 10.1.1.10;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida10,tcp";
   }
   host nnaida13 {
     hardware ethernet 00:04:a3:2b:11:b9;
     fixed-address 10.1.1.13;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida13,tcp";
   }
   host nnaida14 {
     hardware ethernet 00:04:a3:2b:11:b8;
     fixed-address 10.1.1.14;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida14,tcp";
   }
   host nnaida17 {
     hardware ethernet 00:04:a3:2a:d9:cc;
     fixed-address 10.1.1.17;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida17,tcp";
   }
   host nnaida18 {
     hardware ethernet 00:04:a3:2a:b2:b2;
     fixed-address 10.1.1.18;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida18,tcp";
   }
   host nnaida21 {
     hardware ethernet 00:04:a3:2b:27:23;
     fixed-address 10.1.1.21;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida21,tcp";
   }
   host nnaida22 {
     hardware ethernet 00:04:a3:2a:f6:e9;
     fixed-address 10.1.1.22;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida22,tcp";
   }
   host nnaida25 {
     hardware ethernet 00:04:a3:2a:d0:11;
     fixed-address 10.1.1.25;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida25,tcp";
   }
   host nnaida26 {
     hardware ethernet 00:04:a3:2b:27:54;
     fixed-address 10.1.1.26;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida26,tcp";
   }
   host nnaida29 {
     hardware ethernet 00:04:a3:2a:d0:06;
     fixed-address 10.1.1.29;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida29,tcp";
   }
   host nnaida30 {
     hardware ethernet 00:04:a3:2a:d9:b6;
     fixed-address 10.1.1.30;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida30,tcp";
   }


}


group {
   use-host-decl-names true;
   default-lease-time 3600;
   max-lease-time 14400;

   server-name "10.1.2.250";
   next-server 10.1.2.250;

   host nnaida3 {
     hardware ethernet 00:04:a3:2a:f7:06;
     fixed-address 10.1.2.3;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida3,tcp";
   }
   host nnaida4 {
     hardware ethernet 00:04:a3:2a:ed:b8;
     fixed-address 10.1.2.4;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida4,tcp";
   }
   host nnaida7 {
     hardware ethernet 00:04:a3:2a:b8:8d;
     fixed-address 10.1.2.7;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida7,tcp";
   }
   host nnaida8 {
     hardware ethernet 00:04:a3:2a:9c:07;
     fixed-address 10.1.2.8;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida8,tcp";
   }
   host nnaida11 {
     hardware ethernet 00:04:a3:2b:11:af;
     fixed-address 10.1.2.11;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida11,tcp";
   }
   host nnaida12 {
     hardware ethernet 00:04:a3:2a:d0:2f;
     fixed-address 10.1.2.12;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida12,tcp";
   }
   host nnaida15 {
     hardware ethernet 00:04:a3:2a:f3:ac;
     fixed-address 10.1.2.15;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida15,tcp";
   }
   host nnaida16 {
     hardware ethernet 00:04:a3:2a:9c:0e;
     fixed-address 10.1.2.16;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida16,tcp";
   }
# 1 of 2 scratch FEE modules assembled by PJCS April 2016
   host nnaida19 {
     hardware ethernet 00:04:a3:2a:ed:9a;
     fixed-address 10.1.2.19;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida19,tcp";
   }
   host nnaida20 {
     hardware ethernet 00:04:a3:2b:11:c5;
     fixed-address 10.1.2.20;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida20,tcp";
   }
   host nnaida23 {
     hardware ethernet 00:04:a3:2a:b8:90;
     fixed-address 10.1.2.23;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida23,tcp";
   }
   host nnaida24 {
     hardware ethernet 00:04:a3:2a:b6:45;
     fixed-address 10.1.2.24;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida24,tcp";
   }
   host nnaida27 {
     hardware ethernet 00:04:a3:2b:22:55;
     fixed-address 10.1.2.27;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida27,tcp";
   }
# 2 of 2 scratch FEE modules assembled by PJCS April 2016
   host nnaida28 {
     hardware ethernet 00:04:a3:2b:09:e7;
     fixed-address 10.1.2.28;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida28,tcp";
   }
#   host nnaida31 {
#     hardware ethernet 00:04:a3:2b:11:ae;
#     fixed-address 10.1.2.31;
#     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida31,tcp";
#   }
#   host nnaida32 {
#     hardware ethernet 00:04:a3:2a:ed:b9;
#     fixed-address 10.1.2.32;
#     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida32,tcp";
#   }
}


group {
# 8 days
   default-lease-time 691200;

#    option dhcp-client-identifier "\0foo";

   host nndhcp052 {
# Analysis server
     hardware ethernet 00:22:19:50:02:40;
     fixed-address 10.1.1.252;
   }

}

Throughout day:
      DSSD2 (3058-25) would not bias, either short circuit or suspiciously low leakage current.
      Carried out some test in situ which were inconclusive.
      Removed snout and took DSSD2 out.
      Measuring the resistance across the two pins providing the n+n bias yielded 20 Ohms.
      For the p+n the same measurement saw an open circuit => at least one of the bond wires broken.

      DSSD1 (3131-9) was moved into the DSSD2 position and DSSD1 is now BB18-1000 3058-4.

      All detectors were biased downstairs and all looked fine - leakage currents of 3.1 - 3.8 uA.

      First detector sits 54.5cm from Al base plate and 10cm from the upstream end of the snout.
      9mm between each of the DSSDs.

      Stack now:
           |   3058-4
        b  |   3131-9
        e  |   2998-23
        a  |   3058-5
        m  |   3058-6
           V   3058-7

      207Bi source installed at end of snout.

      Snout moved upstairs and mounted.
      DSSD2 would not bias. This was due to the HV cable providing bias for this DSSD having a short to ground.
      Replaced with HV cable 7 and biased successfully.
      All DSSDs now bias. Screenshots of leakage currents attached (attachments 4+5) at room temp 25.3oC.
      Caen module Addr 00 provides bias to DSSDs 1, 2, 3 and 4 via channels 0, 1, 2 and 3 respectively.
      Module Addr 01 provides bias to DSSDs 5 and 6 on channels 0 and 1, respectively.
 
      Snout pushed in to EURICA.

22.05 nnaida17 ASIC parameters not loading
      power cycle & reboot

      nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3

> Throughout day:
>       DSSD2 (3058-25) would not bias, either short circuit or suspiciously low leakage current.
>       Carried out some test in situ which were inconclusive.
>       Removed snout and took DSSD2 out.
>       Measuring the resistance across the two pins providing the n+n bias yielded 20 Ohms.
>       For the p+n the same measurement saw an open circuit => at least one of the bond wires broken.
> 
>       DSSD1 (3131-9) was moved into the DSSD2 position and DSSD1 is now BB18-1000 3058-4.
> 
>       All detectors were biased downstairs and all looked fine - leakage currents of 3.1 - 3.8 uA.
> 
>       First detector sits 54.5cm from Al base plate and 10cm from the upstream end of the snout.
>       9mm between each of the DSSDs.
> 
>       Stack now:
>            |   3058-4
>         b  |   3131-9
>         e  |   2998-23
>         a  |   3058-5
>         m  |   3058-6
>            V   3058-7
> 
>       207Bi source installed at end of snout.
> 
>       Snout moved upstairs and mounted.
>       DSSD2 would not bias. This was due to the HV cable providing bias for this DSSD having a short to ground.
>       Replaced with HV cable 7 and biased successfully.
>       All DSSDs now bias. Screenshots of leakage currents attached (attachments 4+5) at room temp 25.3oC.
>       Caen module Addr 00 provides bias to DSSDs 1, 2, 3 and 4 via channels 0, 1, 2 and 3 respectively.
>       Module Addr 01 provides bias to DSSDs 5 and 6 on channels 0 and 1, respectively.
>  
>       Snout pushed in to EURICA.
> 
> 22.05 nnaida17 ASIC parameters not loading
>       power cycle & reboot
> 
>       nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3

I suggest you check the hdmi hasn't been disturbed in the Macb or the FEE64.. Since the others are ok. I suggest it is the cable from the 
Macb 
to the FEE64 #5. If this fails to correct then please send a screen shot of the Local Controls status for nnaida5. 

> > 22.05 nnaida17 ASIC parameters not loading
> >       power cycle & reboot
> > 
> >       nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3
> 
> I suggest you check the hdmi hasn't been disturbed in the Macb or the FEE64.. Since the others are ok. I
suggest it is the cable from the 
> Macb 
> to the FEE64 #5. If this fails to correct then please send a screen shot of the Local Controls status for
nnaida5. 

See enclosed.

> 
> > > 22.05 nnaida17 ASIC parameters not loading
> > >       power cycle & reboot
> > > 
> > >       nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3
> > 
> > I suggest you check the hdmi hasn't been disturbed in the Macb or the FEE64.. Since the others are ok. I
> suggest it is the cable from the 
> > Macb 
> > to the FEE64 #5. If this fails to correct then please send a screen shot of the Local Controls status for
> nnaida5. 
> 
> See enclosed.

The LMK3200 control register looks wrong.
Look at another FEE and I think it should be 0x1b

> > 
> > > > 22.05 nnaida17 ASIC parameters not loading
> > > >       power cycle & reboot
> > > > 
> > > >       nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3
> > > 
> > > I suggest you check the hdmi hasn't been disturbed in the Macb or the FEE64.. Since the others are ok. I
> > suggest it is the cable from the 
> > > Macb 
> > > to the FEE64 #5. If this fails to correct then please send a screen shot of the Local Controls status for
> > nnaida5. 
> > 
> > See enclosed.
> 
> The LMK3200 control register looks wrong.
> Look at another FEE and I think it should be 0x1b

nnaida1-4 LMK03200 control register 0xb cf. nnaida5 0x7

> > > 
> > > > > 22.05 nnaida17 ASIC parameters not loading
> > > > >       power cycle & reboot
> > > > > 
> > > > >       nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3
> > > > 
> > > > I suggest you check the hdmi hasn't been disturbed in the Macb or the FEE64.. Since the others are ok. I
> > > suggest it is the cable from the 
> > > > Macb 
> > > > to the FEE64 #5. If this fails to correct then please send a screen shot of the Local Controls status for
> > > nnaida5. 
> > > 
> > > See enclosed.
> > 
> > The LMK3200 control register looks wrong.
> > Look at another FEE and I think it should be 0x1b
> 
> nnaida1-4 LMK03200 control register 0xb cf. nnaida5 0x7

Changing nnaida5 LMK03200 control register 0x7 -> 0xb does not help - see attached - system wide checks
and clock lock status 0x6 (unchanged)

> > > > 
> > > > > > 22.05 nnaida17 ASIC parameters not loading
> > > > > >       power cycle & reboot
> > > > > > 
> > > > > >       nnaida5 (master) clock not locked - status 0x6 - see attachments 1-3
> > > > > 
> > > > > I suggest you check the hdmi hasn't been disturbed in the Macb or the FEE64.. Since the others are ok. I
> > > > suggest it is the cable from the 
> > > > > Macb 
> > > > > to the FEE64 #5. If this fails to correct then please send a screen shot of the Local Controls status for
> > > > nnaida5. 
> > > > 
> > > > See enclosed.
> > > 
> > > The LMK3200 control register looks wrong.
> > > Look at another FEE and I think it should be 0x1b
> > 
> > nnaida1-4 LMK03200 control register 0xb cf. nnaida5 0x7
> 
> Changing nnaida5 LMK03200 control register 0x7 -> 0xb does not help - see attached - system wide checks
> and clock lock status 0x6 (unchanged)

Changing nnaida5 LMK03200 control register 0x7 -> 0x1b does not help - nnaida5 fails 'check clock status'
and check clock lock *not* locked status *0x0*

18.30 Options for nnaida19 and a.n.other (working) FEE (nnaida18)

15.20 DAQ histogramming & data transfer #1 enabled
      Merger configured, started, input paused
      Following DAQ GO nnaida9 data transfer 'X' nnaida19 histogramming 'H' disappear - see attachments 1-7

      Workaround suggested by https://elog.ph.ed.ac.uk/AIDA/230 appear not to work


16.25 Resolved data transfer issue
      nnaida9 producing SYNCs but merger data queue blocked
      rebooted aidas1

      nnaida19 histogramming issue remains

17:50 6 DSSD insalled

      From front to back of stack:
        
      DSSD 1 = 3131-9
           2 = 3058-25 (rotated 90deg w.r.t. other detectors - p-strips horizontal and n-strips vertical)
           3 = 2998-23
           4 = 3058-5
           5 = 3058-6
           6 = 3058-7

      HV mapping (-ve bias):

        DSSD     Braid      Core
          1     nnaida20   nnaida17
          2     nnaida19   nnaida18
          3     nnaida12   nnaida14
          4     nnaida11   nnaida13
          5     nnaida4    nnaida6
          6     nnaida3    nnaida5

18.55 Change ASIC settings 

      nnaida18, nnaida21 positive -> negative input
                         diode link threshold 0xca -> 0xbf
                         LED settings negative -> positive, threshold 7200 -> 9000

      nnaida19, nnaida24 negative -> positive input
                         diode link threshold 0x11 -> 0x23
                        LED settings positive -> negative, threshold 9000 -> 7200

      Saved new settings to DB key 2016May28-18.52.07
      Saved new DB key to Options

> 15.20 DAQ histogramming & data transfer #1 enabled
>       Merger configured, started, input paused
>       Following DAQ GO nnaida9 data transfer 'X' nnaida19 histogramming 'H' disappear - see attachments 1-7
> 
>       Workaround suggested by https://elog.ph.ed.ac.uk/AIDA/230 appear not to work
> 

########### The reason being that it is not the solution to this problem. When the X will not stay it seems to be because the FEE64 cannot open a 
connection to the Server. -------- Entry 230 was to help when the rates in the fastest  part of the system caused one of the FEE64 to be blocked for 
control access  while waiting for the slowest to produce data. Judging by the next entry in this diary I think this is now understood but .... 'belt and 
braces' seems a good idea ;-)

I've not seen the 'H' disappear but it could similarly mean that the enabling of Histogramming is failing. Perhaps check the Options settings for this 
FEE64 to see that the Histogram quantity and size parameters are the same as another FEE64.

> 
> 16.25 Resolved data transfer issue
>       nnaida9 producing SYNCs but merger data queue blocked
>       rebooted aidas1
> 
>       nnaida19 histogramming issue remains
> 
> 17:50 6 DSSD insalled
> 
>       From front to back of stack:
>         
>       DSSD 1 = 3131-9
>            2 = 3058-25 (rotated 90deg w.r.t. other detectors - p-strips horizontal and n-strips vertical)
>            3 = 2998-23
>            4 = 3058-5
>            5 = 3058-6
>            6 = 3058-7
> 
>       HV mapping (-ve bias):
> 
>         DSSD     Braid      Core
>           1     nnaida20   nnaida17
>           2     nnaida19   nnaida18
>           3     nnaida12   nnaida14
>           4     nnaida11   nnaida13
>           5     nnaida4    nnaida6
>           6     nnaida3    nnaida5
> 
> 18.55 Change ASIC settings 
> 
>       nnaida18, nnaida21 positive -> negative input
>                          diode link threshold 0xca -> 0xbf
>                          LED settings negative -> positive, threshold 7200 -> 9000
> 
>       nnaida19, nnaida24 negative -> positive input
>                          diode link threshold 0x11 -> 0x23
>                         LED settings positive -> negative, threshold 9000 -> 7200
> 
>       Saved new settings to DB key 2016May28-18.52.07
>       Saved new DB key to Options

All AIDA operations are controlled from the Dell T410 Workstation aidas1 using web browsers.

AIDA has multiple, independent data acquisition servers connected by an Ethernet network.

Response times to commands, information updates etc are ~10-60s - please be patient!



How To Start Run 

1) Workspace 1 - Firefox web browser - Run Control tab

   Select Update

   Check DAQ stopped (green GO button displayed)

   Check state of *all* data acquisition servers is 'stopped' and histogramming and data transfer 
   is enabled indicated by 'H X'

   See attachment 1

2) Workspace 2 - Firefox web browser - TapeServer tab

   Check Reload

   Check TapeServer stopped and disk file closed (green GO button displayed)

   See attachment 2

3) Workspace 2 - Firefox web browser - MERGE tab

   Check Reload

   Check Merge Program paused - see banner 

   Merge State = GOing     :    paused     :    xfer enabled     :    output paused

   If not paused select Toggle Merge Program Pause State

   See attachment 3

4) Workspace 1 - Firefox web browser - ASIC Control tab

   Check Reload

   Check 'Act on ALL FEE64 modules?' and wait for request to be completed

   Check 'Act on ALL ASICs' and wait for request to be completed

   From 'Select required function' select 'Check ASIC Control'
   After ~60s a pop-up will appear showing the response from each ASIC of each data acquisition server.
   Check all ASICs are OK and status = 0x001F0000.
   Dismiss pop-up by selecting OK

   See attachments 4-5

5) Workspace 1 - Firefox web browser - Run Control tab 

   Start DAQ - select green GO button

   Wait (~60s) until state of all data acquisition servers (nnaida1, nnaida2 ... etc) updates 

   Select 'Data Acquisition Statistics'

6) Workspace 1 - Firefox web browser - Statistics tab 

   Check Reload

   Check 'Show ALL Data Acquisition Servers' 

   From 'Select counter to Monitor' select 'AIDA SYNC'

   Select 'Update Once'

   Check *all* data acquisition servers have a non-zero rate (typically ~300-500Hz)

   See attachment 6

   N.B. If one, or more, data acquisition servers have zero rate

        return to Run Control tab

           stop DAQ (select red STOP button)

           check state of *all* data acquisition servers is 'stopped' with histogramming and
           data transfer are enabled indicated by 'H X'

        start DAQ (select green GO button)

           check state of *all* data acquisition servers is 'going' with histogramming and
           data transfer are enabled indicated by 'H X'

        return to Statistics tab

           check AIDA SYNC rates again and if zero rate persists for one, or more, data acquisition
           servers call for expert help and do *NOT* proceed!

7) Workspace 2 - Firefox web browser - TapeServer tab

   Start TapeServer and open disk file - select green GO button

8) Workspace 2 - Firefox web browser - MERGE tab

   Select 'Reload' several times and check all enabled data links (0-23) are active
         bright green = active, olive green = inactive, red = disabled 

   N.B. If some data links are *always* inactive call for expert help and do NOT proceed!

   Select Toggle Merge Program Pause State to enable data merging 

   Select Reload to observe merge rate (data items/s)

   Observe active spinners in MERGE and TapeServer server terminal windows adjacent to web browser

   See attachment 7

9) Workspace 2 - Firefox web browser - TapeServer tab

   Select Reload and observe number of blocks written to disk

10) Workspace 1 - Firefox web browser - Control tab

    Select 'Save/Restore Settings'

    From 'Save/Restore Module Settings' tab

     select 'Reload'

     select 'Module Names' whose settings should be saved (usually all)

     select 'Generate new DB key' and make a note of the DB key generated
          the DB key will have the format YYYYMMMDD-HH.MM.SS

          The DB key will be used to name a directory to store AIDA settings
          and is created uid: npg, gid: npgstaff, perms 755. However, its
          contents are written uid: nfsnobody, gid nfsnobody. The default
          directory (DB Key) permissions do not work - change the permissions
          to 777 - before attempting to save data to this directory (DB Key).

     launch a terminal and change the permissions of the DB key directory using the command

     chmod 777 /MIDAS/DB/EXPERIMENTS/AIDA/[YYYYMMMDD-HH.MM.SS]

     select 'Save Settings' to save AIDA ASIC, LED and waveform settings to
     the directory (DB key)

11) Update EURICA 2016 Elog with the following information

    AIDA
    run filename (e.g. R99)
    [# data blocks]
    start date & time
    [stop date & time]
    ASIC settings DB key
    AIDA trigger (e.g. OR DSSSDs #1 - #6) 
    additional comments
    your name

    Complete run sheet for written logbook



How to Stop Run

1) Workspace 2 - Firefox web browser - MERGE tab

   Pause MERGE input - select Toggle Merge Program Pause State

2) Workspace 1 - Firefox web browser - Run Control tab

   Select Update

   Stop DAQ - select red STOP button

   Wait (~60s) until state of all data acquisition servers (nnaida1, nnaida2 ... etc) updates 

   Check state of *all* data acquisition servers is 'stopped'

3) Workspace 2 - Firefox web browser - TapeServer tab

   Stop TapeServer and close disk file - select red STOP button

4) Complete EURICA 2016 Elog with the following information

    AIDA
    run filename (e.g. R99)
    [# data blocks]
    start date & time
    [stop date & time]
    ASIC settings DB key
    AIDA trigger (e.g. OR DSSSDs #1 - #6) 
    additional comments
    your name

    Complete run sheet for written logbook




   

1) Start Julabo FL11006 Recirculating Chiller

   See manual (page 19)  http://www2.ph.ed.ac.uk/~td/AIDA/Information/Julabo%20FL11006.pdf 
    
   Set point +20 deg C

   Check flow of coolant by inspecting the two flow indicators the left and right hand sides
   on top of the AIDA stand

   Do NOT proceed if the Julabo FL11006 Recirculating Chiller is not operating, or if there is
   little, or no, flow in one, or both, flow indicators.

2) Start interface to USB-controlled ac mains relay to AIDA data acquisition servers

   On the AIDA Dell T410 Workstation aidas1 switch to Desktop 7 and atart a Firefox web browser
   
   Enter URL   http://nnrpi1:8015/AIDA/Rly16/

   See attachment 1

   Select 'Sequence ALL On' to powerup the AIDA data acquisition servers

   Check all relays Relay 1 to Relay 8 move from the 'Switch ON' to 'Switch OFF' row

   See attachment 2

   Wait 8 minutes (yes - really!) before proceeding

3) Start Httpd Data Acquisition server

   See attachment 3

   Switch to Desktop 1 and select MIDAS yellow icon 'Httpd for DataAcquisition' which will start a terminal
   to display server messages as follows

System identified is CPU x86_64; Platform is unix; OS is Linux and Version is 2.6.32-504.8.1.el6.x86_64
Environment selected is CPU x64_64; Platform unix; OS Linux64 and Operating System Linux64
MIDASBASE = /MIDAS@aidas and MIDAS_LIBRARY = /MIDAS@aidas/TclHttpd/Linux64
PATH =
/MIDAS@aidas/bin_Linux64:/MIDAS@aidas/TclHttpd/Linux64:/homes/npg/root/bin:/homes/npg/root/bin:/homes/npg/root/lib:/MIDAS/Linux/bin64:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin
package limit is not available: can't find package limit
Running with default file descriptor limit
package setuid is not available: can't find package setuid
Could not change to user 50 group 50: not owner
/debug user "debug" password "jhi+u8jzdbpl"
httpd started on port 8015

Custom startup from /MIDAS@aidas/config/TclHttpd/aidas1@8015/startup.tcl
DefineMessage defined with server at http://elog.ph.ed.ac.uk:8015/MessageLoggerServer
/DataBaseAccessServer
/NetVarService
/SigTaskService
Loaded MemSasAccess
/SpectrumService
loading tcl/AIDARunControl.tcl for namespace ::
RunControlClient provided
RunControlClient loaded
Completed custom startup from /MIDAS@aidas/TclHttpd/Html/AIDA/RunControl/stats.defn.tcl

   See attachment 4

4) Start web browser for interface to AIDA

   Switch to Desktop 1 and start Firefox web browser

   Enter URL localhost:8015

   See attachments 5-6

5) Commence startup of AIDA interface

   Select AIDA Experiment Control

6) From AIDA Experiment Control tab 

   See attachment 7

   Select AIDA Hardware Control

   See attachment 8

   Re-select AIDA Experiment Control tab

   Select Data Acquisition Run Control

7) From Data Acquisition Run Control tab

   See attachment 9

   Select Act On ALL Data Acquisition Servers

   See attachment 10

   Select Reset

   Wait for update and check state of *all* data acquisition servers is 'reset'

   Select Setup

   See attachment 11

   Wait for timestamp re-synchronisation pop-up

   See attachment 12

   Usually all data acquisition servers (nnaida1, nnaida2 ... etc) will ReSYNC OK
   Sometimes one, or more, data acquisition servers report ReSYNC not complete

   Re-select AIDA Hardware Control tab and select Master Timestamp Control

   From the Master Timestamp Control tab

   Select Reload

   Select FEE64 -> nnaida6

   Select Perform ReSYNC

   See attachment 13

   Wait for timestamp re-synchronisation pop-up

   See attachments 14-15


   
8) AIDA: Master Timestamp Control

Ditto ReSync

7) Data Acquisition Run Control

8) Spectrum Browser

14.30 DSSSD stack moved upstream to position DSSSD#3 at centre of EURICA.

      Initial tests of detector bias with DSSSD #1-6 were Ok. Unfortunately we were unable to bias
      DSSSD #7 obtaining either open or short circuit depending on which of the two p+n junction 
      side and n+n ohmic side detector bias bus lines we connected to.

      Demonstrated that short circuit was upstream, of AIDA adaptor PCB by disconnecting Kapton
      LH couplers.

      Remove DSSSD stack and replace DSSSD #7. In progress.

15.50 Startup AIDA with DSSSDs disconnected

      Temperatures & firmware version - see attachment 1
      AIDA SYNCs - attachment 2
      System wide checks - attachments 3-6 - note persistent nnaida19 ASIC clock and SYNC errors
      Statistics nnaida19, 20 - attachments 7-8
      
      nnaida19, 20, 27 & 28 hit pattern and waveform spectra - see attachments 9-13

      Some nnaida19 system wide errors above and noisy ASIC#4 hit channel for nnaida28 - otherwise OK 

The latest version of the FEE64 software Interface document ( May 2016 ) is available as a .pdf from
http://npg.dl.ac.uk/documents/edoc000/#AIDA. EDOC955

The version available via the pink "documentation" button in the Control browser window is now out of date. This
will be updated at some future time.

Other documents that are of use are there also.
MACB specification.
GREAT Data Format.

Attached is the specification for the MACB with the settings currently available.

11.45 AIDA discriminator rates - see attachment 1
      Today's rates similar to yesterday's rates 

14.00 Commence positioning of AIDA. Adjust stand height using laser scanner and aligned to wall
      references. Determine that the most forward position AIDA DSSSD#1 is ~3cm downstream of
      EURICA centre. Need to move DSSSDs ~6cm upstream and lengthen DSSSD - AIDA adpptor PCB 
      cabling. In progress.

20.50 Update /etc/dhcp/dhcpd.conf 

      nnaida19 is faulty, nnaida28 is not used - see https://elog.ph.ed.ac.uk/AIDA/193
      We have swapped FEE modules for nnaida19/20 for nnaida27/28 such that nnaida19 -> 28, nnaida20 -> 27,
      nnaida27 -> 19, nnaida28 -> 20. 
      The power cables for nnaida19 and nnaida28 have also been swapped - the power cable to nnaida19
      *might* be faulty as we have experienced problems at this crate position before. Also swapped
      AIDA FEE PSU outlets to ensure pairs of FEE64 cards are powered from the same PSU outlet.
 
[root@aidas1 dhcp]# diff dhcpd.conf dhcpd.conf.BAK-260516
205,206c205,206
<    host nnaida19 {
<      hardware ethernet 00:04:a3:2a:ed:9a;
---
>    host nnaida19 {
>      hardware ethernet 00:04:a3:2b:09:e7;
210,211c210,211
<    host nnaida20 {
<      hardware ethernet 00:04:a3:2b:11:c5;
---
>    host nnaida20 {
>      hardware ethernet 00:04:a3:2b:22:55;
225,226c225,227
<    host nnaida27 {
<      hardware ethernet 00:04:a3:2b:22:55;
---
> # 2 of 2 scratch FEE modules assembled by PJCS April 2016
>    host nnaida27 {
>      hardware ethernet 00:04:a3:2a:ed:9a;
230,232c231,232
< # 2 of 2 scratch FEE modules assembled by PJCS April 2016
<    host nnaida28 {
<      hardware ethernet 00:04:a3:2b:09:e7;
---
>    host nnaida28 {
>      hardware ethernet 00:04:a3:2b:11:c5;
[root@aidas1 dhcp]# cat dhcpd.conf
#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample  
#

authoritative;

ddns-update-style none; ddns-updates off;

max-lease-time 691200;

option domain-search code 119 = string;

subnet 10.1.1.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.1.255;
   option routers 10.1.1.250;
   pool {
      range 10.1.1.100 10.1.1.249;
   }
}

subnet 10.1.2.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.2.255;
   option routers 10.1.2.250;
   pool {
      range 10.1.2.100 10.1.2.249;
   }
}

subnet 10.1.3.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.3.255;
   option routers 10.1.3.250;
   pool {
      range 10.1.3.100 10.1.3.249;
   }
}

subnet 10.1.4.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.4.255;
   option routers 10.1.4.250;
   pool {
      range 10.1.4.100 10.1.4.249;
   }
}

subnet 10.1.5.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option broadcast-address 10.1.5.255;
   option routers 10.1.5.250;
   pool {
      range 10.1.5.100 10.1.5.249;
   }
}

group {
   use-host-decl-names true;
   default-lease-time 3600;
   max-lease-time 14400;

   server-name "10.1.1.250";
   next-server 10.1.1.250;

   host nnrpi1 {
     hardware ethernet b8:27:eb:78:ee:44;
     fixed-address 10.1.1.251;
   }
   host nnaida1 {
     hardware ethernet 00:04:a3:2a:d0:1b;
     fixed-address 10.1.1.1;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida1,tcp";
   }
   host nnaida2 {
     hardware ethernet 00:04:a3:2a:d9:e1;
     fixed-address 10.1.1.2;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida2,tcp";
   } 
   host nnaida5 {
     hardware ethernet 00:04:a3:2a:d0:10;
     fixed-address 10.1.1.5;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida5,tcp";
   }
   host nnaida6 {
     hardware ethernet 00:04:a3:2a:d4:b7;
     fixed-address 10.1.1.6;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida6,tcp";
   }
   host nnaida9 {
     hardware ethernet 00:04:a3:2a:d9:ad;
     fixed-address 10.1.1.9;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida9,tcp";
   }
   host nnaida10 {
     hardware ethernet 00:04:a3:2a:f7:07;
     fixed-address 10.1.1.10;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida10,tcp";
   }
   host nnaida13 {
     hardware ethernet 00:04:a3:2b:11:b9;
     fixed-address 10.1.1.13;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida13,tcp";
   }
   host nnaida14 {
     hardware ethernet 00:04:a3:2b:11:b8;
     fixed-address 10.1.1.14;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida14,tcp";
   }
   host nnaida17 {
     hardware ethernet 00:04:a3:2a:d9:cc;
     fixed-address 10.1.1.17;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida17,tcp";
   }
   host nnaida18 {
     hardware ethernet 00:04:a3:2a:b2:b2;
     fixed-address 10.1.1.18;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida18,tcp";
   }
   host nnaida21 {
     hardware ethernet 00:04:a3:2b:27:23;
     fixed-address 10.1.1.21;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida21,tcp";
   }
   host nnaida22 {
     hardware ethernet 00:04:a3:2a:f6:e9;
     fixed-address 10.1.1.22;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida22,tcp";
   }
   host nnaida25 {
     hardware ethernet 00:04:a3:2a:d0:11;
     fixed-address 10.1.1.25;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida25,tcp";
   }
   host nnaida26 {
     hardware ethernet 00:04:a3:2b:27:54;
     fixed-address 10.1.1.26;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida26,tcp";
   }
   host nnaida29 {
     hardware ethernet 00:04:a3:2a:d0:06;
     fixed-address 10.1.1.29;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida29,tcp";
   }
   host nnaida30 {
     hardware ethernet 00:04:a3:2a:d9:b6;
     fixed-address 10.1.1.30;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida30,tcp";
   }


}


group {
   use-host-decl-names true;
   default-lease-time 3600;
   max-lease-time 14400;

   server-name "10.1.2.250";
   next-server 10.1.2.250;

   host nnaida3 {
     hardware ethernet 00:04:a3:2a:f7:06;
     fixed-address 10.1.2.3;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida3,tcp";
   }
   host nnaida4 {
     hardware ethernet 00:04:a3:2a:ed:b8;
     fixed-address 10.1.2.4;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida4,tcp";
   }
   host nnaida7 {
     hardware ethernet 00:04:a3:2a:b8:8d;
     fixed-address 10.1.2.7;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida7,tcp";
   }
   host nnaida8 {
     hardware ethernet 00:04:a3:2a:9c:07;
     fixed-address 10.1.2.8;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida8,tcp";
   }
   host nnaida11 {
     hardware ethernet 00:04:a3:2b:11:af;
     fixed-address 10.1.2.11;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida11,tcp";
   }
   host nnaida12 {
     hardware ethernet 00:04:a3:2a:d0:2f;
     fixed-address 10.1.2.12;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida12,tcp";
   }
   host nnaida15 {
     hardware ethernet 00:04:a3:2a:f3:ac;
     fixed-address 10.1.2.15;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida15,tcp";
   }
   host nnaida16 {[root@aidas1 aidas1]# diff startup.tcl startup.tcl.BAK-260516
31,32c31,32
<     variable PACQSERVERS; set PACQSERVERS { nnaida1 nnaida2 nnaida5 nnaida6  nnaida9 nnaida10 nnaida13
nnaida14 nnaida17 nnaida18 nnaida21 nnaida22 nnaida25 nnaida26 nnaida29 nnaida30 }
<     variable NACQSERVERS; set NACQSERVERS { nnaida3 nnaida4 nnaida7 nnaida8 nnaida11 nnaida12 nnaida15
nnaida16 nnaida19 nnaida20 nnaida23 nnaida24 nnaida27 nnaida28 nnaida31 nnaida32 }
---
>     variable PACQSERVERS; set PACQSERVERS { nnaida1 nnaida2 nnaida5 nnaida6  nnaida9 nnaida10 nnaida13
nnaida14 nnaida17 nnaida18 nnaida21 nnaida22 nnaida25 nnaida29 nnaida30 }
>     variable NACQSERVERS; set NACQSERVERS { nnaida3 nnaida4 nnaida7 nnaida8 nnaida11 nnaida12 nnaida15
nnaida16 nnaida20 nnaida23 nnaida24 nnaida27 nnaida28 nnaida31 nnaida32 }
33a34
> # startup.tcl.BAK-130516 has all 32 NNAIDA modules included
52c53
<     lappend ACQSERVERS nnaida19
---
> #    lappend ACQSERVERS nnaida19
59c60
<     lappend ACQSERVERS nnaida26
---
> #    lappend ACQSERVERS nnaida26

     hardware ethernet 00:04:a3:2a:9c:0e;
     fixed-address 10.1.2.16;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida16,tcp";
   }
# 1 of 2 scratch FEE modules assembled by PJCS April 2016
   host nnaida19 {
     hardware ethernet 00:04:a3:2a:ed:9a;
     fixed-address 10.1.2.19;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida19,tcp";
   }
   host nnaida20 {
     hardware ethernet 00:04:a3:2b:11:c5;
     fixed-address 10.1.2.20;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida20,tcp";
   }
   host nnaida23 {
     hardware ethernet 00:04:a3:2a:b8:90;
     fixed-address 10.1.2.23;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida23,tcp";
   }
   host nnaida24 {
     hardware ethernet 00:04:a3:2a:b6:45;
     fixed-address 10.1.2.24;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida24,tcp";
   }
   host nnaida27 {
     hardware ethernet 00:04:a3:2b:22:55;
     fixed-address 10.1.2.27;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida27,tcp";
   }
# 2 of 2 scratch FEE modules assembled by PJCS April 2016
   host nnaida28 {
     hardware ethernet 00:04:a3:2b:09:e7;
     fixed-address 10.1.2.28;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida28,tcp";
   }
   host nnaida31 {
     hardware ethernet 00:04:a3:2b:11:ae;
     fixed-address 10.1.2.31;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida31,tcp";
   }
   host nnaida32 {
     hardware ethernet 00:04:a3:2a:ed:b9;
     fixed-address 10.1.2.32;
     option root-path "/MIDAS@aidas/XilinxLinux/ppc_4xx/rfs/nnaida32,tcp";
   }
}


group {
# 8 days
   default-lease-time 691200;

#    option dhcp-client-identifier "\0foo";

   host nndhcp052 {
# Analysis server
     hardware ethernet 00:22:19:50:02:40;
     fixed-address 10.1.1.252;
   }

}


DAQ server configuration file /MIDAS/config/TclHttpd/aidas1/startup.tcl update - see attachment 2

[root@aidas1 aidas1]# diff startup.tcl startup.tcl.BAK-260516
31,32c31,32
<     variable PACQSERVERS; set PACQSERVERS { nnaida1 nnaida2 nnaida5 nnaida6  nnaida9 nnaida10 nnaida13
nnaida14 nnaida17 nnaida18 nnaida21 nnaida22 nnaida25 nnaida26 nnaida29 nnaida30 }
<     variable NACQSERVERS; set NACQSERVERS { nnaida3 nnaida4 nnaida7 nnaida8 nnaida11 nnaida12 nnaida15
nnaida16 nnaida19 nnaida20 nnaida23 nnaida24 nnaida27 nnaida28 nnaida31 nnaida32 }
---
>     variable PACQSERVERS; set PACQSERVERS { nnaida1 nnaida2 nnaida5 nnaida6  nnaida9 nnaida10 nnaida13
nnaida14 nnaida17 nnaida18 nnaida21 nnaida22 nnaida25 nnaida29 nnaida30 }
>     variable NACQSERVERS; set NACQSERVERS { nnaida3 nnaida4 nnaida7 nnaida8 nnaida11 nnaida12 nnaida15
nnaida16 nnaida20 nnaida23 nnaida24 nnaida27 nnaida28 nnaida31 nnaida32 }
33a34
> # startup.tcl.BAK-130516 has all 32 NNAIDA modules included
52c53
<     lappend ACQSERVERS nnaida19
---
> #    lappend ACQSERVERS nnaida19
59c60
<     lappend ACQSERVERS nnaida26
---
> #    lappend ACQSERVERS nnaida26

Need to update nnaida19 and nnaida26 to latest firmware version - see https://elog.ph.ed.ac.uk/AIDA/237

The attached firmware file, FEE_GF_Feb16_18.bin, should be saved to /MIDAS/Aida and the FlashPgm.csh file edited
to load "FEE_GF_Feb16_18.bin"

Use the Run Control Expert command to update the firmware on all the FEE64s.

Power cycle the FEE64s to load the new firmware.

Make a backup copy of the files in the directory /MIDAS/TclHttpd/Html/AIDA/DISC.

Unzip the files from DISC_25May16.zip and copy them into /MIDAS/TclHttpd/Html/AIDA/DISC to replace the existing
ones.

Make a backup copy of the file /MIDAS/TclHttpd/Html/AIDA/LOCAL.tml

Unzip the file from LOCAL_tml_25May16.zip and copy into /MIDAS/TclHttpd/Html/AIDA/LOCAL to replace the existing
file.

'RESET' and browser refresh the two updated control windows to load the new software.
-----------------------------------------------------

To use the Multiplicity Trigger:-
In the Local Controls select option 5 for the Trigger.

In the Discriminator window.

Set the 'Upper Limit'
Set the 'Lower Limit' ( always greater than 0 ..... or the Trigger will always be present )
Set the 'Time window'. The number of 10nS clocks. So 4 => 40nS. Register is 0 to 255.

-----------------------------------------------------

These registers are not in the Save/Restore set yet.

Tested on the T9 system using the pulser and setting/clearing Mask bits.

Please let me know how this works for you.

Done. Awaiting test. See attachments 1-2.

> The attached firmware file, FEE_GF_Feb16_18.bin, should be saved to /MIDAS/Aida and the FlashPgm.csh file edited
> to load "FEE_GF_Feb16_18.bin"
> 
> Use the Run Control Expert command to update the firmware on all the FEE64s.
> 
> Power cycle the FEE64s to load the new firmware.
> 
> Make a backup copy of the files in the directory /MIDAS/TclHttpd/Html/AIDA/DISC.
> 
> Unzip the files from DISC_25May16.zip and copy them into /MIDAS/TclHttpd/Html/AIDA/DISC to replace the existing
> ones.
> 
> Make a backup copy of the file /MIDAS/TclHttpd/Html/AIDA/LOCAL.tml
> 
> Unzip the file from LOCAL_tml_25May16.zip and copy into /MIDAS/TclHttpd/Html/AIDA/LOCAL to replace the existing
> file.
> 
> 'RESET' and browser refresh the two updated control windows to load the new software.
> -----------------------------------------------------
> 
> To use the Multiplicity Trigger:-
> In the Local Controls select option 5 for the Trigger.
> 
> In the Discriminator window.
> 
> Set the 'Upper Limit'
> Set the 'Lower Limit' ( always greater than 0 ..... or the Trigger will always be present )
> Set the 'Time window'. The number of 10nS clocks. So 4 => 40nS. Register is 0 to 255.
> 
> -----------------------------------------------------
> 
> These registers are not in the Save/Restore set yet.
> 
> Tested on the T9 system using the pulser and setting/clearing Mask bits.
> 
> Please let me know how this works for you.

10.05 Recirculating chiller on
      FEE power on
      Detector bias on - ambient temp +23 deg  C - see attachments 1-2

20.30 Noisy fast discriminator channels masked in all nnaida to bring 'AIDA discriminator' rate to <~5kHz.
      Slow and fast comparator thresholds at 16 (decimal).
      Settings saved to 2016May14-13.57.38 DB key.

The USB controlled power Relays are near their AC fuse operating limit which has caused some Fuse failures.
To reduce the power consumption of each FEE64 it is possible to power down the Waveforms ADCs saving about 20W per FEE64. 

To Powerdown the ADCs in a FEE64 use the 'Local Data' browser window from the 'Control' browser window. Change the setting of the ADC Control 
Register at offset 2 from 0 to 0xFF. All the FEE64s can be thus controlled by using the 'Act on all' tick box.
Clearly, the System Check for ADC calibration will now fail for all those that are powered down.

To Power up the ADCs change the setting from 0xFF to 0. Then using the FADC Calibration browser window calibrate the FADCs. 

The SYSTEM should be in the 'STOP' state during these procedures.

Should the SYSTEM be power cycled then the ADCs will be powered up.

Saving at the 16A AC fuse is estimated to be 3A as there are 16 FEE64 being powered through each.

The 3x WDC WD30EFRX ATA 3Tb disks installed in aidas1 in April 2015 (formerly /data20, /data30 and
/data40) have now been added to the aidas1 logical volume management (LVM) configuration to form a
single c. 8Tb filesystem (/data10) which will be automatically mounted at boot.

N.B. Although the disks are 3Tb capacity, Linux OS/BIOS can only access the first 2.2Tb of each disk.

Data previously stored on /data20, /data30 and /data40 has been copied to the local Seagate USB 8Tb
disk (/ntfs) and the University of Edinburgh ECDF multi-Pb disk array.

aidas1> df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_aidas1-lv_root
                       50G   27G   20G  58% /
tmpfs                 3.9G  1.1M  3.9G   1% /dev/shm
/dev/sdb1             477M   77M  376M  17% /boot
/dev/mapper/vg_aidas1-lv_home
                      860G  106M  816G   1% /home
/dev/mapper/Data1-data10
                      7.7T  1.6T  5.8T  22% /data10
/dev/sda2             7.3T  3.4T  4.0T  46% /ntfs

[root@aidas1 /]# ln -s /data10/TapeData /TapeData
[root@aidas1 /]# ls -l /
total 210
dr-xr-xr-x.   2 root root      4096 Apr  7 03:49 bin
dr-xr-xr-x.   5 root root      1024 Feb 17  2015 boot
drwxr-xr-x.  10 root root      4096 Jul 23  2015 cgroup
drwxr-xr-x.   8 root root      4096 Dec 12 19:29 data10
drwxr-xr-x.   2 root root      4096 Apr 28  2015 data20
drwxr-xr-x.   2 root root      4096 Apr 28  2015 data30
drwxr-xr-x.   2 root root      4096 Apr 28  2015 data40
drwxr-xr-x.  21 root root      4500 May 24 14:40 dev
drwxr-xr-x. 135 root root     12288 May 24 17:55 etc
drwxr-xr-x.   4 root root      4096 Apr 28  2015 home
drwxr-xr-x.   4 root root      4096 Jan  8  2014 homes
dr-xr-xr-x.  13 root root      4096 Feb 18 03:19 lib
dr-xr-xr-x.  11 root root     12288 Apr 14 06:02 lib64
drwx------.   2 root root     16384 Jan  7  2014 lost+found
drwxr-xr-x.   2 root root      4096 May 24 11:00 media
lrwxrwxrwx.   1 root root        12 Apr 22  2014 MIDAS -> /MIDAS@aidas
drwxrwxr-x.  29 npg  npgstaff  4096 May  3 23:47 MIDAS@aidas
drwxr-xr-x.  22 root root      4096 Dec 12 12:10 MIDAS@aidas.121215
drwxr-xr-x.  28 root root      4096 Feb 24  2015 MIDAS@aidas.240215
drwxr-xr-x.   2 root root         0 May 24 11:00 misc
drwxr-xr-x.   2 root root      4096 Jul 21  2011 mnt
drwxr-xr-x.   2 root root         0 May 24 11:00 net
drwxrwxrwx.   1 root root      4096 Apr 28 10:55 ntfs
drwxr-xr-x.   4 root root      4096 Feb 27  2014 opt
dr-xr-xr-x. 411 root root         0 May 24 10:58 proc
dr-xr-x---.  28 root root      4096 May 24 18:01 root
drwxr-xr-x.   2 root root     12288 Feb 18 03:19 sbin
dr-xr-xr-x.   2 root root      4096 Feb 27  2014 scratch
drwxr-xr-x.   7 root root         0 May 24 10:58 selinux
drwxr-xr-x.   2 root root      4096 Jul 21  2011 srv
drwxr-xr-x.  13 root root         0 May 24 10:58 sys
lrwxrwxrwx.   1 root root        16 May 24 18:02 TapeData -> /data10/TapeData
drwxrwxrwt.  41 root root     65536 May 24 18:01 tmp
drwxr-xr-x.  13 root root      4096 Jan  7  2014 usr
drwxr-xr-x.  23 root root      4096 Jan  7  2014 var
dr-xr-xr-x.   2 root root      4096 Feb 27  2014 WWW

Attachments 1-30 per FEE64 ASIC #1 waveforms

Note - nnaida19 and nnaida26 disabled
       nnaida11, nnaida17 and nnaida29 ADC calibration failed => no waveforms

Overnight. DAQ stopped. Detector bias off. FEE power and recirculating chiller on.

08.00 Detector bias on OK - see attachments 1-2
      DAQ start OK - see attachments 3-4
      All system-wide tests OK *except* nnaida9 and nnaida29 failed ADC calibration
      Temperatures OK 

18.00 Saved corrected ASIC settings to DB Key 2016May14-13.57.38
      Changed options - nnaida5 master timestamp sync phase from 0x1 to 0x3 

When starting Aida some FEE64 fail to provide SYNC data , or any data for that matter, on the ASIC data stream.
The problem is that the ASIC Readout is not starting properly and is becoming stuck waiting for an internal
event which will never arrive.
The chief source has been found to be the Correlation part of the VHDL. The reason is not yet clear but the work
around of disabling the Correlation part of all of the FEE64 at 'GO' except the Master has allowed the System to
start with all FEE64 producing SYNCs. 

This change is now incorporated in the sys.tcl file which is used when 'GO' is activated in the RunControl window.

The Master is required as it provides the 25Mhz clock and the Reset pulse. The Correlation Trigger will cause a
correlation data item to be put in the Master ASIC data stream.
Only one Correlation data item is required in the data stream, so having just the Master should be fine.

If it is required to enable another FEE64 then do this after 'GO' by opening the Correlation Browser window from
the Control window and set the Control ( at offset 0 ) to 0x0001.

Should one of the FEE64s still fail to provide SYNCs first try to 'STOP' , 'GO' the system two times and see
if that works.

A further means of correcting the problem is to directly reset the ASIC Readout using the Data Readout Window
available through the Control window. In the ASIC Readout - buffer status & control (0x300) section enter 0x4000
into the Control register to reset the state machines. Then enter 0x0001 to re-enable them. This may solve the
problem.

This is all by no means an ideal situation and the source will be found and the problem solved.

Please read and comment on the attached specification.