Difference: DaqSpecial (1 vs. 20)

Revision 202010-08-20 - MatteoDuranti

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

Special Operations

Line: 77 to 77
 

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])
  • The procedure has to be:
Changed:
<
<
    1. Create a parameter file or edit the template (* TDRParamFile.txt)
    2. ./ConfigFile * TDRParamFile.txt]] <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh> <ConfFileName>
      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, ...))
      ConfFileName is the name of the configuration files that will be produced
    3. ./LoadConfs.sh #port #oldconffilename
      #oldconfname is the name of the "old" configuration file to be erased in order to write the new one
>
>
    1. Create a parameter file or edit the template (TDRParamFile.txt)
    2. ./ConfigFile TDRParamFile.txt]] <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh> <ConfFileName>
      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, ...))
      ConfFileName is the name of the configuration files that will be produced
    3. ./LoadConfs.sh #port #oldconffilename
      #oldconfname is the name of the "old" configuration file to be erased in order to write the new one
 

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.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.
>
>
  • 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

    - CreateAndLoadConfs.sh: the script that create and 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.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
>
>
  • The procedure has to be

    - to change and load the configuration file BBBB, erasing the old configuration file AAAA, 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 X NN MM AAAA BBBB
    3. ./LoadConfs_X.sh

    - to change and load the configuration file BBBB, erasing the old configuration file AAAA, 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's (they will be automatically called by the script below )
    2. ./CreateAndLoadConfs.sh NN MM AAAA BBBB
  -- PaoloZuccon - 03-Dec-2009

Revision 192010-08-18 - MatteoDuranti

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

Special Operations

Line: 40 to 40
  or
Changed:
<
<
  • (Unofficial way to have the default program with the official default name)
>
>
  • (Unofficial way to have the default program with its own name)
 

  • WHEN WRITING SOFTWARE ON JINF-T REMEMBER TO REPEAT THE SAME OPERATION ALSO ON THE OTHER SIDE JINF
Line: 76 to 76
 

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, ...)):
>
>
  • The procedure has to be:
 
    1. Create a parameter file or edit the template (* TDRParamFile.txt)
Changed:
<
<
    1. ./ConfigFile * TDRParamFile.txt]] <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh>
    2. ./LoadConfs.sh #port
>
>
    1. ./ConfigFile * TDRParamFile.txt]] <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh> <ConfFileName>
      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, ...))
      ConfFileName is the name of the configuration files that will be produced
    2. ./LoadConfs.sh #port #oldconffilename
      #oldconfname is the name of the "old" configuration file to be erased in order to write the new one
 

How to Create and Load a JINF 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/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.

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"

Revision 172010-08-16 - MatteoDuranti

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

Special Operations

How to directly command a JINF/TDR:

Changed:
<
<
  • Go to ~/TrackerUser/AMSWireCommands/ of the "tracker" user
  • here you can find the program TESTjmdc
    this is a program that let talk to JINJ boards and to all the nodes after it

    The syntax for this program is:
    ./TESTjmdc port amsw_node cmd arg1 arg2 ...
>
>
  • Go to ~/TrackerUser/AMSWireCommands/ of the "tracker" user
    here you can find the program TESTjmdc
    this is a program that let talk to JINJ boards and to all the nodes after it
    that uses the slowconf.conf file for the HRDL settings

    The syntax for this program is:
    ./TESTjmdc port amsw_node cmd arg1 arg2 ...
 
    • port
Changed:
<
<
    • amsw_node is the address (in AMSWire scheme, NOT in JMDC scheme!!! You can refer to the table below...) of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f
