SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf ·...

14
SWIFT: SWIFT Users Manual SWF- Fraser Clarke Version: 0.2 Date: 2009-04-29

Transcript of SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf ·...

Page 1: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT: SWIFT Users Manual

SWF-Fraser ClarkeVersion: 0.2

Date: 2009-04-29

Page 2: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14
Page 3: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 3 of 14

Version Date Author Comments

0.1 2008-12-08 FCl Created

0.1 2009-04-29 FCl Changes relevant for April/May 09run

Page 4: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 4 of 14

Contents

1 Introduction 5

2 Daily tasks check list 52.1 Every afternoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Every morning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Software Startup 63.1 Start up CCD PCI card drivers . . . . . . . . . . . . . . . . . . . . 63.2 Check disc space . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.3 Data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.4 DataDisplayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.5 SwiftUserGUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.5.1 Instrument Control Panels . . . . . . . . . . . . . . . . . . . 73.5.2 Instrument Monitoring Panels . . . . . . . . . . . . . . . . . 93.5.3 General Information . . . . . . . . . . . . . . . . . . . . . . 9

3.6 CCD control GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.7 Network Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Software Operation 94.1 Back up data from swiftws . . . . . . . . . . . . . . . . . . . . . . . 94.2 RTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.2.1 How to make reconstruction vectors . . . . . . . . . . . . . 104.3 Data Reduction Pipeline . . . . . . . . . . . . . . . . . . . . . . . . 10

5 Observing strategies 105.1 Position Angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2 Exposure times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3 Faint objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.4 AO flatmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.5 Focus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.6 Spectral “Features” . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5.6.1 9500A emission . . . . . . . . . . . . . . . . . . . . . . . . . 125.6.2 Emission “chains” . . . . . . . . . . . . . . . . . . . . . . . 125.6.3 Fringing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6 Trouble Shooting 126.1 IP addresses/can’t connect to swiftXX . . . . . . . . . . . . . . . . 126.2 TCS information not updating . . . . . . . . . . . . . . . . . . . . 126.3 Can’t offset telescope from TCSAO window . . . . . . . . . . . . . 136.4 REALLY can’t connect to the AO system . . . . . . . . . . . . . . 136.5 ArcVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6.5.1 Loss of communications with ArcVIEW . . . . . . . . . . . 136.5.2 ERROR 111 writing message . . . . . . . . . . . . . . . . . 136.5.3 ArcVIEW won’t shut down . . . . . . . . . . . . . . . . . . 146.5.4 Can’t restart a module . . . . . . . . . . . . . . . . . . . . . 14

Page 5: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 5 of 14

1 Introduction

This document is designed to be users manual for the Oxford SWIFT instrumentat the Palomar 200-inch telescope.

2 Daily tasks check list

Quick check list of daily startup/shutdown checks. More detailed descriptions ofeach proceedure are below.

2.1 Every afternoon

Good to do this before dinner. The dome is dark from 4pm.

• Check the cryostats have been filled (on white board in data room)

• Back up data from swiftws to DVD

• Check disc space on swiftws and swiftlcu

• Start up SwiftUserGUI

• Check/restart ArcVIEW

• Open up network power supply webpage. Check on/offs.

• Start/initalise sdsuGUI (after midday)

• Restart swift lcu2ws

• Restart/check datadisplayer master slave

• on swiftws & swiftlcu, move to current night’s data directory and restartrtdds9

• Take some short darks to check the read noise

• Take some standard calibrations (dome is dark from 4pm)

– darks, if you know your exposure times

– flats in all scales to be used

– arcs in all scales to be used

– trace in all scales to be used

– 5 bias frames (0 length darks)

2.2 Every morning

• disconnect from AO (Disconnect AO on TCS/AO panel)

• Take any calibrations you need (dome lights will be on from ∼7:30am)

• Check power off to all lamps

Page 6: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 6 of 14

3 Software Startup

Log into the SWIFT workstation (swiftws) and the SWIFT LCU (swiftlcu).

