This is the description of the Mathematica 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 Mathematica API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (ExampleScanForTags.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 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 | Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]
host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your NFC/RFID Bricklet*)
(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
nr=NETNew["Tinkerforge.BrickletNFCRFID",uid,ipcon]
ipcon@Connect[host,port]
currentTageType=Tinkerforge`BrickletNFCRFID`TAGUTYPEUMIFAREUCLASSIC
(*Callback function for state changed callback*)
StateChangedCB[sender_,state_,idle_]:=
Module[{},
If[state==Tinkerforge`BrickletNFCRFID`STATEUREQUESTUTAGUIDUREADY,
tagType=0;tidLength=0;tid={};
sender@GetTagID[tagType,tidLength,tid];
result={ToString[tid[[1]]]};
For[i=2,i<=tidLength,++i,
AppendTo[result," "<>ToString[tid[[i]]]]
];
Print["Found tag of type "<>ToString[tagType]<>" with ID ["<>StringJoin[result]<>"]"]
];
(*Cycle through all types*)
If[idle,
currentTageType=Mod[currentTageType+1,3];
sender@RequestTagID[currentTageType]
]
]
AddEventHandler[nr@StateChangedCallback,StateChangedCB]
(*Start scan loop*)
nr@RequestTagID[Tinkerforge`BrickletNFCRFID`TAGUTYPEUMIFAREUCLASSIC]
Input["Click OK to exit"]
(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[nr]
ReleaseNETObject[ipcon]
|
Download (ExampleWriteReadType2.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 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 | Needs["NETLink`"]
LoadNETAssembly["Tinkerforge",NotebookDirectory[]<>"../../.."]
host="localhost"
port=4223
uid="XYZ"(*Change XYZ to the UID of your NFC/RFID Bricklet*)
(*Create IPConnection and device object*)
ipcon=NETNew["Tinkerforge.IPConnection"]
nr=NETNew["Tinkerforge.BrickletNFCRFID",uid,ipcon]
ipcon@Connect[host,port]
(*Callback function for state changed callback*)
StateChangedCB[sender_,state_,idle_]:=
Module[{},
If[state==Tinkerforge`BrickletNFCRFID`STATEUREQUESTUTAGUIDUREADY,
Print["Tag found"];
(* Write 16 byte to pages 5-8 *)
dataWrite={0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15};
sender@WritePage[5,dataWrite];
Print["Writing data..."];
];
If[state==Tinkerforge`BrickletNFCRFID`STATEUWRITEUPAGEUREADY,
(* Request pages 5-8 *)
sender@RequestPage[5];
Print["Requesting data..."];
];
If[state==Tinkerforge`BrickletNFCRFID`STATEUREQUESTUPAGEUREADY,
(* Get and print pages 5-8 *)
dataRead=sender@GetPage[];
result={ToString[dataRead[[1]]]};
For[i=2,i<=16,++i,AppendTo[result," "<>ToString[dataRead[[i]]]]];
Print["Read data: ["<>StringJoin[result]<>"]"]
];
If[IntegerDigits[state,2,8][[2]]==1,
(* All errors have bit 6 set *)
Print["Error: "<>ToString[state]]
]
]
AddEventHandler[nr@StateChangedCallback,StateChangedCB]
(*Select NFC Forum Type 2 tag*)
nr@RequestTagID[Tinkerforge`BrickletNFCRFID`TAGUTYPEUTYPE2]
Input["Click OK to exit"]
(*Clean up*)
ipcon@Disconnect[]
ReleaseNETObject[nr]
ReleaseNETObject[ipcon]
|
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.*
.
BrickletNFCRFID
[uid, ipcon] → nfcRFID¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
nfcRFID=NETNew["Tinkerforge.BrickletNFCRFID","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.
BrickletNFCRFID
@
RequestTagID
[tagType] → Null¶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:
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
@
GetTagID
[out tagType, out tidLength, out {tid1, tid2, ..., tid7}] → Null¶Output Parameters: |
|
---|
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:
RequestTagID[]
GetState[]
or
StateChangedCallback
callback)GetTagID[]
The following constants are available for this function:
For tagType:
BrickletNFCRFID
@
GetState
[out state, out idle] → Null¶Output Parameters: |
|
---|
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
@
AuthenticateMifareClassicPage
[page, keyNumber, {key1, key2, ..., key6}] → Null¶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:
RequestTagID[]
GetState[]
or StateChangedCallback
callback)GetTagID[]
and check if the
expected tag was found, if it was not found go back to step 1AuthenticateMifareClassicPage[]
with page and key for the pageGetState[]
or StateChangedCallback
callback)RequestPage[]
or WritePage[]
to read/write pageThe following constants are available for this function:
For keyNumber:
BrickletNFCRFID
@
WritePage
[page, {data1, data2, ..., data16}] → Null¶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:
The general approach for writing to a tag is as follows:
RequestTagID[]
GetState[]
or
StateChangedCallback
callback)GetTagID[]
and check if the
expected tag was found, if it was not found got back to step 1WritePage[]
with page number and dataGetState[]
or
StateChangedCallback
callback)If you use a Mifare Classic tag you have to authenticate a page before you
can write to it. See AuthenticateMifareClassicPage[]
.
BrickletNFCRFID
@
RequestPage
[page] → Null¶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:
The general approach for reading a tag is as follows:
RequestTagID[]
GetState[]
or StateChangedCallback
callback)GetTagID[]
and check if the
expected tag was found, if it was not found got back to step 1RequestPage[]
with page numberGetState[]
or StateChangedCallback
callback)GetPage[]
to retrieve the page from the bufferIf you use a Mifare Classic tag you have to authenticate a page before you
can read it. See AuthenticateMifareClassicPage[]
.
BrickletNFCRFID
@
GetPage
[] → {data1, data2, ..., data16}¶Returns: |
|
---|
Returns 16 bytes of data from an internal buffer. To fill the buffer
with specific pages you have to call RequestPage[]
beforehand.
BrickletNFCRFID
@
GetIdentity
[out uid, out connectedUid, out position, out {hardwareVersion1, hardwareVersion2, hardwareVersion3}, out {firmwareVersion1, firmwareVersion2, firmwareVersion3}, out deviceIdentifier] → Null¶Output Parameters: |
|
---|
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 by assigning a function to a callback property of the device object:
MyCallback[sender_,value_]:=Print["Value: "<>ToString[value]] AddEventHandler[nfcRFID@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.
BrickletNFCRFID
@
StateChangedCallback
[sender, state, idle]¶Callback Parameters: |
|
---|
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:
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.
BrickletNFCRFID
@
GetAPIVersion
[] → {apiVersion1, apiVersion2, apiVersion3}¶Output Parameters: |
|
---|
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.
BrickletNFCRFID
@
GetResponseExpected
[functionId] → responseExpected¶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
@
SetResponseExpected
[functionId, responseExpected] → Null¶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
@
SetResponseExpectedAll
[responseExpected] → Null¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletNFCRFID
`
DEVICEUIDENTIFIER
¶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.
BrickletNFCRFID
`
DEVICEDISPLAYNAME
¶This constant represents the human readable name of a NFC/RFID Bricklet.