Mathematica - Industrial Dual Relay Bricklet

This is the description of the Mathematica API bindings for the Industrial Dual Relay Bricklet. General information and technical specifications for the Industrial Dual Relay 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).

Simple

Download (ExampleSimple.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
Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]

host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your Industrial Dual Relay Bricklet*)

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

(*Turn relays alternating on/off 10 times with 1 second delay*)
For[i=0,i<5,i++,
 Pause[1];
 idr@SetValue[True,False];
 Pause[1];
 idr@SetValue[False,True]
]

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

API

Generally, every method 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 method. 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

BrickletIndustrialDualRelay[uid, ipcon] → industrialDualRelay
Parameters:
  • uid -- String
  • ipcon -- NETObject[IPConnection]
Returns:
  • industrialDualRelay -- NETObject[BrickletIndustrialDualRelay]

Creates an object with the unique device ID uid:

industrialDualRelay=NETNew["Tinkerforge.BrickletIndustrialDualRelay","YOUR_DEVICE_UID",ipcon]

This object can then be used after the IP Connection is connected (see examples above).

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.

BrickletIndustrialDualRelay@SetValue[channel0, channel1] → Null
Parameters:
  • channel0 -- True/False
  • channel1 -- True/False

Sets the state of the relays, true means on and false means off. For example: (true, false) turns relay 0 on and relay 1 off.

If you just want to set one of the relays and don't know the current state of the other relay, you can get the state with GetValue[] or you can use SetSelectedValue[].

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

The default value is (false, false).

BrickletIndustrialDualRelay@GetValue[out channel0, out channel1] → Null
Parameters:
  • channel0 -- True/False
  • channel1 -- True/False

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

Advanced Functions

BrickletIndustrialDualRelay@SetMonoflop[channel, value, time] → Null
Parameters:
  • channel -- Integer
  • value -- True/False
  • time -- Integer

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

If this function is called with the parameters (1, true, 1500): Relay 1 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 Industrial Dual 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.

BrickletIndustrialDualRelay@GetMonoflop[channel, out value, out time, out timeRemaining] → Null
Parameters:
  • channel -- Integer
  • value -- True/False
  • time -- Integer
  • timeRemaining -- Integer

Returns (for the given relay) 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.

BrickletIndustrialDualRelay@SetSelectedValue[channel, value] → Null
Parameters:
  • channel -- Integer
  • value -- True/False

Sets the state of the selected relay (0 or 1), true means on and false means off.

The other relay remains untouched.

BrickletIndustrialDualRelay@GetAPIVersion[] → {apiVersion1, apiVersion2, apiVersion3}
Returns:
  • apiVersioni -- Integer

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.

BrickletIndustrialDualRelay@GetResponseExpected[functionId] → responseExpected
Parameters:
  • functionId -- Integer
Returns:
  • responseExpected -- 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 send and errors are silently ignored, because they cannot be detected.

See SetResponseExpected[] for the list of function ID constants available for this function.

BrickletIndustrialDualRelay@SetResponseExpected[functionId, responseExpected] → Null
Parameters:
  • functionId -- Integer
  • responseExpected -- 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 send and errors are silently ignored, because they cannot be detected.

