LabVIEW - OLED 128x64 Bricklet 2.0

This is the description of the LabVIEW API bindings for the OLED 128x64 Bricklet 2.0. General information and technical specifications for the OLED 128x64 Bricklet 2.0 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

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

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

BrickletOLED128x64V2.WritePixels(xStart, yStart, xEnd, yEnd, pixels)
Input:
  • xStart -- Byte
  • yStart -- Byte
  • xEnd -- Byte
  • yEnd -- Byte
  • pixels -- Boolean[]

Writes pixels to the specified window.

The x-axis goes from 0 to 127 and the y-axis from 0 to 63. The pixels are written into the window line by line top to bottom and each line is written from left to right.

If automatic draw is enabled (default) the pixels are directly written to the screen. Only pixels that have actually changed are updated on the screen, the rest stays the same.

If automatic draw is disabled the pixels are written to an internal buffer and the buffer is transferred to the display only after DrawBufferedFrame() is called. This can be used to avoid flicker when drawing a complex frame in multiple steps.

Automatic draw can be configured with the SetDisplayConfiguration() function.

BrickletOLED128x64V2.ReadPixels(xStart, yStart, xEnd, yEnd) → pixels
Input:
  • xStart -- Byte
  • yStart -- Byte
  • xEnd -- Byte
  • yEnd -- Byte
Output:
  • pixels -- Boolean[]

Reads pixels from the specified window.

The x-axis goes from 0 to 127 and the y-axis from 0 to 63. The pixels are read from the window line by line top to bottom and each line is read from left to right.

If automatic draw is enabled (default) the pixels that are read are always the same that are shown on the display.

If automatic draw is disabled the pixels are read from the internal buffer (see DrawBufferedFrame()).

Automatic draw can be configured with the SetDisplayConfiguration() function.

BrickletOLED128x64V2.ClearDisplay()

Clears the complete content of the display.

BrickletOLED128x64V2.WriteLine(line, position, text)
Input:
  • line -- Byte
  • position -- Byte
  • text -- String

Writes text to a specific line (0 to 7) with a specific position (0 to 21). The text can have a maximum of 22 characters.

For example: (1, 10, "Hello") will write Hello in the middle of the second line of the display.

The display uses a special 5x7 pixel charset. You can view the characters of the charset in Brick Viewer.

BrickletOLED128x64V2.DrawBufferedFrame(forceCompleteRedraw)
Input:
  • forceCompleteRedraw -- Boolean

Draws the currently buffered frame. Normally each call of WritePixels() and WriteLine() draws directly onto the display. If you turn automatic draw off (SetDisplayConfiguration()), the data is written in an internal buffer and only transferred to the display by calling this function. This can be used to avoid flicker when drawing a complex frame in multiple steps.

Set the force complete redraw to true to redraw the whole display instead of only the changed parts. Normally it should not be necessary to set this to true. It may only become necessary in case of stuck pixels because of errors.

Advanced Functions

BrickletOLED128x64V2.SetDisplayConfiguration(contrast, invert, automaticDraw)
Input:
  • contrast -- Byte
  • invert -- Boolean
  • automaticDraw -- Boolean

Sets the configuration of the display.

You can set a contrast value from 0 to 255 and you can invert the color (white/black) of the display.

If automatic draw is set to true, the display is automatically updated with every call of WritePixels() or WriteLine(). If it is set to false, the changes are written into an internal buffer and only shown on the display after a call of DrawBufferedFrame().

The default values are contrast 143, inverting off and automatic draw on.

BrickletOLED128x64V2.GetDisplayConfiguration() → contrast, invert, automaticDraw
Output:
  • contrast -- Byte
  • invert -- Boolean
  • automaticDraw -- Boolean

Returns the configuration as set by SetDisplayConfiguration().

BrickletOLED128x64V2.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.

BrickletOLED128x64V2.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.

