The Terminal Does Not Power Up
- Verify the wiring and the connections to the power source. See Systems Operation, "Connections".
Expected Results: The connections to the power source are not correct.
OK - The connections to the power source are not correct. Fix the connections. See Systems Operation, "Connections". STOP.
Not OK - The connections to the power source are correct. Go to step 2.
- Verify that 24 DCV is present at the power terminals.
Expected Results: 24 DCV is not present at the power terminals.
OK - 24 DCV is not present at the power terminals. Repair the power supply or replace the power supply. STOP.
Not OK - 24 DCV is present at the power terminals. Go to step 1.
- Check to see if the DC positive and negative power wires are connected to the proper terminals.
Expected Results: The DC power wires are reversed.
OK - The DC power wires are reversed. Reconnect the wires to the proper terminals. STOP.
Not OK - The DC power wires are connected to the proper terminals. Replace the Panelview terminal. STOP
An Application File Will Not Download (First Attempt)
- Check the type of the communication cable and the connections.
Expected Results: The communication cable is disconnected.
OK - The communication cable is disconnected. Make sure the cable is the correct cable and connect the cable. STOP.
Not OK - The communication cable is connected and the communication cable is the correct cable type. Go to step 2.
- Verify that the computer and the terminal are set to the same communication settings.
Expected Results: The computer and the terminal have different communication settings.
OK - The computer and the terminal have different communication settings. Change the settings on the computer or on the terminal so that the settings are the same for both. STOP.
Not OK - The computer and the terminal have the same communication settings. Replace the Panelview terminal.
An Application File Will Not Download (Subsequent Attempts)
- Verify that the computer and the terminal are set to the same communication settings.
Expected Results: The computer and the terminal have different communication settings.
OK - The computer and the terminal have different communication settings. Change the settings on the computer or on the terminal so that the settings are the same for both. STOP.
Not OK - The computer and the terminal have the same communication settings. Replace the Panelview terminal.
No Communications With an SLC Controller or a PLC Controller
- Check the type of the communication cable and the connections.
Expected Results: The communication cable is disconnected.
OK - The communication cable is disconnected. Make sure the cable is the correct cable and connect the cable. STOP.
Not OK - The communication cable is connected and the communication cable is the correct cable type. Go to step 2.
- Verify that the terminal and the controller are set at the same baud rate.
Expected Results: The terminal and the controller are not set at the same baud rate.
OK - The terminal and the controller are not set at the same baud rate. Change the baud rate of either the terminal or the controller so that the baud rates are the same. STOP.
Not OK - The terminal and the controller are set at the same baud rate. Go to step 3.
- Check to see if the controller is in the run mode.
Expected Results: The controller is not in the run mode.
OK - The controller is not in the run mode. Place the controller in the run mode. STOP.
Not OK - The controller is in the run mode. Go to step 4.
- Verify the address of the node.
Expected Results: The terminal node and the maximum node numbers are not set correctly.
OK - The terminal node and the maximum node numbers are not set correctly. Reset the terminal node and the maximum node numbers so that the numbers are correct. STOP
Not OK - The terminal node and the maximum node numbers are set correctly. Replace the Panelview terminal.
No Communications With the PLC and the "COMM" LED is Active
- Verify the address of the controller.
Expected Results: The Panelview terminal is trying to communicate with a controller at a different address.
OK - The Panelview terminal is trying to communicate with a controller at a different address. Change the address of the controller. STOP.
Not OK - The Panelview terminal is not trying to communicate with a controller at a different address. Go to step 2.
- Check the setting of the inhibit bit.
Expected Results: The inhibit bit is set as the default on the "Channel Status" screen in the PLC.
OK - The inhibit bit is set as the default on the "Channel Status" screen in the PLC. Change the inhibit bit to the correct setting. STOP.
Not OK - The inhibit bit is set to the correct setting on the "Channel Status" screen in the PLC. Replace the Panelview terminal.
No Communications With the Computer
- Check the type of communication cable and the connections.
Expected Results: The communication cable is disconnected.
OK - The communication cable is disconnected. Make sure the cable is the correct cable and connect the cable. STOP.
Not OK - The communication cable is connected and the communication cable is the correct cable type. Go to step 2.
- The personal computer interface converter receives power from the DH-485 connection. Verify that the terminal is connected to an SLC, network, or a wallmount power supply.
Expected Results: The terminal is not connected to an SLC, network, or wallmount power supply.
OK - The terminal is not connected to an SLC, network, or wallmount power supply. Connect the terminal to an SLC, network, or wallmount power supply.
Not OK - The terminal is connected to an SLC, network, or wallmount power supply. Go to step 3.
- Verify that the computer and the terminal are set to the same baud rate.
Expected Results: The computer and the terminal have different baud rates.
OK - The computer and the terminal are set to different baud rates. Change the baud rate on the computer or on the terminal so that the settings are the same for both. STOP.
Not OK - The computer and the terminal are set to the same baud rates. Go to step 4.
- Verify the address of the node.
Expected Results: The terminal node and the maximum node numbers are not set correctly.
OK - The terminal node and the maximum node numbers are not set correctly. Reset the terminal node and the maximum node numbers so that the numbers are correct. STOP
Not OK - The terminal node and the maximum node numbers are set correctly. Replace the Panelview terminal.
- Check to see if there is a computer fault.
Expected Results: There is a computer fault.
OK - There is a computer fault. Refer to the user manual for the computer.
Not OK - There is not a computer fault. Replace the Panelview terminal.
"Clock Module Battery Low" Message is Displayed
- Reload the application and cycle the power to the terminal.
Expected Results: "Clock Module Battery Low" message will no longer be displayed.
OK - "Clock Module Battery Low" message is no longer displayed. STOP.
Not OK - "Clock Module Battery Low" message is still displayed. Go to step 2.
- Replace the clock module battery. See Testing and Adjusting, "Battery - Replace".
Expected Results: "Clock Module Battery Low" message will no longer be displayed.
OK - "Clock Module Battery Low" message is no longer displayed. STOP.
Not OK - "Clock Module Battery Low" message is still displayed. Replace the Panelview terminal.
An Application Cannot be Transferred from a Memory Card
- Verify that the memory card is installed properly. See Systems Operation, "Memory Card".
Expected Results: The memory card is not installed properly.
OK - The memory card is not installed properly. Remove the memory card and reinstall the memory card properly. See Systems Operation, "Memory Card". STOP.
Not OK - The memory card is installed properly. Go to step 2.
- Check the size of the application file.
Expected Results: The application file is too large for the terminal memory.
OK - The application file is too large for the terminal memory. Reduce the size of the application file. STOP.
Not OK - The application file is not too large for the terminal memory. Go to step 3.
- Verify that the format of the file being transmitted is ".PVA".
Expected Results: The file format of the transmitted file is not ".PVA".
OK - The file format of the transmitted file is not ".PVA". Change to a file that is the correct format. STOP.
Not OK - The file format of the transmitted file is ".PVA". Replace the Panelview terminal.
An Application Cannot be Transferred to a Memory Card
- Verify that the memory card is installed properly. See Systems Operation, "Memory Card".
Expected Results: The memory card is not installed properly.
OK - The memory card is not installed properly. Remove the memory card and reinstall the memory card properly. See Systems Operation, "Memory Card". STOP.
Not OK - The memory card is installed properly. Go to step 2.
- Check to see if the memory card is write protected.
Expected Results: The memory card is write protected.
OK - The memory card is write protected. Change the memory card protection switch. STOP.
Not OK - The memory card is not write protected. Go to step 3.
- Check to see if the file already exists on the memory card.
Expected Results: The file already exists on the memory card.
OK - The file already exists on the memory card. Erase and reformat the card. STOP.
Not OK - The file does not already exist on the memory card. Go to step 4.
- Check the amount of space that is is available on the memory card.
Expected Results: The application file is too large. There is not enough space left on the memory card.
OK - There is not enough space left on the memory card. Reformat the memory card. If the problem still exists try another memory card. STOP.
Not OK - There is enough space left on the memory card. Go to step 5.
- Check the "TERMINAL INFO" screen to verify that an application exists.
Expected Results: An application does not exist.
OK - An application does not exist. An application cannot be transferred to the memory card. STOP.
Not OK - An application does exist. Replace the Panelview terminal.
Screen Objects Do Not Function
- Check the status of the "COMM" LED.
Expected Results: The terminal is not communicating with the controller.
OK - The terminal is not communicating with the controller. Go to "No Communications With an SLC Controller or a PLC Controller".
Not OK - The terminal is communicating with the controller. Go to step 3.
- Access the screen setup from the "CONFIGURATION MODE" menu in order to check if the terminal is in the screen saver mode.
Expected Results: The terminal is in the screen saver mode.
OK - The terminal is in the screen saver mode. Change the setting so that the terminal is not in the screen saver mode. STOP.
Not OK - The terminal is not in the screen saver mode. Replace the Panelview terminal.
The Application Filename Appears as "********" on the "TERMINAL INFO" Screen
- Download the application and try again.
Expected Results: The filename appears correctly in the "TERMINAL INFO" screen.
OK - The filename appears correctly in the "TERMINAL INFO" screen. STOP.
Not OK - The filename does not appear correctly in the "TERMINAL INFO" screen. Go to step 2.
- Download a new application.
Expected Results: The new filename appears correctly in the "TERMINAL INFO" screen.
OK - The new filename appears correctly in the "TERMINAL INFO" screen. STOP.
Not OK - the new filename does not appear correctly in the "TERMINAL INFO" screen. The application is unusable because of an error.
An Area on the Color Screen Appears Dark
- Replace the color backlight.
Expected Results: The color screen is no longer dark.
OK - The color screen is no longer dark. STOP.
Not OK - The color screen is still dark. Replace the Panelview terminal.
Screen Objects are Not Visible
- Verify the wiring and the connections to the power source. See Systems Operation, "Connections".
Expected Results: The connections to the power source are not correct.
OK - The connections to the power source are not correct. Fix the connections. See Systems Operation, "Connections". STOP.
Not OK - The connections to the power source are correct. Go to step 2.
- Access the "Screen Setup" on the "CONFIGURATION MODE" menu and adjust the contrast.
Expected Results: The contrast is not set correctly.
OK - The contrast is not set correctly. Adjust the contrast until objects are visible. STOP.
Not OK - The contrast is set correctly. Go to step 3.
- Access the screen setup from the "CONFIGURATION MODE" menu in order to check if the terminal is in the screen saver mode.
Expected Results: The terminal is in the screen saver mode.
OK - The terminal is in the screen saver mode. Change the setting so that the terminal is not in the screen saver mode. STOP.
Not OK - The terminal is not in the screen saver mode. Go to step 2.
- Replace the color backlight.
Expected Results: The screen objects are visible.
OK - The screen objects are visible. STOP.
Not OK - The color screen is still dark. Replace the Panelview terminal.
Values Do Not Update on the Display but Appear as Asterisks "****"
- Check the status of the "COMM" LED.
Expected Results: The terminal is not communicating with the controller.
OK - The terminal is not communicating with the controller. Go to "No Communications With an SLC Controller or a PLC Controller". STOP.
Not OK - The terminal is communicating with the controller. Go to step 2.
- Check the field width for the object.
Expected Results: The value exceeds the field width that is defined for the object.
OK - The value exceeds the field width that is defined for the object. Change the field width for the object. STOP.
Not OK - The value does not exceed the field with that is defined for the object. The value is invalid. STOP.