--------------------------------------------------------------------------------
                      VME_Access Version 5.0 Release Notes
                          -------------------------

22-APR-2003: (Rev C)

Gneral

  Big change is switching to Memory Mapped IO for a factor x10 in speed 
  improvement.

  It turned out to be a factor of x20 because the former API method was
  actually doing an extra call after each IO to verify the status of 
  the bit3 adapter, which seems to take as long as an IO.

  Find_DAC used to take 29.5s per Pedstal using Option #2,
  while it now takes 1.2s per Trigger Tower Pedestal.


All Comamnd Files

  Add new Keywords "Error_Tag:", "Warning_Tag:" and "Info_Tag:" accepted
  in all types of command file.

  This keyword must be followed by a string within double quotes. e.g.
  Error_Tag: "Pedestal Control Value Not Found  for EM_TT(+ 1, 1)"

  When Trics executes a command file and encounters such keyword it will print 
  the content of the associated string to the console screen. e.g. 
  E$ Error_Tag: <Failed Finding Pedestal Control Value for EM_TT(+ 9,21)>, at Line #304

  "Error_Tag:" will generate an error line, in red.
  "Warning_Tag:" will generate a warning line, in bright white.
  "Info_Tag:" will generate an info line, in normal white.


Find_DAC 

  Enter failures to find a satisfactory pedestal control values as an "Error_Tag:"
  line in the Find_DAC TTI result file.  This file will thus be directly
  executable by Trics V10.4.A, or VME_Access V5.0.C or later versions.
  Executing a Find_DAC TTI result file will thus generate red error lines 
  on the console screen unless the operator edits the file and decides to 
  accept or modify the proposed control value.  The operator can then add
  a comment flag "!" in front of "Error_Tag:" to remove the error message.

  Find_DAC leaves the Trigger Tower programmed with the selected control value
  when it is successful.  Find_DAC programs the pedestal control DAC with the 
  maximum control value in case of failure, which will produce a Zero Energy
  response of 0 counts, e.g. in TT_ADC_Trigmon.

  Change the value writen as "Ped_Deviation:" in the TTI Result file to be the
  average of standard deviation of the 26 histograms built by Find_DAC (instead 
  of the standard deviation of the chosen histogram, which now appears in the
  comment at the end of the line). e.g. 
  TT_Phi:  1  Pedestal_Control_DAC: 3522  Ped_Average: 8.00  Ped_Deviation: 0.99
    ! EM_TT(+ 1, 1)  Selected_Histo_Dev: 0.96

  Loosen the requirement of the best histogram to only be within 0.15 ADC count
  of the target Zero Energy Response instead of the previous value of 0.1.


Find_DAC Result Analysis Tools

  The Analysis of Find_DAC results now writes the total number of reported
  errors.

--------------------------------------------------------------------------------
                      VME_Access Version 4.1 Release Notes
                          -------------------------

6-MAR-2003: (Rev D)

