Maintenance and Troubleshooting

Maintenance and Troubleshooting
Maintenance and
Troubleshooting
19
In This Chapter. . . .
— Hardware Maintenance
— Diagnostics
— CPU Indicators
— PWR Indicator
— RUN Indicator
— CPU Indicator
— BATT Indicator
— Communications Problems
— I/O Module Troubleshooting
— Noise Troubleshooting
— Machine Startup and Program Troubleshooting
9--2
Maintenance and Troubleshooting
Hardware Maintenance
Standard
Maintenance
Maintenance
and Troubleshooting
Air Quality
Maintenance
Low Battery
Indicator
CPU Battery
Replacement
The DL305 is a low maintenance system requiring only a few periodic checks to help
reduce the risks of problems. Routine maintenance checks should be made
regarding two key items.
S Air quality (cabinet temperature, airflow, etc.)
S CPU battery
The quality of the air your system is exposed to can affect system performance. If
you have placed your system in an enclosure, check to see the ambient temperature
is not exceeding the operating specifications. If there are filters in the enclosure,
clean or replace them as necessary to ensure adequate airflow. A good rule of thumb
is to check your system environment every one to two months. Make sure the DL305
is operating within the system operating specifications.
The CPU has a battery LED that indicates the battery voltage is low. You should
check this indicator periodically to determine if the battery needs replacing. You can
also detect low battery voltage from within the CPU program. SP43 is a special relay
that comes on when the battery needs to be replaced.
The CPU battery is used to retain program V--memory and the system parameters.
The life expectancy of this battery is five years.
To install the D3--BAT--1 CPU battery in the
DL350 CPU:
1. Press the retaining clip on the battery door
down and swing the battery door open.
2. Place the battery into the coin--type slot.
3. Close the battery door making sure that it
locks securely in place.
4. Make a note of the date the battery was
installed.
WARNING: Do not attempt to recharge the battery or dispose of an old battery
by fire. The battery may explode or release hazardous materials.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
NOTE: Before installing or replacing your CPU battery, back-up your V-memory and
system parameters. You can do this by using DirectSOFT to save the program,
V-memory, and system parameters to hard/floppy disk on a personal computer.
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
9--3
Diagnostics
Your DL305 system performs many pre-defined diagnostic routines with every CPU
scan. The diagnostics have been designed to detect various types of failures for the
CPU and I/O modules. There are two primary error classes, fatal and non-fatal.
Fatal Errors
Fatal errors are errors the CPU has detected that offer a risk of the system not
functioning safely or properly. If the CPU is in Run Mode when the fatal error occurs,
the CPU will switch to Program Mode. (Remember, in Program Mode all outputs are
turned off.) If the fatal error is detected while the CPU is in Program Mode, the CPU
will not enter Run Mode until the error has been corrected.
Here are some examples of fatal errors.
S Base power supply failure
S Parity error or CPU malfunction
S I/O configuration errors
S Certain programming errors
Non-fatal Errors
Non-fatal errors are errors that are flagged by the CPU as requiring attention. They
can neither cause the CPU to change from Run Mode to Program Mode, nor do they
prevent the CPU from entering Run Mode. There are special relays the application
program can use to detect if a non-fatal error has occurred. The application program
can then be used to take the system to an orderly shutdown or to switch the CPU to
Program Mode if necessary.
Some examples of non-fatal errors are:
S Backup battery voltage low
S All I/O module errors
S Certain programming errors
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
Many of these messages point to supplemental memory locations which can be
referenced for additional related information. These memory references are in the
form of V-memory and SPs (special relays).
The following two tables name the specific memory locations that correspond to
certain types of error messages. The special relay table also includes status
indicators which can be used in programming. For a more detailed description of
each of these special relays refer to Appendix D.
Maintenance
and Troubleshooting
Finding Diagnostic Diagnostic information can be found in several places with varying levels of
message detail.
Information
S The CPU automatically logs error codes and any FAULT messages into
two separate tables which can be viewed with the Handheld or
DirectSOFT.
S The handheld programmer displays error numbers and short
descriptions of the error.
S DirectSOFT provides the error number and an error message.
S Appendix B in this manual has a complete list of error messages sorted
by error number.
Maintenance
and Troubleshooting
Diagnostics
9--4
Maintenance and Troubleshooting
V-memory
Locations
Corresponding to
Error Codes
Error Class
Error Category
Diagnostic Vmemory
User-Defined
Error code used with FAULT instruction
V7751
System Error
Fatal Error code
V7755
Major Error code
V7756
Minor Error code
V7757
Address where syntax error occurs
V7763
Error Code found during syntax check
V7764
Number of scans since last Program to Run
Mode transition
V7765
Current scan time (ms)
V7775
Minimum scan time (ms)
V7776
Maximum scan time (ms)
V7777
Grammatical
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
CPU Scan
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
9--5
Special Relays (SP)
Corresponding to
Error Codes
On first scan only
SP60
Acc. is less than value
SP1
Always ON
SP61
Acc. is equal to value
SP3
1 minute clock
SP62
Acc. is greater than value
SP4
1 second clock
SP63
Acc. result is zero
SP5
100 millisecond clock
SP64
Half borrow occurred
SP6
50 millisecond clock
SP65
Borrow occurred
SP7
On alternate scans
SP66
Half carry occurred
SP67
Carry occurred
Forced run mode
SP70
Result is negative (sign)
SP12
Terminal run mode
SP71
Pointer reference error
SP13
Test run mode
SP73
Overflow
SP14
Test hold mode
SP75
Data is not in BCD
SP15
Test program mode
SP76
Load zero
SP16
Terminal program mode
Communication Monitoring Relays
SP20
STOP instruction was executed
SP116
SP21
BREAK instruction was executed
Port 2 is communicating with another
device
SP22
Interrupt enabled
SP117
Communication error on Port 2
SP120
Module busy, Slot 0
SP121
Communication error Slot 0
SP122
Module busy, Slot 1
SP123
Communication error Slot 1
SP124
Module busy, Slot 2
SP125
Communication error Slot 2
SP126
Module busy, Slot 3
SP127
Communication error Slot 3
SP130
Module busy, Slot 4
SP131
Communication error Slot 4
SP132
Module busy, Slot 5
SP133
Communication error Slot 5
SP134
Module busy, Slot 6
SP135
Communication error Slot 6
SP136
Module busy, Slot 7
SP137
Communication error Slot 7
CPU Status Relays
SP11
System Monitoring Relays
SP40
Critical error
SP41
Non-critical error
SP43
Battery low
SP46
Communications error
SP47
I/O configuration error
SP50
Fault instruction was executed
SP51
Watchdog timeout
SP52
Syntax error
SP53
Cannot solve the logic
SP54
Intelligent module communication error
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
SP0
Maintenance
and Troubleshooting
Accumulator Status Relays
Maintenance
and Troubleshooting
Startup and Real-time Relays
9--6
Maintenance and Troubleshooting
Maintenance
and Troubleshooting
Error Message
Tables
The DL350 CPU will automatically log any system error codes and any custom
messages you have created in your application program with the FAULT
instructions. The CPU logs the error code, the date, and the time the error occurred.
There are two separate tables that store this information.
S
Error Code Table -- the system logs up to 32 errors in the table. When
an error occurs, the errors already on the table are pushed down and
the most recent error is loaded into the top slot. If the table is full when
an error occurs, the oldest error is pushed (erased) from the table.
S
Message Table -- the system logs up to 16 messages in this table. When
a message is triggered, the messages already stored in the table are
pushed down and the most recent message is loaded into the top slot. If
the table is full when an error occurs, the oldest message is pushed
(erased) from the table.
The following diagram shows an example of an error table for messages.
Date
Time
Message
1993--05--26
08:41:51:11
*Conveyor--2 stopped
1993--04--30
17:01:11:56
* Conveyor--1 stopped
1993--04--30
17:01:11:12
* Limit SW1 failed
1993--04--28
03:25:14:31
* Saw Jam Detect
You can access the error code table and the message table through DirectSOFT’s
PLC Diagnostic sub-menus or from the Handheld Programmer. Details on how to
access these logs are provided in the DirectSOFT and D2--HPP manual.
The following examples show you how to use the Handheld and AUX Function 5C to
show the error codes. The most recent error or message is always displayed. You
can use the PREV and NXT keys to scroll through the messages.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Use AUX 5C to view the tables
CLR
F
5
SHFT
C
2
AUX
AUX 5C HISTORY D
ERROR/MESAGE
ENT
Use the arrow key to select Errors or Messages
AUX 5C HISTORY D
ERROR/MESAGE
ENT
Example of an error display
E252NEW I/O CFG
93/09/21 10:11:15
Year
DL350 User Manual, 2nd Edition
Month
Day
Time
Maintenance and Troubleshooting
System Error
Codes
9--7
The System error log contains 32 of the most recent errors that have been detected.
The errors that are trapped in the error log are a subset of all the error messages
which the DL305 systems generate. These errors can be generated by the CPU or
by the Handheld Programmer, depending on the actual error. Appendix B provides a
more complete description of the error codes.
The errors can be detected at various times. However, most of them are detected at
power-up, on entry to Run Mode, or when a Handheld Programmer key sequence
results in an error or an illegal request.
Description
E003
Software time-out
E520
Bad operation -- CPU in Run
E004
Invalid instruction (RAM parity error)
E521
Bad operation -- CPU in Test Run
E041
CPU battery low
E523
Bad operation -- CPU in Test Program
E043
Memory cartridge battery low
E524
Bad operation -- CPU in Program
E099
Program memory exceeded
E525
Mode switch not in TERM
E101
CPU memory cartridge missing
E526
Unit is offline
E104
Write fail
E527
Unit is online
E151
Invalid command
E528
CPU mode
E155
RAM failure
E540
CPU locked
E201
Terminal block missing
E541
Wrong password
E202
Missing I/O module
E542
Password reset
E203
Blown fuse
E601
Memory full
E206
User 24V power supply failure
E602
Instruction missing
E210
Power fault
E604
Reference missing
E250
Communication failure in the I/O chain
E610
Bad I/O type
E251
I/O parity error
E611
Bad Communications ID
E252
New I/O configuration
E620
Out of memory
E262
I/O out of range
E621
EEPROM Memory not blank
E312
Communications error 2
E622
No Handheld Programmer EEPROM
E313
Communications error 3
E624
V memory only
E316
Communications error 6
E625
Program only
E320
Time out
E627
Bad write operation
E321
Communications error
E628
Memory type error (should be EEPROM)
E499
Invalid Text entry for Print Instruction
E640
Miscompare
E501
Bad entry
E650
Handheld Programmer system error
E502
Bad address
E651
Handheld Programmer ROM error
E503
Bad command
E652
Handheld Programmer RAM error
E504
Bad reference / value
E505
Invalid instruction
E506
Invalid operation
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
Error
Code
Maintenance
and Troubleshooting
Description
Maintenance
and Troubleshooting
Error
Code
9--8
Maintenance and Troubleshooting
Program Error
Codes
The following list shows the errors that can occur when there are problems with the
program. These errors will be detected when you try to place the CPU into Run
Mode, or, when you use AUX 21 -- Check Program. The CPU will also turn on SP52
and store the error code in V7755. Appendix B provides a more complete description
of the error codes.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Error Code
Description
Error Code
Description
E4**
No Program in CPU
E461
Stack Overflow
E401
Missing END statement
E462
Stack Underflow
E402
Missing LBL
E463
Logic Error
E403
Missing RET
E464
Missing Circuit
E404
Missing FOR
E471
Duplicate coil reference
E405
Missing NEXT
E472
Duplicate TMR reference
E406
Missing IRT
E473
Duplicate CNT reference
E412
SBR/LBL >64
E480
CV position error
E413
FOR/NEXT >64
E481
CV not connected
E421
Duplicate stage reference
E482
CV exceeded
E422
Duplicate SBR/LBL reference
E483
CVJMP placement error
E423
Nested loops
E484
No CV
E431
Invalid ISG/SG address
E485
No CVJMP
E432
Invalid jump (GOTO) address
E486
BCALL placement error
E433
Invalid SBR address
E487
No Block defined
E434
Invalid RTC address
E488
Block position error
E435
Invalid RT address
E489
Block CR identifier error
E436
Invalid INT address
E490
No Block stage
E437
Invalid IRTC address
E491
ISG position error
E438
Invalid IRT address
E492
BEND position error
E440
Invalid Data Address
E493
BEND I error
E441
ACON/NCON
E494
No BEND
E451
Bad MLS/MLR
E452
X input used as output coil
E453
Missing T/C
E454
Bad TMRA
E455
Bad CNT
E456
Bad SR
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
9--9
CPU Indicators
The DL350 CPU has indicators on the front to help you diagnose problems with the
system. The table below gives a quick reference of potential problems associated
with each status indicator. Following the table will be a detailed analysis of each of
these indicator problems.
Potential Problems
PWR (off)
1. System voltage incorrect.
2. Power supply/CPU is faulty
3. Other component such an I/O module has power
supply shorted
4. Power budget exceeded for the base being used
RUN
(will not come on)
1. CPU programming error
2. Switch in TERM position
3. Switch in STOP position
RUN (flashing)
1. CPU in firmware upgrade mode.
CPU (on)
1. Electrical noise interference
2. CPU defective
BATT (on)
1. CPU battery low
2. CPU battery missing, or disconnected
TX1
1. Transmitting data from Port 1
RX1
1. Receiving data at Port 1
TX2
1. Transmitting data from Port 2
RX2
1. Receiving data at Port 2
Status Indicators
Port 1
Maintenance
and Troubleshooting
DL350
Maintenance
and Troubleshooting
Indicator Status
Mode Switch
Port 2
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
Battery Slot
9--10
Maintenance and Troubleshooting
PWR Indicator
Maintenance
and Troubleshooting
There are four general reasons for the CPU power status LED (PWR) to be OFF:
1. Power to the base is incorrect or is not applied.
2. Base power supply is faulty.
3. Other component(s) have the power supply shut down.
4. Power budget for the base has been exceeded.
Incorrect Base
Power
WARNING: To minimize the risk of electrical shock, always disconnect the
system power before inspecting the physical wiring.
Faulty CPU
1. First, disconnect the system power and check all incoming wiring for loose
connections.
2. If you are using a separate termination panel, check those connections to
make sure the wiring is connected to the proper location.
3. If the connections are acceptable, reconnect the system power and
measure the voltage at the base terminal strip to insure it is within
specification. If the voltage is not correct shut down the system and correct
the problem.
4. If all wiring is connected correctly and the incoming power is within the
specifications required, the base power supply should be returned for
repair.
There is not a good check to test for a faulty CPU other than substituting a known
good one to see if this corrects the problem. If you have experienced major power
surges, it is possible the CPU and power supply have been damaged. If you suspect
this is the cause of the power supply damage, a line conditioner which removes
damaging voltage spikes should be used in the future.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
If the voltage to the power supply is not correct, the CPU and/or base may not
operate properly or may not operate at all. Use the following guidelines to correct the
problem.
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
9--11
It is possible a faulty module or external device using the system 5V can shut down
Device or Module
causing the Power the power supply. This 5V can be coming from the base or from the CPU
communication ports.
Supply to
Shutdown
To test for a device causing this problem:
1. Turn off power to the CPU.
2. Disconnect all external devices (i.e., communication cables) from the CPU.
3. Reapply power to the system.
Maintenance
and Troubleshooting
If the power supply operates normally you may have either a shorted device or a
shorted cable. If the power supply does not operate normally then test for a module
causing the problem by following the steps below:
If the PWR LED operates normally the problem could be in one of the modules. To
isolate which module is causing the problem, disconnect the system power and
remove one module at a time until the PWR LED operates normally.
Follow the procedure below:
S Turn off power to the base.
S Remove a module from the base.
S Reapply power to the base.
Bent base connector pins on the module can cause this problem. Check to see the
connector is not the problem.
Power Budget
Exceeded
If the machine had been operating correctly for a considerable amount of time prior
to the indicator going off, the power budget is not likely to be the problem. Power
budgeting problems usually occur during system start-up when the PLC is under
operation and the inputs/outputs are requiring more current than the base power
supply can provide.
Maintenance
and Troubleshooting
WARNING: The PLC may reset if the power budget is exceeded. If there is any
doubt about the system power budget please check it at this time. Exceeding
the power budget can cause unpredictable results which can cause damage
and injury. Verify the modules in the base operate within the power budget for
the chosen base. You can find these tables in Chapter 4, System Design and
Configuration.
Maintenance
and Troubleshooting
DL350 User Manual, 2nd Edition
9--12
Maintenance and Troubleshooting
Maintenance
and Troubleshooting
RUN Indicator
If the CPU will not enter the Run mode (the RUN indicator is off), the problem is
usually in the application program, unless the CPU has a fatal error. If a fatal error
has occurred, the CPU LED should be on. You can use a programming device to
determine the cause of the error.
If you are using a DL350 and you are trying to change the modes with a programming
device, make sure the mode switch is in the TERM position.
Both of the programming devices, Handheld Programmer and DirectSOFT, will
return a error message describing the problem. Depending on the error, there may
also be an AUX function you can use to help diagnose the problem. The most
common programming error is “Missing END Statement”. All application programs
require an END statement for proper termination. A complete list of error codes can
be found in Appendix B.
CPU Indicator
If the CPU indicator is on, a fatal error has occurred in the CPU. Generally, this is not
a programming problem but an actual hardware failure. You can power cycle the
system to clear the error. If the error clears, you should monitor the system and
determine what caused the problem. You will find this problem is sometimes caused
by high frequency electrical noise introduced into the CPU from an outside source.
Check your system grounding and install electrical noise filters if the grounding is
suspected. If power cycling the system does not reset the error, or if the problem
returns, you should replace the CPU.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
BATT Indicator
If the BATT indicator is on, the CPU battery is either disconnected or needs
replacing. The battery voltage is continuously monitored while the system voltage is
being supplied.
Communications Problems
If you cannot establish communications with the CPU, check these items.
S The cable is disconnected.
S The cable has a broken wire or has been wired incorrectly.
S The cable is improperly terminated or grounded.
S The device connected is not operating at the correct baud rate (9600
baud for the top port. Use AUX 56 to select the baud rate for the bottom
port on a DL350).
S The device connected to the port is sending data incorrectly.
S A grounding difference exists between the two devices.
S Electrical noise is causing intermittent errors
S The CPU has a bad comm port and the CPU should be replaced.
S If you are using DirectSOFT, refer to the troubleshooting section of the
Quick Start Manual.
If an error occurs the indicator will come on and stay on until a successful
communication has been completed.
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
9--13
I/O Module Troubleshooting
If you suspect an I/O error, there are several things that could be causing the
problem.
S A blown fuse
S A loose terminal block
S The 24 VDC supply has failed
S The module has failed
S The I/O configuration check detects a change in the I/O configuration
I/O Diagnostics
If the modules are not providing any clues to the problem, run AUX 42 from the
handheld programmer or I/O diagnostics in DirectSOFT. Both options will provide
the base number, the slot number and the problem with the module. Once the
problem is corrected the indicators will reset.
An I/O error will not cause the CPU to switch from the run to program mode, however
there are special relays (SPs) available in the CPU which will allow this error to be
read in ladder logic. The application program can then take the required action such
as entering the program mode or initiating an orderly shutdown. The following figure
shows an example of the failure indicators.
V7752 0020 Desired module ID code
E252
NEW I/O CFG
V7753 0021 Current module ID code
V7754 0002 Location of conflict
Maintenance
and Troubleshooting
Program Control Information
Maintenance
and Troubleshooting
Things to Check
V7755 0252 Fatal error code
I/O Configuration Error
Maintenance
and Troubleshooting
SP47
DL350 User Manual, 2nd Edition
9--14
Maintenance and Troubleshooting
When troubleshooting the DL305 series I/O modules there are a few facts you
should be aware of. These facts may assist you in quickly correcting an I/O problem.
S The output modules cannot detect shorted or open output points. If you
suspect one or more points on a output module to be faulty, you should
measure the voltage drop from the common to the suspect point.
Remember when using a Digital Volt Meter, leakage current from an
output device such as a triac or a transistor must be considered. A point
which is off may appear to be on if no load is connected the the point.
S The I/O point status indicators on the modules are logic side indicators.
This means the LED which indicates the on or off status reflects the
status of the point in respect to the CPU. On an output module the
status indicators could be operating normally while the actual output
device (transistor, triac etc.) could be damaged. With an input module if
the indicator LED is on, the input circuitry should be operating properly.
To verify proper functionality check to see the LED goes off when the
input signal is removed.
S Leakage current can be a problem when connecting field devices to I/O
modules. False input signals can be generated when the leakage
current of an output device is great enough to turn on the connected
input device. To correct this, install a resistor in parallel with the input or
output of the circuit. The value of this resistor will depend on the amount
of leakage current and the voltage applied but usually a 10K to 20KΩ
resistor will work. Insure the wattage rating of the resistor is correct for
your application.
S The easiest method to determine if a module has failed is to replace it if
you have a spare. However, if you suspect another device to have
caused the failure in the module, that device may cause the same
failure in the replacement module as well. As a point of caution, you
may want to check devices or power supplies connected to the failed
module before replacing it with a spare module.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Some Quick Steps
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
Testing Output
Points
9--15
If you want to do an I/O check out independent of the application program, for the
DL350 follow the procedure below:
Step
Action
Use a handheld programmer or DirectSOFT to communicate online to
the PLC.
2
Change to Program Mode.
3
Go to address 0.
4
Insert an “END” statement at address 0. (This will cause program
execution to occur only at address 0 and prevent the application program from turning the I/O points on or off).
5
Change to Run Mode.
6
Use the programming device to set (turn) on or off the points you wish
to test.
7
When you finish testing I/O points delete the “END” statement at
address 0.
WARNING: Depending on your application, forcing I/O points may cause
unpredictable machine operation that can result in a risk of personal injury or
equipment damage. Make sure you have taken all appropriate safety
precautions prior to testing any I/O points.
Handheld
Programmer
Keystrokes Used
to Test an Output
Point
Maintenance
and Troubleshooting
1
END
X0
X2
X1
X3
X5
X7
Y2
Insert an END statement
at the beginning of the
program. This disables
the remainder of the
program.
X4
END
STAT
16P STATUS
BIT REF
X
ENT
Use the PREV or NEXT keys to select the Y data type
NEXT
A
0
Y
ENT
SHFT
ON
INS
Y
0
Y2 is now on
Y
10
Y
0
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
Use arrow keys to select point, then use
ON and OFF to change the status
10
Maintenance
and Troubleshooting
From a clear display, use the following keystrokes
9--16
Maintenance and Troubleshooting
Electrical Noise
Problems
Noise is one of the most difficult problems to diagnose. Electrical noise can enter a
system in many different ways and fall into one of two categories, conducted or
radiated. It may be difficult to determine how the noise is entering the system but the
corrective actions for either of the types of noise problems are similar.
S Conducted noise is when the electrical interference is introduced into
the system by way of a attached wire, panel connection ,etc. It may
enter through an I/O module, a power supply connection, the
communication ground connection, or the chassis ground connection.
S Radiated noise is when the electrical interference is introduced into the
system without a direct electrical connection, much in the same manner
as radio waves.
Reducing
Electrical Noise
While electrical noise cannot be eliminated it can be reduced to a level that will not
affect the system.
S Most noise problems result from improper grounding of the system. A
good earth ground can be the single most effective way to correct noise
problems. If a ground is not available, install a ground rod as close to
the system as possible. Insure all ground wires are single point grounds
and are not daisy chained from one device to another. Ground metal
enclosures around the system. A loose wire is no more than a large
antenna waiting to introduce noise into the system; therefore, you
should tighten all connections in your system. Loose ground wires are
more susceptible to noise than the other wires in your system. Review
Chapter 2 Installation, Wiring, and Specifications if you have questions
regarding how to ground your system.
S Electrical noise can enter the system through the power source for the
CPU and I/O. Installing a isolation transformer for all AC sources can
correct this problem. DC sources should be well grounded good quality
supplies. Switching DC power supplies commonly generate more noise
than linear supplies.
S Separate input wiring from output wiring. Never run I/O wiring close to
high voltage wiring.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Noise Troubleshooting
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
9--17
Machine Startup and Program Troubleshooting
The DL350 CPU provides several features to help you debug your program before
and during machine startup. This section discusses the following topics which can
be very helpful.
Program Syntax Check
S
Duplicate Reference Check
S
Test Modes
S
Special Instructions
S
Run Time Edits
S
Forcing I/O Points
Even though the Handheld Programmer and DirectSOFT provide error checking
during program entry, you may want to check a modified program. Both
programming devices offer a way to check the program syntax. For example, you
can use AUX 21, CHECK PROGRAM to check the program syntax from a Handheld
Programmer, or you can use the PLC Diagnostics menu option within DirectSOFT.
This check will find a wide variety of programming errors. The following example
shows how to use the syntax check with a Handheld Programmer.
Maintenance
and Troubleshooting
Syntax Check
S
Use AUX 21 to perform syntax check
CLR
C
2
B
1
AUX
AUX 21 CHECK PRO
1:SYN 2:DUP REF
ENT
Select syntax check (default selection)
(You may not get the busy display
if the program is not very long.)
BUSY
One of two displays will appear
Error Display (example)
$00050 E401
MISSING END
Maintenance
and Troubleshooting
ENT
(shows location in question)
NO SYNTAX ERROR
?
See Appendix B for a complete listing of programming error codes. If you get an
error, press CLR and the Handheld will display the instruction where the error
occurred. Correct the problem and continue running the Syntax check until the NO
SYNTAX ERROR message appears.
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
Syntax OK display
9--18
Maintenance and Troubleshooting
Duplicate
Reference Check
You can also check for multiple uses of the same output coil. Both programming
devices offer a way to check for this condition. For example, you can AUX 21,
CHECK PROGRAM to check for duplicate references from a Handheld
Programmer, or you can use the PLC Diagnostics menu option within DirectSOFT.
The following example shows how to perform the duplicate reference check with a
Handheld Programmer.
Use AUX 21 to perform syntax check
Maintenance
and Troubleshooting
CLR
C
2
B
1
AUX
ENT
AUX 21 CHECK PRO
1:SYN 2:DUP REF
Select duplicate reference check
ENT
(You may not get the busy
display if the program is not
very long.)
BUSY
One of two displays will appear
Error Display (example)
$00024 E471
DUP COIL REF
(shows location in question)
NO DUP REFS
?
If you get an error, press CLR and the Handheld will display the instruction where the
duplicate reference occurred. Correct the problem and continue running the
Duplicate Reference check until no duplicate references are found.
NOTE: You can use the same coil in more than one location, especially in programs
using the Stage instructions and/or the OROUT instructions. The Duplicate
Reference check will find these outputs even though they may be used in an
acceptable fashion.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Syntax OK display
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
TEST-PGM and
TEST-RUN Modes
9--19
Test Mode allows the CPU to start in TEST-PGM mode, enter TEST-RUN mode, run
a fixed number of scans, and return to TEST-PGM mode. You can select from 1 to
65,525 scans. Test Mode also allows you to maintain output status while you switch
between Test-Program and Test-Run Modes. You can select Test Modes from either
the Handheld Programmer (by using the MODE key) or from DirectSOFT via a PLC
Modes menu option.
The primary benefit of using the TEST mode is to maintain certain outputs and other
parameters when the CPU transitions back to Test-program mode. Also, the CPU
will maintain timer and counter current values when it switches to TEST-PGM mode.
With the Handheld, the actual mode entered when you first select Test Mode
depends on the mode of operation at the time you make the request. If the CPU is in
Run Mode mode, then TEST-RUN is available. If the mode is Program, then
TEST-PGM is available. Once you’ve selected TEST Mode, you can easily switch
between TEST-RUN and TEST-PGM. DirectSOFT provides more flexibility in
selecting the various modes with different menu options. The following example
shows how you can use the Handheld to select the Test Modes.
Maintenance
and Troubleshooting
NOTE: You can only use DirectSOFT to specify the number of scans. This feature is
not supported on the Handheld Programmer. However, you can use the Handheld to
switch between Test Program and Test Run Modes.
Use the MODE key to select TEST Modes (example assumes Run Mode)
MODE
NEXT
*MODE CHANGE*
GO TO T-RUN MODE
ENT
Press ENT to confirm TEST-RUN Mode
ENT
(Note, the TEST LED on the DL205
Handheld indicates the CPU is in
TEST Mode.)
*MODE CHANGE*
CPU T-RUN
CLR
MODE
NEXT
NEXT
*MODE CHANGE*
GO TO T-PGM MODE
ENT
Press ENT to confirm TEST-PGM Mode
ENT
*MODE CHANGE*
CPU T-PGM
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
(Note, the TEST LED on the DL205
Handheld indicates the CPU is in
TEST Mode.)
Maintenance
and Troubleshooting
You can return to Run Mode, enter Program Mode, or enter TEST-PGM
Mode by using the Mode Key
9--20
Maintenance and Troubleshooting
Test Displays: With the Handheld Programmer you also have a more detailed
display when you use TEST Mode. For some instructions, the TEST-RUN mode
display is more detailed than the status displays shown in RUN mode. The following
diagram shows an example of a Timer instruction display during TEST-RUN mode.
RUN Mode
TEST-RUN Mode
S
1425
TMR T0 K1000
Maintenance
and Troubleshooting
TMR T0 K1000
T0 Contact (S is off)
(is on)
S
T0 Contact (S is off)
(is on)
Current Value
Input to Timer
Holding Output States: The ability to hold output states is very useful, because it
allows you to maintain key system I/O points. In some cases you may need to modify
the program, but you do not want certain operations to stop. In normal Run Mode, the
outputs are turned off when you return to Program Mode. In TEST-RUN mode you
can set each individual output to either turn off, or, to hold its last output state on the
transition to TEST-PGM mode. This feature is available via a menu option within
DirectSOFT. The following diagram shows the differences between RUN and
TEST-RUN modes.
RUN Mode to PGM Mode
Maintenance
and Troubleshooting
X2
X1
X3
X10
X2
X1
X3
Y0
X4
X10
Status on final scan
X0
X0
Y0
END
X4
Y1
END
TEST-RUN to TEST-PGM
X0
X2
Y0
X1
X3
X4
Hold Y0 ON
Y1
X10
Maintenance
and Troubleshooting
Outputs are
OFF
Y1
Let Y1 turn
OFF
END
Before you decide that Test Mode is the perfect choice, remember the DL350 CPU
also allows you to edit the program during Run Mode. The primary difference
between the Test Modes and the Run Time Edit feature is you do not have to
configure each individual I/O point to hold the output status. When you use Run Time
Edits, the CPU automatically maintains all outputs in their current states while the
program is being updated.
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
Special
Instructions
9--21
There are several instructions that can be used to help you debug your program
during machine startup operations.
S END
S PAUSE
S STOP
END Instruction: If you need a way to quickly disable part of the program, insert an
END statement prior to the portion that should be disabled. When the CPU
encounters the END statement, it assumes it is the end of the program. The following
diagram shows an example.
X0
X2
X1
X3
Y0
X4
X0
X2
X1
X3
Y0
X4
Y1
X10
END
Y1
X10
Maintenance
and Troubleshooting
New END disables X10 and Y1
Normal Program
END
END
STOP Instruction: Sometimes during machine startup you need a way to quickly
turn off all the outputs and return to Program Mode. In addition to using the Test
Modes, you can also use the STOP instruction. When this instruction is executed the
CPU automatically exits Run Mode and enters Program Mode. Remember, all
outputs are turned off during Program Mode. The following diagram shows an
example of a condition that returns the CPU to Program Mode.
STOP puts CPU in Program Mode
Normal Program
X2
Y0
X20
STOP
X1
X10
X3
X4
Y1
X0
X2
X1
X3
X10
Y0
X4
Y1
END
Maintenance
and Troubleshooting
X0
END
DL350 User Manual, 2nd Edition
Maintenance
and Troubleshooting
In the example shown above, you could trigger X20 which would execute the STOP
instruction. The CPU would enter Program Mode and all outputs would be turned off.
9--22
Maintenance and Troubleshooting
Run Time Edits
The DL350 CPU allows you to make changes to the application program during Run
Mode. These edits are not “bumpless.” Instead, CPU scan is momentarily
interrupted (and the outputs are maintained in their current state) until the program
change is complete. This means if the output is off, it will remain off until the program
change is complete. If the output is on, it will remain on.
Maintenance
and Troubleshooting
WARNING: Only authorized personnel fully familiar with all aspects of the
application should make changes to the program. Changes during Run Mode
become effective immediately. Make sure you thoroughly consider the impact
of any changes to minimize the risk of personal injury or damage to
equipment. There are some important operations sequence changes during
Run Time Edits.
1. If there is a syntax error in the new instruction, the CPU will not enter the
Run Mode.
2. If you delete an output coil reference and the output was on at the time, the
output will remain on until it is forced off with a programming device.
3. Input point changes are not acknowledged during Run Time Edits. So, if
you’re using a high-speed operation and a critical input comes on, the CPU
may not see the change.
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
Not all instructions can be edited during a Run Time Edit session. The following list
shows the instructions that can be edited.
Mnemonic
Description
Mnemonic
Description
TMR
Timer
OR, ORN
TMRF
Fast timer
Or greater than or equal
Or less than
TMRA
Accumulating timer
LD
Load data (constant)
TMRAF
Accumulating fast timer
LDD
Load data double (constant)
CNT
Counter
ADDD
Add data double (constant)
UDC
Up / Down counter
SUBD
Subtract data double (constant)
SGCNT
Stage counter
MUL
Multiply (constant)
STR, STRN
Store, Store not
DIV
Divide (constant)
AND, ANDN
And, And not
CMPD
Compare accumulator (constant)
OR, ORN
Or, Or not
ANDD
And accumulator (constant)
STRE, STRNE
Store equal, Store not equal
ORD
Or accumulator (constant)
ANDE, ANDNE
And equal, And not equal
XORD
Exclusive or accumulator (constant)
ORE, ORNE
Or equal, Or not equal
LDF
Load discrete points to accumulator
STR, STRN
Store greater than or equal
Store less than
OUTF
Output accumulator to discrete points
SHFR
Shift accumulator right
AND, ANDN
And greater than or equal
And less than
SHFL
Shift accumulator left
NCON
Numeric constant
DL350 User Manual, 2nd Edition
Maintenance and Troubleshooting
Use the program logic shown to describe
how this process works. In the example,
change X0 to C10. Note, the example assumes you have already placed the CPU
in Run Mode.
X0
X1
9--23
Y0
OUT
C0
Use the MODE key to select Run Time Edits
NEXT
NEXT
*MODE CHANGE*
RUN TIME EDIT?
ENT
Press ENT to confirm the Run Time Edits
ENT
(Note, the RUN LED on the DL205
Handheld starts flashing to indicate
Run Time Edits are enabled.)
*MODE CHANGE*
RUNTIME EDITS
Maintenance
and Troubleshooting
MODE
Find the instruction you want to change (X0)
SHFT
X
SET
A
0
SHFT
FD REF
FIND
$00000 STR X0
Press the arrow key to move to the X. Then enter the new contact (C10).
SHFT
C
2
B
1
A
0
ENT
RUNTIME EDIT?
STR C10
ENT
(Note, once you press ENT, the next
address is displayed.
OR C0
Maintenance
and Troubleshooting
Press ENT to confirm the change
Maintenance
and Troubleshooting
DL350 User Manual, 2nd Edition
9--24
Maintenance and Troubleshooting
Forcing I/O Points
There are many times, especially during machine startup and troubleshooting,
where you need the capability to force an I/O point to be either on or off. Before you
use a programming device to force any data type, it is important to understand how
the DL350 CPU processes the forcing requests.
Maintenance
and Troubleshooting
WARNING: Only authorized personnel fully familiar with all aspects of the
application should make changes to the program. Make sure you thoroughly
consider the impact of any changes to minimize the risk of personal injury or
damage to equipment.
Regular Forcing — This type of forcing can temporarily change the
status of a discrete bit. For example, you may want to force an input on,
even though it is really off. This allows you to change the point status
that was stored in the image register. This value will be valid until the
image register location is written to during the next scan. This is
primarily useful during testing situations when you need to force a bit on
to trigger another event.
S
The following diagrams show a brief
example of how you could use the
Handheld Programmer to force an I/O
point. The image register will not be
updated with the status from the input
module. Also, the solution from the
application program will not be used to
update the output image register. The
example assumes you have already
placed the CPU into Run Mode.
X0
Y0
OUT
C0
From a clear display, use the following keystrokes
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
STAT
16P STATUS
BIT REF
X
ENT
Use the PREV or NEXT keys to select the Y data type. (Once the Y
appears, press 0 to start at Y0.)
NEXT
A
0
Y
ENT
Use arrow keys to select point, then use
ON and OFF to change the status
SHFT
DL350 User Manual, 2nd Edition
ON
INS
10
Y
0
Y
0
Y2 is now on
Y
10
Maintenance and Troubleshooting
Regular Forcing
with Direct Access
From a clear display, use the following
keystrokes to force Y10 ON
SHFT
Y
MLS
B
1
A
0
SHFT
ON
INS
B
1
A
0
SHFT
OFF
DEL
No fill indicates point is off.
BIT FORCE
Y10
Maintenance
and Troubleshooting
Y
MLS
Solid fill indicates point is on.
BIT FORCE
Y10
From a clear display, use the following
keystrokes to force Y10 OFF
SHFT
9--25
Maintenance
and Troubleshooting
Maintenance
and Troubleshooting
DL350 User Manual, 2nd Edition
1
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement