Differences

This shows you the differences between two versions of the page.

--- amc:ss2024:chicken_check:start [2024/07/30 14:47] – [For this project the following materials were used:] tarik.aydin
+++ amc:ss2024:chicken_check:start [2024/07/31 15:20] (current) – [Chicken Check] rolf.becker
@@ Line 2: / Line 2: @@
 Group T: Jirad Al Massri (32323), Nour-Hamed-Raafat Hamed (31348) and Tarik Aydin (26751)
 ====== Chicken Check ======
+**[[.:nxp_rfid:start|NXP RFID Info Collection by the EOLab Team]]**
 =====1. Introduction=====
@@ Line 228: / Line 230: @@
 =====4. Discussion=====
 Written by Jihad Al Massri
+\\
+First challenge was the usage of I2C, where it uses 7-bit to 10-bit addresses to make the identification of devices on the bus, with many PN532 address conflict can increase because of the limited number of unique addresses. In addition, data collision and bus contention can increase in an environment with high communication traffic because I2C use the same set of wires (SDA and SCL) to the communication of multiple devices. Switching to SPI was the choice since SPI uses separate Chip select for each PN532 that eliminate address conflict, make device management more easy. Moreover, SPI enable a fast communication between the microcontroller and the PN532 because it has a higher data rate as well as it allows simultaneous data transmission and reception. The usage of SPI facilitate the addition of new PN532 to the system since its only require to identify a specific chip select line for every new PN532.\\
+Second challenge was the electromagnetic interference. When the PN532 where on, they were interfering with each other, causing a disruption in their operation. This interference created a dead spot in the detection area because both boards were not able to read data. Additionally, these interference has weakened the detection range of each board that reduces their efficiency and reliability. This has affected the overall performance of the system, making difficulties to have accurate reading from the devices.
 =====5. Conclusion=====
-Written by Jihad Al Massri
+Written by Jihad Al Massri and Nour-Hamed-Raafat Hamed
+\\
-=====6. References=====
-  - https://www.anker.com/blogs/cables/how-to-identify-different-types-of-usb-cables-a-brief-guide
-  - https://www.adafruit.com/product/789
-  - https://www.adafruit.com/product/359
-  - https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html
-  - https://openai.com/index/chatgpt/
-  - https://github.com/adafruit/Adafruit-PN532/blob/master/Adafruit_PN532.cpp
-===== First Draft Ideas =====
-  * RFID bird ringing, bird banding, tagging
-  * 13.56 MHz HF band (not LF nor UHF)
-  * https://learn.adafruit.com/adafruit-pn532-rfid-nfc?view=====all
-===== About RFID ====
-  * https://www.rfid-grundlagen.de/
-  * https://www.smart-tec.com/de/faq
-===== HF RFID Technology (13.56 MHz) =====
-  * :!: Matt Rose and Jon Kurtz (2016): **{{:amc:ss2024:chicken_check:ftf-ins-n2040_future_electronics-nfc_a_closer_look.pdf|NFC - A Closer Look}}** \\ Future Electronics, original  {{https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/ftf2016/124/1/FTF-INS-N2040%20Future%20Electronics-NFC%20A%20closer%20look.pdf|download}}
-==== ISO 14443: Proximity Communication (typ. range: 7-15 cm) ====
-   - **Frequency**: Both ISO 14443 and ISO 15693 operate at **13.56 MHz**.
-   - **Purpose**: ISO 14443 is commonly used in contactless smart cards and NFC-enabled devices.
-   - **Read Range**: ISO 14443 has a shorter read range of **7-15 cm** (approximately 2.8-5.9 inches).
-   - **Data Transfer Rate**: It offers a higher data transfer rate with a **106 kbps** Baud rate.
-   - **Applications**: ISO 14443 is suitable for financial transactions, access control, parking solutions, and attendance systems².
-==== ISO 15693: Vicinity Communication (typ. range: < 100 cm) ====
-   - **Purpose**: ISO 15693 defines the communication protocol for RFID tags operating at **13.56 MHz**.
-   - **Read Range**: ISO 15693 provides an extended read range of **up to 1 meter** (approximately 3.3 feet).
-   - **Data Transfer Rate**: It has a slower data rate with a **26 kbps** Baud rate.
-   - **Applications**: ISO 15693 is useful for applications like inventory management, asset tracking, and libraries¹⁵.
-In summary, ISO 14443 is ideal for short-range applications like wireless payments, while ISO 15693 suits scenarios where longer read distances are necessary. 📡🔍🏷️¹²
-Source: Conversation with Copilot, 30/06/2024
-(1) NFC Reader Guide - Shop NFC. https://bing.com/search?q=iso+14443+vs+iso+15693.
+In this project, the initial use of I2C communication for PN532 NFC/RFID has faced a challenge, to distinguish between multiple boards. The switch to SPI communication has solved the issue by the usage separate chip select lines that made the communication more reliable and stable. Despite these improvements, the interference between the boards is still a challenge that promotes to explore techniques such as physical separation and shielding.
+Because of the challenges we faced, a lot of insight was gained.
 \\
