This is the description of the MATLAB/Octave API bindings for the NFC/RFID Bricklet. General information and technical specifications for the NFC/RFID Bricklet are summarized in its hardware description.
An installation guide for the MATLAB/Octave API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (matlab_example_write_read_type2.m)
1function matlab_example_write_read_type2()
2 global nr;
3
4 import com.tinkerforge.IPConnection;
5 import com.tinkerforge.BrickletNFCRFID;
6
7 HOST = 'localhost';
8 PORT = 4223;
9 UID = 'XYZ'; % Change XYZ to the UID of your NFC/RFID Bricklet
10
11 ipcon = IPConnection(); % Create IP connection
12 nr = handle(BrickletNFCRFID(UID, ipcon), 'CallbackProperties'); % Create device object
13
14 ipcon.connect(HOST, PORT); % Connect to brickd
15 % Don't use device before ipcon is connected
16
17 % Register state changed callback to function cb_state_changed
18 set(nr, 'StateChangedCallback', @(h, e) cb_state_changed(e));
19
20 % Select NFC Forum Type 2 tag
21 nr.requestTagID(BrickletNFCRFID.TAG_TYPE_TYPE2);
22
23 input('Press key to exit\n', 's');
24 ipcon.disconnect();
25end
26
27% Callback function for state changed callback
28function cb_state_changed(e)
29 global nr;
30
31 if e.state == nr.STATE_REQUEST_TAG_ID_READY
32 fprintf('Tag found\n');
33
34 % Write 16 byte to pages 5-8
35 data_write = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15];
36 nr.writePage(5, data_write);
37 fprintf('Writing data...\n');
38 elseif e.state == nr.STATE_WRITE_PAGE_READY
39 % Request pages 5-8
40 nr.requestPage(5);
41 fprintf('Requesting data...\n');
42 elseif e.state == nr.STATE_REQUEST_PAGE_READY
43 % Get and print pages
44 data = nr.getPage();
45 fprintf('Read data: [%d]\n', data);
46 elseif (bitand(e.state, 64) == 64)
47 % All errors have bit 6 set
48 fprintf('Error: %d\n', e.state);
49 end
50end
Download (octave_example_write_read_type2.m)
1function octave_example_write_read_type2()
2 more off;
3
4 global nr;
5
6 HOST = "localhost";
7 PORT = 4223;
8 UID = "XYZ"; % Change XYZ to the UID of your NFC/RFID Bricklet
9
10 ipcon = javaObject("com.tinkerforge.IPConnection"); % Create IP connection
11 nr = javaObject("com.tinkerforge.BrickletNFCRFID", UID, ipcon); % Create device object
12
13 ipcon.connect(HOST, PORT); % Connect to brickd
14 % Don't use device before ipcon is connected
15
16 % Register state changed callback to function cb_state_changed
17 nr.addStateChangedCallback(@cb_state_changed);
18
19 % Select NFC Forum Type 2 tag
20 nr.requestTagID(nr.TAG_TYPE_TYPE2);
21
22 input("Press key to exit\n", "s");
23 ipcon.disconnect();
24end
25
26% Callback function for state changed callback
27function cb_state_changed(e)
28 global nr;
29
30 if java2int(e.state) == java2int(nr.STATE_REQUEST_TAG_ID_READY)
31 fprintf("Tag found\n");
32
33 % Write 16 byte to pages 5-8
34 data_write = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15];
35 nr.writePage(5, data_write);
36 fprintf("Writing data...\n");
37 elseif java2int(e.state) == java2int(nr.STATE_WRITE_PAGE_READY)
38 % Request pages 5-8
39 nr.requestPage(5);
40 fprintf("Requesting data...\n");
41 elseif java2int(e.state) == java2int(nr.STATE_REQUEST_PAGE_READY)
42 % Get and print pages
43 data = nr.getPage();
44 fprintf("Read data: [%d %d %d %d %d %d %d %d %d %d %d %d %d %d %d %d]\n",
45 java2int(data(1)), java2int(data(2)), java2int(data(3)), java2int(data(4)),
46 java2int(data(5)), java2int(data(6)), java2int(data(7)), java2int(data(8)),
47 java2int(data(9)), java2int(data(10)), java2int(data(11)), java2int(data(12)),
48 java2int(data(13)), java2int(data(14)), java2int(data(15)), java2int(data(16)));
49 elseif (bitand(java2int(e.state), 64) == 64)
50 % All errors have bit 6 set
51 fprintf("Error: %d\n", java2int(e.state));
52 end
53end
54
55function int = java2int(value)
56 if compare_versions(version(), "3.8", "<=")
57 int = value.intValue();
58 else
59 int = value;
60 end
61end
Generally, every method of the MATLAB bindings that returns a value can
throw a 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 unplugs the
device). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Beside the TimeoutException there is also a NotConnectedException that
is thrown if a method needs to communicate with the device while the
IP Connection is not connected.
Since the MATLAB bindings are based on Java and Java does not support multiple return values and return by reference is not possible for primitive types, we use small classes that only consist of member variables. The member variables of the returned objects are described in the corresponding method descriptions.
The package for all Brick/Bricklet bindings and the IP Connection is
com.tinkerforge.*
All methods listed below are thread-safe.
| Parameters: |
|
|---|---|
| Returns: |
|
Creates an object with the unique device ID uid.
In MATLAB:
import com.tinkerforge.BrickletNFCRFID;
nfcRFID = BrickletNFCRFID('YOUR_DEVICE_UID', ipcon);
In Octave:
nfcRFID = java_new("com.tinkerforge.BrickletNFCRFID", "YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
| Parameters: |
|
|---|
To read or write a tag that is in proximity of the NFC/RFID Bricklet you first have to call this function with the expected tag type as parameter. It is no problem if you don’t know the tag type. You can cycle through the available tag types until the tag gives an answer to the request.
Currently the following tag types are supported:
Mifare Classic
NFC Forum Type 1
NFC Forum Type 2
After you call requestTagID() the NFC/RFID Bricklet will try to read
the tag ID from the tag. After this process is done the state will change.
You can either register the StateChangedCallback callback or you can poll
getState() to find out about the state change.
If the state changes to RequestTagIDError it means that either there was
no tag present or that the tag is of an incompatible type. If the state
changes to RequestTagIDReady it means that a compatible tag was found
and that the tag ID could be read out. You can now get the tag ID by
calling getTagID().
If two tags are in the proximity of the NFC/RFID Bricklet, this
function will cycle through the tags. To select a specific tag you have
to call requestTagID() until the correct tag id is found.
In case of any Error state the selection is lost and you have to
start again by calling requestTagID().
The following constants are available for this function:
For tagType:
BrickletNFCRFID.TAG_TYPE_MIFARE_CLASSIC = 0
BrickletNFCRFID.TAG_TYPE_TYPE1 = 1
BrickletNFCRFID.TAG_TYPE_TYPE2 = 2
| Return Object: |
|
|---|
Returns the tag type, tag ID and the length of the tag ID
(4 or 7 bytes are possible length). This function can only be called if the
NFC/RFID is currently in one of the Ready states. The returned ID
is the ID that was saved through the last call of requestTagID().
To get the tag ID of a tag the approach is as follows:
Call requestTagID()
Wait for state to change to RequestTagIDReady (see getState() or
StateChangedCallback callback)
Call getTagID()
The following constants are available for this function:
For tagType:
BrickletNFCRFID.TAG_TYPE_MIFARE_CLASSIC = 0
BrickletNFCRFID.TAG_TYPE_TYPE1 = 1
BrickletNFCRFID.TAG_TYPE_TYPE2 = 2
| Return Object: |
|
|---|
Returns the current state of the NFC/RFID Bricklet.
On startup the Bricklet will be in the Initialization state. The initialization will only take about 20ms. After that it changes to Idle.
The functions of this Bricklet can be called in the Idle state and all of the Ready and Error states.
Example: If you call requestPage(), the state will change to
RequestPage until the reading of the page is finished. Then it will change
to either RequestPageReady if it worked or to RequestPageError if it
didn’t. If the request worked you can get the page by calling getPage().
The same approach is used analogously for the other API functions.
The following constants are available for this function:
For state:
BrickletNFCRFID.STATE_INITIALIZATION = 0
BrickletNFCRFID.STATE_IDLE = 128
BrickletNFCRFID.STATE_ERROR = 192
BrickletNFCRFID.STATE_REQUEST_TAG_ID = 2
BrickletNFCRFID.STATE_REQUEST_TAG_ID_READY = 130
BrickletNFCRFID.STATE_REQUEST_TAG_ID_ERROR = 194
BrickletNFCRFID.STATE_AUTHENTICATING_MIFARE_CLASSIC_PAGE = 3
BrickletNFCRFID.STATE_AUTHENTICATING_MIFARE_CLASSIC_PAGE_READY = 131
BrickletNFCRFID.STATE_AUTHENTICATING_MIFARE_CLASSIC_PAGE_ERROR = 195
BrickletNFCRFID.STATE_WRITE_PAGE = 4
BrickletNFCRFID.STATE_WRITE_PAGE_READY = 132
BrickletNFCRFID.STATE_WRITE_PAGE_ERROR = 196
BrickletNFCRFID.STATE_REQUEST_PAGE = 5
BrickletNFCRFID.STATE_REQUEST_PAGE_READY = 133
BrickletNFCRFID.STATE_REQUEST_PAGE_ERROR = 197
| Parameters: |
|
|---|
Mifare Classic tags use authentication. If you want to read from or write to
a Mifare Classic page you have to authenticate it beforehand.
Each page can be authenticated with two keys: A (key_number = 0) and B
(key_number = 1). A new Mifare Classic
tag that has not yet been written to can be accessed with key A
and the default key [0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF].
The approach to read or write a Mifare Classic page is as follows:
Call requestTagID()
Wait for state to change to RequestTagIDReady (see getState()
or StateChangedCallback callback)
If looking for a specific tag then call getTagID() and check if the
expected tag was found, if it was not found go back to step 1
Call authenticateMifareClassicPage() with page and key for the page
Wait for state to change to AuthenticatingMifareClassicPageReady (see
getState() or StateChangedCallback callback)
Call requestPage() or writePage() to read/write page
The following constants are available for this function:
For keyNumber:
BrickletNFCRFID.KEY_A = 0
BrickletNFCRFID.KEY_B = 1
| Parameters: |
|
|---|
Writes 16 bytes starting from the given page. How many pages are written depends on the tag type. The page sizes are as follows:
Mifare Classic page size: 16 byte (one page is written)
NFC Forum Type 1 page size: 8 byte (two pages are written)
NFC Forum Type 2 page size: 4 byte (four pages are written)
The general approach for writing to a tag is as follows:
Call requestTagID()
Wait for state to change to RequestTagIDReady (see getState() or
StateChangedCallback callback)
If looking for a specific tag then call getTagID() and check if the
expected tag was found, if it was not found got back to step 1
Call writePage() with page number and data
Wait for state to change to WritePageReady (see getState() or
StateChangedCallback callback)
If you use a Mifare Classic tag you have to authenticate a page before you
can write to it. See authenticateMifareClassicPage().
| Parameters: |
|
|---|
Reads 16 bytes starting from the given page and stores them into a buffer.
The buffer can then be read out with getPage().
How many pages are read depends on the tag type. The page sizes are
as follows:
Mifare Classic page size: 16 byte (one page is read)
NFC Forum Type 1 page size: 8 byte (two pages are read)
NFC Forum Type 2 page size: 4 byte (four pages are read)
The general approach for reading a tag is as follows:
Call requestTagID()
Wait for state to change to RequestTagIDReady (see getState()
or StateChangedCallback callback)
If looking for a specific tag then call getTagID() and check if the
expected tag was found, if it was not found got back to step 1
Call requestPage() with page number
Wait for state to change to RequestPageReady (see getState()
or StateChangedCallback callback)
Call getPage() to retrieve the page from the buffer
If you use a Mifare Classic tag you have to authenticate a page before you
can read it. See authenticateMifareClassicPage().
| Returns: |
|
|---|
Returns 16 bytes of data from an internal buffer. To fill the buffer
with specific pages you have to call requestPage() beforehand.
| Return Object: |
|
|---|
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 “set” function of MATLAB. The parameters consist of the IP Connection object, the callback name and the callback function. For example, it looks like this in MATLAB:
function my_callback(e)
fprintf('Parameter: %s\n', e.param);
end
set(device, 'ExampleCallback', @(h, e) my_callback(e));
Due to a difference in the Octave Java support the “set” function cannot be used in Octave. The registration is done with “add*Callback” functions of the device object. It looks like this in Octave:
function my_callback(e)
fprintf("Parameter: %s\n", e.param);
end
device.addExampleCallback(@my_callback);
It is possible to add several callbacks and to remove them with the corresponding “remove*Callback” function.
The parameters of the callback are passed to the callback function as fields of
the structure e, which is derived from the java.util.EventObject class.
The available callback names with corresponding structure fields 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 Object: |
|
|---|
This callback is called if the state of the NFC/RFID Bricklet changes.
See getState() for more information about the possible states.
The following constants are available for this function:
For state:
BrickletNFCRFID.STATE_INITIALIZATION = 0
BrickletNFCRFID.STATE_IDLE = 128
BrickletNFCRFID.STATE_ERROR = 192
BrickletNFCRFID.STATE_REQUEST_TAG_ID = 2
BrickletNFCRFID.STATE_REQUEST_TAG_ID_READY = 130
BrickletNFCRFID.STATE_REQUEST_TAG_ID_ERROR = 194
BrickletNFCRFID.STATE_AUTHENTICATING_MIFARE_CLASSIC_PAGE = 3
BrickletNFCRFID.STATE_AUTHENTICATING_MIFARE_CLASSIC_PAGE_READY = 131
BrickletNFCRFID.STATE_AUTHENTICATING_MIFARE_CLASSIC_PAGE_ERROR = 195
BrickletNFCRFID.STATE_WRITE_PAGE = 4
BrickletNFCRFID.STATE_WRITE_PAGE_READY = 132
BrickletNFCRFID.STATE_WRITE_PAGE_ERROR = 196
BrickletNFCRFID.STATE_REQUEST_PAGE = 5
BrickletNFCRFID.STATE_REQUEST_PAGE_READY = 133
BrickletNFCRFID.STATE_REQUEST_PAGE_ERROR = 197
In MATLAB the set() function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addStateChangedCallback() function. An added callback function can be removed with
the removeStateChangedCallback() function.
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.
| Return Object: |
|
|---|
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.
| 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 functionId:
BrickletNFCRFID.FUNCTION_REQUEST_TAG_ID = 1
BrickletNFCRFID.FUNCTION_AUTHENTICATE_MIFARE_CLASSIC_PAGE = 4
BrickletNFCRFID.FUNCTION_WRITE_PAGE = 5
BrickletNFCRFID.FUNCTION_REQUEST_PAGE = 6
| Parameters: |
|
|---|
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:
BrickletNFCRFID.FUNCTION_REQUEST_TAG_ID = 1
BrickletNFCRFID.FUNCTION_AUTHENTICATE_MIFARE_CLASSIC_PAGE = 4
BrickletNFCRFID.FUNCTION_WRITE_PAGE = 5
BrickletNFCRFID.FUNCTION_REQUEST_PAGE = 6
| Parameters: |
|
|---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
This constant is used to identify a NFC/RFID 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.
This constant represents the human readable name of a NFC/RFID Bricklet.