Skip to end of metadata
Go to start of metadata
How do I use the UniMag reader?
The UniMag series of readers, including the UniMag Pro, UniMag II, and Shuttle, are card reading devices which ID Tech has published a free demo and utility to the Google Play store, which let basic device function be explored, such as attempting a connection and sending commands including a method for all these devices to swipe cards. Please note that the UniMag Pro does not support two way command exchange, and only the UniMag II and Shuttle can respond to commands such as get serial number. All of these devices follow the same method to swipe a card, when the associated reader type is selected in application (where applicable).
The following steps are intended as a simple set of instructions to obtain and use the app with our reader, as well as instructions to include and apply the latest set of configuration testing confirmation results, which we have hosted to a fixed location in our public-facing knowledge base.
- Search "ID Tech UniMag" or "UniMag" to find the UniMag Demo. Please note that the UniMag Utility is a similar overall software application, but this guide is specific to using the Demo program.
- After obtaining and opening the app, you will be prompted to select a reader type. You may identify the device by its name or matching model number, which should appear on the device and box materials. Please note that the Shuttle's device label is obscured by a protective cover. This statement is not intended to instruct the removal of the cover, but to clarify the location of the identifying labels associated with each of the UniMag products. There are multiple individual model configurations among the Shuttle, but any ID Tech UniMag series reader with such a protective cover is conventionally considered a Shuttle, in terms of the reader-type selection of the software demonstration published to the Play Store.
- When on the next screen, a static but not most current config file is included. Should the Android device not be within that present config, the Software Development Kit, or SDK, info given among the upper display window will report an XML version of null. In this case, consider checking for present confirmed compatibility support on the product page and also consider referring to our latest config file which was generated through developer testing.
- The product pages are here, but please note that each device has a separate confirmation list, but we have additional positive results among each config .xml file which can work to other varying degrees (these categories include unknown and maybe supported) http://idtechproducts.com/products/mobile-readers/msr-only although the lists on the product pages only mentioned confirmed support through our in house testing effort.
- The current most latest config file is available here - https://atlassian.idtechproducts.com/confluence/download/attachments/30479625/umcfg.5.0.10.xml?api=v2
- Reloading an XML to connection is described in specific detail in step 5 below
- If connection is attempted without reloading any .xml, and fails, then please refer to the UniMag FAQ for troubleshooting steps which can help ultimately get the reader connected - FAQ - Mobile Card Readers
- Please also refer back to the FAQ in case connection times out from either reloading another .xml or attempting autoconfig, and in case connection can't be made, then please consider contacting ID Tech support for additional assistance.
- Some Android devices may not be compatible with ID Tech audio jack readers, and some may not be compatible without additional consideration in our design, including a customized design change. To the former, any Android device without a built-in microphone to the audio jack can't support our reader, and to the latter, some devices have a myriad of conditions, including to mention only one, not producing enough output voltage from the audio jack, that require some other, to the ID Tech product, design-level change, in order to be made compatible
- If connection is not attempted, and a match is available per the current .xml, then please save that file to local storage of the Android phone or tablet, and refer to Settings within the menu in order to reload that file and apply its present support.
- To reload an .xml, first save a config to the Android device's local storage. Two simple ways ID Tech can recommend are to transfer the file from a Windows computer after downloading it there and using a USB data cable (these are commonly supplied with Android mobile devices), and also to download it from an email client, which the default directory is typically "Download" or "Downloads". Downloading directly from a browser in Android, such as to a Chrome or other web app, might present some issue, but could be possible, depending on the Android device and web browsing app.
- Reload XML is an option from Settings. Settings will appear after launching the Menu. The autoconfig walkthrough on our PKB can help illustrate how to get into the menu when it is not obvious to any particular Android device - How to use Autoconfig?
- Reload XML will report as successful or else give a prompt to remove and reattach the reader in order to attempt a connection after loading that config. Should another message occur, then please try re-saving the .xml to the Android device, as some transfer methods can incidentally corrupt the file.
- In case a path to attempting connection with a manually loaded config is not successful, please consider contacting ID Tech support for assistance further from this guide's instructions
- In regards to autoconfig, when there is no present confirmed profile in the latest .xml, then please consider attempting this as a means to get a connection within the demonstration. This tool in success does require additional effort to translate to either ID Tech's confirmed results or potentially also another software product including our SDK library or some similar means connecting our hardware to a finished product.
- Please note that dedicated support is intended for any use of our UniMag devices as other than specifically towards development or another OEM purpose, they are not considered ready for finished use entirely on their own. The specific value or integration added in another product including ours varies.