Master Terminal Config:  

Use this terminal config to get started:


5F3601029F1A0208409F3501219F33036028C89F4005F000F0A0019F1E085465726D696E616C9F150212349F160F3030303030303030303030303030309F1C0838373635343332319F4E2231303732312057616C6B65722053742E20437970726573732C204341202C5553412EDF260101DF1008656E667265737A68DF110100DF270100DFEE150101DFEE160100DFEE170105DFEE180180DFEE1E08D09C20D0C41E1600DFEE1F0180DFEE1B083030303135313030DFEE20013CDFEE21010ADFEE2203323C3CDFEF4B037F0000DFEF620101DFEF7D0103DFEF7E06500150055036DFEF5A624F5056575A8284878A959A9B9C5F245F2A5F305F349F029F039F069F079F089F099F119F0D9F0E9F0F9F109F129F1A9F1E9F219F269F279F339F349F359F369F379F389F399F3C9F409F419F539F6E9F7C5F205F285F2D5F56DFEE23DFEE26FFEE01


Terminal entry mode (9F39) is returning the incorrect value. How come? How do I resolve this?  

We can modify this in our terminal configs - IDTECH defined tag DFEE17 to set the value of 9F39.

In your current terminal configs (example below), change the value of DFEE17 from 7 -> 5. 
This tag was set to 7 in our default example as we have the same EMV L2 kernel being used across our contact/contactless family.

5F 36 01 02 9F 1A 02 08 40 9F 35 01 21 9F 33 03 60 28 C8 9F 40 05 F0 00 F0 A0 01 9F 1E 08 54 65 72 6D 69 6E 61 6C 9F 15 02 12 34 9F 16 0F 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 9F 1C 08 38 37 36 35 34 33 32 31 9F 4E 22 31 30 37 32 31 20 57 61 6C 6B 65 72 20 53 74 2E 20 43 79 70 72 65 73 73 2C 20 43 41 20 2C 55 53 41 2E DF 26 01 01 DF 10 08 65 6E 66 72 65 73 7A 68 DF 11 01 00 DF 27 01 00 DF EE 15 01 01 DF EE 16 01 00 DF EE 17 01 05 DF EE 18 01 80 DF EE 1E 08 D0 9C 20 D0 C4 1E 16 00 DF EE 1F 01 80 DF EE 1B 08 30 30 30 31 35 31 30 30 DF EE 20 01 3C DF EE 21 01 0A DF EE 22 03 32 3C 3C DF EF 4B 03 7F 00 00 DF EF 62 01 01 DF EF 7D 01 03 DF EF 7E 06 50 01 50 05 50 36 DF EF 5A 62 4F 50 56 57 5A 82 84 87 8A 95 9A 9B 9C 5F 24 5F 2A 5F 30 5F 34 9F 02 9F 03 9F 06 9F 07 9F 08 9F 09 9F 11 9F 0D 9F 0E 9F 0F 9F 10 9F 12 9F 1A 9F 1E 9F 21 9F 26 9F 27 9F 33 9F 34 9F 35 9F 36 9F 37 9F 38 9F 39 9F 3C 9F 40 9F 41 9F 53 9F 6E 9F 7C 5F 20 5F 28 5F 2D 5F 56 DF EE 23 DF EE 26 FF EE 01

To modify this, just pull up your existing terminal configurations and edit the value of DFEE17.
That should cause all your transactions to be flagged correctly as 5 rather than 7.



This output tag value is not documented in the documentation!  

Our documentation needs to be updated to clearly reflect all possible scenarios, and error codes. This is a work in progress as we are working on getting this product EMV L3 certified, as well as preparing a small booklet.


What are all these proprietary tags? Where do I find more information about these?  

Proprietary tags can be found on our knowledge base. These are TLVs (tag, length, value) that IDTECH has defined in order to accommodate settings, behaviors, and storage of certain elements to better help you, the customer implement your solution.

Latest revision here: https://atlassian.idtechproducts.com/confluence/download/attachments/30479625/80000503-001%20ID%20TECH%20TLV%20Tag%20Reference%20Guide%20rev.%20F.pdf?version=2&modificationDate=1497283830963&api=v2 


I want my own tags to show up in the display. How do I go about doing this?  


IDTECH has defined tag DFEF5A. An example below on how this is utilized: (see the terminal configuration)