>
>
    • amsw_node is the address (in AMSWire scheme, NOT in JMDC scheme!!! You can refer to the table below...) of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f
 
    • cmd is the command to send to the node (from Kounine document)
      Examples of Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
    • args are the parameters you want to pass to cmd
      you can pass how many args (command's parameters) you need
    • numbers must be written in hex
Line: 22 to 21
 
+ RAM - 7 T7 0x173f 23 0xC2 0xC3 0xC4 0xC5  

Filenames convention and history:

Changed:
<
<
The dsp codes are stored in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/
>
>
The dsp codes are stored in : ~/TrackerUser/AMSWireCommands/DspCodes/
  the file name has to be file_ node _ name.dat

where:

  • node = tdr, jinft, jinj, jlvl1
  • name = versnumber = same name as in Philipp list i.e. 3ee3, MUST be THE SAME as the first line in the contents of the file itself.
Changed:
<
<

How to Load a new JINF-T/TDR firmware

  • Get the new dsp code in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/file_ node _ name.dat
  • copy the file as file.dat in : /home/ams/TrackerUser/AMSWireCommands/
>
>

How to Upload a new JINF-T/TDR firmware

  • Get the new dsp code in : ~/TrackerUser/AMSWireCommands/DspCodes/file_ node _ name.dat

  • (Official way to have the default program with the official default name)
    • copy the file as file.dat in : ~/TrackerUser/AMSWireCommands/
 
  • edit the first line of the file.dat and set it as:
    • 29F2 if it will be the default file for JINF-T
    • 29F3 if it will be the default file for TDR
Added:
>
>

or

  • (Unofficial way to have the default program with the official default name)
 
  • WHEN WRITING SOFTWARE ON JINF-T REMEMBER TO REPEAT THE SAME OPERATION ALSO ON THE OTHER SIDE JINF
Changed:
<
<
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is loaded in memory with the right command (AMSWire 0x46).
>
>
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is loaded in memory with the right command (AMSWire command 0x46).
 
  • There are useful scripts:
Changed:
<
<
>
>
 
  1. DeleteFlashFileOnAllnodes.sh port# filename#
    where node=TDR,JINF
  2. a - WriteFlashFileOnAllnodesFromHere.sh port# filename#
    where node=TDR,JINF
    It loads file.dat from the current directory, read back the flash content and
    checks that filename# is in the flash memory.
    b - WriteFlashFileOnAllnodesFromDSPCodes.sh port# filename#
    where node=TDR,JINF
    checks for file_ node _ name.dat in the /DspCodes directory and copies it in file.dat in current directory before uploading.
  3. SetDefaultFlashFileOnAllnodes.sh port# filename# #status
    where node=TDR,JINF
    looks for the filename in the flash and if it is found and set the default bit according to #status
    status=1 set it to default (from 3xxx to 2xxx, from 7xxx to 6xxx)
    status=0 downgrade from default
  4. LoadFlashFileOnAllnodes #port #filename
    runs the #filename on all nodes
  5. WriteANewnodesCodeOnAllnodesFromHereAndSetAsDefault.sh port# new_filename# old_filename#
Changed:
<
<
  1. WriteANewnodesCodeOnAllnodesFromDSPCodesAndSetAsDefault.sh port# new_filename# old_filename#
    Performs either 2a or 2b on the new_filename + 3 with status=0 on old filename and 3 with status=1 + 4 on new filename.
  2. 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. WriteANewnodesCodeOnAllnodesFromDSPCodesAndSetAsDefault.sh port# new_filename# old_filename#
  2. Performs either 2a or 2b on the new_filename + 3 with status=0 on old filename and 3 with status=1 + 4 on new filename.

    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)
 
Added:
>
>

How to change settings

  • There are useful scripts to do this:

  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]
  4. EnablePedestals.sh #port
    where port=the port of JMDC to be used [i.e. which JINJ and which side of JINF-T]
  5. 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)
 

How to Create and Load a TDR config file:

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


    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 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])
  • The procedure has to be, the 6 thresholds for external planes HAS TO BE PASSED EXPLICITELY (Thresholds have to be passed in 'standard' way (1, 2, 3.5, ...)):
>
>
  • 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])
  • 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>
    3. ./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:
    /home/ams/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_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 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

-- PaoloZuccon - 03-Dec-2009

Changed:
<
<
META FILEATTACHMENT attachment="TDRParamFile.txt" attr="" comment="Human readable TDR parameter file" date="1261590818" name="TDRParamFile.txt" path="TDRParamFile.txt" size="1787" stream="TDRParamFile.txt" tmpFilename="/usr/tmp/CGItemp35309" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_0.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) generic" date="1261591453" name="TDRconfigfile_0.dat" path="TDRconfigfile_0.dat" size="275" stream="TDRconfigfile_0.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_1.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 1" date="1261591521" name="TDRconfigfile_1.dat" path="TDRconfigfile_1.dat" size="274" stream="TDRconfigfile_1.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_2.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 2" date="1261591541" name="TDRconfigfile_2.dat" path="TDRconfigfile_2.dat" size="275" stream="TDRconfigfile_2.dat" tmpFilename="/usr/tmp/CGItemp35312" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_3.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 3" date="1261591560" name="TDRconfigfile_3.dat" path="TDRconfigfile_3.dat" size="275" stream="TDRconfigfile_3.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_4.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 4" date="1261591882" name="TDRconfigfile_4.dat" path="TDRconfigfile_4.dat" size="275" stream="TDRconfigfile_4.dat" tmpFilename="/usr/tmp/CGItemp35179" user="mduranti" version="1"
>
>
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"
Deleted:
<
<
META FILEATTACHMENT attachment="JINFconfigfile_0.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_0.txt) for Crate 0" date="1261603867" name="JINFconfigfile_0.dat" path="JINFconfigfile_0.dat" size="165" stream="JINFconfigfile_0.dat" tmpFilename="/usr/tmp/CGItemp35241" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_1.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_1.txt) for Crate 1" date="1261603886" name="JINFconfigfile_1.dat" path="JINFconfigfile_1.dat" size="165" stream="JINFconfigfile_1.dat" tmpFilename="/usr/tmp/CGItemp35242" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_2.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_2.txt) for Crate 2" date="1261603905" name="JINFconfigfile_2.dat" path="JINFconfigfile_2.dat" size="165" stream="JINFconfigfile_2.dat" tmpFilename="/usr/tmp/CGItemp35213" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_3.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_3.txt) for Crate 3" date="1261603932" name="JINFconfigfile_3.dat" path="JINFconfigfile_3.dat" size="165" stream="JINFconfigfile_3.dat" tmpFilename="/usr/tmp/CGItemp35197" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_4.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_4.txt) for Crate 4" date="1261603957" name="JINFconfigfile_4.dat" path="JINFconfigfile_4.dat" size="185" stream="JINFconfigfile_4.dat" tmpFilename="/usr/tmp/CGItemp35248" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_5.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_5.txt) for Crate 5" date="1261603978" name="JINFconfigfile_5.dat" path="JINFconfigfile_5.dat" size="165" stream="JINFconfigfile_5.dat" tmpFilename="/usr/tmp/CGItemp35285" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_6.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_6.txt) for Crate 6" date="1261603996" name="JINFconfigfile_6.dat" path="JINFconfigfile_6.dat" size="165" stream="JINFconfigfile_6.dat" tmpFilename="/usr/tmp/CGItemp35212" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_7.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_7.txt) for Crate 7" date="1261604214" name="JINFconfigfile_7.dat" path="JINFconfigfile_7.dat" size="165" stream="JINFconfigfile_7.dat" tmpFilename="/usr/tmp/CGItemp35226" user="mduranti" version="1"

