• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 765 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

LDC1612EVM: Request for communication protocol

LDC1612EVM: Request for communication protocol

Edgar Ortega
Intellectual 270 points
Part Number: LDC1612EVM
Other Parts Discussed in Thread: LDC1614EVM, LDC1614

Hi,

I've developed my own hardware based on a LDC1614EVM and LabView USB raw interface.

Both my own hardware and LDC1614 stream raw data to my application, however there is a point where the stream starts to transfer the last 16 or 20 bytes of the pocket at the on the first 16 or 20 bytes of the pockets and the balance is on the end.

I send:

4C 05 01 00 06 01 29 04 04 30 2A C1,

Then I read 32 bytes

After I start reading 32 bytes every 50ms, and for some time the replies are:

4C30 0100 092A 0151 42CB 0150 5FFF 1C00 0000 0000 0000 0000 0000 0000 0000 001C

At some point the string shifts to:

1C00 0000 0000 0000 0000 0000 0000 0000 001C4C30 0100 092A 0151 42CB 0150 5FFF

I can reset the system and the issue repeats,

Does anyone has any suggestions on what might be happening?

Thanks in advance.

  • 0
    TI__Genius 17440 points
    Hi Edgar,

    Could you clarify which registers you want to write to in your first commands? And is this the first time you write to the LDC1614's registers, or do you configure register values earlier as well?

    Regards,
  • 0 in reply to Kristin Jones93
    Intellectual 270 points
    Register Values are configured in Firmware during initialization,

    I'm not writing to a register, I'm just sending a command that enters the firmware in a state where it sends the data to the host every time a conversion is completed.

    The firmware itself does talks to the converter and it simply places the device in continues conversion mode, this portion works, the same works fine with Sensing Solutions GUI.

    Thanks.
  • 0 in reply to Edgar Ortega
    TI__Genius 17440 points
    Hi Edgar,

    While I would be happy to help you with device or sensor questions, unfortunately I'm not able to provide guidance for this issue. If you think that this issue is related to the device's I2C communication I'd be happy to help you debug that portion, but otherwise I think you might find more help on StackOverflow.

    Regards,