tinkerforge 2.1.17 → 2.1.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/tinkerforge/brick_dc.rb +6 -6
- data/lib/tinkerforge/brick_imu.rb +6 -6
- data/lib/tinkerforge/brick_imu_v2.rb +13 -6
- data/lib/tinkerforge/brick_master.rb +6 -6
- data/lib/tinkerforge/brick_red.rb +2 -2
- data/lib/tinkerforge/brick_servo.rb +9 -7
- data/lib/tinkerforge/brick_silent_stepper.rb +13 -13
- data/lib/tinkerforge/brick_stepper.rb +6 -6
- data/lib/tinkerforge/bricklet_accelerometer.rb +2 -2
- data/lib/tinkerforge/bricklet_air_quality.rb +514 -0
- data/lib/tinkerforge/bricklet_ambient_light.rb +2 -2
- data/lib/tinkerforge/bricklet_ambient_light_v2.rb +2 -2
- data/lib/tinkerforge/bricklet_analog_in.rb +2 -2
- data/lib/tinkerforge/bricklet_analog_in_v2.rb +2 -2
- data/lib/tinkerforge/bricklet_analog_in_v3.rb +5 -5
- data/lib/tinkerforge/bricklet_analog_out.rb +2 -2
- data/lib/tinkerforge/bricklet_analog_out_v2.rb +2 -2
- data/lib/tinkerforge/bricklet_analog_out_v3.rb +210 -0
- data/lib/tinkerforge/bricklet_barometer.rb +2 -2
- data/lib/tinkerforge/bricklet_barometer_v2.rb +497 -0
- data/lib/tinkerforge/bricklet_can.rb +2 -2
- data/lib/tinkerforge/bricklet_can_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_co2.rb +2 -2
- data/lib/tinkerforge/bricklet_color.rb +2 -2
- data/lib/tinkerforge/bricklet_current12.rb +2 -2
- data/lib/tinkerforge/bricklet_current25.rb +2 -2
- data/lib/tinkerforge/bricklet_distance_ir.rb +2 -2
- data/lib/tinkerforge/bricklet_distance_ir_v2.rb +398 -0
- data/lib/tinkerforge/bricklet_distance_us.rb +2 -2
- data/lib/tinkerforge/bricklet_dmx.rb +7 -5
- data/lib/tinkerforge/bricklet_dual_button.rb +2 -2
- data/lib/tinkerforge/bricklet_dual_button_v2.rb +283 -0
- data/lib/tinkerforge/bricklet_dual_relay.rb +2 -2
- data/lib/tinkerforge/bricklet_dust_detector.rb +2 -2
- data/lib/tinkerforge/bricklet_gps.rb +2 -2
- data/lib/tinkerforge/bricklet_gps_v2.rb +6 -6
- data/lib/tinkerforge/bricklet_hall_effect.rb +2 -2
- data/lib/tinkerforge/bricklet_humidity.rb +2 -2
- data/lib/tinkerforge/bricklet_humidity_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_industrial_analog_out.rb +2 -2
- data/lib/tinkerforge/bricklet_industrial_analog_out_v2.rb +336 -0
- data/lib/tinkerforge/bricklet_industrial_counter.rb +12 -12
- data/lib/tinkerforge/bricklet_industrial_digital_in_4.rb +2 -2
- data/lib/tinkerforge/bricklet_industrial_digital_in_4_v2.rb +7 -7
- data/lib/tinkerforge/bricklet_industrial_digital_out_4.rb +2 -2
- data/lib/tinkerforge/bricklet_industrial_digital_out_4_v2.rb +302 -0
- data/lib/tinkerforge/bricklet_industrial_dual_0_20ma.rb +2 -2
- data/lib/tinkerforge/bricklet_industrial_dual_0_20ma_v2.rb +382 -0
- data/lib/tinkerforge/bricklet_industrial_dual_analog_in.rb +2 -2
- data/lib/tinkerforge/bricklet_industrial_dual_analog_in_v2.rb +374 -0
- data/lib/tinkerforge/bricklet_industrial_dual_relay.rb +5 -5
- data/lib/tinkerforge/bricklet_industrial_quad_relay.rb +2 -2
- data/lib/tinkerforge/bricklet_industrial_quad_relay_v2.rb +11 -11
- data/lib/tinkerforge/bricklet_io16.rb +2 -2
- data/lib/tinkerforge/bricklet_io16_v2.rb +418 -0
- data/lib/tinkerforge/bricklet_io4.rb +2 -2
- data/lib/tinkerforge/bricklet_io4_v2.rb +6 -6
- data/lib/tinkerforge/bricklet_isolator.rb +282 -0
- data/lib/tinkerforge/bricklet_joystick.rb +2 -2
- data/lib/tinkerforge/bricklet_laser_range_finder.rb +2 -2
- data/lib/tinkerforge/bricklet_lcd_128x64.rb +486 -0
- data/lib/tinkerforge/bricklet_lcd_16x2.rb +2 -2
- data/lib/tinkerforge/bricklet_lcd_20x4.rb +2 -2
- data/lib/tinkerforge/bricklet_led_strip.rb +2 -2
- data/lib/tinkerforge/bricklet_led_strip_v2.rb +8 -8
- data/lib/tinkerforge/bricklet_line.rb +2 -2
- data/lib/tinkerforge/bricklet_linear_poti.rb +2 -2
- data/lib/tinkerforge/bricklet_load_cell.rb +2 -2
- data/lib/tinkerforge/bricklet_load_cell_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_moisture.rb +2 -2
- data/lib/tinkerforge/bricklet_motion_detector.rb +2 -2
- data/lib/tinkerforge/bricklet_motion_detector_v2.rb +6 -6
- data/lib/tinkerforge/bricklet_motorized_linear_poti.rb +5 -5
- data/lib/tinkerforge/bricklet_multi_touch.rb +2 -2
- data/lib/tinkerforge/bricklet_nfc.rb +6 -6
- data/lib/tinkerforge/bricklet_nfc_rfid.rb +2 -2
- data/lib/tinkerforge/bricklet_oled_128x64.rb +2 -2
- data/lib/tinkerforge/bricklet_oled_128x64_v2.rb +387 -0
- data/lib/tinkerforge/bricklet_oled_64x48.rb +2 -2
- data/lib/tinkerforge/bricklet_one_wire.rb +305 -0
- data/lib/tinkerforge/bricklet_outdoor_weather.rb +5 -5
- data/lib/tinkerforge/bricklet_particulate_matter.rb +5 -5
- data/lib/tinkerforge/bricklet_piezo_buzzer.rb +2 -2
- data/lib/tinkerforge/bricklet_piezo_speaker.rb +2 -2
- data/lib/tinkerforge/bricklet_ptc.rb +2 -2
- data/lib/tinkerforge/bricklet_ptc_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_real_time_clock.rb +2 -2
- data/lib/tinkerforge/bricklet_real_time_clock_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_remote_switch.rb +2 -2
- data/lib/tinkerforge/bricklet_remote_switch_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_rgb_led.rb +2 -2
- data/lib/tinkerforge/bricklet_rgb_led_button.rb +5 -5
- data/lib/tinkerforge/bricklet_rgb_led_matrix.rb +5 -5
- data/lib/tinkerforge/bricklet_rotary_encoder.rb +2 -2
- data/lib/tinkerforge/bricklet_rotary_encoder_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_rotary_poti.rb +2 -2
- data/lib/tinkerforge/bricklet_rs232.rb +2 -2
- data/lib/tinkerforge/bricklet_rs232_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_rs485.rb +5 -5
- data/lib/tinkerforge/bricklet_segment_display_4x7.rb +2 -2
- data/lib/tinkerforge/bricklet_solid_state_relay.rb +2 -2
- data/lib/tinkerforge/bricklet_solid_state_relay_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_sound_intensity.rb +2 -2
- data/lib/tinkerforge/bricklet_sound_pressure_level.rb +9 -9
- data/lib/tinkerforge/bricklet_temperature.rb +2 -2
- data/lib/tinkerforge/bricklet_temperature_ir.rb +2 -2
- data/lib/tinkerforge/bricklet_temperature_ir_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_temperature_v2.rb +278 -0
- data/lib/tinkerforge/bricklet_thermal_imaging.rb +5 -5
- data/lib/tinkerforge/bricklet_thermocouple.rb +2 -2
- data/lib/tinkerforge/bricklet_thermocouple_v2.rb +5 -5
- data/lib/tinkerforge/bricklet_tilt.rb +2 -2
- data/lib/tinkerforge/bricklet_uv_light.rb +6 -5
- data/lib/tinkerforge/bricklet_uv_light_v2.rb +430 -0
- data/lib/tinkerforge/bricklet_voltage.rb +2 -2
- data/lib/tinkerforge/bricklet_voltage_current.rb +2 -2
- data/lib/tinkerforge/bricklet_voltage_current_v2.rb +5 -5
- data/lib/tinkerforge/version.rb +1 -1
- metadata +18 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: bde8e824cb722b6bd2d367cb688fc397bc4009c7
|
|
4
|
+
data.tar.gz: a297469354481812a0b72f510f85848e13ba1795
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6c33877eb966b1ca81857d2fbd719978b095ec4108af5c7c1cca199326db8f5925afda45664bdc390cb7a0b3d87737e428304a4eb6d05d8225f0e699c7d73a34
|
|
7
|
+
data.tar.gz: b5cce56fda0fe0d3e2909e19e26a02b3c3aab3b8b1af9301eb9853fca3a64561606a0767fc25dd3742265e2c76b02662a6c76c5640e52d9b82109c0626924c3b
|
data/lib/tinkerforge/brick_dc.rb
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -332,7 +332,7 @@ module Tinkerforge
|
|
|
332
332
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
333
333
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
334
334
|
#
|
|
335
|
-
# The baudrate will be increased
|
|
335
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
336
336
|
# decreased linearly if little data is send/received.
|
|
337
337
|
#
|
|
338
338
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -343,7 +343,7 @@ module Tinkerforge
|
|
|
343
343
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
344
344
|
# the dynamic baudrate off to get the highest possible performance.
|
|
345
345
|
#
|
|
346
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
346
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
347
347
|
# BrickDC#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
348
348
|
# as set by BrickDC#set_spitfp_baudrate will be used statically.
|
|
349
349
|
#
|
|
@@ -386,7 +386,7 @@ module Tinkerforge
|
|
|
386
386
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
387
387
|
# function corresponds to the maximum baudrate (see BrickDC#set_spitfp_baudrate_config).
|
|
388
388
|
#
|
|
389
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
389
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
390
390
|
# or similar is necessary in you applications we recommend to not change
|
|
391
391
|
# the baudrate.
|
|
392
392
|
#
|
|
@@ -410,7 +410,7 @@ module Tinkerforge
|
|
|
410
410
|
#
|
|
411
411
|
# * ACK checksum errors,
|
|
412
412
|
# * message checksum errors,
|
|
413
|
-
# *
|
|
413
|
+
# * framing errors and
|
|
414
414
|
# * overflow errors.
|
|
415
415
|
#
|
|
416
416
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -492,7 +492,7 @@ module Tinkerforge
|
|
|
492
492
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
493
493
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
494
494
|
#
|
|
495
|
-
# The baudrate will be increased
|
|
495
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
496
496
|
# decreased linearly if little data is send/received.
|
|
497
497
|
#
|
|
498
498
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -503,7 +503,7 @@ module Tinkerforge
|
|
|
503
503
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
504
504
|
# the dynamic baudrate off to get the highest possible performance.
|
|
505
505
|
#
|
|
506
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
506
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
507
507
|
# BrickIMU#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
508
508
|
# as set by BrickIMU#set_spitfp_baudrate will be used statically.
|
|
509
509
|
#
|
|
@@ -546,7 +546,7 @@ module Tinkerforge
|
|
|
546
546
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
547
547
|
# function corresponds to the maximum baudrate (see BrickIMU#set_spitfp_baudrate_config).
|
|
548
548
|
#
|
|
549
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
549
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
550
550
|
# or similar is necessary in you applications we recommend to not change
|
|
551
551
|
# the baudrate.
|
|
552
552
|
#
|
|
@@ -570,7 +570,7 @@ module Tinkerforge
|
|
|
570
570
|
#
|
|
571
571
|
# * ACK checksum errors,
|
|
572
572
|
# * message checksum errors,
|
|
573
|
-
# *
|
|
573
|
+
# * framing errors and
|
|
574
574
|
# * overflow errors.
|
|
575
575
|
#
|
|
576
576
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -146,6 +146,7 @@ module Tinkerforge
|
|
|
146
146
|
SENSOR_FUSION_OFF = 0 # :nodoc:
|
|
147
147
|
SENSOR_FUSION_ON = 1 # :nodoc:
|
|
148
148
|
SENSOR_FUSION_ON_WITHOUT_MAGNETOMETER = 2 # :nodoc:
|
|
149
|
+
SENSOR_FUSION_ON_WITHOUT_FAST_MAGNETOMETER_CALIBRATION = 3 # :nodoc:
|
|
149
150
|
COMMUNICATION_METHOD_NONE = 0 # :nodoc:
|
|
150
151
|
COMMUNICATION_METHOD_USB = 1 # :nodoc:
|
|
151
152
|
COMMUNICATION_METHOD_SPI_STACK = 2 # :nodoc:
|
|
@@ -522,6 +523,12 @@ module Tinkerforge
|
|
|
522
523
|
# absolute with respect to the earth). However, the calculation can't be influenced
|
|
523
524
|
# by spurious magnetic fields.
|
|
524
525
|
#
|
|
526
|
+
# Since firmware version 2.0.13 you can also use a fusion mode without fast
|
|
527
|
+
# magnetometer calibration. This mode is the same as the normal fusion mode,
|
|
528
|
+
# but the fast magnetometer calibration is turned off. So to find the orientation
|
|
529
|
+
# the first time will likely take longer, but small magnetic influences might
|
|
530
|
+
# not affect the automatic calibration as much.
|
|
531
|
+
#
|
|
525
532
|
# By default sensor fusion is on.
|
|
526
533
|
#
|
|
527
534
|
# .. versionadded:: 2.0.5$nbsp;(Firmware)
|
|
@@ -540,7 +547,7 @@ module Tinkerforge
|
|
|
540
547
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
541
548
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
542
549
|
#
|
|
543
|
-
# The baudrate will be increased
|
|
550
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
544
551
|
# decreased linearly if little data is send/received.
|
|
545
552
|
#
|
|
546
553
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -551,7 +558,7 @@ module Tinkerforge
|
|
|
551
558
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
552
559
|
# the dynamic baudrate off to get the highest possible performance.
|
|
553
560
|
#
|
|
554
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
561
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
555
562
|
# BrickIMUV2#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
556
563
|
# as set by BrickIMUV2#set_spitfp_baudrate will be used statically.
|
|
557
564
|
#
|
|
@@ -594,7 +601,7 @@ module Tinkerforge
|
|
|
594
601
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
595
602
|
# function corresponds to the maximum baudrate (see BrickIMUV2#set_spitfp_baudrate_config).
|
|
596
603
|
#
|
|
597
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
604
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
598
605
|
# or similar is necessary in you applications we recommend to not change
|
|
599
606
|
# the baudrate.
|
|
600
607
|
#
|
|
@@ -618,7 +625,7 @@ module Tinkerforge
|
|
|
618
625
|
#
|
|
619
626
|
# * ACK checksum errors,
|
|
620
627
|
# * message checksum errors,
|
|
621
|
-
# *
|
|
628
|
+
# * framing errors and
|
|
622
629
|
# * overflow errors.
|
|
623
630
|
#
|
|
624
631
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -1680,7 +1680,7 @@ module Tinkerforge
|
|
|
1680
1680
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
1681
1681
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
1682
1682
|
#
|
|
1683
|
-
# The baudrate will be increased
|
|
1683
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
1684
1684
|
# decreased linearly if little data is send/received.
|
|
1685
1685
|
#
|
|
1686
1686
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -1691,7 +1691,7 @@ module Tinkerforge
|
|
|
1691
1691
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
1692
1692
|
# the dynamic baudrate off to get the highest possible performance.
|
|
1693
1693
|
#
|
|
1694
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
1694
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
1695
1695
|
# BrickMaster#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
1696
1696
|
# as set by BrickMaster#set_spitfp_baudrate will be used statically.
|
|
1697
1697
|
#
|
|
@@ -1734,7 +1734,7 @@ module Tinkerforge
|
|
|
1734
1734
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
1735
1735
|
# function corresponds to the maximum baudrate (see BrickMaster#set_spitfp_baudrate_config).
|
|
1736
1736
|
#
|
|
1737
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
1737
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
1738
1738
|
# or similar is necessary in you applications we recommend to not change
|
|
1739
1739
|
# the baudrate.
|
|
1740
1740
|
#
|
|
@@ -1758,7 +1758,7 @@ module Tinkerforge
|
|
|
1758
1758
|
#
|
|
1759
1759
|
# * ACK checksum errors,
|
|
1760
1760
|
# * message checksum errors,
|
|
1761
|
-
# *
|
|
1761
|
+
# * framing errors and
|
|
1762
1762
|
# * overflow errors.
|
|
1763
1763
|
#
|
|
1764
1764
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -21,7 +21,9 @@ module Tinkerforge
|
|
|
21
21
|
CALLBACK_UNDER_VOLTAGE = 26
|
|
22
22
|
|
|
23
23
|
# This callback is triggered when a position set by BrickServo#set_position
|
|
24
|
-
# is reached.
|
|
24
|
+
# is reached. If the new position matches the current position then the
|
|
25
|
+
# callback is not triggered, because the servo didn't move.
|
|
26
|
+
# The parameters are the servo and the position that is reached.
|
|
25
27
|
#
|
|
26
28
|
# You can enable this callback with BrickServo#enable_position_reached_callback.
|
|
27
29
|
#
|
|
@@ -449,7 +451,7 @@ module Tinkerforge
|
|
|
449
451
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
450
452
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
451
453
|
#
|
|
452
|
-
# The baudrate will be increased
|
|
454
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
453
455
|
# decreased linearly if little data is send/received.
|
|
454
456
|
#
|
|
455
457
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -460,7 +462,7 @@ module Tinkerforge
|
|
|
460
462
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
461
463
|
# the dynamic baudrate off to get the highest possible performance.
|
|
462
464
|
#
|
|
463
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
465
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
464
466
|
# BrickServo#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
465
467
|
# as set by BrickServo#set_spitfp_baudrate will be used statically.
|
|
466
468
|
#
|
|
@@ -503,7 +505,7 @@ module Tinkerforge
|
|
|
503
505
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
504
506
|
# function corresponds to the maximum baudrate (see BrickServo#set_spitfp_baudrate_config).
|
|
505
507
|
#
|
|
506
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
508
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
507
509
|
# or similar is necessary in you applications we recommend to not change
|
|
508
510
|
# the baudrate.
|
|
509
511
|
#
|
|
@@ -527,7 +529,7 @@ module Tinkerforge
|
|
|
527
529
|
#
|
|
528
530
|
# * ACK checksum errors,
|
|
529
531
|
# * message checksum errors,
|
|
530
|
-
# *
|
|
532
|
+
# * framing errors and
|
|
531
533
|
# * overflow errors.
|
|
532
534
|
#
|
|
533
535
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -430,16 +430,16 @@ module Tinkerforge
|
|
|
430
430
|
# Sets the basic configuration parameters for the different modes (Stealth, Coolstep, Classic).
|
|
431
431
|
#
|
|
432
432
|
# * Standstill Current: This value can be used to lower the current during stand still. This might
|
|
433
|
-
# be reasonable to reduce the heating of the motor and the Brick. When the motor is in standstill
|
|
434
|
-
# the configured motor phase current will be driven until the configured
|
|
435
|
-
# Power Down Time is elapsed. After that the phase current will be reduced to the standstill
|
|
433
|
+
# be reasonable to reduce the heating of the motor and the Brick. When the motor is in standstill
|
|
434
|
+
# the configured motor phase current will be driven until the configured
|
|
435
|
+
# Power Down Time is elapsed. After that the phase current will be reduced to the standstill
|
|
436
436
|
# current. The elapsed time for this reduction can be configured with the Standstill Delay Time.
|
|
437
437
|
# The unit is in mA and the maximum allowed value is the configured maximum motor current
|
|
438
438
|
# (see BrickSilentStepper#set_motor_current).
|
|
439
439
|
#
|
|
440
|
-
# * Motor Run Current: The value sets the motor current when the motor is running.
|
|
441
|
-
# Use a value of at least one half of the global maximum motor current for a good
|
|
442
|
-
# microstep performance. The unit is in mA and the maximum allowed value is the current
|
|
440
|
+
# * Motor Run Current: The value sets the motor current when the motor is running.
|
|
441
|
+
# Use a value of at least one half of the global maximum motor current for a good
|
|
442
|
+
# microstep performance. The unit is in mA and the maximum allowed value is the current
|
|
443
443
|
# motor current. The API maps the entered value to 1/32 ... 32/32 of the maximum
|
|
444
444
|
# motor current. This value should be used to change the motor current during motor movement,
|
|
445
445
|
# whereas the global maximum motor current should not be changed while the motor is moving
|
|
@@ -676,7 +676,7 @@ module Tinkerforge
|
|
|
676
676
|
#
|
|
677
677
|
# * Motor Stalled: Is true if a motor stall was detected.
|
|
678
678
|
#
|
|
679
|
-
# * Actual Motor Current: Indicates the actual current control scaling as used in Coolstep mode.
|
|
679
|
+
# * Actual Motor Current: Indicates the actual current control scaling as used in Coolstep mode.
|
|
680
680
|
# The returned value is between 0 and 31. It represents a multiplier of 1/32 to 32/32 of the
|
|
681
681
|
# ``Motor Run Current`` as set by BrickSilentStepper#set_basic_configuration. Example: If a ``Motor Run Current``
|
|
682
682
|
# 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
|
|
|
759
759
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
760
760
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
761
761
|
#
|
|
762
|
-
# The baudrate will be increased
|
|
762
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
763
763
|
# decreased linearly if little data is send/received.
|
|
764
764
|
#
|
|
765
765
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -770,7 +770,7 @@ module Tinkerforge
|
|
|
770
770
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
771
771
|
# the dynamic baudrate off to get the highest possible performance.
|
|
772
772
|
#
|
|
773
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
773
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
774
774
|
# BrickSilentStepper#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
775
775
|
# as set by BrickSilentStepper#set_spitfp_baudrate will be used statically.
|
|
776
776
|
#
|
|
@@ -811,7 +811,7 @@ module Tinkerforge
|
|
|
811
811
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
812
812
|
# function corresponds to the maximum baudrate (see BrickSilentStepper#set_spitfp_baudrate_config).
|
|
813
813
|
#
|
|
814
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
814
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
815
815
|
# or similar is necessary in you applications we recommend to not change
|
|
816
816
|
# the baudrate.
|
|
817
817
|
#
|
|
@@ -831,7 +831,7 @@ module Tinkerforge
|
|
|
831
831
|
#
|
|
832
832
|
# * ACK checksum errors,
|
|
833
833
|
# * message checksum errors,
|
|
834
|
-
# *
|
|
834
|
+
# * framing errors and
|
|
835
835
|
# * overflow errors.
|
|
836
836
|
#
|
|
837
837
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|
|
@@ -502,7 +502,7 @@ module Tinkerforge
|
|
|
502
502
|
# enabled, the Brick will try to adapt the baudrate for the communication
|
|
503
503
|
# between Bricks and Bricklets according to the amount of data that is transferred.
|
|
504
504
|
#
|
|
505
|
-
# The baudrate will be increased
|
|
505
|
+
# The baudrate will be increased exponentially if lots of data is send/received and
|
|
506
506
|
# decreased linearly if little data is send/received.
|
|
507
507
|
#
|
|
508
508
|
# This lowers the baudrate in applications where little data is transferred (e.g.
|
|
@@ -513,7 +513,7 @@ module Tinkerforge
|
|
|
513
513
|
# (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn
|
|
514
514
|
# the dynamic baudrate off to get the highest possible performance.
|
|
515
515
|
#
|
|
516
|
-
# The maximum value of the baudrate can be set per port with the function
|
|
516
|
+
# The maximum value of the baudrate can be set per port with the function
|
|
517
517
|
# BrickStepper#set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate
|
|
518
518
|
# as set by BrickStepper#set_spitfp_baudrate will be used statically.
|
|
519
519
|
#
|
|
@@ -556,7 +556,7 @@ module Tinkerforge
|
|
|
556
556
|
# If the dynamic baudrate feature is enabled, the baudrate set by this
|
|
557
557
|
# function corresponds to the maximum baudrate (see BrickStepper#set_spitfp_baudrate_config).
|
|
558
558
|
#
|
|
559
|
-
# Regulatory testing is done with the default baudrate. If CE
|
|
559
|
+
# Regulatory testing is done with the default baudrate. If CE compatibility
|
|
560
560
|
# or similar is necessary in you applications we recommend to not change
|
|
561
561
|
# the baudrate.
|
|
562
562
|
#
|
|
@@ -580,7 +580,7 @@ module Tinkerforge
|
|
|
580
580
|
#
|
|
581
581
|
# * ACK checksum errors,
|
|
582
582
|
# * message checksum errors,
|
|
583
|
-
# *
|
|
583
|
+
# * framing errors and
|
|
584
584
|
# * overflow errors.
|
|
585
585
|
#
|
|
586
586
|
# The errors counts are for errors that occur on the Brick side. All
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# -*- ruby encoding: utf-8 -*-
|
|
2
2
|
#############################################################
|
|
3
|
-
# This file was automatically generated on 2018-
|
|
3
|
+
# This file was automatically generated on 2018-09-28. #
|
|
4
4
|
# #
|
|
5
|
-
# Ruby Bindings Version 2.1.
|
|
5
|
+
# Ruby Bindings Version 2.1.18 #
|
|
6
6
|
# #
|
|
7
7
|
# If you have a bugfix for this file and want to commit it, #
|
|
8
8
|
# please fix the bug in the generator. You can find a link #
|