Download User Manual - LUCKINSlive

Transcript
Case 3
Line fault
Results
After loading a project, some bus slaves start and become faulty.
Causes
Actions
A line termination is detected but it is not at
the end of the bus.
 Test all the Profibus DP connectors and
place the bus termination at the end of the
line.
Case 4
Faulty slave
Results
A bus slave is faulty but has not caused a bus error.
Causes
Actions
The slave has some input/output errors or
configuration error or the watchdog is
inactive
 Test the slave diagnostics data via the
debugging screen.
Case 5
Delay in starting up the slave
Results
Bus slaves do not react immediately to start-up without causing a bus error. After a while, the
slave starts.
Causes
Actions
Some slaves require a control command
before being activated. These slaves have
been too slow to react to the first command
sent
 Modify the bus parameters to delay the
35006212 10/2013
sending of the first command.
 Add 5 time units to the Timeout.
89