This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RI-SMD-MRD2: No reader identified: Connect reader

Part Number: RI-SMD-MRD2
Other Parts Discussed in Thread: RI-STU-MRD2, MRD2EVM,

Hi team,

Our customer is using the  RI-STU-MRD2 reader module, however, upon connecting the board, the software does not recognize it. An error message "No reader identified: Connect reader”  occurred.  Any suggestions to solve the error?




Do we have any other transponder and reader evaluation kits aside from RI-STU-MRD2?

Thank you.

Regards,
Carlo

  • Hello Carlo,

    there are some questions from my side. You wrote the customer is using the RI-STU-MRD2 which is only the reader module not the EVM. The module itself can be connected with USB or a serial port connection. Which connection is used by the customer? Is the PC using WIN10?

    When using a WIN10 PC and the USB connection the system will automatically install a virtual COM port driver. This should be visible in the Windows Device Manager when connecting the reader. If Windows will not recognize the module and will not automatically assign a COM port, then something seems to be wrong with the USB connection or the module in not functioning correct.

    Other LF reader evaluation kits are not available. The MRD2EVM is the only one.

    Best regards,

    Helfried

  • Hello Helfired,

    Good day.


    Apologies, the customer is using the RI-SMD-MRD2 and not the RI-STU-MRD2. The same error above was still encountered by the customer after reinstalling the driver but the software does not recognize that a board is connected. The customer is getting a “ding” sound when the USB cable is plug into the laptop and the red and yellow LED is flashing when the CRDM tie high.

    Please advise with the workaround.Thank you


    Regards,
    Carlo

  • Hello Carlo,

    the RI-SMD-MRD2 and the RI-STU-MRD2 are functional the same. The difference is only in the size and in the way the module can be contacted  (SMD versus pins).

    Has the customer checked in the Windows Device Manager if a COM port is assigned to the reader or if any error status is shown?

    Also the USB connection to the MRD2 should be verified. 

    Is this a problem with a single reader module or is this a general problem the customer has. In case of a single module it could also have a defect.

    Best regards,

    Helfried