LabVIEW - Stepper Brick

This is the description of the LabVIEW API bindings for the Stepper Brick. General information and technical specifications for the Stepper Brick are summarized in its hardware description.

An installation guide for the LabVIEW API bindings is part of their general description.

API

Generally, every method of the LabVIEW bindings that outputs a value can report a Tinkerforge.TimeoutException. This error gets reported if the device did not respond. If a cable based connection is used, it is unlikely that this exception gets thrown (assuming nobody plugs the device out). However, if a wireless connection is used, timeouts will occur if the distance to the device gets too big.

The namespace for all Brick/Bricklet bindings and the IPConnection is Tinkerforge.*.

Basic Functions

BrickStepper(uid, ipcon) → stepper
Input:
  • uid -- String
  • ipcon -- .NET Refnum (IPConnection)
Output:
  • stepper -- .NET Refnum (BrickStepper)

Creates an object with the unique device ID uid. This object can then be used after the IP Connection is connected (see examples above).

BrickStepper.SetMaxVelocity(velocity)
Input:
  • velocity -- Int32

Sets the maximum velocity of the stepper motor in steps per second. This function does not start the motor, it merely sets the maximum velocity the stepper motor is accelerated to. To get the motor running use either SetTargetPosition(), SetSteps(), DriveForward() or DriveBackward().

BrickStepper.GetMaxVelocity() → velocity
Output:
  • velocity -- Int32

Returns the velocity as set by SetMaxVelocity().

BrickStepper.GetCurrentVelocity() → velocity
Output:
  • velocity -- Int32

Returns the current velocity of the stepper motor in steps per second.

BrickStepper.SetSpeedRamping(acceleration, deacceleration)
Input:
  • acceleration -- Int32
  • deacceleration -- Int32

Sets the acceleration and deacceleration of the stepper motor. The values are given in steps/s². An acceleration of 1000 means, that every second the velocity is increased by 1000 steps/s.

For example: If the current velocity is 0 and you want to accelerate to a velocity of 8000 steps/s in 10 seconds, you should set an acceleration of 800 steps/s².

An acceleration/deacceleration of 0 means instantaneous acceleration/deacceleration (not recommended)

The default value is 1000 for both

BrickStepper.GetSpeedRamping() → acceleration, deacceleration
Output:
  • acceleration -- Int32
  • deacceleration -- Int32

Returns the acceleration and deacceleration as set by SetSpeedRamping().

BrickStepper.FullBrake()

Executes an active full brake.

Warning

This function is for emergency purposes, where an immediate brake is necessary. Depending on the current velocity and the strength of the motor, a full brake can be quite violent.

Call Stop() if you just want to stop the motor.

BrickStepper.SetSteps(steps)
Input:
  • steps -- Int32

Sets the number of steps the stepper motor should run. Positive values will drive the motor forward and negative values backward. The velocity, acceleration and deacceleration as set by SetMaxVelocity() and SetSpeedRamping() will be used.

BrickStepper.GetSteps() → steps
Output:
  • steps -- Int32

Returns the last steps as set by SetSteps().

BrickStepper.GetRemainingSteps() → steps
Output:
  • steps -- Int32

Returns the remaining steps of the last call of SetSteps(). For example, if SetSteps() is called with 2000 and GetRemainingSteps() is called after the motor has run for 500 steps, it will return 1500.

BrickStepper.DriveForward()

Drives the stepper motor forward until DriveBackward() or Stop() is called. The velocity, acceleration and deacceleration as set by SetMaxVelocity() and SetSpeedRamping() will be used.

BrickStepper.DriveBackward()

Drives the stepper motor backward until DriveForward() or Stop() is triggered. The velocity, acceleration and deacceleration as set by SetMaxVelocity() and SetSpeedRamping() will be used.

BrickStepper.Stop()

Stops the stepper motor with the deacceleration as set by SetSpeedRamping().

BrickStepper.SetMotorCurrent(current)
Input:
  • current -- Int32

Sets the current in mA with which the motor will be driven. The minimum value is 100mA, the maximum value 2291mA and the default value is 800mA.

Warning

Do not set this value above the specifications of your stepper motor. Otherwise it may damage your motor.

BrickStepper.GetMotorCurrent() → current
Output:
  • current -- Int32

Returns the current as set by SetMotorCurrent().

BrickStepper.Enable()

Enables the driver chip. The driver parameters can be configured (maximum velocity, acceleration, etc) before it is enabled.

BrickStepper.Disable()

Disables the driver chip. The configurations are kept (maximum velocity, acceleration, etc) but the motor is not driven until it is enabled again.

