Struct tinkerforge::industrial_digital_out_4_v2_bricklet::IndustrialDigitalOut4V2Bricklet

pub struct IndustrialDigitalOut4V2Bricklet { /* private fields */ }

4 galvanically isolated digital outputs

Implementations

impl IndustrialDigitalOut4V2Bricklet

pub const DEVICE_IDENTIFIER: u16 = 2_124u16

pub const DEVICE_DISPLAY_NAME: &'static str = "Industrial Digital Out 4 Bricklet 2.0"

pub fn new(
    uid: &str,
    ip_connection: &IpConnection
) -> IndustrialDigitalOut4V2Bricklet

Creates an object with the unique device ID uid. This object can then be used after the IP Connection ip_connection is connected.

pub fn get_response_expected(
    &mut self,
    fun: IndustrialDigitalOut4V2BrickletFunction
) -> Result<bool, GetResponseExpectedError>

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 send and errors are silently ignored, because they cannot be detected.

See set_response_expected for the list of function ID constants available for this function.

pub fn set_response_expected(
    &mut self,
    fun: IndustrialDigitalOut4V2BrickletFunction,
    response_expected: bool
) -> Result<(), SetResponseExpectedError>

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 send and errors are silently ignored, because they cannot be detected.

pub fn set_response_expected_all(&mut self, response_expected: bool)

Changes the response expected flag for all setter and callback configuration functions of this device at once.

pub fn get_monoflop_done_callback_receiver(
    &self
) -> ConvertingCallbackReceiver<MonoflopDoneEvent>

This receiver is triggered whenever a monoflop timer reaches 0. The parameters contain the channel and the current value of the channel (the value after the monoflop).

pub fn set_value(&self, value: [bool; 4]) -> ConvertingReceiver<()>

Sets the output value of all four channels. A value of true or false outputs logic 1 or logic 0 respectively on the corresponding channel.

Use Set Selected Value to change only one output channel state.

For example: (True, True, False, False) will turn the channels 0-1 high and the channels 2-3 low.

pub fn get_value(&self) -> ConvertingReceiver<[bool; 4]>

Returns the logic levels that are currently output on the channels.

pub fn set_selected_value(
    &self,
    channel: u8,
    value: bool
) -> ConvertingReceiver<()>

Sets the output value of a specific channel without affecting the other channels.

pub fn set_monoflop(
    &self,
    channel: u8,
    value: bool,
    time: u32
) -> ConvertingReceiver<()>

The first parameter is the desired state of the channel (true means output high and false means output low). The second parameter indicates the time (in ms) that the channel should hold the state.

If this function is called with the parameters (true, 1500): The channel 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 IO-4 Bricklet is connected to one of the slave stacks. You can now call this function every second, with a time parameter of two seconds. The channel will be high all the time. If now the RS485 connection is lost, the channel will turn low in at most two seconds.

pub fn get_monoflop(&self, channel: u8) -> ConvertingReceiver<Monoflop>

Returns (for the given channel) the current value and the time as set by Set Monoflop as well as the remaining time until the value flips.

If the timer is not running currently, the remaining time will be returned as 0.

pub fn set_channel_led_config(
    &self,
    channel: u8,
    config: u8
) -> ConvertingReceiver<()>

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.

By default all channel LEDs are configured as Channel Status.

Associated constants:

• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_OFF
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_ON
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_SHOW_HEARTBEAT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_SHOW_CHANNEL_STATUS

pub fn get_channel_led_config(&self, channel: u8) -> ConvertingReceiver<u8>

Returns the channel LED configuration as set by Set Channel LED Config

Associated constants:

• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_OFF
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_ON
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_SHOW_HEARTBEAT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_CHANNEL_LED_CONFIG_SHOW_CHANNEL_STATUS

pub fn set_pwm_configuration(
    &self,
    channel: u8,
    frequency: u32,
    duty_cycle: u16
) -> ConvertingReceiver<()>

Activates a PWM for the given channel with the frequency given in 1/10Hz and the duty cycle given in 1/100%.

To turn the PWM off again, you can set the frequency to 0 or any other function that changes a value of the channel (e.g. Set Selected Value).

The maximum duty cycle value is 10000 (100%). The optocoupler of the Industrial Digital Out 4 Bricklet 2.0 has a rise time and fall time of 11.5us (each) at 24V. So the maximum useful frequency value is about 400000 (40kHz).

The default values are 0, 0.

pub fn get_pwm_configuration(
    &self,
    channel: u8
) -> ConvertingReceiver<PwmConfiguration>

Returns the PWM configuration as set by Set PWM Configuration.

pub fn get_spitfp_error_count(&self) -> ConvertingReceiver<SpitfpErrorCount>

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 Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

pub fn set_bootloader_mode(&self, mode: u8) -> ConvertingReceiver<u8>

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.

Associated constants:

• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_BOOTLOADER
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_FIRMWARE
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_STATUS_OK
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_STATUS_INVALID_MODE
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_STATUS_NO_CHANGE
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_STATUS_CRC_MISMATCH

pub fn get_bootloader_mode(&self) -> ConvertingReceiver<u8>

Returns the current bootloader mode, see Set Bootloader Mode.

Associated constants:

• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_BOOTLOADER
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_FIRMWARE
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT

pub fn set_write_firmware_pointer(&self, pointer: u32) -> ConvertingReceiver<()>

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.

pub fn write_firmware(&self, data: [u8; 64]) -> ConvertingReceiver<u8>

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.

pub fn set_status_led_config(&self, config: u8) -> ConvertingReceiver<()>

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.

Associated constants:

• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_OFF
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_ON
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS

pub fn get_status_led_config(&self) -> ConvertingReceiver<u8>

Returns the configuration as set by Set Status LED Config

Associated constants:

• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_OFF
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_ON
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_SHOW_HEARTBEAT
• INDUSTRIAL_DIGITAL_OUT_4_V2BRICKLET_STATUS_LED_CONFIG_SHOW_STATUS

pub fn get_chip_temperature(&self) -> ConvertingReceiver<i16>

Returns the temperature in °C 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.

pub fn 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!

pub fn write_uid(&self, uid: u32) -> ConvertingReceiver<()>

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.

pub fn read_uid(&self) -> ConvertingReceiver<u32>

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

pub fn get_identity(&self) -> ConvertingReceiver<Identity>

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’ or ‘d’.

The device identifier numbers can be found here. |device_identifier_constant|

Trait Implementations

impl Clone for IndustrialDigitalOut4V2Bricklet

fn clone(&self) -> IndustrialDigitalOut4V2Bricklet

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.