-(2) The difference between ISO15693 and ISO14443 - RFID Card. https://www.rfidcard.com/the-difference-between-iso15693-and-iso14443/.
+Technology Integration: Learned to combine ESP32 microcontrollers and PN532 with RFID tags technology for tracking.
 \\
-(3) Understanding the ISO15693 Protocol: An In-depth Look. https://www.rfidlabel.com/understanding-the-iso15693-protocol-an-in-depth-look/.
-\\
+Understanding Antennas :\\
-(4) NFC Reader Guide - Shop NFC. https://www.shopnfc.com/en/content/31-nfc-reader-guide.
+Gained knowledge on how antennas work with RFID systems and UID detection.
 \\
-(5) What is ISO/IEC 15693? RFID Communication Standard for HF and NFC. https://www.encstore.com/blog/5722-what-is-iso-iec-15693-rfid-communication-standard-for-hf-and-nfc.
-==== Differences between ISO/IEC 15693-26 and ISO/IEC 15693-53 (Collected by COPILOT) ====
+UID detection:\\
+Gained knowledge on how NFC/RFID tags interacts with readers like the PN532.
+\\
-**ISO/IEC 15693-26**:
+System Design:\\
-   - **Modulation Scheme**: ISO/IEC 15693-26 uses a subcarrier frequency of 423.75 kHz.
+ As a group a lot of experience was gained through trail and troubleshooting integrated systems involving hardware and software parts of the project.
-   - **Data Rate**: The data rate for ISO/IEC 15693-26 is **26.48 kbps.**
+\\
-   - **Application**: This variant is commonly used in applications such as inventory management, asset tracking, and library systems.
-   - **Read Range**: The read range is typically up to 1 meter (approximately 3.3 feet).
-**ISO/IEC 15693-53**:
+I2C and SPI:\\
-   - **Modulation Scheme**: ISO/IEC 15693-53 uses a subcarrier frequency of 847.5 kHz.
+I2C has a communication serial line to all antennas (sda scl), and for the SPI can distinguish between the antennas through chip select.
-   - **Data Rate**: The data rate for ISO/IEC 15693-53 is **53.98 kbps.**
+\\
-   - **Application**: It is also used for inventory management, asset tracking, and similar applications.
-   - **Read Range**: Similar to ISO/IEC 15693-26, the read range is up to 1 meter.
-In summary, both variants are part of the ISO/IEC 15693 standard and share similar use cases. The main difference lies in their modulation frequencies and data rates. 📡🔍🏷️
+Future work:\\
+Where to pick up this project?
+The main focus should be on advanced method to reduce electromagnetic interference as this was the main challenge in our project , improve system flexibility where it can track multiple behaviors like chicken nesting habits and health tracking, and real world testing to apply the methods and then accordingly make changes in hardware or software.
-Source: Conversation with Copilot, 30/06/2024
+=====6. References=====
+  - https://www.anker.com/blogs/cables/how-to-identify-different-types-of-usb-cables-a-brief-guide
+  - https://www.adafruit.com/product/789
+  - https://www.adafruit.com/product/359
+  - https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html
+  - https://openai.com/index/chatgpt/
+  - https://github.com/adafruit/Adafruit-PN532/blob/master/Adafruit_PN532.cpp
-==== GAO RFID ====
-  * {{https://gaorfid.com/RFID-brochures/13.56_MHz_HF_High-powered_RFID_Reader_233016.pdf}}
-  * Range: up to 90 cm with single antenna
-  * Speed: up to 60 readings per second
-  * Separation: 300 tags at once
-==== NXP NFC Solutions ====
-  * :!: **[[https://www.mouser.de/new/nxp-semiconductors/nxp-nfc-solutions/|START HERE!]]**
-==== NXP CLRC663 plus (CLRC66303HN) - High performance multi-protocol NFC frontend ====
-**https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/clrc663-iplus-i-family-high-performance-nfc-frontends:CLRC66303HN**
-| {{https://www.nxp.com/assets/images/en/photography/CLRC663-IMG.png?800&direct}} |
-| Source: **[[https://www.nxp.com/pages/high-performance-multi-protocol-nfc-frontend:CLRC663|NXP CLRC663 product page]]** |
-| {{https://www.nxp.com/assets/images/en/dev-board-image/BOARD-OM26630FDK-PRODUCT-SHOT.png?400&direct}} | {{https://www.nxp.com/assets/images/en/dev-board-image/CLRC663-PLUS.jpg?400&direct}} |
-| Evaluation Board **CLEV6630B** (NXP) | Development Kit **OM26630FDKM** (NXP, including CLEV6630B) |
-  * :!: ** [[https://www.nxp.com/pages/high-performance-multi-protocol-nfc-frontend:CLRC663|NXP CLRC663 Product Page]]**
-  * Chip Mame: **CLRC66303HN** (I_T(max) 350-500 mA, up to 2 Watts)
-  * Eval Board Name: **CLEV6630B**
-  * Dev Kit Name: **OM26630FDKM** (includes CLEV6630B)
-  * Datasheet **CLRC663:** {{https://www.nxp.com/docs/en/data-sheet/CLRC663.pdf|NXP CLRC663 - High performance multi-protocol NFC frontend CLRC663 and CLRC663 plus}}
-  * Datasheet **SLRC610:** {{https://www.nxp.com/docs/en/data-sheet/SLRC610.pdf|NXP SLRC610 - High-performance ICODE frontend SLRC610 and SLRC610 plus}}
-  * {{https://www.nxp.com/docs/en/application-note/AN11022.pdf|AN11022 CLRC663 evaluation board quick start guide}}
-  * {{https://www.nxp.com/docs/en/application-note/AN12657.pdf|AN12657 Using the RC663 without library}}
-==== NXP PN5180 ====
-| {{https://www.nxp.com/assets/images/en/dev-board-image/OM25180FDK-DK.png?400&direct}}                                                                                              | {{https://de.farnell.com/productimages/standard/en_GB/2663168-40.jpg?400&direct}}                                               |
-| OM25180FDK Dev. Kit + Extras from [[https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/pn5180-nfc-frontend-development-board-for-pos-terminal-applications:OM25180FDK|NXP]]  | NNEV5180BM product picture by [[https://de.farnell.com/nxp/pnev5180bm/evaluationsboard-nfc-reader/dp/2663168|Farnell]].  |
-  * :!: **[[https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/full-nfc-forum-compliant-frontend-ic:PN5180|NXP PN5180 Product Page]]**
-  * Chip Name: **PN5180B** (I_T(max) 250 mA) (PN5180A0HN???)
-  * Eval Board Name: **PNEV5180B**
-  * Dev Kit Name: **OM25180FDKM** (includes PNEV5180B)
-  * NXP [[https://community.nxp.com/t5/NFC/bd-p/nfc|NFC Antenna Tool]]
-  * :!: Datasheet PN5180, **C3,C4** (Rev. 4.1, 2023-03-13): {{https://www.nxp.com/docs/en/data-sheet/PN5180A0XX_C3_C4.pdf|NXP PN5180A0xx/C3,C4 Rev. 4.1}}
-  * Datasheet PN5180, **C1,C2** (Rev. 3.6, 2018-05-07): {{https://www.nxp.com/docs/en/data-sheet/PN5180A0XX-C1-C2.pdf|NXP PN5180A0xx/C1/C2 Rev. 3.6}}
-| {{https://raw.githubusercontent.com/playfultechnology/PN5180-Library/master/doc/PN5180-NFC.png?400&direct}} | {{:amc:ss2024:chicken_check:pn5180_r1_1_170710_sch.png?direct&400|}} |
-| A cheap PN5180 board (R1.1-170710) for Arduino-like projects. | Schematic by Future Electronics \\ (Download: {{https://github.com/ATrappmann/PN5180-Library/blob/master/doc/PN5180%20R1.1-170710_SCH.PDF|A. Trappmann's Github}}) |
-=== PN5180 Application Notes ===
-  * {{https://www.nxp.com/docs/en/application-note/AN11744.pdf|AN11744 PN5180 Evaluation board quick start guide}}
-  * {{https://www.nxp.com/docs/en/user-guide/UM10954.pdf|UM10954 PN5180 SW quick start guide}}
-  * {{https://www.nxp.com/docs/en/application-note/AN11740.pdf|AN11740 PN5180 Antenna design guide}}
-  * {{https://www.nxp.com/docs/en/application-note/AN11741.pdf|AN11741 How to design an antenna with DPC}}
-  * {{https://www.nxp.com/docs/en/application-note/AN11906.pdf|AN11906 Starting a product development with PN5180}}
-  * {{https://www.nxp.com/docs/en/application-note/AN12650.pdf|AN12650 Using the PN5180 without library}}
-  * {{https://www.nxp.com/docs/en/application-note/AN12810.pdf|AN12810 How to use the NanoVNA for the NFC reader antenna design}}
-=== PN5180 Arduino Libraries ===
-  * https://github.com/ATrappmann/PN5180-Library
-  * https://github.com/L4M0S/PN5180-Library-14443
-  * https://github.com/playfultechnology/arduino-rfid-PN5180
-  * https://github.com/playfultechnology/PN5180-Library
-==== PN532 Module V3 by Elechouse (5V, red board) ====
-This is the cheap version (the red board with 8 + 4 pin headers / connectors) you still can buy everywhere. Drawback: Only the 5V is exposed to the connector and not the 3.3V output. The board has to be modified to be usable with a 3.3V voltage source, e.g. by desoldering the voltage regulator and building wire bridge from 3.3V to the power pin on the connector (origially named 5V).
-  * {{https://www.elechouse.com/elechouse/images/product/PN532_module_V3/PN532_ Manual_V3.pdf}}
-  * [[https://github.com/elechouse/PN532]]
-| {{:amc:ss2024:chicken_check:elechouse_pn532_module_v3_top.jpg?direct&400|}} | {{:amc:ss2024:chicken_check:elechouse_pn532_module_v3_bottom.jpg?direct&400|}} |
-==== Adafruit RFID/NFC PN532 Breakout ====
-[[.nxp_rfid:adafruit_pn532]]
-==== Other version of the red board (3.3V, 5V) ====
-Wiki: http://wiki.sunfounder.cc/index.php?title=PN532_NFC_RFID_Module
-{{:amc:ss2024:chicken_check:pn532-1.jpg?direct&400|}}
-Instructables: https://www.instructables.com/HackerBox-0072-Tagger/
-{{https://content.instructables.com/FFB/WOP5/KVP8ZV1E/FFBWOP5KVP8ZV1E.png?400&direct}}
-{{http://wiki.sunfounder.cc/images/a/af/PN532_Schematic.pdf}}
-===== Terminology =====
-Bird ringing is the term used in the UK and in some other parts of Europe and the world. Bird banding is the term used in the US. Organised ringing efforts are called ringing or banding schemes, and the organisations that run them are ringing or banding authorities. (Birds are ringed rather than rung) Those who ring or band are known as ringers or banders, and they are typically active at ringing or banding stations.
-\\
-[[https://en.wikipedia.org/wiki/Bird_ringing]]