User: SWIFTPassword: ******** (see support)

To start up a terminal (terminal symbol in top bar, or Applications->SystemTools->Terminal).For the April/May 09 run, most software is being run directly on theswiftlcu

3.1 Start up CCD PCI card drivers

You should only have to do this after a reboot of the LCU.

• Log into swiftlcu

• cd astropci

• su (log in as root, note no ’-’)

• ./astropci load

• check that /dev/astropci0 and /dev/astropci1 exist

• exit root

3.2 Check disc space

Make sure the /home disc on swiftlcu is not too full, there should be at least8Gb free for a night’s observing. If it is too full, cd into the /home/swift/datadirectory and remove the oldest folders. Be sure they have been backed up!

Also worth checking swiftws, but the disc here is much larger.

3.3 Data transfer

Data transfer must be restarted every day, after the first file has beencreated

Data arrives from the CCD controllers onto the LCU. A copy of the data onthe LCU is maintained and should not be touched. An automated script transfersthe data from the LCU to the WS as soon as it arrives. To start this script;

Log into swiftlcu (user swift, usual password).run the script swift lcu2ws.sh & (note &).logout of swiftlcu

If the data do not transfer, it may be worth checking the IP address in the/etc/hosts file on swiftlcu matches up with the actual address of swiftws.

Page 7: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 7 of 14

Figure 1: SWIFT User GUI

3.4 DataDisplayer

To set up the data displayer, run ;datadisplayer.sh <master> <slave>from a terminal on swiftws, where <master> and <slave> are the prefix

of the two CCDs (normally “master” and “slave”). This will bring up two ds9windows (ds9isis and ds9cherwell) which will automatically display masterand slave images respectively as they arrive. Images are displayed with longwavelengths to the top of the image.

It is useful to keep the window running the datadisplayer visibile in all workspacesas a notifyier of when new images arrive on the WS. The ds9 windows from thisprocess seem to crash quite frequently. Just restart datadisplayer to fire them upagain

3.5 SwiftUserGUI

The SwiftUserGUI is the main interface for operations. It currently runs only onthe swiftlcu. To start up the GUI, run SwiftUserGUI on the swiftlcu. This willbring up a large window with several different sub panels, each of which shouldpopulate with a control panel.

There are three tabs; “Instrumnet Control Panels”, “Instrument MonitoringPanels” and “General Information”.

3.5.1 Instrument Control Panels

These panels are the main ones for controlling the instrument functions.

Page 8: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 8 of 14

3.5.1.1 TCS/AO control

This panel controls the interface to the AO and TCS. There are five tabs “TCS”,“AO”, “RTD”, “History” and “Config”. At the bottom of the window are fourbuttons giving the status of the connections. “Link up” shows the TCS/AO GUIis connected to ArcVIEW. “TCS on” & “AO on” show whether ArcVIEW isreceiving information from the AO/TCS systems respectively (these can be a bitunreliable unfortunately! A key test is to check if the “UTC-TCS” field is updat-ing every few seconds. This generally indicates everything is OK.). “Telescopestable” shows if the telescope is tracking.

TCS tab This panel interfaces with the TCS. Offsets can be applied fromthe N/S/E/W control. These offsets move the telescope (i.e. to move a star Easton the image, give the telescope a West offset). The U/D/L/R option is notfully tested, and may not work at high declination or different rotator positions.The maximum offset with AO loops closed is 7 arcseconds. If you need to movefurther, it is best to bootstrap it with two or more consecutive moves. Themaximum offset is 120 arcseconds (a safety feature in the GUI). It is always goodto check on the AO message window that the “pt” command was received withthe right offsets.

AO tab This tab interfaces with the AO system. You can open and closethe AO loops. Always close TT and then DM, and always open DM and thenTT. Make sure the DM and TT loops are open before telling the TO to slew thetelescope. If the AO system is going to be rebooted, “disconnect AO” first.

