This is the description of the Ruby API bindings for the Remote Switch Bricklet 2.0. General information and technical specifications for the Remote Switch Bricklet 2.0 are summarized in its hardware description.
An installation guide for the Ruby API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example_switch_socket.rb)
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 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_remote_switch_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Remote Switch Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
rs = BrickletRemoteSwitchV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Switch on a type A socket with house code 17 and receiver code 1.
# House code 17 is 10001 in binary (least-significant bit first)
# and means that the DIP switches 1 and 5 are on and 2-4 are off.
# Receiver code 1 is 10000 in binary (least-significant bit first)
# and means that the DIP switch A is on and B-E are off.
rs.switch_socket_a 17, 1, BrickletRemoteSwitchV2::SWITCH_TO_ON
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
Download (example_remote_callback.rb)
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 34 35 36 37 38 39 40 41 42 | #!/usr/bin/env ruby
# -*- ruby encoding: utf-8 -*-
require 'tinkerforge/ip_connection'
require 'tinkerforge/bricklet_remote_switch_v2'
include Tinkerforge
HOST = 'localhost'
PORT = 4223
UID = 'XYZ' # Change XYZ to the UID of your Remote Switch Bricklet 2.0
ipcon = IPConnection.new # Create IP connection
rs = BrickletRemoteSwitchV2.new UID, ipcon # Create device object
ipcon.connect HOST, PORT # Connect to brickd
# Don't use device before ipcon is connected
# Configure to receive from remote type A with minimum repeats set to 1 and enable callback
rs.set_remote_configuration BrickletRemoteSwitchV2::REMOTE_TYPE_A, 1, true
# Register remote status a callback
rs.register_callback(BrickletRemoteSwitchV2::CALLBACK_REMOTE_STATUS_A) do |house_code,
receiver_code,
switch_to,
repeats|
puts "House Code: #{house_code}"
puts "Receiver Code: #{receiver_code}"
if switch_to == BrickletRemoteSwitchV2::SWITCH_TO_OFF
puts "Switch To: Off"
elsif switch_to == BrickletRemoteSwitchV2::SWITCH_TO_ON
puts "Switch To: On"
end
puts "Repeats: #{repeats}"
puts ''
end
puts 'Press key to exit'
$stdin.gets
ipcon.disconnect
|
All functions listed below are thread-safe.
BrickletRemoteSwitchV2
::
new
(uid, ipcon) → remote_switch_v2¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
remote_switch_v2 = BrickletRemoteSwitchV2.new 'YOUR_DEVICE_UID', ipcon
This object can then be used after the IP Connection is connected.
BrickletRemoteSwitchV2
#
get_switching_state
→ int¶Returns: |
|
---|
Returns the current switching state. If the current state is busy, the Bricklet is currently sending a code to switch a socket. It will not accept any calls of switch socket functions until the state changes to ready.
How long the switching takes is dependent on the number of repeats, see
#set_repeats
.
The following constants are available for this function:
For state:
BrickletRemoteSwitchV2
#
switch_socket_a
(house_code, receiver_code, switch_to) → nil¶Parameters: |
|
---|
To switch a type A socket you have to give the house code, receiver code and the state (on or off) you want to switch to.
A detailed description on how you can figure out the house and receiver code can be found here.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
#
switch_socket_b
(address, unit, switch_to) → nil¶Parameters: |
|
---|
To switch a type B socket you have to give the address, unit and the state (on or off) you want to switch to.
To switch all devices with the same address use 255 for the unit.
A detailed description on how you can teach a socket the address and unit can be found here.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
#
dim_socket_b
(address, unit, dim_value) → nil¶Parameters: |
|
---|
To control a type B dimmer you have to give the address, unit and the dim value you want to set the dimmer to.
A detailed description on how you can teach a dimmer the address and unit can be found here.
BrickletRemoteSwitchV2
#
switch_socket_c
(system_code, device_code, switch_to) → nil¶Parameters: |
|
---|
To switch a type C socket you have to give the system code, device code and the state (on or off) you want to switch to.
A detailed description on how you can figure out the system and device code can be found here.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
#
set_remote_configuration
(remote_type, minimum_repeats, callback_enabled) → nil¶Parameters: |
|
---|
Sets the configuration for receiving data from a remote of type A, B or C.
::CALLBACK_REMOTE_STATUS_A
callback,
::CALLBACK_REMOTE_STATUS_B
callback and ::CALLBACK_REMOTE_STATUS_C
callback).The following constants are available for this function:
For remote_type:
BrickletRemoteSwitchV2
#
get_remote_configuration
→ [int, int, bool]¶Return Array: |
|
---|
Returns the remote configuration as set by #set_remote_configuration
The following constants are available for this function:
For remote_type:
BrickletRemoteSwitchV2
#
get_remote_status_a
→ [int, int, int, int]¶Return Array: |
|
---|
Returns the house code, receiver code, switch state (on/off) and number of repeats for remote type A.
Repeats == 0 means there was no button press. Repeats >= 1 means there was a button press with the specified house/receiver code. The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number.
Use the callback to get this data automatically when a button is pressed,
see #set_remote_configuration
and ::CALLBACK_REMOTE_STATUS_A
callback.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
#
get_remote_status_b
→ [int, int, int, int, int]¶Return Array: |
|
---|
Returns the address (unique per remote), unit (button number), switch state (on/off) and number of repeats for remote type B.
If the remote supports dimming the dim value is used instead of the switch state.
If repeats=0 there was no button press. If repeats >= 1 there was a button press with the specified address/unit. The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number.
Use the callback to get this data automatically when a button is pressed,
see #set_remote_configuration
and ::CALLBACK_REMOTE_STATUS_B
callback.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
#
get_remote_status_c
→ [chr, int, int, int]¶Return Array: |
|
---|
Returns the system code, device code, switch state (on/off) and number of repeats for remote type C.
If repeats=0 there was no button press. If repeats >= 1 there was a button press with the specified system/device code. The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number.
Use the callback to get this data automatically when a button is pressed,
see #set_remote_configuration
and ::CALLBACK_REMOTE_STATUS_C
callback.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
#
set_repeats
(repeats) → nil¶Parameters: |
|
---|
Sets the number of times the code is sent when one of the Switch Socket functions is called. The repeats basically correspond to the amount of time that a button of the remote is pressed.
Some dimmers are controlled by the length of a button pressed, this can be simulated by increasing the repeats.
BrickletRemoteSwitchV2
#
get_repeats
→ int¶Returns: |
|
---|
Returns the number of repeats as set by #set_repeats
.
BrickletRemoteSwitchV2
#
get_spitfp_error_count
→ [int, int, int, int]¶Return Array: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
BrickletRemoteSwitchV2
#
set_status_led_config
(config) → nil¶Parameters: |
|
---|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following constants are available for this function:
For config:
BrickletRemoteSwitchV2
#
get_status_led_config
→ int¶Returns: |
|
---|
Returns the configuration as set by #set_status_led_config
The following constants are available for this function:
For config:
BrickletRemoteSwitchV2
#
get_chip_temperature
→ int¶Returns: |
|
---|
Returns the temperature 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 bad accuracy. Practically it is only useful as an indicator for temperature changes.
BrickletRemoteSwitchV2
#
reset
→ nil¶Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
BrickletRemoteSwitchV2
#
get_identity
→ [str, str, chr, [int, ...], [int, ...], int]¶Return Array: |
|
---|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.
Callbacks can be registered to receive time critical or recurring data from
the device. The registration is done with the
#register_callback
function of
the device object. The first parameter is the callback ID and the second
parameter is a block:
remote_switch_v2.register_callback BrickletRemoteSwitchV2::CALLBACK_EXAMPLE, do |param|
puts "#{param}"
end
The available constants with inherent number and 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.
BrickletRemoteSwitchV2
::
CALLBACK_SWITCHING_DONE
¶Callback Parameters: |
|
---|
This callback is triggered whenever the switching state changes
from busy to ready, see #get_switching_state
.
BrickletRemoteSwitchV2
::
CALLBACK_REMOTE_STATUS_A
¶Callback Parameters: |
|
---|
Returns the house code, receiver code, switch state (on/off) and number of repeats for remote type A.
The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number. The callback is triggered with every repeat.
You have to enable the callback with #set_remote_configuration
. The number
of repeats that you can set in the configuration is the minimum number of repeats that have
to be seen before the callback is triggered for the first time.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
::
CALLBACK_REMOTE_STATUS_B
¶Callback Parameters: |
|
---|
Returns the address (unique per remote), unit (button number), switch state (on/off) and number of repeats for remote type B.
If the remote supports dimming the dim value is used instead of the switch state.
The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number. The callback is triggered with every repeat.
You have to enable the callback with #set_remote_configuration
. The number
of repeats that you can set in the configuration is the minimum number of repeats that have
to be seen before the callback is triggered for the first time.
The following constants are available for this function:
For switch_to:
BrickletRemoteSwitchV2
::
CALLBACK_REMOTE_STATUS_C
¶Callback Parameters: |
|
---|
Returns the system code, device code, switch state (on/off) and number of repeats for remote type C.
The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number. The callback is triggered with every repeat.
You have to enable the callback with #set_remote_configuration
. The number
of repeats that you can set in the configuration is the minimum number of repeats that have
to be seen before the callback is triggered for the first time.
The following constants are available for this function:
For switch_to:
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
BrickletRemoteSwitchV2
#
get_api_version
→ [int, ...]¶Return Array: |
|
---|
Returns the version of the API definition 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.
BrickletRemoteSwitchV2
#
get_response_expected
(function_id) → bool¶Parameters: |
|
---|---|
Returns: |
|
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
#set_response_expected
. 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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletRemoteSwitchV2
#
set_response_expected
(function_id, response_expected) → nil¶Parameters: |
|
---|
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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
BrickletRemoteSwitchV2
#
set_response_expected_all
(response_expected) → nil¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletRemoteSwitchV2
#
set_bootloader_mode
(mode) → int¶Parameters: |
|
---|---|
Returns: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following constants are available for this function:
For mode:
For status:
BrickletRemoteSwitchV2
#
get_bootloader_mode
→ int¶Returns: |
|
---|
Returns the current bootloader mode, see #set_bootloader_mode
.
The following constants are available for this function:
For mode:
BrickletRemoteSwitchV2
#
set_write_firmware_pointer
(pointer) → nil¶Parameters: |
|
---|
Sets the firmware pointer for #write_firmware
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletRemoteSwitchV2
#
write_firmware
(data) → int¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
#set_write_firmware_pointer
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletRemoteSwitchV2
#
write_uid
(uid) → nil¶Parameters: |
|
---|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
BrickletRemoteSwitchV2
#
read_uid
→ int¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletRemoteSwitchV2
::
DEVICE_IDENTIFIER
¶This constant is used to identify a Remote Switch Bricklet 2.0.
The #get_identity()
function and the
IPConnection::CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletRemoteSwitchV2
::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Remote Switch Bricklet 2.0.