Find_DAC 

  Fix inversion of the MTG bit2 Pal Control Register Read Mask vs Write mask.

  Find_DAC de-excludes all trigger towers on the mother CTFE card before 
  starting and leaves all trigger towers NOT excluded when done.
  
  Control of Read/Write Pipe during Find_DAC:
  Implement user option to control the Read/Write Pipe to freeze each pipeful 
  of 29525 data while reading histogram values from these stable snapshots.  

  The user can select how many samples are kept from each pipeful.  The most
  recent sample is always rejected, because switching of the write pipe by Trics
  is not synchronized with L1CT operation and the last sample may be corrupted.

  The user can elect to keep every crossing (Option #1), every other crossing 
  (Option #2), or every third/fourth/fifth/sixth/seventh (Option #3/4/5/6/7).  
  The histograming automatically adjusts the number of pipeful needed to collect 
  the required number of samples per histogram.   The legacy mode of not
  controlling the Read and Write Pipes corresponds to Option #0.

  In the Option #0 mode Trics keep both Read/Write pipes always aimed at Pipe_A.
  In  all modes except option #0 Trics holds the Read_Pipe to Pipe_B, and keeps
  the Write_Pipe to Pipe_B only while filling the pipe with fresh information, 
  and switches the Write_Pipe to Pipe_A while reading frozen data from Pipe_B.

  Option#     Use Pipe     Keep Tot    Approx Approx
  Keep      Slice Number   Per  Pipe   Time/  Time per TT
  Every   0 1 2 3 4 5 6 7  Pipe Switch Histo  using API

    0     - - - - - - - -  -       -   0.13s  7.8s      Does not freeze pipes
    1     . Y Y Y Y Y Y Y  7     143   0.36s  ~20s      Keep every slice
    2     . Y . Y . Y . Y  4     250   0.49s  29.5      Keep every other slice
    3     . Y . . Y . . Y  3     334                    Keep every third slice
    4     . Y . . . Y . .  2     500                    Keep every fourth slice
    5     . Y . . . . Y .  2     500                    Keep every fifth slice
    6     . Y . . . . . Y  2     500                    Keep every sixth slice
    7     . Y . . . . . .  1    1000                    Keep only one slice

  Add a sanity check while scanning through successive values of Pedestal 
  control DAC and building histogram: verify that the average is no more
  than 2 counts away from the target zeresp.  This is not a tight requirement,
  but it would detect a hard failure during the programming of the Serial DACs.


--------------------------------------------------------------------------------
                      VME_Access Version 4.0 Release Notes
                          -------------------------

7-FEB-2003: (Rev B)

Switch to ITC V02-20-00

Find_DAC (and this is also part of VME_Access V4.0)

  Drop the ability to run Find_DAC on the legacy Run I CTFE front-end.

  Rework the search algorithm which was until now a simple port of Run I code.

  Find_DAC will now follow these steps:

  1a) Set the DAC Control value to zero -> push ADC zeresp up to full scale
  1b) Take a 100 Sample Histogram and verify that the average > 254.0

  2a) Set the DAC Control value to full scale -> push ADC zeresp down to zero
  2b) Take a 100 Sample Histogram and verify that the average < 1.0

  3a) Set the DAC Control value to mid-scale -> set ADC zeresp to mid range
  3b) Take a 1,000 Sample Histogram and verify average is within [0x70:0x90]

  4a) Using the average from (3b) and the typical 13.1 DAC to ADC ratio compute
      and set an DAC control value to produce a Zeresp of 20.
  4b) Bail out if computed DAC control value was out of range
  4c) Take a 1,000 Sample Histogram 
  4d) Compute and Verify that measured DAC to ADC ratio is within 0.5 of 13.1
  4e) Bail out if couldn't compute DAC to ADC ratio

  5a) Using the Average from (4c) and the DAC to ADC ratio from (4d) compute
      and set an ADC control to produce a Zeresp of ~7.5 
  5b) Bail out if computed DAC control value was out of range
  5c) Take 26x successive 1,000 Sample Histograms by decrementing the ADC 
      control value.  We should thus cover Averages between 7.0 and 9.0
  5d) While capturing these histograms remember which histogram had the 
      average closest to the target value zeresp of 8 counts.
      The code for instead picking the histogram with highest population 
      for bin[8] is also there but turned off by a compiler flags.
  5e) complain if the histogram selected was the first or last one
      complain if the average of the selected histogram is not within 0.1 
      of the target value.
      Either complaint is an error and will be flagged in the TTI and HST files.
      Find_DAC still writes a Pedestal_DAC line in the TTI file.
      The user will have to go edit the file and deal with the error.

  6a) Set the DAC control value to the value chosen in (5d)
      or with the max control value -> lowest Zeresp -> stand out in TT_ADCmon
  6b) Report the DAC control value, and the corresponding Average and Std Dev.
  6c) Also report the Average of the Std Dev of the 13 Histograms as this
      number should be more stable because of higher statistics and because
      we covered all smearing patterns caused by quantization boundaries.
      We will use this Std Dev average number (6c) in the TTI report, which 
      will bevisible to the Find_DAC analysis tools.  We will also report the
      actual Std Dev (6b) of the selected histograms in the TTI file, 
      as comment, and for reference.
  

  Below are simulated examples (not real DAC or real noise but software model).

  This would be the screen report if one doesn't ask for a Histogram File:

  I$Now Processing EM_TT(+ 1, 1)                                            
  I$Computed DAC to ADC ratio = 13.11                                       
  I$EM_TT(+ 1, 1) Picked Histo# 7 DAC= 3529 Avr= 7.98 Dev= 0.98 DevAvr= 0.99
  I$                                                                           

  This would be the screen report if one elects to write a Histogram File:

  I$Now Processing EM_TT(+ 1, 1)                                                
  I$ DAC=    0 -> Avr=255.00 Dev= 0.00 ( 100@255 )                              
  I$ DAC= 4095 -> Avr=  0.00 Dev= 0.00 ( 100@0 )                                
  I$ DAC= 2054 -> Avr=119.97 Dev= 0.94 ( 87@118 127@119 579@120 142@121 65@122 )
  I$ DAC= 3364 -> Avr= 20.02 Dev= 0.91 ( 69@18 123@19 601@20 135@21 72@22 )     
  I$Computed DAC to ADC ratio = 13.11                                           
  I$ DAC= 3535 -> Avr=  7.50 Dev= 1.01 ( 38@5 89@6 360@7 397@8 83@9 33@10 )     
  I$ DAC= 3534 -> Avr=  7.70 Dev= 1.03 ( 30@5 88@6 227@7 506@8 101@9 48@10 )    
  I$ DAC= 3533 -> Avr=  7.78 Dev= 1.01 ( 24@5 88@6 177@7 554@8 105@9 52@10 )    
  I$ DAC= 3532 -> Avr=  7.82 Dev= 0.98 ( 22@5 78@6 172@7 561@8 118@9 49@10 )    
  I$ DAC= 3531 -> Avr=  7.91 Dev= 0.99 ( 15@5 73@6 159@7 563@8 118@9 72@10 )    
  I$ DAC= 3530 -> Avr=  7.92 Dev= 0.97 ( 9@5 81@6 146@7 577@8 119@9 68@10 )     
  I$ DAC= 3529 -> Avr=  7.98 Dev= 0.98 ( 4@5 80@6 143@7 569@8 117@9 87@10 )     
  I$ DAC= 3528 -> Avr=  8.03 Dev= 0.94 ( 78@6 114@7 587@8 147@9 72@10 2@11 )    
  I$ DAC= 3527 -> Avr=  8.07 Dev= 0.93 ( 61@6 115@7 611@8 128@9 78@10 7@11 )    
  I$ DAC= 3526 -> Avr=  8.15 Dev= 0.97 ( 56@6 108@7 585@8 153@9 81@10 17@11 )   
  I$ DAC= 3525 -> Avr=  8.21 Dev= 0.98 ( 48@6 112@7 547@8 193@9 80@10 20@11 )   
  I$ DAC= 3524 -> Avr=  8.23 Dev= 0.98 ( 51@6 100@7 540@8 203@9 89@10 17@11 )   
  I$ DAC= 3523 -> Avr=  8.35 Dev= 1.05 ( 43@6 99@7 504@8 214@9 104@10 36@11 )   
  I$ DAC= 3522 -> Avr=  8.47 Dev= 1.06 ( 46@6 95@7 364@8 362@9 99@10 34@11 )    
  I$ DAC= 3521 -> Avr=  8.74 Dev= 1.05 ( 34@6 83@7 214@8 500@9 116@10 53@11 )   
  I$ DAC= 3520 -> Avr=  8.82 Dev= 1.00 ( 21@6 87@7 163@8 568@9 101@10 60@11 )   
  I$ DAC= 3519 -> Avr=  8.82 Dev= 1.02 ( 17@6 88@7 192@8 535@9 98@10 70@11 )    
  I$ DAC= 3518 -> Avr=  8.88 Dev= 0.93 ( 11@6 74@7 153@8 600@9 105@10 57@11 )   
  I$ DAC= 3517 -> Avr=  8.96 Dev= 0.91 ( 5@6 69@7 144@8 585@9 139@10 58@11 )    
  I$ DAC= 3516 -> Avr=  8.99 Dev= 0.96 ( 3@6 75@7 135@8 588@9 110@10 89@11 )    
  I$ DAC= 3515 -> Avr=  9.04 Dev= 0.97 ( 73@7 130@8 577@9 128@10 86@11 6@12 )   
  I$ DAC= 3514 -> Avr=  9.05 Dev= 0.97 ( 79@7 117@8 571@9 152@10 73@11 8@12 )   
  I$ DAC= 3513 -> Avr=  9.15 Dev= 0.97 ( 55@7 106@8 597@9 140@10 84@11 18@12 )  
  I$ DAC= 3512 -> Avr=  9.16 Dev= 0.94 ( 50@7 105@8 585@9 165@10 85@11 10@12 )  
  I$ DAC= 3511 -> Avr=  9.28 Dev= 1.02 ( 44@7 103@8 542@9 182@10 100@11 29@12 ) 
  I$ DAC= 3510 -> Avr=  9.36 Dev= 1.02 ( 34@7 108@8 491@9 230@10 109@11 28@12 ) 
  I$EM_TT(+ 1, 1) Picked Histo# 7 DAC= 3529 Avr= 7.98 Dev= 0.98 DevAvr= 0.99    
  I$                                                                           
  
  This would be the typical entry in the .TTI file (the line has been wrapped around)
  
  TT_Phi:  1  Pedestal_Control_DAC: 3529  Ped_Average: 7.98  Ped_Deviation: 0.98  
    ! EM_TT(+ 1, 1)  Dev_Average: 0.99
  
  This would be the typical entry in the .HST file 
  
