This is the description of the JavaScript API bindings for the Dual Relay Bricklet. General information and technical specifications for the Dual Relay Bricklet are summarized in its hardware description.
An installation guide for the JavaScript API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
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 26 27 28 29 30 31 32 33 34 35 36 37 | var Tinkerforge = require('tinkerforge');
var HOST = 'localhost';
var PORT = 4223;
var UID = 'XYZ'; // Change XYZ to the UID of your Dual Relay Bricklet
var ipcon = new Tinkerforge.IPConnection(); // Create IP connection
var dr = new Tinkerforge.BrickletDualRelay(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT,
function (error) {
console.log('Error: ' + error);
}
); // Connect to brickd
// Don't use device before ipcon is connected
ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
function (connectReason) {
// Turn relays alternating on/off 10 times with 1 second delay
for(var i = 0; i < 5; ++i) {
setTimeout(function () {
dr.setState(true, false);
}, 2000 * i + 1000);
setTimeout(function () {
dr.setState(false, true);
}, 2000 * i + 2000);
}
}
);
console.log('Press key to exit');
process.stdin.on('data',
function (data) {
ipcon.disconnect();
process.exit(0);
}
);
|
Download (ExampleSimple.html), Test (ExampleSimple.html)
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 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 | <!DOCTYPE html>
<html>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<head>
<title>Tinkerforge | JavaScript Example</title>
</head>
<body>
<div style="text-align:center;">
<h1>Dual Relay Bricklet Simple Example</h1>
<p>
<input value="localhost" id="host" type="text" size="20">:
<input value="4280" id="port" type="text" size="5">,
<input value="uid" id="uid" type="text" size="5">
<input value="Start Example" id="start" type="button" onclick="startExample();">
</p>
<p>
<textarea readonly id="text" cols="80" rows="24" style="resize:none;"
>Press "Start Example" to begin ...</textarea>
</p>
</div>
<script src="./Tinkerforge.js" type='text/javascript'></script>
<script type='text/javascript'>
var ipcon;
var textArea = document.getElementById("text");
function startExample() {
textArea.value = "";
var HOST = document.getElementById("host").value;
var PORT = parseInt(document.getElementById("port").value);
var UID = document.getElementById("uid").value;
if(ipcon !== undefined) {
ipcon.disconnect();
}
ipcon = new Tinkerforge.IPConnection(); // Create IP connection
var dr = new Tinkerforge.BrickletDualRelay(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT,
function(error) {
textArea.value += 'Error: ' + error + '\n';
}
); // Connect to brickd
// Don't use device before ipcon is connected
ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
function (connectReason) {
// Turn relays alternating on/off 10 times with 1 second delay
for(var i = 0; i < 5; ++i) {
setTimeout(function () {
dr.setState(true, false);
}, 2000 * i + 1000);
setTimeout(function () {
dr.setState(false, true);
}, 2000 * i + 2000);
}
}
);
}
</script>
</body>
</html>
|
Generally, every function of the JavaScript bindings can take two optional
parameters, returnCallback
and errorCallback
. These are two user
defined callback functions. The returnCallback
function is called with the
results as arguments, if the function returns its results asynchronously. The
errorCallback
is called with an error code in case of an error. The error
code can be one of the following values:
The namespace for the JavaScript bindings is Tinkerforge.*
.
BrickletDualRelay
(uid, ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
var dualRelay = new BrickletDualRelay("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletDualRelay.
setState
(relay1, relay2[, returnCallback][, errorCallback])¶Parameters: |
|
---|---|
Callback Parameters: |
|
Returns: |
|
Sets the state of the relays, true means on and false means off. For example: (true, false) turns relay 1 on and relay 2 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 getState()
or you
can use setSelectedState()
.
All running monoflop timers will be aborted if this function is called.
BrickletDualRelay.
getState
([returnCallback][, errorCallback])¶Callback Parameters: |
|
---|---|
Returns: |
|
Returns the state of the relays, true means on and false means off.
BrickletDualRelay.
setMonoflop
(relay, state, time[, returnCallback][, errorCallback])¶Parameters: |
|
---|---|
Callback Parameters: |
|
Returns: |
|
The first parameter can be 1 or 2 (relay 1 or relay 2). The second parameter is the desired state of the relay (true means on and false means off). The third parameter indicates the time 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 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.
BrickletDualRelay.
getMonoflop
(relay[, returnCallback][, errorCallback])¶Parameters: |
|
---|---|
Callback Parameters: |
|
Returns: |
|
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.
BrickletDualRelay.
setSelectedState
(relay, state[, returnCallback][, errorCallback])¶Parameters: |
|
---|---|
Callback Parameters: |
|
Returns: |
|
Sets the state of the selected relay (1 or 2), true means on and false means off.
A running monoflop timer for the selected relay will be aborted if this function is called.
The other relay remains untouched.
BrickletDualRelay.
getIdentity
([returnCallback][, errorCallback])¶Callback Parameters: |
|
---|---|
Returns: |
|
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 can be registered to receive
time critical or recurring data from the device. The registration is done
with the on()
function of
the device object. The first parameter is the callback ID and the second
parameter the callback function:
dualRelay.on(BrickletDualRelay.CALLBACK_EXAMPLE,
function (param) {
console.log(param);
}
);
The available constants with inherent number and 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.
BrickletDualRelay.
CALLBACK_MONOFLOP_DONE
¶Callback Parameters: |
|
---|
This callback is triggered whenever a monoflop timer reaches 0. The parameter contain the relay (1 or 2) and the current state of the relay (the state after the monoflop).
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.
BrickletDualRelay.
getAPIVersion
()¶Returns: |
|
---|
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.
BrickletDualRelay.
getResponseExpected
(functionId[, errorCallback])¶Parameters: |
|
---|---|
Returns: |
|
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 function_id:
BrickletDualRelay.
setResponseExpected
(functionId, responseExpected[, errorCallback])¶Parameters: |
|
---|---|
Returns: |
|
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 function_id:
BrickletDualRelay.
setResponseExpectedAll
(responseExpected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletDualRelay.
DEVICE_IDENTIFIER
¶This constant is used to identify a Dual Relay Bricklet.
The getIdentity()
function and the
IPConnection.CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletDualRelay.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Dual Relay Bricklet.