Using the trace

In the simplest configuration the data trace allows you to look at servo and profile parameters to determine how the system is functioning. In this mode the trace capture typically starts at the moment the motion “go” command is given, and stops when the trace buffer is filled. As long as the axis under study settles by the time the trace buffer is filled, this type of capture will be satisfactory.

Some applications require the trace to start upon the occurrence of some event. In the case of the Navigator/Magellan chipset any of the numerous digital signals may be specified as the trace start trigger, as well as any of several internal chipset events. This is useful for looking at events that happen not at a particular time, but based on some external system occurrence.

Sometimes it is useful to capture continuously and stop the trace upon some event. This can be accomplished using the Navigator or Magellan chipset by putting the trace in rolling mode, and setting a special stop condition. This can be used to look at the performance of the motion leading up to a particular event. For example if a servo error occurs very infrequently, the Navigator/Magellan chipset can be set to stop the trace on a servo error. Depending on the size of the trace buffer, seconds or even minutes of the preceding trace data will then be captured, showing how the system behaved leading up to the final event.