MQTT - Stepper Brick

This is the description of the MQTT 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 MQTT API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Configuration

Download (example-configuration.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
# Change XXYYZZ to the UID of your Stepper Brick

setup:
    publish '{"current": 800}' to tinkerforge/request/stepper_brick/XXYYZZ/set_motor_current  # 800mA
    
    publish '{"mode": "eighth_step"}' to tinkerforge/request/stepper_brick/XXYYZZ/set_step_mode  # 1/8 step mode
    
    publish '{"velocity": 2000}' to tinkerforge/request/stepper_brick/XXYYZZ/set_max_velocity  # Velocity 2000 steps/s
    
    # Slow acceleration (500 steps/s^2),
    # Fast deacceleration (5000 steps/s^2)
    publish '{"acceleration": 500, "deacceleration": 5000}' to tinkerforge/request/stepper_brick/XXYYZZ/set_speed_ramping 
    
    
    
    publish '' to tinkerforge/request/stepper_brick/XXYYZZ/enable  # Enable motor power
    
    publish '{"steps": 60000}' to tinkerforge/request/stepper_brick/XXYYZZ/set_steps  # Drive 60000 steps forward

cleanup:
    # If you are done, run this to clean up
    publish '' to tinkerforge/request/stepper_brick/XXYYZZ/disable 

Callback

Download (example-callback.txt)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
# Change XXYYZZ to the UID of your Stepper Brick

setup:
    # Use position reached callback to program random movement
    subscribe to tinkerforge/callback/stepper_brick/XXYYZZ/position_reached
        if a message arives
            # message contains the current position as int
            generate random numbers r,
                    steps [1000;5000],
                    vel [200; 2000],
                    acc [100; 1000]
                and dec [100; 1000]
                
            if r is even
                # Driving forward        
            else
                # Driving backward
                set steps to -steps
            endif
            publish '{"acceleration": acc, "deceleration": dec}' to tinkerforge/request/stepper_brick/XXYYZZ/set_speed_ramping
            publish '{"velocity": vel}' to tinkerforge/request/stepper_brick/XXYYZZ/set_max_velocity
            publish '{"steps": steps}' to tinkerforge/request/stepper_brick/XXYYZZ/set_steps
        endif
    endsubscribe
    
    publish '{"register": true}' to tinkerforge/register/stepper_brick/XXYYZZ/position_reached # Register position_reached callback

    publish '' to tinkerforge/request/stepper_brick/XXYYZZ/enable  # Enable motor power
    publish '{"steps": 1}' to tinkerforge/request/stepper_brick/XXYYZZ/set_steps  # Drive one step forward to get things going
    
cleanup:
    # If you are done, run this to clean up
    publish '' to tinkerforge/request/stepper_brick/XXYYZZ/disable 

API

All published payload to an from the MQTT bindings is in the JSON format.

If an error occures, the bindings publish a JSON object containing the error message as attribute "_ERROR". It is published on the corresponding response topic: .../response/... for .../request/... and .../callback/... for .../register/....

Basic Functions

request/stepper_brick/<UID>/set_max_velocity
Request payload:
 
  • velocity -- int

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 request/stepper_brick/<UID>/set_target_position, request/stepper_brick/<UID>/set_steps, request/stepper_brick/<UID>/drive_forward or request/stepper_brick/<UID>/drive_backward.

request/stepper_brick/<UID>/get_max_velocity
Response payload:
 
  • velocity -- int

Returns the velocity as set by request/stepper_brick/<UID>/set_max_velocity.

request/stepper_brick/<UID>/get_current_velocity
Response payload:
 
  • velocity -- int

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

request/stepper_brick/<UID>/set_speed_ramping
Request payload:
 
  • acceleration -- int
  • deacceleration -- int

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

request/stepper_brick/<UID>/get_speed_ramping
Response payload:
 
  • acceleration -- int
  • deacceleration -- int

Returns the acceleration and deacceleration as set by request/stepper_brick/<UID>/set_speed_ramping.

request/stepper_brick/<UID>/full_brake

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 request/stepper_brick/<UID>/stop if you just want to stop the motor.

request/stepper_brick/<UID>/set_steps
Request payload:
 
  • steps -- int

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 request/stepper_brick/<UID>/set_max_velocity and request/stepper_brick/<UID>/set_speed_ramping will be used.

request/stepper_brick/<UID>/get_steps
Response payload:
 
  • steps -- int

Returns the last steps as set by request/stepper_brick/<UID>/set_steps.

request/stepper_brick/<UID>/get_remaining_steps
Response payload:
 
  • steps -- int

Returns the remaining steps of the last call of request/stepper_brick/<UID>/set_steps. For example, if request/stepper_brick/<UID>/set_steps is called with 2000 and request/stepper_brick/<UID>/get_remaining_steps is called after the motor has run for 500 steps, it will return 1500.

request/stepper_brick/<UID>/drive_forward

Drives the stepper motor forward until request/stepper_brick/<UID>/drive_backward or request/stepper_brick/<UID>/stop is called. The velocity, acceleration and deacceleration as set by request/stepper_brick/<UID>/set_max_velocity and request/stepper_brick/<UID>/set_speed_ramping will be used.

request/stepper_brick/<UID>/drive_backward

Drives the stepper motor backward until request/stepper_brick/<UID>/drive_forward or request/stepper_brick/<UID>/stop is triggered. The velocity, acceleration and deacceleration as set by request/stepper_brick/<UID>/set_max_velocity and request/stepper_brick/<UID>/set_speed_ramping will be used.

request/stepper_brick/<UID>/stop

Stops the stepper motor with the deacceleration as set by request/stepper_brick/<UID>/set_speed_ramping.

request/stepper_brick/<UID>/set_motor_current
Request payload:
 
  • current -- int

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.

request/stepper_brick/<UID>/get_motor_current
Response payload:
 
  • current -- int

Returns the current as set by request/stepper_brick/<UID>/set_motor_current.

request/stepper_brick/<UID>/enable

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

request/stepper_brick/<UID>/disable

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

request/stepper_brick/<UID>/is_enabled
Response payload:
 
  • enabled -- bool

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

Advanced Functions

request/stepper_brick/<UID>/set_current_position
Request payload:
 
  • position -- int

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).

