polarization modulator controller user’s guide · project documentation document man-0014...

12
Project Documentation Document MAN-0014 Revision A Polarization Modulator Controller User’s Guide Austin Kootz Instrumentation Group March 14, 2017

Upload: others

Post on 18-Apr-2020

37 views

Category:

Documents


0 download

TRANSCRIPT

Project Documentation Document MAN-0014

Revision A

Polarization Modulator Controller User’s Guide

Austin Kootz Instrumentation Group

March 14, 2017

PMC User’s Guide

MAN-0014, Revision A Page ii

REVISION SUMMARY:

1. Date: 14 April 2016 Revision: Draft 1 Changes: Initial release with Alpha_0

2. Date: 13 March 2017 Revision: Draft 2 Changes: Updated for Beta_0 release

3. Date: 26 April 2017 Revision: Draft 3 Changes: Updated for Beta_1 release

4. Date: 12 January 2018 Revision: A Changes: Updated for PAC CDR, Section 4 modified. Initial formal release.

PMC User’s Guide

MAN-0014, Revision A Page iii

Table of Contents

1. DEPENDENCIES .................................................................................................. 1 1.1 CSF DEPENDENCIES ............................................................................................... 1 1.2 BASE DEPENDENCIES ............................................................................................ 1 2. INSTALLATION .................................................................................................... 2 2.1 CENTOS 7 INSTALLATION ....................................................................................... 2 2.1.1 Checkout from CVS and build ..................................................................................... 2 2.1.2 Running pacDevel ........................................................................................................ 2 2.1.3 Testing the installation................................................................................................. 3 2.1.4 Testing continuous modulation mode ........................................................................ 3 2.1.5 Testing discrete modulation mode.............................................................................. 3 2.1.6 Testing active mode ..................................................................................................... 3 2.1.7 Testing off mode........................................................................................................... 4 3. GUI OVERVIEW .................................................................................................... 5 3.1 DEFAULT GUI......................................................................................................... 5 3.1.1 Composite GUI ............................................................................................................. 5 3.1.2 The Status Screen ........................................................................................................ 5 3.1.3 The Submit Screen ....................................................................................................... 6 4. OVERVIEW OF PMC DIRECTORY STRUCTURE ............................................... 7 4.1 $ATST/ADMIN/PMC................................................................................................. 7 4.2 $ATST/RESOURCES/SCREENS/PAC/PMC .................................................................. 7 4.3 $ATST/SRC/JAVA/ATST/PAC/PMC ............................................................................ 7 4.4 $ATST/SRC/JYTHON/ATST/PAC/PMC ........................................................................ 7 4.5 $ATST/SRC/POWERPMAC/ATST/PAC/PMC................................................................. 7 5. SETTING UP THE DELTA TAU ........................................................................... 8 5.1 FACTORY RESET FIRST ............................................................................................. 8 5.2 GO THROUGH SYSTEM SETUP MENU .......................................................................... 8 5.3 THEN OPEN TUNING ................................................................................................. 8 5.4 BUILD TIMEBASE ..................................................................................................... 8 5.5 MISCELLANEOUS ..................................................................................................... 8 5.6 MOTION PROGRAMS ................................................................................................. 9 5.6.1 The Windows 7 VM ....................................................................................................... 9 5.6.2 The IDE .......................................................................................................................... 9 5.6.3 The Motion Programs ................................................................................................... 9

PMC User’s Guide

MAN-0014, Revision A Page 1 of 9

1. DEPENDENCIES

1.1 CSF DEPENDENCIES

The PMC System was built and tested using the Canary_10 release of CSF. For best guaranteed stability

use this release if possible. Please follow the instructions in SPEC-0022-2 Rev L for install information

for CSF.

1.2 BASE DEPENDENCIES

The PMC System was built and tested using the Canary_10 release of the Base repository. For best

guaranteed stability use this release if possible. Please follow the instructions in TN-0088 Rev K for

install information for Base.

1.3 QAS DEPENDENCIES

The PMC System was built and tested using the Canary_10 release of the QAS repository. For best

guaranteed stability use this release if possible.

PMC User’s Guide

