Unfortunately the MultiTest-x stand may do this very occasionally. If this happens we advise that you reset the ‘Absolute Zero’ setting (the zero position used for absolute readings) on the test stand. This is done by running the manual Touch function from the 0 button on the front panel.
Entering 0 for the value in SegB causes the program to run to break. I.e. it doesn`t run to zero force, distance or time but continues running until another factor finishes the test.
Mecmesin can upgrade your MultiTest-x but please note that:
1. Mecmesin can not be held responsible for any consequences arising if any non-Mecmesin staff perform the upgrade.
2. The upgrade will erase all current settings on the stand.
3. The instructions to perform the firmware upgrade must be followed carefully.
3. You will require a Windows PC and a RS232 lead to connect to the test stand.
You need to set the MultiTest-x to TERM protocol in the Print Menu and the printer needs to be set to ASCII. You also need to use a standard 1-1 RS 232 cable with all it`s pins connected.
If the Local Overload setting on a MultiTest-x is not set correctly then this message can appear. The Local Overload setting is used to protect the loadcell but stopping the stand when the value is exceeded.
Please try changing the value of the Local Overload if this message is appearing but you believe it should not.
If the message still appears it could be caused by other factors: the XLC is not connected properly, there is a problem with the XLC cable or the XLC has been overloaded.
If there is a problem with the XLC cable or the XLC has been overloaded the XLC must be sent to your local Mecmesin distributor for investigation.
There are two things you can do.
The first is to turn off any unrequired calculations so you only have the calculations you need.
The second is to reduce the sample rate in the Log Rate to as low as rate as possible. Note that this means readings are not taken as quickly, if the Log Rate is too low a peak reading could be missed.
Your local Mecmesin distributor will be able to advise the best sample rate for an application.
It sounds like you have the Supervisor OFF. In this mode the user can`t change the program settings. You can view but not change settings.
If you are `stuck` in a menu press ENT to leave the menu.
If you need to change something, turn the Supervisor ON (you will need the password), make the change and turn the Supervisor OFF again. Instructions can be found in the MultiTest-x Operating Manual.
The FHT calculation depends on a number of factors which can affect the reading given.
Firstly, the FHT is calculated from the Absolute Zero and from the Touch at the start of the program run. It therefore depends on setting the Absolute Zero by performing a manual Touch from the console.
The factors affecting the FHT measurement are:
2. Resolution of the XLC.
3. Touch manually (speed and load variables).
4. Absolute Zero (set by manual touch).
5. Touch in program (speed and load variables).
The MultiTest-x Operating Manual has more detailed information about each of these factors.
This is a function that was not implemented fully in earlier versions of the firmware and so has now been removed.
If the ‘4’ button is pressed on the console it cycles through displaying ‘T’ then ‘C’ then disappears. So if you have 'C 'on the display press 4 once to get rid of it. If you have 'T' press 4 twice to get rid of it.
Whilst a 'T' or 'C' is on the screen the load reading appears to be frozen.
This issue has been corrected in v0.4i onwards.
The diagnostic menu on the MultiTest-X displays a reading for the ADC counts and the encoder position.
However we strongly advise customers not to access this menu as it is no longer used by Mecmesin.
The MultiTest-x accepts the value 9999999.00 sec (166666.65 min) (2777.7775 hr) (115.7407297 days) for the time. It could be dangerous to attempt a loadhold for this long.
You can have a maximum of 65563 secs of log time
=1092.72 mins=18.2119 hrs.
This is the maximum amount of data you can record.
After this the buffer will be full and the data lost.
So the answer is 18.2119 hrs is the longest feasible time a test can last if all the data needs to be recorded.
Any calculations from this will take some time though.
When the limits are set on the results an `L` will appear if the result is below the lower limit and an `H` if the result is above the upper limit.
DS PASS is displayed if all results are within the pass band otherwise DS FAIL is displayed.
If any analysis results are turned on the MultiTest-x always shows a DS FAIL or DS PASS on screen because any limits are used.
Check with your Mecmesin distributor that your XLC is not damaged. If possible try another XLC to confirm there is a problem with that XLC.
Emperor™ Lite is designed to work with the MultiTest-x stand but both the stand and Emperor™ Lite need to be set up properly.
For most Mecmesin products the `Test Communication` button can be used to check if Emperor™ Lite and the product are set up correctly. However as the MultiTest-x is designed to send but not receive data this can not be used with the MultiTest-x and so in Emperor™ Lite this button is greyed out when MultiTest-x is selected.
1. Set Emperor™ Lite instrument to MultiTest-x.
(Setup-System Setup-System Settings.)
2. Set Emperor™ Lite Primary data input to COM n.
(Setup-System Setup-System Settings.) *
3. Set Emperor™ Lite baud rate to qq.
(Setup-System Setup-System Settings.)
4. On MultiTest-x set to baud qq.
5. On MultiTest-x set the protocol as WCP not TERM.
6. Set the latency for the USB converter to 1ms.
qq is the baud rate. (Emperor™ Lite baud = MultiTest-x baud)
n is the COM port number.
*If using a USB-Serial converter the COM port must be the COM port picked in the Device Manager as `USB Serial Port`.
The MultiTest-x needs to be set to WCP mode. If it is not set to WCP nothing will happen when used with Emperor™ Lite.
(If you are using a terminal program like Hyperterminal to test communications the MultiTest-x needs to be set to TERM mode and then changed back to WCP for use with Emperor™ Lite.)
The Sample Break on the MultiTest-x is entered in the Acquisition Menu as a % break. A value of 100 turns it off. For the Sample Break condition to stop a test the load needs to fall by the given % from the current peak at any moment. For example, if the force is reading 5N and drops below 2.5N this would trigger a 50% sample break and stop the test.
Two other variables affect the Sample Break - Log Rate and Threshold.
The Log Rate is the stand's sampling rate. If set too low a drop in the load that could trigger the break could be missed. If set too high the calculations will take longer and the stand can run out of memory during a test ('XA' or 'XB').
The Threshold setting is the load value which needs to be exceeded before data is recorded. Before the Threshold is reached a 'TA' or 'TB' is displayed. If this is set to 0N or too low with a Sample Break set then the test may stop before required. This is because very low readings can register a sample break with a very small change. For example if the force reading is 0.01N and drops to 0.00 N this would trigger a 90% sample break. It is common to set the Threshold to the tolerance of the XLC.
The most likely cause is that the console power configuration is not correct.
When power is lost or the console is shutdown/put to sleep it must go into the correct power mode.
If necessary plug in a USB keyboard or USB mouse so that you can Recover/Resume/Restore Windows. Depending on option selected this could take some time.
Then once Windows has started please make sure your console is set up as below.
The current power settings should be set up as below:
Put the computer to sleep set to Never.
Always use normal Sleep or Shutdown, note Hibernation and Hybrid Sleep should be avoided.