NT Motor&Encoder Module CLI - Revision history

OlliW at 06:04, 9 July 2019

2019-07-09T06:04:29Z

← Older revision		Revision as of 08:04, 9 July 2019
Line 1:		Line 1:
	~~Accessing the~~ CLI of a NT motor&encoder module ~~requires~~ using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].		The CLI of a NT motor&encoder module can be accesses either by using the "NT Module CLI Tool" located in the {{GUI\|Tools}} menu, or by using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].

	For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.		For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.

OlliW at 11:08, 7 August 2018

2018-08-07T11:08:39Z

← Older revision		Revision as of 13:08, 7 August 2018
Line 36:		Line 36:
	\|-		\|-
	\| r2setvmax X; \|\| set the motor power in percent used in the r2 commands		\| r2setvmax X; \|\| set the motor power in percent used in the r2 commands
			\|-
			\|
			\|-
			\| setlpf2n; \|\| set LPF for potentiometric encoders
			\|-
			\| clrlpf2n; \|\| disable LPF for potentiometric encoders
	\|-		\|-
	\|		\|

OlliW at 05:32, 10 May 2018

2018-05-10T05:32:54Z

← Older revision		Revision as of 07:32, 10 May 2018
Line 89:		Line 89:
	\|		\|
	\|-		\|-
	\| @Q \|\| resets main board and module		\| @Q \|\| resets main board and module, note: don't add a ';' at the end
	\|-		\|-
	\| RESTART \|\| restarts QMODE		\| RESTART; \|\| restarts QMODE
	\|}		\|}

OlliW at 07:28, 4 May 2018

2018-05-04T07:28:09Z

