tinkerforge 2.1.17 → 2.1.18

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 617ee249ffa5abe4ff9e12e178bee3ede5fcb248
-  data.tar.gz: b5f84ca2e34947f1dae73738c4349d2eba41162b
+  metadata.gz: bde8e824cb722b6bd2d367cb688fc397bc4009c7
+  data.tar.gz: a297469354481812a0b72f510f85848e13ba1795
 SHA512:
-  metadata.gz: 3bc085806cd7fd14670cea29d29b5fbe2e030cf7b4d5f5739abb13a6ec519b779387c3377b311664fa2e3b8839d720bd652789f9fc7ed0ef850a86947e0a6860
-  data.tar.gz: ad8b5ea516151373147e4b5d3351732ba6cb97ed1f63e4e1cd16cf01f7c742b01144a0c37801d985652fade40fc5cfaee24126373d1e4806230d7138065388a5
+  metadata.gz: 6c33877eb966b1ca81857d2fbd719978b095ec4108af5c7c1cca199326db8f5925afda45664bdc390cb7a0b3d87737e428304a4eb6d05d8225f0e699c7d73a34
+  data.tar.gz: b5cce56fda0fe0d3e2909e19e26a02b3c3aab3b8b1af9301eb9853fca3a64561606a0767fc25dd3742265e2c76b02662a6c76c5640e52d9b82109c0626924c3b

data/lib/tinkerforge/brick_dc.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -332,7 +332,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -343,7 +343,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickDC#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickDC#set_spitfp_baudrate will be used statically.
     # 
@@ -386,7 +386,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickDC#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -410,7 +410,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/brick_imu.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -492,7 +492,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -503,7 +503,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickIMU#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickIMU#set_spitfp_baudrate will be used statically.
     # 
@@ -546,7 +546,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickIMU#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -570,7 +570,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/brick_imu_v2.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -146,6 +146,7 @@ module Tinkerforge
     SENSOR_FUSION_OFF = 0 # :nodoc:
     SENSOR_FUSION_ON = 1 # :nodoc:
     SENSOR_FUSION_ON_WITHOUT_MAGNETOMETER = 2 # :nodoc:
+    SENSOR_FUSION_ON_WITHOUT_FAST_MAGNETOMETER_CALIBRATION = 3 # :nodoc:
     COMMUNICATION_METHOD_NONE = 0 # :nodoc:
     COMMUNICATION_METHOD_USB = 1 # :nodoc:
     COMMUNICATION_METHOD_SPI_STACK = 2 # :nodoc:
@@ -522,6 +523,12 @@ module Tinkerforge
     # absolute with respect to the earth). However, the calculation can't be influenced
     # by spurious magnetic fields.
     # 
+    # Since firmware version 2.0.13 you can also use a fusion mode without fast
+    # magnetometer calibration. This mode is the same as the normal fusion mode,
+    # but the fast magnetometer calibration is turned off. So to find the orientation
+    # the first time will likely take longer, but small magnetic influences might
+    # not affect the automatic calibration as much.
+    # 
     # By default sensor fusion is on.
     # 
     # .. versionadded:: 2.0.5$nbsp;(Firmware)
@@ -540,7 +547,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -551,7 +558,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickIMUV2#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickIMUV2#set_spitfp_baudrate will be used statically.
     # 
@@ -594,7 +601,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickIMUV2#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -618,7 +625,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/brick_master.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -1680,7 +1680,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -1691,7 +1691,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickMaster#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickMaster#set_spitfp_baudrate will be used statically.
     # 
@@ -1734,7 +1734,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickMaster#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -1758,7 +1758,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/brick_red.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #

data/lib/tinkerforge/brick_servo.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -21,7 +21,9 @@ module Tinkerforge
     CALLBACK_UNDER_VOLTAGE = 26
 
     # This callback is triggered when a position set by BrickServo#set_position
-    # is reached. The parameters are the servo and the position that is reached.
+    # is reached. If the new position matches the current position then the
+    # callback is not triggered, because the servo didn't move.
+    # The parameters are the servo and the position that is reached.
     # 
     # You can enable this callback with BrickServo#enable_position_reached_callback.
     # 
