In any case, check that the detector entrance window is not damaged. If it is, power off the detector and contact Support

If only a single module is affected:

• could be an artefact, a blown fuse, or a module malfunction. Please send us at least one original image where the effect is visible using the Support Request Form. Please specify if the problem is persistent.

If the entire detector is affected:

• entire detector is has a tiled patter of very high and 0 values . Probably the humidity and/or temperature limit was exceeded.
  • Check Camserver for error messages
  • use command THread to enquirer conditions
  • ensure dry air and coolant flow
  • restart
  • if problem persists, contact Support and send an original image

Verify with an oscilloscope that the trigger pulse is present and that the high level is higher than 2.1 V. Never exceed 5 V! 

Check the Tech Specs for more details. The PILATUS EXT IN (Trigger Input) is terminated with 50Ω, your trigger source must be able to drive that load.

No physical link between detector and detector server. Check that:

• Detector is powered
• Undamaged CAT 6A S/FTP Ethernet cables, no longer than 30m are used and are properly connected
• Link LED must be lit. LEDis located in the RJ45 connector socket for PILATUS3 M sized detectors. LED is located in back panel and labeled "Link" for PILATUS3 K sized detectors.

If the above does not solve the issue, contact Support with a photo or output of error and the network Settings (ifconfig output).

Most likely data package was lost between the detector and the server. If this was a single occurence reboot the server and detector and restart Camserver. If it happens multiple times most likely a data cable is not meeting the specifications. This can be due to  minor damages or wear not visible from outside. Make sure that:

• Undamaged CAT 6A S/FTP Ethernet cables, no longer than 30m are used and are properly connected.
• Exchange all cables with the spare set or equivalent CAT 6A S/FTP Ethernet cables

If problems persist contact Support with the error output and a description of when it occurs and with what frequency.

In any case, check that the detector entrance window is not damaged. If it is, power off the detector and contact Support

If only a single module is affected:

• could be an artefact, a blown fuse, or a module malfunction. Please send us at least one original image where the effect is visible using the Support Request Form. Please specify if the problem is persistent.

If the entire detector is affected:

• entire detector is has a tiled patter of very high and 0 values . Probably the humidity and/or temperature limit was exceeded.
  • Check Camserver for error messages
  • use command THread to enquirer conditions
  • ensure dry air and coolant flow
  • restart
  • if problem persists, contact Support and send an original image

Verify with an oscilloscope that the trigger pulse is present and that the high level is higher than 2.1 V. Never exceed 5 V! 

Check the Tech Specs for more details. The PILATUS EXT IN (Trigger Input) is terminated with 50Ω, your trigger source must be able to drive that load.

Yes. To write e.g. that only the det user gets read and write permissions (600, rw - -) please add the line "umask 077" to the .bashrc in the /home/det directory. 

Try following steps:

• restart DAQ
• try to initialize

If the problem persists, send the rest_api.log to our support team.

After the exposure has ended no data was written or submitted. Make sure to check following points:

• Make sure the interface in question is enabled (filewriter, stream, monitor).
• Make sure the buffer of said interface isn't full.

• Filewriter is automatically disabled once the buffer is full.
• Stream and monitor data is lost when not read out.

If the problem persists send the corresponding logs (stream, rest, monitor, filewriter) to our support team.

Send a request to our support team for further analysis along with following information:

• all log files
• detector serial no.
• time of incident
• images with bad quality

• Make sure the chiller is fully functional.
• Check the dry air supply.

If the problem persists send the rest_api log and time of incident to our support team.

EIGER detectors only support in-vacuum operation if ordered as such. For more information please refer to our documentation.

For in-vacuum operation of the detector the following conditions must be fulfilled:

HTTP error 404: Not found - parameter xxx does not exist

• Initialize the detector.

HTTP error 400: Bad request – Upload data is corrupted / Undefined value for parameter nimages: Parameter is less than minimum

• Check correctness of the input value.

HTTP error 500:

• Is the detector running?
• Is the DCU running?

If you experience any issue with the signal quality, please send a detailed error description, all experimental parameters, the MYTHEN settings as well as raw data to our support team.

The general settings which influence the recorded data are the flatfield correction, count rate correction, the threshold settings, and the energy settings (trimming). Please refer to the manual for a detailed description.

Try pinning the current DCS IP. If there is no response confirm that:

• the device is powered
• the ethernet cable is connected
• the network LEDs on the DCS as well as control computer are on
• the correct IP is addressed

The DCS is delivered either with DHCP running or a static IP (default 192.168.0.90). The initial configuration of your system is described on the system information sheet under the keyword IP-Address. If your DCS is configured with DHCP running or you have manually changed the IP settings ask your IT administrator for the current IP address. The MAC-address and the hostname of your DCS are noted on the system information sheet with the keywords MAC-address and hostname.

In case you do not know your former IP settings you can revert to factory settings. Please proceed as described in the section "Factory Reset" in MYTHEN2 manual.

Yes. The module specific data is stored directly in the modules. Modules can be connected to any DCS.

The default setup is not designed for vacuum operation. However, we are able to construct a specific solution tailored specifically to your experiments.
Please contact us  with a description of your experiments and requirements for a nonbinding discussion.  

If you experience any issue with the signal quality, please send a detailed error description, all experimental parameters, the MYTHEN settings as well as raw data to our support team.

The general settings which influence the recorded data are the flatfield correction, count rate correction, the threshold settings, and the energy settings (trimming). Please refer to the manual for a detailed description.

The default setup is not designed for vacuum operation. However, we are able to construct a specific solution tailored specifically to your experiments.

Please contact us  with a description of your experiments and requirements for a nonbinding discussion.  

The general guidelines are:

Flashing the MYTHEN DCS is required in case you want to revert to factory settings or the flash memory has corrupted. The flash process can be performed using a virtual linux machine which is provided in the following download links. Please follow the instructions to re-flash your system:

REQUIREMENTS:

• VMplayer (free download)
• virtual linux machine (VM): CentOS_5.8x86_64_Customer_Dectris (please unpack archive)
• empty flash image: fimage_0xff (please unpack archive)
• DCS flash image which is contained on the delivered system CD or USB media in the folder software/fimages/

HOW TO:

• install the previously downloaded VMPlayer and start the virtual linux image.
• log in as user det with password Mythen (be aware of the keyboard layout (US, y ↔ z))
• apply the correct network settings: On your virtual machine go to System->Administration->Networ<wbr></wbr>k and set a static IP to 192.168.0.100
• power the MYTHEN DCS and connect it to the correct LAN port on your computer
• copy the downloaded empty as well as DCS flash images to /home/det/Desktop/axis/devboar<wbr></wbr>d-R2_10/fimages/
• open a shell and change the working directory to devboard:
  • cd /home/det/Desktop/axis/devboar<wbr></wbr>d-R2_10
• become super user (password: MYTHEN):
  su
• set up the flash environment:
  source init_env
• flash the empty firmware image:
  cd /home/det/Desktop/axis/devboar<wbr></wbr>d-R2_10/
boot_linux -F -d eth0 -i fimages/fimage_0xff
• On the DCS (see also the animation):

• press the BOOT push-button and keep it pressed
• press in addition the RESET push-button and keep it pressed
• release the RESET button
• release the BOOT button
• the MYTHEN system should be flashing now. This may take a while (~10 mins) and generates a terminal output. The system should reboot once it has finished flashing.
• flash the DCS image with the fimage_XXX_FIX if you want to have initially a static IP configured or fimage_XXX_DHCP if you want the MYTHEN to be configured with DHCP (the network settings can be changed upon login):
  
  boot_linux -F -d eth0 -i fimages/fimage_XXX
   
• please follow the flash instructions as described previously to write the emtpy firmware image
• Now, the MYTHEN should be reverted to factory settings. You can try to access the MYTHEN webinterface over the corresponding IP (192.168.0.90 if the fimage_FIX was flashed).

After flashing, the following access credentials apply:

USER: root

PW: pass

Try pinning the current DCS IP. If there is no response confirm that:

• the device is powered
• the ethernet cable is connected
• the network LEDs on the DCS as well as control computer are on
• the correct IP is addressed

The DCS is delivered either with DHCP running or a static IP (default 192.168.0.90). The initial configuration of your system is described on the system information sheet under the keyword IP-Address. If your DCS is configured with DHCP running or you have manually changed the IP settings ask your IT administrator for the current IP address. The MAC-address and the hostname of your DCS are noted on the system information sheet with the keywords MAC-address and hostname.

In case the ACT LED on the DCS should blink continuously at a high frequency, the flash memory might be corrupted. Please follow the FAQ article [MYTHEN] flash DCS.