Read Sharp UP-X300 (serv.man50) FAQ online
1.17 Master Terminal slow whilst performing B/O Jobs and EOD
Q. The X300 was much slower when performing B/O jobs or carrying out the
EOD Job.
Q. The X300 was much slower when performing B/O jobs or carrying out the
EOD Job.
A. The problem was caused because the Mlist.dat file was incorrect, please
delete the Mlist.dat file, it will automatically be recreated by the system.
Mlist.dat contains the Master list of terminals and also any data to be sent to
these terminals, if the system originally had more terminals than at present.
Mlist.dat could contain their data and cannot download it, as they are no
longer there, this causes the delay
delete the Mlist.dat file, it will automatically be recreated by the system.
Mlist.dat contains the Master list of terminals and also any data to be sent to
these terminals, if the system originally had more terminals than at present.
Mlist.dat could contain their data and cannot download it, as they are no
longer there, this causes the delay
1.18 Touch Screen Calibration
Q. The touch screen is not responding correctly, when numeric “1“ key is
pressed the numeric “4” key is entered.
Q. The touch screen is not responding correctly, when numeric “1“ key is
pressed the numeric “4” key is entered.
A. The X300 Touch Screen probably needs calibrating to do this:
Please open Settings\Control Panel\Stylus -> Tab Calibration
Please open Settings\Control Panel\Stylus -> Tab Calibration
1.19 UP-X200 Battery Life
Q. How long should the battery last in the UP-X200?
Q. How long should the battery last in the UP-X200?
A. The Batteries are specified to have the following.
1.
1.
500 Cycles (Discharge-Recharge)
2.
Approx. 9 Hours of use at 1 Transaction per minute (1 TRN = 5 items and
finalise)
finalise)
3.
The Recharge time is between 3 and 4.5 hours (depending if terminal is
on or off
on or off
1.20 Master Terminal slow whilst performing B/O Jobs and EOD
Q. The above was reported on an X300 with X200 system configuration.
Q. The above was reported on an X300 with X200 system configuration.
A. The problem was caused because the Mlist.dat file was incorrect, see Q
1.17 above.
1.17 above.
It is highly recommended that if frequent programming is carried out on the
X300 terminal that the X200 terminals be in Power On mode this will mean
they receive updated program data from the X300 and not build up the Mlist
file which can lead to slow down of operations.
1.21 Master Terminal Froze after doing an End of Day (EOD)
Q. The Master terminal “Froze” and would not allow anything other than
Power Off.
X300 terminal that the X200 terminals be in Power On mode this will mean
they receive updated program data from the X300 and not build up the Mlist
file which can lead to slow down of operations.
1.21 Master Terminal Froze after doing an End of Day (EOD)
Q. The Master terminal “Froze” and would not allow anything other than
Power Off.
A. On this occasion the System date had been changed to pass the BST
daylight saving date (Last Sunday in March/October)
Whilst the “Automatic adjust clock for daylight saving” was ticked, this will be
fixed in later release, in the interim please ensure the “Automatic adjust clock
for daylight saving” is not ticked
daylight saving date (Last Sunday in March/October)
Whilst the “Automatic adjust clock for daylight saving” was ticked, this will be
fixed in later release, in the interim please ensure the “Automatic adjust clock
for daylight saving” is not ticked
Click on the first or last page to see other UP-X300 (serv.man50) service manuals if exist.