The following function ID constants are available for this function:

  • BrickletIndustrialDualRelay`FUNCTIONUSETUVALUE = 1
  • BrickletIndustrialDualRelay`FUNCTIONUSETUMONOFLOP = 3
  • BrickletIndustrialDualRelay`FUNCTIONUSETUSELECTEDUVALUE = 6
  • BrickletIndustrialDualRelay`FUNCTIONUSETUWRITEUFIRMWAREUPOINTER = 237
  • BrickletIndustrialDualRelay`FUNCTIONUSETUSTATUSULEDUCONFIG = 239
  • BrickletIndustrialDualRelay`FUNCTIONURESET = 243
  • BrickletIndustrialDualRelay`FUNCTIONUWRITEUUID = 248
BrickletIndustrialDualRelay@SetResponseExpectedAll[responseExpected] → Null
Parameters:
  • responseExpected -- True/False

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

BrickletIndustrialDualRelay@GetSPITFPErrorCount[out errorCountAckChecksum, out errorCountMessageChecksum, out errorCountFrame, out errorCountOverflow] → Null
Parameters:
  • errorCountAckChecksum -- Integer
  • errorCountMessageChecksum -- Integer
  • errorCountFrame -- Integer
  • errorCountOverflow -- Integer

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.

BrickletIndustrialDualRelay@SetBootloaderMode[mode] → status
Parameters:
  • mode -- Integer
Returns:
  • status -- Integer

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:

  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4
  • BrickletIndustrialDualRelay`BOOTLOADERUSTATUSUOK = 0
  • BrickletIndustrialDualRelay`BOOTLOADERUSTATUSUINVALIDUMODE = 1
  • BrickletIndustrialDualRelay`BOOTLOADERUSTATUSUNOUCHANGE = 2
  • BrickletIndustrialDualRelay`BOOTLOADERUSTATUSUENTRYUFUNCTIONUNOTUPRESENT = 3
  • BrickletIndustrialDualRelay`BOOTLOADERUSTATUSUDEVICEUIDENTIFIERUINCORRECT = 4
  • BrickletIndustrialDualRelay`BOOTLOADERUSTATUSUCRCUMISMATCH = 5
BrickletIndustrialDualRelay@GetBootloaderMode[] → mode
Returns:
  • mode -- Integer

Returns the current bootloader mode, see SetBootloaderMode[].

The following constants are available for this function:

  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUBOOTLOADER = 0
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUFIRMWARE = 1
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUBOOTLOADERUWAITUFORUREBOOT = 2
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUFIRMWAREUWAITUFORUREBOOT = 3
  • BrickletIndustrialDualRelay`BOOTLOADERUMODEUFIRMWAREUWAITUFORUERASEUANDUREBOOT = 4
BrickletIndustrialDualRelay@SetWriteFirmwarePointer[pointer] → Null
Parameters:
  • pointer -- Integer

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.

BrickletIndustrialDualRelay@WriteFirmware[{data1, data2, ..., data64}] → status
Parameters:
  • datai -- Integer
Returns:
  • status -- Integer

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.

BrickletIndustrialDualRelay@SetStatusLEDConfig[config] → Null
Parameters:
  • config -- Integer

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:

  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUOFF = 0
  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUON = 1
  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletIndustrialDualRelay@GetStatusLEDConfig[] → config
Returns:
  • config -- Integer

Returns the configuration as set by SetStatusLEDConfig[]

The following constants are available for this function:

  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUOFF = 0
  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUON = 1
  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUSHOWUHEARTBEAT = 2
  • BrickletIndustrialDualRelay`STATUSULEDUCONFIGUSHOWUSTATUS = 3
BrickletIndustrialDualRelay@GetChipTemperature[] → temperature
Returns:
  • temperature -- Integer

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.

BrickletIndustrialDualRelay@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!

BrickletIndustrialDualRelay@WriteUID[uid] → Null
Parameters:
  • uid -- Integer

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.

BrickletIndustrialDualRelay@ReadUID[] → uid
Returns:
  • uid -- Integer

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

BrickletIndustrialDualRelay@GetIdentity[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null
Parameters:
  • uid -- String
  • connectedUid -- String
  • position -- Integer
  • hardwareVersioni -- Integer
  • firmwareVersioni -- Integer
  • deviceIdentifier -- Integer

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:

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

AddEventHandler[industrialDualRelay@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 BrickletIndustrialDualRelay@MonoflopDoneCallback[sender, channel, value]
Parameters:
  • sender -- NETObject[BrickletIndustrialDualRelay]
  • channel -- Integer
  • value -- True/False

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

Constants

BrickletIndustrialDualRelay`DEVICEUIDENTIFIER

This constant is used to identify a Industrial Dual 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.

BrickletIndustrialDualRelay`DEVICEDISPLAYNAME

This constant represents the human readable name of a Industrial Dual Relay Bricklet.