Difference: DaqSpecial (17 vs. 18)

Revision 182010-08-17 - MatteoDuranti

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

Special Operations

Line: 66 to 66
 
  1. SetHighThresholdsOnAllTDRs.sh #port #threshS1 #threshS2 #threshK
    where port= the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
    threshS1= the S1 high threshold
    threshS2= the S2 high threshold
    thresh K=the K high threshold
  2. SetLowThresholdsOnAllTDRs.sh #port #threshS1 #threshS2 #threshK
    where port= the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
    threshS1= the S1 low threshold
    threshS2= the S2 low threshold
    thresh K=the K low threshold
  3. DisableDynamicPedestals.sh #port
    where port=the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
Changed:
<
<
  1. EnablePedestals.sh #port
    where port=the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
  2. EnableDynamicPedestalsWithPar.sh #port #part
    where port=the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
    par= the parameter to use for the dynamic pedestals (how many ADC counts will be "touched" at each event)

    Output:
    during the running of these script you can see two types of info/output:
    if the AMSWire Command was sended without (with) problems -> rxdone=0x0000 (0x0001)
    if the operations was done -> File Erased (Not Erased) / File Loaded (Not Loaded)
>
>
  1. EnableDynamicPedestals.sh #port
    where port=the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
  2. EnableDynamicPedestalsWithPar.sh #port #part
    where port=the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
    par= the parameter to use for the dynamic pedestals (how many ADC counts will be "touched" at each event)
  3. LoadDSPCode.sh #port #code
    to load (AMSWire command 0x46) a dsp code on all the TDRs
    where port= the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
    code= the code to load
  4. ./DeleteFlags.sh #port #par
    to delete a user provided set of flags (choosable in the bit range from 0 to 15) in all TDRs
    where port= the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
    par= the parameter to use (which flags to erase)
  5. ./DeletePermanentFlags.sh #port
    to delete permanent flags (bit 9 to 15) in all TDRs
    where port= the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
  6. ./DeleteAllFlags.sh #port
    to delete all the flags (bit form 0 to 15) in all TDRs
    where port= the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]

    Output:
    during the running of these script you can see two types of info/output:
    if the AMSWire Command was sended without (with) problems -> rxdone=0x0000 (0x0001)
    if the operations was done -> File Erased (Not Erased) / File Loaded (Not Loaded)
 

How to Create and Load a TDR config file:

  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    ~/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    In this directory you can find all the stuff (except for TESTjmdc and slowconf.conf of which there's a simbolic link) needed for create and load configuration files for TDRs:

    - ConfigFile: this is the program to create binary config files for TDRs starting from a "human readable" parameters file
    (as example TDRParamFile.txt) and to create the script (LoadConfs.sh) usefull to uplaod the binary files

    - LoadConfs.sh: the script that load the correct configuration file in each TDR

    - TDRParamFile.txt: can be used as a template for the "human readable" parameter file for TDR

    The file of parameters ("human readable file") can be filled using the TDR documentation by Philipp Azzarello
    and taking into account that for "compliantness" a parameter indicated as "N" here has to written as "0 0 N"
    (where the first two numbers are the Group and the SubGroup, here 0).

    The script for loading the configuration file has to be called using 1 parameter
    (the JMDC port to be used, i.e.
    to use JINF-T-B [JMDC ports: 0,3]
    to use JINF-T-A [JMDC ports: 1,2])
Changed:
<
<
  • The procedure has to be, the 6 thresholds for external planes (up to now, it means layer 1 & 8, in the future has to be probably 1 & 8 & 9) HAS TO BE PASSED EXPLICITELY (Thresholds have to be passed in 'standard' way (1, 2, 3.5, ...)):
    1. Create a parameter file or edit the template (TDRParamFile.txt)
    2. ./ConfigFile TDRParamFile.txt <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh>
>
>
  • The procedure has to be, the 6 thresholds for external planes ( up to now, it means layer 1 & 8, in the future has to be probably 1 & 8 & 9) HAS TO BE PASSED EXPLICITELY (Thresholds have to be passed in 'standard' way (1, 2, 3.5, ...)):
    1. Create a parameter file or edit the template (* TDRParamFile.txt)
    2. ./ConfigFile * TDRParamFile.txt]] <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh>
 
    1. ./LoadConfs.sh #port

How to Create and Load a JINF config file:

