pub struct SegmentDisplay4x7Bricklet { /* private fields */ }
Expand description
Four 7-segment displays with switchable colon
Implementations§
source§impl SegmentDisplay4x7Bricklet
impl SegmentDisplay4x7Bricklet
pub const DEVICE_IDENTIFIER: u16 = 237u16
pub const DEVICE_DISPLAY_NAME: &'static str = "Segment Display 4x7 Bricklet"
sourcepub fn new<T: GetRequestSender>(
uid: &str,
req_sender: T
) -> SegmentDisplay4x7Bricklet
pub fn new<T: GetRequestSender>( uid: &str, req_sender: T ) -> SegmentDisplay4x7Bricklet
Creates an object with the unique device ID uid
. This object can then be used after the IP Connection ip_connection
is connected.
sourcepub fn get_response_expected(
&mut self,
fun: SegmentDisplay4x7BrickletFunction
) -> Result<bool, GetResponseExpectedError>
pub fn get_response_expected( &mut self, fun: SegmentDisplay4x7BrickletFunction ) -> 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 sent 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.
sourcepub fn set_response_expected(
&mut self,
fun: SegmentDisplay4x7BrickletFunction,
response_expected: bool
) -> Result<(), SetResponseExpectedError>
pub fn set_response_expected( &mut self, fun: SegmentDisplay4x7BrickletFunction, 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 sent and errors are silently ignored, because they cannot be detected.
sourcepub fn set_response_expected_all(&mut self, response_expected: bool)
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.
sourcepub fn get_api_version(&self) -> [u8; 3]
pub fn get_api_version(&self) -> [u8; 3]
Returns the version of the API definition (major, minor, revision) 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.
sourcepub fn get_counter_finished_callback_receiver(
&self
) -> ConvertingCallbackReceiver<()>
pub fn get_counter_finished_callback_receiver( &self ) -> ConvertingCallbackReceiver<()>
This receiver is triggered when the counter (see start_counter
) is
finished.
sourcepub fn set_segments(
&self,
segments: [u8; 4],
brightness: u8,
colon: bool
) -> ConvertingReceiver<()>
pub fn set_segments( &self, segments: [u8; 4], brightness: u8, colon: bool ) -> ConvertingReceiver<()>
The 7-segment display can be set with bitmaps. Every bit controls one segment:
.. image:: /Images/Bricklets/bricklet_segment_display_4x7_bit_order.png :scale: 100 % :alt: Bit order of one segment :align: center
For example to set a 5 you would want to activate segments 0, 2, 3, 5 and 6. This is represented by the number 0b01101101 = 0x6d = 109.
The brightness can be set between 0 (dark) and 7 (bright). The colon parameter turns the colon of the display on or off.
sourcepub fn get_segments(&self) -> ConvertingReceiver<Segments>
pub fn get_segments(&self) -> ConvertingReceiver<Segments>
Returns the segment, brightness and color data as set by
[set_segments
].
sourcepub fn start_counter(
&self,
value_from: i16,
value_to: i16,
increment: i16,
length: u32
) -> ConvertingReceiver<()>
pub fn start_counter( &self, value_from: i16, value_to: i16, increment: i16, length: u32 ) -> ConvertingReceiver<()>
Starts a counter with the from value that counts to the to value with the each step incremented by increment. length is the pause between each increment.
Example: If you set from to 0, to to 100, increment to 1 and length to 1000, a counter that goes from 0 to 100 with one second pause between each increment will be started.
Using a negative increment allows to count backwards.
You can stop the counter at every time by calling [set_segments
].
sourcepub fn get_counter_value(&self) -> ConvertingReceiver<u16>
pub fn get_counter_value(&self) -> ConvertingReceiver<u16>
Returns the counter value that is currently shown on the display.
If there is no counter running a 0 will be returned.
sourcepub fn get_identity(&self) -> ConvertingReceiver<Identity>
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’, ‘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. |device_identifier_constant|
Trait Implementations§
source§impl Clone for SegmentDisplay4x7Bricklet
impl Clone for SegmentDisplay4x7Bricklet
source§fn clone(&self) -> SegmentDisplay4x7Bricklet
fn clone(&self) -> SegmentDisplay4x7Bricklet
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more