POTENTIAL OPERATING ISSUES
Touchpoint Pro
Pt. No. 2400M2566_1_EN
62
Operating Manual
Category
Fault / Problem
Possible Cause
Remedial Action
User Interface
(Touchscreen)
Screen does not
respond to touch
Internal
communication
issue
1) On the front panel, select the Accept and Reset
buttons together for >10 s to reset the Communication
Board.
2) Contact your service representative if this fails.
User Interface
(Touchscreen)
Screen does not
respond to user
input as expected
Screen calibration The touch screen may require recalibration.
GUI
(Webserver)
‘Web browser
already open’
error message
MS Windows
limitation:
Browser does not
fully shut down on
exit, or other
instances remain
open on exit
Use Task Manager to close the browser or select
CTRL+ALT+DEL>Start Task
Manager>Processes>[Your browser]>End Process
Close Task Manager and relaunch your browser.
Web Server
No Web Server
connection
Verify that the TPPR has a valid Webserver licence.
Check TCP/IP settings, check if the PC network adapter
is enabled, check proper cable connections. The
Ethernet port of the Touchpoint Pro Control Module
should be connected to a network. Please refer to
Ch.5.2 Cabling Requirements
for further information.
Web Server
Communication
with the Controller
is lost
The Touchpoint
Pro Controller is
busy, or the
network has been
interrupted.
If possible, check the TPPR Touchscreen for any
instruction or detailed error message.
A system operation such as power up, backup or restore
may be in progress. Allow time for completion and retry.
Web Server
Slow / intermittent
response from the
Touchpoint Pro
system
The Web Server
supports 5
concurrent web
clients, however it
does not restrict
further users from
connecting
Reduce the number of web clients to five or below.
Table 14.
Potential Issues
10.2
Other Issues
10.2.1
Modules Reporting a Fault
If the system detects a module fault, the fault will be reported on the screen and the module’s LED will change colour to
orange.
If the fault is transient in nature – possibly due to low power supply voltage or to ring communication problems – the module
will return automatically to normal operation when the fault is cleared.
When the system detects a module fault, that module will be set to a safe state. If this happens, the module stops
communicating on the ring and takes its inputs / outputs to the defined ‘safe’ state e.g. it turns off mV bead current and takes
relays to a power-off state. See
Ch.19 Ring Communication Errors
for further information.
A failed module will generate ring fault reports, module fault reports and channel fault reports. The channels either side of it
will also report lost communications, but will not be shown as faulty. See
Ch19.4 Ring Fault Diagnostics and Debugging
Techniques
for further information.
The module should only be replaced if the fault is
not
due to low power or a ring problem in another part of the system.
Contact your local service representative for help if required.
Note
:
it may be possible to restore module operation by physically removing and refitting the module to disrupt its power
supply. However, you should contact your service representative for advice as the recovery may only be temporary.