← Older revision		Revision as of 09:28, 4 May 2018
Line 1:		Line 1:
	Accessing the CLI of a NT motor&encoder module requires using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].		Accessing the CLI of a NT motor&encoder module requires using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].

	For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port~~, as usual~~. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.		For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.

	{{COMMENT\|The CLI can also be accessed by connecting the NT motor module on its NT port directly to a PC via a USB-TTL adapter, pretty much as one would do for the [[NT_Data_Logging#Live_Recording\|Live Recording]], except that now both the Tx and Rx lines need to be connected to the USB-TTL adapter. In the terminal program the baud rate must be set to 2000000 bps.}}		{{COMMENT\|The CLI can also be accessed by connecting the NT motor module on its NT port directly to a PC via a USB-TTL adapter, pretty much as one would do it for the [[NT_Data_Logging#Live_Recording\|Live Recording]], except that now both the Tx and Rx lines need to be connected to the USB-TTL adapter. In the terminal program the baud rate must be set to 2000000 bps.}}

	{\| class="wikitable"		{\| class="wikitable"

OlliW at 07:07, 1 May 2018

2018-05-01T07:07:29Z

← Older revision		Revision as of 09:07, 1 May 2018
Line 71:		Line 71:
	\| setmodelas5048a; \|\| set the module's encoder to AS5048A (spi)		\| setmodelas5048a; \|\| set the module's encoder to AS5048A (spi)
	\|-		\|-
	\| setmodelpotadc5; \|\| set the module's encoder to a ~~potentiometer~~ on ADC5		\| setmodelpotadc5; \|\| set the module's encoder to a resistive sensor (poti) on ADC5
	\|-		\|-
	\| clrmodel; \|\| set the module's encoder to NONE		\| clrmodel; \|\| set the module's encoder to NONE

OlliW at 07:06, 1 May 2018

2018-05-01T07:06:35Z

← Older revision		Revision as of 09:06, 1 May 2018
Line 3:		Line 3:
	For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port, as usual. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.		For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port, as usual. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.

	{{COMMENT\|The CLI can also be accessed by connecting the NT motor module on its NT port directly to a PC via a USB-TTL adapter, pretty much as one would do for [[NT_Data_Logging#Live_Recording\|Live Recording]], except that now both the Tx and Rx lines need to be connected to the USB-TTL adapter. In the terminal program the baud rate must be set to 2000000 bps.}}		{{COMMENT\|The CLI can also be accessed by connecting the NT motor module on its NT port directly to a PC via a USB-TTL adapter, pretty much as one would do for the [[NT_Data_Logging#Live_Recording\|Live Recording]], except that now both the Tx and Rx lines need to be connected to the USB-TTL adapter. In the terminal program the baud rate must be set to 2000000 bps.}}

	{\| class="wikitable"		{\| class="wikitable"
Line 29:		Line 29:
	\| r2ppofs; \|\| run the ranged motor pole pairs and offset determination sequence		\| r2ppofs; \|\| run the ranged motor pole pairs and offset determination sequence
	\|-		\|-
	\| ~~r2ofs~~ X; \|\| run the ranged motor pole pairs and offset determination sequence, with the number of pole pairs fixed to the given value		\| r2sppofs X; \|\| run the ranged motor pole pairs and offset determination sequence, with the number of the pole pairs fixed to the given value
			\|-
			\| r2ofs; \|\| run the ranged motor offset determination sequence
	\|-		\|-
	\| r2setrange X; \|\| set the range used in the r2 commands		\| r2setrange X; \|\| set the range used in the r2 commands

OlliW at 21:30, 30 April 2018

2018-04-30T21:30:19Z

← Older revision		Revision as of 23:30, 30 April 2018
Line 1:		Line 1:
	Accessing the CLI of a NT motor&encoder module requires using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].		Accessing the CLI of a NT motor&encoder module requires using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].

	~~It can be done in two ways:~~		For accessing the CLI, the STorM32 main board is used, so to say, as a USB-TTL adapter to connect the NT module to the PC. That is, the NT motor module is connected to the STorM32 main board on the NT bus and the STorM32 main board is connected to a PC, typically via the main board's USB port, as usual. Before the CLI can be accessed, the STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.
	* '''''Direkt Connection:''''' The NT motor module is connected on ~~its~~ NT ~~port directly~~ to a PC via a USB~~-TTL adapter~~, ~~pretty much~~ as ~~one would do for [[NT_Data_Logging#Live_Recording\|Live Recording]]~~, ~~except that now both~~ the ~~Tx and Rx lines need~~ to be ~~connected~~ to the ~~USB-TTL adapter~~. In the terminal program the baud rate ~~must be~~ set to ~~2000000~~ bps.

	* '''''Via STorM32 Main Board:''''' In this configuration, a STorM32 main board is used, so to say, as USB-TTL adapter. The NT motor module ~~is connected to the STorM32 main board via the~~ NT ~~bus, as for normal operation. The STorM32 main board is connected~~ to a PC~~, typically~~ via ~~the main board's~~ USB ~~port. The STorM32 main board has first to be put into a pass~~-~~through mode by sending the special command "xQTNTQMODE0X" to it~~, ~~where X = 4~~ for ~~accessing~~ the ~~pitch NT motor module, X = 5 for roll,~~ and ~~X = 6 for yaw. The STorM32 board then works as tunnel connecting~~ the ~~PC with the selected NT module~~. In the terminal program the baud rate ~~is typically~~ set to ~~115200~~ bps.		{{COMMENT\|The CLI can also be accessed by connecting the NT motor module on its NT port directly to a PC via a USB-TTL adapter, pretty much as one would do for [[NT_Data_Logging#Live_Recording\|Live Recording]], except that now both the Tx and Rx lines need to be connected to the USB-TTL adapter. In the terminal program the baud rate must be set to 2000000 bps.}}

	{\| class="wikitable"		{\| class="wikitable"
Line 17:		Line 16:
	\|-		\|-
	\| reval; \|\| run the display encoder raw values sequence, send a character to stop it		\| reval; \|\| run the display encoder raw values sequence, send a character to stop it
			\|-
			\|
			\|-
			\| moveby X; \|\| moves the motor by the given value (can be positive or negative)
			\|-
			\| moveto X; \|\| moves the motor to the position specified by the given value (can be positive or negative)
			\|-
			\| movevmax X; \|\| set the motor power in percent
			\|-
			\|
			\|-
			\| r2ppofs; \|\| run the ranged motor pole pairs and offset determination sequence
			\|-
			\| r2ofs X; \|\| run the ranged motor pole pairs and offset determination sequence, with the number of pole pairs fixed to the given value
			\|-
			\| r2setrange X; \|\| set the range used in the r2 commands
			\|-
			\| r2setvmax X; \|\| set the motor power in percent used in the r2 commands
	\|-		\|-
	\|		\|
Line 26:		Line 43:
	\| clrofs; \|\| set the current offset to zero		\| clrofs; \|\| set the current offset to zero
	\|-		\|-
	\| setpp X; \|\| set the current pole pairs to the given value		\| setpp X; \|\| set the current pole pairs to the given value
	\|-		\|-
	\| setofs X; \|\| set the current poffset to the given value		\| setofs X; \|\| set the current poffset to the given value
Line 51:		Line 68:
	\|-		\|-
	\| setmodelas5048a; \|\| set the module's encoder to AS5048A (spi)		\| setmodelas5048a; \|\| set the module's encoder to AS5048A (spi)
			\|-
			\| setmodelpotadc5; \|\| set the module's encoder to a potentiometer on ADC5
	\|-		\|-
	\| clrmodel; \|\| set the module's encoder to NONE		\| clrmodel; \|\| set the module's encoder to NONE

OlliW at 20:11, 8 October 2017

2017-10-08T20:11:48Z

← Older revision		Revision as of 22:11, 8 October 2017
Line 47:		Line 47:
	\|-		\|-
	\| clrid; \|\| set the module's ID to ID = 0		\| clrid; \|\| set the module's ID to ID = 0
			\|-
			\| setmodeltle5012b; \|\| set the module's encoder to TLE5012B (spi)
			\|-
			\| setmodelas5048a; \|\| set the module's encoder to AS5048A (spi)
			\|-
			\| clrmodel; \|\| set the module's encoder to NONE
	\|-		\|-
	\|		\|

OlliW at 09:40, 14 May 2017

2017-05-14T09:40:08Z

← Older revision		Revision as of 11:40, 14 May 2017
Line 1:		Line 1:
			Accessing the CLI of a NT motor&encoder module requires using a standard terminal program, such as [http://www.der-hammer.info/terminal/index.htm HTerm].

			It can be done in two ways:
			* '''''Direkt Connection:''''' The NT motor module is connected on its NT port directly to a PC via a USB-TTL adapter, pretty much as one would do for [[NT_Data_Logging#Live_Recording\|Live Recording]], except that now both the Tx and Rx lines need to be connected to the USB-TTL adapter. In the terminal program the baud rate must be set to 2000000 bps.

			* '''''Via STorM32 Main Board:''''' In this configuration, a STorM32 main board is used, so to say, as USB-TTL adapter. The NT motor module is connected to the STorM32 main board via the NT bus, as for normal operation. The STorM32 main board is connected to a PC, typically via the main board's USB port. The STorM32 main board has first to be put into a pass-through mode by sending the special command "xQTNTQMODE0X" to it, where X = 4 for accessing the pitch NT motor module, X = 5 for roll, and X = 6 for yaw. The STorM32 board then works as tunnel connecting the PC with the selected NT module. In the terminal program the baud rate is typically set to 115200 bps.

	{\| class="wikitable"		{\| class="wikitable"
	!CLI command		!CLI command

OlliW at 07:24, 14 May 2017

2017-05-14T07:24:49Z

← Older revision		Revision as of 09:24, 14 May 2017
Line 43:		Line 43:
	\|		\|
	\|-		\|-
	\| r4; \|\| run the ~~determine~~ torque cogging sequence		\| r4; \|\| run the torque cogging sequence
	\|-		\|-
	\| getdt; \|\| display the determined time constants		\| getdt; \|\| display the determined time constants