Changed:
<
<
  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    ~/TrackerUser/AMSWireCommands/ConfigurationFileJINF/


    In this directory you can find all the stuff (except for TESTjmdc of which there's a simbolic link)
    needed for create and load configuration files for JINF-Ts:

    - ConfigFile: this is the program to create binary config files for JINF-Ts starting from a "human readable" parameters file
    (as example JINFParamFile_X.txt, with X is the crate number in [0-8])
    and to create the script (LoadConfs_X.sh, with X is the crate number in [0-8])
    usefull to uplaod the binary files

    - LoadConfs_X.sh: the script that load the correct configuration file in JINF-T number X

    - LoadConfs.sh: the script that load the correct configuration file in each JINF-T

    - JINFParamFile_X.txt: can be used as a template for the "human readable" parameter file for JINF-T X


    8 different configuration files are created for the 8 crates/JINFs (for now all equals except for crate/JINF 4 [PowerGroup3 with Bias 60V]).
    The file of parameters ("human readable file") can be filled using the JINF documentation by Kounine or the JINF-T one by Philipp Azzarello.
>
>
  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    ~/TrackerUser/AMSWireCommands/ConfigurationFileJINF/


    In this directory you can find all the stuff (except for TESTjmdc of which there's a simbolic link)
    needed for create and load configuration files for JINF-Ts:

    - ConfigFile: this is the program to create binary config files for JINF-Ts starting from a "human readable" parameters file
    (as example * JINFParamFile.txt, with X is the crate number in [0-8])
    and to create the script (LoadConfs_X.sh, with X is the crate number in [0-8])
    usefull to uplaod the binary files

    - LoadConfs_X.sh: the script that load the correct configuration file in JINF-T number X

    - LoadConfs.sh: the script that load the correct configuration file in each JINF-T

    - * JINFParamFile.txt: can be used as a template for the "human readable" parameter file for JINF-T X


    8 different configuration files are created for the 8 crates/JINFs (for now all equals except for crate/JINF 4 [PowerGroup3 with Bias 60V]).
    The file of parameters ("human readable file") can be filled using the JINF documentation by Kounine or the JINF-T one by Philipp Azzarello.
 
Changed:
<
<
  • The procedure has to be

    - to change and load the config file only for the JINF-T X using JINJ NN and JINJ MM to talk with JINF-T A and JINF-T B:

    1. Create a parameter file or edit the template (JINFParamFile_X.txt)
    2. ./ConfigFile JINFParamFile_X.txt NN MM
    3. ./LoadConfs_X.sh

    - to change and load the config file on all JINF-Ts using JINJ NN and JINJ MM to talk with JINF-T's A and JINF-T's B:

    1. Edit the template parameter files (JINFParamFile_X.txt)
    2. ./LoadConfs.sh NN MM
>
>
  • The procedure has to be

    - to change and load the config file only for the JINF-T X using JINJ NN and JINJ MM to talk with JINF-T A and JINF-T B:

    1. Create a parameter file or edit the template (* JINFParamFile.txt)
    2. ./ConfigFile * JINFParamFile.txt NN MM
    3. ./LoadConfs_X.sh

    - to change and load the config file on all JINF-Ts using JINJ NN and JINJ MM to talk with JINF-T's A and JINF-T's B:

    1. Edit the template parameter files (* JINFParamFile.txt)
    2. ./LoadConfs.sh NN MM
  -- PaoloZuccon - 03-Dec-2009
Deleted:
<
<
META FILEATTACHMENT attachment="TDRParamFile.txt" attr="" comment="Human readable TDR parameter file" date="1281980273" name="TDRParamFile.txt" path="TDRParamFile.txt" size="2307" stream="TDRParamFile.txt" tmpFilename="/usr/tmp/CGItemp22228" user="mduranti" version="2"
META FILEATTACHMENT attachment="JINFParamFile.txt" attr="" comment="Human readable JINF parameter file (generic)" date="1261603777" name="JINFParamFile.txt" path="JINFParamFile.txt" size="1380" stream="JINFParamFile.txt" tmpFilename="/usr/tmp/CGItemp35319" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFParamFile_4.txt" attr="" comment="Human readable JINF parameter file (Crate 4)" date="1263400008" name="JINFParamFile_4.txt" path="JINFParamFile_4.txt" size="1667" stream="JINFParamFile_4.txt" tmpFilename="/usr/tmp/CGItemp50824" user="mduranti" version="2"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback