Trouble-shooting

1. Common problems

The graphical display doesn't show an object properly assigned.

This is common symptom that you gave the same number to two or more different objects in your hydra file. Check the number and make sure it is unique.

2. Hydra Error Messages

Hydra error messages start with the word ERROR followed by a sequence of collon separated list of precedure names and explanatory messages. Most of the time is the last part of the message the one that gives more information about what's wrong with the system.

ERROR: ... : already running or not initialized -

The system returns this error message when the user attempt to execute a Galil box macro while the same Galil macro is under execution. Following are examples of real error messages of this type.

ERROR: gripin: couldn't bring gripper in: gripIn: ColdStart: st_sequence: boxCold: already running or not initialized
ERROR: home: HomeMotors: st_sequence: boxGhome: already running or not initialized
ERROR: move: unresolved: buttonPresent: unable to test: st_sequence: boxIfButt: already running or not initialized
ERROR: tempsense: can't sense temperature: st_sequence: boxTemp: already running or not initialized

ERROR: ... : can't grab the box -

The system returns this error messages when the user attempt to execute a Galil box macro while another Galil box macro is under execution. Following are examples of reat error messages of this type.

ERROR: bump: offsetToXY: unresolved: buttonPresent: unable to test: st_sequence: boxIfButt: can't grab the box
ERROR: coldstart: led: st_sequence: boxLed: can't grab the box
ERROR: gripin: couldn't bring gripper in: gripIn: ColdStart: st_sequence: boxCold: can't grab the box
ERROR: gripout: buttonPresent: unable to test: st_sequence: boxIfButt: can't grab the box
ERROR: minit: InitMotors: st_sequence: boxGinit: can't grab the box
ERROR: move: unresolved: buttonPresent: unable to test: st_sequence: boxIfButt: can't grab the box
ERROR: park: buttonPresent: unable to test: st_sequence: boxIfButt: can't grab the box
ERROR: plate: st_sequence: boxIsWarpd: can't grab the box
ERROR: plate: st_sequence: boxPlate: can't grab the box
ERROR: view: buttonPresent: unable to test: st_sequence: boxIfButt: can't grab the box

ERROR: ... : NoResponse -

The system returns this error message when a Galil box macro command has been succesfully written to the serial port, but no response was received in the last 25 seconds. The last under the assumption that no operation takes longer than that. Following are examples of real error messages of this type.

ERROR: brakes: Brakes: st_sequence: boxBrakes: NoResponse
ERROR: coldstart: ColdStart: st_sequence: boxCold: NoResponse
ERROR: coldstart: led: st_sequence: boxLed: NoResponse
ERROR: gox: unresolved: buttonPresent: unable to test: st_sequence: boxIfButt: NoResponse
ERROR: goz: no motion: GoToZ: can't move: st_sequence: boxzgo: NoResponse
ERROR: gripin: couldn't bring gripper in: gripIn: ColdStart: st_sequence: boxCold: NoResponse
ERROR: gripout: buttonPresent: unable to test: st_sequence: boxIfButt: NoResponse
ERROR: home: HomeMotors: st_sequence: boxXYhome: NoResponse
ERROR: home: HomeMotors: st_sequence: boxZhome: NoResponse
ERROR: home: HomeMotors: st_sequence: boxGhome: NoResponse
ERROR: minit: InitMotors: st_sequence: boxGinit: NoResponse
ERROR: minit: InitMotors: st_sequence: boxXYinit: NoResponse
ERROR: minit: InitMotors: st_sequence: boxZinit: NoResponse
ERROR: move: unresolved: buttonPresent: unable to test: st_sequence: boxIfButt: NoResponse
ERROR: move: MoveButt: unknown error: st_sequence: boxMove: NoResponse
ERROR: openwide: OpenWide: st_sequence: boxOpen: NoResponse
ERROR: park: ParkButt: MoveButt: unknown error: st_sequence: boxMove: NoResponse
ERROR: park: buttonPresent: unable to test: st_sequence: boxIfButt: NoResponse
ERROR: plate: st_sequence: boxPlate: NoResponse
ERROR: view: buttonPresent: unable to test: st_sequence: boxIfButt: NoResponse
ERROR: view: buttonview: ViewButt: GoToXY: can't move: st_sequence: boxxygo: NoResponse

