rfid | 易学教程

Zebra RZ400 prints an RFID tag, but encodes the subsequent one

阅读更多关于 Zebra RZ400 prints an RFID tag, but encodes the subsequent one

问题 I'm trying to use my RZ400 for the first time. I have placed the RFID tags and the ribbon, calibrated the media and sent the ^XA ^RS8 ^FO50,50^A0N,65^FDHex Pattern 1^FS ^RFW,H^FD112233445566778899AABBCC^FS ^XZ instructions from the programming manual and a RFID tag is printed. The problem is that the NEXT tag is the one that gets encoded. The tags are SMARTRAC 292-2 Belt and the dimensions are 3x0.625 inches. This is a supported tag according to the vendor. Thanks. 回答1: I believe the issue

How to read both EPC and USER memory banks using RFID handheld?

阅读更多关于 How to read both EPC and USER memory banks using RFID handheld?

问题 We are using Handheld Chainway C4000 UHF RFID Reader, and UHF tags. Those tags contains EPC and USER memory banks, Right now I can read all the tags' EPC memory bank by scanning them using the handheld device. This is how I read single tag's EPC memory bank RFIDWithUHF mReader = RFIDWithUHF.getInstance(); String strUII = mReader.inventorySingleTag(); String strEPC = mReader.convertUiiToEPC(strUII); And to read USER memory bank I found that I should stop scanning and start it again but with

Android NFC read Tags issue. Activity starts each time on data received

阅读更多关于 Android NFC read Tags issue. Activity starts each time on data received

问题 I have 2 issues with reading NFC Tags. First is Tag Read Activity creates each time when tag received. And second issue is activity opens in full screen window, not under Tab Host Activity, but first issue is worst. What do I do ( AndroidManifest.xml ): <activity android:name="readingActivity" > <intent-filter> <action android:name="android.nfc.action.TAG_DISCOVERED" /> <category android:name="android.intent.category.DEFAULT" /> </intent-filter> </activity> and readingActivity.cs: @Override

How to determine from which keyboard the input comes

阅读更多关于 How to determine from which keyboard the input comes

问题 Scenario: I have an usb-RFID reader attaching it to notebook it works as an newly attached USB keyboard, e.g. without needing to install any drivers when touching the reader with RFID tag it enters into my current window (for example terminal/shell) the RFID number (like 0009339384\n ) - e.g. it even sends the \n . so, it works exactly as if I had typed the numbers in my notebook's keyboard The questions are: is it possible read the RFID reader directly without some kernel-level drivers, e.g.

read NFC tags in React Native app

阅读更多关于 read NFC tags in React Native app

问题 I want to make a react-native app which can read the NFC tags. I am using react-native-nfc but cannot get it working. Can anyone help with figuring out what I am doing wrong and point me in the right direction? Code in index.android.js is the following: import React, { Component } from 'react'; import { AppRegistry, StyleSheet, Text, View, ToastAndroid } from 'react-native'; import NFC, {NfcDataType, NdefRecordType} from "react-native-nfc"; export default class nfcTry extends Component {

Transceive Failed on ISO15693 / Tag-it HF-I

阅读更多关于 Transceive Failed on ISO15693 / Tag-it HF-I

问题 I have some ISO15693 / Tag-it HF-I Plus chips and need to write something on them. These chips are completly fresh, and i read now a ton of pdf's telling me all the same. But nothing work, and i get all the time the Transceive Failed error. I send these Data in the transceive command: Byte: <data> 0: 0x00 // pdf says the tag understands only flag = 0x00 1: 0x21 // write single block 2-10: ID // needs to be send for this tag, only supports addressed mode 11: 0x00 // Block ID, try to write to

Mifare Access condition calculation

阅读更多关于 Mifare Access condition calculation

问题 I am aware of this post :- Locking mechanism of Mifare Classic 1K However, it is really not clear - how a value like FF 07 80 FF is calculated in this string: D3 F7 D3 F7 D3 F7 FF 07 80 FF 00 00 00 00 00 00 This means that the blocks can be read with key A and written with Key B but does not allow inc/dec. How should the access bits look like if I have to support increment and decrement operations. I understand that C1, C2 and C3 must be 1,1,0 how does this reflect to the byte 6, 7 and 8. Any

NFC-V SLIX-S write password

阅读更多关于 NFC-V SLIX-S write password

问题 I'm trying to set AFI password to the SLIX-S tag. I found the command for set password is B3: take a look please (Link here: Page 12). But every time my set password command crash. I think the format of the code line I use is wrong. Is there any way to solve this problem? Thanks a lot for anything can help me. Update: I tried this one sequence of bytes but still can't set password successfully. buffer = nfcv.transceive(new byte[] { 0x00, //flag 0xB3, //set password command 0x04, /

Distinguish Mifare Ultralight from Mifare Ultralight C

阅读更多关于 Distinguish Mifare Ultralight from Mifare Ultralight C

问题 Is there a reliable way to find out if an RFID card is either a Mifare Ultralight or a Mifare Ultralight C? The only way i found so far is utilizing the difference in size of those two cards issuing a read command beyond the boundaries of the smaller one. But it does look like a hack and i assume the read command might fail if the card uses the Ultralight C authentication mechanism. const char* mifare_ultralight_identification(const nfc_target_info_t nti) { byte_t abtCmd[2]; byte_t abtRx[265]

What mobile phones with NFC have full support of Mifare Classic (1K & 4K) cards? [closed]

阅读更多关于 What mobile phones with NFC have full support of Mifare Classic (1K & 4K) cards? [closed]

Closed. This question is off-topic . It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 6 years ago . Google has stopped supporting such tags in the latest Nexus 4, but what phones still have possibility of reading\writing Mifare Classic cards? Especially interested in hi-end models with powerful processors. Also could anyone provide some inforamtion on emulating such nfc tags with your phone? Thanks in advance Its not that Google stopped support for MIFARE Classic. Instead licensing issues prevent Broadcom to