Forum Replies Created

  • Re: Reply To: Can not read the DESFire application info with TapLinx SDK Sample App

    3. January 2022 at 14:16
    in reply to: Can not read the DESFire application info with TapLinx SDK Sample App
    Dear Treeway,

    Error returned is 0x6700 as can be seen, with CLA (ISO7816 APDU) value of 0x00. As per DesFIRE datasheet it means "Wrong or inconsistent APDU length". You are sending just 0x60 byte. Which command would you like to send?

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: DesfireEV2 – invalid length exception

    3. January 2022 at 14:01
    in reply to: DesfireEV2 – invalid length exception
    Dear Ritesh,

    Details on Authentication are part of MIFARE DesFIRE datasheet.

    Example with use of TapLinx SDK is within "TapLinx example application", file WriteActivity.java, line 1162.

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Tpllinx Android SDK Invalid Parameters! {Invalid Value for SdmAccessRights}

    3. January 2022 at 13:54
    in reply to: Tpllinx Android SDK Invalid Parameters! {Invalid Value for SdmAccessRights}
    Dear Liban,

    In order that SDM is working, also UID mirroring needs to be enabled, you need to set Offset positions for each as well. Something like:

    `fileSettings.setUIDMirroringEnabled(true);
    fileSettings.setUidOffset(new byte[] { (byte) 0x1A, (byte) 0x00, (byte) 0x00 });
    fileSettings.setSdmMacOffset(new byte[] {(byte) 0x42, (byte) 0x00, (byte) 0x00 });
    fileSettings.setSdmMacInputOffset(new byte[] {(byte) 0x42, (byte) 0x00, (byte) 0x00 });
    fileSettings.setSdmReadCounterOffset(new byte[]{(byte) 0x29, (byte) 0x00, (byte) 0x00});
    fileSettings.setSdmAccessRights(new byte[]{(byte) 0x12, (byte) 0xFE}); //FileAR.SDMMetaRead (ENCPICCData) key = 0xE, FileAR.SDMFileRead (CMAC) key = 0x2, RFU = 0xF, FileAR.SDMCtrRet key = 0xE
    ntag424DNATT.changeFileSettings( (byte) 0x02, settings);`

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Defire EV1 authencation

    3. January 2022 at 13:44
    in reply to: Defire EV1 authencation
    Dear Sameer,

    Please check following:
    - Application with ID F013F2 is created on the MF DF
    - Application is selected (with SELECT) command before you are trying to Authenticate.

    Thank you and best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: TapLinx Developer Center login error

    3. January 2022 at 13:37
    in reply to: TapLinx Developer Center login error
    Dear users,

    Sorry for the inconvenience. We faced user authentication fails. Issue has been solved.

    Happy coding in 2022.

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Invalid MAC problem

    26. August 2021 at 15:01
    in reply to: Invalid MAC problem
    Hello Daniel,

    Is it "Data 1" ASCII converted to HEX? What is the line where you assign the value to "data" variable? You are printing into a Log "dataToWrite" but in .writeData you are using "data".

    Log.e("a",dataToWrite);
    desFireEV1.writeData(0, 0, data,IDESFireEV1.CommunicationType.Echipered);

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Invalid MAC problem

    20. August 2021 at 10:54
    in reply to: Invalid MAC problem
    Dear Daniel,

    Please post as well:
    • data you write with which you do not see the issue
    • data you write and you see the issue


    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Problem when calling "writeRecord" for cyclic log file with desfireEV3

    20. August 2021 at 10:40
    in reply to: Problem when calling "writeRecord" for cyclic log file with desfireEV3
    Dear Florian,

    This is a bug with Taplinx 1.8 and we are working to resolve this one for the next Release.

    As of now, you can do a workaround and use another similar API that passes Communication Type as parameter and that shall work.

    Use this API : writeRecord(final int fileNo, final int offsetInRecord,
    final byte[] data, final CommunicationType comSettings)


    The above API is similar to what you have, except that it takes one additional parameter Communication Type.


    Thank you,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: TapLinx Android 1.8 throws exception for Plus X SL1 card

    9. August 2021 at 14:07
    in reply to: TapLinx Android 1.8 throws exception for Plus X SL1 card
    Dear Norbert.

    Please check Release Note of TapLinx 1.8., chapter 1.1.:

    Known issues for V1.8.
    1) PLUS EV2 SL1 is not completely supported. PLUS Ev2 SL0 and SL3 are fully functional.

    Best regards,
    TapLinx team


    + 0  |  - 0

    Re: Reply To: Debit Credit Desfire

    6. August 2021 at 14:31
    in reply to: Debit Credit Desfire
    Dear Daniel,

    Did you select targeted value file before?

    Thank you,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Problem when calling "writeRecord" for cyclic log file with desfireEV3

    6. August 2021 at 14:29
    in reply to: Problem when calling "writeRecord" for cyclic log file with desfireEV3
    Hello Florian,

    Please excuse inconvenience. We are taking look at it and will respond as soon as possible.

    Thank you,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: DESFire : apdu must be at least 4 bytes long

    6. August 2021 at 12:02
    in reply to: DESFire : apdu must be at least 4 bytes long
    Hello fperinel,

    Are you trying to Authenticate on the PICC level or Application level?

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Debit Credit Desfire

    5. July 2021 at 12:24
    in reply to: Debit Credit Desfire
    Hello,

    A "Value file" needs to be created on the MIFARE DesFIRE card, within Application. The Value file can be read with the GetValue command. The value can be manipulated
    with Credit, Debit and LimitedCredit commands, respectively. Transactions confirmed by CommitTransaction commands.

    Take a look to MIFARE DesFIRE datasheets. (search for DS on MIFARE DesFIRE Light webpage )

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Can we use the library to a flutter project?

    5. July 2021 at 12:18
    in reply to: Can we use the library to a flutter project?
    Hello,

    At the moment there is no plan to support Android Flutter project.

    Best regards,
    TapLinx team

    + 0  |  - 0

    Re: Reply To: Use TapLinx library on a Java Card

    21. May 2021 at 12:37
    in reply to: Use TapLinx library on a Java Card
    Dear dexter,

    Java Taplinx SDK
    You can try using "apduExchange(byte[] apduData)"

    found in:
    com.nxp.nfclib.interfaces
    Interface IApduHandler

    Best regards,
    TapLinx team

    + 0  |  - 0
Viewing 15 posts - 31 through 45 (of 1,152 total)