• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 487 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:

PGA305EVM-034: PGA305EVM

PGA305EVM-034: PGA305EVM-034

jey TS
Prodigy 20 points

Part Number: PGA305EVM-034

Hi, 

when using the standard PGA305 labview run time module from TE, the OWI activation pulses are as in the manual "PGA 305 signal conditioner and transmjtter for pressure sensors - SLDS231" page 24 . 2 pulse sequence with  Pulse ON 10 ms, OFF 20 ms , delay 110 ms  

1. When trying to activate the OWI directly from own Labview Program -  the Pulse ON and OFF time duration change with each execution and OWI is not activated. 

Vi property  -Execution set to high priority.

used "delay" , "ms wait" , " high resolution polling wait " .vi in labview 

part of code:

output from oscilloscope - pulse sequence 1

this varies with every run,

can you please suggest a way to get tigger pulse duration correct with Labview .

  • 0
    TI__Guru** 113765 points

    Hi jey TS,

    Welcome to the E2E forum! The EVM uses the GPIO signals from the USB2ANY to control the activation pulses.  Are you attempting to use the USB2ANY or are you directly interfacing some other controller to the EVM?

    Unfortunately I can't really help you with the timing of your LabView program.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 20 points

    Hi bob, 

    Thanks for quick reply.

    I am using USB2ANY and Labview interface module to EVM305.

    1. The interface module to EVM305 from Ti is based on Labview . I was just wondering with LABView and windows OS ( 10/11) ,is it really possible to achieve these accurate 10 ms timing requirement each time . Or is there any other setting we  need to make. 

    2. Or do i need to consider LAbview Realtime with Real TIme OS: 

    3. can TI help with the LABView source code  to the OWI  pulse trigger portion 

    thanks 

    Jey

  • 0 in reply to jey TS
    TI__Guru** 113765 points

    Hi Jey,

    Unfortunately TI has very limited resources for helping you with respect to code.   I currently do not have access to the LabView VIs for the GUI to help determine how the OWI activation is commanded on the USB2ANY.  As the USB2ANY communication is HID, this is probably a bigger issue than the LabView portion.  You could review the USB2ANY documentation to see what can be done here.  There is an API reference for USB2ANY located in your install directory:

    Included in the reference are the function calls for OWI stating in section 5.16 on page 73.

    This thread may also be helpful.

    Best regards,

    Bob B