-16-
v7.0
Libelium’s library
8.2. Switching the module on
This function takes the RFID/NFC module out of the power-down mode by starting the wake up procedure.
If you connected the RFID/NFC module into the usual XBee socket, please use SOCKET0; if you connected the RFID/NFC module
into the Expansion Board, you must use SOCKET1.
Example of use:
{
RFID13.ON(SOCKET0); // switches the module on with the socket 0 (the normal socket, without
// using the Expansion Board)
}
http://www.libelium.com/development/waspmote/examples/RFID1356-01-basic-example
8.3. Switching the module off
This function takes the RFID/NFC module to the software power-down mode.
Example of use:
{
RFID13.OFF(); // switches the module off
}
http://www.libelium.com/development/waspmote/examples/RFID1356-01-basic-example
8.4. Initiating the module
This function initializes the necessary variables, requests if there is an ISO/IEC 14443-A card in the field, does the anti-collision
loop and selects the card to operate.
This function is enough for those applications which just require to get the UID of cards, since most of the ISO/IEC 14443-A
processes are executed inside.
It is highly advised to execute this function in the beginning of each loop, just as shown in any of the examples. Even if the
module is already initialized, it is good to start from the same point every time.
This function initializes many internal registers and variables. All the settings are optimized for the best operation. Changing
those settings may result in a defective operation.
Example of use:
{
uint8_t state; // stores the status of the executed command
uint8_t ATQ[2]; // stores the ATQ-A (answer to request, type 14443- A). Generally stored in
// a bigger buffer (16B)
uint8_t UID[4]; // stores the UID (unique identification) of a card
...
state = RFID13.init(UID, ATQ); // The goal of this command is to detect as many targets
// (maximum MaxTg) as possible in passive mode.
}
http://www.libelium.com/development/waspmote/examples/RFID1356-01-basic-example