Now Processing EM_TT(+ 1, 1)
 DAC=    0 -> Avr=255.00 Dev= 0.00 ( 100@255 )
 DAC= 4095 -> Avr=  0.00 Dev= 0.00 ( 100@0 )
 DAC= 2054 -> Avr=119.99 Dev= 0.94 ( 78@118 134@119 586@120 123@121 79@122 )
 DAC= 3364 -> Avr= 20.00 Dev= 0.97 ( 87@18 121@19 580@20 128@21 84@22 )
Computed DAC to ADC ratio = 13.10
 DAC= 3534 -> Avr=  7.53 Dev= 1.05 ( 42@5 84@6 354@7 378@8 107@9 35@10 )
 DAC= 3533 -> Avr=  7.73 Dev= 1.00 ( 29@5 80@6 211@7 534@8 104@9 42@10 )
 DAC= 3532 -> Avr=  7.77 Dev= 0.99 ( 21@5 88@6 192@7 542@8 111@9 46@10 )
 DAC= 3531 -> Avr=  7.79 Dev= 0.97 ( 18@5 90@6 175@7 565@8 107@9 45@10 )
 DAC= 3530 -> Avr=  7.89 Dev= 0.94 ( 11@5 81@6 136@7 605@8 111@9 56@10 )
 DAC= 3529 -> Avr=  7.93 Dev= 1.01 ( 12@5 87@6 143@7 556@8 125@9 77@10 )
 DAC= 3528 -> Avr=  8.00 Dev= 1.00 ( 5@5 91@6 115@7 553@8 159@9 77@10 )
 DAC= 3527 -> Avr=  8.01 Dev= 0.94 ( 79@6 122@7 583@8 139@9 76@10 1@11 )
 DAC= 3526 -> Avr=  8.05 Dev= 0.93 ( 63@6 127@7 592@8 141@9 70@10 7@11 )
 DAC= 3525 -> Avr=  8.10 Dev= 0.96 ( 62@6 121@7 571@8 158@9 79@10 9@11 )
 DAC= 3524 -> Avr=  8.17 Dev= 0.96 ( 49@6 113@7 571@8 168@9 83@10 16@11 )
 DAC= 3523 -> Avr=  8.19 Dev= 1.01 ( 55@6 106@7 567@8 170@9 73@10 29@11 )
 DAC= 3522 -> Avr=  8.29 Dev= 1.02 ( 39@6 122@7 494@8 226@9 89@10 30@11 )
 DAC= 3521 -> Avr=  8.46 Dev= 1.03 ( 35@6 107@7 376@8 364@9 82@10 36@11 )
 DAC= 3520 -> Avr=  8.74 Dev= 0.97 ( 20@6 87@7 207@8 542@9 104@10 40@11 )
 DAC= 3519 -> Avr=  8.79 Dev= 0.97 ( 14@6 99@7 172@8 553@9 121@10 41@11 )
 DAC= 3518 -> Avr=  8.90 Dev= 1.00 ( 13@6 70@7 191@8 533@9 119@10 74@11 )
 DAC= 3517 -> Avr=  8.91 Dev= 0.97 ( 13@6 83@7 128@8 595@9 119@10 62@11 )
 DAC= 3516 -> Avr=  8.89 Dev= 0.93 ( 5@6 90@7 135@8 604@9 107@10 59@11 )
 DAC= 3515 -> Avr=  8.98 Dev= 0.95 ( 3@6 80@7 132@8 583@9 125@10 77@11 )
 DAC= 3514 -> Avr=  9.05 Dev= 0.95 ( 67@7 135@8 573@9 136@10 86@11 3@12 )
 DAC= 3513 -> Avr=  9.09 Dev= 0.95 ( 66@7 114@8 576@9 158@10 81@11 5@12 )
 DAC= 3512 -> Avr=  9.08 Dev= 0.93 ( 56@7 126@8 595@9 135@10 81@11 7@12 )
 DAC= 3511 -> Avr=  9.28 Dev= 1.04 ( 51@7 105@8 516@9 202@10 98@11 28@12 )
 DAC= 3510 -> Avr=  9.19 Dev= 0.98 ( 54@7 99@8 571@9 178@10 74@11 24@12 )
 DAC= 3509 -> Avr=  9.30 Dev= 1.00 ( 34@7 115@8 516@9 215@10 90@11 30@12 )
