Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate EV3 Support #13

Open
johnnyb opened this issue Jun 10, 2024 · 5 comments
Open

Investigate EV3 Support #13

johnnyb opened this issue Jun 10, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@johnnyb
Copy link
Owner

johnnyb commented Jun 10, 2024

Just received a package of EV3 tags. They don't work with the example app out of the box, so using this ticket to record what I'm seeing/messing with.

@johnnyb johnnyb added the enhancement New feature or request label Jun 10, 2024
@johnnyb johnnyb self-assigned this Jun 10, 2024
@johnnyb
Copy link
Owner Author

johnnyb commented Jun 10, 2024

Tag Tech reports: android.nfc.tech.IsoDep, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable

Here is the initial communication:

BytesSending: 00A4000C02E11000
BytesReceived: 6A82
BytesSending: 90640000010000
BytesReceived: 009100
BytesSending: 9071000002000000
BytesReceived: 91AE
BytesSending: 9071000002000000
BytesReceived: 91AE

@johnnyb
Copy link
Owner Author

johnnyb commented Jun 10, 2024

@johnnyb
Copy link
Owner Author

johnnyb commented Jun 10, 2024

Created branch ev3-support (nothing in it yet).

@MichaelsPlayground
Copy link

As a starting point you should select the tag by this command sequence:

00 a4 04 00 07 d2 76 00 00 85 01 00

Thats the "byte SELECT_MODE_BY_FILE_IDENTIFIER = 0x00" method using the default DESFire identification "d2 76 00 00 85 01".

This is similar to the command "IsoSelectFile.run(communicator, IsoSelectFile.SELECT_MODE_BY_FILE_IDENTIFIER, Constants.DF_FILE_ID);" but using "d2 76 00 00 85 01" instead of "byte[] DF_NAME = new byte[]{(byte)0xd2, 0x76, 0x00, 0x00, (byte)0x85, 0x01, 0x01};" for the NTAG 424 DNA tag.

The next step could be a "list applications" command (that would give no data as no application is available on a fabric tag (the NTAG 424 DNA tag has an application pre-installed). The following commands would be to create an application and create a (Standard) file. From this point you could use the read and write commands available in the library (after a "select application" and an authentication, depending on the file settings).

I'm glad that you are trying to expand the library to DESFire (EV3) tags as well !

Greetings
Michael

@johnnyb
Copy link
Owner Author

johnnyb commented Jun 13, 2024

Many thanks! I'll give this a try soon hopefully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants