BPM6W1 Beam Position Monitor Electronic Logbook 2007

January 2007

January 2, 2007 (C.Strohman, T.Wilksen, E. Tanke): Upgrade of Xlinx and Coldfire software

• The new version of the Xilinx software now running on this unit is 5.5
• The new version of the Coldfire software now running on this unit is 0.96B

February 2007

February 13, 2007 (E. Tanke): DVGA comparison AD8369 (old) to AD8370 (new)

• DVGA comparison AD8369 (old) to AD8370 (new) in terms of RMS noise as a function of gain can be found below. Conditions: Both DVGAs are on one and the same board (AD8370 connected to channel 0, AD3869 connected to channel 1); measurements for 1024 turns, 1 bunch with a 50 Ohm termination to the input.
  • AD8369
  • AD8370

March 2007

March 5, 2007 (E. Tanke): BPM_V1 code now contains a post-trigger acquisition routine

• The BPM_V1 code now contains a post-trigger acquisition routine (routine # 8). An example of the corresponding .ini file is bpm_v1_posttrig.ini in the [PALMER.TS101.BPM] directory. The fourth entry in the .ini file is the number of turns to acquire following the trigger. The before last entry is the number of turns to acquire prior to the trigger (see example .ini file below for a non-interactive acquisition of electron data using BPM6W1):
  • n
  • n
  • n
  • 1 <--- 1 post-trigger turn to be acquired
  • t
  • r
  • 5
  • e
  • 1045
  • 1045
  • 6
  • 6
  • 678
  • 695
  • 695
  • 700
  • 702
  • 720
  • 707
  • 725
  • 79
  • 1 <--- select the HW trigger (0, 1 or 2)
  • 8 <--- select the post-trigger routine (#8)
  • 1024 <--- 1024 pre-trigger turns to be acquired
  • -1

April 2007

April 05, 2007 (E.Tanke): New trigger handling for HW trigger 1 (bit 0)

• In the bpm_v1.ini file one now needs to enter a supplementary parameter, which is a delay in turns. The entry is behind the trigger mask (see below). Setting this new parameter to 70k turns, upon seeing the trigger, this unit will wait for 70k turns and then take the data. This is useful when one wants to take BPM data simultanuously with BSM data. Note that currently this is the way this unit functions ONLY for taking raw data and ONLY for trigger bit 0. This can be expanded as needed. If you do NOT wish a delay, you can set this new parameter to 0.
• Example of bpm_v1.ini file for raw data taking:
  • n
  • n
  • n
  • 1024
  • t
  • r
  • 5
  • e
  • 1035
  • 1035
  • 4
  • 4
  • 678
  • 695
  • 695
  • 700
  • 702
  • 720
  • 707
  • 725
  • 79
  • 1 70000 <--- select the HW trigger (0, 1 or 2) and the number of turns to delay acquisition by
  • 2
  • -1

April 09, 2007 (E.Tanke): New trigger handling for HW trigger 2 (bit 1)

• The same option of having a delay after trigger 1 (see 5-Apr-2007 log entry) has been implemented for trigger 2 (bit 1)

April 11, 2007 : /nfs server directory restructuring

• The /nfs server directory has been restructured (see this link). BPM files that have been stored under /nfs/cesr/temp/ts101/BPM6W1_data before, can now be found under /nfs/acc/temp/ts101/BPM6W1_data

June 2007

June 08, 2007 (E.Tanke): Timing for 4 ns spaced bunches

• Timings for 4 ns spaced bunches, obtained from the MS in early April, can be found here.