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.

TSW1400EVM: Call Library Function Node in 1400_DAC_Write.vi Error

Part Number: TSW1400EVM
Other Parts Discussed in Thread: DAC34SH84

tHello,

I am trying to run the example LabVIEW code that has been provided in an earlier post to write to our DAC34SH84. I keep getting an error code 1097 Call Library Function Node in 1400_DAC_Write.vi. I am using LabVIEW 2015 and the file is the 6076Exampl.VI from an earlier post. I could really use the help please if I could get this example coding running I would be very happy.

Thank you,

Joshua Johnson

  • Hi Joshua,

    We are looking into your question. We will reply as soon as we can.

    Regards,
    Neeraj
  • Hi Joshua,

    Have you tried running these example vi in the HSDC Pro Automation directory? This has ADC and DAC examples.
    C:\Program Files (x86)\Texas Instruments\High Speed Data Converter Pro\HSDCPro Automation DLL\Manual and Examples

    You should me able to modify the VI to have it connect to the appropriate TSW1400 serial number.

    That labview code 1097 has been associated with the FPGA not responding correctly to the DLL functions. This could be caused by not connecting to the TSW14xxx platform (ensure that HSDC Pro sees the appropriate TSW1400 serial number at the bottom of HSDC Pro after a connection command is issued), not having the firmware loaded correctly (Check TSW1400 EVM LED status after firmware load as per TSW1400 EVM users guide), not providing enough current to TSW1400EVM for the FPGA firmware to load properly (recommend 5V 3-4A).

    Let me know if any of these suggestions help.

    Ken
  • Hello Ken,

    Thank you for the response and I have tried your suggestions but now I am receiving a 7007 error code on the HSDCPro Automation DLL DAC example, which is a file not found error referring to the DAC test files but I have checked that they are indeed there. I really appreciate the help.

    Looking forward to your response,
    Joshua Johnson
  • Hi Joshua,

    Where in the process is the error occuring?  In general the automation process is similar to what you would do manually with HSDC Pro GUI.

    Have you been able to manually run the setup successfully with a DAC to generate some output?

    Ken

  • Hello Ken,

    Yes I have been able to run the HSDC Pro GUI manually many times and I even ran it after trying the automation process to ensure it isn't the HSDC Pro GUI. The error in the automation process occurs after the firmware is downloaded successfully, I can tell that the automation process is attempting to do something because I see processes being ran on the HSDC Pro. I have also noticed that the board disconnects briefly after attempting to send the data.

    Any suggestions/thoughts would be helpful and greatly appreciated,

    Joshua Johnson
  • Hi Joshua,

    When you say it disconnects, does it drop the connection, as in HSDC Pro no longer connected to the TSW1400?

    I will check with the software team to see if we can find out the cause of this error.

    Ken.
  • Joshua,

    In some cases the 5V supply drops out due to lack of current after firmware load. Can you confirm you have at least 5V 3-4A supply?

    Ken
  • Joshua,

    I spoke with our software team and they indicated that the examples were validated and should work ok. There is one condition that may cause this and that is if the path is incorrect, possibly caused by spaces at the beginning of the path.

    Also another possible cause could be if the HSDCPro Automation DLL DAC Example.vi is run in a 32b machine and if the x86 is present in the path. If this is the case you may need to move the files to another location.

    Can you send us the path that is being passed to the automation function?

    Ken.
  • Ken,

    Yes I can confirm I have 5v supply, I think the 32b machine is the problem because it is in a x86 path. The path is:

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

    What location should I move the path to and what files should I move?

    Thank you so much,

    Joshua Johnson
  • Joshua,

    I don't have a 32b machine here so I cannot confirm this - you may need to copy the entire HSDC Pro directory to c:/ to be on the safe side.

    The example may refer to the Automation Function APIs directory.

    Ken