LabVIEW - OLED 128x64 Bricklet 2.0¶

Hello World¶

Download (Example Hello World.vi)

Basic Functions¶

BrickletOLED128x64V2(uid, ipcon) → oled128x64V2¶

Input:	uid – Type: String ipcon – Type: .NET Refnum (IPConnection)
Output:	oled128x64V2 – Type: .NET Refnum (BrickletOLED128x64V2)

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

BrickletOLED128x64V2.WritePixels(xStart, yStart, xEnd, yEnd, pixels)¶

Input:	xStart – Type: Byte, Range: [0 to 127] yStart – Type: Byte, Range: [0 to 63] xEnd – Type: Byte, Range: [0 to 127] yEnd – Type: Byte, Range: [0 to 63] pixels – Type: Boolean[], Length: variable

Writes pixels to the specified window.

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 – Type: Byte, Range: [0 to 127] yStart – Type: Byte, Range: [0 to 63] xEnd – Type: Byte, Range: [0 to 127] yEnd – Type: Byte, Range: [0 to 63]
Output:	pixels – Type: Boolean[], Length: variable

Reads pixels from the specified window.

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.

If automatic draw is enabled (default) the pixels are directly cleared.

If automatic draw is disabled the the internal buffer is cleared 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.WriteLine(line, position, text)¶

Input:	line – Type: Byte, Range: [0 to 7] position – Type: Byte, Range: [0 to 21] text – Type: String, Length: up to 22

Writes text to a specific line with a specific position. 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.

If automatic draw is enabled (default) the text is 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 text is 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.

The font conforms to code page 437.

BrickletOLED128x64V2.DrawBufferedFrame(forceCompleteRedraw)¶

Input:	forceCompleteRedraw – Type: 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 – Type: Byte, Range: [0 to 255], Default: 143 invert – Type: Boolean, Default: F automaticDraw – Type: Boolean, Default: T

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().

BrickletOLED128x64V2.GetDisplayConfiguration() → contrast, invert, automaticDraw¶

Output:	contrast – Type: Byte, Range: [0 to 255], Default: 143 invert – Type: Boolean, Default: F automaticDraw – Type: Boolean, Default: T

Returns the configuration as set by SetDisplayConfiguration().

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

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

• 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 – Type: Byte, Range: See constants, Default: 3

Returns the configuration as set by SetStatusLEDConfig()

The following constants are available for this function:

For config:

• 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 – 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.

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

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.

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

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

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

• 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 – 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.

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

• 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

For status:

• 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 – Type: Byte, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode().

The following constants are available for this function:

For mode:

• 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 – 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.

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

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

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

BrickletOLED128x64V2.DEVICE_IDENTIFIER¶

This constant is used to identify a OLED 128x64 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.

BrickletOLED128x64V2.DEVICE_DISPLAY_NAME¶

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