Diagnostics Help

At a Glance

Situations may arise which you have to resolve. The following procedure is designed to help diagnose these situations, and indicates the path to follow.

What to Do in Situations

New parameters not taken into account

Problem	The TSX CAY module does not seem to have registered the new parameters written by WRITE_PARAM.
Diagnostics	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
What to do	Test the ADJ_IN_PROGR (%MWr.m.c.0.2) bit before exchanging any adjustment parameters.

Event processing

Problem	The event processing associated with the axis control channel has not been executed.
Diagnostics	Check that the whole event feedback string has been confirmed: 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 (AUX0MINTIME(%S38) = 1). Unmasked events at system level (UNMASKEVT()).
What to do	Refer to event usage.

Lost adjustments

Problem	Adjustments have been lost.
Diagnostics	A cold restart can cause current adjustments that have been carried out via a screen or by a WRITE_PARAM instruction to be lost.
What to do	Save current adjustments by using the Utilities → Save parameters command, or by using the SAVE_PARAM instruction.

Inconsistent status words

Problem	EXCH_RPT (%MWr.m.c.1) and CH_FLT (%MWr.m.c.2) status words are inconsistent with the status of the axis control channel.
Diagnostics	These words are only updated through an explicit READ_STS request.
What to do	Program a READ_STS instruction into the application.

Encoder supply fault

Problem	The encoder supply fault persists while the encoder is properly supplied and the current value is changing.
Diagnostics	The encoder supply return signal has not been wired correctly.
What to do	Check the encoder connections.

Ineffective commands

Problem	The debugging screen commands are ineffective.
Diagnostics	The application or the task is in STOP mode.
What to do	Change the application or the task to RUN mode.

Non-modifiable commands

Problem	Certain debugging screen commands cannot be modified.
Diagnostics	These bits are written by the application.
What to do	Use bit forcing (for %Qr.m.c.d 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	It is not possible to enter more than 3 characters into the digital fields in the adjustment and configuration screens.
Diagnostics	The thousands separator has not been selected in the Windows configuration panel.
What to do	In the Windows configuration panel, select the International icon in the Number format field. Activate the Modify command and choose a thousands separator.