FLEX OBJECTS in ATLAS Pixel Production Database



   The Flex Object part identifier has the format:

2021 00 nn vv xxxx

00 – Flex Hybrid + Modules subsystem code
vv – version number
xxxx – the identifier part to be put on the Flex Hybrid
nn – the assembly type:

 

nn

Item Category

Description

00

FlexBare

FlexBarePrototype

bare flex

00

FlexBareOnFrame

FlexBareProtOnFrame

bare flex on frame

00

FlexLoaded

FlexLoadedPrototype

flex on frame loaded with Rs and Cs

10

FlexMCC

FlexMCCPrototype

flex hybrid + MCC + pigtail

20

Module

ModuleFEIPrototype

Module 

 

The identification procedure for these objects is defined in
            Pixel Flex Hybrid and Module Bar Code Tracking (ATL-IP-AP-0008) document.
             

            "Mfr Ser No" is the hand written number on v3 and v4.x prototypes, e.g., v3-40.


Java application for FlexLoaded and FlexLoadedPrototype upload.

Please get applications-ASSM-PDB.zip and unzip it.  You need the following files:

            java application archive file ASSEMBLY.jar, which you should put to C:\PixelPDB
            and add it to CLASSPATH variable in the AUTOEXEC.BAT file:
set CLASSPATH=%CLASSPATH%;C:\PixelPDB\ASSEMBLY.jar
            or set up in:
Settings -> Control Panel -> System -> Advanced -> Environment Variables

command file LoadFlex.BAT to register and assembly FlexLoaded and FlexLoadedPrototype.

file LOAD.txt is an example of the input file containing flex components to load.

            You also can run the applications from command prompt:

C:\atlas\measurement > java LoadFlex username passwd filename flexserialnumber

 

Attention! Since June 2003 we upload both FlexLoadedPrototype and FlexLoaded Items. The application searches for Flex Item type (by 6 last digits you have input). If it is FlexBareProtOnFrame the application creates FlexLoadedPrototype, if it is FlexBareOnFrame it creates FlexLoaded.

Please update your ASSEMBLY.jar file if it is older than October 2003!


Important!


             Please pay attention that to be able to run this application:

1.      You must be the owner of all the Items-components.

2.      The Items FlexBareOnFrame or FlexBareProtOnFrame assembly MUST have been registered before,
they will be renamed to FlexLoaded or FlexLoadedPrototype.
.


Java application for FlexMCC and FlexMCCPrototype upload.

 

The java application for FlexMCC and FlexMCCPrototype upload is located in the same package as the applications for Module and Bare Module uploads.

Please get applications-MODULE-PDB.zip and unzip it.  You need the following files:

            java application archive file MODULE.jar, which you should put to C:\PixelPDB
            and add it to CLASSPATH variable in the AUTOEXEC.BAT file:
            set CLASSPATH=%CLASSPATH%;C:\PixelPDB\MODULE.jar
            or set up in:
            Settings -> Control Panel -> System -> Advanced -> Environment Variables

command file LoadFlexMCC.BAT to register and assembly FlexMCC and FlexMCCPrototype.

            You also can run the applications from command prompt:

C:\atlas\measurement > java LoadFlexMCC

 

Attention! Since June 2003 we upload both FlexMCCPrototype and FlexMCC Items. The application searches for Flex Item type (by 6 last digits you have input). If it is FlexLoadedPrototype the application creates FlexMCCPrototype, if it is FlexLoaded it creates FlexMCC.

Please update your MODULE.jar file if it is older than June 2003!


Important!


             Please pay attention that to be able to run this application:

             1. You must be the owner of all the Items-components.
             2. The Item-assembly (FlexMCC or FlexMCCPrototype) must NOT have been registered before.




        See General Help to learn more about java applications.