D-Logic hardware · Independent distribution & integrationThe right interface. The right reader.

Applications

Define the data operation first.

Read or write the required card or tag data through an application. Identify the exact operation, card model and intended result.

Configuration boundaries

PR PC/SC Standard, PR SDK and PR libNFC use different software paths. PR libNFC uses libNFC, not the µFR SDK. Protocol support does not establish access to every memory area: card commands, permissions and selected firmware still matter.

Prepare a tag read/write brief

Define the required result before comparing readers. Send the project details below and identify unknown items for confirmation.

  • Card or tag and target data

    Identify the chip and version, card or tag format, and target data area. State whether you need a UID, NDEF content, a file or a memory block; a UID read alone does not verify a data operation.

  • Operation and access requirements

    Specify the read, write or command sequence and the expected returned data. Describe authentication and access requirements without including card keys or passwords in the inquiry. Confirm write permissions before changing sample data or protection settings.

  • Host and software environment

    Record the operating system, CPU architecture, application and library versions, selected firmware and USB driver or device class. Evaluate the software path your application expects; a USB connector does not make the paths interchangeable.

  • Sample acceptance and purchase

    Use approved sample cards to test the full operation and compare the result with expected data. For writing, verify data after removing and presenting the tag again. Include reconnection checks, sample and later quantities, destination and requested schedule; configuration and commercial terms require quotation confirmation.

Review the card compatibility and sample checks →

Match the operation to a software path

Manufacturer SDK

Evaluate the selected USB model with the documented SDK functions, host library and firmware needed for the actual card operation. Reader discovery or a successful UID read does not confirm every read/write or authentication workflow.

PR-101

Discuss this read/write model

PC/SC

Evaluate the selected USB CCID configuration with the host PC/SC stack and actual APDU or card-command sequence. Confirm the card, required operation and selected firmware in the application; detection alone is not acceptance.

PR-201

Discuss this read/write model

libNFC

Evaluate the selected USB model with the target libNFC/libusb build, enabled driver and device access permissions. Test the required card operation in that application. PR libNFC does not use the µFR SDK.

PR-401

Discuss this read/write model

Related guides

Compare PC/SC, SDK and keyboard input →

Software and installation paths

See the procurement process →

Prepare your next step

LET’S FIND YOUR FIT

A reader for your project, not the other way around.

Tell us your card type, platform and quantity. We’ll help narrow the options.

Tell us about your project