Anyone else encountered issues with RF IDeas contactless readers and the Canon USB MEAP driver? The MEAP driver is converting "tildes" in the string to "back ticks". Same reader with the same config works perfectly on a PS200.
This depends on which version of Pharos iMFP for Canon you are using.
For Legacy devices (not iR-Advance devices) Pharos iMFP for Canon, version 2.x is used. This version didn't convert shifted USB scan codes to shifted ASCII codes. In other words all keystrokes sent by the reader are converted to lower case or un-shifted keys. Note that Pharos is no longer actively developing on this timeline.
For iR-Advance devices, Pharos iMFP for Canon, version 3.x is used. This version does convert shifted USB scan codes to shifted ASCII codes but this support was just added to the latest version, 3.3.2.
Your actions are this:
It has been my experience that most touchless cards rarely send anything but ASCII numbers or a binary blob that contains a card ID. They can be programmed to send pre and post characters that surround the card data. I'm curious, can you tell me if the cards are coming from the factory with the ~ in the card data or are you programming the cards with the ~ in the data or are you programming the reader to insert the ~ before or after the card data?
Upgrading to 3.3.2 resolved the issue. We program the readers to insert the ~ before the card data to match the media type in our accounting system.
Maybe just reconfigure the RF Ideas reader so that the ~ character is not output (unless its part of the actual card data)
The reader can be reconfigured using the RFIdeas PCprox config program from https://www.rfideas.com/support/downloads
I recommend saving the settings on the existing reader through the PCProx config app BEFORE you start changing the settings in case you need to revert back.
Thanks for the info Nic. If we couldn't resolve from the client end we would have explored creating a new, compatible media type in our accounting system.
Retrieving data ...