XIA
Overview¶
Xia controllers can run in single point or continuous (aka mapping) acquisitions.
Supported controllers:
- Mercury
- FalconX
Todo
- LIVE, EVENTS, TRIGGERS preset modes
- USER and SYNC advance modes
Mosca to XIA
The conversion from mosca parameters to xia parameter is done in the function mosca.devices.xia.xia.Xia.apply_mosca
.
Source code in mosca/devices/xia/xia.py
330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 |
|
enum values
The given values for preset_value and gate_polarity settings are based on the enumeration defined in the XIA headers at the time of writing the documentation (and code...).
Single point acquisition¶
To configure the hardware to run a single point acquisition, acq_nb_points must be set to 1.
- realtime: the acquisition starts when the hardware is started, and runs for the given number of seconds (acq_realtime, measured by the hardware).
- freerun: the acquisition start as when the hardware is started, and runs until a stop is requested.
In both cases the acquisition can be inhibited with the gate (gate_mode).
Realtime run¶
Starts acquiring as soon as the hardware is started.
Mosca | Value |
---|---|
acq_nb_points | 1 |
run_mode | REALTIME |
acq_realtime | time in s |
gate_mode |
|
This translates into the following XIA settings:
XIA | Value |
---|---|
mapping_mode | 0.0 |
preset_type | 1.0 (XIA_PRESET_FIXED_REAL) |
preset_value | acq_realtime |
gate_ignore |
|
input_logic_polarity |
|
Free run¶
The acquisition time is controller by the user (start/stop).
Mosca | Value |
---|---|
acq_nb_points | 1 |
run_mode | FREERUN |
gate_mode |
|
This translates into the following XIA settings:
XIA | Value |
---|---|
mapping_mode | 0.0 |
preset_type | 0.0 (XIA_PRESET_NONE) |
gate_ignore |
|
input_logic_polarity |
|
Continuous (mapping) acquisition¶
To configure the hardware to run in mapping mode, acq_nb_points must be higher than 1.
Individual points (aka pixel) are completed ("advanced") either when a rising or falling edge is detector.
WIP: advance modes
XIA also support USER and SYNC advance modes, they are not supported yet.
Mosca | Value |
---|---|
acq_nb_points | >1 |
gate_mode |
|
stop_trigger |
|
block_size | >=1 |
This translates into the following XIA settings:
XIA | Value |
---|---|
mapping_mode | 1.0 |
num_map_pixels | acq_nb_points |
gate_ignore |
|
input_logic_polarity |
|
pixels_per_buffer | block_size |
Controller specific settings¶
FalconX¶
At the time of writing the documentation, the maximum value for nump_map_pixels is 1020. The FalconX has mca_refresh setting that can be set directly through the controller instance.
Mercury¶
n/a
Tango¶
The DS has three optional properties:
- default_ini_dir: default folder (ini_dir) into which look for ini files. If not provided, the default_ini_file directory will be used (if provided). If default_ini_file is not provided either, the current working directory is used.
- default_ini_file: default ini file (ini_file) to load at DS startup, if provided.
- lib_dir: folder containing the handel.dll library. If not provided, the one found (if any) in the system path will be used. If none is found, the DS will fail to start.
The DS has an attribute named ini_dir. It is used when available_configs is called.
When setting ini_file with a relative path, the DS will try to find it relative to ini_dir.
When setting ini_file with an absolute path, ini_dir will not be used.