LabVIEW - Solid State Relay Bricklet

This is the description of the LabVIEW API bindings for the Solid State Relay Bricklet. General information and technical specifications for the Solid State Relay Bricklet are summarized in its hardware description.

An installation guide for the LabVIEW API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

API

Generally, every method of the LabVIEW bindings that outputs a value can report a Tinkerforge.TimeoutException. This error gets reported if the device did not respond. If a cable based connection is used, it is unlikely that this exception gets thrown (assuming nobody plugs the device out). However, if a wireless connection is used, timeouts will occur if the distance to the device gets too big.

The namespace for all Brick/Bricklet bindings and the IPConnection is Tinkerforge.*.

Basic Functions

BrickletSolidStateRelay(uid, ipcon) → solidStateRelay
Input:
  • uid -- String
  • ipcon -- .NET Refnum (IPConnection)
Output:
  • solidStateRelay -- .NET Refnum (BrickletSolidStateRelay)

Creates an object with the unique device ID uid. This object can then be used after the IP Connection is connected (see examples above).

BrickletSolidStateRelay.SetState(state)
Input:
  • state -- Boolean

Sets the state of the relays true means on and false means off.

Running monoflop timers will be overwritten if this function is called.

The default value is false.

BrickletSolidStateRelay.GetState() → state
Output:
  • state -- Boolean

Returns the state of the relay, true means on and false means off.

Advanced Functions

BrickletSolidStateRelay.SetMonoflop(state, time)
Input:
  • state -- Boolean
  • time -- Int64

The first parameter is the desired state of the relay (true means on and false means off). The second parameter indicates the time (in ms) that the relay should hold the state.

If this function is called with the parameters (true, 1500): The relay 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 Solid State 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.

BrickletSolidStateRelay.GetMonoflop() → state, time, timeRemaining
Output:
  • state -- Boolean
  • time -- Int64
  • timeRemaining -- Int64

Returns the current state and the time as set by SetMonoflop() 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.

BrickletSolidStateRelay.GetAPIVersion() → apiVersion
Output:
  • apiVersion -- Byte[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.

BrickletSolidStateRelay.GetResponseExpected(functionId) → responseExpected
Input:
  • functionId -- Byte
Output:
  • responseExpected -- Boolean

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 SetResponseExpected(). 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 SetResponseExpected() for the list of function ID constants available for this function.

BrickletSolidStateRelay.SetResponseExpected(functionId, responseExpected)
Input:
  • functionId -- Byte
  • responseExpected -- Boolean

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.

The following function ID constants are available for this function:

  • BrickletSolidStateRelay.FUNCTION_SET_STATE = 1
  • BrickletSolidStateRelay.FUNCTION_SET_MONOFLOP = 3
BrickletSolidStateRelay.SetResponseExpectedAll(responseExpected)
Input:
  • responseExpected -- Boolean

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

BrickletSolidStateRelay.GetIdentity() → uid, connectedUid, position, hardwareVersion, firmwareVersion, deviceIdentifier
Output:
  • uid -- String
  • connectedUid -- String
  • position -- Char
  • hardwareVersion -- Byte[3]
  • firmwareVersion -- Byte[3]
  • deviceIdentifier -- Int32

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. There is also a constant for the device identifier of this Bricklet.

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a function to a callback property of the device object. The available callback property and their 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.

event BrickletSolidStateRelay.MonoflopDoneCallback(sender, state)
Input:
  • sender -- .NET Refnum (BrickletSolidStateRelay)
  • state -- Boolean

This callback is triggered whenever the monoflop timer reaches 0. The parameter is the current state of the relay (the state after the monoflop).

Constants

BrickletSolidStateRelay.DEVICE_IDENTIFIER

This constant is used to identify a Solid State Relay Bricklet.

The GetIdentity() function and the EnumerateCallback callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

BrickletSolidStateRelay.DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Solid State Relay Bricklet.