Skip to content
DownloadsSales enquiry
English

PR1043 vs PR1008: USB NFC readers

Choose a desktop reader by card technology, required operation and host software, rather than by USB connector alone.

Application guides

A desktop NFC project starts with a specific card or tag and a defined operation: reading an identifier, exchanging card commands or writing supported tag data. USB connectivity alone does not establish compatibility with the card application. Use the required card standard and operating mode to narrow the hardware, then test it with the intended host and software.

Discuss this application

PR1043 vs PR1008: key selection specifications

Both models use USB CCID and PC/SC. Compare the card standards, operating modes and exact connector variant before selecting a reader.

PR1043 vs PR1008: key selection specifications
Selection factor PR1043PR1008
USB connector and variant USB Type-A: PR1043-M1; USB Type-C: PR1043-MF.USB Type-A: PR1008-M1; USB Type-C: PR1008-MF.
Listed contactless standards ISO 14443 Type A and B; ISO 15693; ISO/IEC 18092 NFC; MIFARE; FeliCa.ISO 14443 Type A and B; ISO/IEC 18092 NFC; MIFARE; FeliCa. ISO 15693 is not listed in the referenced specifications; this does not establish that it is unsupported.
Maximum card communication rate Up to 848 kbps for ISO 14443; up to 26 kbps for ISO 15693. Actual results depend on the card and operation.Up to 424 kbps; actual results depend on the card and operation.
Listed NFC operating modes Reader/writer; card emulation; keyboard emulation.Reader/writer; card emulation; peer-to-peer.
SAM interface 1 SAM slot; ISO 7816 Class A (5 V).1 SAM slot; ISO 7816 Class A (5 V).
Software and configuration USB CCID and PC/SC. The listed Windows configuration tool is for UID keyboard emulation only.USB CCID and PC/SC. Check this model's driver and API manual for integration.

Listed standards and modes do not guarantee that a complete card application will work. Evaluate the intended card, commands, keys, middleware and host software before ordering. The quoted maximum card communication rates are not measured application throughput.

Manufacturer references: PR1043PR1008

Moving from an ACR122U project?

ACS marks ACR122U as end-of-life, advises against new deployments and recommends PR1043 as an alternative. Treat this as a migration to evaluate: it does not establish that an existing application will work unchanged.

  • Record the existing setup

    Identify the complete reader model and firmware, host OS version, driver and application or middleware. Standard ACR122U and the separate ACR122U-SAM are different variants; state whether the workflow uses a SAM.

  • Review card and command requirements

    Record the card or tag, the required operations, reader-specific commands and expected UID or response format. Shared USB CCID and PC/SC interfaces do not prove that model-specific APIs or commands are interchangeable.

  • Evaluate the target configuration

    Confirm the PR1043 variant and USB connector, select PC/SC or keyboard emulation as required, then test the actual cards, application, SAM workflow if used and recovery after reconnecting. Keyboard UID output is not a substitute for card-command access.

ACS lifecycle notice and manufacturer reference

Compare candidate models

Use these models as a starting point. Confirm the exact variant, software support and evaluation results for your project before ordering.

Compare candidate models
ModelSelection focusConfirm for your project
PR1043 Specifications & downloads PR1043 supports reader/writer, card emulation and keyboard emulation. Its listed card standards include ISO 15693. Choose the connector variant and required operating mode; check the card commands and SAM requirements in the model documentation.
PR1008 Specifications & downloads PR1008 lists reader/writer, card emulation and peer-to-peer NFC modes, with a SAM slot. Check the exact card standard and mode. Do not assume its supported modes or card families are identical to PR1043.

Plan the evaluation

  1. Define a repeatable test

    Use the intended card or tag and record the read/write operations, expected response and host environment.

  2. Check the software route

    Review the driver, reference manual and applicable SDK. Confirm what is included and whether separate software or licences are needed.

  3. Evaluate the complete setup

    Test card presentation, operating mode and recovery after disconnecting the reader before choosing a deployment quantity.

What to include in your enquiry

  • Card or tag model and required operations
  • Host operating system, application and USB connector
  • Operating mode and SAM requirements
  • Evaluation quantity, delivery country and project schedule
Discuss this application

The Contact form will include this guide as its source. Add your requirements, review the details and submit your enquiry online.

Price, evaluation-unit availability, quantities, software scope and delivery need confirmation for each request.

Before you order

Can one NFC reader work with every NFC card?

Start with the standards listed for the reader, then confirm the exact card application and commands. A supported radio standard does not by itself provide the application's keys, data format or business software.

Is keyboard emulation the same as PC/SC access?

They are different integration routes. Define whether the application expects keyboard input or needs to exchange card commands, and check the model's supported mode and configuration instructions.

Will a driver or SDK complete my application?

Drivers and development resources help connect and evaluate the hardware. Confirm the software scope, licence and work needed to implement your own card workflow.

Manufacturer references

Technical details refer to the original ACS model documentation. Use the linked product pages for the full specifications and downloads.