EM_TT(+ 1, 1) Picked Histo# 7 DAC= 3528 Avr= 8.00 Dev= 1.00 DevAvr= 0.98

  These are the control parameters that we can adjust to tighten or loosen
  the above requirements:
  
      /////////////////////////////////////////////
      //Search parameters
      /////////////////////////////////////////////
  
  #define KfDacToAdcRatioTyp               13.1  
          // Increasing the DAC by +13 increases the Zeresp by +1 
  #define KfDacToAdcRatioOkDiff             0.5  
          // Accepted Difference between Calculated and Typical DAC to ADC ratio
  
  #define KiManyTimeConst                     2  
          // 2 ms = many times the time const (~20 us)
  
  #define KiDacMinValue                       0  
          // should produce a High Zeresp of 0xff
  #define KiDacMaxValue                    4095  
          // should produce a Low Zeresp of 0x00
  #define KiDacMidValue                    2054  
          // should produce a Mid-range Zeresp around half scale
  
  #define KfZerespHighOk                  254.0  
          // lowest value acceptable for High Zeresp
  #define KfZerespLowOk                     1.0  
          // highest value acceptable for a Low Zeresp
  
  #define KiZerespMidOkLow                 0x70  
          // lowest value acceptable for mid range Zeresp
  #define KiZerespMidOkHigh                0x90  
          // highest value acceptable for mid range Zeresp
  
  #define KfZerespLow                      20.0  
          // First targeted Low Zeresp to compute DAC to ADC ratio
  
  #define KiTotHistoScanned                  26  
          // How many histograms will be built around the target zeresp
  #define KfZerespDiffOk                    0.1  
          // How close to the target zeresp the best histogram needs to be
  
  #define KiSmallSampleSize                 100  
          // Small Histogram Sample Size (for checking 0x00 and 0xff rails)
  #define KiLargeSampleSize                1000  
          // Large Histogram Sample Size (for everything else)
  
  //#define PICK_BEST_POPULATION
  #define PICK_BEST_AVERAGE
  

  The result file used to write in comment fields the selected Pedestal 
  Average and Standard Deviation.
  e.g. TT_Phi:  1    Pedestal_Control_DAC: 3710    ! EM_TT(+ 1, 1) Avr = 7.92
