User Tools

Site Tools


commands:dump

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
commands:dump [2018/06/11 18:10]
jon [Table]
commands:dump [2019/04/18 23:33] (current)
Line 1: Line 1:
 +====== Command:​DUMP (DU) ======
  
 +--> MS2000 or RM2000 syntax#
 +
 +^Shortcut ​ |DU| 
 +^Format ​ |DUMP [X] [Y][F] |
 +^Units ​   |none|
 +
 +<--
 +
 +--> Tiger syntax# ​
 +
 +^ Shortcut ​   | DU                                         |
 +^ Format ​     | [addr#]DUMP [X][Y][F][R=mode][T=interval] ​ |
 +^ Units       | none                                       |
 +^ Type        | Card-Addressed ​                            |
 +^ Remembered ​ | not possible ​                              |
 +
 +<--
 +
 +Dump internal buffers to terminal screen.
 +
 +The Tiger and MS-2000 controller has several built-in diagnostic capabilities that are useful for troubleshooting difficulties and for tuning the servo motion parameters. ​ It is often useful to see how well the servo motion is tracking the theoretical trajectory. The controller has a built-in buffer that can hold 200 to 500 move steps. ​ For best results, restrict testing to a single axis at a time; otherwise information from multiple axes will be interleaved in the dump buffer. ​ Any motion from any axis will write information into the dump buffer until it is full.  ​
 +
 +''​DU'',​ without arguments, dumps the Trajectory Buffer.
 +
 +''​DU X''​ clears Trajectory Buffer.
 +
 +''​DU Y''​ dumps Error Buffer. See [[:​error_codes|Error Codes for MS2000,​RM2000 and TG-1000 Diagnostics]]
 +
 +''​DU F''​ Prints controller log, it has information like total time controller was ON, Total distance XY stage travelled and others. The log first has to be initialized with command <wrap cmd> DU F=999 </​wrap>​. This is done in the factory, and we suggest users not reset the log as it may wipe data that is useful for ASIs long term reliability study. ​
 +
 +''​DU R=mode''​ sets the trajectory buffer mode (introduced in Tiger v3.19). ​ Mode 0 (default) means the trajectory buffer, once full, will not be changed further. ​ Mode 1 continuously overwrites the trajectory buffer information so that the most recent move information is always present.
 +
 +''​DU T=interval''​ sets the sampling interval for the trajectory buffer (introduced in Tiger v3.19). ​ Default is 1 which adds to the trajectory buffer on every axis loop.  Setting to e.g. 10 will add to the buffer once and then skip the next 9 axis loops. ​ Handy for looking at longer-term trends.
 +
 +
 +--> Tiger Example#
 +
 +<wrap cmd> 1DU X </​wrap> ​       Clears the dump buffers on card#1 \\
 +Then make a short move, e.g.: <wrap cmd> M X=12345 </​wrap> ​  ​[Moves about 1.23 mm]
 +After the move is complete, you can dump the buffer to the screen:
 +<wrap cmd> 1DU </​wrap> ​         Dumps Trajectory Buffer on card #1 \\
 +<wrap cmd> 2DU Y </​wrap> ​       Dumps Error Buffer on card #2 \\
 +<wrap cmd> 4DU F </​wrap> ​       Dumps Card#​4'​s Piezo History \\
 +<wrap cmd> 4DU F=999 </​wrap> ​   Resets Card#​4'​s Piezo History \\
 +<--
 +
 +-->​MS2000 Example#
 +
 +<wrap cmd> DU X </​wrap> ​       Clears the dump buffers \\
 +Then make a short move, e.g.: M X=12345 ​  ​[Moves about 1.23 mm] \\
 +After the move is complete, you can dump the buffer to the screen: \\
 +<wrap cmd> DU  </​wrap> ​        Dumps Trajectory Buffer \\
 +<wrap cmd> DU Y  </​wrap> ​      Dumps Error Buffer \\
 +<wrap cmd> DU F </​wrap> ​       Dumps Piezo History \\
 +<wrap cmd> DU F=999 </​wrap> ​   Resets Piezo History \\
 +
 +
 +<--
 +
 +
 +
 +{{tag>​commands tiger ms2000}}
commands/dump.txt · Last modified: 2019/04/18 23:33 (external edit)