5F3601029F1A0208409F3501219F33036028C89F4005F000F0A0019F1E085465726D696E616C9F150212349F160F3030303030303030303030303030309F1C0838373635343332319F4E2231303732312057616C6B65722053742E20437970726573732C204341202C5553412EDF260101DF1008656E667265737A68DF110100DF270100DFEE150101DFEE160100DFEE170107DFEE180180DFEE1E08D09C20D0C41E1600DFEE1F0180DFEE1B083030303135313030DFEE20013CDFEE21010ADFEE2203323C3CDFEF4B037F0000DFEF620101DFEF7D0103DFEF7E06500150055036DFEF5A624F5056575A8284878A959A9B9C5F245F2A5F305F349F029F039F069F079F089F099F119F0D9F0E9F0F9F109F129F1A9F1E9F219F269F279F339F349F359F369F379F389F399F3C9F409F419F539F6E9F7C5F205F285F2D5F56DFEE23DFEE26FFEE01


As you can see in the large blob of text - DFEF5A is there! How do I use it?

DFEF5A is a TLV that defines ALL the output tags for the Augusta. The default value of DFEF5A is what comes out of the Augusta QC KB on an insert when this value has not been defined.

In the example above - following TLV structure, we have DFEF5A 62 XXXX .. etc. 62 defines the length of the tag names. 

You can see tag 4F, 50, 56, 57... in this example. Here is where you can customize all the output tags you might need for your certification / operational use cases!

In the example above, the total length of the tags sum up to 62 hex nibbles.


For another example - let's say we only wanted 9F1E output in the return tags.


We'd do the following for our terminal config:

5F3601029F1A0208409F3501219F33036028C89F4005F000F0A0019F1E085465726D696E616C9F150212349F160F3030303030303030303030303030309F1C0838373635343332319F4E2231303732312057616C6B65722053742E20437970726573732C204341202C5553412EDF260101DF1008656E667265737A68DF110100DF270100DFEE150101DFEE160100DFEE170107DFEE180180DFEE1E08D09C20D0C41E1600DFEE1F0180DFEE1B083030303135313030DFEE20013CDFEE21010ADFEE2203323C3CDFEF4B037F0000DFEF620101DFEF7D0103DFEF7E06500150055036DFEF5A029F1E


Our output from the Augusta QC KB would now only have 9F1E.


Can I have IDTECH do a custom part number with my custom tags to save me time, or can I order this configuration from distribution?  

Absolutely. However - your sales rep will have to work with you to ensure that we understand exactly what your requirements are.

This will need to go through our internal CPR process to be qualified by our sales, operations, and engineering departments before there is a specific part number you can order - which may take upwards to a month.

The process can be made simpler by having a configurator tool written on your end (which our Sales Engineers can help you with) to scale your production pipeline and also afford you much more control in the long run.



I swiped a card, and I'm getting no feedback. Why?  

Couple of reasons why this behavior could be happening.

Scenario A:  

Provided you set your terminal configurations for DFEF61 to 1, default behavior for swiping a chip card is no output (regardless of card brand).

If the card does not have a chip on it, the reader should allow the swipe. 

Scenario B:

MSR Auto Mode needs to be enabled. This can be done with the Universal Demo utility or by issuing a low level command to the device. 

Scenario C:

Your device is in USB HID mode. If you are expected output as if you typed on a keyboard, your device needs to be in USB-KB mode for it to function as so, along with being set to Auto Mode.

In USB HID mode, you would 'start MSR' and get a response back with data. 

Scenario D:

You have an Augusta S device with no key injected. A SRED product (denoted by 'S') for the Augusta will not function properly until the device has a DEK injected (data encryption key). 


How do I allow fallback when the device is missing an AID / no matching AID, or if the card fails to read?

As of FW version v16, the Augusta QC KB allows for this behavior.

The followings tags and implementation are heavily covered in this document - Handling Augusta QC KB Fallback behavior, for EMV L3 integration

At a high level, you need to specify the following terminal configurations:


The length of the fallback output doesn't match up with TLV Structure? What's the matter?


Due to the Augusta returning ASCII embedded in the return MSR data (as how our other readers function), we had to figure out the best way to move forwards.

Tthe length you see is a character count rather than the actual length, including a carriage return. I performed a bit of a proof below on this guide - Handling Augusta QC KB Fallback behavior, for EMV L3 integration


I'm seeing a '80' come back as the value of 9F39. What does that mean?

'80' is Fallback to Magnetic Stripe. 

Other values of 9F39 can be found here: What are the 'PAN Entry Modes' of tag 9F39?