![Dectris MYTHEN Interface Manual Download Page 31](http://html1.mh-extra.com/html/dectris/mythen/mythen_interface-manual_2462219031.webp)
Socket Interface Specification. MYTHEN Detector System. Version: 2
31/34
8.1.2. Migration notes
If you migrate from version 2 take care of the following changes:
For optimal flatfield correction, the X-ray energy has to be specified.
After initialization all modules are selected
Commands retrieving module specific information return the values for all values.
The “-kthresh” commands only accepts arguments within the range supported by the specific MYTHEN
system.
Since the gain automatically changes with the threshold energy, the number of bad channels can change
with the specified threshold energy.
The “-autosettings” command is deprecated. Please use “-kthreshenergy” instead.
The commands “-get settings” and “-get settingsmode” are deprecated.
The arguments “StdCu”, “HgCr”, … of the “-settings”command are deprecated.
8.1.3. Legacy2 mode
If for some reasons you are not going to migrate, you can enable the Legacy2 mode with the "-legacy2"
command. After having sent this command, the interface to the server is identical with version 2 and your software
will still run. Although the interface is the same, keep in mind that the calibration of the detector will be different
than for a system delivered with version 2. For example you will not see any differences in data acquired with
“StdCu” and “FastCu” settings, because these deprecated arguments are internally mapped to the same detector
settings. Furthermore there are upper and lower limits on the allowed threshold and energy ranges.
8.2. Version 2.1.0
The bad channel interpolation now supports neighboring bad channels. In this case the interpolated value
is equal to the average number of counts of the next lower and the next upper working channels. If there is
no next lower (upper) working channel, the number of counts of the next upper (lower) working channel is
used.
Different modules can now have different dead time constants for the rate correction. This fixes the first
known issue of version 2.0.5.
Increasing the number of active modules now works flawlessly, fixing the second known issue of version
2.0.5.
The rate correction is now applied before the flatfield correction.
8.3. Version 2.0.5
New command to get the assembly date of the system („-get assemblydate“).
8.4. Version 2.0.4
New commands (“-get sensorthickness”, “-get sensormaterial”, “-get systemnum”) to retrieve information about
the sensor and the system. If the information can not be found, one of the new error codes -20 and -21 is
returned. If you upgrade an older system to version 2.0.4, the sensor information will not be available.