The error message above may indicate problems in the serial link between Hydra Instrument and its host computer.

Check that the Galil Box is up and running and that the serial link is OK. Try the ping command to test the link. If it works then the Galil Box might be in error condition. Try cycling the power.

ERROR: ... : NoDrive -

This error message indicates that the drive power is off. Following are examples of real error messages of this type.

ERROR: gripout: gripOut: no xy motion: GoToXY: can't move: st_sequence: boxxygo: NoDrive
ERROR: minit: InitMotors: st_sequence: boxZinit: NoDrivePower
ERROR: view: buttonview: ViewButt: GoToXY: can't move: st_sequence: boxxygo: NoDrive

ERROR: ... : NoZInit -

This error message indicates that the Z motor was not properly initialize during a cold start sequence (i.e. coldstart and gripin commands). During a cold start sequence the Z motor is powered up and then initialized to its zero point. Following are examples of real error messages of this type.

ERROR: coldstart: ColdStart: st_sequence: boxCold: NoZInit
ERROR: gripin: couldn't bring gripper in: gripIn: ColdStart: st_sequence: boxCold: NoZInit

To figure out what exactly caused the problem try manually initializing the motor using the minit z command and the home z command. Then look for the new error messages in this trouble shooting guide.

ERROR: ... : NoHome -

This error message indicates that the motor was unable to find the fiducial point. The motor is then probably at one of its limits. Following are examples of real error messages of this type.

ERROR: gripout: gripOut: HomeMotors: st_sequence: boxZhome: NoHome
ERROR: home: HomeMotors: st_sequence: boxZhome: NoHome

Unfortunately often this failure to find the fiducial hangs the Galil built in macro to find the zero point and prevent the box from answering to further command macro requests. Below is a crude procedure to try to clear this fault.

1. ping the Galil Box with the ping command. If the Galil Box answer a bunch of numbers then you know at least the box is alive. If not then try resetting the box and start over again.
   Fiborg3.2.5> ping
   0000000 0000000 000000000 0000000 0000000\r
    
2. Then repeat the home procedure for the axis in trouble (more probably Z in the Hydra system) using the home command. If the answer is ok then the motor is working again. If the answer is NoResponse is still trying to find the zero point. If the answer is NoHome go back to step 1.
   Fiborg3.2.5> home z
   ERROR: home: HomeMotors: st_sequence: boxZhome: NoResponse
    
3. Reset the Galil Box by software using the "lit RS" command. This command will send the built in command RS to the Galil Box to reset the box. All the variable values set at program startup time will be cleared.
   Fiborg3.2.5> lit RS
   :
4. Try initializing the motor again using the minit command and then the home command. If the answer is ok the motor is working again. If the answer is NoResponse go back to step 3. If the answer is NoHome go back to step 1.

If the above doesn't work you might have to check hardware issues like drive power, limit switches, optical switch, etc.

ERROR: ... : FsaOrthoRFL2 -

This error message indicates that at least one of the following safety intelock signals has been activated: FSA interlocks, orthogonality switch, forward and reverse X-Y limits. Following are examples of real error messages of this type.

ERROR: goxy: no motion: GoToXY: can't move: st_sequence: boxxygo: FsaOrthoRFL2
ERROR: gripout: gripOut: no xy motion: GoToXY: can't move: st_sequence: boxxygo: FsaOrthoRFL2
ERROR: view: buttonview: ViewButt: GoToXY: can't move: st_sequence: boxxygo: FsaOrthoRFL2

Each of the interlocks mentioned above are AND gated before input to the Galil Box. So when the this error message occurs all three possible causes has to be checked, that is, check that the FSA is properly closed, check that the second forward and reverse limits are clear and check that the system is orthogonal. Read the listTI command documentation since it can be of great help when dealing withi problem.

ERROR: ... : Inhibited -

This error message indicates that the stages had not been initialized. Use the coldstart command to initialize the system. Following are examples of real error messages of this type.

