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

TRF371109EVM: Automation dll or any other way to automate TRF371109 with python script?

Rakesh Chahar
Prodigy 90 points
Part Number: TRF371109EVM
Other Parts Discussed in Thread: TRF371109, LMX2594, ADS42JB69

Hi team,

Is there anyway to automate the TRF371109 just like HSDC pro automation dll?

I want to either automate the TRF371109 GUI or directly change the value on the hardware,either way is fine.

The complete idea is to automate the complete process what we do manually, my setup consist of 4 part.

1. TRF371109 IQ demodulator,

2. LMX2594 and its gui(TICS pro), 

3.ADS42JB69E 16bit and its gui and 

4. TSW14J50 Data capture and its gui HSDC pro.

On all this parts i am manually making changes through there GUI(HSDC pro GUI,TICS pro GUI,TRF3711 GUI,ADS42 GUI), All these changes I want to Automate using the python script.

One i already found for HSDC pro using the automation dll files , similarly i am looking to automate rest 3 part number devices, please do suggest if there is anyway to do that ?

Automation scripts for HSDCPRO are available in the following location:

C:\Program Files (x86)\Texas Instruments\High Speed Data Converter Pro\HSDCPro Automation DLL\Manual and Examples

For any clarification on the above details plz do let me know ?

Thank-you in advance 

Rakesh Chahar.

 

  • 0
    TI__Mastermind 18065 points

    Rakesh:

    There is no DLL for the TRF3711.  I can give you access to the LabVIEW source code for the TRF3711 GUI; I think I can pull that out of the archives.  You may be able to use that in part of an automation suite if you are interested.

    --RJH

  • 0 in reply to RJ Hopper
    Prodigy 90 points

    Hello RJH,

    Thank-you for your reply

    ok i would try with labView source code, with TRF371109 GUI labView source code, can you also send me link to LabView source code of ADS42JB69E GUI and LMX2594 GUI(TICS pro GUI). Because i have to automate all four part(TSW14J50(HSDC PRO GUI),ADS42JB69E,TRF371109 and LMX2594)  together using one single python script. and

    it would be great if you provide a link to a document or a manual related to these automation procedures.

    Any clarification on above details please let me know !!

    Thank-you

    Rakesh Chahar

  • 0 in reply to Rakesh Chahar
    TI__Mastermind 18065 points

    Rakesh:

    Here is a link to the TRF3711 GUI LabVIEW source code: https://txn.box.com/s/0pzktrf3tpr0gqqbokto7nn93fpjzgj5.  This link is valid until 9-11-19.

    DISCLAIMER:  This source code is provided as-is.  TI will not be able to support modifications nor extensive technical support related to GUI source code.

    I am unable to assist on the ADS42JB69 as I do not have the source code available for that device.  The LMX2594 is supported from a different group and I do not know what they have available.  You may post a separate question on that device specifically so that the LMX team will see it.

    --RJH

  • 0 in reply to RJ Hopper
    Prodigy 90 points

    Hi RJH,

    I ll try out this solution using labView.

    it would be great if you could link to a document related to this Labview automation. it would be easier for me to understand the process of the labView automation using the source code you sent.

    Thank-you so much for your support.

    --Rakesh chahar

  • 0 in reply to Rakesh Chahar
    TI__Mastermind 18065 points

    Rakesh:

    I do not have any documentation for the LabVIEW source code, but I can give you a quick overview of its operation.  Hopefully the flow is easy to understand.

    The flow is:

     1. Build registers: this converts button, switches, and knob controls to appropriate register bits

     2. Write registers: this executes the SPI writes to the USB

     3. Read Registers: this reads back the registers and loads the readback values into the front panel control

    For automation you can toggle "One Shot" which will execute the GUI one time based on provided register inputs.

    --RJH

  • 0 in reply to RJ Hopper
    Prodigy 90 points

    Hi RJH,

    As I am new to Labview, it would be helpful if you could explain me the process of loading the labview source code to LabView and further instruction to carry out on labview.

    I have currently downloaded and  installed LabView 2019 from NI website.

    Thank-you for your great support.

    Regards,

    Rakesh Chahar

  • 0 in reply to Rakesh Chahar
    TI__Mastermind 18065 points

    Rakesh:

    I am concerned that this approach using the LV GUI is not going to work for you.  If you are new to LV then you have a steep learning curve on that platform and TI will not be able to provide adequate support.  Further, the GUI was created in LV version 14 and is likely not compatible with newer versions available today.  I fear that you will be chasing a myriad of issues and deviating from your true course of action.

    I think a better course for you would be to create a simple SPI driver in your automation program of choice.  TI does not have this, but you may already have the means to transfer SPI information through USB port.  Programming for the demodulator, ADC, and clock are completed through simple SPI bus.  You can use the respective GUIs to generate the required SPI address/data information, and then use that in your SPI driver to configure the respective devices.

    Alternatively, you may be able to use the existing GUIs in your set-up in a semi-automated mode where a user must intervene when a device modification is required.  Obviously not ideal for automation, but may be a faster approach to get you where you need to go.

    I apologize that TI cannot provide more assistance in this area on our older device platforms.

    --RJH