Dev = 1.21

  It will now use explicit Keywords for these quantities
  e.g. TT_Phi:  1    Pedestal_Control_DAC: 3710    Ped_Average: 7.92
Ped_Deviation:
1.21    ! EM_TT(+ 1, 1)


Find_DAC Result Analysis Tools

  Add section at bottom of Find_DAC dialog to analyze previously parsed 
  Find_DAC Pedestal Control DAC Result files.  

   The ">> Scan over Range of TrgTwr defined above <<" button will analyze the 
  Pedestal control DAC values over the Trigger Tower Range specified in 
  the top part of the Dialog.

  Four different analysis tools can be applied independently.
  
  "Check Ped Ave within +/- X counts of Z.E.R."
    This checks that the pedestal average for the histogram selected by 
    Find_DAC falls within the user given X counts of the Zero Energy Response.

  "Check Ped Std Dev within X % of eta average
    This checks that the Standard Deviation for the histogram selected by 
    Find_DAC falls within X % of the computed average Standard deviation
    at this eta value for all the phi values included in the analyzed range.

  "Check Ped Std Dev within X % of Prev Measur"
    This checks that the Standard Deviation for the histogram selected by 
    Find_DAC falls within X % of the previously given value.
    For this test to be meningful two TTI files must have been loaded and
    the values from the second file are compared to the values from the
    first file.

  "Check Ped Ctrl DAC within X of previous value"
    This checks that the pedestal average for the histogram selected by 
    Find_DAC falls within X counts of the the previously given value.
    For this test to be meningful two TTI files must have been loaded and
    the values from the second file are compared to the values from the
    first file.

  VME_Access didn't use to know anything beyond registers.  To execute
  TTI files, it would just use the mapping of eta-phi into register 
  coordinates.  VME_Access would not remember anything that it had done.

  We now want to use VME_Access to analyze the Find_DAC result files.
  VME_Access will thus keep a mini version of the L1CT object with just
  the trigger tower objects.  This will give it a place to store the 
  DAC control values, etc. for analysis.