request/stepper_brick/<UID>/get_current_position
Response payload:
 
  • position -- int

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 (request/stepper_brick/<UID>/set_target_position, request/stepper_brick/<UID>/set_steps, request/stepper_brick/<UID>/drive_forward or request/stepper_brick/<UID>/drive_backward). It also is possible to reset the steps to 0 or set them to any other desired value with request/stepper_brick/<UID>/set_current_position.

request/stepper_brick/<UID>/set_target_position
Request payload:
 
  • position -- int

Sets the target position of the stepper motor in steps. For example, if the current position of the motor is 500 and request/stepper_brick/<UID>/set_target_position is called with 1000, the stepper motor will drive 500 steps forward. It will use the velocity, acceleration and deacceleration as set by request/stepper_brick/<UID>/set_max_velocity and request/stepper_brick/<UID>/set_speed_ramping.

A call of request/stepper_brick/<UID>/set_target_position with the parameter x is equivalent to a call of request/stepper_brick/<UID>/set_steps with the parameter (x - request/stepper_brick/<UID>/get_current_position).

request/stepper_brick/<UID>/get_target_position
Response payload:
 
  • position -- int

Returns the last target position as set by request/stepper_brick/<UID>/set_target_position.

request/stepper_brick/<UID>/set_step_mode
Request payload:
 
  • mode -- int (has symbols)

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 symbols are available for this function:

for mode:

  • "FullStep" = 1
  • "HalfStep" = 2
  • "QuarterStep" = 4
  • "EighthStep" = 8
request/stepper_brick/<UID>/get_step_mode
Response payload:
 
  • mode -- int (has symbols)

Returns the step mode as set by request/stepper_brick/<UID>/set_step_mode.

The following symbols are available for this function:

