Deutsch
English
Menu
Software / API Bindings / LabVIEW / API Reference and Examples / Bricklets / Load Cell Bricklet 2.0

LabVIEW - Load Cell Bricklet 2.0

This is the description of the LabVIEW API bindings for the Load Cell Bricklet 2.0. General information and technical specifications for the Load Cell Bricklet 2.0 are summarized in its hardware description.

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

API

Generally, every function 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

BrickletLoadCellV2(uid, ipcon) → loadCellV2
Input:
  • uid – Type: String
  • ipcon – Type: .NET Refnum (IPConnection)
Output:
  • loadCellV2 – Type: .NET Refnum (BrickletLoadCellV2)

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

BrickletLoadCellV2.GetWeight() → weight
Output:
  • weight – Type: Int32, Unit: 1 g, Range: [-231 to 231 - 1]

Returns the currently measured weight.

If you want to get the value periodically, it is recommended to use the WeightCallback callback. You can set the callback configuration with SetWeightCallbackConfiguration().

BrickletLoadCellV2.SetInfoLEDConfig(config)
Input:
  • config – Type: Byte, Range: See constants, Default: 0

Configures the info LED to be either turned off, turned on, or blink in heartbeat mode.

The following constants are available for this function:

For config:

  • BrickletLoadCellV2.INFO_LED_CONFIG_OFF = 0
  • BrickletLoadCellV2.INFO_LED_CONFIG_ON = 1
  • BrickletLoadCellV2.INFO_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletLoadCellV2.GetInfoLEDConfig() → config
Output:
  • config – Type: Byte, Range: See constants, Default: 0

Returns the LED configuration as set by SetInfoLEDConfig()

The following constants are available for this function:

For config:

  • BrickletLoadCellV2.INFO_LED_CONFIG_OFF = 0
  • BrickletLoadCellV2.INFO_LED_CONFIG_ON = 1
  • BrickletLoadCellV2.INFO_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletLoadCellV2.Tare()

Sets the currently measured weight as tare weight.

Advanced Functions

BrickletLoadCellV2.SetMovingAverage(average)
Input:
  • average – Type: Int32, Range: [1 to 100], Default: 4

Sets the length of a moving averaging for the weight value.

Setting the length to 1 will turn the averaging off. With less averaging, there is more noise on the data.

BrickletLoadCellV2.GetMovingAverage() → average
Output:
  • average – Type: Int32, Range: [1 to 100], Default: 4

Returns the length moving average as set by SetMovingAverage().

BrickletLoadCellV2.Calibrate(weight)
Input:
  • weight – Type: Int64, Unit: 1 g, Range: [0 to 232 - 1]

To calibrate your Load Cell Bricklet 2.0 you have to

  • empty the scale and call this function with 0 and
  • add a known weight to the scale and call this function with the weight.

The calibration is saved in the flash of the Bricklet and only needs to be done once.

We recommend to use the Brick Viewer for calibration, you don't need to call this function in your source code.

BrickletLoadCellV2.SetConfiguration(rate, gain)
Input:
  • rate – Type: Byte, Range: See constants, Default: 0
  • gain – Type: Byte, Range: See constants, Default: 0

The measurement rate and gain are configurable.

The rate can be either 10Hz or 80Hz. A faster rate will produce more noise. It is additionally possible to add a moving average (see SetMovingAverage()) to the measurements.

The gain can be 128x, 64x or 32x. It represents a measurement range of ±20mV, ±40mV and ±80mV respectively. The Load Cell Bricklet uses an excitation voltage of 5V and most load cells use an output of 2mV/V. That means the voltage range is ±15mV for most load cells (i.e. gain of 128x is best). If you don't know what all of this means you should keep it at 128x, it will most likely be correct.

The following constants are available for this function:

For rate:

  • BrickletLoadCellV2.RATE_10HZ = 0
  • BrickletLoadCellV2.RATE_80HZ = 1

For gain:

  • BrickletLoadCellV2.GAIN_128X = 0
  • BrickletLoadCellV2.GAIN_64X = 1
  • BrickletLoadCellV2.GAIN_32X = 2
BrickletLoadCellV2.GetConfiguration() → rate, gain
Output:
  • rate – Type: Byte, Range: See constants, Default: 0
  • gain – Type: Byte, Range: See constants, Default: 0

Returns the configuration as set by SetConfiguration().

The following constants are available for this function:

For rate:

  • BrickletLoadCellV2.RATE_10HZ = 0
  • BrickletLoadCellV2.RATE_80HZ = 1

For gain:

  • BrickletLoadCellV2.GAIN_128X = 0
  • BrickletLoadCellV2.GAIN_64X = 1
  • BrickletLoadCellV2.GAIN_32X = 2
