Troubleshooting¶
In the event of an error or unexpected behaviour, please consult the system log in the first instance. In the event that it is not possible to diagnose and resolve an error using the steps below, please save the system log, and where available any loaded recipe and run data, and send these to the Exobotics support team with a description of the problem, and we will endeavour to assist as quickly as possible.
Logged errors¶
The system logger can detect a wide range of events within the XO-VAC+ system, some of which are described below:
| Logger error message | Description | Action |
|---|---|---|
Unable to connect to internal serial devices | When the XO-VAC+ is powered up it will attempt to initialise all its internal systems, and the central onboard computer will attempt to connect to the internal slave devices. If it fails to connect to one or more of these devices, the system will continue to attempt to connect every 5s. This error may be accompanied by one of the following two communication errors. | The system may be able to resolve this error internally, however if the error persists after several minutes the most likely cause is an internal hardware fault. It may be possible to resolve the error by powering down the XO-VAC+ for several minutes, then restarting. Check that the Dsub 25 cables connection are not loose or damaged |
Error communicating with TEC controller | Internal software communication error, may be a hardware or software fault. | Restarting the device may help, otherwise please contact the support team. |
Error communicating with RTD controller | Internal software communication error during intialisation, may be a hardware or software fault. | Restarting the device may help, otherwise please contact the support team. |
TEC controller frame communication error | Internal software communication error during intialisation, may be a hardware or software fault. | Restarting the device may help, otherwise please contact the support team. |
Unable to reach target temperature! Step will continue at achieved temperature | Device was unable to achieve target temperature during a recipe run, possibly due to the physical limitations of the system. The system will continue running the recipe step, but at the achieved temperature rather than the target. This message is not necessarily indicative of an error and may be due to the physical limitations of the system. | If the system is failing to reach target temperatures that should be achievable, please check the following: 1. The vacuum is running correctly and the chamber pressure is below the recommended operational level. 2. The test subject does not have an unusually large thermal mass. 3. The internal heat exchanger sensors are both showing apporoximately similar readings and responses to thermal changes. 4. There are no other associated errors relating to hardware or software communications. |
Run Terminated: Internal TEC unit exceeded working temperature limit... | The temperature at the internal heat exchanger was detected to have exceeded operational limits. | Check all sensor readings for any anomalous or unexpected behaviour. Ensure the test subject is not emitting thermal energy of its own to the chamber (for example, a battery or operating electronic device). |
Run Terminated: External TEC unit exceeded working temperature limit... | The temperature at the external heat sink was detected to have exceeded operational limits. | Check the rear of the device to ensure vents are not blocked or obstructed. Check all fans around rear box of device are operational. Check there is no damage or leak to the cooling fluid system. |
TEC Controller [1 / 2] in error state [error number], channel [1 / 2] | The XO-VAC+ has detected an error in one of the internal serial devices. These could be triggered by a range of issues, including unusual thermal response, damaged cabling (inside or outside device) or loose connections. | XO-VAC+ will try to reset the error. If the device is running the run will be automatically cancelled as a precaution. Check all cabling is in good condition and firmly connected into the sockets to the rear of the device. Check that the sensors and cabling around payload tray are not damaged. If error is not resolved, try restarting the device. Please note the error details from the log and send to the Exobotics support team for further advice. |
System moving toErrorstate | An unhandled error has been detected and the system is moving to Error state. The system will attempt to cut power to the Thermal Controllers, and then move to Error state to attempt to handle the error or provide further information. | View system log for any further information regarding the error. If error is not resolved, try restarting the device. |
System unable to reset TEC controller, please consult user manual and reset manually | The system is in error state due to a fault with one of the internal TEC controllers. The system has attempted several times to reset the controller, but failed. | Power down the device and allow system to cool to ambient temperature before restarting. If problems persist please contact the support team. |
Other errors | The system can display and log errors not described in this section. | Please contact Exobotics for support with a detailed description of the error message and the log file. |
General issues¶
Various possible issues that may not show up in the system log are discussed below.
Difficulty connecting to XO-VAC+ device from user software¶
Check that:
- The device is switched on and has had time to start up (approximately one minute).
- Check that ethernet cable is connected properly and is in good condition.
- Check that both your PC and the XO-VAC+ are connected to the same network.
- Check the correct IP address and port have been entered (see theSystem Information Page for more).
- Check that there are no firewall or antivirus systems on your PC blocking the connection.
Very slow thermal response time¶
It generally takes several hours for thermal changes in XO-VAC+ to completely stabilise throughout the chamber due to the thermal mass of the system. Test subjects with high thermal mass, conductivity, or reflectivity may affect the time taken for the system to stabilise. Please ensure the vacuum system is running correctly and the chamber is within the recommended pressure range before running a thermal cycle.
Reference temperature not staying within limits of target¶
During a run the control system will attempt to bring the temperature to within the target temperature ± the convergence margin (set on the Settings page), and then hold within this range. Sometimes the temperature may drift outside of these limits due to the physical limitations of the system or changes in environmental factors. In this case the control system will try and correct the drift. Depending on which sensor(s) are selected as reference sensors the corrections may take some time to be effective due to the large thermal mass and associated response time.
Tip
We recommend a value of 0.5C for the temperature convergence margin was found to work well in most cases.
User PC or software crashes during run¶
This should not affect the XO-VAC+ itself; if it was in run state it will continue to handle the run in the background. Simply re-open the user software and reconnect to the device. If the device is in run go to the Run Page to continue viewing the run data. At the end of the run it will be possible to import the full run data from the device, which can then be viewed on the View Data Page. If it is not possible to reconnect to the device, the device may be shut down safely using the emergency shut-down procedure.
Shroud temperatures do not appear to be changing¶
The copper shroud inside the XO-VAC+ chamber has a high thermal mass. This high thermal mass is necessary for providing a uniform thermal environment to for the payload tray and test subjects, however it also means it will be much slower to react to changes in temperature than the heat exchanger face sensors. When running to a new target temperature it should be possible to observe a change in trend of the shroud rear sensor after only a few minutes, however the entire shroud may take several hours to reach thermal equilibrium to within the convergence margin.
If you are not observing any response to thermal changes at the shroud rear sensor, or the shroud front and rear sensors consistently give readings that are very close, it may be that the shroud has become dislodged inside the chamber and the physical connection to the heat exchanger has been compromised. In this case please contact the Exobotics support team for further advice.