Revision 162010-08-16 - MatteoDuranti

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

Special Operations

How to directly command a JINF/TDR:

Changed:
<
<
  • Go to /home/ams/TrackerUser/AMSWireCommands/
>
>
  • Go to ~/TrackerUser/AMSWireCommands/ of the "tracker" user
 
  • here you can find the program TESTjmdc
    this is a program that let talk to JINJ boards and to all the nodes after it

    The syntax for this program is:
    ./TESTjmdc port amsw_node cmd arg1 arg2 ...
    • port
Changed:
<
<
    • amsw_node is the address (in AMSWire scheme, NOT in JMDC scheme!!!) of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f
>
>
    • amsw_node is the address (in AMSWire scheme, NOT in JMDC scheme!!! You can refer to the table below...) of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f
    • cmd is the command to send to the node (from Kounine document)
      Examples of Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
    • args are the parameters you want to pass to cmd
      you can pass how many args (command's parameters) you need
    • numbers must be written in hex
 
          JINJ   JMDC  
X Y Z OCT Crate ADDR NUM A B P S  
+ WAKE + 1 T0 0x033f 03 0xA6 0xA7 0xA8 0xA9  
Line: 17 to 20
 
- WAKE - 6 T5 0x113f 17 0xBA 0xBB 0xBC 0xBD  
- RAM - 8 T6 0x163f 22 0xBE 0xBF 0xC0 0xC1  
+ RAM - 7 T7 0x173f 23 0xC2 0xC3 0xC4 0xC5  
Deleted:
<
<
    • cmd is the command to send to the node (from Kounine document)
      Examples of Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
    • args are the parameters you want to pass to cmd
      you can pass how many args (command's parameters) you need
    • numbers must be written in hex
 

Filenames convention and history:

The dsp codes are stored in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/

Revision 152010-08-16 - MatteoDuranti

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

Special Operations

Line: 18 to 18
 
- RAM - 8 T6 0x163f 22 0xBE 0xBF 0xC0 0xC1  
+ RAM - 7 T7 0x173f 23 0xC2 0xC3 0xC4 0xC5  
Changed:
<
<
    • cmd is the command to send to the node (from Kounine document)
      Examples of Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
>
>
 
    • args are the parameters you want to pass to cmd
      you can pass how many args (command's parameters) you need
    • numbers must be written in hex

Filenames convention and history:

Revision 142010-02-21 - MatteoDuranti

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

Special Operations

Line: 52 to 52
 

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:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    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 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 HAS TO BE PASSED EXPLICITELY:
>
>
  • The procedure has to be, the 6 thresholds for external planes 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>
    3. ./LoadConfs.sh #port

Revision 132010-02-20 - MatteoDuranti

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

Special Operations

Line: 52 to 52
 

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:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    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 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 HAS TO BE PASSED EXPLICITELY:
>
>
  • The procedure has to be, the 6 thresholds for external planes HAS TO BE PASSED EXPLICITELY:
 
    1. Create a parameter file or edit the template (TDRParamFile.txt)
    2. ./ConfigFile TDRParamFile.txt <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh>
    3. ./LoadConfs.sh #port

Revision 122010-01-21 - MatteoDuranti

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

Special Operations

Line: 52 to 52
 

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:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    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 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 procedure has to be, the 6 thresholds for external HAS TO BE PASSED EXPLICITELY:
 
    1. Create a parameter file or edit the template (TDRParamFile.txt)
Changed:
<
<
    1. ./ConfigFile TDRParamFile.txt
>
>
    1. ./ConfigFile TDRParamFile.txt <S1HighThresh> <S1LowThresh> <S2HighThresh> <S2LowThresh> <KHighThresh> <KLowThresh>
 
    1. ./LoadConfs.sh #port

How to Create and Load a JINF config file:

  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    /home/ams/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.
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

-- PaoloZuccon - 03-Dec-2009

Revision 112010-01-13 - MatteoDuranti

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

Special Operations

Line: 34 to 34
 
  • Get the new dsp code in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/file_ node _ name.dat
  • copy the file as file.dat in : /home/ams/TrackerUser/AMSWireCommands/
  • edit the first line of the file.dat and set it as:
Changed:
<
<
    • 2932 if it will be the default file for JINFT (will become 29F2)
>
>
    • 29F2 if it will be the default file for JINF-T
 
    • 29F3 if it will be the default file for TDR
  • WHEN WRITING SOFTWARE ON JINF-T REMEMBER TO REPEAT THE SAME OPERATION ALSO ON THE OTHER SIDE JINF
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is loaded in memory with the right command (AMSWire 0x46).
Line: 51 to 51
 
  1. 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:

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


    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 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])
>
>
  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    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 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])
 

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:
    /home/ams/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 procedure has to be

    - to change and load the config file for only one JINF-T:

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

    - to change and load the config file on all JINF-Ts:

    1. Edit the template parameter files (JINFParamFile_X.txt)
    2. ./LoadConfs.sh
