The JavaScript bindings allow you to control Bricks and Bricklets from your JavaScript scripts. The ZIP file for the bindings contains:
nodejs/tinkerforge.tgz
, a Node.js NPM package (installable with npm tool)nodejs/source/
the source code of tinkerforge.tgz
nodejs/examples/
the Node.js examples for every Brick and Brickletbrowser/source/
the source code of the browser version of the bindingsbrowser/examples/
the HTML examples for every Brick and BrickletIf and how the JavaScript bindings should or have to be installed depends on how they should be used.
There are two ways to install the Node.js version of the bindings: from our APT repository for Debian based Linux distributions or from NPM package. But the bindings can also be used without installing them first.
The bindings are available in our APT repository for Debian based Linux distributions (in this case you don't even need the ZIP file for the bindings). Follow the setup guide then install the bindings:
sudo apt install node-tinkerforge
Now you're ready to test an example. The Debian package does not include the examples. Those are available as part of the bindings ZIP file.
There is a NPM package available for using the Bindings with Node.js. It is available from the Node.js Package Repository and can be installed with the following command:
npm install tinkerforge
Alternatively, the NPM Package is also part of the ZIP file of the bindings. It can be installed from there as well:
npm install nodejs/tinkerforge.tgz
Now you're ready to test an example. The NPM package does not include the examples. Those are available as part of the bindings ZIP file.
You can use the JavaScript bindings for Node.js without having to install them.
Just copy the Tinkerforge/
folder and the Tinkerforge.js
file from the
nodejs/source/
folder in the same folder as your JavaScript script. The
section about testing an example has more details about this.
The browser version of the bindings can be found in the browser/source/
folder. The Tinkerforge.js
file contains the complete bindings. Just copy
this file into the same directory as your HTML file using the bindings. The
section about testing an example has more details about this.
To test a JavaScript example Brick Daemon and Brick Viewer have to be installed first. Brick Daemon acts as a proxy between the USB interface of the Bricks and the API bindings. Brick Viewer connects to Brick Daemon and helps to figure out basic information about the connected Bricks and Bricklets.
As an example let's test the configuration example for the Stepper Brick.
For this copy the ExampleConfiguration.js
file from the
nodejs/examples/Brick/Stepper/
folder into a new folder:
example_project/
-> ExampleConfiguration.js
In the example HOST
and PORT
specify at which network address the
Stepper Brick can be found. If it is connected locally to USB then localhost
and 4223 is correct. The UID
value has to be changed to the UID of the
connected Stepper Brick, which you can figure out using Brick Viewer:
var HOST = 'localhost';
var PORT = 4223;
var UID = 'XXYYZZ'; // Change XXYYZZ to the UID of your Stepper Brick
If you did install the bindings then you're now ready to test this example:
node ExampleConfiguration.js
If you did not install the bindings then you can also use the source of the
bindings directly. Just copy the Tinkerforge/
folder and the
Tinkerforge.js
file from the nodejs/source/
folder to your
example_project/
folder:
example_project/
-> Tinkerforge/
-> Tinkerforge.js
-> ExampleConfiguration.js
Then the require
statement in ExampleConfiguration.js
has to be
modified as follows. Instead of:
var Tinkerforge = require('tinkerforge');
use:
var Tinkerforge = require('./Tinkerforge.js');
Now you're ready to test this example:
node ExampleConfiguration.js
The Browser version of the JavaScript bindings is using WebSockets. WebSockets are supported by Brick Daemon (since version 2.1.0) and the Ethernet Extension (since Master Brick firmware version 2.2.0), but they are disabled by default and need to be configured first:
As an example let's test the configuration example for the Stepper Brick.
For this copy the ExampleConfiguration.html
file from the
browser/examples/Brick/Stepper/
folder and the Tinkerforge.js
file
from the browser/source/
folder into a new folder:
example_project/
-> Tinkerforge.js
-> ExampleConfiguration.html
Now you're ready to open this example in a browser.
The example contains input boxes for host and port information. You have to
specify at which network address the Stepper Brick can be found. If it is
connected locally to USB then localhost
and 4280 is correct. The UID value
has to be changed to the UID of the connected Stepper Brick, which you can
figure out using Brick Viewer. If every<thing is configured correctly you can
start the example the clicking the "Start Example" button.
Links to the API reference for the IP Connection, Bricks and Bricklets as well as the examples from the ZIP file of the bindings are listed in the following table. Further project descriptions can be found in the Kits section.