for mode:

  • "FullStep" = 1
  • "HalfStep" = 2
  • "QuarterStep" = 4
  • "EighthStep" = 8
request/stepper_brick/<UID>/get_stack_input_voltage
Response payload:
 
  • voltage -- int

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.

request/stepper_brick/<UID>/get_external_input_voltage
Response payload:
 
  • voltage -- int

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

request/stepper_brick/<UID>/get_current_consumption
Response payload:
 
  • current -- int

Returns the current consumption of the motor in mA.

request/stepper_brick/<UID>/set_decay
Request payload:
 
  • decay -- int

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 request/stepper_brick/<UID>/set_sync_rect).

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

request/stepper_brick/<UID>/get_decay
Response payload:
 
  • decay -- int

Returns the decay mode as set by request/stepper_brick/<UID>/set_decay.

request/stepper_brick/<UID>/set_sync_rect
Request payload:
 
  • sync_rect -- bool

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

With synchronous rectification on, the decay can be changed (see request/stepper_brick/<UID>/set_decay). 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.

request/stepper_brick/<UID>/is_sync_rect
Response payload:
 
  • sync_rect -- bool

Returns true if synchronous rectification is enabled, false otherwise.

request/stepper_brick/<UID>/set_time_base
Request payload:
 
  • time_base -- int

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.

request/stepper_brick/<UID>/get_time_base
Response payload:
 
  • time_base -- int

Returns the time base as set by request/stepper_brick/<UID>/set_time_base.

request/stepper_brick/<UID>/get_all_data
Response payload:
 
  • current_velocity -- int
  • current_position -- int
  • remaining_steps -- int
  • stack_voltage -- int
  • external_voltage -- int
  • current_consumption -- int

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 register/stepper_brick/<UID>/all_data callback.

request/stepper_brick/<UID>/set_spitfp_baudrate_config
Request payload:
 
  • enable_dynamic_baudrate -- bool
  • minimum_dynamic_baudrate -- int

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 request/stepper_brick/<UID>/set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate as set by request/stepper_brick/<UID>/set_spitfp_baudrate 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).

request/stepper_brick/<UID>/get_spitfp_baudrate_config
Response payload:
 
  • enable_dynamic_baudrate -- bool
  • minimum_dynamic_baudrate -- int

Returns the baudrate config, see request/stepper_brick/<UID>/set_spitfp_baudrate_config.

New in version 2.3.6 (Firmware).

request/stepper_brick/<UID>/get_send_timeout_count
Request payload:
 
  • communication_method -- int (has symbols)
Response payload:
 
  • timeout_count -- int

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 symbols are available for this function:

for communication_method:

  • "None" = 0
  • "USB" = 1
  • "SPIStack" = 2
  • "Chibi" = 3
  • "RS485" = 4
  • "WIFI" = 5
  • "Ethernet" = 6
  • "WIFIV2" = 7

New in version 2.3.4 (Firmware).

request/stepper_brick/<UID>/set_spitfp_baudrate
Request payload:
 
  • bricklet_port -- string
  • baudrate -- int

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 request/stepper_brick/<UID>/get_spitfp_error_count) you can decrease the baudrate.

If the dynamic baudrate feature is enabled, the baudrate set by this function corresponds to the maximum baudrate (see request/stepper_brick/<UID>/set_spitfp_baudrate_config).

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).

request/stepper_brick/<UID>/get_spitfp_baudrate
Request payload:
 
  • bricklet_port -- string
Response payload:
 
  • baudrate -- int

Returns the baudrate for a given Bricklet port, see request/stepper_brick/<UID>/set_spitfp_baudrate.

New in version 2.3.3 (Firmware).

request/stepper_brick/<UID>/get_spitfp_error_count
Request payload:
 
  • bricklet_port -- string
Response payload:
 
  • error_count_ack_checksum -- int
  • error_count_message_checksum -- int
  • error_count_frame -- int
  • error_count_overflow -- int

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).

request/stepper_brick/<UID>/enable_status_led

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).