RTD tab This tab interfaces with the RTD ds9 window (rtdds9). Clickon “clear regions” to setup the rtd into “click and drag mode”. In this mode,you can click on a postion on the RTD, and drag a line to move the position(i.e. click on a star, and draw a line to the centre of the field). Clicking “GetRA/Dec offsets” retrieves the required shift from the RTD, and clicking “Apply”will move the telescope to put the object to the new position. Remember the 7arcsecond limit for loops closed offsets.

The “Get XY offsets” button probably doesn’t work correctly...

History tab This tab displays messages from ArcVIEW. Check here if youare having problems with sending offsets. Lots of “Failed to send cmd” messagesindicate ArcVIEW needs to be restarted.

Config Shouldn’t need to do anything here. Try “Reset TCS/AO link” ifyou’re having trouble talking to ArcVIEW.

3.5.1.2 Motor Control

This panel controls the position of the three moveable stages in SWIFT (imagescale, focal plane mask & input selection). Each motor has a drop down list ofpredefined positions. A bright green light next indicates the motor is on and inposition. Dark green indicates the motor is off. Red indicates the motor is notat the position indicated by the panel. Orange indicates the motor is moving.

Page 9: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 9 of 14

To move to a new position, select the position from the list (the light willturn red) and click “Move” (the light should turn orange). When the motion hasfinished, the light will turn green again. You can move all the stages simultane-ously.

“Sync” retrieves the actual motor position from the controller and updatesthe GUI. If the motor is in an undefined position, the angular position of themotor is returned.

After a power cycle, you may turn power on to the Motors. Use the “Com-mands” drop down menu. If the motors lose their reference, send the “Home”command.

The “Mask” and “Input” stages take ∼80s to make a full revolution. We havetried to put the common functions as close together on these stages. The “Scale”stage takes ∼30s for a full revolution.

3.5.2 Instrument Monitoring Panels

This tab shows the montoring information from the instrument; temperatures andpressures. Shouldn’t be anything to worry about. Check the temps occasionallyto make sure the coldplates are at 77K and the detectors are at 150K. If thecoldplates warm up, the cryostats need to be filled.

3.5.3 General Information

Currently only shows the 200-inch weather/temperature information.

3.6 CCD control GUI

The CCDs are controlled from a Python GUI.See Tim’s “how to drive the CCDs”

3.7 Network Power Supply

The network power supply is mounted in the electronics rack in the cass cage. Itsupplies power to all of the electronics units in the rack, and can be controlled viaa webpage. The main use is to turn on/off the calibration lamps. To access thepower supply, open a firefox web browser and go to the bookmarked “networkpower supply” on the navigation bar. The user/password are in the workstationcase. Select on/off for the function you want, and click “apply”. Remember toturn calibration lamps off after use.Make sure the “master con” and “slave con” options are always on!

4 Software Operation

4.1 Back up data from swiftws

Use the DVD burning programme GnomeBaker on the desktop of swiftws. Createa “new data DVD” project, and add the data director to it. Click to burn. Youmay need to split the data over multiple discs.

Page 10: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 10 of 14

4.2 RTD

4.2.1 How to make reconstruction vectors

If the reconstruction looks really bad, you may need to recalculate the recon-struction vectors. If this is the case please let Matthias or Fraser know; it impliessomething has moved in the instrument!. To recalculate them;

1. take a Halogen lamp frame with the vertical line mask in.

2. In IRAF, measure the position of the central trace for each slit (do this forboth master and slave)

• start at the bottom of the frame, low y values and work up.

• use the region around x=2000

• imexam + logging + ’k’ to fit a vertical guassian is pretty efficientmethod

• the slit spacing is 93 pixels, if you get confused about which line iswhich!

3. extract the y position of each trace from the log file.

4. Cat the y positions for the master and slave into one file (with 44 lines).These are the reconstruction vectors for the RTD.

5. You will probably find that the absolute position of the vectors are notright (the edge of the field isn’t at the edge of the reconstructed image).Play around with offsets for the master and slave parts vectors to adjustthis. I use awk ’print $1-N.N’ master.vectors > master.newvectorsto adjust the offset (where N.N is the offset).