BrickletLoadCellV2.GetSPITFPErrorCount() → errorCountAckChecksum, errorCountMessageChecksum, errorCountFrame, errorCountOverflow
Output:
  • errorCountAckChecksum – Type: Int64, Range: [0 to 232 - 1]
  • errorCountMessageChecksum – Type: Int64, Range: [0 to 232 - 1]
  • errorCountFrame – Type: Int64, Range: [0 to 232 - 1]
  • errorCountOverflow – Type: Int64, Range: [0 to 232 - 1]

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.

BrickletLoadCellV2.SetStatusLEDConfig(config)
Input:
  • config – Type: Byte, Range: See constants, Default: 3

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:

  • BrickletLoadCellV2.STATUS_LED_CONFIG_OFF = 0
  • BrickletLoadCellV2.STATUS_LED_CONFIG_ON = 1
  • BrickletLoadCellV2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletLoadCellV2.STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletLoadCellV2.GetStatusLEDConfig() → config
Output:
  • config – Type: Byte, Range: See constants, Default: 3

Returns the configuration as set by SetStatusLEDConfig()

The following constants are available for this function:

For config:

  • BrickletLoadCellV2.STATUS_LED_CONFIG_OFF = 0
  • BrickletLoadCellV2.STATUS_LED_CONFIG_ON = 1
  • BrickletLoadCellV2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletLoadCellV2.STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletLoadCellV2.GetChipTemperature() → temperature
Output:
  • temperature – Type: Int16, Unit: 1 °C, Range: [-215 to 215 - 1]

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.

BrickletLoadCellV2.Reset()

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!

BrickletLoadCellV2.GetIdentity() → uid, connectedUid, position, hardwareVersion, firmwareVersion, deviceIdentifier
Output:
  • uid – Type: String, Length: up to 8
  • connectedUid – Type: String, Length: up to 8
  • position – Type: Char, Range: ["a" to "h", "z"]
  • hardwareVersion – Type: Byte[3]
    • 0: major – Type: Byte, Range: [0 to 255]
    • 1: minor – Type: Byte, Range: [0 to 255]
    • 2: revision – Type: Byte, Range: [0 to 255]
  • firmwareVersion – Type: Byte[3]
    • 0: major – Type: Byte, Range: [0 to 255]
    • 1: minor – Type: Byte, Range: [0 to 255]
    • 2: revision – Type: Byte, Range: [0 to 255]
  • deviceIdentifier – Type: Int32, Range: [0 to 216 - 1]

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.

Callback Configuration Functions

BrickletLoadCellV2.SetWeightCallbackConfiguration(period, valueHasToChange, option, min, max)
Input:
  • period – Type: Int64, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • valueHasToChange – Type: Boolean, Default: F
  • option – Type: Char, Range: See constants, Default: "x"
  • min – Type: Int32, Unit: 1 g, Range: [-231 to 231 - 1], Default: 0
  • max – Type: Int32, Unit: 1 g, Range: [-231 to 231 - 1], Default: 0

The period is the period with which the WeightCallback callback is triggered periodically. A value of 0 turns the callback off.

If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.

If it is set to false, the callback is continuously triggered with the period, independent of the value.

It is furthermore possible to constrain the callback with thresholds.

The option-parameter together with min/max sets a threshold for the WeightCallback callback.

The following options are possible:

Option Description
'x' Threshold is turned off
'o' Threshold is triggered when the value is outside the min and max values
'i' Threshold is triggered when the value is inside or equal to the min and max values
'<' Threshold is triggered when the value is smaller than the min value (max is ignored)
'>' Threshold is triggered when the value is greater than the min value (max is ignored)

If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.

The following constants are available for this function:

For option:

  • BrickletLoadCellV2.THRESHOLD_OPTION_OFF = "x"
  • BrickletLoadCellV2.THRESHOLD_OPTION_OUTSIDE = "o"
  • BrickletLoadCellV2.THRESHOLD_OPTION_INSIDE = "i"
  • BrickletLoadCellV2.THRESHOLD_OPTION_SMALLER = "<"
  • BrickletLoadCellV2.THRESHOLD_OPTION_GREATER = ">"
BrickletLoadCellV2.GetWeightCallbackConfiguration() → period, valueHasToChange, option, min, max
Output:
  • period – Type: Int64, Unit: 1 ms, Range: [0 to 232 - 1], Default: 0
  • valueHasToChange – Type: Boolean, Default: F
  • option – Type: Char, Range: See constants, Default: "x"
  • min – Type: Int32, Unit: 1 g, Range: [-231 to 231 - 1], Default: 0
  • max – Type: Int32, Unit: 1 g, Range: [-231 to 231 - 1], Default: 0

Returns the callback configuration as set by SetWeightCallbackConfiguration().

The following constants are available for this function:

For option:

  • BrickletLoadCellV2.THRESHOLD_OPTION_OFF = "x"
  • BrickletLoadCellV2.THRESHOLD_OPTION_OUTSIDE = "o"
  • BrickletLoadCellV2.THRESHOLD_OPTION_INSIDE = "i"
  • BrickletLoadCellV2.THRESHOLD_OPTION_SMALLER = "<"
  • BrickletLoadCellV2.THRESHOLD_OPTION_GREATER = ">"

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 BrickletLoadCellV2.WeightCallback → sender, weight
Callback Output:
  • sender – Type: .NET Refnum (BrickletLoadCellV2)
  • weight – Type: Int32, Unit: 1 g, Range: [-231 to 231 - 1]

