Related Manuals for Tokenworks IDWedgeBT
Summary of Contents for Tokenworks IDWedgeBT
- Page 1 IDWedgeBT™ Users Guide Serial Port Profile Mode Version 2.3 Software Confidential Page 1 5/31/2013...
-
Page 2: Copyright
® ® ® TokenWorks , CardVisor , CardTool , IDVisor and IDWedge are registered trademarks of TokenWorks, Inc. IDWedgeBT is a TokenWorks Inc trademark. Version Description of Change Auth Date Initial 07272012 Change wording for SD card access 08062012 Update Config.xml, firmware rev 1.5... -
Page 3: Table Of Contents
Copyright ........................... 2 1 Introduction......................... 4 1.1 Document overview....................4 1.2 Operational overview....................4 1.2.1 Power ......................... 5 1.2.2 Battery........................ 5 1.2.3 Function Button ....................5 1.2.4 Connection Status ....................5 Configuration file ...................... 6 2.1 Config.xml......................... 6 2.1.1 Version....................... 7 2.1.2 Name ........................ -
Page 4: Introduction
1.2 Operational overview The diagram below shows the top view of the IDWedgeBT scanner and the location of the LED indicators and button switches used during the operation of the device. -
Page 5: Power
Continue to hold the Battery button for 3-4 seconds, and then release it. When the USB cable is connected to a PC, the IDWedgeBT will now appear as an external USB memory device, and the Connection Status LED will stay lit. -
Page 6: Configuration File
2 Configuration file The IDWedgeBT maintains configuration file called Config.xml. This file stores the application parameters. If the file gets erased, it will be created automatically using default settings. If the file contains editing errors or is corrupted and cannot be opened, then a file called ConfigError.txt will be written to the SD card. -
Page 7: Version
3 for details on Auth setting. 2.1.5 FuncKey FuncKey holds a custom string, 10 character maximum length, with a default value of TokenWorks. The FuncKey is also used to re-program the unit. 2.1.6 CreditCard CreditCard Controls the output of Credit Card scans 2.1.7 1DBarcode... -
Page 8: Scanmsg
“MNR” which means Mag No Read. 2.2 Reading/Writing Config.xml To Access the Config.xml file, you must boot the IDWedgeBT while holding the battery button as described in section 1.2.2. Once you have connected a USB cable and can explore the contents of the SD memory card, you will be able to read and write the Config.xml file. -
Page 9: Credit Card Csv String
The Magnetic Formula used to send fields to the host and is stored in a file on the SD card. To Access the Config.xml file, you must boot the IDWedgeBT while holding the battery button as described in section 1.2.2... - Page 10 stored as a comma separated string of 10 integer values. Any formula with less than 10 values will be rejected. If you do not need all of the 4 possible fields, then populate the unused track, field and offset with zeros. Example of first line of Magnetic.txt: 1,2,4,6,9,2,1,5,6,5 (Track 1, offset1 = 2, length1 = 4, offset2 = 6, length9 = 5, track 2, offset1 = 1, length1 = 5, offset2 = 6,lenght2 = 5).
- Page 11 The Magnetic formula and parsing has been designed to handle cards on any of the 3 possible tracks. The Magnetic formula applies to cards that have 25 or less characters of information encoded on any track (Except old New Mexico ID/DL). The following list of cards is used to identify Drivers License/ID cards, Credit Cards and AAA cards.
-
Page 12: Serial Protocol
Revision information: Rev 1.8 and newer allows magnetic card of less than 10 characters to be parsed, previous versions of IDWedgeBT required that all cards have 10 or more characters encoded. 4 Serial Protocol The outgoing messages will be bounded by start and end characters:... -
Page 13: Incoming Bluetooth Commands And Outgoing Responses
Magnetic Formula Error (MFE) 01 02 4D 46 45 03 04 Magnetic offset error (OTx) x=track # 1-3 01 02 4F 54 3x 03 04 * Note: the MNR, MND message will append the track# for Magnetic parsing. 4.2 Incoming Bluetooth Commands and Outgoing Responses Once the Host and the scanner are paired and connected, the host can send commands to the IDWedge. -
Page 14: Speaker Volume
4.2.3 Speaker Volume The Speaker Volume command controls the Volume of the speaker in the Scanner There are 4 possible commands Send: 01 <SPVOLU=OFF> 04 Send: 01 <SPVOLU=LOW> 04 Send: 01 <SPVOLU=MEDIUM> 04 * Default Send: 01 <SPVOLU=HIGH> 04 byte[] SPLOW = { 0x01, 0x3C, 0x53, 0x50, 0x56, 0x4F, 0x4C, 0x55, 0x3D, 0x4c, 0x4F, 0x57, 0x3E, 0x04 };... -
Page 15: Write Registration
4.2.5 Write Registration The Write Registration will send a 16-byte number or characters to the Scanner to be saved in the Scanners EEPROM memory, the length must be 16 or the message will not be recognized. The scanner will also triple beep on a successful write command. -
Page 16: Appendix 1 - Power On Bit (Built In Test) Description
HID application will only light up the first LED, and the SPP application will light up LED1 and 2. The IDWedgeBT USB Keyboard application will light three LEDs 1,2,3. This is helpful for all users to identify what application is running on the device. - Page 17 Appendix 3 – Auth settings Authentication can have the values 0, 1, 2, or 4, depending on the mode desired with some limitations on implementation. // With this mode, the module uses Bluetooth version 2.0 NO encryption (open mode). This mode is useful for legacy devices that do not need security. For this mode to work, both devices must support open mode.
Need help?
Do you have a question about the IDWedgeBT and is the answer not in the manual?
Questions and answers