6. A reconstructed image of the vertical line mask should have straight lines!

4.3 Data Reduction Pipeline

The data reduction pipeline is not a science grade pipeline at this stage, butshould take out basic instrument signatures and allow an analysis of data qualityat the telescope.

5 Observing strategies

Some hints and tips based on using SWIFT. This isn’t a complete list by anymeans, just a list of lessons learned.

5.1 Position Angle

Arghhhh!!!! Position angle confuses us. We usually get it wrong!The default position angle for SWIFT is North along the short axis of the

IFU, and East along the long axis of the IFU. The default Cassegrain rotatorangle for SWIFT is 15.9 degrees. This puts the master chip North and the slavechip South. The WCS information (i.e N-E arrows) on the RTD is reliable.

Page 11: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 11 of 14

health warning – this may be out by 90 degrees If the RTD is set todisplay the default image North up East left, then a positive move of the cassrotator moves the North arrow clockwise on the field. I.e. To aling the long axisof the slicer with a PA of 45 degrees North through East (equivilent to movingNorth arrow counterclockwise on field), you would subtract 45 degrees from therotator PA, giving cass rotator angle of -29.1 degrees (330.9).

5.2 Exposure times

The thick detectors in SWIFT are more sensitive to cosmics than normal CCDs.Maximum practical exposure time is 1800 seconds. It is sensible to “cosmic split”your integrations, and take at least 3 exposures to reject the cosmics.

The minimum exposure time is 0.1 seconds. Below this there are some effectsfrom sychronising the shutter with the CCD readout.

5.3 Faint objects

Faint objects, meaning those which can’t be seen in a single exposure. Thetelescope tracking is good, but not great. The errors in the pointing model meanthat the WCS information reported by the TCS can drift by 1arcsec/hour (theactual rate isn’t clear). This means that you cannot effectively use the WCSinformation to align a long sequence of images.

• Take an image of offset star. Something you can see in say a 60s exposure.

• Move the offset star to the place you want the target to be.

• When you are happy with the position, ask the TO to “tx here”. Thisresets the telescope coordinate system.

• Offset to your target and take some science frames.

• Every hour, at least, offset back to the star and take another exposure.Comparing this to the previous frames lets you measure the telescope track-ing error, and build up a model to align the science frames.

• repeat until you have enough science signal!

This applies both with and without AO. There is extra information in theAO headers which could be used to correct the effect, but it’s not available toSWIFT at present. We’ve asked the AO software people to change their softwareto make it available so that we can store it in the SWIFT FITS headers.

5.4 AO flatmap

The AO system can correct the static aberations of the primary mirror (quitesignificant) by making a “flatmap”. This should be done even if you are notusing AO correction for science. Ask the TO to make a new flat map every fewhours, or after every significant slew. You will also need a new flatmap if youchange the rotator angle.

Page 12: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 12 of 14

5.5 Focus

The focus of the telescope changes throughout the night. The effect can be quiterapid, depending on the temperature changes, and seems to be most significantin the first few hours of the night. To make sure the system is well focused, askthe TO to make a new flatmap for the AO system. This will measure the defocusand offload it to the telescope. It also corrects the primary mirror aberations. Ittakes about 5 minutes to run, slewing to a nearby bright star. Suggest doing thisevery hour at the start of the night.

If you are doing NGS AO, the focus is corrected constantly so the above isn’tnecessary.

5.6 Spectral “Features”

There are several spectral “features” in the SWIFT data.

5.6.1 9500A emission

There is a broad spectral feature roughly around 9500A covering 2/3 of the imageslicer field of view. This is most likely an LED scattering into the instrumentfrom somewhere. We haven’t managed to track it down yet!

5.6.2 Emission “chains”

There are several small emission features throughout the spectrum, taking theform of a “chain” at slight angle across the slices. We suspect these come fromflourescent lamps somewhere in the dome. The unwary and overexcitable observercan become very enthusiastic about clumpy rotating discs etc...

