Part Number: RF-HDT-DVBE Hi, Good day. Our customer wants to know the password for the RF-HDT-DVBE-N2. They were able to read from it but when he tries to write it says he doesn't have access rights. Can you please help us provide the password to allow…
Part Number: RF-HDT-DVBB Hi Team,
We would like to ask your help regarding our customer's inquiry below.
I have a technical question about NFC tags Tag-IT HF-I. I have a TAG - IT HF-I which cannot be programmed, all memory blocks are at 000000, what…
Part Number: RF-HDT-DVBB We purchased some RF-HDT-DVBB-N2 tags, but cannot write by using the 15693 reader. We can read from the data blocks and the UID, but the reader cannot detect the tag when trying to write. We find there are two possible reasons…
Part Number: RF-HDT-DVBB Hi,
Does TI sell any RFID tags that are compatible with reading and writing from smartphones? The RF-HDT-DVBB seems like it should be compatible, but I am not sure.
Part Number: RF-HDT-AJLS Dear Sir / Madam,
We would like to purchase RFID tags based on TI's RF-HDT-AJLS IC. Request you to please let us know the tag manufacturers who can help us with the same.
Inquiries about RF-HDT-DVBB-N2
Could you expand Material_Content data?
It is necessary to obtain these data at the request of the customer.
Your customer support center will instruct you to request by E2E.
Thanking you in advance.
Part Number: TRF7970A Other Parts Discussed in Thread: RF-HDT-DVBB Tool/software:
Hi Expert,
we need advice for how to apply a Japan technical standard compliance, Japanese FCC.
Refer to TRF7970A datasheet 7.1.2 Schematic
https://www.ti.com/lit/ds/symlink…
Part Number: RF-HDT-DVBE Other Parts Discussed in Thread: RF-HDT-DVBB Hi Team,
A customer wants to attach the RF-HDT-DVBE or RF-HDT-DVBB at the back of a mobile phone. A reader will be place beside a door. The maximum distance between the door and mobile…
Part Number: RF-HDT-AJLC Hello,
We have some queries for RF-HDT-AJLC-G0.
1.Do you know cases that malfunction occurs during a write sequence?
2.What operation does cause the lock of the specific memory area (in our case, block 16)?
Background is following…