ERROR: goxy: no motion: GoToXY: can't move: st_sequence: boxxygo: Inhibited
ERROR: gripout: gripOut: no xy motion: GoToXY: can't move: st_sequence: boxxygo: Inhibited
ERROR: view: buttonview: ViewButt: GoToXY: can't move: st_sequence: boxxygo: Inhibited

ERROR: ... : BelowHome -

This error message appears when the system has been commanded to move while the gripper is below its home position. The home position for the gripper is high enough to clear the fibers on the field as well as the fiber slots. Following are examples of real error messages of this type.

ERROR: dropit: releaseHere: DisposeButt: GoToXY: can't move: st_sequence: boxxygo: BelowHome
ERROR: park: ParkButt: DisposeButt: GoToXY: can't move: st_sequence: boxxygo: BelowHome
ERROR: view: buttonview: ViewButt: GoToXY: can't move: st_sequence: boxxygo: BelowHome

To clear this problem move the gripper up at least to its home position. In order to do that you can either home the gripper with the coldstart command or move it with the goz command and a positive value.

ERROR: ... : AxisFailure -

This error message indicates that an error ocurred during the initialization of the x and y motors. Following are examples of real error messages of this type.

ERROR: home: HomeMotors: st_sequence: boxXYhome: AxisFailure

Use the listTI command to figure out which of the motors is causing the problem and why.

ERROR: ... : ButtonOnInit -

This message indicates that the system has found a button in the gripper at the moment of initialization. You may have to follow a recovery procedure to drop the button before initializing the system. Following are examples of real error messages of this type.

ERROR: coldstart: ColdStart: st_sequence: boxCold: ButtonOnInit
ERROR: gripin: couldn't bring gripper in: gripIn: ColdStart: st_sequence: boxCold: ButtonOnInit

The recovery procedure starts by initializing the gripper motor and the Z axis motor using the minit command and then the home command for each axis.

For example to initialize the axis:

Fiborg3.2.5> minit gripper
Fiborg3.2.5> home gripper
Fiborg3.2.5> minit z
Fiborg3.2.5> home z

The second step is to drop the button by using the dropit command. It may be necessary to issue the command several times before the system
drop the button. If no success open the gripper to its wide open position and try removing the button from the gripper jaws manually.

ERROR: ... : NoMotion -

This message appear when the motor is not able to finish its motion. Try the listTI command for more diagnosis information. Following are examples of real error messages of this type.

ERROR: goz: no motion: GoToZ: can't move: st_sequence: boxzgo: NoMotion

ERROR: gripper is disabled, use gripin to activate -

This message appear when a the system has been ordered to move the stages while the stages are at their park position. Following are examples of real error messages of this type.

ERROR: bump: offsetToXY: GoToXY: gripper is disabled, use gripin to activate
ERROR: goxy: no motion: GoToXY: gripper is disabled, use gripin to activate
ERROR: move: MoveButt: gripper is disabled, use gripin to activate
ERROR: park: ParkButt: MoveButt: gripper is disabled, use gripin to activate
ERROR: view: buttonview: ViewButt: GoToXY: gripper is disabled, use gripin to activate

Activate the gripper either by using the GUI button or typing the gripin command

ERROR: please wait a few seconds and try again -

This message appear if the user has tried to activate the gripper too soon after parking it. For some unknown reason the motor drives have to rest a few seconds after been turned off to prevent the Galil Box to run into a fault condition. Following are examples of real error messages of this type.

ERROR: coldstart: ColdStart: please wait a few seconds and try again
ERROR: gripin: couldn't bring gripper in: ColdStart: please wait a few seconds and try again

ERROR: ... : target is beyond X-Y limits -

This message appear when the user tries to move the gripper to a non valid position. Following are examples of real error messages of this type.

ERROR: bump: offsetToXY: GoToXY: target is beyond X-Y limits

ERROR: ... : fiber <fiber number> doesn't physically exists... -

This message tell the user he has tried to move a fiber that has been marked as "non existant" in the concentricities configuration file. Following are examples of real error messages of this type.

ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: fiber #102 doesn't physically exists...
ERROR: configure: mqu_orderMoves: ERROR: physmove: MoveButt: fiber #2 doesn't physically exists...
ERROR: configure: orderMoves: ERROR: physmove: MoveButt: fiber #2 doesn't physically exists...
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: fiber #232 doesn't physically exists...
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: physmove: MoveButt: fiber #232 doesn't physically exists...
ERROR: move: MoveButt: fiber #10 doesn't physically exists...
ERROR: park: ParkButt: MoveButt: fiber #102 doesn't physically exists...