BrickStepper.IsEnabled() → enabled
Output:
  • enabled -- Boolean

Returns true if the driver chip is enabled, false otherwise.

Advanced Functions

BrickStepper.SetCurrentPosition(position)
Input:
  • position -- Int32

Sets the current steps of the internal step counter. This can be used to set the current position to 0 when some kind of starting position is reached (e.g. when a CNC machine reaches a corner).

BrickStepper.GetCurrentPosition() → position
Output:
  • position -- Int32

Returns the current position of the stepper motor in steps. On startup the position is 0. The steps are counted with all possible driving functions (SetTargetPosition(), SetSteps(), DriveForward() or DriveBackward()). It also is possible to reset the steps to 0 or set them to any other desired value with SetCurrentPosition().

BrickStepper.SetTargetPosition(position)
Input:
  • position -- Int32

Sets the target position of the stepper motor in steps. For example, if the current position of the motor is 500 and SetTargetPosition() is called with 1000, the stepper motor will drive 500 steps forward. It will use the velocity, acceleration and deacceleration as set by SetMaxVelocity() and SetSpeedRamping().

A call of SetTargetPosition() with the parameter x is equivalent to a call of SetSteps() with the parameter (x - GetCurrentPosition()).

BrickStepper.GetTargetPosition() → position
Output:
  • position -- Int32

Returns the last target position as set by SetTargetPosition().

BrickStepper.SetStepMode(mode)
Input:
  • mode -- Byte

Sets the step mode of the stepper motor. Possible values are:

  • Full Step = 1
  • Half Step = 2
  • Quarter Step = 4
  • Eighth Step = 8

A higher value will increase the resolution and decrease the torque of the stepper motor.

The default value is 8 (Eighth Step).

The following constants are available for this function:

  • BrickStepper.STEP_MODE_FULL_STEP = 1
  • BrickStepper.STEP_MODE_HALF_STEP = 2
  • BrickStepper.STEP_MODE_QUARTER_STEP = 4
  • BrickStepper.STEP_MODE_EIGHTH_STEP = 8
BrickStepper.GetStepMode() → mode
Output:
  • mode -- Byte

Returns the step mode as set by SetStepMode().

The following constants are available for this function:

  • BrickStepper.STEP_MODE_FULL_STEP = 1
  • BrickStepper.STEP_MODE_HALF_STEP = 2
  • BrickStepper.STEP_MODE_QUARTER_STEP = 4
  • BrickStepper.STEP_MODE_EIGHTH_STEP = 8
BrickStepper.GetStackInputVoltage() → voltage
Output:
  • voltage -- Int32

Returns the stack input voltage in mV. The stack input voltage is the voltage that is supplied via the stack, i.e. it is given by a Step-Down or Step-Up Power Supply.

BrickStepper.GetExternalInputVoltage() → voltage
Output:
  • voltage -- Int32

Returns the external input voltage in mV. The external input voltage is given via the black power input connector on the Stepper Brick.

If there is an external input voltage and a stack input voltage, the motor will be driven by the external input voltage. If there is only a stack voltage present, the motor will be driven by this voltage.

Warning

This means, if you have a high stack voltage and a low external voltage, the motor will be driven with the low external voltage. If you then remove the external connection, it will immediately be driven by the high stack voltage

BrickStepper.GetCurrentConsumption() → current
Output:
  • current -- Int32

Returns the current consumption of the motor in mA.

BrickStepper.SetDecay(decay)
Input:
  • decay -- Int32

Sets the decay mode of the stepper motor. The possible value range is between 0 and 65535. A value of 0 sets the fast decay mode, a value of 65535 sets the slow decay mode and a value in between sets the mixed decay mode.

Changing the decay mode is only possible if synchronous rectification is enabled (see SetSyncRect()).

For a good explanation of the different decay modes see this blog post by Avayan.

A good decay mode is unfortunately different for every motor. The best way to work out a good decay mode for your stepper motor, if you can't measure the current with an oscilloscope, is to listen to the sound of the motor. If the value is too low, you often hear a high pitched sound and if it is too high you can often hear a humming sound.

Generally, fast decay mode (small value) will be noisier but also allow higher motor speeds.

The default value is 10000.

Note

There is unfortunately no formula to calculate a perfect decay mode for a given stepper motor. If you have problems with loud noises or the maximum motor speed is too slow, you should try to tinker with the decay value

BrickStepper.GetDecay() → decay
Output:
  • decay -- Int32

Returns the decay mode as set by SetDecay().

BrickStepper.SetSyncRect(syncRect)
Input:
  • syncRect -- Boolean