MAN-0014, Revision A Page 2 of 9

2. INSTALLATION

2.1 CENTOS 7 INSTALLATION

On kernel 3.10.0 or newer.

2.1.1 Checkout from CVS and build

From $ATST

cd ..

Set CVSROOT to:

export CVSROOT=:pserver:[email protected]:/home/atst/src/pac

Log in to cvs:

cvs login

Pull

cvs checkout –P –r Beta_1 atst

Make the java classes for the pmc.

From $ATST

build classes

That should complete the checkout and build process for the pmc.

2.1.2 Running pacDevel

From $ATST

cd admin/pac/pmc

Next make a local copy of the pmcSite.config file from the template file:

cp pmcSite.config.template pmcSite.config

Note: The previous step must be done to populate the simulated connection information to the properties

database

Edit the pmcSite.config file to contain the needed information. This can be done by supplying text after

every open equal sign.

gedit pmcSite.config

OR

vim pmcSite.config

Once the local copy of pmcSite.config is filled in and complete, edit:

$ATST/admin/pac/pacSite.config

Change PMC_INSTALL="no" to PMC_INSTALL="yes”

From $ATST/admin/pac run:

./pacDevel --make-all

Now continue to testing the installation.

PMC User’s Guide

MAN-0014, Revision A Page 3 of 9

2.1.3 Testing the installation

From $ATST/bin

./pmcGui

The GUI window should appear. (see section 4.1.1 for screenshot)

Next, start up the PMC control system components by running:

./pmcUp

The GUI should show the components up and running. The icon in the upper left corner should turn

green. Enter a valid configuration into the config submission window. The following sections contain

example configurations that can be used to test the different pmc operation modes:

2.1.4 Testing continuous modulation mode

mod:mode = modulate

mod:reverse = true

mod:type = continuous

state:rate = 5

state:samples = 10

state: start = 1

state:t0 = yyyy-mm-dd tz

Example: 2017-01-01 -10

Note: Good practice is to make it recent, but anything after 1970-01-01 0 should work. This

argument can also accept many other string formats up to: yyyy-mm-dd hh:mm:ss:mm:nn tz

2.1.5 Testing discrete modulation mode

mod:mode = modulate

mod:reverse = true

mod:type = discrete

state:duration = 0.1

state:rate = 0.5

state:settings = 10,200,3000,40000,500000

state:start = 1

state:t0 = yyyy-mm-dd tz

Example: 2017-01-01 -10

Note: Good practice is to make it recent, but anything after 1970-01-01 0 should work. This

argument can also accept many other string formats up to: yyyy-mm-dd hh:mm:ss:mm:nn tz

2.1.6 Testing active mode

mod:mode = active

PMC User’s Guide

MAN-0014, Revision A Page 4 of 9

2.1.7 Testing off mode

mod:mode = off

PMC User’s Guide

MAN-0014, Revision A Page 5 of 9

3. GUI OVERVIEW

3.1 DEFAULT GUI

The default GUI is created and stored in $ATST/bin

3.1.1 Composite GUI

The GUI brought up by the command pmcGui is a composite screen containing both the status screen and

a basic configuration submission interface. These screens are created from templates during pmcDevel

that may be used in instrument GUIs. The individual screens are listed in sections 3.1.2 and 3.1.3. They

may be found in $ATST/resources/screens/pac/pmc/

3.1.2 The Status Screen

The Information displayed on the status screen is as follows:

Source: The name of the Polarization Modulator Controller.

Time: The timestamp of the most recent status event received.

Lifecycle: The lifecycle state of the PMC.

Health: The health of the PMC.

Simulated: This is intended to tell if the Delta-Tau motion controller is simulated, however, the

AdvancedMotionController is unable to provide that information, so the field will always report

false. Because this is something that hopefully will be implemented before the final release, it

will remain in the GUI.

Mode: The mode of the PMC

Type: The type of the PMC. Do not conflate this with the mode, Type defines the continuous or

discrete operation of the modulator.

PMC User’s Guide

MAN-0014, Revision A Page 6 of 9

Sync Time: The time at which the Modulator will be operating in the requested manner. If this

