Deutsch
English
Menu
Software / API Bindings / Mathematica / API Reference and Examples / Bricklets / E-Paper 296x128 Bricklet

Mathematica - E-Paper 296x128 Bricklet

This is the description of the Mathematica API bindings for the E-Paper 296x128 Bricklet. General information and technical specifications for the E-Paper 296x128 Bricklet are summarized in its hardware description.

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

Examples

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

Hello World

Download (ExampleHelloWorld.nb)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your E-Paper 296x128 Bricklet*)

(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
ep=NETNew["Tinkerforge.BrickletEPaper296x128",uid,ipcon]
ipcon@Connect[host,port]

(*Use black background*)
ep@FillDisplay[Tinkerforge`BrickletEPaper296x128`COLORUBLACK]

(*Write big white "Hello World" in the middle of the screen*)
ep@DrawText[16,48,Tinkerforge`BrickletEPaper296x128`FONTU24X32,
            Tinkerforge`BrickletEPaper296x128`COLORUWHITE,
            Tinkerforge`BrickletEPaper296x128`ORIENTATIONUHORIZONTAL,"Hello World"]
ep@Draw[]

(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[ep]
ReleaseNETObject[ipcon]

API

Generally, every function of the Mathematica bindings that returns a value can throw a Tinkerforge.TimeoutException. This exception gets thrown 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.

Since .NET/Link does not support multiple return values directly, we use the out keyword to return multiple values from a function. For further information about the out keyword in .NET/Link see the corresponding Mathematica .NET/Link documentation.

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

Basic Functions

BrickletEPaper296x128[uid, ipcon] → ePaper296x128
Parameters:
  • uid – Type: String
  • ipcon – Type: NETObject[IPConnection]
Returns:
  • ePaper296x128 – Type: NETObject[BrickletEPaper296x128]

Creates an object with the unique device ID uid:

ePaper296x128=NETNew["Tinkerforge.BrickletEPaper296x128","YOUR_DEVICE_UID",ipcon]

This object can then be used after the IP Connection is connected.

The .NET runtime has built-in garbage collection that frees objects that are no longer in use by a program. But because Mathematica can not automatically tell when a Mathematica "program" doesn't use a .NET object anymore, this has to be done by the program. For this the ReleaseNETObject[] function is used in the examples.

For further information about object management in .NET/Link see the corresponding Mathematica .NET/Link documentation.

BrickletEPaper296x128@Draw[] → Null

Draws the current black/white and red or gray buffer to the e-paper display.

The Bricklet does not have any double-buffering. You should not call this function while writing to the buffer. See GetDrawStatus[].

BrickletEPaper296x128@GetDrawStatus[] → drawStatus
Returns:
  • drawStatus – Type: Integer, Range: See constants

Returns one of three draw statuses:

  • Idle
  • Copying: Data is being copied from the buffer of the Bricklet to the buffer of the display.
  • Drawing: The display is updating its content (during this phase the flickering etc happens).

You can write to the buffer (through one of the write or draw functions) when the status is either idle or drawing. You should not write to the buffer while it is being copied to the display. There is no double-buffering.

The following constants are available for this function:

For drawStatus:

  • BrickletEPaper296x128`DRAWUSTATUSUIDLE = 0
  • BrickletEPaper296x128`DRAWUSTATUSUCOPYING = 1
  • BrickletEPaper296x128`DRAWUSTATUSUDRAWING = 2
BrickletEPaper296x128@WriteBlackWhite[xStart, yStart, xEnd, yEnd, {pixels1, pixels2, ...}] → Null
Parameters:
  • xStart – Type: Integer, Range: [0 to 295]
  • yStart – Type: Integer, Range: [0 to 127]
  • xEnd – Type: Integer, Range: [0 to 295]
  • yEnd – Type: Integer, Range: [0 to 127]
  • pixelsi – Type: True/False

Writes black/white pixels to the specified window into the buffer.

The pixels are written into the window line by line top to bottom and each line is written from left to right.

The value 0 (false) corresponds to a black pixel and the value 1 (true) to a white pixel.

This function writes the pixels into the black/white pixel buffer, to draw the buffer to the display use Draw[].

Use WriteColor[] to write red or gray pixels.

BrickletEPaper296x128@ReadBlackWhite[xStart, yStart, xEnd, yEnd] → {pixels1, pixels2, ...}
Parameters:
  • xStart – Type: Integer, Range: [0 to 295]
  • yStart – Type: Integer, Range: [0 to 127]
  • xEnd – Type: Integer, Range: [0 to 295]
  • yEnd – Type: Integer, Range: [0 to 127]
Returns:
  • pixelsi – Type: True/False

Returns the current content of the black/white pixel buffer for the specified window.

The pixels are read into the window line by line top to bottom and each line is read from left to right.

The current content of the buffer does not have to be the current content of the display. It is possible that the data was not drawn to the display yet and after a restart of the Bricklet the buffer will be reset to black, while the display retains its content.

BrickletEPaper296x128@WriteColor[xStart, yStart, xEnd, yEnd, {pixels1, pixels2, ...}] → Null
Parameters:
  • xStart – Type: Integer, Range: [0 to 295]
  • yStart – Type: Integer, Range: [0 to 127]
  • xEnd – Type: Integer, Range: [0 to 295]
  • yEnd – Type: Integer, Range: [0 to 127]
  • pixelsi – Type: True/False

The E-Paper 296x128 Bricklet is available with the colors black/white/red and black/white/gray. Depending on the model this function writes either red or gray pixels to the specified window into the buffer.

The pixels are written into the window line by line top to bottom and each line is written from left to right.

The value 0 (false) means that this pixel does not have color. It will be either black or white (see WriteBlackWhite[]). The value 1 (true) corresponds to a red or gray pixel, depending on the Bricklet model.

This function writes the pixels into the red or gray pixel buffer, to draw the buffer to the display use Draw[].

Use WriteBlackWhite[] to write black/white pixels.

BrickletEPaper296x128@ReadColor[xStart, yStart, xEnd, yEnd] → {pixels1, pixels2, ...}
Parameters:
  • xStart – Type: Integer, Range: [0 to 295]
  • yStart – Type: Integer, Range: [0 to 127]
  • xEnd – Type: Integer, Range: [0 to 295]
  • yEnd – Type: Integer, Range: [0 to 127]
Returns:
  • pixelsi – Type: True/False

Returns the current content of the red or gray pixel buffer for 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.

The current content of the buffer does not have to be the current content of the display. It is possible that the data was not drawn to the display yet and after a restart of the Bricklet the buffer will be reset to black, while the display retains its content.

BrickletEPaper296x128@FillDisplay[color] → Null
Parameters:
  • color – Type: Integer, Range: See constants

Fills the complete content of the display with the given color.

This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer to the display use Draw[].

The following constants are available for this function:

For color:

  • BrickletEPaper296x128`COLORUBLACK = 0
  • BrickletEPaper296x128`COLORUWHITE = 1
  • BrickletEPaper296x128`COLORURED = 2
  • BrickletEPaper296x128`COLORUGRAY = 2
BrickletEPaper296x128@DrawText[positionX, positionY, font, color, orientation, text] → Null
Parameters:
  • positionX – Type: Integer, Range: [0 to 295]
  • positionY – Type: Integer, Range: [0 to 127]
  • font – Type: Integer, Range: See constants
  • color – Type: Integer, Range: See constants
  • orientation – Type: Integer, Range: See constants
  • text – Type: String, Length: up to 50

Draws a text with up to 50 characters at the pixel position (x, y).

You can use one of 9 different font sizes and draw the text in black/white/red|gray. The text can be drawn horizontal or vertical.

This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer to the display use Draw[].

The font conforms to code page 437.

The following constants are available for this function:

For font:

  • BrickletEPaper296x128`FONTU6X8 = 0
  • BrickletEPaper296x128`FONTU6X16 = 1
  • BrickletEPaper296x128`FONTU6X24 = 2
  • BrickletEPaper296x128`FONTU6X32 = 3
  • BrickletEPaper296x128`FONTU12X16 = 4
  • BrickletEPaper296x128`FONTU12X24 = 5
  • BrickletEPaper296x128`FONTU12X32 = 6
  • BrickletEPaper296x128`FONTU18X24 = 7
  • BrickletEPaper296x128`FONTU18X32 = 8
  • BrickletEPaper296x128`FONTU24X32 = 9

For color:

  • BrickletEPaper296x128`COLORUBLACK = 0
  • BrickletEPaper296x128`COLORUWHITE = 1
  • BrickletEPaper296x128`COLORURED = 2
  • BrickletEPaper296x128`COLORUGRAY = 2

For orientation:

  • BrickletEPaper296x128`ORIENTATIONUHORIZONTAL = 0
  • BrickletEPaper296x128`ORIENTATIONUVERTICAL = 1
BrickletEPaper296x128@DrawLine[positionXStart, positionYStart, positionXEnd, positionYEnd, color] → Null
Parameters:
  • positionXStart – Type: Integer, Range: [0 to 295]
  • positionYStart – Type: Integer, Range: [0 to 127]
  • positionXEnd – Type: Integer, Range: [0 to 295]
  • positionYEnd – Type: Integer, Range: [0 to 127]
  • color – Type: Integer, Range: See constants

Draws a line from (x, y)-start to (x, y)-end in the given color.

This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer to the display use Draw[].

The following constants are available for this function:

For color:

  • BrickletEPaper296x128`COLORUBLACK = 0
  • BrickletEPaper296x128`COLORUWHITE = 1
  • BrickletEPaper296x128`COLORURED = 2
  • BrickletEPaper296x128`COLORUGRAY = 2
BrickletEPaper296x128@DrawBox[positionXStart, positionYStart, positionXEnd, positionYEnd, fill, color] → Null
Parameters:
  • positionXStart – Type: Integer, Range: [0 to 295]
  • positionYStart – Type: Integer, Range: [0 to 127]
  • positionXEnd – Type: Integer, Range: [0 to 295]
  • positionYEnd – Type: Integer, Range: [0 to 127]
  • fill – Type: True/False
  • color – Type: Integer, Range: See constants

Draws a box from (x, y)-start to (x, y)-end in the given color.

If you set fill to true, the box will be filled with the color. Otherwise only the outline will be drawn.

This function writes the pixels into the black/white/red|gray pixel buffer, to draw the buffer to the display use Draw[].

The following constants are available for this function:

For color:

  • BrickletEPaper296x128`COLORUBLACK = 0
  • BrickletEPaper296x128`COLORUWHITE = 1
  • BrickletEPaper296x128`COLORURED = 2
  • BrickletEPaper296x128`COLORUGRAY = 2

Advanced Functions

BrickletEPaper296x128@SetUpdateMode[updateMode] → Null
Parameters:
  • updateMode – Type: Integer, Range: See constants, Default: 0

Note

The default update mode corresponds to the default e-paper display manufacturer settings. All of the other modes are experimental and will result in increased ghosting and possibly other long-term side effects.

If you want to know more about the inner workings of an e-paper display take a look at this excellent video from Ben Krasnow: https://www.youtube.com/watch?v=MsbiO8EAsGw.

If you are not sure about this option, leave the update mode at default.

Currently there are three update modes available:

  • Default: Settings as given by the manufacturer. An update will take about 7.5 seconds and during the update the screen will flicker several times.
  • Black/White: This will only update the black/white pixel. It uses the manufacturer settings for black/white and ignores the red or gray pixel buffer. With this mode the display will flicker once and it takes about 2.5 seconds. Compared to the default settings there is more ghosting.
  • Delta: This will only update the black/white pixel. It uses an aggressive method where the changes are not applied for a whole buffer but only for the delta between the last and the next buffer. With this mode the display will not flicker during an update and it takes about 900-950ms. Compared to the other two settings there is more ghosting. This mode can be used for something like a flicker-free live update of a text.

With the black/white/red display if you use either the black/white or the delta mode, after a while of going back and forth between black and white the white color will start to appear red-ish or pink-ish.

If you use the aggressive delta mode and rapidly change the content, we recommend that you change back to the default mode every few hours and in the default mode cycle between the three available colors a few times. This will get rid of the ghosting and after that you can go back to the delta mode with flicker-free updates.

The following constants are available for this function:

For updateMode:

  • BrickletEPaper296x128`UPDATEUMODEUDEFAULT = 0
  • BrickletEPaper296x128`UPDATEUMODEUBLACKUWHITE = 1
  • BrickletEPaper296x128`UPDATEUMODEUDELTA = 2
BrickletEPaper296x128@GetUpdateMode[] → updateMode
Returns:
  • updateMode – Type: Integer, Range: See constants, Default: 0

Returns the update mode as set by SetUpdateMode[].

The following constants are available for this function:

For updateMode:

  • BrickletEPaper296x128`UPDATEUMODEUDEFAULT = 0
  • BrickletEPaper296x128`UPDATEUMODEUBLACKUWHITE = 1
  • BrickletEPaper296x128`UPDATEUMODEUDELTA = 2
BrickletEPaper296x128@SetDisplayType[displayType] → Null
Parameters:
  • displayType – Type: Integer, Range: See constants

Sets the type of the display. The e-paper display is available in black/white/red and black/white/gray. This will be factory set during the flashing and testing phase. The value is saved in non-volatile memory and will stay after a power cycle.

The following constants are available for this function:

For displayType:

  • BrickletEPaper296x128`DISPLAYUTYPEUBLACKUWHITEURED = 0
  • BrickletEPaper296x128`DISPLAYUTYPEUBLACKUWHITEUGRAY = 1
BrickletEPaper296x128@GetDisplayType[] → displayType
Returns:
  • displayType – Type: Integer, Range: See constants

Returns the type of the e-paper display. It can either be black/white/red or black/white/gray.

The following constants are available for this function:

For displayType:

  • BrickletEPaper296x128`DISPLAYUTYPEUBLACKUWHITEURED = 0
  • BrickletEPaper296x128`DISPLAYUTYPEUBLACKUWHITEUGRAY = 1
BrickletEPaper296x128@SetDisplayDriver[displayDriver] → Null
Parameters:
  • displayDriver – Type: Integer, Range: See constants

Sets the type of display driver. The Bricklet can currently support SSD1675A and SSD1680. This will be factory set during the flashing and testing phase. The value is saved in non-volatile memory and will stay after a power cycle.

The following constants are available for this function:

For displayDriver:

  • BrickletEPaper296x128`DISPLAYUDRIVERUSSD1675A = 0
  • BrickletEPaper296x128`DISPLAYUDRIVERUSSD1680 = 1

New in version 2.0.3 (Plugin).

BrickletEPaper296x128@GetDisplayDriver[] → displayDriver
Returns:
  • displayDriver – Type: Integer, Range: See constants

Returns the e-paper display driver.

The following constants are available for this function:

For displayDriver:

  • BrickletEPaper296x128`DISPLAYUDRIVERUSSD1675A = 0
  • BrickletEPaper296x128`DISPLAYUDRIVERUSSD1680 = 1

New in version 2.0.3 (Plugin).

BrickletEPaper296x128@GetSPITFPErrorCount[out errorCountAckChecksum, out errorCountMessageChecksum, out errorCountFrame, out errorCountOverflow] → Null
Output Parameters:
  • errorCountAckChecksum – Type: Integer, Range: [0 to 232 - 1]
  • errorCountMessageChecksum – Type: Integer, Range: [0 to 232 - 1]
  • errorCountFrame – Type: Integer, Range: [0 to 232 - 1]
  • errorCountOverflow – Type: Integer, 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.

BrickletEPaper296x128@SetStatusLEDConfig[config] → Null
Parameters:
  • config – Type: Integer, 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:

  • BrickletEPaper296x128`STATUSULEDUCONFIGUOFF = 0
  • BrickletEPaper296x128`STATUSULEDUCONFIGUON = 1
  • BrickletEPaper296x128`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletEPaper296x128`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletEPaper296x128@GetStatusLEDConfig[] → config
Returns:
  • config – Type: Integer, Range: See constants, Default: 3

Returns the configuration as set by SetStatusLEDConfig[]

The following constants are available for this function:

For config:

  • BrickletEPaper296x128`STATUSULEDUCONFIGUOFF = 0
  • BrickletEPaper296x128`STATUSULEDUCONFIGUON = 1
  • BrickletEPaper296x128`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletEPaper296x128`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletEPaper296x128@GetChipTemperature[] → temperature
Returns:
  • temperature – Type: Integer, 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.

BrickletEPaper296x128@Reset[] → Null

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!

BrickletEPaper296x128@GetIdentity[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null
Output Parameters:
  • uid – Type: String, Length: up to 8
  • connectedUid – Type: String, Length: up to 8
  • position – Type: Integer, Range: [ToCharacterCode["a"][[0]] to ToCharacterCode["h"][[0]], ToCharacterCode["z"][[0]]]
  • hardwareVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]
  • firmwareVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, Range: [0 to 255]
  • deviceIdentifier – Type: Integer, 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.

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:

MyCallback[sender_,value_]:=Print["Value: "<>ToString[value]]

AddEventHandler[ePaper296x128@ExampleCallback,MyCallback]

For further information about event handling using .NET/Link see the corresponding Mathematica .NET/Link documentation.

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 BrickletEPaper296x128@DrawStatusCallback[sender, drawStatus]
Callback Parameters:
  • sender – Type: NETObject[BrickletEPaper296x128]
  • drawStatus – Type: Integer, Range: See constants

Callback for the current draw status. Will be called every time the draw status changes (see GetDrawStatus[]).

The following constants are available for this function:

For drawStatus:

  • BrickletEPaper296x128`DRAWUSTATUSUIDLE = 0
  • BrickletEPaper296x128`DRAWUSTATUSUCOPYING = 1
  • BrickletEPaper296x128`DRAWUSTATUSUDRAWING = 2

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.

BrickletEPaper296x128@GetAPIVersion[] → {apiVersion1, apiVersion2, apiVersion3}
Output Parameters:
  • apiVersioni – Type: Integer
    • 1: major – Type: Integer, Range: [0 to 255]
    • 2: minor – Type: Integer, Range: [0 to 255]
    • 3: revision – Type: Integer, 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.

BrickletEPaper296x128@GetResponseExpected[functionId] → responseExpected
Parameters:
  • functionId – Type: Integer, Range: See constants
Returns:
  • responseExpected – Type: True/False

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:

  • BrickletEPaper296x128`FUNCTIONUDRAW = 1
  • BrickletEPaper296x128`FUNCTIONUWRITEUBLACKUWHITE = 3
  • BrickletEPaper296x128`FUNCTIONUWRITEUCOLOR = 5
  • BrickletEPaper296x128`FUNCTIONUFILLUDISPLAY = 7
  • BrickletEPaper296x128`FUNCTIONUDRAWUTEXT = 8
  • BrickletEPaper296x128`FUNCTIONUDRAWULINE = 9
  • BrickletEPaper296x128`FUNCTIONUDRAWUBOX = 10
  • BrickletEPaper296x128`FUNCTIONUSETUUPDATEUMODE = 12
  • BrickletEPaper296x128`FUNCTIONUSETUDISPLAYUTYPE = 14
  • BrickletEPaper296x128`FUNCTIONUSETUDISPLAYUDRIVER = 16
  • BrickletEPaper296x128`FUNCTIONUSETUWRITEUFIRMWAREUPOINTER = 237
  • BrickletEPaper296x128`FUNCTIONUSETUSTATUSULEDUCONFIG = 239
  • BrickletEPaper296x128`FUNCTIONURESET = 243
  • BrickletEPaper296x128`FUNCTIONUWRITEUUID = 248
BrickletEPaper296x128@SetResponseExpected[functionId, responseExpected] → Null
Parameters:
  • functionId – Type: Integer, Range: See constants
  • responseExpected – Type: True/False

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:

  • BrickletEPaper296x128`FUNCTIONUDRAW = 1
  • BrickletEPaper296x128`FUNCTIONUWRITEUBLACKUWHITE = 3
  • BrickletEPaper296x128`FUNCTIONUWRITEUCOLOR = 5
  • BrickletEPaper296x128`FUNCTIONUFILLUDISPLAY = 7
  • BrickletEPaper296x128`FUNCTIONUDRAWUTEXT = 8
  • BrickletEPaper296x128`FUNCTIONUDRAWULINE = 9
  • BrickletEPaper296x128`FUNCTIONUDRAWUBOX = 10
  • BrickletEPaper296x128`FUNCTIONUSETUUPDATEUMODE = 12
  • BrickletEPaper296x128`FUNCTIONUSETUDISPLAYUTYPE = 14
  • BrickletEPaper296x128`FUNCTIONUSETUDISPLAYUDRIVER = 16
  • BrickletEPaper296x128`FUNCTIONUSETUWRITEUFIRMWAREUPOINTER = 237
  • BrickletEPaper296x128`FUNCTIONUSETUSTATUSULEDUCONFIG = 239
  • BrickletEPaper296x128`FUNCTIONURESET = 243
  • BrickletEPaper296x128`FUNCTIONUWRITEUUID = 248
BrickletEPaper296x128@SetResponseExpectedAll[responseExpected] → Null
Parameters:
  • responseExpected – Type: True/False

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.

BrickletEPaper296x128@SetBootloaderMode[mode] → status
Parameters:
  • mode – Type: Integer, Range: See constants
Returns:
  • status – Type: Integer, 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:

  • BrickletEPaper296x128`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletEPaper296x128`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletEPaper296x128`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletEPaper296x128`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletEPaper296x128`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4

For status:

  • BrickletEPaper296x128`BOOTLOADERUSTATUSUOK = 0
  • BrickletEPaper296x128`BOOTLOADERUSTATUSUINVALIDUMODE = 1
  • BrickletEPaper296x128`BOOTLOADERUSTATUSUNOUCHANGE = 2
  • BrickletEPaper296x128`BOOTLOADERUSTATUSUENTRYUFUNCTIONUNOTUPRESENT = 3
  • BrickletEPaper296x128`BOOTLOADERUSTATUSUDEVICEUIDENTIFIERUINCORRECT = 4
  • BrickletEPaper296x128`BOOTLOADERUSTATUSUCRCUMISMATCH = 5
BrickletEPaper296x128@GetBootloaderMode[] → mode
Returns:
  • mode – Type: Integer, Range: See constants

Returns the current bootloader mode, see SetBootloaderMode[].

The following constants are available for this function:

For mode:

  • BrickletEPaper296x128`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletEPaper296x128`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletEPaper296x128`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletEPaper296x128`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletEPaper296x128`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4
BrickletEPaper296x128@SetWriteFirmwarePointer[pointer] → Null
Parameters:
  • pointer – Type: Integer, 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.

BrickletEPaper296x128@WriteFirmware[{data1, data2, ..., data64}] → status
Parameters:
  • datai – Type: Integer, Range: [0 to 255]
Returns:
  • status – Type: Integer, 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.

BrickletEPaper296x128@WriteUID[uid] → Null
Parameters:
  • uid – Type: Integer, 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.

BrickletEPaper296x128@ReadUID[] → uid
Returns:
  • uid – Type: Integer, Range: [0 to 232 - 1]

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

Constants

BrickletEPaper296x128`DEVICEUIDENTIFIER

This constant is used to identify a E-Paper 296x128 Bricklet.

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.

BrickletEPaper296x128`DEVICEDISPLAYNAME

This constant represents the human readable name of a E-Paper 296x128 Bricklet.