This is the description of the Visual Basic .NET API bindings for the NFC Bricklet. General information and technical specifications for the NFC Bricklet are summarized in its hardware description.
An installation guide for the Visual Basic .NET API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (ExampleEmulateNDEF.vb)
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 | Imports System
Imports Tinkerforge
Module ExampleEmulateNDEF
Const HOST As String = "localhost"
Const PORT As Integer = 4223
Const UID As String = "XYZ" ' Change XYZ to the UID of your NFC Bricklet
Const NDEF_URI As String = "www.tinkerforge.com"
' Callback subroutine for cardemu state changed callback
Sub CardemuStateChangedCB(ByVal sender As BrickletNFC, ByVal state As Byte, _
ByVal idle As Boolean)
If state = BrickletNFC.CARDEMU_STATE_IDLE Then
Dim i As Integer
Dim ndefURIBytes As Byte() = Text.Encoding.ASCII.GetBytes(NDEF_URI)
Dim ndefRecordURI(ndefURIBytes.Length + 5) As Byte
ndefRecordURI(0) = &HD1
ndefRecordURI(1) = &H01
ndefRecordURI(2) = Convert.ToByte(ndefURIBytes.Length + 1)
ndefRecordURI(3) = Text.Encoding.ASCII.GetBytes("U")(1)
ndefRecordURI(4) = &H04
' Only short records are supported
For i = 0 To ndefURIBytes.Length - 1
ndefRecordURI(5 + i) = ndefURIBytes(i)
Next
sender.CardemuWriteNDEF(ndefRecordURI)
sender.CardemuStartDiscovery()
ElseIf state = BrickletNFC.CARDEMU_STATE_DISCOVER_READY Then
sender.CardemuStartTransfer(BrickletNFC.CARDEMU_TRANSFER_WRITE)
ElseIf state = BrickletNFC.CARDEMU_STATE_DISCOVER_ERROR Then
Console.WriteLine("Discover error")
ElseIf state = BrickletNFC.CARDEMU_STATE_TRANSFER_NDEF_ERROR Then
Console.WriteLine("Transfer NDEF error")
End If
End Sub
Sub Main()
Dim ipcon As New IPConnection() ' Create IP connection
Dim nfc As New BrickletNFC(UID, ipcon) ' Create device object
ipcon.Connect(HOST, PORT) ' Connect to brickd
' Don't use device before ipcon is connected
' Register cardemu state changed callback to subroutine CardemuStateChangedCB
AddHandler nfc.CardemuStateChangedCallback, AddressOf CardemuStateChangedCB
' Enable cardemu mode
nfc.SetMode(BrickletNFC.MODE_CARDEMU)
Console.WriteLine("Press key to exit")
Console.ReadLine()
ipcon.Disconnect()
End Sub
End Module
|
Download (ExampleScanForTags.vb)
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 | Imports System
Imports Tinkerforge
Module ExampleScanForTags
Const HOST As String = "localhost"
Const PORT As Integer = 4223
Const UID As String = "XYZ" ' Change XYZ to the UID of your NFC Bricklet
' Callback subroutine for reader state changed callback
Sub ReaderStateChangedCB(ByVal sender As BrickletNFC, ByVal state As Byte, _
ByVal idle As Boolean)
If state = BrickletNFC.READER_STATE_REQUEST_TAG_ID_READY Then
Dim i As Integer
Dim tagType As Byte
Dim tagID() As Byte
Dim tagInfo As String
sender.ReaderGetTagID(tagType, tagID)
tagInfo = String.Format("Found tag of type {0} with ID [", tagType)
For i = 0 To tagID.Length - 1
tagInfo += String.Format("0x{0:X2}", tagID(i))
If i < tagID.Length - 1 Then
tagInfo += " "
End If
Next
tagInfo += "]"
Console.WriteLine(tagInfo)
End If
If idle Then
sender.ReaderRequestTagID()
End If
End Sub
Sub Main()
Dim ipcon As New IPConnection() ' Create IP connection
Dim nfc As New BrickletNFC(UID, ipcon) ' Create device object
ipcon.Connect(HOST, PORT) ' Connect to brickd
' Don't use device before ipcon is connected
' Register reader state changed callback to subroutine ReaderStateChangedCB
AddHandler nfc.ReaderStateChangedCallback, AddressOf ReaderStateChangedCB
' Enable reader mode
nfc.SetMode(BrickletNFC.MODE_READER)
Console.WriteLine("Press key to exit")
Console.ReadLine()
ipcon.Disconnect()
End Sub
End Module
|
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 59 60 61 62 63 64 65 66 67 68 69 70 71 | Imports System
Imports System.Threading
Imports Tinkerforge
Module ExampleSimple
Const HOST As String = "localhost"
Const PORT As Integer = 4223
Const UID As String = "XYZ" ' Change XYZ to the UID of your NFC Bricklet
Sub Main()
Dim ipcon As New IPConnection() ' Create IP connection
Dim nfc As New BrickletNFC(UID, ipcon) ' Create device object
ipcon.Connect(HOST, PORT) ' Connect to brickd
' Don't use device before ipcon is connected
' Enable simple mode
nfc.SetMode(BrickletNFC.MODE_SIMPLE)
' Get current tag IDs 10 times
Dim cycle As Integer
Dim index As Byte
Dim tagType As Byte
Dim tagID As Byte()
Dim lastSeen As Long
Dim tagInfo As String
Dim i As Integer
For cycle = 1 To 10
Console.WriteLine("Cycle: " + cycle.ToString() + " of 10")
For index = 0 To 7
Try
nfc.SimpleGetTagID(index, tagType, tagID, lastSeen)
Catch
' On error enable simple mode again
nfc.SetMode(BrickletNFC.MODE_SIMPLE)
Continue For
End Try
If tagID.Length = 0 Then
Exit For
End If
tagInfo = "["
For i = 0 To tagID.Length - 1
tagInfo += String.Format("0x{0:X2}", tagID(i))
If i < tagID.Length - 1 Then
tagInfo += " "
End If
Next
tagInfo += "]"
Console.WriteLine(" Index: " + index.ToString() + _
", Tag Type: " + tagType.ToString() + _
", Tag ID: " + tagInfo + _
", Last Seen: " + (lastSeen / 1000.0).ToString() + " seconds ago")
Next index
Console.WriteLine("")
Thread.Sleep(1000)
Next cycle
Console.WriteLine("Press key to exit")
Console.ReadLine()
ipcon.Disconnect()
End Sub
End Module
|
Download (ExampleWriteReadType2.vb)
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 59 60 61 62 63 64 65 66 67 68 69 70 71 | Imports System
Imports Tinkerforge
Module ExampleWriteReadType2
Const HOST As String = "localhost"
Const PORT As Integer = 4223
Const UID As String = "XYZ" ' Change XYZ to the UID of your NFC Bricklet
' Callback subroutine for reader state changed callback
Sub ReaderStateChangedCB(ByVal sender As BrickletNFC, ByVal state As Byte, _
ByVal idle As Boolean)
If state = BrickletNFC.READER_STATE_IDLE Then
sender.ReaderRequestTagID()
ElseIf(state = BrickletNFC.READER_STATE_REQUEST_TAG_ID_READY) Then
Dim tagType As Byte
Dim tagID() As Byte
sender.ReaderGetTagID(tagType, tagID)
If tagType <> BrickletNFC.TAG_TYPE_TYPE2 Then
Console.WriteLine("Tag is not type-2")
return
End If
Console.WriteLine("Found tag of type {0} with ID [0x{1:X} 0x{2:X} 0x{3:X} 0x{4:X}]", _
tagType, _
tagID(0), _
tagID(1), _
tagID(2), _
tagID(3))
sender.ReaderRequestPage(1, 4)
ElseIf state = BrickletNFC.READER_STATE_REQUEST_TAG_ID_ERROR Then
Console.WriteLine("Request tag ID error")
ElseIf state = BrickletNFC.READER_STATE_REQUEST_PAGE_READY Then
Dim page() As Byte
page = sender.ReaderReadPage()
Console.WriteLine("Page read: 0x{0:X} 0x{1:X} 0x{2:X} 0x{3:X}",
page(0),
page(1),
page(2),
page(3))
sender.ReaderWritePage(1, page)
ElseIf state = BrickletNFC.READER_STATE_WRITE_PAGE_READY Then
Console.WriteLine("Write page ready")
ElseIf state = BrickletNFC.READER_STATE_REQUEST_PAGE_ERROR Then
Console.WriteLine("Request page error")
ElseIf state = BrickletNFC.READER_STATE_WRITE_PAGE_ERROR Then
Console.WriteLine("Write page error")
End If
End Sub
Sub Main()
Dim ipcon As New IPConnection() ' Create IP connection
Dim nfc As New BrickletNFC(UID, ipcon) ' Create device object
ipcon.Connect(HOST, PORT) ' Connect to brickd
' Don't use device before ipcon is connected
' Register reader state changed callback to subroutine ReaderStateChangedCB
AddHandler nfc.ReaderStateChangedCallback, AddressOf ReaderStateChangedCB
' Enable reader mode
nfc.SetMode(BrickletNFC.MODE_READER)
Console.WriteLine("Press key to exit")
Console.ReadLine()
ipcon.Disconnect()
End Sub
End Module
|
Since Visual Basic .NET does not support multiple return values directly, we
use the ByRef
keyword to return multiple values from a function.
All functions and procedures listed below are thread-safe.
BrickletNFC
(ByVal uid As String, ByVal ipcon As IPConnection)¶Creates an object with the unique device ID uid
:
Dim nfc As New BrickletNFC("YOUR_DEVICE_UID", ipcon)
This object can then be used after the IP Connection is connected.
BrickletNFC.
SetMode
(ByVal mode As Byte)¶Parameters: |
|
---|
Sets the mode. The NFC Bricklet supports four modes:
If you change a mode, the Bricklet will reconfigure the hardware for this mode. Therefore, you can only use functions corresponding to the current mode. For example, in Reader mode you can only use Reader functions.
The following constants are available for this function:
For mode:
BrickletNFC.
GetMode
() As Byte¶Returns: |
|
---|
Returns the mode as set by SetMode()
.
The following constants are available for this function:
For mode:
BrickletNFC.
ReaderRequestTagID
()¶After you call ReaderRequestTagID()
the NFC 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 ReaderStateChangedCallback
callback or you can poll
ReaderGetState()
to find out about the state change.
If the state changes to ReaderRequestTagIDError it means that either there was
no tag present or that the tag has an incompatible type. If the state
changes to ReaderRequestTagIDReady it means that a compatible tag was found
and that the tag ID has been saved. You can now read out the tag ID by
calling ReaderGetTagID()
.
If two tags are in the proximity of the NFC Bricklet, this
function will cycle through the tags. To select a specific tag you have
to call ReaderRequestTagID()
until the correct tag ID is found.
In case of any ReaderError state the selection is lost and you have to
start again by calling ReaderRequestTagID()
.
BrickletNFC.
ReaderGetTagID
(ByRef tagType As Byte, ByRef tagID() As Byte)¶Output Parameters: |
|
---|
Returns the tag type and the tag ID. This function can only be called if the
NFC Bricklet is currently in one of the ReaderReady states. The returned tag ID
is the tag ID that was saved through the last call of ReaderRequestTagID()
.
To get the tag ID of a tag the approach is as follows:
ReaderRequestTagID()
ReaderGetState()
or
ReaderStateChangedCallback
callback)ReaderGetTagID()
The following constants are available for this function:
For tagType:
BrickletNFC.
ReaderGetState
(ByRef state As Byte, ByRef idle As Boolean)¶Output Parameters: |
|
---|
Returns the current reader state of the NFC Bricklet.
On startup the Bricklet will be in the ReaderInitialization state. The initialization will only take about 20ms. After that it changes to ReaderIdle.
The Bricklet is also reinitialized if the mode is changed, see SetMode()
.
The functions of this Bricklet can be called in the ReaderIdle state and all of the ReaderReady and ReaderError states.
Example: If you call ReaderRequestPage()
, the state will change to
ReaderRequestPage until the reading of the page is finished. Then it will change
to either ReaderRequestPageReady if it worked or to ReaderRequestPageError if it
didn't. If the request worked you can get the page by calling ReaderReadPage()
.
The same approach is used analogously for the other API functions.
The following constants are available for this function:
For state:
BrickletNFC.
ReaderWriteNDEF
(ByVal ndef() As Byte)¶Parameters: |
|
---|
Writes NDEF formated data.
This function currently supports NFC Forum Type 2, 4, 5 and Mifare Classic.
The general approach for writing a NDEF message is as follows:
ReaderRequestTagID()
ReaderGetState()
or ReaderStateChangedCallback
callback)ReaderGetTagID()
and check
if the expected tag was found, if it was not found got back to step 1ReaderWriteNDEF()
with the NDEF message that you want to writeReaderGetState()
or ReaderStateChangedCallback
callback)BrickletNFC.
ReaderRequestNDEF
()¶Reads NDEF formated data from a tag.
This function currently supports NFC Forum Type 1, 2, 3, 4, 5 and Mifare Classic.
The general approach for reading a NDEF message is as follows:
ReaderRequestTagID()
ReaderGetState()
or ReaderStateChangedCallback
callback)ReaderGetTagID()
and check if the
expected tag was found, if it was not found got back to step 1ReaderRequestNDEF()
ReaderGetState()
or ReaderStateChangedCallback
callback)ReaderReadNDEF()
to retrieve the NDEF message from the bufferBrickletNFC.
ReaderReadNDEF
() As Byte()¶Returns: |
|
---|
Returns the NDEF data from an internal buffer. To fill the buffer
with a NDEF message you have to call ReaderRequestNDEF()
beforehand.
BrickletNFC.
ReaderAuthenticateMifareClassicPage
(ByVal page As Integer, ByVal keyNumber As Byte, ByVal key() As Byte)¶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:
ReaderRequestTagID()
ReaderGetState()
or ReaderStateChangedCallback
callback)ReaderGetTagID()
and check if the
expected tag was found, if it was not found got back to step 1ReaderAuthenticateMifareClassicPage()
with page and key for the pageReaderGetState()
or ReaderStateChangedCallback
callback)ReaderRequestPage()
or ReaderWritePage()
to read/write pageThe authentication will always work for one whole sector (4 pages).
The following constants are available for this function:
For keyNumber:
BrickletNFC.
ReaderWritePage
(ByVal page As Integer, ByVal data() As Byte)¶Parameters: |
|
---|
Writes a maximum of 8192 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:
ReaderRequestTagID()
ReaderGetState()
or
ReaderStateChangedCallback
callback)ReaderGetTagID()
and check if the
expected tag was found, if it was not found got back to step 1ReaderWritePage()
with page number and dataReaderGetState()
or
ReaderStateChangedCallback
callback)If you use a Mifare Classic tag you have to authenticate a page before you
can write to it. See ReaderAuthenticateMifareClassicPage()
.
NFC Forum Type 4 tags are not organized into pages but different files. We currently support two files: Capability Container file (CC) and NDEF file.
Choose CC by setting page to 3 or NDEF by setting page to 4.
The following constants are available for this function:
For page:
BrickletNFC.
ReaderRequestPage
(ByVal page As Integer, ByVal length As Integer)¶Parameters: |
|
---|
Reads a maximum of 8192 bytes starting from the given page and stores them into a buffer.
The buffer can then be read out with ReaderReadPage()
.
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:
ReaderRequestTagID()
ReaderGetState()
or ReaderStateChangedCallback
callback)ReaderGetTagID()
and check if the
expected tag was found, if it was not found got back to step 1ReaderRequestPage()
with page numberReaderGetState()
or ReaderStateChangedCallback
callback)ReaderReadPage()
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 ReaderAuthenticateMifareClassicPage()
.
NFC Forum Type 4 tags are not organized into pages but different files. We currently support two files: Capability Container file (CC) and NDEF file.
Choose CC by setting page to 3 or NDEF by setting page to 4.
The following constants are available for this function:
For page:
BrickletNFC.
ReaderReadPage
() As Byte()¶Returns: |
|
---|
Returns the page data from an internal buffer. To fill the buffer
with specific pages you have to call ReaderRequestPage()
beforehand.
BrickletNFC.
CardemuGetState
(ByRef state As Byte, ByRef idle As Boolean)¶Output Parameters: |
|
---|
Returns the current cardemu state of the NFC Bricklet.
On startup the Bricklet will be in the CardemuInitialization state. The initialization will only take about 20ms. After that it changes to CardemuIdle.
The Bricklet is also reinitialized if the mode is changed, see SetMode()
.
The functions of this Bricklet can be called in the CardemuIdle state and all of the CardemuReady and CardemuError states.
Example: If you call CardemuStartDiscovery()
, the state will change to
CardemuDiscover until the discovery is finished. Then it will change
to either CardemuDiscoverReady if it worked or to CardemuDiscoverError if it
didn't.
The same approach is used analogously for the other API functions.
The following constants are available for this function:
For state:
BrickletNFC.
CardemuStartDiscovery
()¶Starts the discovery process. If you call this function while a NFC reader device is near to the NFC Bricklet the state will change from CardemuDiscovery to CardemuDiscoveryReady.
If no NFC reader device can be found or if there is an error during discovery the cardemu state will change to CardemuDiscoveryError. In this case you have to restart the discovery process.
If the cardemu state changes to CardemuDiscoveryReady you can start the NDEF message
transfer with CardemuWriteNDEF()
and CardemuStartTransfer()
.
BrickletNFC.
CardemuWriteNDEF
(ByVal ndef() As Byte)¶Parameters: |
|
---|
Writes the NDEF message that is to be transferred to the NFC peer.
The maximum supported NDEF message size in Cardemu mode is 255 byte.
You can call this function at any time in Cardemu mode. The internal buffer will not be overwritten until you call this function again or change the mode.
BrickletNFC.
CardemuStartTransfer
(ByVal transfer As Byte)¶Parameters: |
|
---|
You can start the transfer of a NDEF message if the cardemu state is CardemuDiscoveryReady.
Before you call this function to start a write transfer, the NDEF message that
is to be transferred has to be written via CardemuWriteNDEF()
first.
After you call this function the state will change to CardemuTransferNDEF. It will change to CardemuTransferNDEFReady if the transfer was successful or CardemuTransferNDEFError if it wasn't.
The following constants are available for this function:
For transfer:
BrickletNFC.
P2PGetState
(ByRef state As Byte, ByRef idle As Boolean)¶Output Parameters: |
|
---|
Returns the current P2P state of the NFC Bricklet.
On startup the Bricklet will be in the P2PInitialization state. The initialization will only take about 20ms. After that it changes to P2PIdle.
The Bricklet is also reinitialized if the mode is changed, see SetMode()
.
The functions of this Bricklet can be called in the P2PIdle state and all of the P2PReady and P2PError states.
Example: If you call P2PStartDiscovery()
, the state will change to
P2PDiscover until the discovery is finished. Then it will change
to either P2PDiscoverReady* if it worked or to P2PDiscoverError if it
didn't.
The same approach is used analogously for the other API functions.
The following constants are available for this function:
For state:
BrickletNFC.
P2PStartDiscovery
()¶Starts the discovery process. If you call this function while another NFC P2P enabled device is near to the NFC Bricklet the state will change from P2PDiscovery to P2PDiscoveryReady.
If no NFC P2P enabled device can be found or if there is an error during discovery the P2P state will change to P2PDiscoveryError. In this case you have to restart the discovery process.
If the P2P state changes to P2PDiscoveryReady you can start the NDEF message
transfer with P2PStartTransfer()
.
BrickletNFC.
P2PWriteNDEF
(ByVal ndef() As Byte)¶Parameters: |
|
---|
Writes the NDEF message that is to be transferred to the NFC peer.
The maximum supported NDEF message size for P2P transfer is 255 byte.
You can call this function at any time in P2P mode. The internal buffer will not be overwritten until you call this function again, change the mode or use P2P to read an NDEF messages.
BrickletNFC.
P2PStartTransfer
(ByVal transfer As Byte)¶Parameters: |
|
---|
You can start the transfer of a NDEF message if the P2P state is P2PDiscoveryReady.
Before you call this function to start a write transfer, the NDEF message that
is to be transferred has to be written via P2PWriteNDEF()
first.
After you call this function the P2P state will change to P2PTransferNDEF. It will change to P2PTransferNDEFReady if the transfer was successfull or P2PTransferNDEFError if it wasn't.
If you started a write transfer you are now done. If you started a read transfer
you can now use P2PReadNDEF()
to read the NDEF message that was written
by the NFC peer.
The following constants are available for this function:
For transfer:
BrickletNFC.
P2PReadNDEF
() As Byte()¶Returns: |
|
---|
Returns the NDEF message that was written by a NFC peer in NFC P2P mode.
The NDEF message is ready if you called P2PStartTransfer()
with a
read transfer and the P2P state changed to P2PTransferNDEFReady.
BrickletNFC.
SimpleGetTagID
(ByVal index As Byte, ByRef tagType As Byte, ByRef tagID() As Byte, ByRef lastSeen As Long)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns the tag type and tag ID from simple mode sorted by last seen time for a given index.
Up to eight tags are saved.
The following constants are available for this function:
For tagType:
New in version 2.0.6 (Plugin).
BrickletNFC.
CardemuSetTagID
(ByVal tagIDLength As Byte, ByVal tagIDData() As Byte)¶Parameters: |
|
---|
Sets the tag ID for cardemu mode. The tag ID can either have a length of 4 or 7.
Set a length of 0 for random tag ID (default)
New in version 2.1.0 (Plugin).
BrickletNFC.
CardemuGetTagID
(ByRef tagIDLength As Byte, ByRef tagIDData() As Byte)¶Output Parameters: |
|
---|
Returns the tag ID and length as set by CardemuSetTagID()
.
New in version 2.1.0 (Plugin).
BrickletNFC.
SetDetectionLEDConfig
(ByVal config As Byte)¶Parameters: |
|
---|
Sets the detection LED configuration. By default the LED shows if a card/reader is detected.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For config:
BrickletNFC.
GetDetectionLEDConfig
() As Byte¶Returns: |
|
---|
Returns the configuration as set by SetDetectionLEDConfig()
The following constants are available for this function:
For config:
BrickletNFC.
SetMaximumTimeout
(ByVal timeout As Integer)¶Parameters: |
|
---|
Sets the maximum timeout.
This is a global maximum used for all internal state timeouts. The timeouts depend heavily
on the used tags etc. For example: If you use a Type 2 tag and you want to detect if
it is present, you have to use ReaderRequestTagID()
and wait for the state
to change to either the error state or the ready state.
With the default configuration this takes 2-3 seconds. By setting the maximum timeout to 100ms you can reduce this time to ~150-200ms. For Type 2 this would also still work with a 20ms timeout (a Type 2 tag answers usually within 10ms). A type 4 tag can take up to 500ms in our tests.
If you need a fast response time to discover if a tag is present or not you can find a good timeout value by trial and error for your specific tag.
By default we use a very conservative timeout, to be sure that any tag can always answer in time.
New in version 2.0.1 (Plugin).
BrickletNFC.
GetMaximumTimeout
() As Integer¶Returns: |
|
---|
Returns the timeout as set by SetMaximumTimeout()
New in version 2.0.1 (Plugin).
BrickletNFC.
GetSPITFPErrorCount
(ByRef errorCountAckChecksum As Long, ByRef errorCountMessageChecksum As Long, ByRef errorCountFrame As Long, ByRef errorCountOverflow As Long)¶Output Parameters: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
BrickletNFC.
SetStatusLEDConfig
(ByVal config As Byte)¶Parameters: |
|
---|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following constants are available for this function:
For config:
BrickletNFC.
GetStatusLEDConfig
() As Byte¶Returns: |
|
---|
Returns the configuration as set by SetStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletNFC.
GetChipTemperature
() As Short¶Returns: |
|
---|
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.
BrickletNFC.
Reset
()¶Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
BrickletNFC.
GetIdentity
(ByRef uid As String, ByRef connectedUid As String, ByRef position As Char, ByRef hardwareVersion() As Byte, ByRef firmwareVersion() As Byte, ByRef deviceIdentifier As Integer)¶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 procedure to an callback property of the device object:
Sub MyCallback(ByVal sender As BrickletNFC, ByVal value As Short) Console.WriteLine("Value: {0}", value) End Sub AddHandler nfc.ExampleCallback, AddressOf MyCallback
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.
BrickletNFC.
ReaderStateChangedCallback
(ByVal sender As BrickletNFC, ByVal state As Byte, ByVal idle As Boolean)¶Callback Parameters: |
|
---|
This callback is called if the reader state of the NFC Bricklet changes.
See ReaderGetState()
for more information about the possible states.
The following constants are available for this function:
For state:
BrickletNFC.
CardemuStateChangedCallback
(ByVal sender As BrickletNFC, ByVal state As Byte, ByVal idle As Boolean)¶Callback Parameters: |
|
---|
This callback is called if the cardemu state of the NFC Bricklet changes.
See CardemuGetState()
for more information about the possible states.
The following constants are available for this function:
For state:
BrickletNFC.
P2PStateChangedCallback
(ByVal sender As BrickletNFC, ByVal state As Byte, ByVal idle As Boolean)¶Callback Parameters: |
|
---|
This callback is called if the P2P state of the NFC Bricklet changes.
See P2PGetState()
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.
BrickletNFC.
GetAPIVersion
() As Byte()¶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.
BrickletNFC.
GetResponseExpected
(ByVal functionId As Byte) As Boolean¶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:
BrickletNFC.
SetResponseExpected
(ByVal functionId As Byte, ByVal responseExpected As Boolean)¶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:
BrickletNFC.
SetResponseExpectedAll
(ByVal responseExpected As Boolean)¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletNFC.
SetBootloaderMode
(ByVal mode As Byte) As Byte¶Parameters: |
|
---|---|
Returns: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following constants are available for this function:
For mode:
For status:
BrickletNFC.
GetBootloaderMode
() As Byte¶Returns: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletNFC.
SetWriteFirmwarePointer
(ByVal pointer As Long)¶Parameters: |
|
---|
Sets the firmware pointer for WriteFirmware()
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletNFC.
WriteFirmware
(ByVal data() As Byte) As Byte¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
SetWriteFirmwarePointer()
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletNFC.
WriteUID
(ByVal uid As Long)¶Parameters: |
|
---|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
BrickletNFC.
ReadUID
() As Long¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletNFC.
DEVICE_IDENTIFIER
¶This constant is used to identify a NFC 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.
BrickletNFC.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a NFC Bricklet.