Diagnostic help
(Original Document)
About us
At a Glance
You might be faced with situations that you need to resolve. The following procedure helps you to diagnose these situations and informs you of what to do.
Procedure to follow in various situations
New parameters are not recognized
Symptom
The TSX CFY module does not seem to have recognized the new parameters written by WRITE_PARAM
Diagnostics
Program a READ_PARAM instruction into your application so that you can find out the values actually used by the module.
A WRITE_PARAM activated while another adjustment exchange is in progress is ignored.
What to do
Test the ADJ_IN_PROGR bit (%MWr.m.c.0.2) before any adjustment exchange
Event processing
Symptom
The event processing associated with the axes control channel is not executed
Diagnostics
Check that the whole event trace string is valid
  • Event number declared in the configuration is identical to that in the event processing,
  • The event source is unmasked (code M of the SMOVE command),
  • Events are authorized at system level ACTIVEVT = 1 (%S38),
  • Events are unmasked at system level (UNMASKEVT)
What to do
Refer to the use of events
Adjustments are lost
Symptom
Your adjustments have been lost
Diagnostics
A cold start causes the loss of the current adjustments carried out via the screen or a WRITE_PARAM instruction
What to do
Save the current adjustments using the command Service → Save parameters or using the instruction SAVE_PARAM
Inconsistent status words
Symptom
The status words EXCH_RPT (%MWr.m.c.1) and CH_FLT (%MWr.m.c.2) are not consistent with the status of the axis control channel.
Diagnostics
These words are only updated on the explicit request READ_STS
What to do
Program a READ_STS instruction in your application
Ineffectual commands
Symptom
The commands from the debug screen are not having any effect
Diagnostics
The application or the task is in STOP mode
What to do
Switch the application or the task into RUN mode
Non modifiable commands
Symptom
Certain commands from the debug screen are not modifiable
Diagnostics
These bits are written by the application
What to do
Use bit forcing for objects of type %Qr.m.c.d or rewrite your application so that it does not write these bits systematically (modification on transition and not on state)
Impossible to enter characters
Symptom
It is impossible to enter more than 3 characters in the numeric fields of the adjustment and configuration screens
Diagnostics
In the Windows configuration panel, you have not selected the thousand separator
What to do
In the Windows configuration panel, select the icon International in the field Number format.
Activate the Modify command and select a thousand separator
Command refused
Symptom
In DIRDRIVE mode, after a stop after exceeding the soft stops, commands are refused.
Diagnostics
The DIRDRIVE mode is activated after a session in MANU or AUTO mode during which a reference point has been taken. The axis is referenced. Monitoring of soft stops is active.
Exceeding one of these limits causes a stop with an error.
No further movement in DIRDRIVE mode is accepted.
What to do
Two types of actions are possible to restart movements:
  • Cause the loss of the axis reference, after the moving part has completely stopped:
    • unset the channel, ENABLE = 0 (%Qr.m.c.10)
    • reset the channel, ENABLE = 1 (%Qr.m.c.10)
    • acknowledge the error (rising edge on the command ACK_FLT (%Qr.m.c.9))
  • Force the position of the moving part between the soft stops:
    • switch for a moment to MANU mode
    • acknowledge the error: ACK_FLT (%Qr.m.c.9)
    • take a forced reference point at a position situated between the soft stops
    • switch back to DIRDRIVE mode.
Bad recognition of commands in AUTO mode
Symptom
In AUTO mode, after overshooting the soft stops of the end of run, movement commands are not carried out correctly.
Diagnostics
After overshooting an end of run limit, the only commands accepted are movement commands going back in the return direction between the end of run limits.
What to do
Check whether the movement requested and incorrectly carried out was aiming to bring the moving part back between the end of run limits.