Check the concentricities configuration file for more information about the fiber.

ERROR: ... : button 249 is not stowed -

This error message tell the user he has tried to stowed a fiber that is not actually stowed, that is, is not at its fiducial position in the plate. Following are examples of real error messages of this type.

ERROR: unstow: Unstow: button 249 is not stowed

ERROR: ... : can't move with plate warped -

This message appear when the user tries to move a fiber with the plate at its warp position. Following are examples of real error messages of this type.

ERROR: configure: can't move with plate warped
ERROR: move: can't move with plate warped
ERROR: park: can't move with plate warped

Use either the GUI button or the plate command to unwarp the plate.

ERROR: ... : invalid move requested for button <button number> -

This message appear when the user tries to move a fiber to a non-valid position. The actual reason why the target position is not valid can be found at the xterm window from which hydractio was launched. Following are examples of real error messages of this type.

ERROR: configure: mqu_orderMoves: ERROR: physmove: invalid move requested for button #207
ERROR: configure: orderMoves: ERROR: physmove: invalid move requested for button #159
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: physmove: invalid move requested for button #88
ERROR: move: invalid move requested for button #0

ERROR: ... : it's not safe to grab button at current location -

This message tell the user that the position that the known position of the fiber is out of bounder. Following are examples of real error messages of this type.

ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: it's not safe to grab button at current location
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: it's not safe to grab button at current location

This is a very unusual error message and may be an indication that the Galil Box variables that are set the first time the application starts up has been corrupted some how or the result of incorrect use of either thisis or ThisIs recovery commands.

ERROR: ... : couldn't pick up button <button number> -

This message tell the user that the system failed in grabing the specified button. Following are examples of real error messages of this type.

ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: couldn't pick up button 1
ERROR: configure: mqu_orderMoves: ERROR: physmove: MoveButt: couldn't pick up button 101
ERROR: configure: orderMoves: ERROR: park: ParkButt: MoveButt: couldn't pick up button 159
ERROR: configure: orderMoves: ERROR: physmove: MoveButt: couldn't pick up button 247
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: couldn't pick up button 0
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: physmove: MoveButt: couldn't pick up button 7
ERROR: move: MoveButt: couldn't pick up button 0
ERROR: park: ParkButt: MoveButt: couldn't pick up button 84

To actually pick up the button we recommend using the thisis or ThisIs command to correct the known coordinates of the software. You will have to cruise around and center the gripper on top of the button and then issue one of the two commands. Then park the button.

ERROR: ... : gripper has no button to drop -

This message indicate that the button was lost during the move. This is a very dangerous situation sice is not possible to know were the button was left. Following are examples of real error messages of this type.

ERROR: configure: orderMoves: ERROR: physmove: MoveButt: gripper has no button to drop
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: gripper has no button to drop
ERROR: fieldsetup2: ERROR: configure: mqu_orderMoves: ERROR: physmove: MoveButt: gripper has no button to drop
ERROR: move: MoveButt: gripper has no button to drop
ERROR: park: ParkButt: MoveButt: gripper has no button to drop

You can use the gripper camera two see if you can find the button and then update its last known coordinates to its current position with the ThisIs command . The other way to go is to manually stow the fiber and then tell the software with the xstowed command that the fiber is now stowed.

ERROR: ... : couldn't drop button <button number> -

This message tell the user that the gripper still has the button in the gripper after trying to drop it at its target position. Following are examples of real error messages of this type.

ERROR: configure: mqu_orderMoves: ERROR: park: ParkButt: MoveButt: couldn't drop button 88
ERROR: configure: mqu_orderMoves: ERROR: physmove: MoveButt: couldn't drop button 174
ERROR: dropit: releaseHere: DisposeButt: DropButt: couldn't drop button!
ERROR: move: MoveButt: couldn't drop button 170
ERROR: park: ParkButt: DisposeButt: DropButt: couldn't drop button!
ERROR: park: ParkButt: MoveButt: couldn't drop button 103

