• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 227 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.

OPT3005DTSEVM: Labview

Jonathan Navor
Genius 9475 points
Part Number: OPT3005DTSEVM

Hi Experts,

As per request by our customer, I am posting this on their behalf.

We would like control eval board OPT3005DTSEVM with LabVIEW (not with include sw-tool).

If this is possible, could you give us a command list to do this?

Thank you in advance. 


Best regards,

Jonathan

  • 0
    TI__Expert 6800 points

    Hi Jonathan,

    We do not have any resources for controlling our EVM with LabVIEW.

    Thank you,

    Brent Elliott

  • 0 in reply to Brent Elliott
    Prodigy 10 points

    Hi Brent,

    i search not resources for labview but i search a command list for control your EVM.

    I will log sensor data with own software.

  • 0 in reply to Josef Reichmuth
    TI__Expert 6800 points

    Hi Josef,

    I understand. You can control the EVM over the comport that appears when plugging in the EVM. There will be two comports, you can identify the correct port for issuing commands by writing "HWR?" to the port. The correct port will return "C". Below are the commands used to communicate with the device.

    "REGRx[address]" in place of [address], put the 2 digit hex address in order to read that register. Note that the byte order will be reversed, so the output bytes will need to be switched to get the correct value.

    Ex. REGRx01 might return 0x0102, meaning the register value is 0x0201.

    "REGWx[address]x[value]" write [value] in 4 digit hex format to [address] in 2 digit hex format.

    Ex: REGWx02x0FFF will write 0x0FFF to register address 0x02.

    Let me know if you have any further questions.

    Thank you,

    Brent Elliott