BrickletOLED128x64V2.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:

  • BrickletOLED128x64V2.FUNCTION_WRITE_PIXELS = 1
  • BrickletOLED128x64V2.FUNCTION_CLEAR_DISPLAY = 3
  • BrickletOLED128x64V2.FUNCTION_SET_DISPLAY_CONFIGURATION = 4
  • BrickletOLED128x64V2.FUNCTION_WRITE_LINE = 6
  • BrickletOLED128x64V2.FUNCTION_DRAW_BUFFERED_FRAME = 7
  • BrickletOLED128x64V2.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BrickletOLED128x64V2.FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BrickletOLED128x64V2.FUNCTION_RESET = 243
  • BrickletOLED128x64V2.FUNCTION_WRITE_UID = 248
BrickletOLED128x64V2.SetResponseExpectedAll(responseExpected)
Input:
  • responseExpected -- Boolean

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

BrickletOLED128x64V2.GetSPITFPErrorCount() → errorCountAckChecksum, errorCountMessageChecksum, errorCountFrame, errorCountOverflow
Output:
  • errorCountAckChecksum -- Int64
  • errorCountMessageChecksum -- Int64
  • errorCountFrame -- Int64
  • errorCountOverflow -- Int64

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.

BrickletOLED128x64V2.SetBootloaderMode(mode) → status
Input:
  • mode -- Byte
Output:
  • status -- Byte

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:

  • BrickletOLED128x64V2.BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletOLED128x64V2.BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletOLED128x64V2.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletOLED128x64V2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletOLED128x64V2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
  • BrickletOLED128x64V2.BOOTLOADER_STATUS_OK = 0
  • BrickletOLED128x64V2.BOOTLOADER_STATUS_INVALID_MODE = 1
  • BrickletOLED128x64V2.BOOTLOADER_STATUS_NO_CHANGE = 2
  • BrickletOLED128x64V2.BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • BrickletOLED128x64V2.BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • BrickletOLED128x64V2.BOOTLOADER_STATUS_CRC_MISMATCH = 5
BrickletOLED128x64V2.GetBootloaderMode() → mode
Output:
  • mode -- Byte

Returns the current bootloader mode, see SetBootloaderMode().

The following constants are available for this function:

  • BrickletOLED128x64V2.BOOTLOADER_MODE_BOOTLOADER = 0
  • BrickletOLED128x64V2.BOOTLOADER_MODE_FIRMWARE = 1
  • BrickletOLED128x64V2.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BrickletOLED128x64V2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BrickletOLED128x64V2.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
BrickletOLED128x64V2.SetWriteFirmwarePointer(pointer)
Input:
  • pointer -- Int64

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.

BrickletOLED128x64V2.WriteFirmware(data) → status
Input:
  • data -- Byte[64]
Output:
  • status -- Byte

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.

BrickletOLED128x64V2.SetStatusLEDConfig(config)
Input:
  • config -- Byte

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:

  • BrickletOLED128x64V2.STATUS_LED_CONFIG_OFF = 0
  • BrickletOLED128x64V2.STATUS_LED_CONFIG_ON = 1
  • BrickletOLED128x64V2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletOLED128x64V2.STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletOLED128x64V2.GetStatusLEDConfig() → config
Output:
  • config -- Byte

Returns the configuration as set by SetStatusLEDConfig()

The following constants are available for this function:

  • BrickletOLED128x64V2.STATUS_LED_CONFIG_OFF = 0
  • BrickletOLED128x64V2.STATUS_LED_CONFIG_ON = 1
  • BrickletOLED128x64V2.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BrickletOLED128x64V2.STATUS_LED_CONFIG_SHOW_STATUS = 3
BrickletOLED128x64V2.GetChipTemperature() → temperature
Output:
  • temperature -- Int16

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.

BrickletOLED128x64V2.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!

BrickletOLED128x64V2.WriteUID(uid)
Input:
  • uid -- Int64

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.

BrickletOLED128x64V2.ReadUID() → uid
Output:
  • uid -- Int64

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

BrickletOLED128x64V2.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.

Constants

BrickletOLED128x64V2.DEVICE_IDENTIFIER

This constant is used to identify a OLED 128x64 Bricklet 2.0.

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

BrickletOLED128x64V2.DEVICE_DISPLAY_NAME

This constant represents the human readable name of a OLED 128x64 Bricklet 2.0.