This is the description of the Rust API bindings for the Industrial Dual AC Relay Bricklet. General information and technical specifications for the Industrial Dual AC Relay Bricklet are summarized in its hardware description.
An installation guide for the Rust API bindings is part of their general description. Additional documentation can be found on docs.rs.
The example code below is Public Domain (CC0 1.0).
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 | use std::{error::Error, io, thread, time::Duration};
use tinkerforge::{industrial_dual_ac_relay_bricklet::*, ip_connection::IpConnection};
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your Industrial Dual AC Relay Bricklet.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let idacr = IndustrialDualAcRelayBricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
// Turn relays alternating on/off 10 times with 1 second delay
for _i in 0..5 {
thread::sleep(Duration::from_millis(1000));
idacr.set_value(true, false).recv()?;
thread::sleep(Duration::from_millis(1000));
idacr.set_value(false, true).recv()?;
}
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
ipcon.disconnect();
Ok(())
}
|
To allow non-blocking usage, nearly every function of the Rust bindings returns a wrapper around a mpsc::Receiver. To block until the function has finished and get your result, call one of the receiver's recv variants. Those return either the result sent by the device, or any error occurred.
Functions returning a result directly will block until the device has finished processing the request.
All functions listed below are thread-safe, those which return a receiver are lock-free.
IndustrialDualAcRelayBricklet::
new
(uid: &str, ip_connection: &IpConnection) → IndustrialDualAcRelayBricklet¶Parameters: |
|
---|---|
Returns: |
|
Creates a new IndustrialDualAcRelayBricklet
object with the unique device ID uid
and adds
it to the IPConnection ip_connection
:
let industrial_dual_ac_relay = IndustrialDualAcRelayBricklet::new("YOUR_DEVICE_UID", &ip_connection);
This device object can be used after the IP connection has been connected.
IndustrialDualAcRelayBricklet::
set_value
(&self, channel0: bool, channel1: bool) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the state of the relays, true means on and false means off. For example: (true, false) turns relay 0 on and relay 1 off.
If you just want to set one of the relays and don't know the current state
of the other relay, you can get the state with IndustrialDualAcRelayBricklet::get_value
or you
can use IndustrialDualAcRelayBricklet::set_selected_value
.
All running monoflop timers will be aborted if this function is called.
IndustrialDualAcRelayBricklet::
get_value
(&self) → ConvertingReceiver<Value>¶Return Object: |
|
---|
Returns the state of the relays, true means on and false means off.
IndustrialDualAcRelayBricklet::
set_channel_led_config
(&self, channel: u8, config: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
Each channel has a corresponding LED. You can turn the LED off, on or show a heartbeat. You can also set the LED to "Channel Status". In this mode the LED is on if the channel is high and off otherwise.
The following constants are available for this function:
For config:
IndustrialDualAcRelayBricklet::
get_channel_led_config
(&self, channel: u8) → ConvertingReceiver<u8>¶Parameters: |
|
---|---|
Returns: |
|
Returns the channel LED configuration as set by IndustrialDualAcRelayBricklet::set_channel_led_config
The following constants are available for this function:
For config:
IndustrialDualAcRelayBricklet::
set_monoflop
(&self, channel: u8, value: bool, time: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
The first parameter can be 0 or 1 (relay 0 or relay 1). The second parameter is the desired state of the relay (true means on and false means off). The third parameter indicates the time that the relay should hold the state.
If this function is called with the parameters (1, true, 1500): Relay 1 will turn on and in 1.5s it will turn off again.
A monoflop can be used as a failsafe mechanism. For example: Lets assume you have a RS485 bus and a Industrial Dual AC Relay Bricklet connected to one of the slave stacks. You can now call this function every second, with a time parameter of two seconds. The relay will be on all the time. If now the RS485 connection is lost, the relay will turn off in at most two seconds.
IndustrialDualAcRelayBricklet::
get_monoflop
(&self, channel: u8) → ConvertingReceiver<Monoflop>¶Parameters: |
|
---|---|
Return Object: |
|
Returns (for the given relay) the current state and the time as set by
IndustrialDualAcRelayBricklet::set_monoflop
as well as the remaining time until the state flips.
If the timer is not running currently, the remaining time will be returned as 0.
IndustrialDualAcRelayBricklet::
set_selected_value
(&self, channel: u8, value: bool) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the state of the selected relay, true means on and false means off.
A running monoflop timer for the selected relay will be aborted if this function is called.
The other relay remains untouched.
IndustrialDualAcRelayBricklet::
get_spitfp_error_count
(&self) → ConvertingReceiver<SpitfpErrorCount>¶Return Object: |
|
---|
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.
IndustrialDualAcRelayBricklet::
set_status_led_config
(&self, config: u8) → ConvertingReceiver<()>¶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:
IndustrialDualAcRelayBricklet::
get_status_led_config
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the configuration as set by IndustrialDualAcRelayBricklet::set_status_led_config
The following constants are available for this function:
For config:
IndustrialDualAcRelayBricklet::
get_chip_temperature
(&self) → ConvertingReceiver<i16>¶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.
IndustrialDualAcRelayBricklet::
reset
(&self) → ConvertingReceiver<()>¶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!
IndustrialDualAcRelayBricklet::
get_identity
(&self) → ConvertingReceiver<Identity>¶Return Object: |
|
---|
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 corresponding get_*_callback_receiver function, which returns a receiver for callback events.
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.
IndustrialDualAcRelayBricklet::
get_monoflop_done_callback_receiver
(&self) → ConvertingCallbackReceiver<MonoflopDoneEvent>¶Event Object: |
|
---|
Receivers created with this function receive Monoflop Done events.
This callback is triggered whenever a monoflop timer reaches 0. The parameters contain the relay and the current state of the relay (the state after the monoflop).
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.
IndustrialDualAcRelayBricklet::
get_api_version
(&self) → [u8; 3]¶Return Object: |
|
---|
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.
IndustrialDualAcRelayBricklet::
get_response_expected
(&mut self, function_id: u8) → 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
IndustrialDualAcRelayBricklet::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:
IndustrialDualAcRelayBricklet::
set_response_expected
(&mut self, function_id: u8, response_expected: bool) → ()¶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:
IndustrialDualAcRelayBricklet::
set_response_expected_all
(&mut self, response_expected: bool) → ()¶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.
IndustrialDualAcRelayBricklet::
set_bootloader_mode
(&self, mode: u8) → ConvertingReceiver<u8>¶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:
IndustrialDualAcRelayBricklet::
get_bootloader_mode
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the current bootloader mode, see IndustrialDualAcRelayBricklet::set_bootloader_mode
.
The following constants are available for this function:
For mode:
IndustrialDualAcRelayBricklet::
set_write_firmware_pointer
(&self, pointer: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the firmware pointer for IndustrialDualAcRelayBricklet::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.
IndustrialDualAcRelayBricklet::
write_firmware
(&self, data: [u8; 64]) → ConvertingReceiver<u8>¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
IndustrialDualAcRelayBricklet::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.
IndustrialDualAcRelayBricklet::
write_uid
(&self, uid: u32) → ConvertingReceiver<()>¶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.
IndustrialDualAcRelayBricklet::
read_uid
(&self) → ConvertingReceiver<u32>¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
IndustrialDualAcRelayBricklet::
DEVICE_IDENTIFIER
¶This constant is used to identify a Industrial Dual AC Relay Bricklet.
The IndustrialDualAcRelayBricklet::get_identity
function and the IpConnection::get_enumerate_callback_receiver
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
IndustrialDualAcRelayBricklet::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Industrial Dual AC Relay Bricklet.