• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 33 subscribers
  • Views 312 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.

TIDM-ULTRASONIC-FLOW-TDC: Echo Threshold not set properly

May
Genius 9880 points
Part Number: TIDM-ULTRASONIC-FLOW-TDC
Other Parts Discussed in Thread: TDC1000, TDC7200

Hi,

Customer is using the TIDM-ULTRASONIC-TDC board and encountering some inconsistency in their design. More details below.

"

I'm dealing with the TIDM-ULTRASONIC-TDC board, I also removed some parts of it like the RF and the LCD section from it. on my test board, it worked properly. Now I ordered a few more PCBs of the customed PCB and more components, but there is something odd. When I set ECHO_QUAL_THDL to anything except -75mv and -775mv in the GUI, it only excites one Piezoelectric but it supposes to excite both channels for flow measurement purposes.

I doubt that there is something wrong with my CCS, According to the datasheet it should be programmed with CCS v6 but it pop-up an error, so I have to compile it with CCSv7.

The changed schematic is attached to the file. In addition, I noticed that some parameters of TDC1000 and TDC7200 are not their default values even after programming the MSP, e.g. according to the datasheet the ECHO_QUAL_THLD register should be 3h: –125 mV (default) but after programing the MSP While I read registers this register value is -75mv except -125mv. Few registers like the Measurement mode of TDC7200 have the same situation.

6038.TID-PCB-EDITED_1.pdf

Regards,
Maynard

  • 0
    TI__Genius 11296 points

    Hi Maynard,

    Thank you for relaying the information.

    I have not encountered an issue like this before, it seems abnormal to program the device and not receive the expected data back. 

    Is it possible to issue a read command on all of the TDC1000 and TDC7200 registers? This will allow me to compare the expected programmed values to the actual read values. 

    In the meantime, I will verify the schematic looks proper from a hardware perspective. 

    Finally, were there any other changes from the test board to the customer board? 

    Please let me know if you have any questions.

    Thank you,

    Jacob

  • 0 in reply to Jacob Nogaj
    TI__Genius 9880 points

    Hi Jacob,

    Just received response from customer, details below.

    "Actually, only a few parts of it that were unused were excluded from the schematic and the program of the MSP430FR is same as the sample which is provided on the TI Website.

    Is it possible using the CCS v7.4.0 except using the v6.1 cause this problem? according to the document "tidu965a", Section 7.2 instruction, it should be programmed with v6.1 of CSS, "Program it using CCS 6.1, with the firmware which defines PC GUI by using "#define OPERATION_MODE 2" in "global.h". After that, exit CCS." 

    Reading registers is ok, when I set parameters, after a while I try to read them their values are what I've set.
    "

    Regards,
    Maynard

  • 0 in reply to May
    TI__Genius 11296 points

    Hi Maynard, 

    Thank you for describing the read register values. 


    It is possible that the version of CCS is causing the problem. Can you try using CCS v6.1 to program the firmware? This will verify if CCS is the reason for issue.

    Thank you,

    Jacob

     

  • 0 in reply to Jacob Nogaj
    TI__Genius 9880 points

    Hi Jacob,

    Customer tried using the CCS v6.1 but encountered an error, details below.

    The compiler on v6.1.3 show a warning after make the code and pop-up an error during the programming procedure.

    The warning message:

    This project was created using a version of compiler that is not currently installed: 4.4.3 [MSP430]. Another version of the compiler will be used during build: 15.12.1.LTS. Go to 'Help > Check for Updates' page to check for updates and visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compilers. Go to 'Help > Install New Software...' to install older compilers. Alternatively, migrate the project to one of the available compiler versions by adjusting project properties


    The error message:

    Error initializing emulator:
    Could not set device Vcc

    Regards,
    Maynard

  • 0 in reply to May
    TI__Genius 11296 points

    Hi Maynard, 

    Thank you for the update, sorry the issue still persists.

    The error message regarding the compiler version makes me think there could still be issues with CCS. I found this thread that includes a link to CCS 6.1.0 specifically mentioned to include 4.4.3 for the MSP. :https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/939457/ccs-ccstudio-msp-msp430-compiler-version-for-ccsv6-1-0-and-6-1-1/3469888?tisearch=e2e-sitesearch&keymatch=4.4.3%2520%255BMSP430%255D#3469888

    Additionally, can the customer measure the voltage at VCC. I would like to understand if the error message is correct in mentioning VCC not being set properly. 

    Thank you,

    Jacob

  • 0 in reply to Jacob Nogaj
    TI__Genius 9880 points

    Hi Jacob,

    Just received response from customer, details below.

    I measured the VCC and also see the voltage on the oscilloscope, the VCC is 3.25v DC. I also couldn't find any download link of the CCSv6.1 on the mentioned thread, the link in the thread guide to a web page that only mention specification, features, etc.
    I have check the compiler but I cannot also find the compiler in our side: http://software-dl.ti.com/codegen/non-esd/downloads/download_archive.htm#MSP430

    Regards,
    Maynard

  • 0 in reply to May
    TI__Genius 11296 points

    Hi Maynard,

    Can the customer program the TDC7200 and TDC1000 without using the GUI? I want to understand if the issue is software or hardware related. If the customer is willing to test some of the configuration options that were previously not working, we will gain a better understanding of where to continue debugging.

    Thank you,

    Jacob