This is the description of the LabVIEW 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 LabVIEW API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Generally, every method of the LabVIEW bindings that outputs a value can report a Tinkerforge.TimeoutException. This error gets reported 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.
The namespace for all Brick/Bricklet bindings and the IPConnection is Tinkerforge.*.
Input: |
|
---|---|
Output: |
|
Creates an object with the unique device ID uid. This object can then be used after the IP Connection is connected (see examples above).
Input: |
|
---|
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.
Current 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 StateChanged 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:
Output: |
|
---|
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:
The following constants are available for this function:
Output: |
|
---|
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.
Possible states are:
The following constants are available for this function:
Input: |
|
---|
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 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:
The following constants are available for this function:
Input: |
|
---|
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:
If you use a Mifare Classic tag you have to authenticate a page before you can write to it. See AuthenticateMifareClassicPage().
Input: |
|
---|
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:
If you use a Mifare Classic tag you have to authenticate a page before you can read it. See AuthenticateMifareClassicPage().
Output: |
|
---|
Returns 16 bytes of data from an internal buffer. To fill the buffer with specific pages you have to call RequestPage() beforehand.
Output: |
|
---|
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.
Input: |
|
---|---|
Output: |
|
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.
Input: |
|
---|
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 and callbacks it is always disabled.
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:
Input: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Output: |
|
---|
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 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. 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.
Input: |
|
---|
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:
This constant is used to identify a NFC/RFID 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.