Trigger Tower Info Command File 

  Added keywords "Ped_Average:" and "Ped_Deviation:" to read these values
  reported in the Find_DAC result files.  This is later used to analyze
  and compare the Find_DAC result files.  Trics will in fact record
  the latest value of these two quantities for each Trigger Tower as well
  as remember the previously given value to allow comparison.

  Trics also remembers the values of the gain and pedestal control DAC values
  given in TTI files.  These values are not written to the serial DACs when
  the TTI file is executed, unless explicitely requested from the "CTFE Dac 
  Programming" Dialog.


--------------------------------------------------------------------------------
                      VME_Access Version 3.1 Release Notes
                          -------------------------

12-JUL-2002: (Rev H)

TTI Command Files

  VME_Access can now execute a TTI file from the "CTFE DAC Programming" dialog.
    
  - The full TTI syntax can be ingested, but PROM coefficient 
    definitions are not supported, nor the Legacy front end flags.

  - With a TTI file you can program a Serial Gain and Pedestal 
    Control DAC values.

    Note: VME_Access immediately writes the values in the TTI file 
          while Trics only remembers them for future INIT.

  - Only the new serial DAC Pedestals can be programmed by a VME_Access 
    TTI files (we can use a CBus IO file to program legacy ped DAC)

Find_DAC

  The operator can now ask to create two independent output files:

  - Enabling the check-box "For Results" 
    will create a file with a name like D0_Log\Find_DAC_V3_1_G_20020524.tti;6

    This is the file that VME_Access (and also Trics in the future) 
    can ingest and execute.  

    There will no longer be a line length issue when executing the file.

    There may still be some "Failed" lines that VME_Access will choke on.
    This is a feature, not a bug.

  - Enabling the check-box "For Histograms"
    will create a file with a name like D0_Log\Find_DAC_V3_1_G_20020524.hst;4

    This is the file that will have all the histograms.

  Programming the Serial DACs now allocates the trigger IO semaphore.  
  This means that the monitoring process from Trics could not interfere
  with Find_DAC if it were run from Trics.  Unfortunately this does not
  prevent VME_access and Trics from colliding during CBUS IOs.  To run
  Find_DAC from VME_Access, we thus still need to tell Trics to "Ignore L1CT".


  To run Find_DAC:

 1) Shut off 5 second interferences with Monitoring over CBUS IO:
    In Trics check box "Totally Ignore L1CT" 
    from the "System Control/Status" dialog

 2) Program the Nominal Gain DAC values:
    In VME_Access use the "CTFE DAC Programming" dialog
    to execute the new Trics\D0_Config\RunII_L1CT_Nominal_Gain.tti
    appended below for reference.

 3) Run Find_DAC:
    use the "Find DAC" sub-dialog of the "CTFE DAC PRogramming" dialog
    to select an eta-phi range and run Find_DAC.

  To load the result of Find_DAC:

    In VME Access use the "CTFE DAC PRogramming" dialog
    to execute the file that Find_DAC created with a name like
    Trics\D0_Log\Find_DAC_V3_1_B_20020521.tti;1


  Once we have a Find_DAC TTI file you like, we should:

    - Copy it to trics\d0_config 

    - Edit it as needed to add a '!' in front of each "failed"
      (or replace with a line that loads some other value)
  
    - edit trics\d0_config\Excluded_Trigger_Towers.msg
      to add/remove excluded towers
  
  Note: We will need to manually execute from VME_Access 
      the Nominal Gain TTI file
      and the Find_DAC result file 
  after every Power up, and until we give this job to Trics.

     
