未知厂商RFID读卡器通用读写方法咨询（以C#为例）及驱动API疑问

Hey there! Let's break down your questions about working with an unknown RFID reader in C#—I’ve dealt with a fair share of these, so here’s what you need to know:

1. Are there universal card read/write methods in C#? #

Sort of—but it depends heavily on the RFID standard your device and cards follow. Here’s the breakdown:

• PC/SC Compliant Readers: If your reader adheres to the PC/SC (Personal Computer/Smart Card) standard (common for 13.56MHz NFC/contactless cards like MIFARE), you can use universal APIs. Windows has a built-in Smart Card Service that supports PC/SC, and there’s a great NuGet package called PCSC that wraps this functionality for C#.

  This lets you do things like enumerate readers, connect to cards, and send standard APDU commands (the language smart cards understand) without vendor-specific code. Here’s a quick example:

  using PCSC;
  using System;
  
  class RfidDemo
  {
      static void Main()
      {
          using (var context = new SCardContext())
          {
              context.Establish(SCardScope.System);
              var readers = context.GetReaders();
  
              if (readers.Length == 0)
              {
                  Console.WriteLine("No PC/SC readers detected.");
                  return;
              }
  
              // Connect to the first available reader
              using (var reader = new SCardReader(context))
              {
                  var connectResult = reader.Connect(
                      readers[0], 
                      SCardShareMode.Shared, 
                      SCardProtocol.Any);
  
                  if (connectResult != SCardError.Success)
                  {
                      Console.WriteLine($"Failed to connect: {connectResult}");
                      return;
                  }
  
                  // Send an APDU to get the card's UID (works for most 13.56MHz cards)
                  var getUidApdu = new byte[] { 0xFF, 0xCA, 0x00, 0x00, 0x00 };
                  var responseBuffer = new byte[256];
                  var transmitResult = reader.Transmit(
                      getUidApdu, 
                      responseBuffer, 
                      out var bytesReceived);
  
                  if (transmitResult == SCardError.Success)
                  {
                      Console.WriteLine($"Card UID: {BitConverter.ToString(responseBuffer, 0, bytesReceived)}");
                  }
                  else
                  {
                      Console.WriteLine($"Command failed: {transmitResult}");
                  }
  
                  reader.Disconnect(SCardDisposition.Leave);
              }
          }
      }
  }
  

• Non-Standard Readers: For devices that don’t follow PC/SC (like many cheap 125kHz readers or custom UHF readers), there’s no true "universal" method. You’ll need to either:

  • Use the vendor’s provided serial/USB command set (if they document it) and communicate via SerialPort or UsbDevice classes in C#.
  • Wait for the vendor to release an SDK with C# bindings.

2. Does every RFID reader require a dedicated driver/API? #

Again, not always—but most do in practice:

• PC/SC Compliant Readers: These work with Windows’ built-in smart card driver, so you don’t need to install extra vendor software. The universal PC/SC APIs (like the PCSC NuGet package) will handle communication.
• Custom/Proprietary Readers: Yes, you’ll almost always need the vendor’s driver or SDK. These devices use closed communication protocols that don’t align with industry standards. Without the vendor’s documentation or API, you’ll struggle to send/receive data correctly—even if you can detect the device via USB/serial, you won’t know what commands to send.

Pro Tips for Working with Unknown Readers: #

1. Check the Device Manual: Look for mentions of PC/SC, ISO standards (like ISO 14443 for 13.56MHz), or supported communication protocols (serial, HID, USB).
2. Test for PC/SC Compatibility: Use Windows’ built-in scardsvr service (you can check it via Services.msc) and tools like PCSC Diagnostics to see if your reader is detected as a PC/SC device.
3. Reach Out to the Vendor: Even if it’s an unknown brand, many manufacturers will provide SDKs or command docs if you ask—don’t skip this step!

内容的提问来源于stack exchange，提问作者khorshid