Troubleshooting Your PanelView Plus 400
PanelView Plus 400 Incorrect Start-Up
If the PanelView Plus 400 terminal is not starting up correctly always check for adequate power first. Inadequate power can cause a variety of unpredictable behavior. Simply verify the terminal’s power requirement in the specifications table. It is also good practice to determine whether there have been any changes since the last startup. Determine what these are to see if they can be reversed.
Battery voltage, as well as the display temperature, are indicative of other potential issues as well. Check the battery voltage and display temperature from the PanelView Plus 400 terminal desktop or from the FactoyTalk View ME station configuration mode. If the voltage is below 2.75 volts DC, consider replacing the battery. Obstructed airflow in the chassis can cause the CPU and/or display to overheat. If the CPU temperature is above 95 degrees Celsius or the display temperature is above 55 degrees Celsius, try to moderate the ambient temperatures.
If you continue have start-up issues, observe the splash screen for state messages and for the status or error codes.
PANELVIEW PLUS 400 STATUS INDICATORS
Status indicators are located on the back of your PanelView 400 terminal. The COMM indicator is green and reflects communication. The FAULT indicator is red and reflects hardware faults. Upon startup, the fault indicator should be off and the comm indicator on. If the fault indicator flashes a few times at startup, this is not a concern. However, if both indicators are off you should check the power cable. See the table below to interpret the terminal’s indicator status:
|Fault Indicator (RED)||Comm Indicator (GREEN)||Meaning and Action|
|Possibly Recoverable Error|
|Blinking||On||Windows CE Operating System failed or missing. Reload firmware.|
|Off||Most recent firmware download failure. Reload firmware.|
|Blinking||EBC boot loader firmware missing/failed. Reload firmware.|
|On||Blinking||Fatal display hardware error. Replace terminal.|
|Off||Fatal hardware error. Replace terminal.|
PanelView Plus 400 Terminal Component Anomalies
|Dim or Unreadable Display||Check contrast settings –When in configuration mode, select Terminal Setting>Display>Display Contrast|
|Backlight Unexpectedly Turning Off or Dimming||Check screen saver settings – When in configuration mode, select Terminal Settings>Display>Screen Saver|
|Touch Screen Operating Incorrectly/Inaccurate Input and Dragging||Calibrate Your Touch Screen –When in configuration mode, select Terminal Settings> Touch Screen>Calibration|
|Screen Cursor Not Visible||Verify the Cursor is Enabled –When in configuration mode, select Terminal Settings> Input Devices> Touch Screen > Cursor|
|Touch Screen Not Accepting Touch Input||Attach USB Mouse:Mouse works but touch screen does not: Touch driver or screen is nonfunctionalNeither mouse nor touch screen working: Application issue|
If the PanelView Plus 400 display lacks a touch screen, you may not have a touch screen display. Check the label on the terminal and the part number of the unit to verify.
Please Note: When calibrating your touch screen, the process requires four (4) screen touches. If the touches are not satisfactory, more will be requested until calibration is successful. If the touch screen does not calibrate or continues to malfunction replace the PanelView Plus 400 terminal.
|Mouse Operating Incorrectly||Reattach USB mouse, restart terminal|
|Cursor Not Visible/Mouse Settings Require Adjustment||Verify the Cursor is Enabled –When in configuration mode, select Terminal Settings>Display>CursorCheck Mouse Settings –|
When in configuration mode, select Terminal Settings>Input Devices>Mouse
|Mouse is Composite Device (Keyboard and Mouse)||Replace with standalone mouse|
|USB Mouse Non-Operational||Replace the USB mouse. Current mouse may be noncompliant|
|Keyboard Operating Incorrectly||Reattach the USB keyboard, restart the terminal|
|Keyboard Rejecting Key Input||Check Keypad Input –If keypad works either the keyboard driver or keyboard stopped working. If neither the keypad nor the keyboard work, an application failure is likely|
|Keyboard is USB Composite Keyboard and Mouse||Simply use a standalone USB keyboard|
|USB Keyboard is Non-Operational||Replace the USB keyboard. Current keyboard may be noncompliant|
|Keyboard Not Enabled||Check Alt-Ctrl KeysWhen in configuration mode, select Terminal Settings>Input Devices>Keyboard|
|Keypad Not Accepting Input||Check Keyboard Input-If the keyboard works either the keypad driver or keypad stopped working. If neither the keypad nor the keyboard work, an application failure is likely|
|Hold-Off Delay too Long/Multiple Key Presses Inhibited by Multi-Key Lockout||Check Keypad Settings-When in configuration mode, select Terminal Settings>Input Devices>KeypadNote: Home, End, Up and Down keys do not work when single or multi-key lockout is enabled.|