@@ -449,7 +451,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -460,7 +462,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickServo#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickServo#set_spitfp_baudrate will be used statically.
     # 
@@ -503,7 +505,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickServo#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -527,7 +529,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/brick_silent_stepper.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -430,16 +430,16 @@ module Tinkerforge
     # Sets the basic configuration parameters for the different modes (Stealth, Coolstep, Classic).
     # 
     # * Standstill Current: This value can be used to lower the current during stand still. This might
-    #   be reasonable to reduce the heating of the motor and the Brick. When the motor is in standstill 
-    #   the configured motor phase current will be driven until the configured 
-    #   Power Down Time is elapsed. After that the phase current will be reduced to the standstill 
+    #   be reasonable to reduce the heating of the motor and the Brick. When the motor is in standstill
+    #   the configured motor phase current will be driven until the configured
+    #   Power Down Time is elapsed. After that the phase current will be reduced to the standstill
     #   current. The elapsed time for this reduction can be configured with the Standstill Delay Time.
     #   The unit is in mA and the maximum allowed value is the configured maximum motor current
     #   (see BrickSilentStepper#set_motor_current).
     # 
-    # * Motor Run Current: The value sets the motor current when the motor is running. 
-    #   Use a value of at least one half of the global maximum motor current for a good 
-    #   microstep performance. The unit is in mA and the maximum allowed value is the current 
+    # * Motor Run Current: The value sets the motor current when the motor is running.
+    #   Use a value of at least one half of the global maximum motor current for a good
+    #   microstep performance. The unit is in mA and the maximum allowed value is the current
     #   motor current. The API maps the entered value to 1/32 ... 32/32 of the maximum
     #   motor current. This value should be used to change the motor current during motor movement,
     #   whereas the global maximum motor current should not be changed while the motor is moving
@@ -676,7 +676,7 @@ module Tinkerforge
     # 
     # * Motor Stalled: Is true if a motor stall was detected.
     # 
-    # * Actual Motor Current: Indicates the actual current control scaling as used in Coolstep mode. 
+    # * Actual Motor Current: Indicates the actual current control scaling as used in Coolstep mode.
     #   The returned value is between 0 and 31. It represents a multiplier of 1/32 to 32/32 of the
     #   ``Motor Run Current`` as set by BrickSilentStepper#set_basic_configuration. Example: If a ``Motor Run Current``
     #   of 1000mA was set and the returned value is 15, the ``Actual Motor Current`` is 16/32*1000mA = 500mA.
@@ -759,7 +759,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -770,7 +770,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickSilentStepper#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickSilentStepper#set_spitfp_baudrate will be used statically.
     # 
@@ -811,7 +811,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickSilentStepper#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -831,7 +831,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/brick_stepper.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #
@@ -502,7 +502,7 @@ module Tinkerforge
     # 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 exponetially if lots of data is send/receieved and
+    # 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.
@@ -513,7 +513,7 @@ module Tinkerforge
     # (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 
+    # The maximum value of the baudrate can be set per port with the function
     # BrickStepper#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
     # as set by BrickStepper#set_spitfp_baudrate will be used statically.
     # 
@@ -556,7 +556,7 @@ module Tinkerforge
     # If the dynamic baudrate feature is enabled, the baudrate set by this
     # function corresponds to the maximum baudrate (see BrickStepper#set_spitfp_baudrate_config).
     # 
-    # Regulatory testing is done with the default baudrate. If CE compatability
+    # 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.
     # 
@@ -580,7 +580,7 @@ module Tinkerforge
     # 
     # * ACK checksum errors,
     # * message checksum errors,
-    # * frameing errors and
+    # * framing errors and
     # * overflow errors.
     # 
     # The errors counts are for errors that occur on the Brick side. All

data/lib/tinkerforge/bricklet_accelerometer.rb

@@ -1,8 +1,8 @@
 # -*- ruby encoding: utf-8 -*-
 #############################################################
-# This file was automatically generated on 2018-06-08.      #
+# This file was automatically generated on 2018-09-28.      #
 #                                                           #
-# Ruby Bindings Version 2.1.17                              #
+# Ruby Bindings Version 2.1.18                              #
 #                                                           #
 # If you have a bugfix for this file and want to commit it, #
 # please fix the bug in the generator. You can find a link  #