Diagnostics and maintenance
Diagnostics help
Introduction
What to do in situations
Situations may arise which you have to resolve. The following procedure is designed to help diagnose these situations, and indicates the path to follow.
New parameters not taken into account
Problem
Diagnostics
What to do
The TSX CAY module does not seem to have registered the new parameters written by WRITE_PARAM.
Program a READ_PARAM instruction into the application to find out the values actually being used by the module.
A WRITE_PARAM is triggered and ignored while exchanging other adjustment parameters
Test the %Mwxy.i.0.X2 bit before exchanging any adjustment parameters.
Event processing
Problem
Diagnostics
What to do
The event processing associated with the axis control channel has not been executed.
l l l
Check that the whole event feedback string has been confirmed: l Event number declared in the configuration is identical to the one in event processing.
Origin of event unmasked (M code from the SMOVE command).
Events authorized at system level (%S38 = 1.
Unmasked events at system level (UNMASKEVT()).
Refer to event usage.
Lost adjustments
Problem
Diagnostics
What to do
Adjustments have been lost.
A cold restart can cause current adjustments that have been carried out via a screen or by a WRITE_PARAM instruction to be lost.
Save current adjustments by using the Utilities
→
Save parameters command, or by using the SAVE_PARAM instruction.
Inconsistent status words
Problem
Diagnostics
What to do
%Mwxy.i.1 and %Mwxy.i.2 status words are inconsistent with the status of the axis control channel.
These words are only updated through an explicit READ_STS request.
Program a READ_STS instruction into the application.
TLX DS 57 PL7xx
247
Diagnostics and maintenance
Encoder supply fault
Problem
Diagnostics
What to do
The encoder supply fault persists while the encoder is properly supplied and the current value is changing.
The encoder supply return signal has not been wired correctly.
Check the encoder connections.
Ineffective commands
Problem
Diagnostics
What to do
The debugging screen commands are ineffective.
The application or the task is in STOP mode.
Change the application or the task to RUN mode.
Non-modifiable commands
Problem
Diagnostics
What to do
Certain debugging screen commands cannot be modified.
These bits are written by the application.
Use bit forcing (for %Qxy.i.r type objects) or re-do the application to avoid systematic writing of these bits (modification on transition and not on status).
Character entry not possible
Problem
Diagnostics
What to do
It is not possible to enter more than 3 characters into the digital fields in the adjustment and configuration screens.
The thousands separator has not been selected in the Windows configuration panel.
In the Windows configuration panel, select the International icon in the
Number format field.
Activate the Modify command and choose a thousands separator.
248
TLX DS 57 PL7xx
