New handel release
The following FalconX handel issues have been reported to XIA a few months ago:
F1: Firmware file path is not realtive to the INI file directory (as mentionded here: http://xia.com/Software/docs/handel-sitoro/1.1.16/handel-falconxn.html#fnref6)
F2: A previous gate pixel advance run in mapping mode messes up with the statistics of the next gate-filtered run in MCA mode (as mentioned here: http://support.xia.com/default.asp?W689 - ProSpect v1.1.16-FalconXn (2017-10-20) - Knwon issue)
F3: A buffer is reported as full even after the "buffer_done" command is sent. It's only reset when it starts being filled up again. That's not the current behavior for the mercury and the XMAP, and it's not so convenient to interface with since the software has to keep track of which buffers are "done".
F4: Handel seems to get stuck in a while loop when performing the next API call after the hardware is reset:
[...] [ERROR] 2017-11-08 16:51:34,177 falconXNSincResultToHandel (falconxn_psl.c:496) :  read failed [ERROR] 2017-11-08 16:51:34,177 psl__ModuleReceiver (falconxn_psl.c:7066) :  Read message failed for FalconXN connection: 192.168.200.201:8756 [ERROR] 2017-11-08 16:51:34,177 falconXNSincResultToHandel (falconxn_psl.c:496) :  read failed [ERROR] 2017-11-08 16:51:34,177 psl__ModuleReceiver (falconxn_psl.c:7066) :  Read message failed for FalconXN connection: 192.168.200.201:8756 [...]
F5: In MCA mode, spectrum data needs to be read first in order to get the statistics to update.
XIA recently made new handel releases that address most of those issues.
Fixed buffer reports full after buffer_done command
Simplified configuration management by storing all data in the INI file. Existing BIN files are loaded in place and saved to the new format in the next save.
Fixed the socket error/logging loop after resetting the box. Calling xiaStartSystem is required to reconnect, but in the interim errors are returned from API calls, the CPU does not spin, and the log file will not fill the disk.
Fixed MCA spectrum/statistics read order requirements. Both are available in real time in any order according to the latest data received from the FalconX on the mca_refresh interval.
Also related to the GATE veto feature, it is now disabled during characterization, to allow that process to reliably succeed regardless of prior GATE veto settings