• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 17 subscribers
  • Views 2841 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLP-RFID2D reader & MLX90129

Bochao Lu
Prodigy 70 points
Other Parts Discussed in Thread: RF430FRL152H

Hi,

I'm working on a project to use MLX90129 and external sensor as RFID powered sensor for my bioengineering Project. I bought a reader DLP-RFID2D. Since MLX90129 is not common RFID tag, I need to use the RFID reader to send some ISO15963 command to the tag. I tried to use Code Composer studio v6 to send programs to DLP-RFID2D, but the CCS sent an error back said "no USB FET found". The screenshot is attached.

DLP-RFID2D is simply a USB stick, and there's no way to plug in a MSP-FET430UIF. Does this mean I can't use CCS to program the DLP-RFID2D?  Is there any other way to send ISO15963 standard command using DLP-RFID2D? 

Is there any people that have experience with DLP-RFID2D or MLX90129 can help me out of this??

Thank you very much.

  • 0
    TI__Guru**** 169234 points

    Hi,

    I never heard about this development kit before, but a quick glance at its datasheet does not mention any JTAG debugging capabilities on the dongle (DLP-RFID2D). The schematic diagram at the last page, which is related to the bigger board with the LCD display, shows a small 12-pin JTAG header on the DLP-RFID2U and that would allow it to be connected to CCS and program the MSP430 that will customize the RFID operation mode.

    However, it says there the kit is compatible with the Texas Instruments demonstration GUI - this tool may allow you to configure and format the data sent. However, I will forward this to thread to the experts at the wireless connectivity forum so you could get a better educated response.

    Regards,

    Rafael

     

  • 0 in reply to desouza
    Prodigy 70 points
    Thanks Rafael! Do you know any Texas instruments demonstration GUI Tutorial or introduction datasheet I can use to learn this? Somehow I can't find any of that online.
  • 0 in reply to Bochao Lu
    TI__Mastermind 40400 points

    Hi Bochao,

    Instead of reprogramming the MSP430, you can send a custom host command for the ISO 15693 commands you require. 

    Have a look at section 4.1 of the datasheet below.  This describes the host command structure, but does not describe the "Raw Write" Command that may be useful to you. 

    http://www.mouser.com/ds/2/117/dlp-rfid2-ds-v10-215391.pdf

    The raw write command code is '18'.  When you use this command, everything after the 18 is what is transmitted over the air.

    Here is an example of an ISO14443B Attrib command using the raw write '18' command. 

    0111000304181DBC2E8C8E000805000000 - Entire Host Command

    01-start byte

    11 -length

    000304 - constant

    18 -request command

    1DBC2E8C8E00080500 - the data

    0000 - end of EVM packet token

    With the 18 request command type the data is essentially what is transmitted over the air minus

    the SOF, EOF and CRC bytes.

    The return format for this example attrib is:

    [80] - the returned data is enclosed in brackets.

     

    Also, have you seen our recently released RF430FRL152H Sensor transponder?  I have released an app note for interfacing with a thermistor and the EVM also interfaces with many other sensors.  Have a look and see if this could offer some value to your application.  If you have any questions, please let me know.

    http://www.ti.com/product/RF430FRL152H

  • 0 in reply to Eddie LaCost
    Prodigy 70 points

    Thank you very much for your help.

    I still have some further questions.

    1. It seems the GUI I got is different from the GUI you showed in your application report. My GUI look like this.

    Have you ever used this GUI? How do I use this GUI to write the configuration? The attached file is the application note of MLX90129, which I'm using for my project. If you look at the 4.1memory setting on page 13, you will find the settings I need to write. I have no idea how to write these settings. On one hand I don't know how to use this GUI to write settings, and on the other hand I don't know what command to use to write settings. 

    90129 application note.pdf

    2.

    01-start byte

    11 -length

    000304 - constant

    How do I know everytime I send a command which byte to start with, what length and what constant to use?

    Are these always the same for every command?

    Thank you very very much!

    Bochao

  • 0 in reply to Bochao Lu
    TI__Mastermind 40400 points

    The GUI in the application note that I referenced is specific to use with the RF430FRL152H sensor transponder, so it would not apply to the Melexis part.  I was just throwing that out there that you could also evaluate the RF430FRL152H as it offers similar functionality.

    With the EVM GUI that you show, you can send custom commands using the test tab.  To do this, follow the steps below.

     After connecting to the board, go to the test tab.  Check the box "expert".  This will allow you to keep the register settings for ISO 15693 after changing tabs. 

    Go back to the 15693  tab.  Select your flags(typically only high data rate is selected).  Click Set Protocol(this sets the registers for ISO 15693).

    At this point, you can test the communication by sending a inventory command.

    If you go back to the test tab, you can now send custom commands as well.  If you use the send button, you do not need to include the start byte, length or constant.  It will automatically be calculated and added by the GUI.  You can see this in the log window after you send a command.  If you use send raw, you need to include the entire packet. 

     

    How do I know everytime I send a command which byte to start with, what length and what constant to use?  You always start with the start byte.  Length should be calculated based on the length of the command you are sending.  The constant is always the same.

    Are these always the same for every command?  Start and constant are always the same.  The length could vary depending on the length of your command.

     

  • 0 in reply to Eddie LaCost
    Prodigy 70 points
    Hi Eddie,
    Thank you for your help. Those are very detailed answers.

    I just found send command one by one is kinda tedious. Is it possible I use the "Test New Program" under Test tab to load a series of commands and run it? It seems the Test New Program can recognize .cpp file. What file or language I should use then? Do you have sample files or programs that can be used by Run TP?

    Thank you so much.
    Sincerely,
    Bochao
  • 0 in reply to Bochao Lu
    TI__Mastermind 40400 points

    Bochao,

    The test new program function is not available. 

    You could also test with a terminal emulator.  I like to use Docklight which allows you to create and save the command strings.

    http://www.docklight.de/

  • 0 in reply to Eddie LaCost
    Prodigy 70 points

    Hi Eddie,

    I have connected MLX90129 as the reference temperature tag design on Page 2 of the application note.( I have attached the application note that I am using.)  Then I did following:

    1. check the expert under test tab

    2. go back to ISO15693 tab and choose dual sub-carrier. Then set protocol.

    3. choose inventory and execute. I see this in the log.

    19:11:26.015 --> 010B000304140501000000
    19:11:26.757 <-- 010B000304140501000000
    ISO 15693 Inventory request.
    [,40][,40][,40][,40][,40][,40][,40][,40][,40][,40][,40][,40][,40][,40][,40][,40]D

    4. Then I try to use findtag to see if my tag is activated or not, but there's no tag found. 

    5. I use the send button to send some command in order to do the same configuration in section 4.3 on Page 14 of the application note. 

    --> 010D0003041043210971700000
    23:29:07.097 *** Read TIMEOUT ***

    I'm just trying to send the very first RFID command in section 4.3. -----4321097170

    I guess maybe the request command 10 is not right. 

    My question is :

    1. I don't see any response from my tag. How do I use my inventory command?

    2. in order to send those commands in section 4.3 on page 14. what request command I should use?

    01+length+000304+??+4321097170+0000  what should I use to replace the question mark?

    Thank you very much. 

    Sincerely,

    Bochao Lu

    90129_AN_Sensor_tag_001.pdf