Turns synchronous rectification on or off (true or false).

With synchronous rectification on, the decay can be changed (see SetDecay()). Without synchronous rectification fast decay is used.

For an explanation of synchronous rectification see here.

Warning

If you want to use high speeds (> 10000 steps/s) for a large stepper motor with a large inductivity we strongly suggest that you disable synchronous rectification. Otherwise the Brick may not be able to cope with the load and overheat.

The default value is false.

BrickStepper.IsSyncRect() → syncRect
Output:
  • syncRect -- Boolean

Returns true if synchronous rectification is enabled, false otherwise.

BrickStepper.SetTimeBase(timeBase)
Input:
  • timeBase -- Int64

Sets the time base of the velocity and the acceleration of the stepper brick (in seconds).

For example, if you want to make one step every 1.5 seconds, you can set the time base to 15 and the velocity to 10. Now the velocity is 10steps/15s = 1steps/1.5s.

The default value is 1.

BrickStepper.GetTimeBase() → timeBase
Output:
  • timeBase -- Int64

Returns the time base as set by SetTimeBase().

BrickStepper.GetAllData() → currentVelocity, currentPosition, remainingSteps, stackVoltage, externalVoltage, currentConsumption
Output:
  • currentVelocity -- Int32
  • currentPosition -- Int32
  • remainingSteps -- Int32
  • stackVoltage -- Int32
  • externalVoltage -- Int32
  • currentConsumption -- Int32

Returns the following parameters: The current velocity, the current position, the remaining steps, the stack voltage, the external voltage and the current consumption of the stepper motor.

There is also a callback for this function, see AllDataCallback callback.

BrickStepper.GetAPIVersion() → apiVersion
Output:
  • apiVersion -- Byte[3]

Returns the version of the API definition (major, minor, revision) implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.

BrickStepper.GetResponseExpected(functionId) → responseExpected
Input:
  • functionId -- Byte
Output:
  • responseExpected -- Boolean

Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.

For getter functions this is enabled by default and cannot be disabled, because those functions will always send a response. For callback configuration functions it is enabled by default too, but can be disabled by SetResponseExpected(). For setter functions it is disabled by default and can be enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

See SetResponseExpected() for the list of function ID constants available for this function.

BrickStepper.SetResponseExpected(functionId, responseExpected)
Input:
  • functionId -- Byte
  • responseExpected -- Boolean

Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

The following function ID constants are available for this function:

  • BrickStepper.FUNCTION_SET_MAX_VELOCITY = 1
  • BrickStepper.FUNCTION_SET_SPEED_RAMPING = 4
  • BrickStepper.FUNCTION_FULL_BRAKE = 6
  • BrickStepper.FUNCTION_SET_CURRENT_POSITION = 7
  • BrickStepper.FUNCTION_SET_TARGET_POSITION = 9
  • BrickStepper.FUNCTION_SET_STEPS = 11
  • BrickStepper.FUNCTION_SET_STEP_MODE = 14
  • BrickStepper.FUNCTION_DRIVE_FORWARD = 16
  • BrickStepper.FUNCTION_DRIVE_BACKWARD = 17
  • BrickStepper.FUNCTION_STOP = 18
  • BrickStepper.FUNCTION_SET_MOTOR_CURRENT = 22
  • BrickStepper.FUNCTION_ENABLE = 24
  • BrickStepper.FUNCTION_DISABLE = 25
  • BrickStepper.FUNCTION_SET_DECAY = 27
  • BrickStepper.FUNCTION_SET_MINIMUM_VOLTAGE = 29
  • BrickStepper.FUNCTION_SET_SYNC_RECT = 33
  • BrickStepper.FUNCTION_SET_TIME_BASE = 35
  • BrickStepper.FUNCTION_SET_ALL_DATA_PERIOD = 38
  • BrickStepper.FUNCTION_SET_SPITFP_BAUDRATE_CONFIG = 231
  • BrickStepper.FUNCTION_SET_SPITFP_BAUDRATE = 234
  • BrickStepper.FUNCTION_ENABLE_STATUS_LED = 238
  • BrickStepper.FUNCTION_DISABLE_STATUS_LED = 239
  • BrickStepper.FUNCTION_RESET = 243
BrickStepper.SetResponseExpectedAll(responseExpected)
Input:
  • responseExpected -- Boolean

Changes the response expected flag for all setter and callback configuration functions of this device at once.

BrickStepper.SetSPITFPBaudrateConfig(enableDynamicBaudrate, minimumDynamicBaudrate)
Input:
  • enableDynamicBaudrate -- Boolean
  • minimumDynamicBaudrate -- Int64