--------------------------------------------------------------------------------
                      VME_Access Version 3.0 Release Notes
                          -------------------------

7-MAY-2002: (Rev E)

Find_DAC 

  Port Run I Find_DAC to the new Run II Serial DACs.
  
  The Run I Legacy DACs are still supported for the moment.

High Speed Readout

  VME_Access can now dump the content of the L1FW or L1CT VBD VME buffer

TTI Command Files

  The Trigger Tower Info (.TTI) file syntax has also been extended to ingest 
  information describing the Trigger Energy Tower Gain Control Programming.
  cf. www.pa.msu.edu/hep/d0/ftp/tcc/trics_ii/syntax_rules_trgtwr_info.tti

  The keyword "Dac_Value:" has been changed to a more explicit name
  "Pedestal_Control_DAC:".  "Dac_Value:" has been kept as an alias for
  backwards compatibility, but new files created by "Find_DAC" will use
  the new keyword.

  There is a new keyword "Gain_Control_DAC:" to program new Gain Control
  DAC values for the new Terminator-Attenuator mezzanine cards.

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

                      VME_Access Version 2.3 Release Notes
                          -------------------------

12-JUL-2001: (Rev A)

New "High Speed Readout" sub-dialog with 
    "Dump N Longwords from VBD", i.e. Raw Dump of VBD Data
and
    "Analyze Current Event in VBD", i.e. Formatted Dump of VBD Data

This functionality comes from Trics V9.2 Rev J, cf. Trics's release notes.

The user specifies the base address of the VBD, as seen from
the VME communication crate (i.e. A32 address that will be mapped
by the Vertical Interconnect to the A24 address in the readout crate).

There are also two buttons to preset the VBD base address and select the 
L1FW (or L1CT) VBD at its nominal address.

VME_Access will fail "graciously" if it can't access the specified address.

--------------------------------------------------------------------------------
                      VME_Access Version 2.2 Release Notes
                          -------------------------

14-JUN-2001: (Rev B)

Add Find_DAC (from Trics V9.2 Rev I&J, cf. Trics's release notes)

This dialog is available as a sub-dialog of the "CTFE DAC Programming"

--------------------------------------------------------------------------------
                      VME_Access Version 2.1 Release Notes
                          -------------------------

5-APR-2001: (Rev A)

Analyze Input TRM FIFO Depth:

  Add a new sub-menu "Input TRM FIFO Depth" to analyze Andor Input Term
TRM Fifo Depth.  This test reads the L1 TRM Fifo Status Register a number
of times, extracts the Read and Write Fifo Addresses, derives a corresponding
fifo depth, and histograms the result.

  The output is in the form     "n ( a@x b@y c@z )"
Where 'n' was the most populated histogram bin, and bin#'x' had a total
of 'a' hits, bin #'y' had 'b' hits, etc. All non-empty histogram bins
are displayed.

  The test will abort as soon as one of the samples had its read or write
fifo address "reset" bit set.

  In the matching VME_Access version of this utility the user needs to enter
the full TRM FPGA coordinates by hand (don't forget the transposed FPGA
order), but the TRICS version finds the TRM FPGA given the AOIT num.
The user also selects the sample size (default=100).

--------------------------------------------------------------------------------
                      VME_Access Version 2.0 Release Notes
                          -------------------------

29-Jan-2001:

General:

  Add other Sub-menus from Trics

*   "Register IO"           THE-Card Register Access

*   "CBus IO"               Cal Trig Register Access

*   "Configure FPGA"        Download THE-Card FPGA configuration

    "Card CSR"              THE-Card VME Interface Control Status Registers

    "CTFE DAC Programming"  Cal Trig CTFE DAC Programming

(*) these menus, along with the "VME IO" menu support command files.
note that the DAC programming does not, as it involves system level information.

--------------------------------------------------------------------------------
                      VME_Access Version 1.0 Release Notes
                          -------------------------

13-Sep-2000:

General:

    This VME_Access application has been derived from the TCC Trigger Control
    Computer Software, Trics II V9.0.

    The only sub menu available is "VME IO".