From f5f5788afe1c856107629cdb3ab58b34a8f3e6a1 Mon Sep 17 00:00:00 2001 From: Rotzbua Date: Wed, 8 Feb 2017 21:49:27 +0100 Subject: [PATCH] Update ReadUidMultiReader.ino - description was wrong - added warning, because many trouble with example --- .../ReadUidMultiReader/ReadUidMultiReader.ino | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/examples/ReadUidMultiReader/ReadUidMultiReader.ino b/examples/ReadUidMultiReader/ReadUidMultiReader.ino index c1bc4c2..c14c17a 100644 --- a/examples/ReadUidMultiReader/ReadUidMultiReader.ino +++ b/examples/ReadUidMultiReader/ReadUidMultiReader.ino @@ -1,17 +1,16 @@ /** - * ---------------------------------------------------------------------------- - * This is a MFRC522 library example; see https://github.com/miguelbalboa/rfid - * for further details and other examples. + * -------------------------------------------------------------------------------------------------------------------- + * Example sketch/program showing how to read data from more than one PICC to serial. + * -------------------------------------------------------------------------------------------------------------------- + * This is a MFRC522 library example; for further details and other examples see: https://github.com/miguelbalboa/rfid * - * NOTE: The library file MFRC522.h has a lot of useful info. Please read it. + * Example sketch/program showing how to read data from more than one PICC (that is: a RFID Tag or Card) using a + * MFRC522 based RFID Reader on the Arduino SPI interface. * - * Released into the public domain. - * ---------------------------------------------------------------------------- - * This sample shows how to read and write data blocks on a MIFARE Classic PICC - * (= card/tag). - * - * BEWARE: Data will be written to the PICC, in sector #1 (blocks #4 to #7). + * Warning: This may not work! Multiple devices at one SPI are difficult and cause many trouble!! Engineering skill + * and knowledge are required! * + * @license Released into the public domain. * * Typical pin layout used: * -----------------------------------------------------------------------------------------