5.6.3 Fringing?

It looks like there is some fringing visible beyond 9600A. It is at quite a lowlevel, but high spatial frequency. Only noticable in frames with very high counts(i.e. flats)

6 Trouble Shooting

6.1 IP addresses/can’t connect to swiftXX

The SWIFT machines should be on fixed IP addresses (Table 1) and shouldnormally be addressed by their name rather than IP addresses. We have foundoccasionally the IP address has changed to something different (usually WS orLCU), which causes problems as the software cannot communicate. To fix this,either update the software/config files with the correct address, or (a more univer-sal fix), edit the /etc/hosts file with the new IP address (log onto the problemmachine locally, and type /sbin/ifconfig).

6.2 TCS information not updating

The link between the LCU and habor (AO computer) is not very stable, andoften does not close cleanly. The symptom of this is the TCS information not

Page 13: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 13 of 14

Machine normal IP purpose/location

swiftws 198.202.125.179 SWIFT workstation. User machine in the data roomswiftlcu 198.202.125.180 SWIFT control computer.swiftts 198.202.125.173 SWIFT terminal server. RS232-¿IP box in the electronics rack

swiftnps 198.202.125.174 SWIFT network power supply. Remote power switch in electronic rackswiftic 198.202.125.175 SWIFT Imaging Camera USB terminal server. Mounted on instrument

Table 1: SWIFT normal IP addresses. All machines are .palomar.caltech.edu

updating (look at the UTC value - if it does not change every second, the link isdead). To fix it, try the following;

Log into swiftlcu type: palao disconnect type palao connect You shouldget a message like OSWIFT AO connected on port NN (the port number varies).

If this does not work (usual symptom is the message OSWIFT AO not connected!),it usually means a restart of ArcVIEW.

The status buttons at the bottom of the TCSAO window are not always areliable indicator of the link unfortunately.

6.3 Can’t offset telescope from TCSAO window

Check the TCS information is updating and the link is still alive. If so, tcs isprobably disabled in ArcVIEW (a safety feature for daytime engineering). Toenable it, log into swiftlcu & type: palao tcs on

If the TCS is updating, and there are repeated “failed to send command”messages in the history tab, it’s likely ArcVIEW has become blocked up with arouge process. Probably worth a restart of ArcVIEW.

6.4 REALLY can’t connect to the AO system

Check that PHARO is not running; (ping ezra2.palomar.caltech.edu fromthe swiftlcu). PHARO and SWIFT share the same communications port withthe AO system, and only one can connect at any time. If PHARO is running,it can jump in and block the comms port. PHARO should be turned off duringSWIFT runs.

6.5 ArcVIEW

6.5.1 Loss of communications with ArcVIEW

This seems to happen occassionally, for no good reason. ArcVIEW continues torun, but you cannot communicate with it. Only solution seems to be a restart ofArcVIEW.

6.5.2 ERROR 111 writing message

This error occurs when the ArcVIEW TCP port is somehow blocked. I suspectthis is usually from a rouge process taking a while to timeout. It usually fixesitself after 10-20 seconds. If not, a reboot of ArcVIEW should clear it.

Page 14: SWIFT: SWIFT Users Manual - Astrophysics › instr › swift › pdfs › SWIFTUsersGuide.pdf · SWIFT Users Manual Version: 0.2 SWF- Date : 2009-04-29 Fraser Clarke Page : 3 of 14

SWIFT Users Manual Version: 0.2SWF- Date : 2009-04-29Fraser Clarke Page : 14 of 14

6.5.3 ArcVIEW won’t shut down

Occasionally one of the ArcVIEW modules (usually FITS header) will hang upand stop ArcVIEW shutting down cleanly. The only solution seems to be to findthe labview process and kill it;

$> ps -aux | grep labview$> kill XXXX (where XXXX is the process ID of labview)

6.5.4 Can’t restart a module

I don’t know why this doesn’t work anymore.... only solution is to restart Ar-cVIEW.