time is prior to the current time as displayed by the Time field, the modulator is ready for data

acquisition.

3.1.3 The Submit Screen

This screen is used to create and submit configurations to the PMC.

To add attributes to the configuration, select the desired attribute from the dropdown list. Then enter the

value for the attribute in the box below the dropdown menu.

To remove an attribute, select it in the “name | value” table on the right and then click the “Remove”

button on the left. The entire configuration can be cleared using the “Clear” button as well.

Once the configuration is complete click the “Submit” button to send the configuration to the PMC.

PMC User’s Guide

MAN-0014, Revision A Page 7 of 9

4. OVERVIEW OF PMC DIRECTORY STRUCTURE

4.1 $ATST/ADMIN/PAC

This directory contains pacDevel.

4.2 $ATST/ADMIN/PAC/PMC

This directory contains the requisite scripts and templates to run pacDevel for the pmc installation.

4.3 $ATST/RESOURCES/SCREENS/PAC/PMC

This is the source for the JES templates and screens used for the PMC.

4.4 $ATST/SRC/JAVA/ATST/PAC/PMC

This is where the java source code for the PMC controller is stored.

4.5 $ATST/SRC/JYTHON/ATST/PAC/PMC

This is the location of the test scripts and templates for the PMC

These can only be run after the QAS package has been installed.

4.6 $ATST/SRC/POWERPMAC/ATST/PAC/PMC

This is where the motion programs for each instrument’s PowerBrickAC are stored.

PMC User’s Guide

MAN-0014, Revision A Page 8 of 9

5. SETTING UP THE DELTA TAU

This section is for advanced users and should not be used without first contacting DKIST Support. This

section exists primarily of as a reference to track changes to the Delta Tau relative to the factory defaults.

The DeltaTau should be configured with the Version 2.1.1.3 firmware.

5.1 FACTORY RESET FIRST

1. in gpascii: $$$***

5.2 GO THROUGH SYSTEM SETUP MENU

1. make sure to update databases and accept at every step.

2. set phase frequency to 8.192kHz and servo frequency to 4096

3. update database after setting amplifier voltage update database is on the motor page

4. may need to be run several times at different start positions for the phase finding search to work properly.

5.3 THEN OPEN TUNING

1. set Sys.WpKey=$aaaaaaaa

2. set Sys.pAbortAll=0

3. set Motor[x].I2TSet=0

4. set PowerBrick[0].AdcAmpCtrl=$80000100 this sets the amp strobe rate and amp sample delay.

5. for current loop tuning, start with values of IiGain=1.2 and IpbGain=5

6. for motor tuning 5, 50, 0.02, 50, 250, 0

7. set Motor[x].PhaseFindingDac=250

8. set Motor[x].PhaseFindingTime=250

5.4 BUILD TIMEBASE

1. set Coord[x].TimeBaseSlew=1.0 (or greater)

2. set Gate3[0].EncClockDiv=3

3. set Gate3[0].Chan[x].EncCtrl=4

4. set EncTable[0].pEnc=PowerBrick[0].chan[x].ServoCapt.a

5. set EncTable[0].ScaleFactor=1000/32000/256

5.5 MISCELLANEOUS

1. set Motor[x].InPosBand=10 or less

2. set Motor[x].InPosTime=0 or any number of servo cycles

PMC User’s Guide

MAN-0014, Revision A Page 9 of 9

5.6 MOTION PROGRAMS

Motion programs can only be updated from the IDE, this requires several constructs.

5.6.1 The Windows 7 VM

This VM is provided with the PMC system. Configuring the VM is outside the scope of this manual.

5.6.2 The IDE

The IDE version that was used to create the delivered PMC system is 2.2.0.39

5.6.3 The Motion Programs

To acquire the motion programs from CVS, check out the PAC repository on the windows VM. Smart CVS

is a good tool for this use and is installed and configured on the delivered VM.

Set up the motion programs for the instrument by loading the project for the instrument into the DeltaTau

IDE from the $ATST/src/powerpmac/atst/pac/pmc/<inst> folder, then selecting “build and download all

programs” from the right click dropdown menu in the file tree.