Try releasing the fiber using the dropit command. This command will try to cleanly release the fiber at the current gripper position. Try it several times, sometimes takes more than one try to release the offending fiber.
If the above doesn't work you can still try opening the gripper jaws to their open wide position using the openwide command. This command will open the jaws more than usual hopefully releasing the button. If not then try releasing it manually.

ERROR: dropit: why drop a button that is not there -

This message tell the user that there is no button in the gripper to drop.

ERROR: The software thinks another button is already at this location -

This message tell the user that the software has a record of another fiber at the current gripper position when using the thisis command . This prevents from giving a button the coordinates of another button.

ERROR: ... : fiber in jaws - this message appear when trying to park the gripper while holding a button in the gripper. Following is an example of this type of message.

ERROR: gripout: fiber in jaws

ERROR: ... : can't move button # with # in transit -

This message tell the user that te system won't move any other fiber until he resolves the problem with a lost fiber. Following is an example of this type of message.

ERROR: configure: mqu_orderMoves: ERROR: physmove: can't move button 0 with 168 in transit

You will have to find the lost fiber and then update its current location with the thisis or ThisIs command. Only then you will be able to continue moving fibers. Not knowing the lost fiber position can result in fiber collisions.

ERROR: ... : temperature is to large/small -

The read temperature value is out of range. You can override the read value by manually entering the temperature value using the themval command. Following are some examples of this type of message.

ERROR: tempsense: can't set current temperature: ERROR: thermval: temperature is to large/small

ERROR: ... : unable to do the transition. Please ... -

This message tell the user that it was not possible for the software to do a transition from its current configuration to the one specified by the assignment file. The error message now includes information about the offending fiber. Following are examples of real error messages of this type.

ERROR: configure: mqu_orderMoves: ERROR: transition: unable to do the transition. Please check your assignment file for invalid moves.
ERROR: transition: unable to do the transition. Please check your assignment file for invalid moves.

The short way to solve this problem is to comment out the line in your assignments file containing the offending fiber assignment. The long way is to run hydraassign and get new assignments for the objects in the file.

ERROR: Attempt to load a null astrometry param file -

The init file astroparams is corrupted or the environment variable that holds the path to the file is undefined. Check your environment for the ASTROPARAMS environment variable, check you read permissions to the astroparams file and check that the file actually exists.

ERROR: Attempt to load a null system param file-

The init file systemparams is corrupted or the environment variable that holds the path to the file is undefined. Check your environment for the SYSTEMPARAMS environment variable, check you read permissions to the systemparams file and check that the file actually exists.

the transition program was unable to open the script containing fiber moves.
ERROR: configure: mqu_orderMoves: ERROR: transition: hydra file "parkall" not found.
ERROR: transition: hydra file "parkall" not found.

ERROR: ... : transition couldn't find file... -

The transition program was unable to find the plate coordinates file created by the astrometry program. Following are examples of this type of message.

ERROR: configure: mqu_orderMoves: ERROR: transition: transition couldn't find file: "GM.1.out1.hydra.coords"
ERROR: transition: transition couldn't find file: "GM.1.out1.hydra.coords"

Check for error messages about the astrometry program.

ERROR: ... : <file name> doesn't exists -

the scpecified file name doesn't exist. Following are examples of this type of message.

ERROR: fieldsetup2: ERROR: aload: file /home/hydra/fields/GM.out2.hydra doesn't exists

ERROR: User interrupt while sourcing <script> -

The user interrupt the script execution by typing ^C. Following are examples of this type of message.

ERROR: User interrupt while sourcing largecircle

ERROR: no socket connection to FOPS guider -

This message tell the user that no connection was opened to the FOPS guider. Check the ethernet connection and check that the FOPS guider program is actually running.

ERROR: guider: can't send command to guider -

This message tell the user that the program failed to send the command to the FOPS guider. Check the ethernet connection and check that the FOPS guider program is actually running.

ERROR: guider: can't read guider response -

This message tell the user that the program failed to read the command response coming from the FOPS guider. Check the ethernet connection and check that the FOPS guider program is actually running.

 

Last Modified: May 9, 2000
rcantarutti