>
>
  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    /home/ams/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 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
  -- PaoloZuccon - 03-Dec-2009
Line: 69 to 70
 
META FILEATTACHMENT attachment="TDRconfigfile_3.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 3" date="1261591560" name="TDRconfigfile_3.dat" path="TDRconfigfile_3.dat" size="275" stream="TDRconfigfile_3.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_4.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 4" date="1261591882" name="TDRconfigfile_4.dat" path="TDRconfigfile_4.dat" size="275" stream="TDRconfigfile_4.dat" tmpFilename="/usr/tmp/CGItemp35179" user="mduranti" version="1"
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"
Changed:
<
<
META FILEATTACHMENT attachment="JINFParamFile_4.txt" attr="" comment="Human readable JINF parameter file (Crate 4)" date="1261603807" name="JINFParamFile_4.txt" path="JINFParamFile_4.txt" size="1719" stream="JINFParamFile_4.txt" tmpFilename="/usr/tmp/CGItemp35292" 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"
 
META FILEATTACHMENT attachment="JINFconfigfile_0.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_0.txt) for Crate 0" date="1261603867" name="JINFconfigfile_0.dat" path="JINFconfigfile_0.dat" size="165" stream="JINFconfigfile_0.dat" tmpFilename="/usr/tmp/CGItemp35241" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_1.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_1.txt) for Crate 1" date="1261603886" name="JINFconfigfile_1.dat" path="JINFconfigfile_1.dat" size="165" stream="JINFconfigfile_1.dat" tmpFilename="/usr/tmp/CGItemp35242" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_2.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_2.txt) for Crate 2" date="1261603905" name="JINFconfigfile_2.dat" path="JINFconfigfile_2.dat" size="165" stream="JINFconfigfile_2.dat" tmpFilename="/usr/tmp/CGItemp35213" user="mduranti" version="1"

Revision 102009-12-23 - MatteoDuranti

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

Special Operations

Line: 51 to 51
 
  1. 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:

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


    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 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])
>
>
  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    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 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:
<
<
    1. ./LoadConfs #port
>
>
    1. ./LoadConfs.sh #port

How to Create and Load a JINF config file:

  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    /home/ams/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 procedure has to be

    - to change and load the config file for only one JINF-T:

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

    - to change and load the config file on all JINF-Ts:

    1. Edit the template parameter files (JINFParamFile_X.txt)
    2. ./LoadConfs.sh
  -- PaoloZuccon - 03-Dec-2009
Line: 65 to 68
 