This callback is triggered periodically according to the configuration set by SetWeightCallbackConfiguration().

The parameter is the same as GetWeight().

Virtual Functions

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.

BrickletLoadCellV2.GetAPIVersion() → apiVersion
Output:
  • apiVersion – Type: Byte[3]
    • 0: major – Type: Byte, Range: [0 to 255]
    • 1: minor – Type: Byte, Range: [0 to 255]
    • 2: revision – Type: Byte, Range: [0 to 255]

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.

BrickletLoadCellV2.GetResponseExpected(functionId) → responseExpected
Input:
  • functionId – Type: Byte, Range: See constants
Output:
  • responseExpected – Type: 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 sent and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For functionId:

  • BrickletLoadCellV2.FUNCTION_SET_WEIGHT_CALLBACK_CONFIGURATION = 2
  • BrickletLoadCellV2.FUNCTION_SET_MOVING_AVERAGE = 5
  • BrickletLoadCellV2.FUNCTION_SET_INFO_LED_CONFIG = 7
  • BrickletLoadCellV2.FUNCTION_CALIBRATE = 9
  • BrickletLoadCellV2.FUNCTION_TARE = 10
  • BrickletLoadCellV2.FUNCTION_SET_CONFIGURATION = 11
  • BrickletLoadCellV2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletLoadCellV2.FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletLoadCellV2.FUNCTION_RESET = 243
  • BrickletLoadCellV2.FUNCTION_WRITE_UID = 248
BrickletLoadCellV2.SetResponseExpected(functionId, responseExpected)
Input:
  • functionId – Type: Byte, Range: See constants
  • responseExpected – Type: 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 sent and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For functionId:

  • BrickletLoadCellV2.FUNCTION_SET_WEIGHT_CALLBACK_CONFIGURATION = 2
  • BrickletLoadCellV2.FUNCTION_SET_MOVING_AVERAGE = 5
  • BrickletLoadCellV2.FUNCTION_SET_INFO_LED_CONFIG = 7
  • BrickletLoadCellV2.FUNCTION_CALIBRATE = 9
  • BrickletLoadCellV2.FUNCTION_TARE = 10
  • BrickletLoadCellV2.FUNCTION_SET_CONFIGURATION = 11
  • BrickletLoadCellV2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletLoadCellV2.FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletLoadCellV2.FUNCTION_RESET = 243
  • BrickletLoadCellV2.FUNCTION_WRITE_UID = 248
BrickletLoadCellV2.SetResponseExpectedAll(responseExpected)
Input:
  • responseExpected – Type: Boolean

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

Internal Functions

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.

BrickletLoadCellV2.SetBootloaderMode(mode) → status
Input:
  • mode – Type: Byte, Range: See constants
Output:
  • status – Type: Byte, Range: See constants

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:

  • BrickletLoadCellV2.BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletLoadCellV2.BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletLoadCellV2.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletLoadCellV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletLoadCellV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

  • BrickletLoadCellV2.BOOTLOADER_STATUS_OK = 0
  • BrickletLoadCellV2.BOOTLOADER_STATUS_INVALID_MODE = 1
  • BrickletLoadCellV2.BOOTLOADER_STATUS_NO_CHANGE = 2
  • BrickletLoadCellV2.BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • BrickletLoadCellV2.BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • BrickletLoadCellV2.BOOTLOADER_STATUS_CRC_MISMATCH = 5
BrickletLoadCellV2.GetBootloaderMode() → mode
Output:
  • mode – Type: Byte, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode().

The following constants are available for this function:

For mode:

  • BrickletLoadCellV2.BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletLoadCellV2.BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletLoadCellV2.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletLoadCellV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletLoadCellV2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
BrickletLoadCellV2.SetWriteFirmwarePointer(pointer)
Input:
  • pointer – Type: Int64, Unit: 1 B, Range: [0 to 232 - 1]

Sets the firmware pointer for WriteFirmware(). 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.

BrickletLoadCellV2.WriteFirmware(data) → status
Input:
  • data – Type: Byte[64], Range: [0 to 255]
Output:
  • status – Type: Byte, Range: [0 to 255]

Writes 64 Bytes of firmware at the position as written by SetWriteFirmwarePointer() 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.

BrickletLoadCellV2.WriteUID(uid)
Input:
  • uid – Type: Int64, Range: [0 to 232 - 1]

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.

BrickletLoadCellV2.ReadUID() → uid
Output:
  • uid – Type: Int64, Range: [0 to 232 - 1]

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

Constants

BrickletLoadCellV2.DEVICE_IDENTIFIER

This constant is used to identify a Load Cell Bricklet 2.0.

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

BrickletLoadCellV2.DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Load Cell Bricklet 2.0.