The SPITF protocol can be used with a dynamic baudrate. If the dynamic baudrate is enabled, the Brick will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.

The baudrate will be increased exponentially if lots of data is send/received and decreased linearly if little data is send/received.

This lowers the baudrate in applications where little data is transferred (e.g. a weather station) and increases the robustness. If there is lots of data to transfer (e.g. Thermal Imaging Bricklet) it automatically increases the baudrate as needed.

In cases where some data has to transferred as fast as possible every few seconds (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn the dynamic baudrate off to get the highest possible performance.

The maximum value of the baudrate can be set per port with the function SetSPITFPBaudrate(). If the dynamic baudrate is disabled, the baudrate as set by SetSPITFPBaudrate() will be used statically.

The minimum dynamic baudrate has a value range of 400000 to 2000000 baud.

By default dynamic baudrate is enabled and the minimum dynamic baudrate is 400000.

New in version 2.3.6 (Firmware).

BrickStepper.GetSPITFPBaudrateConfig() → enableDynamicBaudrate, minimumDynamicBaudrate
Output:
  • enableDynamicBaudrate -- Boolean
  • minimumDynamicBaudrate -- Int64

Returns the baudrate config, see SetSPITFPBaudrateConfig().

New in version 2.3.6 (Firmware).

BrickStepper.GetSendTimeoutCount(communicationMethod) → timeoutCount
Input:
  • communicationMethod -- Byte
Output:
  • timeoutCount -- Int64

Returns the timeout count for the different communication methods.

The methods 0-2 are available for all Bricks, 3-7 only for Master Bricks.

This function is mostly used for debugging during development, in normal operation the counters should nearly always stay at 0.

The following constants are available for this function:

  • BrickStepper.COMMUNICATION_METHOD_NONE = 0
  • BrickStepper.COMMUNICATION_METHOD_USB = 1
  • BrickStepper.COMMUNICATION_METHOD_SPI_STACK = 2
  • BrickStepper.COMMUNICATION_METHOD_CHIBI = 3
  • BrickStepper.COMMUNICATION_METHOD_RS485 = 4
  • BrickStepper.COMMUNICATION_METHOD_WIFI = 5
  • BrickStepper.COMMUNICATION_METHOD_ETHERNET = 6
  • BrickStepper.COMMUNICATION_METHOD_WIFI_V2 = 7

New in version 2.3.4 (Firmware).

BrickStepper.SetSPITFPBaudrate(brickletPort, baudrate)
Input:
  • brickletPort -- Char
  • baudrate -- Int64

Sets the baudrate for a specific Bricklet port ('a' - 'd'). The baudrate can be in the range 400000 to 2000000.

If you want to increase the throughput of Bricklets you can increase the baudrate. If you get a high error count because of high interference (see GetSPITFPErrorCount()) you can decrease the baudrate.

If the dynamic baudrate feature is enabled, the baudrate set by this function corresponds to the maximum baudrate (see SetSPITFPBaudrateConfig()).

Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in you applications we recommend to not change the baudrate.

The default baudrate for all ports is 1400000.

New in version 2.3.3 (Firmware).

BrickStepper.GetSPITFPBaudrate(brickletPort) → baudrate
Input:
  • brickletPort -- Char
Output:
  • baudrate -- Int64

Returns the baudrate for a given Bricklet port, see SetSPITFPBaudrate().

New in version 2.3.3 (Firmware).

BrickStepper.GetSPITFPErrorCount(brickletPort) → errorCountACKChecksum, errorCountMessageChecksum, errorCountFrame, errorCountOverflow
Input:
  • brickletPort -- Char
Output:
  • errorCountACKChecksum -- Int64
  • errorCountMessageChecksum -- Int64
  • errorCountFrame -- Int64
  • errorCountOverflow -- Int64

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

The errors counts are for errors that occur on the Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.

New in version 2.3.3 (Firmware).

BrickStepper.EnableStatusLED()

Enables the status LED.

The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.

The default state is enabled.

New in version 2.3.1 (Firmware).

BrickStepper.DisableStatusLED()

Disables the status LED.

The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.

The default state is enabled.

New in version 2.3.1 (Firmware).

BrickStepper.IsStatusLEDEnabled() → enabled
Output:
  • enabled -- Boolean

Returns true if the status LED is enabled, false otherwise.

New in version 2.3.1 (Firmware).

BrickStepper.GetProtocol1BrickletName(port) → protocolVersion, firmwareVersion, name
Input:
  • port -- Char
Output:
  • protocolVersion -- Byte
  • firmwareVersion -- Byte[3]
  • name -- String

Returns the firmware and protocol version and the name of the Bricklet for a given port.

This functions sole purpose is to allow automatic flashing of v1.x.y Bricklet plugins.

BrickStepper.GetChipTemperature() → temperature
Output:
  • temperature -- Int16

Returns the temperature in °C/10 as measured inside the microcontroller. The value returned is not the ambient temperature!

The temperature is only proportional to the real temperature and it has an accuracy of +-15%. Practically it is only useful as an indicator for temperature changes.

BrickStepper.Reset()

Calling this function will reset the Brick. Calling this function on a Brick inside of a stack will reset the whole stack.

After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!

BrickStepper.GetIdentity() → uid, connectedUid, position, hardwareVersion, firmwareVersion, deviceIdentifier
Output:
  • uid -- String
  • connectedUid -- String
  • position -- Char
  • hardwareVersion -- Byte[3]
  • firmwareVersion -- Byte[3]
  • deviceIdentifier -- Int32

Returns the UID, the UID where the Brick is connected to, the position, the hardware and firmware version as well as the device identifier.

The position can be '0'-'8' (stack position).

The device identifier numbers can be found here. There is also a constant for the device identifier of this Brick.

Callback Configuration Functions

BrickStepper.SetMinimumVoltage(voltage)
Input:
  • voltage -- Int32

Sets the minimum voltage in mV, below which the UnderVoltageCallback callback is triggered. The minimum possible value that works with the Stepper Brick is 8V. You can use this function to detect the discharge of a battery that is used to drive the stepper motor. If you have a fixed power supply, you likely do not need this functionality.

The default value is 8V.

BrickStepper.GetMinimumVoltage() → voltage
Output:
  • voltage -- Int32

Returns the minimum voltage as set by SetMinimumVoltage().

BrickStepper.SetAllDataPeriod(period)
Input:
  • period -- Int64

Sets the period in ms with which the AllDataCallback callback is triggered periodically. A value of 0 turns the callback off.

BrickStepper.GetAllDataPeriod() → period
Output:
  • period -- Int64

Returns the period as set by SetAllDataPeriod().

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a function to a callback property of the device object. The available callback property and their type of parameters are described below.

Note

Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.

event BrickStepper.UnderVoltageCallback(sender, voltage)
Input:
  • sender -- .NET Refnum (BrickStepper)
  • voltage -- Int32

This callback is triggered when the input voltage drops below the value set by SetMinimumVoltage(). The parameter is the current voltage given in mV.

event BrickStepper.PositionReachedCallback(sender, position)
Input:
  • sender -- .NET Refnum (BrickStepper)
  • position -- Int32

This callback is triggered when a position set by SetSteps() or SetTargetPosition() is reached.

Note

Since we can't get any feedback from the stepper motor, this only works if the acceleration (see SetSpeedRamping()) is set smaller or equal to the maximum acceleration of the motor. Otherwise the motor will lag behind the control value and the callback will be triggered too early.

event BrickStepper.AllDataCallback(sender, currentVelocity, currentPosition, remainingSteps, stackVoltage, externalVoltage, currentConsumption)
Input:
  • sender -- .NET Refnum (BrickStepper)
  • currentVelocity -- Int32
  • currentPosition -- Int32
  • remainingSteps -- Int32
  • stackVoltage -- Int32
  • externalVoltage -- Int32
  • currentConsumption -- Int32

This callback is triggered periodically with the period that is set by SetAllDataPeriod(). The parameters are: the current velocity, the current position, the remaining steps, the stack voltage, the external voltage and the current consumption of the stepper motor.

event BrickStepper.NewStateCallback(sender, stateNew, statePrevious)
Input:
  • sender -- .NET Refnum (BrickStepper)
  • stateNew -- Byte
  • statePrevious -- Byte

This callback is triggered whenever the Stepper Brick enters a new state. It returns the new state as well as the previous state.

The following constants are available for this function:

  • BrickStepper.STATE_STOP = 1
  • BrickStepper.STATE_ACCELERATION = 2
  • BrickStepper.STATE_RUN = 3
  • BrickStepper.STATE_DEACCELERATION = 4
  • BrickStepper.STATE_DIRECTION_CHANGE_TO_FORWARD = 5
  • BrickStepper.STATE_DIRECTION_CHANGE_TO_BACKWARD = 6

Constants

BrickStepper.DEVICE_IDENTIFIER

This constant is used to identify a Stepper Brick.

The GetIdentity() function and the EnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

BrickStepper.DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Stepper Brick.