META FILEATTACHMENT attachment="TDRconfigfile_2.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 2" date="1261591541" name="TDRconfigfile_2.dat" path="TDRconfigfile_2.dat" size="275" stream="TDRconfigfile_2.dat" tmpFilename="/usr/tmp/CGItemp35312" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_3.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 3" date="1261591560" name="TDRconfigfile_3.dat" path="TDRconfigfile_3.dat" size="275" stream="TDRconfigfile_3.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_4.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 4" date="1261591882" name="TDRconfigfile_4.dat" path="TDRconfigfile_4.dat" size="275" stream="TDRconfigfile_4.dat" tmpFilename="/usr/tmp/CGItemp35179" user="mduranti" version="1"
Added:
>
>
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="1261603807" name="JINFParamFile_4.txt" path="JINFParamFile_4.txt" size="1719" stream="JINFParamFile_4.txt" tmpFilename="/usr/tmp/CGItemp35292" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_0.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_0.txt) for Crate 0" date="1261603867" name="JINFconfigfile_0.dat" path="JINFconfigfile_0.dat" size="165" stream="JINFconfigfile_0.dat" tmpFilename="/usr/tmp/CGItemp35241" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_1.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_1.txt) for Crate 1" date="1261603886" name="JINFconfigfile_1.dat" path="JINFconfigfile_1.dat" size="165" stream="JINFconfigfile_1.dat" tmpFilename="/usr/tmp/CGItemp35242" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_2.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_2.txt) for Crate 2" date="1261603905" name="JINFconfigfile_2.dat" path="JINFconfigfile_2.dat" size="165" stream="JINFconfigfile_2.dat" tmpFilename="/usr/tmp/CGItemp35213" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_3.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_3.txt) for Crate 3" date="1261603932" name="JINFconfigfile_3.dat" path="JINFconfigfile_3.dat" size="165" stream="JINFconfigfile_3.dat" tmpFilename="/usr/tmp/CGItemp35197" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_4.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_4.txt) for Crate 4" date="1261603957" name="JINFconfigfile_4.dat" path="JINFconfigfile_4.dat" size="185" stream="JINFconfigfile_4.dat" tmpFilename="/usr/tmp/CGItemp35248" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_5.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_5.txt) for Crate 5" date="1261603978" name="JINFconfigfile_5.dat" path="JINFconfigfile_5.dat" size="165" stream="JINFconfigfile_5.dat" tmpFilename="/usr/tmp/CGItemp35285" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_6.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_6.txt) for Crate 6" date="1261603996" name="JINFconfigfile_6.dat" path="JINFconfigfile_6.dat" size="165" stream="JINFconfigfile_6.dat" tmpFilename="/usr/tmp/CGItemp35212" user="mduranti" version="1"
META FILEATTACHMENT attachment="JINFconfigfile_7.dat" attr="" comment="JINF configfile (created starting from JINFParamFile_7.txt) for Crate 7" date="1261604214" name="JINFconfigfile_7.dat" path="JINFconfigfile_7.dat" size="165" stream="JINFconfigfile_7.dat" tmpFilename="/usr/tmp/CGItemp35226" user="mduranti" version="1"

Revision 92009-12-23 - MatteoDuranti

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

Special Operations

Line: 50 to 50
 
  1. WriteANewnodesCodeOnAllnodesFromDSPCodesAndSetAsDefault.sh port# new_filename# old_filename#
    Performs either 2a or 2b on the new_filename + 3 with status=0 on old filename and 3 with status=1 + 4 on new filename.
  2. 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)
Changed:
<
<

How to Create and Load a JINF-T/TDR config file:

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

    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 TDRs and for JINF-Ts:
  • configuration_JINF: there is the program to create config files for JINF-T starting from a "human readable" parameters file and the last configfiles created
  • configuration_TDR: there is the program to create config files for TDRs starting from a "human readable" parameters file and the last configfiles created
  • LoadConfJINFs & LoadConfTDRs: are the script that load the correct configuration file in each node
  • LoadScript: there are the two programs (editable if needed) that create the scripts to load the configuration files
    • for TDR makes the script loading the correct configfile for each TAS ladder type and, in the future if needed, to have different threshold on each ladder
    • for JINF makes the script loading the correct configfile for each crate/JINF, for now all equals except for crete/JINF 4 [PowerGroup3 with Bias 60V])

  • TDRs:
    • 5 different configuration files are created for the 5 different TAS type of ladders. All the files are created starting from only one parameters file (paramfil.txt can be used as template) and the TAS ladder type parameter is change "automagically" from the program.
      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. if to use JINF-T-B
      [JMDC ports: 0,3] or JINF-T-A [JMDC ports: 1,2])
  • JINFs:
    • 8 different configuration files are created for the 8 crates/JINFs (for now all equals except for crete/JINF 4 [PowerGroup3 with Bias 60V]).
      The file of parameters ("human readable file", paramfil.txt can be used as template) can be filled using the JINF documentation by Kounine or the JINF-T one by Philipp Azzarello.
  • Procedure:
    The procedure has to be something like (starting from this directory):
    • if we want only to change the configuration files
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF file.txt
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR file.txt
      • ./LoadConfJINFs
      • ./LoadConfTDRs #port
    • if starting from scratch
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF file.txt
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR file.txt
      • cd LoadSCript -> make -> ./LoadScriptJINF
      • cd LoadSCript -> make -> ./LoadScripTDR
      • ./LoadConfJINFs
      • ./LoadConfTDRs #port
