TANGO
Device Server
Device Server
|
|
|
|
|
|
Device Server |
| |
|||
| dataRecorderPartialMode: if true, the scanserver only calls WriteScanData on the DataRecorder, but not StartRecording, ..., EndRecording | |||
| filePath: the path where to save the data | |||
| fileBaseName: the name of the file (will be completed by the current hour and the extension) | |||
| fileExtension: the extension of the file | |||
| runName: a descriptive string for the run (will be recorded in Nexus) | |||
| pointNumber: Current number of points performed for the current scan | |||
| pointNumber2: Current number of points performed for the current scan | |||
| scanNumber: Write -> Number of scan to do Read -> Current number of scan performed for this run |
|||
| actuatorsDelay: Waiting time after all actuators have finished moving, in seconds. | |||
| timebasesDelay: Waiting time after all timebases have finished counting, in seconds. | |||
| manualMode: if true, a PAUSE is done at the end of each step of the scan | |||
| automaticDirection | |||
| zigzag: If true, 2D mesh-scan are done in zigzag (even and odd lines are executed in inverse directions) | |||
| onTheFly: If true, do not wait for actuators at each step : instead, send the actuators to their last position and acquire sensor data on the fly during the movement | |||
| hwContinuous | |||
| hwContinuousNbPt | |||
| enableScanSpeed | |||
| scanType: 0 -> timescan 1 -> scan 1d 2 -> scan 2d | |||
| contextValidation: The boolean attribute used to check the context validity | |||
| contextValidationErrorStrategy: Error Strategy of the Context Validation: 0 -> IGNORE : Scan stays at current point scan and continues with sensors integration 1 -> PAUSE (or WAIT) : WAIT the Validity of the context to be VALID 2 -> ABORT : The Run stops immediately |
|||
| actuatorsTimeOut: Timeout for the Actuators positioning, in seconds | |||
| actuatorsRetryCount: the number of times to try to write actuator value | |||
| actuatorsRetryTimeout: the time between two retry | |||
| actuatorsErrorStrategy: Error Strategy of the Actuators: 1 -> IGNORE : Scan stays at current step scan and continues with sensors integration 3 -> NEXTPOINT : Scan jumps to the next point of scan 4 -> NEXTSCAN: Run jump to the next scan. 5 -> ABORT : Run stops immediately |
|||
| timebasesTimeOut: Timeout for the Timebases integration, in seconds | |||
| timebasesRetryCount: the number of times to try to start a timebase | |||
| timebasesRetryTimeout: the time between two retry | |||
| timebasesErrorStrategy: Error Strategy of the Timebases: 1 -> IGNORE : Scan stays at current step scan and continues with sensors integration 2 -> RETRY : Retry to write the actuator 3 -> NEXTPOINT : Scan jumps to the next point of scan 4 -> NEXTSCAN: Run jump to the next scan. 5 -> ABORT : Run stops immediately |
|||
| sensorsTimeOut: Timeout for the Sensors reading, in seconds | |||
| sensorsRetryCount: the number of times to try to read sensor value | |||
| sensorsRetryTimeout: the time between two retry | |||
| sensorsErrorStrategy: Error Strategy of the Sensors: 1 -> IGNORE : Scan stays at current step scan and continues with sensors integration 2 -> RETRY : Retry to write the actuator 3 -> NEXTPOINT : Scan jumps to the next point of scan 4 -> NEXTSCAN: Run jump to the next scan. 5 -> ABORT : Run stops immediately |
|||
| hooksTimeOut: Timeout for the HookServers response, in seconds | |||
| hooksRetryCount: the number of times to try to execute a hook | |||
| hooksRetryTimeout: the time between two retry | |||
| hooksErrorStrategy: Error Strategy of the HookServers: 1 -> IGNORE : Scan stays at current step scan and continues with sensors integration 2 -> RETRY : Retry to write the actuator 3 -> NEXTPOINT : Scan jumps to the next point of scan 4 -> NEXTSCAN: Run jump to the next scan. 5 -> ABORT : Run stops immediately |
|||
| afterRunActionType: 0 -> No action 1 -> First Scan Position 2 -> Prior Scan Position | |||
| afterRunActionSensor | |||
| afterRunActionActuator | |||
| afterRunActionActuatorValue | |||
| runStartDate | |||
| scanStartDate | |||
| scanEndDate | |||
| runEndDate | |||
| scanDuration | |||
| runDuration | |||
| scanRemainingTime | |||
| runRemainingTime | |||
| scanElapsed | |||
| runElapsed | |||
| runCompletion: % of completion [0 - 100] | |||
| scanCompletion: % of completion of the current scan [0 - 100] | |||
| deadTime: the total dead time of the current scan | |||
| deadTimePercent: the percentage of dead time of the current scan | |||
| deadTimePerPoint: the dead time of the current scan, per scan point | |||
| |
|||
| actuators: List of the actuators of the 1st dimension | |||
| actuators2: List of the actuators of the 2nd dimension | |||
| sensors: List of the Sensors | |||
| timebases: List of the Timebases | |||
| integrationTimes: Integration Time in seconds for all points of the trajectory | |||
| scanSpeed | |||
| preRunHooks: List of the Pre-Run Hooks names | |||
| preScanHooks: List of the Pre-Scan Hooks names | |||
| preStepHooks: List of the Pre-Step Hooks names | |||
| postActuatorMoveHooks: List of the Post-Actuator-Move Hooks names | |||
| postIntegrationHooks: List of the Post-Integration Hooks names | |||
| postStepHooks: List of the Post Step Hooks names | |||
| postScanHooks: List of the Post Scan Hooks names | |||
| postRunHooks: List of the Post Run Hooks names | |||
| actuatorsDataList | |||
| actuators2DataList | |||
| sensorsDataList | |||
| |
||||
| trajectories: Desired trajectory of the actuators of the 1st dimension. X -> trajectory Y -> actuators |
||||
| trajectories2: Desired trajectory of the actuators of the 2nd dimension. X -> trajectory Y -> actuators |
||||
| historic: Log messages of the last scan | ||||
TANGO is an open source project hosted by :
|
Core and Tools :
CVS repository on
tango-cs project
Device Servers : CVS repository on tango-ds project |