request/stepper_brick/<UID>/disable_status_led

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).

request/stepper_brick/<UID>/is_status_led_enabled
Response payload:
 
  • enabled -- bool

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

New in version 2.3.1 (Firmware).

request/stepper_brick/<UID>/get_protocol1_bricklet_name
Request payload:
 
  • port -- string
Response payload:
 
  • protocol_version -- int
  • firmware_version -- [int,int,int]
  • 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.

request/stepper_brick/<UID>/get_chip_temperature
Response payload:
 
  • temperature -- int

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.

request/stepper_brick/<UID>/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!

request/stepper_brick/<UID>/get_identity
Response payload:
 
  • uid -- string
  • connected_uid -- string
  • position -- string
  • hardware_version -- [int,int,int]
  • firmware_version -- [int,int,int]
  • device_identifier -- int (has symbols)
  • _display_name -- string

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. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.

The display name contains the Stepper's name in a human readable form.

Callback Configuration Functions

request/stepper_brick/<UID>/set_minimum_voltage
Request payload:
 
  • voltage -- int

Sets the minimum voltage in mV, below which the register/stepper_brick/<UID>/under_voltage 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.

request/stepper_brick/<UID>/get_minimum_voltage
Response payload:
 
  • voltage -- int

Returns the minimum voltage as set by request/stepper_brick/<UID>/set_minimum_voltage.

request/stepper_brick/<UID>/set_all_data_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/stepper_brick/<UID>/all_data callback is triggered periodically. A value of 0 turns the callback off.

request/stepper_brick/<UID>/get_all_data_period
Response payload:
 
  • period -- int

Returns the period as set by request/stepper_brick/<UID>/set_all_data_period.

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding .../register/... topic and an optional suffix. This suffix can be used to deregister the callback later.

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.

register/stepper_brick/<UID>/under_voltage
Request payload:
 
  • register -- bool
Response payload:
 
  • voltage -- int

A callback can be registered for this event by publishing to the .../register/stepper_brick/<UID>/under_voltage[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/stepper_brick/<UID>/under_voltage[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when the input voltage drops below the value set by request/stepper_brick/<UID>/set_minimum_voltage. The callback payload is the current voltage given in mV.

register/stepper_brick/<UID>/position_reached
Request payload:
 
  • register -- bool
Response payload:
 
  • position -- int

A callback can be registered for this event by publishing to the .../register/stepper_brick/<UID>/position_reached[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/stepper_brick/<UID>/position_reached[/<SUFFIX>] topic for each registered suffix.

This callback is triggered when a position set by request/stepper_brick/<UID>/set_steps or request/stepper_brick/<UID>/set_target_position is reached.

Note

Since we can't get any feedback from the stepper motor, this only works if the acceleration (see request/stepper_brick/<UID>/set_speed_ramping) 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.

register/stepper_brick/<UID>/all_data
Request payload:
 
  • register -- bool
Response payload:
 
  • current_velocity -- int
  • current_position -- int
  • remaining_steps -- int
  • stack_voltage -- int
  • external_voltage -- int
  • current_consumption -- int

A callback can be registered for this event by publishing to the .../register/stepper_brick/<UID>/all_data[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/stepper_brick/<UID>/all_data[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/stepper_brick/<UID>/set_all_data_period. The callback payload members are: the current velocity, the current position, the remaining steps, the stack voltage, the external voltage and the current consumption of the stepper motor.

register/stepper_brick/<UID>/new_state
Request payload:
 
  • register -- bool
Response payload:
 
  • state_new -- int (has symbols)
  • state_previous -- int (has symbols)

A callback can be registered for this event by publishing to the .../register/stepper_brick/<UID>/new_state[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/stepper_brick/<UID>/new_state[/<SUFFIX>] topic for each registered suffix.

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 symbols are available for this function:

for state_new:

  • "Stop" = 1
  • "Acceleration" = 2
  • "Run" = 3
  • "Deacceleration" = 4
  • "DirectionChangeToForward" = 5
  • "DirectionChangeToBackward" = 6