>
>

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:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFileTDR/


    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 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])
  • The procedure has to be:
    1. Create a parameter file or edit the template (TDRParamFile.txt)
    2. ./ConfigFile TDRParamFile.txt
    3. ./LoadConfs #port
  -- PaoloZuccon - 03-Dec-2009
Added:
>
>
META FILEATTACHMENT attachment="TDRParamFile.txt" attr="" comment="Human readable TDR parameter file" date="1261590818" name="TDRParamFile.txt" path="TDRParamFile.txt" size="1787" stream="TDRParamFile.txt" tmpFilename="/usr/tmp/CGItemp35309" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_0.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) generic" date="1261591453" name="TDRconfigfile_0.dat" path="TDRconfigfile_0.dat" size="275" stream="TDRconfigfile_0.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_1.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 1" date="1261591521" name="TDRconfigfile_1.dat" path="TDRconfigfile_1.dat" size="274" stream="TDRconfigfile_1.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_2.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 2" date="1261591541" name="TDRconfigfile_2.dat" path="TDRconfigfile_2.dat" size="275" stream="TDRconfigfile_2.dat" tmpFilename="/usr/tmp/CGItemp35312" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_3.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 3" date="1261591560" name="TDRconfigfile_3.dat" path="TDRconfigfile_3.dat" size="275" stream="TDRconfigfile_3.dat" tmpFilename="/usr/tmp/CGItemp35207" user="mduranti" version="1"
META FILEATTACHMENT attachment="TDRconfigfile_4.dat" attr="" comment="TDR configfile (created starting from TDRParamFile.txt) for ladder TAS type 4" date="1261591882" name="TDRconfigfile_4.dat" path="TDRconfigfile_4.dat" size="275" stream="TDRconfigfile_4.dat" tmpFilename="/usr/tmp/CGItemp35179" user="mduranti" version="1"

Revision 82009-12-10 - MatteoDuranti

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

Special Operations

Line: 7 to 7
 
  • here you can find the program TESTjmdc
    this is a program that let talk to JINJ boards and to all the nodes after it

    The syntax for this program is:
    ./TESTjmdc port amsw_node cmd arg1 arg2 ...
    • port
    • amsw_node is the address (in AMSWire scheme, NOT in JMDC scheme!!!) of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f
Changed:
<
<
OCT CRate IND (Hex) IND (DEC)  
3 T3 013f 01  
4 T2 003f 00  
7 T7 173f 23  
8 T6 163f 22  
1 T0 033f 03  
4 T1 093f 09  
5 T4 103f 16  
6 T5 113f 17  

*the octant column is wrong and has to be checked

>
>
          JINJ   JMDC  
X Y Z OCT Crate ADDR NUM A B P S  
+ WAKE + 1 T0 0x033f 03 0xA6 0xA7 0xA8 0xA9  
- WAKE + 2 T1 0x093f 09 0xAA 0xAB 0xAC 0xAD  
- RAM + 4 T2 0x003f 00 0xAE 0xAF 0xB0 0xB1  
+ RAM + 3 T3 0x013f 01 0xB2 0xB3 0xB4 0xB5  
+ WAKE - 5 T4 0x103f 16 0xB6 0xB7 0xB8 0xB9  
- WAKE - 6 T5 0x113f 17 0xBA 0xBB 0xBC 0xBD  
- RAM - 8 T6 0x163f 22 0xBE 0xBF 0xC0 0xC1  
+ RAM - 7 T7 0x173f 23 0xC2 0xC3 0xC4 0xC5  
 
    • cmd is the command to send to the node (from Kounine document)
      Examples of Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
    • args are the parameters you want to pass to cmd
      you can pass how many args (command's parameters) you need
Line: 37 to 36
 
  • edit the first line of the file.dat and set it as:
    • 2932 if it will be the default file for JINFT (will become 29F2)
    • 29F3 if it will be the default file for TDR
Changed:
<
<
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is run afterwards.
>
>
  • WHEN WRITING SOFTWARE ON JINF-T REMEMBER TO REPEAT THE SAME OPERATION ALSO ON THE OTHER SIDE JINF
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is loaded in memory with the right command (AMSWire 0x46).
 
  • There are useful scripts:

Revision 72009-12-10 - MatteoDuranti

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

Special Operations

Line: 62 to 62
 

  • TDRs:
Changed:
<
<
    • 5 different configuration files are created for the 5 different TAS type of ladders. All the files are created starting from only one parameters file (paramfil.txt) and the TAS ladder type parameter is change "automagically" from the program.
      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).
>
>
    • 5 different configuration files are created for the 5 different TAS type of ladders. All the files are created starting from only one parameters file (paramfil.txt can be used as template) and the TAS ladder type parameter is change "automagically" from the program.
      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. if to use JINF-T-B
      [JMDC ports: 0,3] or JINF-T-A [JMDC ports: 1,2])
  • JINFs:
Changed:
<
<
    • 8 different configuration files are created for the 8 crates/JINFs (for now all equals except for crete/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.
>
>
    • 8 different configuration files are created for the 8 crates/JINFs (for now all equals except for crete/JINF 4 [PowerGroup3 with Bias 60V]).
      The file of parameters ("human readable file", paramfil.txt can be used as template) can be filled using the JINF documentation by Kounine or the JINF-T one by Philipp Azzarello.
 
  • Procedure:
    The procedure has to be something like (starting from this directory):
    • if we want only to change the configuration files
Changed:
<
<
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR
>
>
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF file.txt
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR file.txt
 
      • ./LoadConfJINFs
      • ./LoadConfTDRs #port
    • if starting from scratch
Changed:
<
<
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR
>
>
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF file.txt
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR file.txt
 

Revision 62009-12-10 - MatteoDuranti

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

Special Operations

How to directly command a JINF/TDR:

  • Go to /home/ams/TrackerUser/AMSWireCommands/
  • here you can find the program TESTjmdc
    this is a program that let talk to JINJ boards and to all the nodes after it

    The syntax for this program is:
    ./TESTjmdc port amsw_node cmd arg1 arg2 ...
Added:
>
>
    • port
    • amsw_node is the address (in AMSWire scheme, NOT in JMDC scheme!!!) of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f
OCT CRate IND (Hex) IND (DEC)  
3 T3 013f 01  
4 T2 003f 00  
7 T7 173f 23  
8 T6 163f 22  
1 T0 033f 03  
4 T1 093f 09  
5 T4 103f 16  
6 T5 113f 17  

*the octant column is wrong and has to be checked

    • cmd is the command to send to the node (from Kounine document)
      Examples of Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
    • args are the parameters you want to pass to cmd
      you can pass how many args (command's parameters) you need
 
    • numbers must be written in hex
Deleted:
<
<
    • amsw_node is the address of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f

      OCT CRATE IND (Hex) (Dec)
      3 3 013f 01
      4 2 003f 00
      7 7 173f 23
      8 6 163f 22
      1 0 033f 03
      4 1 093f 09
      5 4 103f 16
      6 5 113f 17

      Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
 

Filenames convention and history:

The dsp codes are stored in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/

Line: 23 to 38
 
    • 2932 if it will be the default file for JINFT (will become 29F2)
    • 29F3 if it will be the default file for TDR
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is run afterwards.
Added:
>
>
  • There are useful scripts:
 
Added:
>
>

  1. DeleteFlashFileOnAllnodes.sh port# filename#
    where node=TDR,JINF
  2. a - WriteFlashFileOnAllnodesFromHere.sh port# filename#
    where node=TDR,JINF
    It loads file.dat from the current directory, read back the flash content and
    checks that filename# is in the flash memory.
    b - WriteFlashFileOnAllnodesFromDSPCodes.sh port# filename#
    where node=TDR,JINF
    checks for file_ node _ name.dat in the /DspCodes directory and copies it in file.dat in current directory before uploading.
  3. SetDefaultFlashFileOnAllnodes.sh port# filename# #status
    where node=TDR,JINF
    looks for the filename in the flash and if it is found and set the default bit according to #status
    status=1 set it to default (from 3xxx to 2xxx, from 7xxx to 6xxx)
    status=0 downgrade from default
  4. LoadFlashFileOnAllnodes #port #filename
    runs the #filename on all nodes
  5. WriteANewnodesCodeOnAllnodesFromHereAndSetAsDefault.sh port# new_filename# old_filename#
  6. WriteANewnodesCodeOnAllnodesFromDSPCodesAndSetAsDefault.sh port# new_filename# old_filename#
    Performs either 2a or 2b on the new_filename + 3 with status=0 on old filename and 3 with status=1 + 4 on new filename.
  7. 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 JINF-T/TDR config file:

Added:
>
>
  • The stuff to create a config files, create the script to load config files, and then load config files is in:
    /home/ams/TrackerUser/AMSWireCommands/ConfigurationFile/

    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 TDRs and for JINF-Ts:
  • configuration_JINF: there is the program to create config files for JINF-T starting from a "human readable" parameters file and the last configfiles created
  • configuration_TDR: there is the program to create config files for TDRs starting from a "human readable" parameters file and the last configfiles created
  • LoadConfJINFs & LoadConfTDRs: are the script that load the correct configuration file in each node
  • LoadScript: there are the two programs (editable if needed) that create the scripts to load the configuration files
    • for TDR makes the script loading the correct configfile for each TAS ladder type and, in the future if needed, to have different threshold on each ladder
    • for JINF makes the script loading the correct configfile for each crate/JINF, for now all equals except for crete/JINF 4 [PowerGroup3 with Bias 60V])

  • TDRs:
    • 5 different configuration files are created for the 5 different TAS type of ladders. All the files are created starting from only one parameters file (paramfil.txt) and the TAS ladder type parameter is change "automagically" from the program.
      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. if to use JINF-T-B
      [JMDC ports: 0,3] or JINF-T-A [JMDC ports: 1,2])
  • JINFs:
    • 8 different configuration files are created for the 8 crates/JINFs (for now all equals except for crete/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.
  • Procedure:
    The procedure has to be something like (starting from this directory):
    • if we want only to change the configuration files
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR
      • ./LoadConfJINFs
      • ./LoadConfTDRs #port
    • if starting from scratch
      • cd configuration_JINF -> Edit the parameters files -> ./doparamJINF
      • cd configuration_TDR -> Edit the parameters files -> ./doparamTDR
      • cd LoadSCript -> make -> ./LoadScriptJINF
      • cd LoadSCript -> make -> ./LoadScripTDR
      • ./LoadConfJINFs
      • ./LoadConfTDRs #port
  -- PaoloZuccon - 03-Dec-2009

Revision 52009-12-10 - MatteoDuranti

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

Special Operations

Added:
>
>

How to directly command a JINF/TDR:

  • Go to /home/ams/TrackerUser/AMSWireCommands/
  • here you can find the program TESTjmdc
    this is a program that let talk to JINJ boards and to all the nodes after it

    The syntax for this program is:
    ./TESTjmdc port amsw_node cmd arg1 arg2 ...
    • numbers must be written in hex
    • amsw_node is the address of the node you want talk to:
      Node address examples:
      JINJ-itself = ffff
      JINF-T0 = 033f
      TDR-0-00-A (T0 TDR00) = 003f033f
      TDR-4-10-B (T4 TDR21) = 153f103f
      AllTDR-7 = 4000173f

      OCT CRATE IND (Hex) (Dec)
      3 3 013f 01
      4 2 003f 00
      7 7 173f 23
      8 6 163f 22
      1 0 033f 03
      4 1 093f 09
      5 4 103f 16
      6 5 113f 17

      Command (from Kounine document):
      Read Status: C [no pars]
      Read Flash: 7 [no pars]
      Read last Event Number: 2 [no pars]
 

Filenames convention and history:

The dsp codes are stored in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/

Line: 19 to 24
 
    • 29F3 if it will be the default file for TDR
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is run afterwards.
Changed:
<
<

How to Create a JINF-T/TDR config file

How to directly command a JINF/TDR

>
>

How to Create and Load a JINF-T/TDR config file:

  -- PaoloZuccon - 03-Dec-2009

Revision 42009-12-09 - MatteoDuranti

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

Special Operations

Line: 12 to 12
 
  • node = tdr, jinft, jinj, jlvl1
  • name = versnumber = same name as in Philipp list i.e. 3ee3, MUST be THE SAME as the first line in the contents of the file itself.

How to Load a new JINF-T/TDR firmware

Added:
>
>
  • Get the new dsp code in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/file_ node _ name.dat
  • copy the file as file.dat in : /home/ams/TrackerUser/AMSWireCommands/
  • edit the first line of the file.dat and set it as:
    • 2932 if it will be the default file for JINFT (will become 29F2)
    • 29F3 if it will be the default file for TDR
  • REMEMBER: when a DSP code is written in the flash it will be effectively used only if it is run afterwards.
 

How to Create a JINF-T/TDR config file

How to directly command a JINF/TDR

Revision 32009-12-09 - MatteoDuranti

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

Special Operations

Changed:
<
<

Filenames convention and history

>
>

Filenames convention and history:

 
Changed:
<
<

How to Load a new JINF firmware

>
>
The dsp codes are stored in : /home/ams/TrackerUser/AMSWireCommands/DspCodes/
 
Changed:
<
<

How to Load a new TDR firmware

How to Create a JINF config file

How to Create a TDR config file

>
>
the file name has to be file_ node _ name.dat
 
Added:
>
>
where:
  • node = tdr, jinft, jinj, jlvl1
  • name = versnumber = same name as in Philipp list i.e. 3ee3, MUST be THE SAME as the first line in the contents of the file itself.

How to Load a new JINF-T/TDR firmware

How to Create a JINF-T/TDR config file

 

How to directly command a JINF/TDR

-- PaoloZuccon - 03-Dec-2009

Revision 22009-12-05 - GiovanniAmbrosi

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

Special Operations

Added:
>
>

Filenames convention and history

 

How to Load a new JINF firmware

How to Load a new TDR firmware

Revision 12009-12-03 - PaoloZuccon

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

Special Operations

How to Load a new JINF firmware

How to Load a new TDR firmware

How to Create a JINF config file

How to Create a TDR config file

How to directly command a JINF/TDR

-- PaoloZuccon - 03-Dec-2009

 
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